If you can instruct me on how to gather the pertinent information, I can make a report.
Honestly though, it seems like the chances of some unique rare issue that few have is going to get much attention. If it comes to it that I need Wayland on this system, I'd sooner just reinstall which typically resets weird elusive configuration issues of which there could be many. It's too bad there isn't a financially backed bounty system somewhere for fixing bugs? I might pay into some reward to fix these odd issues that aren't likely to get much attention. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1730174 Title: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrading from 17.04 to 17.10, I encounter strange mouse issues, namely : - The mouse cursor moves allright - But mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop, they are also ignored in all the Gnome panel and lef side dock. However, once started using keyboard, mouse DOES work INSIDE applications allright (all the times), and SOME windows can be moved by dragging their title bar when focus is given to them (i.e. I currently have a gedit window that I can move around with the mouse, while I cannot move a gnome-terminal or the firefox in which I type this text). Also, a directory/file selection dialog for the "save" action in gedit works perfectly well with the mouse. This is definitely not a hardware mouse issue. But I cannot change focus with the mouse, I have to [Alt]-[Tab] to change window. Also if I shift focus to the desktop, I can interact with icons on the desktop and the right-click on the background *may* work. I've purged all the .something config dirs in my homedir to no avail (and I don't believe it relates to it because gdm shows this behaviour even before I actually login). I've seen the exact same problem (after upgrade from 17.04 to 17.10) being reported on miscellaneous forums by at least 3 other people. So I'm not alone, but I have no clue. Trying to investigate this I checked a big part of my system's configuration and fell upon im-config. I have noticed that, when completely uninstalled (all the files that it refers to being removed), then reinstalled, this package actually FAILS installing any of its configuration files (but without any error message), resulting in the following situation : root@totor:~# dpkg -r --force depends im-config dpkg: im-config : problème de dépendance, mais suppression comme demandé : language-selector-gnome dépend de im-config (>= 0.29-1ubuntu10~). (Lecture de la base de données... 387605 fichiers et répertoires déjà installés.) Suppression de im-config (0.32-1ubuntu3) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... root@totor:~# apt-get install im-config Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les NOUVEAUX paquets suivants seront installés : im-config 0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour. Il est nécessaire de prendre 0 o/24,5 ko dans les archives. Après cette opération, 365 ko d'espace disque supplémentaires seront utilisés. Sélection du paquet im-config précédemment désélectionné. (Lecture de la base de données... 387551 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../im-config_0.32-1ubuntu3_all.deb ... Dépaquetage de im-config (0.32-1ubuntu3) ... Paramétrage de im-config (0.32-1ubuntu3) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... root@totor:~# dpkg -V im-config ??5?????? c /etc/X11/Xsession.d/70im-config_launch ??5?????? c /etc/X11/xinit/xinputrc ??5?????? c /etc/default/im-config ??5?????? c /etc/profile.d/input-method-config.sh Any help greatly appreciated, my desktop being currently quite unusable. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: im-config 0.32-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 09:42:24 2017 EcryptfsInUse: Yes JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. PackageArchitecture: all SourcePackage: im-config UpgradeStatus: Upgraded to artful on 2017-10-21 (14 days ago) modified.conffile..etc.X11.Xsession.d.70im-config_launch: [deleted] modified.conffile..etc.X11.xinit.xinputrc: [deleted] modified.conffile..etc.default.im-config: [deleted] modified.conffile..etc.profile.d.input-method-config.sh: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
