Interaction with onboard causes synaptic to become unresponsive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
synaptic (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hello.
I originally filed this report against onboard (see bug #1264315). Original bug description follows:
---snip ---
- When onboard is running (it doesn't matter whether the onboard keyboard is being displayed/used), synaptic experiences major issues of unresponsiveness. Starting synaptic takes minutes, likewise every time the quick search bar in synaptic is used.
During this time, the processes for synaptic, onboard and the accessibility dbus daemon consume lots of cpu time, (almost 100% of one core _each_). After a minute or two of waiting, synaptic becomes usable again, and the cpu load disappears.
- Onboard stay usable the entire time.
- Other applications do not seem to have the same issue.
- When onboard is not running, synaptic does not show this issue.
I've tried a quick strace, and it seems that synaptic spends the unresponsive time sending lots of data using sendmsg(), but I haven't figured out where to.
--snap---
marmuta responded: "The cause I believe is that synaptic sends a storm of AT-SPI focus events when updating the package view. It seems to generate at least one event for each added line."
Therefore I am now filing this bug report on synaptic.
regards,
Daniel
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: synaptic 0.80.2
Uname: Linux 3.12.2-
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Sun Jan 5 18:33:11 2014
InstallationDate: Installed on 2013-12-25 (10 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: synaptic
UpgradeStatus: No upgrade log present (probably fresh install)