Received SIGHUP or SIGTERM: nano cannot edit empty file












3















I have a empty file in home directory, when I run nano temp4 it gives me error Received SIGHUP or SIGTERM and does not open the file



@archlinux ➜  ~  ᐅ  nano temp4
Received SIGHUP or SIGTERM
@archlinux ➜ ~ ᐅ l temp4
-rw-r--r-- 1 edward edward 0 May 17 16:04 temp4
@archlinux ➜ ~ ᐅ file temp4
temp4: empty


what could be the reason? This has been happening too often lately with many other files.



However, I can solve the problem by running echo > temp4 and then opening it with nano



(I am running Arch Linux. nano 2.5.3)










share|improve this question























  • Use strace and auditd to better debug what system calls nano is making and where the signal is coming from.

    – thrig
    May 17 '16 at 14:12






  • 1





    I have encountered this problem also. Solved it after running sudo su before (Debian 9 stretch) .

    – grama
    Dec 20 '17 at 5:26


















3















I have a empty file in home directory, when I run nano temp4 it gives me error Received SIGHUP or SIGTERM and does not open the file



@archlinux ➜  ~  ᐅ  nano temp4
Received SIGHUP or SIGTERM
@archlinux ➜ ~ ᐅ l temp4
-rw-r--r-- 1 edward edward 0 May 17 16:04 temp4
@archlinux ➜ ~ ᐅ file temp4
temp4: empty


what could be the reason? This has been happening too often lately with many other files.



However, I can solve the problem by running echo > temp4 and then opening it with nano



(I am running Arch Linux. nano 2.5.3)










share|improve this question























  • Use strace and auditd to better debug what system calls nano is making and where the signal is coming from.

    – thrig
    May 17 '16 at 14:12






  • 1





    I have encountered this problem also. Solved it after running sudo su before (Debian 9 stretch) .

    – grama
    Dec 20 '17 at 5:26
















3












3








3








I have a empty file in home directory, when I run nano temp4 it gives me error Received SIGHUP or SIGTERM and does not open the file



@archlinux ➜  ~  ᐅ  nano temp4
Received SIGHUP or SIGTERM
@archlinux ➜ ~ ᐅ l temp4
-rw-r--r-- 1 edward edward 0 May 17 16:04 temp4
@archlinux ➜ ~ ᐅ file temp4
temp4: empty


what could be the reason? This has been happening too often lately with many other files.



However, I can solve the problem by running echo > temp4 and then opening it with nano



(I am running Arch Linux. nano 2.5.3)










share|improve this question














I have a empty file in home directory, when I run nano temp4 it gives me error Received SIGHUP or SIGTERM and does not open the file



@archlinux ➜  ~  ᐅ  nano temp4
Received SIGHUP or SIGTERM
@archlinux ➜ ~ ᐅ l temp4
-rw-r--r-- 1 edward edward 0 May 17 16:04 temp4
@archlinux ➜ ~ ᐅ file temp4
temp4: empty


what could be the reason? This has been happening too often lately with many other files.



However, I can solve the problem by running echo > temp4 and then opening it with nano



(I am running Arch Linux. nano 2.5.3)







nano






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 17 '16 at 10:39









Edward TorvaldsEdward Torvalds

2,61373364




2,61373364













  • Use strace and auditd to better debug what system calls nano is making and where the signal is coming from.

    – thrig
    May 17 '16 at 14:12






  • 1





    I have encountered this problem also. Solved it after running sudo su before (Debian 9 stretch) .

    – grama
    Dec 20 '17 at 5:26





















  • Use strace and auditd to better debug what system calls nano is making and where the signal is coming from.

    – thrig
    May 17 '16 at 14:12






  • 1





    I have encountered this problem also. Solved it after running sudo su before (Debian 9 stretch) .

    – grama
    Dec 20 '17 at 5:26



















Use strace and auditd to better debug what system calls nano is making and where the signal is coming from.

– thrig
May 17 '16 at 14:12





Use strace and auditd to better debug what system calls nano is making and where the signal is coming from.

– thrig
May 17 '16 at 14:12




1




1





I have encountered this problem also. Solved it after running sudo su before (Debian 9 stretch) .

– grama
Dec 20 '17 at 5:26







I have encountered this problem also. Solved it after running sudo su before (Debian 9 stretch) .

– grama
Dec 20 '17 at 5:26












0






active

oldest

votes









protected by Community 1 hour ago



Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?














0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes



protected by Community 1 hour ago



Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?



Popular posts from this blog

宮崎県

濃尾地震

シテ島