New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lost tap to click - samsung arm, xfce, precise, chromium #735

Closed
tedm opened this Issue Apr 2, 2014 · 21 comments

Comments

Projects
None yet
8 participants
@tedm
Contributor

tedm commented Apr 2, 2014

Yesterday, after installing the -t extension, to my precise / xfce chroot, I lost tap to click.

Tried to enable it in Application/settings/touchpad, could not get tap to click working, mouse is fine, and hard pressing the touchpad works as a click.

Today, deleted chroot, downloaded latest crouton, ran:

sudo sh -e ~/Downloads/crouton -t xfce, chromium

installation went fine, typed username and password, then startxfce4

default xfce desktop came up, but no tap to click. Went to settings touchpad, and tried all options.

Console gives this:

(xfce4-appearance-settings:28354): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
running 'ssh-agent -s -k'
/etc/xdg/xfce4/xinitrc: 1: eval: ssh-agent: not found
Running exit commands...
/usr/bin/xinit: connection to X server lost

waiting for X server to shut down xscreensaver: 15:57:11: SIGHUP received: restarting...
xscreensaver: 15:57:11: running as ted/ted (1000/1000)

xscreensaver: 15:57:12: Can't open display: :1
xscreensaver: 15:57:12: running as ted/ted (1000/1000)

xscreensaver: 15:57:12: Errors at startup are usually authorization problems.
But you're not logging in as root (good!) so something
else must be wrong. Did you read the manual and the FAQ?

          http://www.jwz.org/xscreensaver/faq.html
          http://www.jwz.org/xscreensaver/man.html

Unmounting /usr/local/chroots/precise...
Sending SIGTERM to processes under /usr/local/chroots/precise...
chronos@localhost ~ $

@tedm

This comment has been minimized.

Show comment
Hide comment
@tedm

tedm Apr 2, 2014

Contributor

I realize that most or all of these warnings are fine, but note the one about the type error for '/general/double_click_distance' below looks new:

(polkit-gnome-authentication-agent-1:28185): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

(xfce4-settings-helper:28195): GLib-CRITICAL **: g_str_has_prefix: assertion `prefix != NULL' failed

(xfwm4:28170): xfwm4-WARNING **: The property '/general/double_click_distance' of type int is not supported

(xfce4-settings-helper:28195): xfce4-settings-helper-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property.

Contributor

tedm commented Apr 2, 2014

I realize that most or all of these warnings are fine, but note the one about the type error for '/general/double_click_distance' below looks new:

(polkit-gnome-authentication-agent-1:28185): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

(xfce4-settings-helper:28195): GLib-CRITICAL **: g_str_has_prefix: assertion `prefix != NULL' failed

(xfwm4:28170): xfwm4-WARNING **: The property '/general/double_click_distance' of type int is not supported

(xfce4-settings-helper:28195): xfce4-settings-helper-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property.

@tedm

This comment has been minimized.

Show comment
Hide comment
@tedm

tedm Apr 5, 2014

Contributor

Is it possible that the latest crouton is not the latest? I did get one instance of xfce working with an old sleep 5 / startxfce4 / move to window and I'm getting different versions of crouton with croutonversion in chromeos / shell than when in the chroot

This is the samsung arm, not an HP haswell, x86, etc.

Contributor

tedm commented Apr 5, 2014

Is it possible that the latest crouton is not the latest? I did get one instance of xfce working with an old sleep 5 / startxfce4 / move to window and I'm getting different versions of crouton with croutonversion in chromeos / shell than when in the chroot

This is the samsung arm, not an HP haswell, x86, etc.

@tedm

This comment has been minimized.

Show comment
Hide comment
@tedm

tedm Apr 5, 2014

Contributor

here's another odd thing in the console:

/usr/bin/xinit: XFree86_VT property unexpectedly has 0 items instead of 1
/etc/xdg/xfce4/xinitrc: 1: /etc/xdg/xfce4/xinitrc: ssh-agent: not found

Contributor

tedm commented Apr 5, 2014

here's another odd thing in the console:

/usr/bin/xinit: XFree86_VT property unexpectedly has 0 items instead of 1
/etc/xdg/xfce4/xinitrc: 1: /etc/xdg/xfce4/xinitrc: ssh-agent: not found

@benzipperer

This comment has been minimized.

Show comment
Hide comment
@benzipperer

benzipperer Apr 6, 2014

I came across this problem too this evening with a new install of crouton on an accidentally (ugh) powerwashed ARM chromebook. Tap to click returns for me after switching back and forth between XFCE and Chrome OS with Ctrl+Alt+Shift+Back and Ctrl+Alt+Shift+Forward. What about you?

Tap to click does not work any more upon a first entrance to XFCE.

benzipperer commented Apr 6, 2014

I came across this problem too this evening with a new install of crouton on an accidentally (ugh) powerwashed ARM chromebook. Tap to click returns for me after switching back and forth between XFCE and Chrome OS with Ctrl+Alt+Shift+Back and Ctrl+Alt+Shift+Forward. What about you?

Tap to click does not work any more upon a first entrance to XFCE.

@benzipperer

This comment has been minimized.

Show comment
Hide comment
@benzipperer

benzipperer Apr 6, 2014

Also, another minor thing I noticed: tap to click in Chrome OS was disabled during the middle of installing precise (-t xfce). Rebooting my Chromebook solved this problem.

benzipperer commented Apr 6, 2014

Also, another minor thing I noticed: tap to click in Chrome OS was disabled during the middle of installing precise (-t xfce). Rebooting my Chromebook solved this problem.

@tedm

This comment has been minimized.

Show comment
Hide comment
@tedm

tedm Apr 6, 2014

Contributor

@benzipperer yes, switching back to ChromeOS, then back to xfce does enable tap to click. I hope this helps the developers. I haven't noticed the disabling during install, but often I'm reading in another browser or away from the chromebook when it is installing so haven't noticed that. I hope your info. plus the console output, and the fact that the sleep 5 trick from previous crouton's provides the developers with what they need to get tap to click working like it used to.

(xfwm4:6571): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(xfdesktop:6577): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(xfwm4:6571): GLib-CRITICAL **: g_str_has_prefix: assertion `prefix != NULL' failed

(xfce4-settings-helper:6596): GLib-CRITICAL **: g_str_has_prefix: assertion `prefix != NULL' failed
xfce4-settings-helper: Another instance is already running. Leaving...

(polkit-gnome-authentication-agent-1:6588): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed

(polkit-gnome-authentication-agent-1:6588): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

(migrate:6595): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(xfce4-settings-helper:6596): xfce4-settings-helper-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property.

(xfwm4:6571): xfwm4-WARNING **: The property '/general/double_click_distance' of type int is not supported

(xfce4-panel:6573): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(wrapper:6734): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(Thunar:6575): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

Contributor

tedm commented Apr 6, 2014

@benzipperer yes, switching back to ChromeOS, then back to xfce does enable tap to click. I hope this helps the developers. I haven't noticed the disabling during install, but often I'm reading in another browser or away from the chromebook when it is installing so haven't noticed that. I hope your info. plus the console output, and the fact that the sleep 5 trick from previous crouton's provides the developers with what they need to get tap to click working like it used to.

(xfwm4:6571): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(xfdesktop:6577): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(xfwm4:6571): GLib-CRITICAL **: g_str_has_prefix: assertion `prefix != NULL' failed

(xfce4-settings-helper:6596): GLib-CRITICAL **: g_str_has_prefix: assertion `prefix != NULL' failed
xfce4-settings-helper: Another instance is already running. Leaving...

(polkit-gnome-authentication-agent-1:6588): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed

(polkit-gnome-authentication-agent-1:6588): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

(migrate:6595): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(xfce4-settings-helper:6596): xfce4-settings-helper-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property.

(xfwm4:6571): xfwm4-WARNING **: The property '/general/double_click_distance' of type int is not supported

(xfce4-panel:6573): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(wrapper:6734): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(Thunar:6575): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

@tedm

This comment has been minimized.

Show comment
Hide comment
@tedm

tedm Apr 10, 2014

Contributor

with new crouton:

chronos@localhost / $ croutonversion
crouton: version 1-20140301024303~master:06549cb2
release: precise
architecture: armhf
host: version unknown
chronos@localhost / $

tap to click after entering chroot with chrosh / shell / sudostartxfce4 still doesn't enable tap to click, but after crtl-alt-shift-Rarrow, then crtl-alt-shift-Larrow it is enabled fine.

Other window issues on ARM seem present. For example, entering the chroot with enter-chroot and typing startx leaves a black screen, but arrow is active. Must powercycle to get screen back.

Note fatal i/o error 11 below, after exiting xfce:


(polkit-gnome-authentication-agent-1:12420): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed

(polkit-gnome-authentication-agent-1:12420): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
running 'ssh-agent -s -k'
/etc/xdg/xfce4/xinitrc: 1: eval: ssh-agent: not found
Running exit commands...
/usr/bin/xinit: connection to X server lost

waiting for X server to shut down xscreensaver: 09:04:14: SIGHUP received: restarting...
xscreensaver: 09:04:14: running as ted/ted (1000/1000)

xfce4-settings-helper: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
xscreensaver: 09:04:14: Can't open display: :1
xscreensaver: 09:04:14: running as ted/ted (1000/1000)

xscreensaver: 09:04:14: Errors at startup are usually authorization problems.
But you're not logging in as root (good!) so something
else must be wrong. Did you read the manual and the FAQ?

          http://www.jwz.org/xscreensaver/faq.html
          http://www.jwz.org/xscreensaver/man.html

Unmounting /usr/local/chroots/precise...
Sending SIGTERM to processes under /usr/local/chroots/precise...
chronos@localhost / $

Contributor

tedm commented Apr 10, 2014

with new crouton:

chronos@localhost / $ croutonversion
crouton: version 1-20140301024303~master:06549cb2
release: precise
architecture: armhf
host: version unknown
chronos@localhost / $

tap to click after entering chroot with chrosh / shell / sudostartxfce4 still doesn't enable tap to click, but after crtl-alt-shift-Rarrow, then crtl-alt-shift-Larrow it is enabled fine.

Other window issues on ARM seem present. For example, entering the chroot with enter-chroot and typing startx leaves a black screen, but arrow is active. Must powercycle to get screen back.

Note fatal i/o error 11 below, after exiting xfce:


(polkit-gnome-authentication-agent-1:12420): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed

(polkit-gnome-authentication-agent-1:12420): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
running 'ssh-agent -s -k'
/etc/xdg/xfce4/xinitrc: 1: eval: ssh-agent: not found
Running exit commands...
/usr/bin/xinit: connection to X server lost

waiting for X server to shut down xscreensaver: 09:04:14: SIGHUP received: restarting...
xscreensaver: 09:04:14: running as ted/ted (1000/1000)

xfce4-settings-helper: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
xscreensaver: 09:04:14: Can't open display: :1
xscreensaver: 09:04:14: running as ted/ted (1000/1000)

xscreensaver: 09:04:14: Errors at startup are usually authorization problems.
But you're not logging in as root (good!) so something
else must be wrong. Did you read the manual and the FAQ?

          http://www.jwz.org/xscreensaver/faq.html
          http://www.jwz.org/xscreensaver/man.html

Unmounting /usr/local/chroots/precise...
Sending SIGTERM to processes under /usr/local/chroots/precise...
chronos@localhost / $

@tedm

This comment has been minimized.

Show comment
Hide comment
@tedm

tedm Apr 10, 2014

Contributor

Some of those errors appear to be related to xscreensaver.

After an apt-get --purge remove xscreensaver, exiting xfce appears to exit cleanly in the console:

Running exit commands...
/usr/bin/xinit: connection to X server lost

waiting for X server to shut down
Unmounting /usr/local/chroots/precise...
Sending SIGTERM to processes under /usr/local/chroots/precise...
chronos@localhost / $

Contributor

tedm commented Apr 10, 2014

Some of those errors appear to be related to xscreensaver.

After an apt-get --purge remove xscreensaver, exiting xfce appears to exit cleanly in the console:

Running exit commands...
/usr/bin/xinit: connection to X server lost

waiting for X server to shut down
Unmounting /usr/local/chroots/precise...
Sending SIGTERM to processes under /usr/local/chroots/precise...
chronos@localhost / $

@nlaney

This comment has been minimized.

Show comment
Hide comment
@nlaney

nlaney Apr 10, 2014

This is the same issue as #38 and which @benzipperer reported. Here's my >croutonversion output:

crouton: version 1-20140405011141~master:bb11badb
release: precise
architecture: armhf
targets: xfce
host: version 5500.100.0 (Official Build) stable-channel daisy

nlaney commented Apr 10, 2014

This is the same issue as #38 and which @benzipperer reported. Here's my >croutonversion output:

crouton: version 1-20140405011141~master:bb11badb
release: precise
architecture: armhf
targets: xfce
host: version 5500.100.0 (Official Build) stable-channel daisy

@tedm

This comment has been minimized.

Show comment
Hide comment
@tedm

tedm Apr 10, 2014

Contributor

@nlaney I understand that the symptoms are the same, but it was resolved for almost a year until recently, so I am thinking that something new in crouton, perhaps recent changes in window management behavior may be the cause of it.

@dnschneid Let me know which one to leave open / reopen / close. We only need one open. It seems like we should be able to revert code until it works again, or am I missing something here?

Contributor

tedm commented Apr 10, 2014

@nlaney I understand that the symptoms are the same, but it was resolved for almost a year until recently, so I am thinking that something new in crouton, perhaps recent changes in window management behavior may be the cause of it.

@dnschneid Let me know which one to leave open / reopen / close. We only need one open. It seems like we should be able to revert code until it works again, or am I missing something here?

@drinkcat

This comment has been minimized.

Show comment
Hide comment
@drinkcat

drinkcat Apr 13, 2014

Collaborator

I can confirm this issue: tap to click only works after a switch to Chrome OS and back. I was hoping #750 would fix this issue as well, but it doesn't. I also tried commenting out if (rotate > 0) in wmtools.c to force the window to be remapped: without success.

host: version 5712.14.0 (Official Build) dev-channel daisy

Will keep digging...

Collaborator

drinkcat commented Apr 13, 2014

I can confirm this issue: tap to click only works after a switch to Chrome OS and back. I was hoping #750 would fix this issue as well, but it doesn't. I also tried commenting out if (rotate > 0) in wmtools.c to force the window to be remapped: without success.

host: version 5712.14.0 (Official Build) dev-channel daisy

Will keep digging...

@tedm

This comment has been minimized.

Show comment
Hide comment
@tedm

tedm Apr 13, 2014

Contributor

@drinkcat let me know if there is any testing I can help you with here. I tried starting, stopping and restarting various processes trying to get a new script in /etc/rc.local but nothing working yet. Thanks.

tap to click with new crouton / xfce precise chroots was working in early March, so something fairly recent may have done something.

Contributor

tedm commented Apr 13, 2014

@drinkcat let me know if there is any testing I can help you with here. I tried starting, stopping and restarting various processes trying to get a new script in /etc/rc.local but nothing working yet. Thanks.

tap to click with new crouton / xfce precise chroots was working in early March, so something fairly recent may have done something.

@dnschneid dnschneid added the bug label Apr 14, 2014

@tedm

This comment has been minimized.

Show comment
Hide comment
@tedm

tedm Apr 21, 2014

Contributor

I deleted and re-installed a precise/xfce chroot on the ARM today and noticed something - after install, and then typing sudo startxfce4 for the first time, the mouse pointer seems to shake a bit on its own with no keys or touchpad input, just before xfce comes up, and tap to click worked on the first instance.

Exiting and restarting, it doesn't, but ctrl-shift-alt-f2 and crtl-shift-alt-f1 still re-enables it.

Contributor

tedm commented Apr 21, 2014

I deleted and re-installed a precise/xfce chroot on the ARM today and noticed something - after install, and then typing sudo startxfce4 for the first time, the mouse pointer seems to shake a bit on its own with no keys or touchpad input, just before xfce comes up, and tap to click worked on the first instance.

Exiting and restarting, it doesn't, but ctrl-shift-alt-f2 and crtl-shift-alt-f1 still re-enables it.

@benzipperer

This comment has been minimized.

Show comment
Hide comment
@benzipperer

benzipperer May 1, 2014

I'm not sure if this is helpful but I have noticed that I lose tap-to-click in XFCE after my screen locks in Chrome OS, when the machine is idle. Switching to Chrome OS and back does not solve the problem, but logging back into Chrome OS solves the problem. Not sure how long this has been occurring.

benzipperer commented May 1, 2014

I'm not sure if this is helpful but I have noticed that I lose tap-to-click in XFCE after my screen locks in Chrome OS, when the machine is idle. Switching to Chrome OS and back does not solve the problem, but logging back into Chrome OS solves the problem. Not sure how long this has been occurring.

@orendon

This comment has been minimized.

Show comment
Hide comment
@orendon

orendon May 9, 2014

I can confirm this issue is also present on Ubuntu Trusty (xfce) I lost both tap and double tap-to-click

I'm using the latest crouton on a Toshiba Chromebook

crouton: version 1-20140421214646~master:b766b319
release: trusty
architecture: amd64
targets: xfce
host: version 5500.130.0 (Official Build) stable-channel leon

orendon commented May 9, 2014

I can confirm this issue is also present on Ubuntu Trusty (xfce) I lost both tap and double tap-to-click

I'm using the latest crouton on a Toshiba Chromebook

crouton: version 1-20140421214646~master:b766b319
release: trusty
architecture: amd64
targets: xfce
host: version 5500.130.0 (Official Build) stable-channel leon
@peter-gulka

This comment has been minimized.

Show comment
Hide comment
@peter-gulka

peter-gulka Jun 15, 2014

Confirmed on Acer C710-2457 (Intel). It happened during the initial install of a new chroot w/ Trusty 14.04 and Unity. The install process is still running but tap-to-click disappeared.

peter-gulka commented Jun 15, 2014

Confirmed on Acer C710-2457 (Intel). It happened during the initial install of a new chroot w/ Trusty 14.04 and Unity. The install process is still running but tap-to-click disappeared.

@reeved

This comment has been minimized.

Show comment
Hide comment
@reeved

reeved Jun 21, 2014

same here. i cant tap to click in ChromeOS with my c720.
I have XFCE 14.04 installed

reeved commented Jun 21, 2014

same here. i cant tap to click in ChromeOS with my c720.
I have XFCE 14.04 installed

@nlaney

This comment has been minimized.

Show comment
Hide comment
@nlaney

nlaney Jul 29, 2014

works great!

/usr/local/bin/croutonversion
crouton: version 1-20140727124603~master:eb4b89cc
release: precise
architecture: armhf
targets: xfce
host: version 5841.73.0 (Official Build) stable-channel daisy

nlaney commented Jul 29, 2014

works great!

/usr/local/bin/croutonversion
crouton: version 1-20140727124603~master:eb4b89cc
release: precise
architecture: armhf
targets: xfce
host: version 5841.73.0 (Official Build) stable-channel daisy

@tedm

This comment has been minimized.

Show comment
Hide comment
@tedm

tedm Jul 29, 2014

Contributor

yes, it does! Thanks David and all for bringing this functionality back.

Contributor

tedm commented Jul 29, 2014

yes, it does! Thanks David and all for bringing this functionality back.

@dnschneid

This comment has been minimized.

Show comment
Hide comment
@dnschneid

dnschneid Jul 29, 2014

Owner

That was all @drinkcat...thank him :)

Owner

dnschneid commented Jul 29, 2014

That was all @drinkcat...thank him :)

@tedm

This comment has been minimized.

Show comment
Hide comment
@tedm

tedm Jul 29, 2014

Contributor

Thanks @drinkcat tap to click is working great, and from the get-go with precise / xfce on the ARM!

Contributor

tedm commented Jul 29, 2014

Thanks @drinkcat tap to click is working great, and from the get-go with precise / xfce on the ARM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment