oligofren's questions

There is a problem for users of IntelliJ on Ubuntu that the Ctrl-Shift-U shortcut is taken. You could use the UI tools, but I like to fix things once by running setup.sh script on my dev machines. That means a scriptable command. One fix is to just uninstall ibus, but if you actually require IBUS that is a bit too rough. So how would I go about disabling a shortcut from the command line?

I assume a config file is written somewhere, which means I should be able to make a copy of that and copy that to some location. But I also see that ibus-setup has a range of commands. Not seeing what to use, though ...

A recurring issue (at least for users that utilize more than one keyboard layout or input source?!), is that Alt+Shift is a sticky setting for changing input source. That means, even if you change Gnome's keyboard settings to something else, like <Super><Space> (a popular choice, it seems), Alt+Shift still sticks! Which not only ruins using Alt+Shift+Tab, but also every other shortcut in all programs using Alt+Shift as modifiers, including IntelliJ (my main work tool). That sucks and is super-confusing.

Today I learned that this is caused by a setting that is stored outside of gnome's keybindings schema (org.gnome.desktop.wm.keybindings has the switch-input-source setting):

gsettings get org.gnome.desktop.input-sources xkb-options
['grp:alt_shift_toggle', 'grp_led:scroll']

Removing this setting "fixes" things (doing gsettings reset org.gnome.desktop.input-sources xkb-options), but why should I ever need to do so? Why can't simply Gnome clear this by default and use its own setting? This is so bad UX and almost seems like a glitch of some kind, but it seems as if it has been there for 4 years now, so in that case it should have been fixed. Is there any good reason for that behaviour?

Related

• https://unix.stackexchange.com/questions/45447/other-than-alt-shift-to-switch-keyboard-layout-any-other-xorg-key-combination
• Ubuntu 18.04 alt+shift+tab does not switch apps backwards

Ubuntu 21.10 distro upgraded from 21.04

This is a bit of a mystery. The hgfs shares all show as read-only, but I have no trouble writing files to them (as I want to). The trouble is that Nautilus refuses to copy files into these folders, as they are marked read-only, even if cp ~/some.file /mnt/hgfs/Downloads poses no problems.

See below for a demo

$ ls -lh /mnt/hgfs/
totalt 304K
dr-xr-xr-x 1 my-user my-user  20K okt.   6 12:35 Dokumenter
dr-xr-xr-x 1 my-user my-user 256K okt.   8 18:02 Downloads
dr-xr-xr-x 1 my-user my-user  28K okt.  12 14:28 Skrivebord

$ echo 123 > /mnt/hgfs/Skrivebord/foo 

$ cat /mnt/hgfs/Skrivebord/foo 
123

$ ls -ld /mnt/hgfs/Skrivebord/
dr-xr-xr-x 1 my-user my-user 28672 okt.  12 14:28 /mnt/hgfs/Skrivebord/

How can I circumvent this so that GUI operations work?

The other day I found out that my Docker container had been killed as the docker daemon had been automatically upgraded on an AWS box I was running.

journald showed these messages in the relevant time slot:

Aug 06 05:56:01 ip-192-168-3-117 systemd[1]: Starting Daily apt download activities...
Aug 06 05:56:11 ip-192-168-3-117 systemd[1]: Started Daily apt download activities.
Aug 06 06:06:39 ip-192-168-3-117 systemd[1]: Starting Daily apt upgrade and clean activities...
Aug 06 06:06:48 ip-192-168-3-117 systemd[1]: Reloading.
Aug 06 06:06:48 ip-192-168-3-117 systemd[1]: Starting Message of the Day...
Aug 06 06:06:48 ip-192-168-3-117 systemd[1]: Reloading.
Aug 06 06:06:49 ip-192-168-3-117 systemd[1]: Reloading.
Aug 06 06:06:49 ip-192-168-3-117 systemd[1]: Stopping Docker Application Container Engine...

How can I know when this is scheduled to run? I looked through the various cron jobs in /etc and I thought /etc/cron.daily/apt-compat was involved, since it contained this at the end:

# delay the job execution by a random amount of time
random_sleep

# ensure we don't do this on battery
check_power || exit 0

# run daily job
exec /usr/lib/apt/apt.systemd.daily

but it turns out it never gets that far, as it actually just uses systemd. I overlooked this at the start of cron.daily/apt-compat:

# Systemd systems use a systemd timer unit which is preferable to
# run. We want to randomize the apt update and unattended-upgrade
# runs as much as possible to avoid hitting the mirrors all at the
# same time. The systemd time is better at this than the fixed
# cron.daily time
if [ -d /run/systemd/system ]; then
    exit 0
fi

So somehow systemd schedules this to run instead.

That file, /usr/lib/apt/apt.systemd.daily, basically seems like the script responsible, although I cannot find any of the strings above, like "Starting .* activities".

So systemd is scheduling this, but where is this stored? Where does is it told to run /usr/lib/apt/apt.systemd.daily?

Quite a few times over the years have I had Ubuntu lock-up at some point, and upon starting I have found that the file system has been damaged in some way. I only notice what went wrong when trying to access files during development and getting errors, making me have to clone repos and whatnot all over. I thought journalling was supposed to take care of this, but does not seem so ... For the last few years, Ubuntu has been running in VMWare, and that has worked pretty darn well, but some time ago the VM crashed - again causing file system corruption on the ext3 partition.

This left me wondering: Windows and the device drivers has its own layer of file system caching. Can I disable write caching in Ubuntu without a noticeable performance hit in order to avoid/minimize file system corruption? Running on SSDs and such makes the performance pretty good anyway.

For the longest time I have a huge performance issue in my Ubuntu VM, as every day at some time the cpu would be at a 100%, pointing to the fuse process that mounts the shared directories under /mnt/hgfs as the problem. To find out what was causing it I did

$ sudo lsof /mnt/hgfs/
[sudo] passord for myuser: 
COMMAND   PID   USER   FD   TYPE DEVICE SIZE/OFF    NODE NAME
find    20811 nobody    4r   DIR   0,45   327680 1644542 /mnt/hgfs/SharedData/Users/myuser/Pictures/Lightroom/Main Previews.lrdata/9

Followed by finding the parent of that find process:

$ sudo pstree -s -p 20811
systemd(1)───anacron(20328)───sh(20470)───run-parts(20472)───locate(20715)───updatedb.findut(20720)───updatedb.findut(20728)───su(20786)───sh(20809)───find(20811+

So it was a cron job that caused this by invoking updatedb. That's fine, I know updatedb has a config file at /etc/updatedb.conf and so I added /mnt/hgfs to the PRUNEPATHS variable and thought that would be it.

Turns out it was not. The same problem kept coming up.

OK, so grepping the /etc/cron.* directories I quickly discovered /etc/cron.daily/locate, and this time I took a look and discovered the script sets its own custom configuration, including PRUNEPATHS. It does not seem to consult /etc/updatedb.conf at all. This seems highly confusing to me. What is the point of a config file that is not used in the daily updates? Now I need to hack a system supplied file for this to work. That seems counter-intuitive and not something I am used to from Ubuntu.

Could someone explain the logic here, alternatively how this was supposed to work?

My laptop has been working mostly fine with Ubuntu 18.04. But recently (like the last week of March) I have noticed that it always boots up to a fresh login - meaning that it has powered down without hibernating or going into standby. Naturally, this sucks on a production (job) computer!

I am assuming this is due to either 1. a bad driver/firmware update (which has happened recently) 2. some new software in Ubuntu

My power settings don't imply anything else than that the laptop should go into hibernation after some time, and I haven't changed any settings.

How can I find out what is causing this? Is there an event log being written somewhere - other than syslog? I can read this from my syslog today:

Mar 29 14:13:07 diffia9350 org.gnome.Shell.desktop[3042]: [4869:4890:0329/141307.593101:ERROR:connection_factory_impl.cc(411)] Failed to connect to MCS endpoint with error -106
Mar 29 14:13:09 diffia9350 systemd[1]: Reached target Sleep.
Mar 29 14:13:09 diffia9350 systemd[1]: Starting Suspend...
Mar 29 14:13:09 diffia9350 systemd-sleep[9174]: Suspending system...
Mar 29 14:13:09 diffia9350 kernel: [ 4315.853054] PM: suspend entry (deep)
Mar 29 14:43:38 diffia9350 systemd-modules-load[360]: Inserted module 'lp'

So it does go into suspend mode. And I can see it waking up half an hour later.

Again:

Mar 29 16:09:49 diffia9350 NetworkManager[1150]: <info>  [1553872189.3201] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Mar 29 16:09:49 diffia9350 NetworkManager[1150]: <info>  [1553872189.3203] device (wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Mar 29 16:09:49 diffia9350 NetworkManager[1150]: <info>  [1553872189.3311] manager: NetworkManager state is now ASLEEP
Mar 29 16:09:49 diffia9350 gnome-shell[1994]: Screen lock is locked down, not locking
Mar 29 16:09:49 diffia9350 gnome-shell[1994]: Failed to set power save mode for output eDP-1: Ikke tilgang
Mar 29 16:09:49 diffia9350 wpa_supplicant[1141]: nl80211: deinit ifname=p2p-dev-wlp58s0 disabled_11b_rates=0
Mar 29 16:09:49 diffia9350 systemd[1]: Reached target Sleep.
Mar 29 16:09:49 diffia9350 systemd[1]: Starting Suspend...
Mar 29 16:09:49 diffia9350 systemd-sleep[10369]: Suspending system...
Mar 29 17:38:13 diffia9350 systemd-modules-load[355]: Inserted module 'lp'
Mar 29 17:38:13 diffia9350 systemd-modules-load[355]: Inserted module 'ppdev'
Mar 29 17:38:13 diffia9350 systemd-modules-load[355]: Inserted module 'parport_pc'
Mar 29 17:38:13 diffia9350 systemd[1]: Mounted Huge Pages File System.
Mar 29 17:38:13 diffia9350 systemd[1]: Started Remount Root and Kernel File Systems.
Mar 29 17:38:13 diffia9350 systemd[1]: Starting Load/Save Random Seed...
Mar 29 17:38:13 diffia9350 systemd[1]: Starting Flush Journal to Persistent Storage...
Mar 29 17:38:13 diffia9350 systemd[1]: Starting Create Static Device Nodes in /dev...

In my dotfiles I have some functions that rely on aliases or functions to exist for them to work. For some reason, I can get them to reference other functions I have created, but not aliases for commands. How do I fix this?

Example:

function open-dotfiles-commit(){ 
    xopen https://github.com/fatso83/dotfiles/blob/$1; 
}

If I have an alias xopen (alias xopen=xdg-open), the open-dotfiles-commit command will fail with xopen: cannot find command. On the other hand, if I replace the alias definition with a function called xopen (function xopen(){ xdg-open; };) it works!

I have even tried setting shopt -s expand_aliases in the same file as where I define the aliases - unsuccessfully. The alias and functions file is sourced by my .bashrc.

I bought a second hand computer, which seems to have a faulty USB port (or something - I haven't encountered it). The only real annoyance is that my syslogs are spammed with the same messages:

[2864513.931908] usb usb4-port2: cannot disable (err = -32)
[2864518.003911] usb usb4-port2: Cannot enable. Maybe the USB cable is bad?
[2864518.003925] xhci_hcd 0000:00:14.0: Cannot set link state.

That three errors every four to five seconds. Due to these, it's hard to notice all the actual/important stuff.

I would like to get rid of these, but I cannot disable USB altogether, as I need it from time to time. Also, it seems the built-in camera is using USB somehow, so the driver seems needed.

Is there some way of disabling usb4-port2 to avoid these errors showing?

This gist has a section from my syslog from the point of suspend to resuming, which ultimately caused X to crash. But I cannot find out which program or service was the actual culprit ... Is there anything from the syslog which is the obvious sinner?

Jun 19 17:20:46 e6330 wpa_supplicant[915]: wlp2s0: WPA: Group rekeying completed with ec:08:6b:ff:d3:bc [GTK=CCMP]
Jun 19 17:28:26 e6330 pulseaudio[31070]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.
Jun 19 17:28:41 e6330 NetworkManager[914]: <info>  [1529422121.5642] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jun 19 17:28:41 e6330 NetworkManager[914]: <info>  [1529422121.5710] manager: NetworkManager state is now ASLEEP
Jun 19 17:28:41 e6330 gnome-shell[31045]: Screen lock is locked down, not locking
Jun 19 17:28:41 e6330 gnome-shell[31045]: Failed to set power save mode for output LVDS-1: Permission denied
Jun 19 17:28:41 e6330 NetworkManager[914]: <info>  [1529422121.7631] device (wlp2s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jun 19 17:28:41 e6330 NetworkManager[914]: <info>  [1529422121.7950] device (wlp2s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jun 19 17:28:41 e6330 avahi-daemon[889]: Withdrawing address record for fe80::55d8:3e2d:6360:269 on wlp2s0.
Jun 19 17:28:41 e6330 avahi-daemon[889]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::55d8:3e2d:6360:269.
Jun 19 17:28:41 e6330 avahi-daemon[889]: Interface wlp2s0.IPv6 no longer relevant for mDNS.
Jun 19 17:28:41 e6330 NetworkManager[914]: <info>  [1529422121.8988] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP client pid 4680
Jun 19 17:28:41 e6330 NetworkManager[914]: <info>  [1529422121.8989] dhcp4 (wlp2s0): state changed bound -> done
Jun 19 17:28:41 e6330 avahi-daemon[889]: Withdrawing address record for 192.168.100.133 on wlp2s0.
Jun 19 17:28:41 e6330 avahi-daemon[889]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.100.133.
Jun 19 17:28:41 e6330 avahi-daemon[889]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Jun 19 17:28:41 e6330 NetworkManager[914]: <info>  [1529422121.9308] device (wlp2s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jun 19 17:28:41 e6330 kernel: [74145.847566] wlp2s0: deauthenticating from ec:08:6b:ff:d3:bc by local choice (Reason: 3=DEAUTH_LEAVING)
Jun 19 17:28:41 e6330 whoopsie[1345]: [17:28:41] offline
Jun 19 17:28:42 e6330 dbus-daemon[904]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.16' (uid=0 pid=914 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jun 19 17:28:42 e6330 wpa_supplicant[915]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=ec:08:6b:ff:d3:bc reason=3 locally_generated=1
Jun 19 17:28:42 e6330 gsd-sharing[31821]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share-webdav.service not loaded.
Jun 19 17:28:42 e6330 gsd-sharing[31821]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Jun 19 17:28:42 e6330 gsd-sharing[31821]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
Jun 19 17:28:42 e6330 gsd-sharing[31821]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded.
Jun 19 17:28:42 e6330 wpa_supplicant[915]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
Jun 19 17:28:42 e6330 systemd[1]: Reached target Sleep.
Jun 19 17:28:42 e6330 systemd[1]: Starting Suspend...
Jun 19 17:28:42 e6330 systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 19 17:28:42 e6330 dbus-daemon[904]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 19 17:28:42 e6330 nm-dispatcher: req:1 'connectivity-change': new request (1 scripts)
Jun 19 17:28:42 e6330 nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Jun 19 17:28:42 e6330 systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 19 17:28:42 e6330 nm-dispatcher: req:2 'down' [wlp2s0]: new request (1 scripts)
Jun 19 17:28:42 e6330 nm-dispatcher: req:2 'down' [wlp2s0]: start running ordered scripts...
Jun 19 17:28:42 e6330 kernel: [74146.271640] PM: suspend entry (deep)
Jun 19 17:28:42 e6330 systemd-sleep[14309]: Suspending system...
Jun 19 17:28:42 e6330 kernel: [74146.271642] PM: Syncing filesystems ... done.
Jun 19 17:29:21 e6330 kernel: [74146.373131] Freezing user space processes ... (elapsed 0.029 seconds) done.
Jun 19 17:29:21 e6330 kernel: [74146.402655] OOM killer disabled.
Jun 19 17:29:21 e6330 kernel: [74146.402656] Freezing remaining freezable tasks ... 
Jun 19 17:29:21 e6330 kernel: [74153.324663] (elapsed 6.922 seconds) done.
Jun 19 17:29:21 e6330 systemd-sleep[14309]: System resumed.
Jun 19 17:29:21 e6330 rtkit-daemon[1252]: The canary thread is apparently starving. Taking action.
Jun 19 17:29:21 e6330 rtkit-daemon[1252]: Demoting known real-time threads.
Jun 19 17:29:21 e6330 rtkit-daemon[1252]: Demoted 0 threads.
Jun 19 17:29:21 e6330 kernel: [74153.324706] Suspending console(s) (use no_console_suspend to debug)
Jun 19 17:29:21 e6330 kernel: [74153.338356] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 19 17:29:21 e6330 kernel: [74153.342880] sd 0:0:0:0: [sda] Stopping disk
Jun 19 17:29:21 e6330 kernel: [74153.379078] e1000e: EEE TX LPI TIMER: 00000011
Jun 19 17:29:21 e6330 kernel: [74153.506865] ACPI: Preparing to enter system sleep state S3
Jun 19 17:29:21 e6330 kernel: [74153.550763] ACPI: EC: event blocked
Jun 19 17:29:21 e6330 kernel: [74153.550764] ACPI: EC: EC stopped
Jun 19 17:29:21 e6330 kernel: [74153.550765] PM: Saving platform NVS memory
Jun 19 17:29:21 e6330 kernel: [74153.550783] Disabling non-boot CPUs ...
Jun 19 17:29:21 e6330 kernel: [74153.566860] IRQ 28: no longer affine to CPU1
Jun 19 17:29:21 e6330 kernel: [74153.567876] smpboot: CPU 1 is now offline
Jun 19 17:29:21 e6330 kernel: [74153.587854] smpboot: CPU 2 is now offline
Jun 19 17:29:21 e6330 kernel: [74153.610720] IRQ 16: no longer affine to CPU3
Jun 19 17:29:21 e6330 kernel: [74153.610730] IRQ 30: no longer affine to CPU3
Jun 19 17:29:21 e6330 kernel: [74153.611739] smpboot: CPU 3 is now offline
Jun 19 17:29:21 e6330 kernel: [74153.613571] ACPI: Low-level resume complete
Jun 19 17:29:21 e6330 kernel: [74153.613627] ACPI: EC: EC started
Jun 19 17:29:21 e6330 google-chrome.desktop[12557]: [12557:12575:0619/172921.436188:ERROR:connection_factory_impl.cc(403)] Failed to connect to MCS endpoint with error -106
Jun 19 17:29:21 e6330 kernel: [74153.613627] PM: Restoring platform NVS memory
Jun 19 17:29:21 e6330 kernel: [74153.613969] Enabling non-boot CPUs ...
Jun 19 17:29:21 e6330 kernel: [74153.614048] x86: Booting SMP configuration:
Jun 19 17:29:21 e6330 kernel: [74153.614049] smpboot: Booting Node 0 Processor 1 APIC 0x2
Jun 19 17:29:21 e6330 kernel: [74153.616564]  cache: parent cpu1 should not be sleeping
Jun 19 17:29:21 e6330 kernel: [74153.616822] CPU1 is up
Jun 19 17:29:21 e6330 kernel: [74153.616853] smpboot: Booting Node 0 Processor 2 APIC 0x1
Jun 19 17:29:21 e6330 kernel: [74153.619311]  cache: parent cpu2 should not be sleeping
Jun 19 17:29:21 e6330 kernel: [74153.619536] CPU2 is up
Jun 19 17:29:21 e6330 kernel: [74153.619565] smpboot: Booting Node 0 Processor 3 APIC 0x3
Jun 19 17:29:21 e6330 kernel: [74153.622002]  cache: parent cpu3 should not be sleeping
Jun 19 17:29:21 e6330 kernel: [74153.622417] CPU3 is up
Jun 19 17:29:21 e6330 kernel: [74153.625927] ACPI: Waking up from system sleep state S3
Jun 19 17:29:21 e6330 kernel: [74154.077382] ACPI: EC: event unblocked
Jun 19 17:29:21 e6330 kernel: [74154.080235] sd 0:0:0:0: [sda] Starting disk
Jun 19 17:29:21 e6330 kernel: [74154.709912] restoring control 00000000-0000-0000-0000-000000000101/10/5
Jun 19 17:29:21 e6330 kernel: [74154.709914] restoring control 00000000-0000-0000-0000-000000000101/12/11
Jun 19 17:29:21 e6330 kernel: [74155.014866] OOM killer enabled.
Jun 19 17:29:21 e6330 kernel: [74155.014866] Restarting tasks ... done.
Jun 19 17:29:21 e6330 kernel: [74155.052409] pci_bus 0000:01: Allocating resources
Jun 19 17:29:21 e6330 kernel: [74155.052423] pci_bus 0000:02: Allocating resources
Jun 19 17:29:21 e6330 kernel: [74155.052441] pci_bus 0000:03: Allocating resources
Jun 19 17:29:21 e6330 kernel: [74155.052458] pci_bus 0000:07: Allocating resources
Jun 19 17:29:21 e6330 kernel: [74155.064880] acpi PNP0401:00: Already enumerated
Jun 19 17:29:21 e6330 kernel: [74155.083897] acpi PNP0501:00: Still not present
Jun 19 17:29:21 e6330 kernel: [74155.122537] PM: suspend exit
Jun 19 17:29:21 e6330 kernel: [74155.596166] ata1.01: failed to resume link (SControl 0)
Jun 19 17:29:21 e6330 kernel: [74155.596248] ata2.01: failed to resume link (SControl 0)
Jun 19 17:29:21 e6330 kernel: [74155.756218] ata1.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Jun 19 17:29:21 e6330 kernel: [74155.756234] ata1.01: SATA link down (SStatus 0 SControl 0)
Jun 19 17:29:21 e6330 kernel: [74155.759160] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Jun 19 17:29:21 e6330 kernel: [74155.759167] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Jun 19 17:29:21 e6330 kernel: [74155.759171] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jun 19 17:29:21 e6330 kernel: [74155.765540] ata1.00: configured for UDMA/133
Jun 19 17:29:21 e6330 bluetoothd[884]: Endpoint unregistered: sender=:1.291 path=/MediaEndpoint/A2DPSource
Jun 19 17:29:21 e6330 bluetoothd[884]: Endpoint unregistered: sender=:1.291 path=/MediaEndpoint/A2DPSink
Jun 19 17:29:21 e6330 NetworkManager[914]: <info>  [1529422161.5099] bluez5: NAP: removed interface 20:16:D8:97:AA:44
Jun 19 17:29:21 e6330 NetworkManager[914]: <info>  [1529422161.5121] bluez5: NAP: added interface 20:16:D8:97:AA:44
Jun 19 17:29:21 e6330 systemd[1]: Starting Load/Save RF Kill Switch Status...
Jun 19 17:29:21 e6330 systemd-rfkill[14446]: Failed to open device rfkill16: No such device
Jun 19 17:29:21 e6330 bluetoothd[884]: Endpoint registered: sender=:1.291 path=/MediaEndpoint/A2DPSource
Jun 19 17:29:21 e6330 bluetoothd[884]: Endpoint registered: sender=:1.291 path=/MediaEndpoint/A2DPSink
Jun 19 17:29:21 e6330 systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
Jun 19 17:29:21 e6330 systemd[1]: Stopped target Bluetooth.
Jun 19 17:29:21 e6330 systemd-sleep[14309]: /dev/sda:
Jun 19 17:29:21 e6330 systemd-sleep[14309]:  setting Advanced Power Management level to 0x80 (128)
Jun 19 17:29:21 e6330 systemd-sleep[14309]:  APM_level#011= 128
Jun 19 17:29:21 e6330 systemd[1]: Reached target Bluetooth.
Jun 19 17:29:21 e6330 systemd[1]: Started Load/Save RF Kill Switch Status.
Jun 19 17:29:21 e6330 systemd-sleep[14309]: /dev/sda:
Jun 19 17:29:21 e6330 systemd-sleep[14309]:  setting standby to 36 (3 minutes)
Jun 19 17:29:21 e6330 systemd[1]: Started Suspend.
Jun 19 17:29:21 e6330 systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Jun 19 17:29:21 e6330 systemd[1]: Stopped target Sleep.
Jun 19 17:29:21 e6330 systemd[1]: Reached target Suspend.
Jun 19 17:29:21 e6330 systemd[1]: suspend.target: Unit not needed anymore. Stopping.
Jun 19 17:29:21 e6330 systemd[1]: Stopped target Suspend.
Jun 19 17:29:21 e6330 NetworkManager[914]: <info>  [1529422161.8614] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jun 19 17:29:21 e6330 NetworkManager[914]: <info>  [1529422161.8615] device (eno1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jun 19 17:29:21 e6330 kernel: [74156.575807] e1000e: eno1 NIC Link is Down
Jun 19 17:29:21 e6330 gnome-shell[31045]: Failed to set power save mode for output LVDS-1: Permission denied
Jun 19 17:29:21 e6330 NetworkManager[914]: <info>  [1529422161.9683] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Jun 19 17:29:21 e6330 kernel: [74156.582687] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Jun 19 17:29:22 e6330 goa-daemon[31772]: secret_password_lookup_sync() returned NULL
Jun 19 17:29:22 e6330 google-chrome.desktop[12557]: [12557:12557:0619/172922.138320:ERROR:chrome_browser_main_extra_parts_x11.cc(62)] X IO error received (X server probably went away)
Jun 19 17:29:22 e6330 at-spi-bus-launcher[31698]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jun 19 17:29:22 e6330 at-spi-bus-launcher[31698]:       after 18829 requests (18829 known processed) with 0 events remaining.
Jun 19 17:29:22 e6330 NetworkManager[914]: <info>  [1529422162.1873] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Jun 19 17:29:22 e6330 kernel: [74156.800355] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Jun 19 17:29:22 e6330 google-chrome.desktop[12557]: [12601:12601:0619/172922.213563:ERROR:x11_util.cc(90)] X IO error received (X server probably went away)
Jun 19 17:29:22 e6330 org.gnome.Shell.desktop[31720]: Gdk-Message: 17:29:22.221: /usr/lib/firefox/firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jun 19 17:29:22 e6330 kernel: [74156.847330] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Jun 19 17:29:22 e6330 kernel: [74156.860440] iwlwifi 0000:02:00.0: Radio type=0x0-0x3-0x1
Jun 19 17:29:22 e6330 gnome-shell[31720]: gnome-shell: Fatal IO error 104 (Connection reset by peer) on X server :0.
Jun 19 17:29:22 e6330 [31832]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jun 19 17:29:22 e6330 gsd-clipboard[31849]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jun 19 17:29:22 e6330 gnome-terminal-[32304]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jun 19 17:29:22 e6330 org.gnome.Shell.desktop[31720]: Gdk-Message: 17:29:22.346: /usr/lib/firefox/firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jun 19 17:29:22 e6330 gsd-media-keys[31861]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jun 19 17:29:22 e6330 update-notifier[355]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jun 19 17:29:22 e6330 gsd-power[31813]: gsd-power: Fatal IO error 104 (Connection reset by peer) on X server :0.
Jun 19 17:29:22 e6330 gsd-wacom[31840]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jun 19 17:29:22 e6330 gsd-color[31856]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jun 19 17:29:22 e6330 firefox[10518]: firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jun 19 17:29:22 e6330 org.gnome.Shell.desktop[31720]: Sandbox: Unexpected EOF, op 2 flags 00 path /etc/localtime
Jun 19 17:29:22 e6330 gnome-session[31606]: gnome-session-binary[31606]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session-binary[31606]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session[31606]: gnome-session-binary[31606]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session-binary[31606]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session[31606]: gnome-session-binary[31606]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session-binary[31606]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session[31606]: gnome-session-binary[31606]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session-binary[31606]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
Jun 19 17:29:22 e6330 kernel: [74157.110810] iwlwifi 0000:02:00.0: Radio type=0x0-0x3-0x1
Jun 19 17:29:22 e6330 bluetoothd[884]: Endpoint unregistered: sender=:1.291 path=/MediaEndpoint/A2DPSource
Jun 19 17:29:22 e6330 bluetoothd[884]: Endpoint unregistered: sender=:1.291 path=/MediaEndpoint/A2DPSink
Jun 19 17:29:22 e6330 kernel: [74157.209997] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Jun 19 17:29:22 e6330 NetworkManager[914]: <info>  [1529422162.5983] manager: NetworkManager state is now DISCONNECTED
Jun 19 17:29:22 e6330 gnome-session[31606]: gnome-session-binary[31606]: WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session[31606]: gnome-session-binary[31606]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session-binary[31606]: WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session-binary[31606]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
Jun 19 17:29:22 e6330 wpa_supplicant[915]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Jun 19 17:29:22 e6330 wpa_supplicant[915]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Jun 19 17:29:22 e6330 wpa_supplicant[915]: dbus: Failed to construct signal
Jun 19 17:29:22 e6330 wpa_supplicant[915]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Jun 19 17:29:22 e6330 NetworkManager[914]: <info>  [1529422162.6965] device (wlp2s0): supplicant interface state: starting -> ready
Jun 19 17:29:22 e6330 kernel: [74157.310768] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Jun 19 17:29:22 e6330 NetworkManager[914]: <info>  [1529422162.6967] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jun 19 17:29:22 e6330 gnome-shell[14514]: Failed to create backend: Unable to open display ':0'
Jun 19 17:29:22 e6330 gnome-session[31606]: gnome-session-binary[31606]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session[31606]: gnome-session-binary[31606]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Jun 19 17:29:22 e6330 gnome-session-binary[31606]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jun 19 17:29:22 e6330 gnome-session-binary[31606]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Jun 19 17:29:22 e6330 gnome-session-binary[31606]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jun 19 17:29:22 e6330 gnome-session[31606]: gnome-session-binary[31606]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Jun 19 17:29:22 e6330 gnome-session-binary[31606]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Jun 19 17:29:22 e6330 systemd[31579]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
Jun 19 17:29:22 e6330 systemd[31579]: gnome-terminal-server.service: Failed with result 'exit-code'.
Jun 19 17:29:22 e6330 gsd-color[31111]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_LG_Display_carlerik_1000
Jun 19 17:29:22 e6330 kernel: [74157.483868] rfkill: input handler enabled
Jun 19 17:29:22 e6330 gsd-keyboard[31869]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jun 19 17:29:22 e6330 gsd-printer[31885]: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.6 was not provided by any .service files
Jun 19 17:29:23 e6330 goa-daemon[31772]: secret_password_lookup_sync() returned NULL
Jun 19 17:29:24 e6330 ModemManager[919]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Jun 19 17:29:24 e6330 ModemManager[919]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0': not supported by any plugin
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8310] policy: auto-activating connection 'breiband'
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8320] device (wlp2s0): Activation: starting connection 'breiband' (eb1aaa3e-1dc0-4296-8772-94fb09a1365b)
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8322] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8324] manager: NetworkManager state is now CONNECTING
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8330] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8332] device (wlp2s0): Activation: (wifi) access point 'breiband' has security, but secrets are required.
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8333] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8334] sup-iface[0x556a7134e390,wlp2s0]: wps: type pbc start...
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8372] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8376] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8377] device (wlp2s0): Activation: (wifi) connection 'breiband' has security, and secrets exist.  No new secrets needed.
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8380] Config: added 'ssid' value 'breiband'
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8380] Config: added 'scan_ssid' value '1'
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8380] Config: added 'bgscan' value 'simple:30:-80:86400'
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8381] Config: added 'key_mgmt' value 'WPA-PSK'
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8381] Config: added 'auth_alg' value 'OPEN'
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8381] Config: added 'psk' value '<hidden>'
Jun 19 17:29:25 e6330 wpa_supplicant[915]: wlp2s0: SME: Trying to authenticate with ec:08:6b:ff:d3:bc (SSID='breiband' freq=2462 MHz)
Jun 19 17:29:25 e6330 kernel: [74160.464063] wlp2s0: authenticate with ec:08:6b:ff:d3:bc
Jun 19 17:29:25 e6330 kernel: [74160.465414] wlp2s0: send auth to ec:08:6b:ff:d3:bc (try 1/3)
Jun 19 17:29:25 e6330 wpa_supplicant[915]: wlp2s0: Trying to associate with ec:08:6b:ff:d3:bc (SSID='breiband' freq=2462 MHz)
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8557] device (wlp2s0): supplicant interface state: ready -> associating
Jun 19 17:29:25 e6330 kernel: [74160.468140] wlp2s0: authenticated
Jun 19 17:29:25 e6330 kernel: [74160.476072] wlp2s0: associate with ec:08:6b:ff:d3:bc (try 1/3)
Jun 19 17:29:25 e6330 kernel: [74160.479874] wlp2s0: RX AssocResp from ec:08:6b:ff:d3:bc (capab=0x431 status=0 aid=2)
Jun 19 17:29:25 e6330 wpa_supplicant[915]: wlp2s0: Associated with ec:08:6b:ff:d3:bc
Jun 19 17:29:25 e6330 kernel: [74160.487069] wlp2s0: associated
Jun 19 17:29:25 e6330 wpa_supplicant[915]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8791] device (wlp2s0): supplicant interface state: associating -> 4-way handshake
Jun 19 17:29:25 e6330 wpa_supplicant[915]: wlp2s0: WPA: Key negotiation completed with ec:08:6b:ff:d3:bc [PTK=CCMP GTK=CCMP]
Jun 19 17:29:25 e6330 wpa_supplicant[915]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to ec:08:6b:ff:d3:bc completed [id=0 id_str=]
Jun 19 17:29:25 e6330 kernel: [74160.495890] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8873] device (wlp2s0): supplicant interface state: 4-way handshake -> completed
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8873] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'breiband'.
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8874] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8888] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.8945] dhcp4 (wlp2s0): dhclient started with pid 14544
Jun 19 17:29:25 e6330 dhclient[14544]: DHCPREQUEST of 192.168.100.133 on wlp2s0 to 255.255.255.255 port 67 (xid=0x1e2aeb94)
Jun 19 17:29:25 e6330 dhclient[14544]: DHCPACK of 192.168.100.133 from 192.168.100.1
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.9744] dhcp4 (wlp2s0):   address 192.168.100.133
Jun 19 17:29:25 e6330 NetworkManager[914]: <info>  [1529422165.9745] dhcp4 (wlp2s0):   plen 24 (255.255.255.0)
Jun 19 17:29:25 e6330 avahi-daemon[889]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.100.133.

As can be seen from the above image, the Norwegian language option is not choosable. I cannot select, nor rearrange the options so that anything but the black text option is at the top. I have read through this thread, and tried reinstalling the language packs without any change.

This is a fresh 18.04 install, where I chose English as the language on install, but it still seems to have installed Norwegian language support based on where my IP was located.

edit: I was later on able to move Norwegian to the top and make it the default system language as well, but it didn't affect the input language which was still English keyboard layout. Turns out this isn't set from the Language settings, but from the Region and Language panel ...

Last year I found a way to debug what is capturing keyboard shortcuts, by sending X events using xdotool. Now, I have a similar problem where using the Ctrl-Alt-Left in IntelliJ isn't doing anything, so I suspect something is holding on to it.

This time, though, nothing is printing in the logs!

I also tried with other keycombos that were global (such as Win+a, which opens the applications menu), but they produced no log entries either.

What has changed from Ubuntu 17.04 to 18.04 that disables the log output, and how can I enable the log output? There are other entries in the logs, mind you :)

You can try out my debugging steps using this gist, like this:

~/bin/debug-x-shortcut Super_R+a

As Electron based apps have trouble using the "systray"/tray icons in Gnome, closing (pressing X) on such applications lead effectively to them being hidden, as they also disappear from the application bar (? not sure about that term).

That means opening the app again would open a second (or third or ...) instance, which could cause errors to start appearing.

These apps show when doing ps -ef | grep my-app, but is there any way of getting Gnome to render the window of an app that has been "closed"/hidden from view by sending it some signal?

P.S. I know one can use xdotool or wmctrl to send X signals (see this link), but sending them to a window that has been removed by itself only results in error messages (since the window no longer exists).

edit: As can be seen from the answer, this actually had nothing to do with standby or hibernation, but rather that it correlated with me often closing the app window (which triggered the bug) before going into standby most of the time.

I have seen multiple people report this in various places on the net, without any solution, but thought I would add mine in any case:

Very often, after returning to the computer after some time (when it has gone into standby), I notice that some shortcuts have stopped working. This does not only happen in the terminal, but also in Chrome (Ctrl-L, Ctrl-R, F5 all stops working). It also does not affect all ctrl-shortcuts: Ctrl-C is still working for instance (thank God!).

Is there any way of debugging this? Trying out xev earlier hasn't gotten me anywhere, but perhaps there is some way of finding out what is preventing my keypresses from reaching the programs?

edit: I can see something weird happening with Ctrl-R

Something is grabbing the keyboard shortcut!

Output captured from xev

KeyPress event, serial 37, synthetic NO, window 0x5200001,
    root 0xee, subw 0x0, time 24547557, (-130,529), root:(0,633),
    state 0x10, keycode 105 (keysym 0xffe4, Control_R), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

FocusOut event, serial 37, synthetic NO, window 0x5200001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 37, synthetic NO, window 0x5200001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 37, synthetic NO, window 0x0,
    keys:  4294967278 0   0   0   0   0   0   0   0   0   0   0   0   2   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

KeyRelease event, serial 37, synthetic NO, window 0x5200001,
    root 0xee, subw 0x0, time 24548550, (-130,529), root:(0,633),
    state 0x14, keycode 105 (keysym 0xffe4, Control_R), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

Compare this to Ctrl-C

we can easily see four logical events happening here

KeyPress event, serial 37, synthetic NO, window 0x5200001,
    root 0xee, subw 0x0, time 24724066, (572,852), root:(702,956),
    state 0x10, keycode 105 (keysym 0xffe4, Control_R), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x5200001,
    root 0xee, subw 0x0, time 24724818, (572,852), root:(702,956),
    state 0x14, keycode 54 (keysym 0x63, c), same_screen YES,
    XLookupString gives 1 bytes: (03) ""
    XmbLookupString gives 1 bytes: (03) ""
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x5200001,
    root 0xee, subw 0x0, time 24724966, (572,852), root:(702,956),
    state 0x14, keycode 54 (keysym 0x63, c), same_screen YES,
    XLookupString gives 1 bytes: (03) ""
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x5200001,
    root 0xee, subw 0x0, time 24725339, (572,852), root:(702,956),
    state 0x14, keycode 105 (keysym 0xffe4, Control_R), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

Any clues to why it takes 20-30 seconds for me to log in using sudo+su?

$ time sudo su ida -l
exit
ida@timbuktu:~$ exit
logout

real    0m18.076s

$ time sudo su ida
exit
ida@timbuktu:/home/carl-erik$ exit
exit

real    0m25.082s

This is quite frustrating when changing users frequently to do work. I might add that this might not be strictly restrictred to sudo, as logging in using ssh also takes approx 25 seconds.

The contents of these files were requested. They are unaltered.

/etc/nsswitch.conf

passwd:         compat
group:          compat
shadow:         compat

hosts:          files mdns4_minimal [NOTFOUND=return] dns mdns4
networks:       files

protocols:      db files
services:       db files
ethers:         db files
rpc:            db files

netgroup:       nis

/etc/hosts

127.0.0.1       localhost
127.0.1.1       myhostname.myisp.net       myhostname
192.168.10.2    myhostname.hopto.org

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters