8000 [BUG] rofi-calc crashes after typing first character when run from dwm keybind · Issue #2088 · davatorium/rofi · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
[BUG] rofi-calc crashes after typing first character when run from dwm keybind #2088
Open
@intael

Description

@intael

Rofi version (rofi -v)

Version: 1.7.8-dirty

Configuration

https://gist.github.com/intael/75adaa6d3904c88da89cf7d5bea4389e

Theme

https://gist.github.com/intael/735bc351098e80ab58a5aa8287610152

Timing report

No response

Launch command

rofi -modi calc -show calc -no-show-match -no-sort

Step to reproduce

The issue occurs when using this plugin: https://github.com/svenstaro/rofi-calc

Step 1: Define a dwm keybind like this:

static const char *roficalc[] = {"rofi", "-show", "calc", "-no-show-match", " -no-sort", NULL};
static const Key keys[] = { {MODKEY, XK_x, spawn, {.v = roficalc}} }

Step 2: Use the keybind. The rofi calc window will shut down after entering the first character.

Expected behavior

When pressing the key the roficalc window correctly appears, but it shuts down after pressing the first character.

Actual behavior

When I press the key, the rofi calc window appears but it shuts down after typing the first character. Looking at dwm's logs I see the following:

** (process:45348): WARNING **: 17:07:04.497: Mode 'calc' does not have a type set. Please update mode/plugin.

(process:45348): GLib-WARNING **: 17:07:05.263: ../glib/glib/gmain.c:5892: waitid(pid:45353, pidfd=10) failed: No child processes (10). See documentation of g_child_watch_source_new() for possible causes.

** (process:45348): ERROR **: 17:07:05.263: Process errored with: Child process exited abnormally

Additional information

The command works correctly when running it from the shell (zsh), but doesnt when run from a dwm keybind.

Using rofi-calc via AUR package rofi-calc-git r201.c54d8e7-1

Using wayland display server protocol

  • No, I don't use the wayland display server protocol

I've checked if the issue exists in the latest stable release

  • Yes, I have checked the problem exists in the latest stable version

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0