Seeing this same issue in 18.04 since a recent update. The dumpkeys fix
appears to resolve for now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through t
I've just experienced this problem again.
The following packages were just updated (from /var/log/apt/history.log):
Start-Date: 2018-07-31 09:48:46
Commandline: aptdaemon role='role-commit-packages' sender=':1.2928'
Upgrade: intel-microcode:amd64 (3.20180425.1~ubuntu0.18.04.1,
3.20180425.1~ubunt
I have this bug on 18.04 with alt+left.
After executing the dumpkeys/loadkeys workaround, then alt+left stops
doing strange things but now, alt+F4 drops me to console 4 which is even
worse.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Extended the workaround to read
dumpkeys |grep -v cr_Console | grep -v -E '^\s+alt\s+keycode.*Console_'
|loadkeys
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input
+1 - any workaround?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates the session on Ctrl+C after
udevadm trigger is executed
+1 for the dumpkeys/loadkeys workaround. Saves me from killing the
current session; so thanks for that.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls throu
I hadn't seen this for a while and it happened again today. The
dumpkeys/loadkeys workaround fixed it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls throug
Same here. I am experiencing the issue in 18.04 (alt+arrow keys)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates the session o
I can also confirm this bug is still very much present (and an annoying
feature) in 18.04, under Xorg. Ctrl+C works as expected though.
Alt+[Arrow keys] switches VTs.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
http
Bug 1767918 indicates this bug is not fixed, and still occurring in
18.04.
** Tags added: fall-through
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls thro
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates the session on Ctrl
I'm experiencing the same thing on Ubuntu Xenial. I initially thought it
was only on using Alt+left/right, but did a Alt+F4 to close a window
just now, and the window did close but it switched to VT4 as well. I
think it started happening today on my system.
Linux 4.4.0-116-generic #140-Ubuntu SMP
I'm experiencing this problem since months, the only "one time" fix when
it occurs I found is :
sudo sh -c 'dumpkeys |grep -v cr_Console |loadkeys'
Until the next reboot...
But it's better than nothing, right?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs
Ok, I'm opening the tasks for Xenial and Trusty, and we can decide
exactly where it makes sense to do the SRU for these changes.
Plus, I understand maybe it was still reproducible in some form on
bionic, so it this should be revisited in general.
** Also affects: console-setup (Ubuntu Xenial)
Would be great to get this fixed in 16.04 also guys
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates the session on Ctrl+C afte
can this be fixed also for 16.04?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates the session on Ctrl+C after
udevadm trigge
It continues... bug 1726608
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates the session on Ctrl+C after
udevadm trigger is e
The forum thread is enough IMO for this improvement (as opposed to bug
fix) and it is in trello.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to g
On Tue, Sep 19, 2017 at 04:16:24PM -, Jamie Strandboge wrote:
> Closing the snappy task-- while we might want to adjust its use of
> udevadm trigger, it is clear that running this command should not break
> the wayland desktop, just like it doesn't under X.
I think this should still be tracked
I still have console-setup 1.166ubuntu4 so decided to poke at this more.
I can confirm that 'sudo udevadm trigger' causes the ctrl+c to logout of
Wayland. It does not cause a logout of gnome-shell under X. I then found
that 'udevadm trigger --subsystem-nomatch=tty' does not cause the issue
under wa
Closing the snappy task-- while we might want to adjust its use of
udevadm trigger, it is clear that running this command should not break
the wayland desktop, just like it doesn't under X.
** Changed in: snappy
Status: New => Opinion
** Changed in: snappy
Status: Opinion => Won't F
@Mathieu, while I understand the wayland gnome-shell desktop session is
not supported on zesty or xenial, I wonder if this should be SRU'd to
those releases?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.
I just now upgraded to 1.166ubuntu5 and no longer see the issue. To
ogra's point, I use encrypted lvm and was able to enter a password and
have everything work like normal.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu
please note that this rule will also likely be used inside the initrd to
set up the console for encyption key input and there will be no systemd
around ... you probably want to rather handle it conditionally so it is
still available when creating an initrd ...
--
You received this bug notificatio
This bug was fixed in the package console-setup - 1.166ubuntu5
---
console-setup (1.166ubuntu5) artful; urgency=medium
* Don't use console-setup-tty or its udev rule. This dates back to lucid and
now systemd is apparently able to handle this correctly. It's now actively
brea
Indeed, it looks like systemd is handling this properly by itself. I'll
do some more testing but it looks like removing that is probably the
best thing to do. At least font/keymaps are set properly.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is su
Not sure why you would if systemd is setting the mode up correctly on
its own?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates
might be that we need it on Ubuntu Core (and server) though ... so
installing the rule at all should probably be conditional ...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
T
^- forgot to say, that was with those udev rules commented out - you
could equally (upstreamable - this bug should apply to Debian too) do
something like
if [ -d /run/systemd/system ]; then
exit 0
fi
at the top of console-setup-tty
--
You received this bug notification because you are a membe
...or stop using this rule completely? I think systemd does thing
properly these days - see:
laney@artful-vm-gdm:~$ sudo ~/temp/a.out # displaying gdm
[sudo] password for laney:
K_OFF
laney@artful-vm-gdm:~$ sudo ~/temp/a.out # switch to vt3, login: prompt
K_UNICODE
...which looks set up correctl
I have this problem on Ubuntu Gnome 17.04 running in virtualbox. I
believe it is not using Wayland.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through t
Indeed changing it to [3-7] fixes it. Or should that be [3-6]?
cyphermox?
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
** Changed in: mutter (Ubuntu)
Status: Incomplete => Invalid
** Changed in:
^- this thing is the thing that breaks it
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates the session on Ctrl+C after
udevad
/lib/udev/rules.d/85-keyboard-configuration.rules:SUBSYSTEM=="tty",
KERNEL=="tty[1-6]", RUN+="console-setup-tty /dev/%k"
/lib/udev/rules.d/85-keyboard-configuration.rules:SUBSYSTEM=="graphics",
KERNEL=="fbcon", RUN+="console-setup-tty fbcon"
--
You received this bug notification because you are
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates
** Summary changed:
- Input falls through to gdm3 and terminates the session on Ctrl+C
+ Input falls through to gdm3 and terminates the session on Ctrl+C after
udevadm trigger is executed under wayland
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Actually point 2 is not exactly true:
- udevadm control --reload-rules does not trigger the bug
- udevadm trigger reproduces the bug.
** Description changed:
+ = Test Cases =
+
+ Test Case 1:
+ - Login under Wayland (session Ubuntu)
+ - Open a terminal
+ - snap install gimp
+ - Wait until instal
- it seems that only snapd using the opengl interface are triggering this issue.
- "udevadm control --reload-rules" or "udevadm trigger" do not trigger the bug
- It only happens under wayland. Installing or removing the same snaps under
Xorg do not trigger the bug.
--
You received this bug notif
strace from snapd when gimp is removed.
** Attachment added: "snapd.strace"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1710637/+attachment/4952143/+files/snapd.strace
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 i
I can reproduce this bug by running in a terminal:
snap install gimp
but not with:
snap install hello
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls throug
snap remove gimp also triggers this bug
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates the session on Ctrl+C
To manage notif
Running "snap remove libreoffice" triggered a state change for me from
K_OFF to K_UNICODE. And sure enough, the next Ctrl+C logged me out.
** Also affects: snappy
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
Note I was seeing this in zesty for a while (then didn't):
https://bugzilla.gnome.org/show_bug.cgi?id=772476
** Bug watch added: GNOME Bug Tracker #772476
https://bugzilla.gnome.org/show_bug.cgi?id=772476
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
k, here's a program.
If the bug is what I think it is then this should print K_OFF when
everything is good and K_UNICODE when it's bad. You can also run it with
BREAK or FIX to break/fix your system too.
Perhaps if you suffer from this bug you could run this very frequently
so you catch as soon a
** Tags added: rls-aa-incoming
** Changed in: gdm3 (Ubuntu)
Importance: Medium => High
** Changed in: gnome-shell (Ubuntu)
Importance: Medium => High
** Changed in: mutter (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Desk
Sounds like the same issue as bug 1716415 / bug 1508146.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates the session on Ctrl+C
I hadn't experienced that issue until yesterday, but it happened to me 5
or 6 times since then. Always when pressing Ctrl+C while working in
gnome-terminal. I'm in a default Ubuntu session (wayland).
osomon@bribon:~$ LANG=C apt policy gdm3 gnome-shell gnome-terminal console-setup
gdm3:
Installed
Could this be why I sometimes get no keyboard input at all in my user sessions
in Artul...?
(Can type password in GDM, but then all keyboard input is lost until reboot.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
well, if it's the same bug that I got to happen, it was console-setup
running `setupcon --force -k' as part of its installation that made the
input that would usually go to mutter go to the console instead.
console-setup has been fixed now not to call this, but if you have other
things calling setu
(otherwise, of course, it could be something totally different - in that
case, please to reopen this!)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls throug
jibel, I think you saw bug #1712356
Saviq, are/were you running wayland or x?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and ter
I've been affected by this issue this morning, It's it not only CTRL+C
for also ALT+Fn, for example ALT-F4 switched to vt4 instead of closing
the window. I didn't find any way to reproduce it reliably. I'm on x11.
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => Medium
** Changed in: gdm3
That may very well be, note this usually happens when I'm in my session
working normally, and trying to Ctrl+C a command in the terminal. Not
sure if that fits your suspected MO.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-sh
Sounds like this is related to VT switching. GDM is in VT1 and the login
is on VT2.
While I can't reproduce the bug right now, I can kind of see how it could
happen: After switching between a bunch of VTs, eventually VT1 starts showing
two screens when I switch to it by Ctrl+Alt+F1:
(a) For a s
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and terminates
55 matches
Mail list logo
