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=2496979
Bug ID: 2496979
Summary: libchewing-0.13.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: libchewing
Keywords: FutureFeature, Triaged
Assignee: kanru(a)kanru.info
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
kanru(a)kanru.info, robinlee.sysu(a)gmail.com
Target Milestone: ---
Classification: Fedora
Releases retrieved: 0.13.0
Upstream release that is considered latest: 0.13.0
Current version/release in rawhide: 0.12.0-3.fc45
URL: https://chewing.im/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_M…
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from Anitya:
https://release-monitoring.org/project/1577/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/libchewing
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2496979
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=2378003
Bug ID: 2378003
Summary: python-polib: Stop using deprecated
%py3_build/%py3_install macros
Product: Fedora
Version: rawhide
Status: NEW
Component: python-polib
Assignee: petersen(a)redhat.com
Reporter: mhroncok(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, reallylongword(a)gmail.com,
sundeep_anand(a)yahoo.com
Blocks: 2376118
Target Milestone: ---
Classification: Fedora
Dear package maintainer,
this bugzilla is automated becasue the number of impacted packages it too high
to go trough manually.
It appears that your package uses the deprecated %py3_build and/or %py3_install
macro.
See https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros for why the
macros are deprecated.
%py3_install expands to python setup.py install. This has been a deprecated
command for 5 years and will likely stop working in Fedora 45.
Please migrate to %pyproject_buildrequires + %pyproject_wheel +
%pyproject_install macros instead.
See
https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros#Migrating_to_…
for migration guide.
See https://github.com/hroncok/pyprojectize/ for a tool that can help you
automate the migration.
Thank you. Let me know if you need help.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2376118
[Bug 2376118] Deprecate RPM Macros for setup.py-based Python Builds
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2378003
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=2498492
Bug ID: 2498492
Summary: the completely moronic choice to make this the default
even for PCs
Product: Fedora
Version: 44
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus-typing-booster
Keywords: CustomerScenariosInitiative, Desktop
Severity: medium
Assignee: mfabian(a)redhat.com
Reporter: vorlmaldor(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Do you have any idea how hard it is to type a password in when you have
ibus-typing-booster enabled by default on a PC?
The descision to include this is so far beyond stupid I just can't even. You
set your keyboard during install time, why in the world would you enforce this
absulote garbage on everyone?
typing a password with predictive text popping up is a privacy nightmare. What
happened to security?
You could let people select their device type during install so that we aren't
all forced into this level of stupid.
If feels like you have these issues:
Blind Probing: The installer only checks generic hardware flags (like looking
for a battery indicator or an I2C touchscreen controller).'
False Positives: If you are using a modern desktop motherboard with Bluetooth,
or a monitor with a built-in USB controller that registers as "touch capable,"
Fedora assumes you are on a mobile-adjacent device.Aggressive Packages:
Because it blindly flags your PC as a "mobile device," it forces the
ibus-typing-booster mobile keyboard packages to run during the initial user
setup, completely ignoring that you are sitting at a desk typing with a
physical 104-key plastic keyboard.
You are better than this. You don't force poor UI design just because you are
to lazy to add a device selection screen.
Reproducible: Always
Steps to Reproduce:
1.install fedora 44
2.try to type a password
3.get frustrated because stupid descisions were made
Actual Results:
I had serious issues trying to get a nominally secure password to login.
Expected Results:
I expect a PC to act like a PC and not get moronic tablet defaults pushed onto
a PC.
At the absolute least I would expect an extremely visible toggle on the login
page, but you couldn't even be bothered to do that.
Additional Information:
The fact that this isn't even easily disabled shows just how out of touch you
are with reality. You should be completely ashamed of this level of stupid.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2498492
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…