Description of problem: Might have changed permissions on folders. Version-Release number of selected component: evolution-3.10.4-2.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: evolution crash_function: __alloc_dir executable: /usr/bin/evolution kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #3 __alloc_dir at ../sysdeps/posix/opendir.c:207 #4 maildir_summary_check at camel-maildir-summary.c:586 #5 maildir_summary_sync at camel-maildir-summary.c:767 #6 local_folder_synchronize_sync at camel-local-folder.c:436 #7 camel_folder_synchronize_sync at camel-folder.c:4325 #8 vee_folder_synchronize_sync at camel-vee-folder.c:934 #9 camel_folder_expunge_sync at camel-folder.c:3583 #10 e_mail_folder_expunge_sync at e-mail-folder-utils.c:437 #11 mail_folder_expunge_thread at e-mail-folder-utils.c:200 #12 run_in_thread at gsimpleasyncresult.c:871 Potential duplicate: bug 894113
Created attachment 887954 [details] File: backtrace
Created attachment 887955 [details] File: cgroup
Created attachment 887956 [details] File: core_backtrace
Created attachment 887957 [details] File: dso_list
Created attachment 887958 [details] File: environ
Created attachment 887959 [details] File: exploitable
Created attachment 887960 [details] File: limits
Created attachment 887961 [details] File: maps
Created attachment 887962 [details] File: open_fds
Created attachment 887963 [details] File: proc_pid_status
Created attachment 887964 [details] File: var_log_messages
(In reply to Ernie D from comment #0) > Description of problem: > Might have changed permissions on folders. Thanks for a bug report. What exactly do you mean by this, please? It crashed when accessing folders: /home/ernie/.local/share/evolution/mail/local/.Sent/new /home/ernie/.local/share/evolution/mail/local/.Sent/cur Did you change disk folder permissions of any in this path or above it, thus they are not accessible anymore? I found some similar bug reports upstream too, but they seemed more like a memory corruption (like when some code accesses already freed memory), not necessarily caused by on-disk folder properties changes.
(In reply to Milan Crha from comment #12) > (In reply to Ernie D from comment #0) > > Description of problem: > > Might have changed permissions on folders. > > Thanks for a bug report. What exactly do you mean by this, please? It > crashed when accessing folders: > /home/ernie/.local/share/evolution/mail/local/.Sent/new > /home/ernie/.local/share/evolution/mail/local/.Sent/cur > Did you change disk folder permissions of any in this path or above it, thus > they are not accessible anymore? > > I found some similar bug reports upstream too, but they seemed more like a > memory corruption (like when some code accesses already freed memory), not > necessarily caused by on-disk folder properties changes. Yea, Sorry about that, but I'm now sure I did. I created a new home folder to try to solve a different problem, and did it using sudo. I forgot to chown to my own username after moving the Evolution files into the new $HOME. I probably should have just ignored the abrt message until I could explore it further, but I didn't think it should have crashed. Ernie D
Created attachment 888941 [details] test.c I agree, it is not supposed to crash. I tried to reproduce this with a test program, but it doesn't crash when I pass it a folder which it cannot open, like other user's home, thus either this is about something else, or you have involved more fine-grained options. In any case, good you managed to have it running again.