| Summary: | nepomukservicestub floods .xsession-errors | ||
|---|---|---|---|
| Product: | [Unmaintained] nepomuk | Reporter: | greylander |
| Component: | nepomukserver | Assignee: | Sebastian Trueg <trueg> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | me |
| Priority: | NOR | ||
| Version First Reported In: | 4.7 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
greylander
2011-12-12 17:51:03 UTC
Correction: KDE & Nepomuk versions for this bug are 4.7.2. (at least the nepomuk config help->about give 4.7.2 as of the "config" application... not sure how this relates to the version of nepomuk, strigi, etc. components. I also want to emphasize that I have seen the other bugs about nepomuk spamming the .xsession-errors,but the error message that my .xsession-errors file is filling up with is different from those. So I think this may not be a duplicate, unless the problem is with the underlying systems by which all nepomuk messages are reported to .xsession-errors and not related to the particular error message. Correction: KDE & Nepomuk versions for this bug are 4.7.2. (at least the nepomuk config help->about give 4.7.2 as of the "config" application... not sure how this relates to the version of nepomuk, strigi, etc. components. I also want to emphasize that I have seen the other bugs about nepomuk spamming the .xsession-errors,but the error message that my .xsession-errors file is filling up with is different from those. So I think this may not be a duplicate, unless the problem is with the underlying systems by which all nepomuk messages are reported to .xsession-errors and not related to the particular error message. You can generally get this information in any KDE application. Help -> About KDE. Does this problem still occur in KDE 4.9? Cause this seems like an installation problem. Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Development has moved to Baloo, please try again using the latest version and applications, and submit a new ticket for frameworks-baloo if you still have an issue. Thank you! |