Description of problem: Program crashes while composing a response to a mail, seemingly while trying to save a draft to the IMAP server. Version-Release number of selected component: claws-mail-3.9.2-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: claws-mail crash_function: spt_copyenv executable: /usr/bin/claws-mail kernel: 3.9.8-300.fc19.x86_64 runlevel: N 5 uid: 500 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #0 spt_copyenv at setproctitle.c:111 #1 spt_init at setproctitle.c:201 #2 call_init at dl-init.c:82 #3 _dl_init at dl-init.c:131 #4 dl_open_worker at dl-open.c:566 #5 _dl_catch_error at dl-error.c:177 #6 _dl_open at dl-open.c:656 #7 do_dlopen at dl-libc.c:87 #8 _dl_catch_error at dl-error.c:177 #9 dlerror_run at dl-libc.c:46
Created attachment 769384 [details] File: backtrace
Created attachment 769385 [details] File: cgroup
Created attachment 769386 [details] File: core_backtrace
Created attachment 769387 [details] File: dso_list
Created attachment 769388 [details] File: environ
Created attachment 769389 [details] File: limits
Created attachment 769390 [details] File: maps
Created attachment 769391 [details] File: open_fds
Created attachment 769392 [details] File: proc_pid_status
Created attachment 769393 [details] File: var_log_messages
The backtrace is completely elsewhere. #1 spt_init (argc=1, argv=0x7ffff02b82c8, envp=<optimized out>) at setproctitle.c:201 libbsd? #6 0x00007f148523221b in _dl_open (file=0x7ffff02b3810 "libnss_wins.so.2", mode=-2147483647, caller_dlopen=0x7f147e83214b <__GI___nss_lookup_function+651>, nsid=-2, argc=1, argv=<optimized out>, env=0x20c2550) at dl-open.c:656 Samba?
My /etc/nsswitch.conf contains: hosts: files mdns4_minimal [NOTFOUND=return] dns wins which accounts for libnss_wins.so.2, which in turn pulls in libbsd. And I can confirm that removing "wins" from that line makes claws-mail not crash. This worked just fine under F18. Where should this go, then?
What version of libbsd is installed? There was a problem in setproctitle in libbsd-0.5.1, but it should be fixed in 0.5.2.
libbsd-0.5.2-1.fc19.x86_64
libbsd-0.6.0-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/libbsd-0.6.0-1.fc19
libbsd-0.6.0-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/libbsd-0.6.0-1.el6
libbsd-0.6.0-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/libbsd-0.6.0-1.el5
Package libbsd-0.6.0-1.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing libbsd-0.6.0-1.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-10849/libbsd-0.6.0-1.el5 then log in and leave karma (feedback).
libbsd-0.6.0-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
libbsd-0.6.0-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
libbsd-0.6.0-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.