From: "Pierre-Henry F." <contact@phfrohring.com>
To: "ludo@gnu.org" <ludo@gnu.org>
Cc: "help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: Re: Guix, Rofi, i3wm and Locales
Date: Wed, 17 Oct 2018 19:29:43 +0000 [thread overview]
Message-ID: <LZuALIG96t_94B7GHmqEJhpW0roShDZZTTKjw-M6aDYPco1eFhp7ICbC4MKyLcn7Q-JvTwszJ2Zo0Fp-dfgpLgKpz1EJtu81pOXF_SMo5aM=@phfrohring.com> (raw)
In-Reply-To: <87woqgdb4j.fsf@gnu.org>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, October 17, 2018 2:13 PM, <ludo@gnu.org> wrote:
> Hi,
>
> "Pierre-Henry F." contact@phfrohring.com skribis:
>
> > > Concretely, if you explicitly run ~/.guix-profile/bin/rofi, what
> > > happens? Does it print warnings about locale issues?
> >
> > I replaced things in the calling script:
> > #! /usr/bin/env bash
> > ~/.guix-profile/bin/rofi -combi-modi window,drun,run -theme solarized -font 'hack 10' -show combi -modi combi
> > And... nothing happens!
>
> You mean you no longer get the warning issues? (I was suggesting running
> the command directly at the prompt rather than in a script, to make sure
> nothing is interfering.)
I did and it works fine from the command line...
The problem occurs only when the script is triggered from the i3 shortcut.
i3 was not installed from Guix... I will try to install i3 with Guix and try
again.
Below is all I have on this bug so far:
# Guix
```
$ guix --version
guix (GNU Guix) 2ab321ca37d1c00c1540d78d587226d3d487b2d4
Copyright (C) 2018 the Guix authors
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
```
```
$ guix package -i glibc-utf8-locales
The following package will be upgraded:
glibc-utf8-locales 2.27 → 2.27 /gnu/store/mbns811n696fl7g060cx6jqjh75mlj8i-glibc-utf8-locales-2.27
14 packages in profile
```
```
$ echo $GUIX_LOCPATH
/home/phf/.guix-profile/lib/locale
```
```
$ guix package -I rofi
rofi 1.5.1 out /gnu/store/4g9m8lv9bqpcb7k4rvscyb7g5yga8zq2-rofi-1.5.1
```
# Rofi
```
$ rofi -v
Version: 1.5.1
```
rofi configuration: https://gist.github.com/phfrohring/237f89df2b2e2a7f25e5a01bf2549729
From: `$ G_MESSAGES_DEBUG=all /home/phf/.guix-profile/bin/rofi -combi-modi window,drun,run,ssh -theme solarized -font 'hack 10' -show combi -modi combi &> ~/rofi_logs/rofi_$(date +'%F-%k-%M-%S')`
To: [Logs](https://gist.github.com/phfrohring/a6d68a007377e8f1f2de73a6cb69583e)
But the logs becomes:
`(process:12536): Rofi-WARNING **: 21:08:53.715: Failed to set locale.`
when called using the i3 shortcut `$mod+d` that calls the `trigger_rofi` script holding the line above: `$ G_MESSAGES …`
# i3
No compositor used.
```
$ i3 --moreversion 2>&-
Binary i3 version: 4.15 (2018-03-10) © 2009 Michael Stapelberg and contributors
Running i3 version: 4.15 (2018-03-10) (pid 1394)o abort…)
Loaded i3 config: /home/phf/.config/i3/config (Last modified: Thu 11 Oct 2018 09:03:19 PM CEST, 3547 seconds ago)
The i3 binary you just called: /usr/bin/i3
The i3 binary you are running: i3
```
relevant line of i3 config: `bindsym --release $mod+d exec ~/bin/./trigger_rofi`
content of `~/bin/./trigger_rofi`:
```
#! /usr/bin/env bash
rofi -combi-modi window,drun,run,ssh -theme solarized -font 'hack 10' -show combi -modi combi
```
```
$ i3-msg shmlog on; i3-msg debuglog on
[{"success":true}]
[{"success":true}]
# type the keybinding that should trigger rofi
$ i3-dump-log >~/i3_logs/i3log-$(date +'%F-%k-%M-%S') 2>&1
$ i3-msg shmlog off; i3-msg debuglog off
[{"success":true}]
[{"success":true}]
```
[log gist](https://gist.github.com/phfrohring/f5556e14499b49ceaa8e1ba0276638a9)
Lines of the log that shows the executed command that does not work properly:
```
13/10/2018 11:04:54 - commands_parser.c:parse_command:265 - COMMAND: *exec ~/bin/./trigger_rofi*
13/10/2018 11:04:54 - commands.c:cmd_criteria_init:155 - Initializing criteria, current_match = 0x561b103e8100
13/10/2018 11:04:54 - commands.c:cmd_exec:1235 - should execute ~/bin/./trigger_rofi, no_startup_id = 0
13/10/2018 11:04:54 - startup id = i3/~|bin|.|trigger_rofi/1388-56-f02c_TIME27690841
13/10/2018 11:04:54 - executing: ~/bin/./trigger_rofi
```
# Linux distribution
```
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
```
# Steps to reproduce
typing `$mod+d` won't trigger rofi.
# What behaviour you see
Nothing.
# What behaviour you expect to see
The same behaviour as when I execute: `$ ~/bin/./trigger_rofi` i.e. rofi to show up.
Many thanks!
PH
next prev parent reply other threads:[~2018-10-17 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 11:08 Guix, Rofi, i3wm and Locales Pierre-Henry F.
2018-10-15 12:13 ` Ludovic Courtès
2018-10-15 22:00 ` Pierre-Henry F.
2018-10-16 11:47 ` Ludovic Courtès
2018-10-16 12:03 ` Pierre-Henry F.
2018-10-17 12:13 ` Ludovic Courtès
2018-10-17 19:29 ` Pierre-Henry F. [this message]
2018-10-24 14:13 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='LZuALIG96t_94B7GHmqEJhpW0roShDZZTTKjw-M6aDYPco1eFhp7ICbC4MKyLcn7Q-JvTwszJ2Zo0Fp-dfgpLgKpz1EJtu81pOXF_SMo5aM=@phfrohring.com' \
--to=contact@phfrohring.com \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).