bug#34616: neovim segfaults

2019-02-24 Thread Efraim Flashner
On Fri, Feb 22, 2019 at 06:11:52PM +0100, Ricardo Wurmus wrote: > > Julien Lepiller writes: > > > I think that's what you mean: > > > > Thread 2 "nvim" received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 0x76206700 (LWP 28664)] > > 0x779682ad in __strcmp_avx2 () fro

bug#34620: Acknowledgement (opam fails)

2019-02-24 Thread Julien Lepiller
Le 24 février 2019 08:43:47 GMT+01:00, Gabriel Hondet a écrit : >Hello, > >Wrapping works except that the binary can't find libraries, how can I >add the libraries of the profile (e.g. =asm/socket.h= or =crti.o=) in >the wrapper? The matter is to get the path of a profile (as if it was >a >packa

bug#34531: Guix profile fails on Overdrive 1000

2019-02-24 Thread Danny Milosavljevic
Final version attached. Works fine now. ;; -*- geiser-scheme-implementation: guile -*- ;;; Implementation: Danny Milosavljevic ;;; Based on: Implementation in Python by Vicent Marti. ;;; License: ISC, like the original generate.py in clar. (use-modules (ice-9 ftw)) (use-modules (ice-9 regex)) (

bug#34531: Guix profile fails on Overdrive 1000

2019-02-24 Thread Ricardo Wurmus
Danny Milosavljevic writes: > Final version attached. Works fine now. The loop looks a bit more complicated than it needs to be, I think. Did my version not work for you? -- Ricardo

bug#34531: Guix profile fails on Overdrive 1000

2019-02-24 Thread Danny Milosavljevic
Hi Ricardo, On Sun, 24 Feb 2019 12:45:34 +0100 Ricardo Wurmus wrote: > Danny Milosavljevic writes: > > > Final version attached. Works fine now. > > The loop looks a bit more complicated than it needs to be, I think. Did > my version not work for you? It did, but I wanted to make sure th

bug#34635: colord not reproducable

2019-02-24 Thread Danny Milosavljevic
On Sat, 23 Feb 2019 22:51:48 +0200 Efraim Flashner wrote: > it appears that colord isn't reproducable. diffoscope output attached icc files are generated by client/cd-create-profile.c . It uses GFile in order to write the file. Since GFile doesn't have a way to call utime, we would have to pat

bug#34630: slock: unable to disable OOM killer. Make sure to suid or sgid slock.

2019-02-24 Thread Leo Famulari
On Sun, Feb 24, 2019 at 04:28:35PM +1100, Carlo Zancanaro wrote: > None of the programs in the Guix store (ie. /gnu/store) will have setuid or > setgid set. On a Guix system you can install a slock screen-locker-service, > which will provide a setuid binary for slock (via the > setuid-program-servi

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

2019-02-24 Thread Bradley Haggerty
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 trie

bug#34642:

2019-02-24 Thread Bradley Haggerty
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:2

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

2019-02-24 Thread 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

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

2019-02-24 Thread 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/Clip

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

2019-02-24 Thread Leo Famulari
On Sun, Feb 24, 2019 at 11:41:09PM +, 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 >

bug#34642:

2019-02-24 Thread Bradley Haggerty
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 +f

bug#34630: slock: unable to disable OOM killer. Make sure to suid or sgid slock.

2019-02-24 Thread Matthew Brooks
Thanks for the info, and sorry for the trouble. This isn't actually a foreign distro, my OS declaration just doesn't use %desktop-services, so the automatic setuid handling wasn't there. Thanks to your info I was able to manually add slock to setuid-programs and it's working fine from /run/setui