bug#34642: clipit cannot be started by awesomewm or rofi

bug#34642: clipit cannot be started by awesomewm or rofi

[Bradley Haggerty]

[-- Attachment #1: Type: text/plain, Size: 378 bytes --]

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 #2: Type: text/html, Size: 428 bytes --]

bug#34642:

[Bradley Haggerty]

[-- Attachment #1: Type: text/plain, Size: 392 bytes --]

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 #2: Type: text/html, Size: 622 bytes --]

bug#34642: clipit cannot be started by awesomewm or rofi

[Leo Famulari]

[-- 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 --]

bug#34642: clipit cannot be started by awesomewm or rofi

[Tobias Geerinckx-Rice]

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

bug#34642: clipit cannot be started by awesomewm or rofi

[Tobias Geerinckx-Rice]

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

bug#34642:

[Bradley Haggerty]

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

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.

[-- Attachment #2: Type: text/html, Size: 1840 bytes --]