Discussion:
[Ltsp-discuss] Chromium 39 logs out thin client
Michael Pope
2015-01-13 06:27:40 UTC
Permalink
I'm using a fresh install of Debian testing on my server and have
install chromium and the latest firefox. I can boot a thin client in and
happily run firefox, but if I start chromium the thin client logs out
straight away. The thin client in question is a notebook. I have tried
to login as different users and they all have the same issue.

If I setup a thin client in VirtualBox however it doesn't logout and I
can use chromium in that thin client fine.

Where can I find log files for this kind of problem?

from
Michael

------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
John Hupp
2015-01-13 14:30:34 UTC
Permalink
Post by Michael Pope
I'm using a fresh install of Debian testing on my server and have
install chromium and the latest firefox. I can boot a thin client in and
happily run firefox, but if I start chromium the thin client logs out
straight away. The thin client in question is a notebook. I have tried
to login as different users and they all have the same issue.
If I setup a thin client in VirtualBox however it doesn't logout and I
can use chromium in that thin client fine.
Where can I find log files for this kind of problem?
from
Michael
I think I would begin by just trying to start chromium from an xterm
window with output captured to a file. Perhaps it will capture
something before the log-off.


------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Vagrant Cascadian
2015-01-13 17:37:52 UTC
Permalink
Post by Michael Pope
I'm using a fresh install of Debian testing on my server and have
install chromium and the latest firefox. I can boot a thin client in and
happily run firefox, but if I start chromium the thin client logs out
straight away. The thin client in question is a notebook. I have tried
to login as different users and they all have the same issue.
If I setup a thin client in VirtualBox however it doesn't logout and I
can use chromium in that thin client fine.
Are you using a thin client with LDM_DIRECTX=true ? I'm wondering if
you're experiencing an issue with the LIBGL_ALWAYS_INDIRECT variable
being set as described in this bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767764#31
Post by Michael Pope
Where can I find log files for this kind of problem?
In the user's ~/.xsession-errors file. What video hardware is in the
notebook?


live well,
vagrant
Michael Pope
2015-01-14 07:49:02 UTC
Permalink
Post by Vagrant Cascadian
Post by Michael Pope
I'm using a fresh install of Debian testing on my server and have
install chromium and the latest firefox. I can boot a thin client in and
happily run firefox, but if I start chromium the thin client logs out
straight away. The thin client in question is a notebook. I have tried
to login as different users and they all have the same issue.
If I setup a thin client in VirtualBox however it doesn't logout and I
can use chromium in that thin client fine.
Are you using a thin client with LDM_DIRECTX=true ? I'm wondering if
you're experiencing an issue with the LIBGL_ALWAYS_INDIRECT variable
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767764#31
I've now tried with LDM_DIRECTX=true & LDM_DIRECTX=false, in both
situations it logs me out.
Post by Vagrant Cascadian
Post by Michael Pope
Where can I find log files for this kind of problem?
In the user's ~/.xsession-errors file. What video hardware is in the
notebook?
The notebook in question is a Lenovo E420 with Intel HD 3000 Graphics.
My notebook is a Sony Viao S13P w/Intel + Nvidia optimus graphics (also
shows the same problem when PXE booted off).

Here is the result from the users .xsession-errors file when starting
the chromium-browser

(Do:4521): GLib-CRITICAL **: Source ID 65 was not found when attempting
to remove it
xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X
server localhost:11.0.
Thunar: Fatal IO error 11 (Resource temporarily unavailable) on X server
localhost:11.0.
wrapper: Fatal IO error 11 (Resource temporarily unavailable) on X
server localhost:11.0.
xfce4-panel: Fatal IO error 11 (Resource temporarily unavailable) on X
server localhost:11.0.
wrapper: Fatal IO error 11 (Resource temporarily unavailable) on X
server localhost:11.0.
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.
xfwm4: Fatal IO error 11 (Resource temporarily unavailable) on X server
localhost:11.0.
wrapper: Fatal IO error 11 (Resource temporarily unavailable) on X
server localhost:11.0.
kactivitymanagerd: Fatal IO error: client killed
xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X
server localhost:11.0.
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: Fatal IO error 11 (Resource temporarily unavailable) on X
server localhost:11.0.
[4772:4772:0114/184157:ERROR:chrome_browser_main_extra_parts_x11.cc(56)]
X IO error received (X server probably went away)
kdeinit4: Fatal IO error: client killed
kded4: Fatal IO error: client killed
klauncher: Exiting on signal 15
[4806:4806:0114/184157:ERROR:x11_util.cc(81)] X IO error received (X
server probably went away)
dropbox: Fatal IO error 11 (Resource temporarily unavailable) on X
server localhost:11.0.
xprop: unable to open display 'localhost:11.0'

Here is the result of me running chromium on the command line within
screen and logging in again to capture the output.
http://pastebin.com/SK7pCVVL

from
Michael

------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
Loading...