https://bugs.kde.org/show_bug.cgi?id=504861
--- Comment #7 from Sanfod Rockowitz <rockow...@minsoft.com> --- I've looked more closely at the specific assertion failure cited. It's not actually an assert() call. Rather it's a macro TRACED_ASSERT() that I defined to facilitate remote debugging. For implementation and cross-platform reasons, I defined it to call exit(1) instead of actually asserting failure, which is why, I expect, powerdevil terminates with "success". If this makes sense, I can replace the TRACED_ASSERT() statements with normal assert() calls. It makes the assert failures less informative, but I can live with that if it's what it takes to make powerdevil terminate with failure instead of success. Of course, the assertion shouldn't be triggered in the first place - it indicates inconsistent data structures. It's hard to prove a negative, but hopefully the changes in 2.2.1-dev will have addressed this situation. -- You are receiving this mail because: You are watching all bug changes.
