all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Bradley Haggerty <bradigger@gmail.com>
Cc: 34642@debbugs.gnu.org
Subject: bug#34642: clipit cannot be started by awesomewm or rofi
Date: Mon, 25 Feb 2019 01:04:05 +0100	[thread overview]
Message-ID: <87zhqklone.fsf@nckx> (raw)
In-Reply-To: <CABGw91fLk4Tdwo9NyL7uLa8U2t94tUymfukMFrp5ZZaTi2KcqA@mail.gmail.com>

Bradley,

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.

I use clipit without issue… but I also never launch it in the 
background. :-)

It's hard to tell, but it might be this[0] upstream issue and 
might be fixed here[1].

Kind regards,

T G-R

[0]: https://github.com/CristianHenzel/ClipIt/issues/87
[1]: https://github.com/CristianHenzel/ClipIt/pull/109

  parent reply	other threads:[~2019-02-25  0:05 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 ` bug#34642: clipit cannot be started by awesomewm or rofi Leo Famulari
2019-02-25  0:04 ` Tobias Geerinckx-Rice [this message]
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

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

  git send-email \
    --in-reply-to=87zhqklone.fsf@nckx \
    --to=me@tobias.gr \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.