Xfce Forum

nostro2

Member

Registered: 2017-01-02

Posts: 5

Xfce not initializing properly from startup

When logging in to my laptop from XDM xfce is failing to completely load and initialize.

The background and panel fail to load making it hard to do anything. The only log file I could think of looking at was ~/.xsession-errors And I got some really weird results.

/usr/bin/startxfce4: X server already running on display :0
gpg-agent[453]: WARNING: "--write-env-file" is an obsolete option - it has no effect
gpg-agent[454]: gpg-agent (GnuPG) 2.1.17 started

(xfce4-session:437): xfce4-session-WARNING **: gpg-agent returned no PID in the variables

** (wrapper-1.0:685): WARNING **: Binding 'XF86AudioLowerVolume' failed!

** (wrapper-1.0:685): WARNING **: Binding 'XF86AudioRaiseVolume' failed!

** (wrapper-1.0:685): WARNING **: Binding 'XF86AudioMute' failed!

(xfce4-terminal:675): Gtk-WARNING **: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node header owner GtkNotebook)

(blueman-applet:719): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
[1052:1072:0104/225316:ERROR:upload_data_presenter.cc(77)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader&)
A Parser-blocking, cross-origin script, http://www.adbayes.com/LoadUnit.jtp?c=1&url=http%3A%2F%2Fxfce.10915.n7.nabble.com%2Fhow-to-restart-panel-td43207.html, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.adbayes.com/LoadUnit.jtp?c=1&url=http%3A%2F%2Fxfce.10915.n7.nabble.com%2Fhow-to-restart-panel-td43207.html, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: cHRM chunk does not match sRGB
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[1052:1072:0104/225350:ERROR:ssl_client_socket_impl.cc(1146)] handshake failed; returned -1, SSL error code 1, net_error -100
[826:826:0104/230835:ERROR:KeyboardEventManager.cpp(344)] Not implemented reached in static bool blink::KeyboardEventManager::currentCapsLockState()
[826:826:0104/230907:ERROR:KeyboardEventManager.cpp(344)] Not implemented reached in static bool blink::KeyboardEventManager::currentCapsLockState()
[826:826:0104/230907:ERROR:KeyboardEventManager.cpp(344)] Not implemented reached in static bool blink::KeyboardEventManager::currentCapsLockState()

There is also something that is bothering me from the log file... its this section

[1052:1072:0104/225316:ERROR:upload_data_presenter.cc(77)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader&)
A Parser-blocking, cross-origin script, http://www.adbayes.com/LoadUnit.jtp?c=1&url=http%3A%2F%2Fxfce.10915.n7.nabble.com%2Fhow-to-restart-panel-td43207.html, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.adbayes.com/LoadUnit.jtp?c=1&url=http%3A%2F%2Fxfce.10915.n7.nabble.com%2Fhow-to-restart-panel-td43207.html, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://pagead2.googlesyndication.com/pagead/show_ads.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.

What is this and why does it look like adware?

ToZ

Administrator

From: Canada

Registered: 2011-06-02

Posts: 11,492

Re: Xfce not initializing properly from startup

When logging in to my laptop from XDM xfce is failing to completely load and initialize.

What exactly is happening (or not happening) that leads you to believe that it is not loading properly?

Have you tried clearing your cached sessions by deleting the ~/.cache/sessions folder before you log in? This is known to solve alot of start up problems related to cached sessions - which may or may not be your issue.

A Parser-blocking, cross-origin script,

A new chrome/chromium feature. For more info, see: https://www.chromestatus.com/feature/5718547946799104

---

Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

nostro2

Member

Registered: 2017-01-02

Posts: 5

Re: Xfce not initializing properly from startup

A new chrome/chromium feature. For more info, see: https://www.chromestatus.com/feature/5718547946799104

Thanks, this answer makes me feel better!

Have you tried clearing your cached sessions by deleting the ~/.cache/sessions folder before you log in? This is known to solve alot of start up problems related to cached sessions - which may or may not be your issue.

I just tried it now... it did not work.

What exactly is happening (or not happening) that leads you to believe that it is not loading properly?

After logging in from my DM, my wallpapers and desktop shortcuts are not loaded (gray background) and my panel does not load (no top or bottom navigation). Some startup applications load like teamviewer and terminal (thank god), but thats it. From terminal I can run xfce4-panel. After restarting a few times I still get the same behaviour with the exception that now xfce sends an error saying something along the line of "xfce4-panel is not running... would you like to run it?". How can I change the startup process so it loads properly the first time?

Edit: Is there any other log files that will help you determine the problem?

Last edited by nostro2 (2017-01-05 19:10:36)

ToZ

Administrator

From: Canada

Registered: 2011-06-02

Posts: 11,492

Re: Xfce not initializing properly from startup

Edit: Is there any other log files that will help you determine the problem?

Maybe. Which distro are you using?

What exactly is happening (or not happening) that leads you to believe that it is not loading properly?

After logging in from my DM, my wallpapers and desktop shortcuts are not loaded (gray background) and my panel does not load (no top or bottom navigation). Some startup applications load like teamviewer and terminal (thank god), but thats it. From terminal I can run xfce4-panel. After restarting a few times I still get the same behaviour with the exception that now xfce sends an error saying something along the line of "xfce4-panel is not running... would you like to run it?". How can I change the startup process so it loads properly the first time?

How have you configured XDM to start Xfce?

---

Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

nostro2

Member

Registered: 2017-01-02

Posts: 5

Re: Xfce not initializing properly from startup

My Distro is Arch Linux.
Xfce is started by appending the following line my ~/.xinitrc file

exec startxfce4

Upon further inspection... The file in my home directory is named .xintric instead of what I thought was normal (".xinitrc"). Im going to see if changing it will fix anything

Edit: Changing the filename to .xinitrc did not help anything

Last edited by nostro2 (2017-01-06 04:30:22)

ToZ

Administrator

From: Canada

Registered: 2011-06-02

Posts: 11,492

Re: Xfce not initializing properly from startup

As a test, I installed xdm on my arch system, created an ~/.xinitrc file with "exec startxfce4" and it worked fine.

Can you try a few other tests:

1. Clear the saved sessions via Settings Manager > Session and Startup > Session > "Clear saved sessions" and logout. Make sure that during logout you don't choose the option to save the session and that Settings Manager >Session and Startup > General > "Automatically save session on logout" is unchecked. Upon login, check your ~/.xsession-errors log file again.

2. Disable xdm and try to login directly from the console using "startxfce4"

3. Create a new user account and login with that account with xdm enabled to rule out whether its a profile issue.

Also, there are a couple of other log files you can look at that might provide some more information (/var/log/xdm.log and "journalctl -u xdm").

One final confirmation: are you using Xfce from the official Arch repositories (not custom built or AUR packages)?

---

Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

nostro2

Member

Registered: 2017-01-02

Posts: 5

Re: Xfce not initializing properly from startup

1. Clear the saved sessions via Settings Manager > Session and Startup > Session > "Clear saved sessions" and logout. Make sure that during logout you don't choose the option to save the session and that Settings Manager >Session and Startup > General > "Automatically save session on logout" is unchecked. Upon login, check your ~/.xsession-errors log file again.

This worked for me so i didnt bother with the other options.
Thanks a lot! This is the second time you've helped me in the week.

dtd

Member

Registered: 2011-12-08

Posts: 74

Re: Xfce not initializing properly from startup

Thank you. Clearing ~/.cache/sessions seems to be OS independent BTW. I use FreeBSD and learing cached sessions also worked for me on a system where xdm was into permanent failure mode. I have had this problem for years having the same software install work on some PCs/laptop and on others xdm would work  sporadically or not at all.