clipit cannot be started by awesomewm or rofi

  • Open
  • quality assurance status badge
Details
4 participants
  • Bradley Haggerty
  • Leo Famulari
  • Tobias Geerinckx-Rice
  • Tobias Geerinckx-Rice
Owner
unassigned
Submitted by
Bradley Haggerty
Severity
normal
B
B
Bradley Haggerty wrote on 25 Feb 2019 00:41
(address . bug-guix@gnu.org)
CABGw91fLk4Tdwo9NyL7uLa8U2t94tUymfukMFrp5ZZaTi2KcqA@mail.gmail.com
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.
Attachment: file
B
B
Bradley Haggerty wrote on 25 Feb 2019 00:49
(address . 34642@debbugs.gnu.org)
CABGw91dQuPKq1n5_nGN6KMPJ=FdFfN23b7XTYACacjtCBKaf0g@mail.gmail.com
forgot to attach guix version...
guix (GNU Guix) 13eb556f9f2b36aa729e63892a28b03b5235bf7b
clipit lacks a --version argument so I'm not entirely sure how to find its
version, but I updated yesterday.

I also get this warning but I've seen it for other programs and I don't
think it matters:
(clipit:2542): Gtk-WARNING **: 17:37:31.273: Unable to locate theme engine
in module_path:
"murrine",
Attachment: file
T
T
Tobias Geerinckx-Rice wrote on 25 Feb 2019 01:04
(name . Bradley Haggerty)(address . bradigger@gmail.com)(address . 34642@debbugs.gnu.org)
87zhqklone.fsf@nckx
Bradley,

Bradley Haggerty wrote:
Toggle quote (11 lines)
> 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

T
T
Tobias Geerinckx-Rice wrote on 25 Feb 2019 01:10
(name . Bradley Haggerty)(address . bradigger@gmail.com)(address . 34642@debbugs.gnu.org)
87y364loc4.fsf@nckx
Tobias Geerinckx-Rice wrote:
Toggle quote (4 lines)
> It's hard to tell, but it might be this[0] upstream issue and
> might be
> fixed here[1].

If so, it should be fixed upstream.

Are you comfortable building clipit from this[2] commit and
testing that?

Kind regards,

T G-R

[2]:
L
L
Leo Famulari wrote on 25 Feb 2019 00:52
(name . Bradley Haggerty)(address . bradigger@gmail.com)(address . 34642@debbugs.gnu.org)
20190224235201.GA7635@jasmine.lan
On Sun, Feb 24, 2019 at 11:41:09PM +0000, Bradley Haggerty wrote:
Toggle quote (6 lines)
> 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.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlxzLh4ACgkQJkb6MLrK
fwgNRBAAx5BOZGw6t9tFZk5j8JRhnHFcnd93hqYBvPpmEGi1zlyawsLO8LrKS4q5
mMJSSahqzSUKZkn1DY7gWfZG4KFui/NF3SVAVLxdVNyCD3K5LIRLgc0eMjzl6aPe
3KV3W6GNbal2P/LgEsp7lhYtdlgZS8CRDTxF/eGezKxu2DqC/DO6cfuQ/1ywm2Wx
u/BqKJHKAitNIGQX+f1+PtnZnh/WySzSCH18oEgDevWHZkLpllmdoRebO0Ecol5r
cL564OTxVE5NtYdzkQheOJwgtm6KvK99Fnq4CQ4FNeeiSQHBDZCDGUXvIFarX6rp
h8RxHbQIZx2/CNd1QKbIpXtp3xrW7JsfHhsnOEa2MG2HLgTKb6y21ulktm0l0rup
N+j6RqSaYzevAZFfW0YwvJN6htaGon8A7oSoJ9PS8a2lqMO2LGDzR5nfIhCgxokg
sT7iygKO0fFnPZg17jltRErkPOl8zPEjyyVipc1TCLN7eAZAnAqtoIb7l/fXzlbV
2dH4X0oTUNvCmEdnmJL3ulnxBItVG6SkMXg93TQOllu8OsBbWLR+FhYkhlzBLZzV
e4DhFSCCGcHckfYFl0tC9Yzc7CRVwOJaxrQ6wTpprM3f4FRytG4q2y9CKAmoupUt
PgMx0+N8T4vjcnVkRQaNIzrknpNniz6NO1BGUFbkgWQh7Eb9l2w=
=0FQk
-----END PGP SIGNATURE-----


B
B
Bradley Haggerty wrote on 25 Feb 2019 02:21
(address . 34642@debbugs.gnu.org)
CABGw91ea1LUGc=kvwKvwrT=q9fpQS8_iqhB3oZT49-e4qNccaQ@mail.gmail.com
Leo Famulari wrote:
Toggle quote (1 lines)
> Can you give some details about how you are trying to start clipit with
your window manager session?
Yes, here's is an excerpt from the end of my ~/.config/awesome/rc.lua file.
-- Startup applications
autorun = true
autorunApps =
{
"xset s off",
"xset -dpms",
"xset +fp /home/brad/.fonts",
"xset +fp $(dirname $(readlink -f
~/.guix-profile/share/fonts/truetype/fonts.dir))",
"xset fp rehash",
--"xrandr --output HDMI-2 --primary --mode 1920x1200 --pos 1200x0
--rotate normal --output HDMI-1 --off --output LVDS-1 --off --output VGA-1
--mode 1920x1200 --pos 0x0 --rotate left",
"mpd",
"mpdscribble",
"nm-applet",
"clipit",
"deluge-gtk",
}
if autorun then
for app = 1, #autorunApps do
awful.util.spawn(autorunApps[app])
end
end

The other way I tried to launch it was manually via the application
launcher called rofi. it is similar to dmenu.

Tobias Geerinckx-Rice wrote:
Toggle quote (2 lines)
> It's hard to tell, but it might be this[0] upstream issue

I agree, that issue sounds like what's happening here.

Tobias Geerinckx-Rice wrote:
Toggle quote (1 lines)
>Are you comfortable building clipit from this[2] commit and
testing that?
I'm afraid I'm not comfortable doing that. I have yet to do anything that
advanced with Guix, and I don't have much experience building things from
source in general.
Attachment: file
?