You are not logged in.
When manjaro wakes up from suspend I experience no response from pressing on Super Key to invoke whisker. Perhaps 10 minutes later whisker menu suddenly shows up. So it seems that the is a delay somewhere. Any ideas?
Specs:
System: Kernel: 4.9.40-1-MANJARO x86_64 (64 bit gcc: 7.1.1)
Desktop: Xfce 4.12.4 (Gtk 2.24.31) Distro: Manjaro Linux
Machine: Device: laptop System: Dell product: XPS 13 9350
Mobo: Dell model: 09JHRY v: A00
UEFI: Dell v: 1.4.18 date: 06/06/2017
Battery BAT0: charge: 13.9 Wh 19.6% condition: 70.8/75.7 Wh (94%)
model: SMP DELL JHXPY53 status: Discharging
CPU: Dual core Intel Core i7-6560U (Skylake rev.3) (-HT-MCP-) cache: 4096 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 8834
clock speeds: max: 3200 MHz 1: 1050 MHz 2: 787 MHz 3: 686 MHz
4: 675 MHz
Graphics: Card: Intel Iris Graphics 540 bus-ID: 00:02.0
Display Server: x11 (X.Org 1.19.3) driver: intel
Resolution: 1280x720@60.00hz
OpenGL: renderer: Mesa DRI Intel Iris Graphics 540 (Skylake GT3e)
version: 4.5 Mesa 17.1.5 Direct Render: Yes
Audio: Card Intel Sunrise Point-LP HD Audio
driver: snd_hda_intel bus-ID: 00:1f.3
Sound: Advanced Linux Sound Architecture v: k4.9.40-1-MANJARO
Network: Card: Broadcom Limited BCM4350 802.11ac Wireless Network Adapter
driver: brcmfmac bus-ID: 3a:00.0
IF: wlp58s0 state: up mac: <filter>
Drives: HDD Total Size: NA (-)
ID-1: /dev/nvme0n1 model: N/A size: 512.1GB
Partition: ID-1: / size: 452G used: 23G (6%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: swap-1 size: 18.34GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p3
Sensors: System Temperatures: cpu: 59.5C mobo: 27.8C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 183 Uptime: 7:40 Memory: 3917.7/15898.0MB
Init: systemd Gcc sys: 7.1.1
Client: Shell (bash 4.4.121) inxi: 2.3.27
$ xfce4-popup-whiskermenu --version
xfce4-popup-whiskermenu 1.7.2
Copyright (C) 2013 Graeme Gott
Issue posted to Manjaro forums
https://forum.manjaro.org/t/after-wakeu … ater/28515
Offline
Hello and welcome.
In a terminal window, run this command:
xev | awk -F'[ )]+' '/^KeyPress/ { a[NR+2] } NR in a { printf "%-3s %s\n", $5, $8 }'
...and press the Super key. When the super key is working, you should see something like "133 Super_L" printed on the screen. Does the key register anything (in xorg) after suspend when it doesn't bring up the whisker menu?
Also helpful might be your journal log entries from the point of resume to see what is happening. For more info, see: https://wiki.archlinux.org/index.php/Systemd#Journal
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
Hello and welcome.
In a terminal window, run this command:
xev | awk -F'[ )]+' '/^KeyPress/ { a[NR+2] } NR in a { printf "%-3s %s\n", $5, $8 }'
...and press the Super key. When the super key is working, you should see something like "133 Super_L" printed on the screen. Does the key register anything (in xorg) after suspend when it doesn't bring up the whisker menu?
When I just log in or wake up from a suspend, when invoking the 1 liner I see
133 Super_L
After a while, '133 Super_L' stops registering and the whiskermenu kicks in. In other words, whiskermenu will supersede the console and not even register that it has been clicked.
Also helpful might be your journal log entries from the point of resume to see what is happening. For more info, see: https://wiki.archlinux.org/index.php/Systemd#Journal
I don't seen any discernible output. For example, if I use
journalctl -f
when the whisker menu doesn't work... I don't see any output in the logfile.
An interesting anomally is that once the system 'syncs', I'll see the whiskermenu flicker on an off many times...I'm assuming it's the amount of times I clicked the Super_L key and the responses are just lagged.
Last edited by kunda (2017-10-17 21:18:49)
Offline
ToZ wrote:Hello and welcome.
In a terminal window, run this command:
xev | awk -F'[ )]+' '/^KeyPress/ { a[NR+2] } NR in a { printf "%-3s %s\n", $5, $8 }'
...and press the Super key. When the super key is working, you should see something like "133 Super_L" printed on the screen. Does the key register anything (in xorg) after suspend when it doesn't bring up the whisker menu?
When I just log in or wake up from a suspend, when invoking the 1 liner I see
133 Super_L
After a while, '133 Super_L' stops registering and the whiskermenu kicks in. In other words, whiskermenu will supersede the console and not even register that it has been clicked.
So there is some sort of lag or hang happening.
ToZ wrote:Also helpful might be your journal log entries from the point of resume to see what is happening. For more info, see: https://wiki.archlinux.org/index.php/Systemd#Journal
I don't seen any discernible output. For example, if I use
journalctl -f
when the whisker menu doesn't work... I don't see any output in the logfile.
I meant more with respect to the suspend/resume log entries. If there is some sort of hang happening, there might be some messages in the journal to indicate so. They probably won't be related to whiskermenu - that's probably a symptom and not the cause.
An interesting anomally is that once the system 'syncs', I'll see the whiskermenu flicker on an off many times...I'm assuming it's the amount of times I clicked the Super_L key and the responses are just lagged.
It sure is starting to sound like something is hanging during the resume that's preventing the keystroke from registering.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
[ Generated in 0.014 seconds, 8 queries executed - Memory usage: 545.04 KiB (Peak: 545.88 KiB) ]