[Bug 2158744] New: Keyboard backlight doesn’t work
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2158744
Bug ID: 2158744
Summary: Keyboard backlight doesn’t work
Product: Fedora
Version: 37
Hardware: x86_64
OS: Linux
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: blake(a)mcbridemail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
negativo17(a)gmail.com, peter.hutterer(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I have an HP Envy Laptop, and I am using Fedora 37 Mate. The keyboard backlight
never lights up.
Version-Release number of selected component (if applicable): Fedora 37
Additional info:
```
[root@FAYE-HP ~]# uname -a
Linux FAYE-HP 6.0.16-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Dec 31 16:47:53
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
[root@FAYE-HP leds]# pwd
/sys/class/leds
[root@FAYE-HP leds]# ls -l
total 0
lrwxrwxrwx. 1 root root 0 Jan 5 16:13 input2::capslock ->
../../devices/platform/i8042/serio0/input/input2/input2::capslock
lrwxrwxrwx. 1 root root 0 Jan 5 16:13 input2::numlock ->
../../devices/platform/i8042/serio0/input/input2/input2::numlock
lrwxrwxrwx. 1 root root 0 Jan 5 16:13 input2::scrolllock ->
../../devices/platform/i8042/serio0/input/input2/input2::scrolllock
lrwxrwxrwx. 1 root root 0 Jan 5 16:16 phy0-led ->
../../devices/pci0000:00/0000:00:14.3/leds/phy0-led
[root@FAYE-HP phy0-led]# pwd
/sys/class/leds/phy0-led
[root@FAYE-HP phy0-led]# ls -l
total 0
-rw-r--r--. 1 root root 4096 Jan 5 16:18 brightness
lrwxrwxrwx. 1 root root 0 Jan 5 16:18 device -> ../../../0000:00:14.3
-r--r--r--. 1 root root 4096 Jan 5 16:18 max_brightness
drwxr-xr-x. 2 root root 0 Jan 5 16:18 power
lrwxrwxrwx. 1 root root 0 Jan 5 16:18 subsystem ->
../../../../../class/leds
-rw-r--r--. 1 root root 0 Jan 5 16:18 trigger
-rw-r--r--. 1 root root 4096 Jan 5 16:13 uevent
[root@FAYE-HP phy0-led]# cat brightness
1
```
None of this worked. Interestingly, the keyboard backlight works on Manjaro
Linux.
Any help would surely be appreciated!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2158744
10 months, 2 weeks
[Bug 2095164] New: Conversion region of ibus-anthy is invisible in
konsole, kwrite, kate
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2095164
Bug ID: 2095164
Summary: Conversion region of ibus-anthy is invisible in
konsole, kwrite, kate
Product: Fedora
Version: 36
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: mfabian(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1888253
--> https://bugzilla.redhat.com/attachment.cgi?id=1888253&action=edit
Video showing the the conversion region is visible in some places but
invisible in konsole, kwrite, kate
Using Fedora-Workstation-Live-x86_64-36-1.2.iso installed in qemu-kvm with all
current updates.
kwrite, kate, and konsole, do not show the conversion region when using
ibus-anthy
konsole5-22.04.1-1.fc36.x86_64
kwrite-22.04.1-1.fc36.x86_64
kate-21.12.2-1.fc36.x86_64
It does not matter whether these programs are used in
Plasma(X11), Plasma(Wayland), Gnome(Xorg), Gnome(Wayland), the behaviour is
always the same, the conversion region is never visible.
In konsole the behaviour is even worse because not even the cursor is shown at
the start of the conversion region.
When testing in Plasma(Wayland) or Plasma(X11) and typing with ibus-anthy into
the search field of the KDE control center, the conversion region is coloured
and thus visible. It is also visible when typing into the entry field for a
command which opens with Alt+F2. So there are only some programs in KDE where
it does not work like konsole, kwrite, kate, ... whereas it works in other
places.
See the attached video.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2095164
10 months, 2 weeks
[Bug 2154819] New: ibus fails to build with Python 3.12:
ModuleNotFoundError: No module named 'distutils'
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2154819
Bug ID: 2154819
Summary: ibus fails to build with Python 3.12:
ModuleNotFoundError: No module named 'distutils'
Product: Fedora
Version: rawhide
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: thrnciar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
mhroncok(a)redhat.com, shawn.p.huang(a)gmail.com,
tfujiwar(a)redhat.com, thrnciar(a)redhat.com
Blocks: 2135404 (PYTHON3.12)
Target Milestone: ---
Classification: Fedora
ibus fails to build with Python 3.12.0a3.
Traceback (most recent call last):
File "/usr/bin/g-ir-scanner", line 94, in <module>
from giscanner.utils import dll_dirs
File "/usr/lib64/gobject-introspection/giscanner/utils.py", line 355, in
<module>
import distutils.cygwinccompiler
ModuleNotFoundError: No module named 'distutils'
Remove the distutils package. It was deprecated in Python 3.10 by PEP 632
“Deprecate distutils module”. For projects still using distutils and cannot be
updated to something else, the setuptools project can be installed: it still
provides distutils. (Contributed by Victor Stinner in gh-92584.)
If your package is listed in [0], you may workaround this issue by
BuildRequiring python-setuptols, note that adding such BuildRequires might
however hide some transitive dependency problem, if the distutils import comes
from a dependency.
Cooperation with upstream is recommended. Additional context [1].
[0]
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedorapr...
[1]
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedorapr...
https://docs.python.org/3.12/whatsnew/3.12.html
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.12/fedora...
For all our attempts to build ibus with Python 3.12, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.12/package/ibus/
Testing and mass rebuild of packages is happening in copr. You can follow these
instructions to test locally in mock if your package builds with Python 3.12:
https://copr.fedorainfracloud.org/coprs/g/python/python3.12/
Let us know here if you have any questions.
Python 3.12 is planned to be included in Fedora 39. To make that update
smoother, we're building Fedora packages with all pre-releases of Python 3.12.
A build failure prevents us from testing all dependent packages (transitive
[Build]Requires), so if this package is required a lot, it's important for us
to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you
don't want to work on this now, let us know so we can try to work around it on
our side.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2135404
[Bug 2135404] Python 3.12
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2154819
10 months, 2 weeks
[Fedora-i18n-bugs] [Bug 1813728] New: Square four dot Unicode character has incorrect glyph
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1813728
Bug ID: 1813728
Summary: Square four dot Unicode character has incorrect glyph
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Severity: low
Assignee: pwu(a)redhat.com
Reporter: guillaumepoiriermorency(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The glyph for the Unicode "square four dot" character is incorrect.
Version-Release number of selected component (if applicable):
I think this problem arose when upgrading from Fedora 30 to Fedora 31.
How reproducible:
The simplest way is to start GNOME Characters Map and search for "square four
dot".
--
You are receiving this mail because:
You are on the CC list for the bug.
10 months, 3 weeks
[Bug 2119015] New: fontconfig-devel may require gettext-runtime
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2119015
Bug ID: 2119015
Summary: fontconfig-devel may require gettext-runtime
Product: Fedora
Version: rawhide
Status: NEW
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: suanand(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
pnemade(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
In F37 we moved the gettext runtime programs to gettext-runtime.
So assuming if fontconfig-devel does not require any translation
management tools (like msgcat or xgettext) at runtime,
it should be possible for it to only Requires: gettext-runtime
(instead of gettext). The goal here is only to install
gettext-runtime in the Fedora live image(s), etc.
Additional info:
https://fedoraproject.org/wiki/Changes/GettextRuntimeSubpackage
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2119015
10 months, 4 weeks
[Fedora-i18n-bugs] [Bug 1938251] New: update_preedit_text_with_mode(..., .., ..., IBus.PreeditFocusMode.COMMIT) doesn’t work in Gnome Wayland (works fine in Gnome Xorg)
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1938251
Bug ID: 1938251
Summary: update_preedit_text_with_mode(..., .., ...,
IBus.PreeditFocusMode.COMMIT) doesn’t work in Gnome
Wayland (works fine in Gnome Xorg)
Product: Fedora
Version: 34
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: mfabian(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
I installed Fedora-Workstation-Live-x86_64-34-20210308.n.0.iso into qemu.
Add the ibus-typing-booster input method in the Gnome control center and
also add the “Vietnamese (telex (m17n))” input method from ibus-m17n.
Both input methods use
update_preedit_text_with_mode(..., .., ..., IBus.PreeditFocusMode.COMMIT)
and this problem can be reproduced with either of them.
Open a gedit and a gnome-terminal.
Select ibus-typing-booster in the Gnome panel and type “test”.
The word “test” is underlined, indicating that it is in preedit and not yet
committed to gedit.
Now click on gnome-terminal to change the focus to gnome-terminal.
The string “test” vanishes from gedit. It should *not* vanish, it should
be committed i.e. the underline under “test” should vanish and the string
“test” should be in gedit.
Same problem with the Vietnamese (telex (m17n)) input method.
Select it in the Gnome panel.
Type “a” into gedit. The “a” is underlined because it is in preedit.
Click on gnome-terminal to change the focus to gnome-terminal.
The “a” vanishes. Here as well the “a” should be commited to gedit, i.e.
the underline should disappear and the “a” should remain in gedit.
--
You are receiving this mail because:
You are on the CC list for the bug.
11 months