Comment # 2 on bug 1061015 from Konstantinos Tsamis

(In reply to Michael Andres from comment #1)
> The network problems are visible in the log, also an interrupted command
> (PID 11221), but all logs end as expected with closing the RpmDb. 
> 
> According to the trace above the crash is located inside libcurl, which
> makes it even harder to analyze/reproduce....
> 
> @Konstantinos Which libcurlversion is installed?
> > rpm -qa 'libcurl*'

~> rpm -qa 'libcurl*'
libcurl4-7.37.0-20.1.x86_64


The interrupted command was probably because I was trying to refresh the repos
and managed to kill zypper once "normally" before getting the core dump.