| 1 |
Jan Jitse Venselaar skrev: |
| 2 |
|
| 3 |
>As the reporter of the problem with nano, I'd like to make 1 correction to |
| 4 |
>this report: Recompiling nano and its depencies did not fix the crashes. It |
| 5 |
>just fixed the eating of the file. |
| 6 |
>I did not recompile my entire system, but a crash of such a small and basic |
| 7 |
>app as nano made me not want to do this outside of a chroot, which I |
| 8 |
>currently do not have the means for. |
| 9 |
>I reread my report, and I saw it was not clear that recompiling nano and its |
| 10 |
>dependencies did not fix the crashes. Sorry for the confusion. |
| 11 |
> |
| 12 |
>Jan Jitse |
| 13 |
> |
| 14 |
> |
| 15 |
I have a theory about the nano problem. Could you please try with nano |
| 16 |
1.2.5 instead and see if it still craches? |
| 17 |
|
| 18 |
I believe this might be a bug in nano 1.3.X and not a problem with the |
| 19 |
amd64 strings patch, it just exposes the bug. Nano 1.3.8 running under |
| 20 |
Suse 9.3 suffers from exactly the same problem (craching when |
| 21 |
searching). But if I downgrade it to 1.2.5 it's completly stable. And |
| 22 |
1.3.X is actually the unstable development branch of nano while 1.2.X is |
| 23 |
the stable so it could very well contain bugs. |
| 24 |
|
| 25 |
-- |
| 26 |
Simon Strandman <simon.strandman@×××××.com> |
| 27 |
|
| 28 |
-- |
| 29 |
gentoo-amd64@g.o mailing list |
Archives