From: Leo Famulari <leo@famulari.name>
To: Bradley Haggerty <bradigger@gmail.com>
Cc: 34642@debbugs.gnu.org
Subject: bug#34642: clipit cannot be started by awesomewm or rofi
Date: Sun, 24 Feb 2019 18:52:01 -0500 [thread overview]
Message-ID: <20190224235201.GA7635@jasmine.lan> (raw)
In-Reply-To: <CABGw91fLk4Tdwo9NyL7uLa8U2t94tUymfukMFrp5ZZaTi2KcqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
On Sun, Feb 24, 2019 at 11:41:09PM +0000, Bradley Haggerty wrote:
> After a recent update, clipit no longer starts with my wm session. I cannot
> launch it from rofi either. It has a tray icon and you can open a search
> with ctrl-alt-f, so it's easy to see when it's not running. I can launch it
> from a terminal, but I cannot close the terminal and keep it going. I tried
> running 'clipit &' and closing the shell, I tried using nohup. Doesn't work.
Can you give some details about how you are trying to start clipit with
your window manager session? We need information about your setup in
order to reproduce and disagnose the problem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-25 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 23:41 bug#34642: clipit cannot be started by awesomewm or rofi Bradley Haggerty
2019-02-24 23:49 ` bug#34642: Bradley Haggerty
2019-02-24 23:52 ` Leo Famulari [this message]
2019-02-25 0:04 ` bug#34642: clipit cannot be started by awesomewm or rofi Tobias Geerinckx-Rice
2019-02-25 0:10 ` Tobias Geerinckx-Rice
2019-02-25 1:21 ` bug#34642: Bradley Haggerty
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190224235201.GA7635@jasmine.lan \
--to=leo@famulari.name \
--cc=34642@debbugs.gnu.org \
--cc=bradigger@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).