[Bug 1990202] New: [abrt] ibus-m17n: g_utf8_strreverse():
ibus-engine-m17n killed by SIGABRT
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1990202
Bug ID: 1990202
Summary: [abrt] ibus-m17n: g_utf8_strreverse():
ibus-engine-m17n killed by SIGABRT
Product: Fedora
Version: 34
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:55ebb818a96b7b57242b05abd0f67514030ac5e2;VAR
IANT_ID=workstation;
Component: ibus-m17n
Assignee: pnemade(a)redhat.com
Reporter: shashikasaragodu(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
pnemade(a)redhat.com, shawn.p.huang(a)gmail.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-m17n-1.4.6-1.fc34
Additional info:
reporter: libreport-2.15.2
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@x11.service
cmdline: /usr/libexec/ibus-engine-m17n --ibus
crash_function: g_utf8_strreverse
executable: /usr/libexec/ibus-engine-m17n
journald_cursor:
s=24fbbc8f54814a67a7d65307f7888094;i=185f2;b=703f0e9ddd994301ae764fe90af9cb12;m=343710d9a;t=5c8be884a8db5;x=62265b6f61ade350
kernel: 5.13.6-200.fc34.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 11 months
[Bug 2014772] New: [abrt] ibus-table: find_handle(): python3.9
killed by SIGSEGV
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2014772
Bug ID: 2014772
Summary: [abrt] ibus-table: find_handle(): python3.9 killed by
SIGSEGV
Product: Fedora
Version: 34
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:a1aaed42743edcb20fa65dfd10f7946d9c9d2615;VAR
IANT_ID=workstation;
Component: ibus-table
Assignee: mfabian(a)redhat.com
Reporter: lewishyu(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
kent.neo(a)gmail.com, mfabian(a)redhat.com,
pwu(a)redhat.com, shawn.p.huang(a)gmail.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-table-1.14.0-1.fc34
Additional info:
reporter: libreport-2.15.2
backtrace_rating: 4
cmdline: /usr/bin/python3 /usr/share/ibus-table/engine/main.py --ibus
crash_function: find_handle
executable: /usr/bin/python3.9
journald_cursor:
s=86c99b90f3ed4a11b6df8b4f3542d7d8;i=61fc4;b=be894692b3f44bf2884a19bc20e887d4;m=49581abf59;t=5cc043c86df83;x=4e68f27cc237fe20
kernel: 5.3.11-100.fc29.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 find_handle at ../src/pipewire/pipewire.c:315
#1 pw_unload_spa_handle at ../src/pipewire/pipewire.c:328
#2 pw_impl_node_destroy at ../src/pipewire/impl-node.c:1764
#3 pw_stream_disconnect at ../src/pipewire/stream.c:1844
#5 proxy_core_removed at ../src/pipewire/core.c:210
#7 pw_proxy_remove at ../src/pipewire/proxy.c:281
#8 pw_core_disconnect at ../src/pipewire/core.c:491
#9 pw_context_destroy at ../src/pipewire/context.c:493
#10 snd_pcm_pipewire_free at ../pipewire-alsa/alsa-plugins/pcm_pipewire.c:149
#11 snd_pcm_pipewire_close at ../pipewire-alsa/alsa-plugins/pcm_pipewire.c:162
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2014772
1 year, 11 months
[Fedora-i18n-bugs] [Bug 1787124] New: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc killed by SIGABRT
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1787124
Bug ID: 1787124
Summary: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc
killed by SIGABRT
Product: Fedora
Version: 31
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:d88e523ce263f66e445a1a6f6cd666d77fad9e05;VAR
IANT_ID=matecompiz;
Component: mozc
Assignee: tagoh(a)redhat.com
Reporter: ryutaroh2006(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
robinlee.sysu(a)gmail.com, tagoh(a)redhat.com,
tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I don't know how or why ibuz-engine-mozc was killed by SIGABRT...
Version-Release number of selected component:
ibus-mozc-2.23.2815.102-8.fc31
Additional info:
reporter: libreport-2.11.3
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/dbus\x2d:1.2\x2dcom.redhat.imsettings.slice/dbus-:1.2-com.redhat.imsettings@0.service
cmdline: /usr/libexec/ibus-engine-mozc --ibus
crash_function: __fdelt_chk
executable: /usr/libexec/ibus-engine-mozc
journald_cursor:
s=4479f645f2da4f17afc9f9415d05055f;i=b7c0;b=a6e351a2ff374b38832aa98ebe9457dd;m=7e0bcb9b;t=59afce7bb1367;x=508717657a4cb7e9
kernel: 5.3.16-300.fc31.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (4 frames)
#6 __fdelt_chk at fdelt_chk.c:25
#7 mozc::(anonymous namespace)::IsWriteTimeout at ../../ipc/unix_ipc.cc:108
#8 mozc::(anonymous namespace)::SendMessage at ../../ipc/unix_ipc.cc:157
#9 mozc::IPCClient::Call at ../../ipc/unix_ipc.cc:328
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 11 months
[Bug 2011130] New: [abrt] ibus-mozc:
__gnu_cxx::__verbose_terminate_handler()(): ibus-engine-mozc killed by
SIGABRT
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2011130
Bug ID: 2011130
Summary: [abrt] ibus-mozc:
__gnu_cxx::__verbose_terminate_handler()():
ibus-engine-mozc killed by SIGABRT
Product: Fedora
Version: 34
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:f003f9842f924762d98c734b478bf77d21a0e328;VAR
IANT_ID=matecompiz;
Component: mozc
Assignee: tagoh(a)redhat.com
Reporter: buribullet(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
robinlee.sysu(a)gmail.com, tagoh(a)redhat.com,
tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
1. Launch RStudio (rstudio-desktop-1.4.1717-2.fc34.x86_64)
2. Open new Rmd
3. Turn ibus-mozc on and Enter multilingual texts like Japanese hiragana.
Then, ibus-mozc dies with SEGV at mozc::ibus::(anonymous
namespace)::GetSurroundingText(_IBusEngine*,
mozc::ibus::SelectionMonitorInterface*, mozc::ibus::(anonymous
namespace)::SurroundingTextInfo*) [clone .part.0] [clone .constprop.0]
(engine=<optimized out>,
Version-Release number of selected component:
ibus-mozc-2.25.4190.102-5.fc34
Additional info:
reporter: libreport-2.15.2
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-com.redhat.imsettings@0.service
cmdline: /usr/libexec/ibus-engine-mozc --ibus
crash_function: __gnu_cxx::__verbose_terminate_handler()
executable: /usr/libexec/ibus-engine-mozc
journald_cursor:
s=56ad17da12da4eed800e68e166be00cd;i=7b37d1;b=f5aaea975c544d17b3b8f1ab25b1ec94;m=113dfa89293;t=5cd7162a6a7c5;x=5d0f1fdfb0e35252
kernel: 5.13.12-200.fc34.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#2 __gnu_cxx::__verbose_terminate_handler() at
../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#3 __cxxabiv1::__terminate(void (*)()) at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48
#4 std::terminate() at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:58
#5 __cxxabiv1::__cxa_throw(void*, std::type_info*, void (*)(void*)) at
../../../../libstdc++-v3/libsupc++/eh_throw.cc:95
#6 std::__throw_length_error(char const*) at
../../../../../libstdc++-v3/src/c++11/functexcept.cc:82
#7 std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::_M_check_length(unsigned long, unsigned long, char
const*) const at /usr/include/c++/11/bits/basic_string.h:323
#8 std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::_M_replace(unsigned long, unsigned long, char const*,
unsigned long) at /usr/include/c++/11/bits/basic_string.tcc:452
#9 std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::replace(unsigned long, unsigned long, char const*,
unsigned long) at /usr/include/c++/11/bits/basic_string.h:1946
#10 std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::replace(__gnu_cxx::__normal_iterator<char const*,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
>, __gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >,
__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >,
__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >) at
/usr/include/c++/11/bits/basic_string.h:2168
#11 std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::assign<__gnu_cxx::__normal_iterator<char const*,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
>, void>(__gnu_cxx::__normal_iterator<char const*,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
>, __gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >) at
/usr/include/c++/11/bits/basic_string.h:1478
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2011130
1 year, 11 months
[Fedora-i18n-bugs] [Bug 1899794] New: Fails to run on KDE in Rawhide
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1899794
Bug ID: 1899794
Summary: Fails to run on KDE in Rawhide
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: system-config-language
Severity: high
Assignee: pnemade(a)redhat.com
Reporter: awilliam(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, nav007(a)gmail.com,
pnemade(a)redhat.com, psatpute(a)redhat.com
Target Milestone: ---
Classification: Fedora
In current Rawhide, system-config-language is installed on KDE out of the box,
but fails to run. Running from a console, after you are prompted for the root
password, you get these errors:
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused
(system-config-language.py:2146): Gtk-WARNING **: 18:09:41.831: cannot open
display: :1
then it exits back to the console.
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 11 months
[Bug 2001332] New: pango-view with --backend=ft2 and
---antialias=none generates antialiased renderings
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2001332
Bug ID: 2001332
Summary: pango-view with --backend=ft2 and ---antialias=none
generates antialiased renderings
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Severity: high
Assignee: pwu(a)redhat.com
Reporter: andre.maute(a)gmx.de
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, 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
Created attachment 1820649
--> https://bugzilla.redhat.com/attachment.cgi?id=1820649&action=edit
image showing the problem
Description of problem:
Hello Fedora Team,
I have a recently updated Fedora 34 installation.
The problem I want to report is that it looks like
the pango-view tool is always turning antialiasing on
when one uses the FreeType backend --backend=ft2,
even when one explicitly switches antialiasing off with --antialias=none,
whereas it works for the --backend=cairo option.
A second question would be if the FreeType backend
generally doesn't/can't support --antialias=none?
I tried to find some examples in C with antialising turned off
but I wasn't successful.
I must confess I didn't check other distributions.
As pango-view is regarded as a tool for creating minimal reproducers
against the font rendering stack, I dare to set the severity to 'high' :-)
Best Regards
Andre
Version-Release number of selected component (if applicable):
$ uname -a
Linux localhost.localdomain 5.13.13-200.fc34.x86_64 #1 SMP Thu Aug 26 17:06:39
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ dnf list installed | grep dejavu
dejavu-lgc-sans-fonts.noarch 2.37-16.fc34
@fedora
dejavu-lgc-sans-mono-fonts.noarch 2.37-16.fc34
@fedora
dejavu-lgc-serif-fonts.noarch 2.37-16.fc34
@fedora
dejavu-sans-fonts.noarch 2.37-16.fc34
@fedora
dejavu-sans-mono-fonts.noarch 2.37-16.fc34
@fedora
dejavu-serif-fonts.noarch 2.37-16.fc34
@fedora
$ dnf list installed | grep ImageMagick
ImageMagick.x86_64 1:6.9.11.27-3.fc34
@fedora
ImageMagick-libs.x86_64 1:6.9.11.27-3.fc34
@fedora
$ dnf list installed | grep pango
pango.i686 1.48.9-2.fc34
@updates
pango.x86_64 1.48.9-2.fc34
@updates
pango-devel.x86_64 1.48.9-2.fc34
@updates
pangomm.x86_64 2.46.1-1.fc34
@updates
$ dnf list installed | grep freetype
freetype.i686 2.10.4-3.fc34
@fedora
freetype.x86_64 2.10.4-3.fc34
@fedora
freetype-devel.x86_64 2.10.4-3.fc34
@fedora
$ dnf list installed | grep fontconfig
fontconfig.i686 2.13.94-2.fc34
@updates
fontconfig.x86_64 2.13.94-2.fc34
@updates
fontconfig-devel.x86_64 2.13.94-2.fc34
@updates
$ dnf list installed | grep cairo
cairo.i686 1.17.4-3.fc34
@fedora
cairo.x86_64 1.17.4-3.fc34
@fedora
cairo-devel.x86_64 1.17.4-3.fc34
@fedora
cairo-gobject.i686 1.17.4-3.fc34
@fedora
cairo-gobject.x86_64 1.17.4-3.fc34
@fedora
cairomm.x86_64 1.14.2-8.fc34
@fedora
python2-cairo.x86_64 1.18.2-8.fc34
@fedora
python3-cairo.x86_64 1.20.0-2.fc34
@fedora
How reproducible:
Always
Steps to Reproduce:
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=none
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-none.png
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=gray
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-gray.png
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=subpixel
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-subpixel.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=none
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-none.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=gray
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-gray.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=subpixel
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-subpixel.png
$ gimp abc-*.png
Actual results:
Attached pngs.
The file abc-ft2-aa-none.png is in gray-scale and not as expected in
black-white.
The file abc-cairo-aa-none.png is in black-white as expected.
Expected results:
I would have expected the files abc*--aa-none.png looking near identical.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 11 months
[Bug 2021366] New: Nimbus Mono PS font should not fc-match Courier,
as certain letter combinations are not monospaced
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2021366
Bug ID: 2021366
Summary: Nimbus Mono PS font should not fc-match Courier, as
certain letter combinations are not monospaced
Product: Fedora
Version: 35
Hardware: x86_64
OS: Linux
Status: NEW
Component: Fonts
Assignee: i18n-bugs(a)lists.fedoraproject.org
Reporter: info(a)skierpage.com
QA Contact: fonts-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Created attachment 1840789
--> https://bugzilla.redhat.com/attachment.cgi?id=1840789&action=edit
look at "affiliation"
Description of problem:
I visited https://schema.org/Person in Firefox in Fedora 35 KDE spin and
noticed the monospace text "affiliation" was not monospaced; the letters "ffi"
were on top of each other as if replaced by the ligature ffi.
The page CSS is styling the <code> tag "font-family: Courier, monospace;", and
in Fedora 35 KDE Spin `fc-match Courier` returns
NimbusMonoPS-Regular.otf: "Nimbus Mono PS" "Regular"
indeed, if I set font-family to "Nimbus Mono PS" in some simple HTML
https://www.skierpage.com/bugs/nimbusmono_not_monospaced.html , other ff
combinations are also "ligature-ized".
I tried these two URLs in the chromium-browser package and in the Epiphany and
Konqueror browser flatpaks. These did not use "Nimbus Mono PS" as the fallback
font for font-family "Courier" so did not display "affiliation" badly on the
Person web page, but if you specify font-family "Nimbus Mono PS", you get the
ligature.
Version-Release number of selected component (if applicable):
Mozilla Firefox 94.0
urw-base35-fonts-20200910-9.fc35.src.rpm
How reproducible:
Always.
Steps to Reproduce:
1. Visit https://schema.org/Person and
https://www.skierpage.com/bugs/nimbusmono_not_monospaced.html in Firefox and
other browsers.
2. Note how "ffi" appears.
Actual results:
Firefox uses "Nimbus Mono PS" as the fallback for font-family Courier; all
these browsers replace "ffi" and such with the ligature character in "Nimbus
Mono PS", destroying the desired monospace effect.
Expected results:
Monospaced fonts should appear... monospaced, so every character should occupy
the same amount of horizontal space. However, if a font provides ligature
glyphs for "ffi" and such, then it's unclear if it's wrong for the browser to
use them; (l33t developers now explicitly use monospaced coding fonts that do
wacky substitutions.)
So the fix could be for Firefox and/or fc-match to _not_ use Nimbus Mono PS
when text handling requests Courier. The other browsers on my system don't,
I'm not sure why. Another could be to remove the ligatures from Nimbus Mono PS.
Additional info:
The rendering of code on that page (see attachment) is pretty terrible, note
the oversized 'd's in "address". Another reason to have Courier match some
other monospaced font than Nimbus Mono PS.
You can use the Fontmatrix program to enable OpenType features; checking latn >
dflt > liga changes the display of "ff" combinations.
Firefox using ligatures in monospaced fonts is
https://bugzilla.mozilla.org/show_bug.cgi?id=384395 , was closed WONTFIX "We
can't really do anything about it -- the underlying text system is doing the
ligaturization, not us".
ArchLinux users discussed the problem in
https://bbs.archlinux.org/viewtopic.php?id=238832
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2021366
2 years
[Bug 2015628] New: No entry /sys/class/leds for Fn 5 key that
toggles keyboard backlight
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2015628
Bug ID: 2015628
Summary: No entry /sys/class/leds for Fn 5 key that toggles
keyboard backlight
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: eb30750(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.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: Keyboard backlight worked until upgrading to FC34. The
Fn 5 key toggled the keyboard backlight on and off. In researching the new
method to expose the Fn keys to the user I found that there is no input/input5.
The input/input3 is configured.
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::capslock ->
../../devices/platform/i8042/serio0/input/input3/input3::capslock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::numlock ->
../../devices/platform/i8042/serio0/input/input3/input3::numlock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::scrolllock ->
../../devices/platform/i8042/serio0/input/input3/input3::scrolllock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 phy0-led ->
../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/leds/phy0-led
Version-Release number of selected component (if applicable):
5.14.11-200.fc34.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
A script or kernel option that builds the /sys/class/leds/input/input5
hierarchy.
Additional info:
If the input5 exists then simply changing the brightness value should turn on
the keyboard backlight.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2015628
2 years
[Fedora-i18n-bugs] [Bug 1903877] New: kde-l10n-pa missing translated file
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1903877
Bug ID: 1903877
Summary: kde-l10n-pa missing translated file
Product: Fedora
Version: 33
Status: NEW
Component: kde-l10n
Keywords: i18n
Assignee: than(a)redhat.com
Reporter: aalam(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
kde-sig(a)lists.fedoraproject.org, me(a)dvratil.cz,
rdieter(a)gmail.com, smparrish(a)gmail.com,
than(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1735891
--> https://bugzilla.redhat.com/attachment.cgi?id=1735891&action=edit
KDE system Tray (software, Keyboard Indicator)
Description of problem:
Version-Release number of selected component (if applicable):
kde-l10n-pa-17.08.3-9.fc33.noarch
apper-1.0.0-6.fc32.x86_64
How reproducible:
every time
Steps to Reproduce:
1. translation is not available for various KDE packages
2.rpm -q kde-l10n-pa -l|grep apper||grep
rpm -q kde-l10n-pa -l|grep kdeplasma
3.
Actual results:
applications are untranslated. Various untranslated section on KDE desktop in
Punjabi
No output for file search
Expected results: 4 following files
apper._desktop_.po
apper.po
org.kde.apper.appdata.po
plasma_applet_org.packagekit.updater.po
Additional info:
KDE svn source has apper fully transalted files for Punjabi since 2011:
https://websvn.kde.org/trunk/l10n-kf5/pa/messages/apper/
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years