FS#29931 - [xiphos] Pages/Chapters keep back-sliding
Attached to Project:
Community Packages
Opened by Andrei Arici (distrohopperarched) - Thursday, 17 May 2012, 15:29 GMT
Last edited by Alexander F. Rødseth (xyproto) - Monday, 21 May 2012, 10:22 GMT
Opened by Andrei Arici (distrohopperarched) - Thursday, 17 May 2012, 15:29 GMT
Last edited by Alexander F. Rødseth (xyproto) - Monday, 21 May 2012, 10:22 GMT
|
Details
Description:
I have experienced it at least 3 times, randomly, with many older versions too, including version 3.1.5-gtkhtml3, that on occasion "pages" keep flipping backwards on their own. It looks like a sort of a loop that makes Xiphos behave as if it's thinking "Oops, I'm displaying the wrong page, I'll flip one back to correct this..." and never stops doing this. Steps to reproduce: If anyone can identify under what conditions this happens and can reproduce this please comment. |
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Monday, 21 May 2012, 10:22 GMT
Reason for closing: Upstream
Additional comments about closing: The problems with xiphos and/or sword doesn't look like they will be fixed any time soon.
Monday, 21 May 2012, 10:22 GMT
Reason for closing: Upstream
Additional comments about closing: The problems with xiphos and/or sword doesn't look like they will be fixed any time soon.
This can be reported upstream to the Xiphos developers.
I also found that I can't read Ezechiel 12, cause it rolls back to chapter 9... but I can read 14. So this might be a hint?
Critical- System crash, severe boot failure that is likely to affect more than just you, or an exploitable security issue in either a core or outward-facing service package.
High- The main functionality of the application does not work, less critical security issues, etc.
Medium- A non-essential functionality does not work, UNIX standards not respected, etc.
Low- An optional functionality (plugin or compilation activated) does not work.
Very Low- Translation or documentation mistake. Something that really does not matter much but should be noticed for a future release.
It would be "High" or "Medium", depending on to wich degree one would consider the program to not be working. In any case, it is not "Critical".