From: zimoun <zimon.toutoune@gmail.com>
To: ng0 <ng0@libertad.pw>
Cc: 25437-done@debbugs.gnu.org
Subject: bug#25437: awesome breaks on configuration reload
Date: Mon, 11 Jan 2021 13:32:32 +0100 [thread overview]
Message-ID: <86r1mru00v.fsf@gmail.com> (raw)
In-Reply-To: <861rg722go.fsf@gmail.com> (zimoun's message of "Thu, 03 Dec 2020 00:49:27 +0100")
Hi,
On Thu, 03 Dec 2020 at 00:49, zimoun <zimon.toutoune@gmail.com> wrote:
> This old bug #25437 is about issue with the Awesome Window Manager and
> the restart.
>
> <http://issues.guix.gnu.org/issue/25437>
>
> I have not read any recent user complaint about this. And because of…
>
> On Fri, 13 Jan 2017 at 15:19, ng0 <ng0@libertad.pw> wrote:
>
>> At the moment I can't provide logs.
>
> …and no news since more than 3 years, and in conjunction with the recent
> [1], if no one provides more, I am proposing to close it.
On Thu, 03 Dec 2020 at 00:58, zimoun <zimon.toutoune@gmail.com> wrote:
> This old bug #29276 is about Awesome Window Manager reload the config.
>
> <http://issues.guix.gnu.org/issue/29276>
>
>
> On Sun, 12 Nov 2017 at 22:24, ng0 <ng0@infotropique.org> wrote:
>> It's already an improvement from the last version
>> of awesome, but here's what I found just now (no logs):
>>
>> log in to awesome
>> press 'Control-Super-r'
>>
>> expected: reload awesome config
>> actual behavior: "login command not found" message before taking you to SLIM again.
>>
>> I'm not volunteering to fix this, I'm no longer using awesome :)
>
> Is it an issue for an AwesomeWM user? Otherwise, since it is 3 years
> old and not commented, I am proposing to close it.
So I am closing. If I have missed something, please reopen it.
All the best,
smon
prev parent reply other threads:[~2021-01-11 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 15:19 bug#25437: awesome breaks on configuration reload ng0
2020-12-02 23:49 ` zimoun
2021-01-11 12:32 ` zimoun [this message]
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=86r1mru00v.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=25437-done@debbugs.gnu.org \
--cc=ng0@libertad.pw \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).