Bug 102018 - while searching for an icc, keyboard is locked out
Summary: while searching for an icc, keyboard is locked out
Status: NEEDINFO
Alias: None
Product: colord
Classification: Unclassified
Component: daemon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Richard Hughes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-02 19:24 UTC by Chris Bruner
Modified: 2017-08-03 17:56 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Chris Bruner 2017-08-02 19:24:29 UTC
This is a bug that has been plaguing me for years, and apparently a few other users. I've finally narrowed it down to something to do with the colord system.

Occasionally the keyboard stalls for about 15 seconds, losing some of the keystrokes.

I can recreate it occasionally when I plug my samsung Galaxy S5 in.

, and the following devices appear in the color management system:
sys-fs(null)
Samsung - SAMSUNG Android.

Even looking at this color management system will cause it to lock. It's locked 3 times while typing this text.

I don't undersstand (just happened now for 1/2 second and I got a double s) how the color system is affecting the keyboard. Makes my system very hard to use.

running killall colord resolves my problem, but really isn't a good solution.

/usr/lib/colord/colord --verbose
15:04:34	Verbose debugging enabled (on console 1)
15:04:34	CdMappingDb: trying to open database '/var/lib/colord/mapping.db'
15:04:34	CdDeviceDb: trying to open database '/var/lib/colord/storage.db'
15:04:34	CdProfileDb: trying to open database '/var/lib/colord/storage.db'
15:04:34	searching for plugins in /usr/lib/x86_64-linux-gnu/colord-plugins
15:04:34	run cd_plugin_initialize on /usr/lib/x86_64-linux-gnu/colord-plugins/libcd_plugin_scanner.so
15:04:34	finished cd_plugin_initialize
15:04:34	run cd_plugin_initialize on /usr/lib/x86_64-linux-gnu/colord-plugins/libcd_plugin_camera.so
15:04:34	finished cd_plugin_initialize
15:04:34	run cd_plugin_initialize on /usr/lib/x86_64-linux-gnu/colord-plugins/libcd_plugin_sane.so
15:04:34	finished cd_plugin_initialize
15:04:34	System vendor: 'MSI', System model: 'MS-7818'
15:04:34	CdMain: lost name: org.freedesktop.ColorManager
15:04:34	run cd_plugin_destroy on /usr/lib/x86_64-linux-gnu/colord-plugins/libcd_plugin_scanner.so
15:04:34	finished cd_plugin_destroy
15:04:34	run cd_plugin_destroy on /usr/lib/x86_64-linux-gnu/colord-plugins/libcd_plugin_camera.so
15:04:34	finished cd_plugin_destroy
15:04:34	run cd_plugin_destroy on /usr/lib/x86_64-linux-gnu/colord-plugins/libcd_plugin_sane.so
15:04:34	finished cd_plugin_destroy
Comment 1 Richard Hughes 2017-08-03 11:02:08 UTC
Are there any logs in the journal about the hardware access? If you run "colord --verbose" are there any warnings printed there too?
Comment 2 Chris Bruner 2017-08-03 17:56:05 UTC
There are no messages from colord after the ones I listed originally.

At one time I think I saw on the client that it was searching for something, (icc probably) but I haven't seen it since.

The mouse used to lock up as well, but now the mouse never locks up. The keyboard occasionally. When it starts to happen it will happen a lot.

Rebooting will fix it for hours. killall colord seems to fix it as well.

the devices make me think that something is miscommunicating.
sys-fs(null) doesn't sound like any device I've seen.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.