From: Mek101 <Mek101@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Snapper complains about locale and fails upon dbus fatal exception
Date: Wed, 09 Dec 2020 15:27:17 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27047@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
New issue by Mek101 on void-packages repository
https://github.com/void-linux/void-packages/issues/27047
Description:
### System
* xuname:
`Void 5.9.13_1 x86_64-musl AuthenticAMD uptodate rFFFF`
* package:
`snapper-0.8.14_1`
### Expected behavior
After enabling and ensuring that `snapperd` is running, `snapper` should run without errors.
### Actual behavior
Snapper complains about the locale, an issue that has already been reported 2 years ago but ignored #5212.
But most importantly, attempting to run snapper results in a fatal exception, which makes the program unusable.
Running `snapper`:
```
[mek101@home-server ~]$ snapper -c public_storage create-config /mountpoints/public_storage/
Failed to set locale. Fix your system.
Failure (dbus fatal exception)
[mek101@home-server ~]$
```
Running `snapperd`:
```
[mek101@home-server ~]$ snapperd
terminate called after throwing an instance of 'DBus::FatalException'
what(): dbus fatal exception
Aborted
[mek101@home-server ~]$
```
### Steps to reproduce the behavior
Install the `snapper` package and run any command
next reply other threads:[~2020-12-09 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 14:27 Mek101 [this message]
2020-12-09 14:48 ` ericonr
2020-12-09 14:51 ` Mek101
2020-12-09 14:59 ` ericonr
2020-12-09 15:06 ` Mek101
2020-12-09 15:08 ` Mek101
2020-12-09 15:31 ` ericonr
2020-12-09 16:24 ` loreb
2020-12-09 16:48 ` Mek101
2020-12-09 16:54 ` loreb
2020-12-09 17:36 ` ericonr
2020-12-10 13:36 ` ericonr
2020-12-10 13:36 ` [ISSUE] [CLOSED] " ericonr
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27047@inbox.vuxu.org \
--to=mek101@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).