[kinfocenter] [Bug 359159] File Indexer Monitor: "Start File Indexer" button has no effect

2020-01-20 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=359159

Harald Sitter  changed:

   What|Removed |Added

 Status|REOPENED|CONFIRMED

--- Comment #5 from Harald Sitter  ---
Right, so, the plugin error is not really so much an error as it is a warning,
and it means nothing for the KCM. It's entirely irrelevant here. (kcmutils
supports two paths, if the first doesn't exist there's a warning about it
failing to load the plugin, but then another path is tried anyway so that
warning is moot)

The actual indexer problem seems to be that baloo gets confused about its own
state.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 359159] File Indexer Monitor: "Start File Indexer" button has no effect

2020-01-18 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=359159

Harald Sitter  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|DOWNSTREAM  |---

--- Comment #4 from Harald Sitter  ---
Oh I think I know what it is! It's not an error though is it? It's a warning...
and everything works correctly, right?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 359159] File Indexer Monitor: "Start File Indexer" button has no effect

2020-01-17 Thread Gregor Mi
https://bugs.kde.org/show_bug.cgi?id=359159

--- Comment #3 from Gregor Mi  ---
On Tumbleweed 20191023 still the same error:

 ~  kcmshell5 kcm_fileindexermonitor  
   
 org.kde.kcoreaddons: Error loading plugin
"kcm_fileindexermonitor" "The shared library was not found." 
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set

Could this still be a packaging error?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 359159] File Indexer Monitor: "Start File Indexer" button has no effect

2020-01-17 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=359159

Harald Sitter  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||sit...@kde.org
 Resolution|--- |DOWNSTREAM

--- Comment #2 from Harald Sitter  ---
This sounds a lot like a packaging problem you should take up with your
distribution. Assuming the bug is still relevant at all.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 359159] File Indexer Monitor: "Start File Indexer" button has no effect

2018-02-19 Thread Luca Weiss
https://bugs.kde.org/show_bug.cgi?id=359159

Luca Weiss  changed:

   What|Removed |Added

 CC||l...@z3ntu.xyz

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 359159] File Indexer Monitor: "Start File Indexer" button has no effect

2016-04-15 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359159

franz.berges...@gmail.com changed:

   What|Removed |Added

 CC||franz.berges...@gmail.com

--- Comment #1 from franz.berges...@gmail.com ---
I have the same problem on openSUSE Tumbleweed (20160412) (x86_64) with
Qt: 5.5.1
KDE Frameworks: 5.21.0

~> kcmshell5 kcm_fileindexer
Error loading plugin "kcm_fileindexermonitor" "The shared library was not
found." 
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set
fetched suspend state
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
KInit could not launch 'khelpcenter5'.

~>

The File Indexer Monitor is fired up, but show only some button, as shown in
the attachment.

A "File Indexer Monitor" app is visible both in the application dashboard and
krunner, but nothing happens.
The "File Indexer Monitor" in KInfoCenter freezes the GUI for about a minute
before showing it and there what it looks like a progress bar, but I'm not sure
it makes sense, given the issues just described

-- 
You are receiving this mail because:
You are watching all bug changes.