GNU bug report logs - #34642
clipit cannot be started by awesomewm or rofi

Previous Next

Package: guix;

Reported by: Bradley Haggerty <bradigger <at> gmail.com>

Date: Sun, 24 Feb 2019 23:42:01 UTC

Severity: normal

To reply to this bug, email your comments to 34642 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#34642; Package guix. (Sun, 24 Feb 2019 23:42:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Bradley Haggerty <bradigger <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Sun, 24 Feb 2019 23:42:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Bradley Haggerty <bradigger <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: clipit cannot be started by awesomewm or rofi
Date: Sun, 24 Feb 2019 23:41:09 +0000
[Message part 1 (text/plain, inline)]
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.
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#34642; Package guix. (Sun, 24 Feb 2019 23:50:02 GMT) Full text and rfc822 format available.

Message #8 received at 34642 <at> debbugs.gnu.org (full text, mbox):

From: Bradley Haggerty <bradigger <at> gmail.com>
To: 34642 <at> debbugs.gnu.org
Date: Sun, 24 Feb 2019 23:49:14 +0000
[Message part 1 (text/plain, inline)]
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",
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#34642; Package guix. (Mon, 25 Feb 2019 00:05:02 GMT) Full text and rfc822 format available.

Message #11 received at 34642 <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: Bradley Haggerty <bradigger <at> gmail.com>
Cc: 34642 <at> debbugs.gnu.org
Subject: Re: bug#34642: clipit cannot be started by awesomewm or rofi
Date: Mon, 25 Feb 2019 01:04:05 +0100
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




Information forwarded to bug-guix <at> gnu.org:
bug#34642; Package guix. (Mon, 25 Feb 2019 00:11:02 GMT) Full text and rfc822 format available.

Message #14 received at 34642 <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <somebody <at> not-sent-or-endorsed-by.tobias.gr>
To: Bradley Haggerty <bradigger <at> gmail.com>
Cc: 34642 <at> debbugs.gnu.org
Subject: Re: bug#34642: clipit cannot be started by awesomewm or rofi
Date: Mon, 25 Feb 2019 01:10:51 +0100
Tobias Geerinckx-Rice wrote:
> 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




Information forwarded to bug-guix <at> gnu.org:
bug#34642; Package guix. (Mon, 25 Feb 2019 00:47:01 GMT) Full text and rfc822 format available.

Message #17 received at 34642 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Bradley Haggerty <bradigger <at> gmail.com>
Cc: 34642 <at> debbugs.gnu.org
Subject: Re: bug#34642: clipit cannot be started by awesomewm or rofi
Date: Sun, 24 Feb 2019 18:52:01 -0500
[Message part 1 (text/plain, inline)]
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.
[signature.asc (application/pgp-signature, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#34642; Package guix. (Mon, 25 Feb 2019 01:23:02 GMT) Full text and rfc822 format available.

Message #20 received at 34642 <at> debbugs.gnu.org (full text, mbox):

From: Bradley Haggerty <bradigger <at> gmail.com>
To: 34642 <at> debbugs.gnu.org
Date: Mon, 25 Feb 2019 01:21:44 +0000
[Message part 1 (text/plain, inline)]
Leo Famulari wrote:
> 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:
> 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:
>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.
[Message part 2 (text/html, inline)]

This bug report was last modified 6 years and 108 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.