clipit cannot be started by awesomewm or rofi

Open

Details

4 participants

Bradley Haggerty
Leo Famulari
Tobias Geerinckx-Rice
Tobias Geerinckx-Rice

Owner: unassigned

Submitted by: Bradley Haggerty

Severity: normal

Bradley Haggerty wrote on 25 Feb 2019 00:41

Recipients:(address . bug-guix@gnu.org)

Message-ID: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

Bradley Haggerty wrote on 25 Feb 2019 00:49

Recipients:(address . 34642@debbugs.gnu.org)

Message-ID: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

Tobias Geerinckx-Rice wrote on 25 Feb 2019 01:04

Recipients:(name . Bradley Haggerty)(address . bradigger@gmail.com)(address . 34642@debbugs.gnu.org)

Message-ID: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

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

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

Tobias Geerinckx-Rice wrote on 25 Feb 2019 01:10

Recipients:(name . Bradley Haggerty)(address . bradigger@gmail.com)(address . 34642@debbugs.gnu.org)

Message-ID: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

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

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

[2]:

https://github.com/CristianHenzel/ClipIt/commit/2c6e47b108b3dd7415c0c81b29201f1b9004e5cb

Leo Famulari wrote on 25 Feb 2019 00:52

Recipients:(name . Bradley Haggerty)(address . bradigger@gmail.com)(address . 34642@debbugs.gnu.org)

Message-ID: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.

Bradley Haggerty wrote on 25 Feb 2019 02:21

Recipients:(address . 34642@debbugs.gnu.org)

Message-ID: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

Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 34642@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it

mumi current 34642

Then, you may apply the latest patchset in this issue (with sign off)

mumi am -- -s

Or, compose a reply to this issue

mumi compose

Or, send patches to this issue

mumi send-email *.patch

is:open	open issues
is:done	closed issues
submitter:<who>	search issue submitter
author:<who>	search by message author
date:yesterday..now	search by issue date
mdate:3m..2d	search by message date