| Summary: | Blank Screen on Startup, With Cursor | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | colony.three |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | grave | CC: | cfeck |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Starts just fine in XFCE.
This is on an Asus H87M-Pro motherboard with Intel E3-1265L v3 CPU graphics.
Also:
[code] $ ps aux |grep plasma
bill 7503 0.0 0.3 365352 27584 ? S 15:48 0:00 /usr/bin/plasma-desktop
bill 7504 0.2 0.0 0 0 ? Zl 15:48 0:00 [plasma-desktop] <defunct>
bill 8008 0.0 0.0 10340 868 pts/4 S+ 15:52 0:00 grep plasma
$ pkill -11 plasma-desktop
$ ps aux |grep plasmatop
bill 7504 0.2 0.0 0 0 ? Zl 15:48 0:00 [plasma-desktop] <defunct>
bill 8133 0.6 0.3 365352 27584 ? S 15:53 0:00 /usr/bin/plasma-desktop --nocrashhandler
bill 8134 2.0 0.3 412612 29240 ? Sl 15:53 0:00 /usr/lib/kde4/libexec/drkonqi -display :53 --appname plasma-desktop --apppath /usr/bin --signal 11 --pid 7504 --appversion 4.11.7 --programname Plasma Desktop Shell --bugaddress submit@bugs.kde.org --startupid 0 --restarted
bill 8135 2.3 0.3 475252 24804 ? S 15:53 0:00 /usr/bin/plasma-desktop --nocrashhandler
bill 8152 0.0 0.0 10340 864 pts/4 S+ 15:53 0:00 grep plasma
$ killall -9 plasma-desktop
$ ps aux |grep plasma
bill 8134 0.1 0.3 412612 29240 ? Sl 15:53 0:00 /usr/lib/kde4/libexec/drkonqi -display :53 --appname plasma-desktop --apppath /usr/bin --signal 11 --pid 7504 --appversion 4.11.7 --programname Plasma Desktop Shell --bugaddress submit@bugs.kde.org --startupid 0 --restarted
bill 8261 0.0 0.0 10340 864 pts/4 S+ 15:53 0:00 grep plasma
$ kill 8134
$ ps aux |grep plasma
bill 8295 0.0 0.0 10340 864 pts/4 S+ 15:54 0:00 grep plasma
$ export DISPLAY=:0
$ plasma-desktop
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
plasma-desktop(9342): KUniqueApplication: Cannot find the D-Bus session server: "/usr/bin/dbus-launch terminated abnormally with the following error: Invalid MIT-MAGIC-COOKIE-1 keyAutolaunch error: X11 initialization failed."
plasma-desktop(9341): KUniqueApplication: Pipe closed unexpectedly. [/code]
Starts just fine in XFCE.
This is on an Asus H87M-Pro motherboard with Intel E3-1265L v3 CPU graphics.
Also:
[code] $ ps aux |grep plasma
bill 7503 0.0 0.3 365352 27584 ? S 15:48 0:00 /usr/bin/plasma-desktop
bill 7504 0.2 0.0 0 0 ? Zl 15:48 0:00 [plasma-desktop] <defunct>
bill 8008 0.0 0.0 10340 868 pts/4 S+ 15:52 0:00 grep plasma
$ pkill -11 plasma-desktop
$ ps aux |grep plasmatop
bill 7504 0.2 0.0 0 0 ? Zl 15:48 0:00 [plasma-desktop] <defunct>
bill 8133 0.6 0.3 365352 27584 ? S 15:53 0:00 /usr/bin/plasma-desktop --nocrashhandler
bill 8134 2.0 0.3 412612 29240 ? Sl 15:53 0:00 /usr/lib/kde4/libexec/drkonqi -display :53 --appname plasma-desktop --apppath /usr/bin --signal 11 --pid 7504 --appversion 4.11.7 --programname Plasma Desktop Shell --bugaddress submit@bugs.kde.org --startupid 0 --restarted
bill 8135 2.3 0.3 475252 24804 ? S 15:53 0:00 /usr/bin/plasma-desktop --nocrashhandler
bill 8152 0.0 0.0 10340 864 pts/4 S+ 15:53 0:00 grep plasma
$ killall -9 plasma-desktop
$ ps aux |grep plasma
bill 8134 0.1 0.3 412612 29240 ? Sl 15:53 0:00 /usr/lib/kde4/libexec/drkonqi -display :53 --appname plasma-desktop --apppath /usr/bin --signal 11 --pid 7504 --appversion 4.11.7 --programname Plasma Desktop Shell --bugaddress submit@bugs.kde.org --startupid 0 --restarted
bill 8261 0.0 0.0 10340 864 pts/4 S+ 15:53 0:00 grep plasma
$ kill 8134
$ ps aux |grep plasma
bill 8295 0.0 0.0 10340 864 pts/4 S+ 15:54 0:00 grep plasma
$ export DISPLAY=:0
$ plasma-desktop
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
plasma-desktop(9342): KUniqueApplication: Cannot find the D-Bus session server: "/usr/bin/dbus-launch terminated abnormally with the following error: Invalid MIT-MAGIC-COOKIE-1 keyAutolaunch error: X11 initialization failed."
plasma-desktop(9341): KUniqueApplication: Pipe closed unexpectedly. [/code]
Another thing I notice is that kwin is crashing and crashing and crashing. ps aux |grep kwin gives a new pid every time, no matter how fast I run it. Could you try running kwin in gdb to get a backtrace of the crash? How? I have a black screen and cannot <alt><f2>, <ctrl><alt><f1>, or
<alt><shift><f12>.
With x2go I can xfce, but when set x2go to KDE, again black screen.
I've removed the last remaining fglrx GLX driver, and now kwin is not
crashing anymore. Seems to hold the same PID for a good while. But
still the black screen with (working) cursor.
On Mon, Mar 31, 2014, at 3:17, Christoph Feck wrote:
> https://bugs.kde.org/show_bug.cgi?id=332744
>
> Christoph Feck <christoph@maxiom.de> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |christoph@maxiom.de
>
> --- Comment #4 from Christoph Feck <christoph@maxiom.de> ---
> Could you try running kwin in gdb to get a backtrace of the crash?
>
> --
> You are receiving this mail because:
> You reported the bug.
Hello? Sorry, this ticket escaped my radar. If this is still an issue, in particular with kwin crashing, could you please add a comment? Note that to get a backtrace from kwin, you can try the following: - start a different window manager, e.g. xfce, and open a terminal - in this terminal, run "gdb --args kwin --replace" - you will then hopefully get a crash, use "bt" to get the backtrace, and save to a file - restart xfce window manager to continue working. I guess without a backtrace, kwin developers cannot help. (In reply to comment #5) > I've removed the last remaining fglrx GLX driver, and now kwin is not > crashing anymore. Seems to hold the same PID for a good while. But > still the black screen with (working) cursor. That would match the OP and indicate that kwin is up and compositing (Shift+Alt+F12 works?) but aparently neither plasma-desktop nor krunner are. This and esp. Debian Testing and even more the XFCE warnings about the failure to contact dbus would match http://forum.kde.org/viewtopic.php?f=66&t=120323 Is the the same or just an equal case (ie. are you "Quantum")? I am Quantum. This plasma-desktop crash is caused by the USB driver not being able to handle some legacy devices. I had to unplug my Silverstone USB touchscreen in order to make KDE work. Quoting Ben from forum.kde.org:
"In this case, there is very little KDE could do to solve the issue. It is completely unexpected behaviour that system services such as UPower, UDisks, etc. will misbehave in such a manner. Future changes to the Solid interface to make it asynchronous would be the only way to fix it at the KDE level (I think there may be such plans as part of KDE Frameworks 5, but i'm not sure).
The issue was caused because the XHCI driver problems caused those system services (UDisks, UPower) to become hung or crash, causing a kernel oops in the process. It is likely the card reader was a principal cause of this. As a result, KDE became hung awaiting their responses - in virtually all cases these services reply instantaneously, but this didn't occur in your case."
|
Since the latest dist-upgrade KDE will not start. This is the case whether I start it from KDM or X2Go. It steps through the splash-screen steps but stays on the finak K for 10 minutes or so, and finally reverts to a black screen with (operational cursor. <alt><f2> has no effect, and <alt><shift><f12> only flips back and forth between the splash screen and black page. [code]# ps aux |grep kwin root 6807 0.0 0.0 10340 864 pts/5 S+ 15:08 0:00 grep kwin bill 7496 0.0 0.4 556732 38872 ? S 07:53 0:00 kwin -session 10d8ec676e000139560321300000229020000_1395817946_697074 # PID=7496 # export DBUS_SESSION_BUS_ADDRESS="`tr '\0' '\n' < /proc/${PID}/environ | grep D_SESSION_BUS_ADDRESS | cut -d"=" -f2-`" # export DISPLAY=:0 # plasma-desktop QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. plasma-desktop(6893): KUniqueApplication: Cannot find the D-Bus session server: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." plasma-desktop(6892): KUniqueApplication: Pipe closed unexpectedly. [/code] .xsession-errors [code]Xsession: X session started for bill at Thu Mar 27 18:39:54 PDT 2014 localuser:bill being added to access control list /etc/X11/Xsession.d/98vboxadd-xclient: line 45: /usr/bin/VBoxClient: No such file or directory /etc/X11/Xsession.d/98vboxadd-xclient: line 46: /usr/bin/VBoxClient: No such file or directory /etc/X11/Xsession.d/98vboxadd-xclient: line 48: /usr/bin/VBoxClient: No such file or directory /etc/X11/Xsession.d/98vboxadd-xclient: line 50: /usr/bin/VBoxClient: No such file or directory /etc/X11/Xsession.d/98vboxadd-xclient: line 52: /usr/bin/VBoxClient: No such file or directory /usr/bin/startxfce4: X server already running on display :0 xfce4-session-Message: gpg-agent is already running QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. [1395970805] [ERR] hddtemp: failed to open connection. libpager-Message: Setting the pager rows returned false. Maybe the setting is not applied. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) glibtop: Non-standard uts for running kernel: release 3.13-1-amd64=3.13.0 gives version code 199936 QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. (xfdesktop:3143): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed kbuildsycoca4 running... konqueror(3146)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "searchproviders/wikit.desktop" not found kded(3490) KDEDModule::setModuleName: registerObject() successful for "favicons" kded(3490) FavIconsModule::iconForUrl: URL: KUrl("https://www.google.com/search?q=%5C%7B@%7D&ie=UTF-8") ICON: "favicons/www.google.com" kded(3490) FavIconsModule::iconForUrl: URL: KUrl("https://en.wikipedia.org/wiki/Special:Search?search=%5C%7B@%7D&go=Go") ICON: "favicons/en.wikipedia.org" kded(3490) FavIconsModule::iconForUrl: URL: KUrl("http://search.yahoo.com/search?toggle=1&cop=mss&ei=UTF-8&fr=yfp-t-701&p=%5C%7B@%7D&x=0&y=0&=Web+Search") ICON: "favicons/search.yahoo.com" kded(3490) FavIconsModule::iconForUrl: URL: KUrl("https://www.youtube.com/results?search_query=%5C%7B@%7D&search_type=&aq=f") ICON: "favicons/www.youtube.com" klauncher(3251)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "kactivitymanagerd.desktop" not found kded(3490) KDEDModule::setModuleName: registerObject() successful for "ktimezoned" konqueror(3146)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: konqueror(3146)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: konqueror(3146)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: glibtop: Non-standard uts for running kernel: release 3.13-1-amd64=3.13.0 gives version code 199936 glibtop: Non-standard uts for running kernel: release 3.13-1-amd64=3.13.0 gives version code 199936 (xfce4-session:3117): xfce4-session-WARNING **: ICE connection 0x7fed15ec5420 rejected (xfce4-session:3117): xfce4-session-WARNING **: ICE connection 0x7fed15e97cb0 rejected (xfce4-terminal:3847): GLib-WARNING **: (/tmp/buildd/glib2.0-2.38.2/./glib/gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0) Failed to connect to session manager: Failed to connect to the session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed 2014-03-27 18:41:49.187942 I Setup Interrupt handler 2014-03-27 18:41:49.187965 I Setup Terminated handler 2014-03-27 18:41:49.187969 I Setup Segmentation fault handler 2014-03-27 18:41:49.187973 I Setup Aborted handler 2014-03-27 18:41:49.187976 I Setup Bus error handler 2014-03-27 18:41:49.187980 I Setup Floating point exception handler 2014-03-27 18:41:49.187983 I Setup Illegal instruction handler 2014-03-27 18:41:49.187988 I Setup Real-time signal 0 handler 2014-03-27 18:41:49.187993 I Setup User defined signal 1 handler 2014-03-27 18:41:49.187996 I Setup User defined signal 2 handler 2014-03-27 18:41:49.188071 C mythfrontend version: fixes/0.27 [9bf1070] www.mythtv.org 2014-03-27 18:41:49.188076 C Qt version: compile: 4.8.6, runtime: 4.8.6 2014-03-27 18:41:49.188079 N Enabled verbose msgs: general 2014-03-27 18:41:49.188090 N Setting Log Level to LOG_INFO 2014-03-27 18:41:49.188217 N Using runtime prefix = /usr/local 2014-03-27 18:41:49.188225 N Using configuration directory = /home/bill/.mythtv 2014-03-27 18:41:49.188274 I Added logging to the console 2014-03-27 18:41:49.188289 I Assumed character encoding: en_US.UTF-8 2014-03-27 18:41:49.188715 I Using localhost value of hex 2014-03-27 18:41:49.195495 N Setting QT default locale to en_US 2014-03-27 18:41:49.195539 I Current locale en_US 2014-03-27 18:41:49.195567 N Reading locale defaults from /usr/local/share/mythtv//locales/en_us.xml 2014-03-27 18:41:49.267041 I Starting process manager 2014-03-27 18:41:49.267048 I Starting process signal handler 2014-03-27 18:41:49.267071 I Starting IO manager (read) 2014-03-27 18:41:49.267087 I Starting IO manager (write) 2014-03-27 18:41:49.367308 I ScreenSaverX11Private: XScreenSaver support enabled 2014-03-27 18:41:49.367949 I ScreenSaverX11Private: DPMS is active. 2014-03-27 18:41:49.411889 I Added logging to mythlogserver at TCP:35327 2014-03-27 18:41:49.443119 N Desktop video mode: 1920x1080 60.000 Hz 2014-03-27 18:41:49.763547 I Listening on TCP 127.0.0.1:6547 2014-03-27 18:41:50.746829 I Loading en_us translation for module mythfrontend 2014-03-27 18:41:50.870312 I UDPListener: Enabling 2014-03-27 18:41:50.870738 I Binding to UDP 127.0.0.1:6948 2014-03-27 18:41:50.949366 I Using Frameless Window 2014-03-27 18:41:50.949389 I Using Full Screen Window 2014-03-27 18:41:50.966175 I Using the Qt painter 2014-03-27 18:41:51.777284 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.777645 E MythSocket(7f8fb8012a90:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.777726 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.777742 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.777865 E MythSocket(7f8fac00c3c0:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.777903 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.777921 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.778037 E MythSocket(7f8fb8016680:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.778073 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.778085 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.778222 E MythSocket(7f8fac00c220:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.778258 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.778281 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.778410 E MythSocket(7f8fa800bec0:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.778453 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.778587 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.778712 E MythSocket(7f8fac0124a0:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.778748 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.778973 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.779085 E MythSocket(7f8fac00c170:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.779117 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.779976 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.780087 E MythSocket(7f8fac00c170:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.780118 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.781214 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.781337 E MythSocket(7f8fac01b290:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.781399 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.783039 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.783154 E MythSocket(7f8fac01be90:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.783214 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.783752 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.783898 E MythSocket(7f8fac01eea0:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.783959 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.784077 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.784247 E MythSocket(7f8fac024090:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.784311 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.784332 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.784512 E MythSocket(7f8fb8019610:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.784575 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:51.786268 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:51.786429 E MythSocket(7f8fac027050:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:51.786506 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:52.527107 I MythUIWebBrowser: Loading css from - file:///usr/local/share/mythtv/themes/default/htmls/mythbrowser.css 2014-03-27 18:41:52.533909 E MythUIWebBrowser: failed to find our parent screen 2014-03-27 18:41:52.535494 I MythUIWebBrowser: enabling plugins 2014-03-27 18:41:52.562089 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:52.562394 E MythSocket(7f8fac01ec80:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:52.562496 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:52.610615 I AirPlay: Created airplay objects. 2014-03-27 18:41:52.610676 E RAOP Device: Aborting startup - no key found. 2014-03-27 18:41:52.610700 I Listening on TCP 127.0.0.1:5100 2014-03-27 18:41:52.621644 I Current MythTV Schema Version (DBSchemaVer): 1317 2014-03-27 18:41:53.559329 I Bonjour: Service registration complete: name 'MythTV on hex' type '_airplay._tcp.' domain: 'local.' 2014-03-27 18:41:55.460510 N Registering Internal as a media playback plugin. 2014-03-27 18:41:55.568825 A MMUnix:CheckMountable: DBus interface error: 2014-03-27 18:41:56.232832 I Loading en_us translation for module mytharchive 2014-03-27 18:41:56.286761 N Registering WebBrowser as a media playback plugin. 2014-03-27 18:41:56.300853 I Loading en_us translation for module mythbrowser 2014-03-27 18:41:56.390702 I Loading en_us translation for module mythgallery 2014-03-27 18:41:56.396918 I Loading en_us translation for module mythgame 2014-03-27 18:41:56.924652 I Current MythMusic Schema Version (MusicDBSchemaVer): 1020 2014-03-27 18:41:56.965992 I Loading en_us translation for module mythmusic 2014-03-27 18:41:57.003290 I Loading en_us translation for module mythnetvision 2014-03-27 18:41:57.133326 I Loading en_us translation for module mythnews 2014-03-27 18:41:57.204009 I Loading en_us translation for module mythweather 2014-03-27 18:41:57.240383 I Loading en_us translation for module mythzoneminder 2014-03-27 18:41:57.296932 I Listening on TCP 127.0.0.1:6546 2014-03-27 18:41:57.298754 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:57.298978 E MythSocket(7f8fac021d20:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:57.299031 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:57.299058 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:57.299239 E MythSocket(7f8fb8012eb0:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:57.299285 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:57.400174 N Found mainmenu.xml for theme 'Mythbuntu' 2014-03-27 18:41:57.401981 I Registering HouseKeeperTask 'HardwareProfiler'. 2014-03-27 18:41:57.432067 I Starting HouseKeeper. 2014-03-27 18:41:57.437991 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:57.438302 E MythSocket(7f8fac024ab0:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:57.438374 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:57.482226 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:41:57.482501 E MythSocket(7f8fac015d90:-1): Failed to connect to (127.0.0.1:6543) Connection refused 2014-03-27 18:41:57.482564 E Connection to master server timed out. Either the server is down or the master server settings in mythtv-settings does not contain the proper IP address 2014-03-27 18:41:57.504382 I Bonjour: Service registration complete: name 'Mythfrontend on hex' type '_mythfrontend._tcp.' domain: 'local.' 2014-03-27 18:42:01.539215 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1) 2014-03-27 18:42:01.540084 I Using protocol version 77 2014-03-27 18:42:02.939347 N Resuming idle timer 2014-03-27 18:42:02.939366 N Resuming idle timer 2014-03-27 18:42:07.241048 I Bonjour: De-registering service '_mythfrontend._tcp.' on 'Mythfrontend on hex' 2014-03-27 18:42:07.241222 I RAOP Device: Cleaning up. 2014-03-27 18:42:07.241230 I AirPlay: Cleaning up. 2014-03-27 18:42:07.241306 I Bonjour: De-registering service '_airplay._tcp.' on 'MythTV on hex' 2014-03-27 18:42:07.241487 I Shutting down UPnP client... 2014-03-27 18:42:07.657398 I Waiting for threads to exit. (Thunar:3959): GLib-CRITICAL **: g_hash_table_foreach_remove_or_steal: assertion 'version == hash_table->version' failed g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. xfce4-session-Message: Got disconnected from D-Bus. Unless this happened during session shutdown, this is probably a bad thing. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. (kdeinit4: kded4 [kdeinit]:3490): GConf-WARNING **: Got Disconnected from DBus. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. ** (xfdesktop:3143): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfdesktop:3143): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed ** (xfsettingsd:3197): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed (xfwm4:19645): xfwm4-CRITICAL **: Xfconf could not be initialized (xfwm4:19645): xfwm4-WARNING **: Missing data from default files (xfwm4:19648): xfwm4-CRITICAL **: Xfconf could not be initialized (xfwm4:19648): xfwm4-WARNING **: Missing data from default files (xfwm4:19649): xfwm4-CRITICAL **: Xfconf could not be initialized (xfwm4:19649): xfwm4-WARNING **: Missing data from default files (xfwm4:19650): xfwm4-CRITICAL **: Xfconf could not be initialized (xfwm4:19650): xfwm4-WARNING **: Missing data from default files (xfwm4:19651): xfwm4-CRITICAL **: Xfconf could not be initialized (xfwm4:19651): xfwm4-WARNING **: Missing data from default files (xfce4-session:3117): xfce4-session-CRITICAL **: Unable to contact D-Bus session bus: Failed to connect to socket /tmp/dbus-DrXVxAiVbx: Connection refused ** (xfdesktop:19647): WARNING **: xfdesktop: unable to connect to settings daemon: Failed to connect to socket /tmp/dbus-DrXVxAiVbx: Connection refused. Defaults will be used ** (xfdesktop:19647): CRITICAL **: xfce_desktop_new: assertion 'channel && property_prefix' failed (xfdesktop:19647): Gtk-CRITICAL **: IA__gtk_widget_add_events: assertion 'GTK_IS_WIDGET (widget)' failed (xfdesktop:19647): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19647): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19647): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19647): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19647): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19647): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19647): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19647): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19647): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed (xfce4-session:3117): xfce4-session-CRITICAL **: Unable to contact D-Bus session bus: Failed to connect to socket /tmp/dbus-DrXVxAiVbx: Connection refused ** (xfdesktop:19653): WARNING **: xfdesktop: unable to connect to settings daemon: Failed to connect to socket /tmp/dbus-DrXVxAiVbx: Connection refused. Defaults will be used ** (xfdesktop:19653): CRITICAL **: xfce_desktop_new: assertion 'channel && property_prefix' failed (xfdesktop:19653): Gtk-CRITICAL **: IA__gtk_widget_add_events: assertion 'GTK_IS_WIDGET (widget)' failed (xfdesktop:19653): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19653): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19653): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19653): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19653): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19653): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19653): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19653): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19653): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed (xfce4-session:3117): xfce4-session-CRITICAL **: Unable to contact D-Bus session bus: Failed to connect to socket /tmp/dbus-DrXVxAiVbx: Connection refused ** (xfdesktop:19654): WARNING **: xfdesktop: unable to connect to settings daemon: Failed to connect to socket /tmp/dbus-DrXVxAiVbx: Connection refused. Defaults will be used ** (xfdesktop:19654): CRITICAL **: xfce_desktop_new: assertion 'channel && property_prefix' failed (xfdesktop:19654): Gtk-CRITICAL **: IA__gtk_widget_add_events: assertion 'GTK_IS_WIDGET (widget)' failed (xfdesktop:19654): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19654): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19654): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19654): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19654): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19654): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19654): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19654): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19654): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed (xfce4-session:3117): xfce4-session-CRITICAL **: Unable to contact D-Bus session bus: Failed to connect to socket /tmp/dbus-DrXVxAiVbx: Connection refused ** (xfdesktop:19655): WARNING **: xfdesktop: unable to connect to settings daemon: Failed to connect to socket /tmp/dbus-DrXVxAiVbx: Connection refused. Defaults will be used ** (xfdesktop:19655): CRITICAL **: xfce_desktop_new: assertion 'channel && property_prefix' failed (xfdesktop:19655): Gtk-CRITICAL **: IA__gtk_widget_add_events: assertion 'GTK_IS_WIDGET (widget)' failed (xfdesktop:19655): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19655): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19655): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19655): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19655): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19655): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19655): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19655): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19655): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed (xfce4-session:3117): xfce4-session-CRITICAL **: Unable to contact D-Bus session bus: Failed to connect to socket /tmp/dbus-DrXVxAiVbx: Connection refused ** (xfdesktop:19656): WARNING **: xfdesktop: unable to connect to settings daemon: Failed to connect to socket /tmp/dbus-DrXVxAiVbx: Connection refused. Defaults will be used ** (xfdesktop:19656): CRITICAL **: xfce_desktop_new: assertion 'channel && property_prefix' failed (xfdesktop:19656): Gtk-CRITICAL **: IA__gtk_widget_add_events: assertion 'GTK_IS_WIDGET (widget)' failed (xfdesktop:19656): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19656): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19656): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19656): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19656): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19656): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19656): GLib-GObject-WARNING **: invalid (NULL) pointer instance (xfdesktop:19656): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:19656): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed[/code] Xorg.0.log [code]This bugtracker would not allow me to post Xorg.0.log[/code] Reproducible: Always Steps to Reproduce: 1. Boot the system and log in. 2. Or, start an x2go session. 3. Actual Results: Black screen with operational cursor. Expected Results: Brought me to the desktop. I've de/reinstalled KDE, and no change. I've logged in as a test user, and no change.