Bug 1283559 - Baloo file extractor uses all possible connections to X
Baloo file extractor uses all possible connections to X
Product: Fedora
Classification: Fedora
Component: kf5-baloo (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: KDE SIG
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-11-19 04:59 EST by webdesigner
Modified: 2016-07-19 14:30 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 14:30:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description webdesigner 2015-11-19 04:59:21 EST
Description of problem:
try to run kate (for example):
Error: Maximum number of clients reachedokular: cannot connect to X server :0
ps shows >100 processes of /bin/baloo_file_extractor

giving "killall baloo_file_extractor" works for me

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.6.3
kernel:         4.2.5-201.fc22.x86_64
type:           libreport
Comment 1 Jakub Filak 2015-11-19 07:48:29 EST
Thank you for the report. Reassigning from gnome-abrt to kf5-baloo. Feel free to report any further bugs you find to our bug tracking system.
Comment 2 Fedora End Of Life 2016-07-19 14:30:30 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.