You are not logged in.
Pages: 1
Hello,
On my latest (Linux Mint) XFCE install I am experiencing problems with the Whisker (start) menu.
When I open it either by mouse or by using the super key, I am often not able to type in the menu to find the program I want to launch.
There is no blinking cursor in the text entry field, and clicking said field also does not give the ability to type.
If I open and close the menu a few times, it works as expected again and I can type a search query to find the program I wish to launch.
How can I help you guys helping me by solving this bug?
Looking forward to your replies.
Offline
Hello and welcome.
What version of the plugin are you using? There was a recent bug report about a delay opening the menu in Mint. Not exactly the same symptoms, but might be related.
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
Thank you for your reply ToZ.
sudo apt-get -s install xfce4-whiskermenu-plugin
[sudo] password for mastermind:
Reading package lists... Done
Building dependency tree
Reading state information... Done
xfce4-whiskermenu-plugin is already the newest version (1.7.3-0ppa1~xenial1).
Plugin version: 1.7.3.
I see that the latest version is 2.1.4, but I don't think that has hit the Mint repositories yet.
Offline
I am using LM 18.2 Xfce 64 bit with xfce4-whiskermenu-plugin 1.7.3 and I can not confirm that behaviour.
LM18.3 beta Xfce 64 bit ships with same version xfce4-whiskermenu-plugin (I am running that in a vbox) and that is also ok here ...
Offline
Thank you for your addition to this topic k-3.14.
As suspected this bug is not affecting everyone.
So what can I do to help trace the source of this issue (debug modes, special logs, etcetera).
It is very probably that if I have this on a fresh install it might affect some other people too, not a great introduction if the start menu is acting up and it is your first Linux experience. I come from Arch and have no trouble replacing the menu for now, but I'd like to see this solved for both myself and others.
Last edited by Mastermind (2017-12-09 14:29:05)
Offline
So what can I do to help trace the source of this issue (debug modes, special logs, etcetera).
Try this. Create the file /usr/local/bin/xfce4-panel with the following content:
#!/bin/sh
PANEL_DEBUG=true /usr/bin/xfce4-panel > /tmp/xfce4-panel.log 2>&1
...and make the file executable.
Then log out and back in again. When the system is ready, open a terminal window and run:
tail -f /tmp/xfce4-panel.log
Then click on the whisker menu. Note what is displayed in the terminal window. Feel free to post back both this and the full contents of the log file if you want a second set of eyes to look at it.
To revert, simply delete the /usr/local/bin/xfce4-panel file and log out and back in again.
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
Thank you for your reply ToZ.
Nothing interesting in the debug logfile I'm afraid:
cat /tmp/xfce4-panel.log
xfce4-panel(main): version 4.12.0 on gtk+ 2.24.30 (2.24.28), glib 2.48.2 (2.45.6)
xfce4-panel: There is already a running instance
xfce4-panel(systray): unregistered manager
xfce4-panel(systray): registered manager on screen 0
xfce4-panel(base-window): 0x562540a64150: compositing=false
xfce4-panel(base-window): 0x562540a64150: compositing=true
xfce4-panel(systray): unregistered manager
xfce4-panel(systray): registered manager on screen 0
xfce4-panel(base-window): 0x562540a64150: compositing=false
xfce4-panel(systray): unregistered manager
xfce4-panel(systray): registered manager on screen 0
xfce4-panel(base-window): 0x562540a64150: compositing=true
xfce4-panel(systray): unregistered manager
xfce4-panel(systray): registered manager on screen 0
It does seem to want to start twice?
Furthermore the issue seems to occur only when using the super key. You can see that two windows remain 'selected' in the panel.
Kind regards
Last edited by Mastermind (2017-12-10 16:42:25)
Offline
If you are not using the saved sessions feature, when logged out, delete the contents of the ~/.cache/sessions folder then try logging in. Xfce may be starting it using a cache session.
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
Pages: 1
[ Generated in 0.010 seconds, 7 queries executed - Memory usage: 547.54 KiB (Peak: 548.38 KiB) ]