https://bugzilla.novell.com/show_bug.cgi?id=765769 https://bugzilla.novell.com/show_bug.cgi?id=765769#c10 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com --- Comment #10 from Bernhard Wiedemann <bwiedemann@suse.com> 2012-06-28 19:56:03 CEST --- I can reproduce this on Factory by causing any conflict popup in qt sw_single. the backtrace is (gdb) bt #0 0xb774d422 in __kernel_vsyscall () #1 0xb71fb656 in kill () from /lib/libc.so.6 #2 0xb75b4aee in signal_handler(int) () from /usr/lib/liby2.so.2 #3 <signal handler called> #4 0xb7472fcc in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) () from /usr/lib/libstdc++.so.6 #5 0xae624846 in YQPkgConflict::addSolutions() () from /usr/lib/YaST2/plugin/libpy2qt_pkg.so.2 #6 0xae6257e1 in YQPkgConflict::YQPkgConflict(QWidget*, boost::intrusive_ptr<zypp::ResolverProblem>) () from /usr/lib/YaST2/plugin/libpy2qt_pkg.so.2 #7 0xae625ac5 in YQPkgConflictList::fill(std::list<boost::intrusive_ptr<zypp::ResolverProblem>, std::allocator<boost::intrusive_ptr<zypp::ResolverProblem> > >) () from /usr/lib/YaST2/plugin/libpy2qt_pkg.so.2 #8 0xae6217d7 in YQPkgConflictDialog::processSolverResult(bool) () from /usr/lib/YaST2/plugin/libpy2qt_pkg.so.2 #9 0xae621e72 in YQPkgConflictDialog::solveAndShowConflicts() () from /usr/lib/YaST2/plugin/libpy2qt_pkg.so.2 #10 0xae603d3c in YQPackageSelectorBase::resolveDependencies() () from /usr/lib/YaST2/plugin/libpy2qt_pkg.so.2 #11 0xae606338 in YQPackageSelector::autoResolveDependencies() () from /usr/lib/YaST2/plugin/libpy2qt_pkg.so.2 I noticed that there is std::list mentioned in #7 which caused trouble with yast2-gtk earlier when mixing old c++ standard with new one (each defining std::list with different size). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.