Github messages for voidlinux
 help / color / mirror / Atom feed
From: 123randomuser321 <123randomuser321@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Xfce's Whiskermenu crashes when using context menu
Date: Sat, 15 Feb 2020 22:00:27 +0100	[thread overview]
Message-ID: <20200215210027.QevSxcpLkTamyYsa2jKfQaRRHUAlYQPgFLscf4Kp_ZQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19075@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

Closed issue by 123randomuser321 on void-packages repository

https://github.com/void-linux/void-packages/issues/19075

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *Void 5.4.19_1 x86_64 AuthenticAMD uptodate rrrmFFFF*
* package:  
  *xfce4-whiskermenu-plugin-2.4.0_1*

### Expected behavior
Right-click on any program in whiskermenu to bring up its context menu. Then click on any __external__ option (i.e. Firefox's private window). The option should be executed correctly.
### Actual behavior
Instead of executing the selected option, whiskermenu crashes and (in most cases) Xfce complains and brings up a dialogue to either remove or restart it.
### Steps to reproduce the behavior
Add Whiskermenu to Xfce's panel.
Open it.
Right-click on anything that has an __external__option.
Select such an option.
Crash.

Note:
Why __external__?
When you select something like "add to desktop" or "add to panel", the crash __doesn't__ occur.


      parent reply	other threads:[~2020-02-15 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 16:10 [ISSUE] " voidlinux-github
2020-02-15 21:00 ` 123randomuser321
2020-02-15 21:00 ` 123randomuser321 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200215210027.QevSxcpLkTamyYsa2jKfQaRRHUAlYQPgFLscf4Kp_ZQ@z \
    --to=123randomuser321@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).