We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.7.7-dirty
https://gist.github.com/skygunner/2bef40f2c171c996c80d36943af19458
https://gist.github.com/skygunner/daa96a2e5e00e8d6303c5ea1693a6174
No response
rofi -show drun
run rofi -show drun choose dconf-editor and enter dconf-editor started, but rofi window is still on top for about 15 seconds then it will go away
should close after start dconf-editor
rofi window is still on top for about 15 seconds then it will go away
The text was updated successfully, but these errors were encountered:
hmm odd one..
If you disable that popup, rofi does not hang around. I wonder what hangs in the DBusActivation.
Sorry, something went wrong.
So if popup enabled, the activate callback timeouts
(process:753654): Modes.DRun-WARNING **: 07:28:37.199: error sending Open message to application: Timeout was reached
[DRun] Reduce DBus timeout to 1500ms add option to disable DBusActiva…
4287ff4
…table. Issue: #2077
Added option to disable DBusActivatable and reduced timeout to 1.5seconds.
DBusActivatable
No branches or pull requests
Rofi version (rofi -v)
1.7.7-dirty
Configuration
https://gist.github.com/skygunner/2bef40f2c171c996c80d36943af19458
Theme
https://gist.github.com/skygunner/daa96a2e5e00e8d6303c5ea1693a6174
Timing report
No response
Launch command
rofi -show drun
Step to reproduce
run rofi -show drun
choose dconf-editor and enter
dconf-editor started,
but rofi window is still on top for about 15 seconds then it will go away
Expected behavior
should close after start dconf-editor
Actual behavior
rofi window is still on top for about 15 seconds then it will go away
Additional information
Using wayland display server protocol
I've checked if the issue exists in the latest stable release
The text was updated successfully, but these errors were encountered: