https://bugzilla.redhat.com/show_bug.cgi?id=2361916
Bug ID: 2361916
Summary: [abrt] imsettings: g_malloc0_n(): imsettings-daemon
killed by SIGTRAP
Product: Fedora
Version: 42
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:8b8d4cb79153aa86bf5c71a5a74b459e4bd8183c;VAR
IANT_ID=cosmic;
Component: imsettings
Assignee: tagoh(a)redhat.com
Reporter: varunrajvj79(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Version-Release number of selected component:
imsettings-1.8.10-2.fc42
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: imsettings-daemon killed by SIGTRAP
journald_cursor:
s=c6bd9352fa734f5297f51e606d1a9e71;i=3915;b=faf40bff69234be1b4df0f4eee99aafe;m=83e92f0;t=6334cdc4f1aef;x=59f4f4a7cc2b347f
executable: /usr/libexec/imsettings-daemon
cmdline: /usr/libexec/imsettings-daemon
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-dbus\x2d:1.2\x2dcom.redhat.imsettings.slice/dbus-:1.2-com.redhat.imsettings@0.service
rootdir: /
uid: 1000
kernel: 6.14.2-300.fc42.x86_64
package: imsettings-1.8.10-2.fc42
runlevel: N 5
backtrace_rating: 4
crash_function: g_malloc0_n
comment:
Truncated backtrace:
Thread no. 1 (9 frames)
#3 g_malloc0_n at ../glib/gmem.c:433
#4 _start_process at
/usr/src/debug/imsettings-1.8.10-2.fc42.x86_64/imsettings-daemon/imsettings-proc.c:351
#5 _start_main_process at
/usr/src/debug/imsettings-1.8.10-2.fc42.x86_64/imsettings-daemon/imsettings-proc.c:272
#6 imsettings_proc_spawn at
/usr/src/debug/imsettings-1.8.10-2.fc42.x86_64/imsettings-daemon/imsettings-proc.c:716
#7 imsettings_server_cb_switch_im at
/usr/src/debug/imsettings-1.8.10-2.fc42.x86_64/imsettings-daemon/imsettings-server.c:921
#8 imsettings_server_bus_method_call at
/usr/src/debug/imsettings-1.8.10-2.fc42.x86_64/imsettings-daemon/imsettings-server.c:1277
#9 call_in_idle_cb at ../gio/gdbusconnection.c:5476
#12 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249
#13 g_main_context_iterate_unlocked at ../glib/gmain.c:4314
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2361916
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2323789
Bug ID: 2323789
Summary: The word "Favorites" appears as a candidate in emojier
when pressed!
Product: Fedora
Version: 41
OS: Linux
Status: NEW
Component: ibus
Keywords: Regression
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Manish and I discovered this bug in emojier last week while testing.
Reproducible: Always
Steps to Reproduce:
0. Open gnome-text-editor
1. Start emojier by pressing Super+Period Space
2. Click on Favorites category
Actual Results:
The word "Favorites" is listed as an emoji candidate in the grid!
Expected Results:
"Favorites" should not be listed as a favorite emoji.
Does not seem to happen in current F40.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2323789
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2277345
Bug ID: 2277345
Summary: NotoSansMono[wght].ttf file name causes scripts with
failglob enabled to fail
Product: Fedora
Version: 40
Hardware: All
OS: Linux
Status: NEW
Component: google-noto-fonts
Severity: medium
Assignee: tagoh(a)redhat.com
Reporter: hartsjc(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
shopt failglob
If set, patterns which fail to match filenames during pathname expansion result
in an expansion error.
Using this feature is good practice in scripts as helps prevent scripting
mistakes; however, having file name with square brackets causes failures. And
with Fedora 40 upgrade seems
google-noto-sans-mono-vf-fonts-20240301-2.fc40.noarch has added one with:
/usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf
Reproducible: Always
Steps to Reproduce:
1. Causes globs that don't expand to cause errors
$ shopt -s failglob
2. Try use files from rpm as variable, and fail
$ for file in $(rpm -q --list google-noto-sans-mono-vf-fonts) ; do
[[ -f "/${file}" ]] || echo "${file}"
done
-bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf
3. Note the RC
$ echo $?
1
4. Or even command line
$ rpm -qf /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf
-bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf
$ rpm -qf '/usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf'
google-noto-sans-mono-vf-fonts-20240301-2.fc40.noarch
Actual Results:
-bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf
Expected Results:
no error accessing files with failglob shopt enabled
started fedora 40 upgrade, as daily script of mine fails because this file is
included in initramfs too.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2277345
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2368622
Bug ID: 2368622
Summary: ibus-daemon uses insane amounts of CPU and causes a
laggy experience
Product: Fedora
Version: 42
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Keywords: Desktop
Severity: high
Assignee: tfujiwar(a)redhat.com
Reporter: torvalds(a)linux-foundation.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Not a lot of details here, but I decided that instead of just fixing it with
killall ibus-daemon
which gets rid of that broken thing, I would at least open a bug report to see
if there is some official fix for this.
Google shows a lot of people complaining about this going back years, so it's
not me.
There's no crash, and no obvious system logs either. All I see in system logs
is gdm-wayland-session activating, and when I kill it systemd seems to log
consumtion information like
org.freedesktop.IBus.session.GNOME.service: Consumed 26min 22.196s CPU
time, 125.1M memory peak.
(That was after the system had been up for one day, so 26 min of CPU time seems
pretty excessive)
Reproducible: Sometimes
Steps to Reproduce:
1. Boot the system
2. Be happy
3. Some time randomly later, notice laggy behavior and ibus-daemon using 100%
CPU in top
Actual Results:
Slow keyboard response on a fast system
Expected Results:
Snappy action
Additional Information:
Sorry for the horrible bug report, but can we please just disable ibus-daemon
by default as a useless problem-causing thing?
When google shows this problem going back AT LEAST to 2020 (and probably
longer), with the solution invariably being "kill, restart or disable
ibus-daemon to fix the problem temporarily", why is that thing enabled by
default in the first place?
Please at least give a good setting for this, so that the answer can be for
people to not enable that thing.
And if somebody has "please debug this next time it happens by doing Xyz", I'll
happily do that. But you need to tell me what Xyz is, because I don't know the
first thing about ibus-daemon.
I know that the "i" is supposed to stand for "intelligent". But honestly, I can
come up with a lot better suggestions for what that "i" might stand for. And
absolutely *none* of them are polite.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2368622
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2397329
Bug ID: 2397329
Summary: ibus-typing-booster: Please build in Fedora 43
Product: Fedora
Version: 43
Status: NEW
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: ksurma(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Blocks: 2373702 (PYC3.14rc3)
Target Milestone: ---
Classification: Fedora
Dear package maintainer,
Due to reasons described in
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
a rebuild of ibus-typing-booster was needed in Fedora 43 and 44.
During the mass rebuild we built the package for Fedora 44, but the automation
determined that there was an existing build for Fedora 43, which was not tagged
to the main repository.
We didn't want to interfere with the plans you may have with the package, so we
ask you to rebuild the package for Fedora 43 once again, when it's convenient
to you.
Thank you. Let me know if you need help.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2373702
[Bug 2373702] Rebuild all packages with .pyc files with Python 3.14.0rc3+
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2397329
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2389767
Bug ID: 2389767
Summary: The brise package is deprecated upstream since 2018
and providing outdated data files for ibus-rime,
fcitx5-rime etc
Product: Fedora
Version: 42
OS: Linux
Status: NEW
Component: brise
Keywords: Desktop, RFE
Severity: medium
Assignee: pwu(a)redhat.com
Reporter: alt.euyis(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Per the readme file in the upstream repo
(https://github.com/rime/brise/blob/master/README.md) brise is deprecated and
the last release version of 0.38 dating back to 2018 is still being served as a
dependency package for Rime front-ends in Fedora (ibus-rime, fcitx5-rime, etc).
As the schema files in the package are essentially what actually provide the
user-facing input features of Rime, the fact that they are several years
outdated when newer, current version are available with updates & bug fixes are
readily available is clearly not ideal. In fact, this bug report is prompted by
me running into an upstream bug (https://github.com/rime/home/issues/831) that
was fixed all the way back to 2021 yet still present Fedora 42, due to the
schema files being stuck in 2018.
Would it be possible to either update the files provided by the brise package
to the latest versions available, or move them to a new dependency package for
Rime front-end packages, since a update version would clearly not be
specifically brise anymore so the name would be misleading in that case?
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2389767
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2319795
Bug ID: 2319795
Summary: Please branch and build translate-toolkit for EPEL 10
Product: Fedora
Version: rawhide
Status: NEW
Component: translate-toolkit
Assignee: petersen(a)redhat.com
Reporter: xavier(a)bachelot.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
petersen(a)redhat.com, sshil(a)redhat.com,
sundeep_anand(a)yahoo.com
Blocks: 2303880 (EPEL10Tracker)
Target Milestone: ---
Classification: Fedora
Hi,
Could you please branch and build translate-toolkit for EPEL 10 ?
It is needed to build another package.
Regards,
Xavier
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2303880
[Bug 2303880] EPEL 10 Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2319795
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2260744
Bug ID: 2260744
Summary: Fedora build does not enable cloud input
Product: Fedora
Version: 39
OS: Linux
Status: NEW
Component: ibus-libpinyin
Keywords: Desktop, EasyFix, RFE
Severity: low
Assignee: pwu(a)redhat.com
Reporter: jiechushou(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
ibus-libpinyin upstream supports cloud input function, which can greatly
improve user experience
Cloud input support can be enabled by adding the --enable-cloud-input-mode flag
to the build configuration.
This cloud input option is optional and turned off by default. It does not
violate Fedora Packaging Guidelines
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2260744
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…