Keyboard "super" (windows key) key turns black screen

zimudec · August 26, 2020, 1:01am

With normal developer use, using nodejs, git client, web browser, vagrant, after hours of use, randomly the following happens:
When you press the “super” key on the keyboard to open the xfce whisker menu, the screen goes black with cursor. I press Ctrl + Alt + F7, and it returns to my desktop, where the displayed whiskey menu appears.

I started closing open processes, and nothing. Until I closed, process xfce4-session, which closed my user session. I opened it again and the “super” button on the keyboard returned to normal operation, opening the whisker menu without locking the screen to black.
With this it seems to me that the problem may go in xfce4 session.

Edit:

Checking more, after leaving the system constantly suspended for a long time, the above mentioned error appears. It only happens sometimes, so I can’t confirm it, but it may be related

motoryzen · September 27, 2020, 1:25pm

My setup:
4790k cpu
rx580 8GB sapphire nitro vid card
Logitech 710+ keyboard
Logitech g600 mouse
z97mpro4 motherboard
1440p 144hz ips monitor
intel 750 800GB pci express ssd ( manjaro …was installed into)
1TB 860 samsung evo drive ( games, docs, etc)
1TB 860 samsung evo drive ( gopro backups)
1TB micron drive ( timeshift backups for mint 20 installation)

I experienced this exact same problem also on Manjaro 20

It began occurring some random time after I either copy and pasted some files from a separate storage drive into my Manjaro-installed drive, or while I was fighting with the xfce panel trying to set it up like I have my Mint 20 cinnamon panel. Or, possibly it began as a result of an update. ( good grief…the creators of xfce need to take a lesson from cinnamon. Legit, cinnamon is so much easier to deal with)

The thing is, I confirmed over and over that both the left and right super keys had absolutely nothing to do with ending the xfce4 session. So when I pressed the super key by itself, it was only supposed to open the whisker menu, but it would basically crash the session/put it in a temporary coma and it would stay that way ( I literally waited over an hour for it to auto come back and never would) until I pressed ctrl alt F7. Then everything came back within 3 seconds or less with the whisker menu open as it should be.

I’ve looked all over the net and your post , zimudec, is the only thing I’ve encountered about this.

Surely someone out there has a fix for this odd and seemingly simple problem. I even purposely changed the default end-xfce4 session OOTB keyboard shortcut key combo to something completely different that I would never use ( I think ctrl alt shift = or +…something like that) and the problem still persisted.

Upon a fresh install of Manjaro 20, the problem is gone, but it reappears after some random time or doing something. I have yet to figure this out

Unfortunately as often as I use the left super key to open that menu ( just like i did in windows from 7 onward and mint cinnamon), this problem makes it a deal-breaker for me trying to use Manjaro, and that saddens me a little. I really wanted to test to see if kernel 5.8 would yield a little better/more stable frame times gaming results for my setup; not that my Mint 20 cinnamon install isn’t solid so far.

Edit:

I never suspend my system in any way sleep nor hibernate as that is already turned off by the time I’m done setting it up. I don’t suspend my laptop either.

If anyone has any ideas I could try, please let me know. I really want to give Manjaro a fair shake here as I’ve heard good things about it from the likes of Anthony from Linus Media Group and a few good things from Chris Titus Tech.

Fabby · September 28, 2020, 10:02am

So this is a different issue. Please open your own topic for this issue as this is considered Thread Hijacking in this community and considered rude…

(Yes, you’re new; yes, we understand; no harm done)

Fabby · September 28, 2020, 10:05am

When it happens, please do the following:

journalctl --system --boot=0 | grep "suspend entry"
journalctl --system --boot=0 | grep "suspend exit"

then have a look at the begin and end time and post the output of:

journalctl --system --boot=0 --since "YYYY-MM-DD HH:MM:SS" --until "YYYY-MM-DD HH:MM:SS"

where obviously --since is the datetime of suspend entry and --until is the datetime of suspension exit.

zimudec · October 2, 2020, 12:27am

Sorry, I have not been able to reproduce the problem, therefore I have not uploaded the requested information.

zimudec · October 2, 2020, 11:41pm

If the problem occurs again, I will attach the results of the previously requested commands.

Thanks!

zimudec · October 8, 2020, 1:05am

Today the problem happened to me. I leave the last 40 lines of journalctl:

oct 07 20:25:53 zimudec systemd[1338]: run-user-969.mount: Succeeded.
oct 07 20:25:53 zimudec systemd[1]: run-user-969.mount: Succeeded.
oct 07 20:25:54 zimudec systemd[1]: user-runtime-dir@969.service: Succeeded.
oct 07 20:25:54 zimudec systemd[1]: Stopped User Runtime Directory /run/user/969.
oct 07 20:25:54 zimudec audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=user-runtime-dir@969 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
oct 07 20:25:54 zimudec systemd[1]: Removed slice User Slice of UID 969.
oct 07 20:25:54 zimudec kernel: audit: type=1131 audit(1602113154.010:236): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=user-runtime-dir@969 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
oct 07 21:01:01 zimudec CROND[50490]: (root) CMD (run-parts /etc/cron.hourly)
oct 07 21:54:47 zimudec kernel: [drm] PCIE gen 2 link speeds already enabled
oct 07 21:54:47 zimudec kernel: [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000).
oct 07 21:54:47 zimudec kernel: radeon 0000:0a:00.0: WB enabled
oct 07 21:54:47 zimudec kernel: radeon 0000:0a:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x0000000076985d37
oct 07 21:54:47 zimudec kernel: radeon 0000:0a:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0x000000004baeab9c
oct 07 21:54:47 zimudec kernel: radeon 0000:0a:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0x00000000e67ac2d1
oct 07 21:54:47 zimudec kernel: radeon 0000:0a:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x00000000e1acbb92
oct 07 21:54:47 zimudec kernel: radeon 0000:0a:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0x00000000d2bd22fd
oct 07 21:54:48 zimudec kernel: [drm] ring test on 0 succeeded in 1 usecs
oct 07 21:54:48 zimudec kernel: [drm] ring test on 1 succeeded in 1 usecs
oct 07 21:54:48 zimudec kernel: [drm] ring test on 2 succeeded in 1 usecs
oct 07 21:54:48 zimudec kernel: [drm] ring test on 3 succeeded in 4 usecs
oct 07 21:54:48 zimudec kernel: [drm] ring test on 4 succeeded in 4 usecs
oct 07 21:54:48 zimudec kernel: [drm] ib test on ring 0 succeeded in 0 usecs
oct 07 21:54:48 zimudec kernel: [drm] ib test on ring 1 succeeded in 0 usecs
oct 07 21:54:48 zimudec kernel: [drm] ib test on ring 2 succeeded in 0 usecs
oct 07 21:54:48 zimudec kernel: [drm] ib test on ring 3 succeeded in 0 usecs
oct 07 21:54:48 zimudec kernel: [drm] ib test on ring 4 succeeded in 0 usecs
oct 07 21:54:50 zimudec systemd[1]: Started Getty on tty2.
oct 07 21:54:50 zimudec audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
oct 07 21:54:50 zimudec kernel: audit: type=1130 audit(1602118490.080:237): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
oct 07 21:54:50 zimudec kernel: fbcon: Taking over console
oct 07 21:54:50 zimudec kernel: Console: switching to colour frame buffer device 170x48
oct 07 21:58:04 zimudec audit: ANOM_PROMISCUOUS dev=vboxnet1 prom=0 old_prom=256 auid=1000 uid=1000 gid=1000 ses=2
oct 07 21:58:04 zimudec audit[2667]: SYSCALL arch=c000003e syscall=16 success=yes exit=0 a0=7 a1=c0485687 a2=7f277262d610 a3=3e3823f959f8 items=0 ppid=2180 pid=2667 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=(none) ses=2 comm="EMT-0" exe="/usr/lib/virtualbox/VBoxHeadless" subj==unconfined key=(null)
oct 07 21:58:04 zimudec audit: PROCTITLE proctitle=2F7573722F6C69622F7669727475616C626F782F56426F78486561646C657373002D2D636F6D6D656E7400686F6D657374656164002D2D7374617274766D0031643765386637342D616630352D346338372D383763342D323662343264623635653164002D2D7672646500636F6E666967
oct 07 21:58:04 zimudec kernel: device vboxnet1 left promiscuous mode
oct 07 21:58:04 zimudec kernel: audit: type=1700 audit(1602118684.490:238): dev=vboxnet1 prom=0 old_prom=256 auid=1000 uid=1000 gid=1000 ses=2
oct 07 21:58:04 zimudec kernel: audit: type=1300 audit(1602118684.490:238): arch=c000003e syscall=16 success=yes exit=0 a0=7 a1=c0485687 a2=7f277262d610 a3=3e3823f959f8 items=0 ppid=2180 pid=2667 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=(none) ses=2 comm="EMT-0" exe="/usr/lib/virtualbox/VBoxHeadless" subj==unconfined key=(null)
oct 07 21:58:04 zimudec kernel: audit: type=1327 audit(1602118684.490:238): proctitle=2F7573722F6C69622F7669727475616C626F782F56426F78486561646C657373002D2D636F6D6D656E7400686F6D657374656164002D2D7374617274766D0031643765386637342D616630352D346338372D383763342D323662343264623635653164002D2D7672646500636F6E666967
oct 07 21:58:14 zimudec kernel: vboxnetflt: 35692 out of 37029 packets were not sent (directed to host)
oct 07 22:01:01 zimudec CROND[56200]: (root) CMD (run-parts /etc/cron.hourly)

It seems the problem is related to my secondary dedicated gpu.

I finished the xcape process, and it no longer locked my screen again, but it does not open the whisker drop-down menu either.

From xfce they tell me that the error seems to be between manjaro and xcape:

Fabby · October 8, 2020, 1:33pm

So it’s specific to XFCE and a bug?
The only thing I can tell you then is: subscribe to the bug and wait for it to be fixed…

zimudec · October 8, 2020, 3:25pm

Yes, that link that I left is the bug that I opened, however, there they answer me that the problem is the implementation or configuration that is made of xcape by manjaro

Fabby · October 8, 2020, 5:35pm

Please follow this then because your output doesn’t show anything…

zimudec · October 15, 2020, 10:08pm

I have another laptop with manjaro installed too, and it doesn’t have xcape in the system autorun.

I disabled xcape from this laptop and added the super button as a shortcut to open the whisker menu of xfce.

If the problem is xcape, I’ll try with that. If the problem occurs again, I will mention it.

samosa-thoke · November 24, 2021, 2:04pm

I’m facing the same issues and pressed the windows key / super key twice (at 15:00h) with the result of my system switching to TTY1 after I pressed it. Ctrl + Alt + F7 gets me back to XFCE.

$ journalctl --system --boot=0 | grep "suspend exit"
$ journalctl --system --boot=0 | grep "suspend entry"
$ journalctl --system --boot=0 --since "2021-11-24 14:55:00"
-- Journal begins at Mon 2021-05-03 08:10:20 CEST, ends at Wed 2021-11-24 14:56:56 CET. --
Nov 24 14:55:35 flathead NetworkManager[629]: <info>  [1637762135.1451] policy: set 'my-company' (wlp114s0) as default for IPv4 routing and DNS
Nov 24 14:56:05 flathead NetworkManager[629]: <info>  [1637762165.5517] policy: set 'Wired connection 1' (enp0s13f0u3u3) as default for IPv4 routing >
Nov 24 14:56:24 flathead wpa_supplicant[914]: wlp114s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-68 noise=-116 txrate=6000
Nov 24 14:56:31 flathead wpa_supplicant[914]: wlp114s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=0 noise=-116 txrate=6000
Nov 24 14:56:34 flathead wpa_supplicant[914]: wlp114s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=-116 txrate=6000
Nov 24 14:56:56 flathead wpa_supplicant[914]: wlp114s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=0 noise=-116 txrate=6000
$ date
Mi 24. Nov 15:01:14 CET 2021

The logs don’t look helpful. Anything else I could try?

Thanks.

Mirdarthos · November 24, 2021, 2:19pm

Hi @samosa-thoke,

This thread is about a year old, according to what I can see. And while this isn’t strictly necroposting, it’s close enough to be frowned upon.

Please open a new support thread in #support with the problem, and providing the neccessary information and, if applicable, [HowTo] post screenshots and links - Contributions / Tutorials - Manjaro Linux Forum

system · November 27, 2021, 4:20am

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.