You are not logged in.
I just updated to Gnome 3.16, and while I do enjoy some of the improvements, others I find a bit unfortunate.
First, I found a bug: I use a touchscreen, and touchpad, and for some reason chrome is having issues with that (look here for more info: https://code.google.com/p/chromium/issu … id=475410).
So part of my boot up routine was to disable the touchpad, start chrome, and then enable the touchpad.
This time, right after I disabled the touchpad, the option to enable it again was gone, and it had me looking for how to enable it again. The touchpad was still working, and detected, because if I logged out, it would work, it was just the setting. I found that I could enable it again with the following command:
gsettings set org.gnome.desktop.peripherals.touchpad send-events 'enabled'
But had no GUI way of doing it.
Is this a legitimate bug (that is, can people reproduce it), or is it my specific configuration?
As a note, I created a new user to test, and had the same issue.
Where would I go to submit a bug for gnome?
Offline
Could it be related to https://plus.google.com/u/0/+MaxWachtel … zr7j6Sy6GS, i.e. see if installing xf86-input-libinput fixes it?
Offline
So, I was hopeful that would fix it, but instead it made my computer completely non-functional
I had to uninstall if through a live CD. It just crashed in the login service.
Any suggestions on how I could debug this?
Offline
faced that bug today after updating to gnome 3.16!!!!
Last edited by Риал Краесис (2015-04-11 19:11:34)
Offline
Having a similar issue even after today's updates... on my Dell Latitude E5530, If I try to disable the touchpad using the keyboard shortcut, nothing happens on the first press. On the second, gnome crashes and prompts for a re-login.
Offline
Installing libinput seems to remove the crashing on my laptop. But the Fn-F8 Touchpad toggle is now nonfunctional.
Offline
The problem was with mutter; version 3.16.1.1, already in the repos, should fix the crasher. (See https://projects.archlinux.org/svntogit … ges/mutter for the bug history).
Last edited by vorbote (2015-04-15 14:27:59)
I break things and put them back together for fun and sometimes profit, because it is the only way to learn.
Offline
The problem was with mutter; version 3.16.1.1, already in the repos, should fix the crasher. (See https://projects.archlinux.org/svntogit … ges/mutter for the bug history).
still not fixed, i press fn + f9 two times and gnome shell crashes
Offline
still not fixed, i press fn + f9 two times and gnome shell crashes
Do you have the gpointing-device-settings package installed?
Last edited by Dowefu (2015-04-15 16:17:32)
Offline
Still broke over here, and installing/uninstalling gpointing-device-settings makes no difference. libinput was already installed; I'll re-install to see if it happens to fix anything
PS- FWIW, on my Dell, it's FN+F5. Not sure on the actual keycode (not listed in keyboard shortcuts, as far as I could tell by skimming).
edit- it comes up as "touchpad toggle"; I tried re-assigning it to a "test" custom shortcut, which did not work, as pressing it once changed the text on screen of the settings (after setting the new assignment, which didn't prompt an assignment conflict warning), the second press, as before, crashed gnome. I'll take some screenshots to illustrate.
Last edited by ratdude747 (2015-04-15 17:12:39)
Offline
I fixed it logging out, choosing Gnome on Wayland as session and enabling touchpad in mouse settings as you normally would.
Offline
I fixed it logging out, choosing Gnome on Wayland as session and enabling touchpad in mouse settings as you normally would.
Are you required to choose Wayland every time you log in? Or is there a better way to debug/fix this?
Wit beyond measure is man's greatest treasure!
Windows Phone app for Linux!
Offline