very high cpu usage, system unresponsive

Bug #2012146 reported by enorrmann
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ibus
Unknown
Unknown
ardour (Debian)
New
Unknown
ardour (Ubuntu)
Confirmed
Undecided
Unassigned
ibus (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: ibus 1.5.28-2
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 18 15:21:55 2023
InstallationDate: Installed on 2022-05-13 (308 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: ibus
UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago)

Revision history for this message
enorrmann (enorrmann) wrote :
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Thanks for your report!

I see that you installed your system last year. Can you possibly tell if it's a regression from ibus 1.5.28-1, i.e. did it work smoothly with that version and the issue started with ibus 1.5.28-2?

I'm asking because 1.5.28-2 includes two patches which are not yet in the upstream git repo, but only in the repo of the upstream maintainer. Those patches are supposed to fix bug #2009700.

Whatever the answer to that question is, I would ask you to report this issue also to the upstream issue tracker:

https://github.com/ibus/ibus/issues

If you do, please post the URL to the issue in a comment here. And, btw, please state in the upstream issue that ibus 1.5.28-2 in Ubuntu includes the patches I mentioned.

Revision history for this message
enorrmann (enorrmann) wrote :

the issue started when I upgraded to 23.04 yes

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Ok.. But when exactly did you do that? If it was very recently, you may have upgraded ibus from 1.5.27-2 directly to 1.5.28-2.

Revision history for this message
enorrmann (enorrmann) wrote :

last friday I upgraded from 22.10 to 23.04

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Thanks for clarifying. It means that we can't tell whether the issue is related to the specific changes in ibus 1.5.28-2, or if it is a general ibus 1.5.28 problem (or an ardour 7.3 problem...).

In any case my plea to also report it to ibus upstream still stands.

Revision history for this message
Frits Jalvingh (fjalvingh) wrote :

Not sure it is related, but I have what seems to be the same issue but I'm still on 22.10. I see the following in dpkg.log:
2023-02-15 10:48:53 upgrade libusb-1.0-0-dev:amd64 2:1.0.25-1ubuntu2 2:1.0.26-1

I had no problems before, so to me it looks like that update might have caused it. I will revert that back and see if the issues are gone.

Revision history for this message
Frits Jalvingh (fjalvingh) wrote :

Sorry, that comment was incorrect, obviously; for some reason my eyes betrayed me 8-( Still have the same problem but clearly not related to this 8-(

Revision history for this message
enorrmann (enorrmann) wrote :

I can confirm this is only present in ardour shipped with ubuntu 23.04 or by compiling ardour from source on ubuntu 23.04. If i run the binary provided by ardour.org, the issue is NOT present

Revision history for this message
enorrmann (enorrmann) wrote :
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

@enorrmann: The latter is valuable info. I submitted an ardour Debian bug, which you should have received a copy of. Please feel free to add relevant info to that bug, if you think that I missed something.

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

And thanks for reporting it to ibus upstream too. :)

Changed in ardour (Debian):
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ardour (Ubuntu):
status: New → Confirmed
Changed in ibus (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.