Summary: | Nepomuk (strigi) suspends repeatedly after power outage | ||
---|---|---|---|
Product: | [Frameworks and Libraries] solid | Reporter: | Ekeluo Chukwuogor <echukwuogor> |
Component: | powermanagement-daemon | Assignee: | Dario Freddi <drf> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | echidnaman, jithin1987, khashayar.lists, trueg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Ekeluo Chukwuogor
2009-07-15 16:40:02 UTC
The service simply connects to the appropriate Solid signal. So I think the problem needs to be in there. No other app or service exhibits any such effect though. which other app would that be for example? Not sure, was referring to any other apps that may listen to the same solid signal. I assume you meant that Strigi seems to be getting repeated power status change signals? Exactly. The problem is that I do not know of any other app using the signal. But it seems we tracked the problem down to PowerDevil. Will try to debug that. *** Bug 201731 has been marked as a duplicate of this bug. *** Sebastian, bug 200991 is another dupe that I commented on. I find the notifications annoying even before a suspend/resume cycle. On my system they show frequently enough anyway. Besides, I mouse over tip already tells you whether strigi is suspended or not, so maybe those two SendEvents should actually be removed? actually #200991 is not a duplicate. It is a wish to remove the signals. This is actually a bug where the powermanager reports invalid data, resulting in the strigi service being disabled and enabled over and over again. You are probably right that the notifications are not really necessary, at least I do not need them, except for testing maybe. But I introduced them due to users wanting to know what was going on. (In reply to comment #8) > actually #200991 is not a duplicate. It is a wish to remove the signals. This > is actually a bug where the powermanager reports invalid data, resulting in the > strigi service being disabled and enabled over and over again. You are probably > right that the notifications are not really necessary, at least I do not need > them, except for testing maybe. But I introduced them due to users wanting to > know what was going on. Right. I see why it's not a duplicate. I'm all for letting the user knowing what is going on, it's just when that information is flooding the user that it becomes annoying. Maybe a "Do not show again" button on the notification bubble would be the way to go? IMHO the real solution would be to fix the bug. But I don't have the knowledge for that. I guess this is fixed in 4.3.1 on Kubuntu 'cause it doesn't happen anymore, no more popups (whatsoever) about strigi status which is fine in my opinion. What kubuntu fixed is removing the code which raises the notification not the cause. #12 was right. It back, and still pops up regularly, about every 30-45 secs. Kind of distracting. (Kubuntu Karmic Beta, kde 4.3.2) Finally fixed it thanks to Jacopo De Simoi. Have an svn revision number handy? I can't find it. revision 1038603 in the 4.3 branch. Thanks a bunch. :) |