Github messages for voidlinux
 help / color / mirror / Atom feed
From: tuxslack <tuxslack@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Gedit 47.0 does not change the language to pt_BR
Date: Thu, 27 Jun 2024 06:29:43 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51022@inbox.vuxu.org> (raw)

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

New issue by tuxslack on void-packages repository

https://github.com/void-linux/void-packages/issues/51022

Description:
### Is this a new report?

Yes

### System Info

Void Linux kernel 6.6.35_1 x86_64

### Package(s) Affected

gedit 47.0 

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

gedit 47.0 does not change the language to pt_BR

Problem starts after updating in void linux


$ xbps-query -i gedit 
architecture: x86_64
changelog: https://gitlab.gnome.org/GNOME/gedit/-/raw/47.0/NEWS
filename-sha256: 80e8fcc131dd18f0631de7b4384bc044ae0921f9869d69757c028963a36b463b
filename-size: 2181KB
homepage: https://wiki.gnome.org/Apps/Gedit
install-date: 2024-06-26 23:17 -03
install-script: 1302B
installed_size: 12MB
license: GPL-2.0-or-later
maintainer: Orphaned <orphan@voidlinux.org>
metafile-sha256: a7c0ccd08fdc080e9c23c5b927c9823357fa7399c3c954dabe39a1105336cb33
pkgname: gedit
pkgver: gedit-47.0_1
remove-script: 1416B
repository: https://repo-default.voidlinux.org/current
run_depends:
	desktop-file-utils>=0
	gsettings-desktop-schemas>=0
	iso-codes>=0
	glib>=2.80.0_1
	gtk+3>=3.0.0_1
	pango>=1.24.0_1
	libgedit-tepl>=6.10.0_1
	libpeas>=1.0.0_2
	glibc>=2.39_1
	gdk-pixbuf>=2.22.0_1
	libgedit-gtksourceview>=299.2.1_1
	gspell>=1.8.0_1
	cairo>=1.8.6_1
	libgedit-amtk>=5.8.0_1
	libgedit-gfls>=0.1.0_1
	libgirepository>=1.30_1
shlib-provides:
	libgedit-47.so
shlib-requires:
	libc.so.6
	libcairo.so.2
	libgdk-3.so.0
	libgdk_pixbuf-2.0.so.0
	libgedit-amtk-5.so.0
	libgedit-gfls-1.so.0
	libgedit-gtksourceview-300.so.1
	libgedit-tepl-6.so.0
	libgio-2.0.so.0
	libgirepository-1.0.so.1
	libglib-2.0.so.0
	libgobject-2.0.so.0
	libgspell-1.so.2
	libgtk-3.so.0
	libm.so.6
	libpango-1.0.so.0
	libpeas-1.0.so.0
	libpeas-gtk-1.0.so.0
short_desc: Text editor for GNOME
source-revisions: gedit:d690dc78d25
state: installed




$ locale -a
C
C.utf8
POSIX
en_US.utf8
pt_BR.utf8


$ locale 
LANG=pt_BR.UTF-8
LC_CTYPE="pt_BR.UTF-8"
LC_NUMERIC="pt_BR.UTF-8"
LC_TIME="pt_BR.UTF-8"
LC_COLLATE=C
LC_MONETARY="pt_BR.UTF-8"
LC_MESSAGES="pt_BR.UTF-8"
LC_PAPER="pt_BR.UTF-8"
LC_NAME="pt_BR.UTF-8"
LC_ADDRESS="pt_BR.UTF-8"
LC_TELEPHONE="pt_BR.UTF-8"
LC_MEASUREMENT="pt_BR.UTF-8"
LC_IDENTIFICATION="pt_BR.UTF-8"
LC_ALL=


### Expected behaviour

Gedit is in Brazilian Portuguese.

Currently, even changing it to pt_BR it returns to en in Gedit.

### Actual behaviour

When opening Gedit it does not identify the system language. It is always in English.

Even changing gedit to pt_BR.UTF-8 doesn't work.

### Steps to reproduce

$ gedit

             reply	other threads:[~2024-06-27  4:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27  4:29 tuxslack [this message]
2024-06-27  6:15 ` classabbyamp
2024-07-01 12:39 ` tuxslack
2024-07-01 13:00 ` classabbyamp

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-51022@inbox.vuxu.org \
    --to=tuxslack@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).