| Status | Name | Version | Date | Platform | ID | By |
| fixed | Link Boundary | Devel | 12.10.05 | ------- | 19 | MA_D |
| fixed | Links Move On deletes | 0.2.5 | 12.14.05 | Linux | 20 | MA_D |
| fixed | Highlight type moves links | 0.2.5 | 12.14.05 | Linux | 21 | MA_D |
| new | Source Install Failure | 0.3.0 | 12.20.05 | Source | 22 | MA_D |
| fixed | Arch Build Prob | 0.3.1 | 12.23.05 | Linux | 23 | MA_D |
| fixed | First Login Login Login | 0.4.0 | 01.12.06 | ALL | 24 | MA_D |
| fixed | Backspace undo messes links | 0.4.0 | 01.12.06 | ALL | 25 | MA_D |
| new | make install fails | 0.3.x | 01.15.06 | any | 26 | hannibal_the_2nd |
| new | No modules dir | Eliza Pinchley | 01.19.06 | Linux | 27 | MA_D |
| new | Highlighting Search Terms | 0.4.beta1 | 01.19.06 | ------ | 28 | MA_D |
| fixed | Random Crashes | 0.4.beta1 | 01.20.06 | ------ | 29 | MA_D |
| fixed | Link Click Lockup | 0.4.beta2 | 01.23.06 | Linux | 30 | MA_D |
If you create a link at the end of your entry, the last few characters you cannot put a return or any other character after it and if you click anywhere below it on the display it activates it.
If you make an entry with a link. And highlight and delete some text before it, then undo, then save and reopen the entry you'll find the links moved back the length of the deleted and undeleted text. Fixed.
When you make a link, and highlight some text before it then push a key to replace it with text, the links will be placed incorrectly upon save. Fixed.
It seems when I packaged the latest ejourn I forgot to reset the defaults. Make sure you: ./configure --prefix=/usr/local or something. I believe /usr/local was the default install directory. The configure script should have warned you to use a prefix, but just in case some people don't notice!
eJourn's build system is incompatible with Archlinux's build/package system. The makefile must support the "DESTDIR" variable for it to work correctly. This may be a simple change: 1.) The configure script should put the --prefix= into DESTDIR 2.) The Makefile should use DESTDIR for the install instead of that in pref.tmp
This has been fixed. eJourn now supports make DESTDIR install
The first time you use the program you may be asked to login as many as three times. This has been confirmed with encryption enabled. It has no further adverse effects on the program. You just have to click login a lot and enter your password a lot. Rather embarrassing ;).
This is now fixed, it won't prompt at all for passwordless journals.
Backspace/delete and then undo/redo will mess up the links in a document. Shifts them around. This has been fixed in development, should ship in 0.4.
you need to create a folder named modules before compiling. Just use: mkdir modules
I know that you advised to do mkdir modules, but changing two lines in makefile solves the problem. line 22: #cp src/modules/*.so modules/ line 55: cp src/modules/*.so $(DESTDIR)/share/ejourn/modules/
I'm having difficult recreating this bug.
Please give me steps to reproduce it, and your version of make (make -v). Thanks.
If you do a search, then edit something the search term gets highlighted even with the search bar blank.
You may notice some random crashes on eJourn 0.4.beta1. It's been fixed for the next release.
In second.c there's an attempt to access a structure which isn't yet created in the second thread because it may not yet have returned for the first thread to set said value; in elog_scnd_initialize().
The result is that some memory location is accessed that shouldn't be and probably also altered, causes random crashing under gdb. Instant crash on valgrind, and unknown results in no debugger.
Upon clicking a link eJourn version 0.4.beta1 and 0.4.beta2 will lockup. This has been fixed for the next release.
Bug reporting is open to everyone, no usernames or passwords, just an image word to punch in to tell me you aren't a bot.
Give your bug a fitting name, leave id and status alone (for new bugs, not modifying old ones), put in the version of eJourn you're using, if you can't remember "current" is ok. And in description please put in a good, ie not vague (500 words is fine, 250 is fine, 100 is great, 10 is not enough), description of how to reproduce the bug: If it's not reproducable, please say so and describe what happens.
You may leave "Your ID:" as "a user" if you don't wish to provide a name. This block is mostly so that you can see which developer has fixed a bug, not who has reported it
If you've done a backtrace you may post that in the description