Bugzilla – Bug 805731
[libyui-gtk-pkg] YaST2 Software Manager crashes by a violation of segmentation when I choose many packages in a hurry.
Last modified: 2013-09-27 11:45:38 UTC
Created attachment 526457 [details] y2log, signal, GDB backtrace , and messages User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1411.0 Safari/537.31 SUSE/26.0.1411.0 I'm testing openSUSE12.3RC1 i586 GNOME on VirtualBox4.2.6 in Windows 7 SP1 64bit . YaST2 Software Manager crashes by a violation of segmentation when I choose many packages in a hurry. I attach files . 1) /var/log/YaST2/y2log 2) /var/log/YaST2/signal 3) backtrace.txt - gdb backtrace full 4) free_invalid_pointer.txt - Software Manager's dying messages Reproducible: Always Steps to Reproduce: 1. # /usr/lib/YaST2/bin/y2base sw_single gtk 2. Input KDE into the "Find:" textbox . 3. Choose packages in a hurry in an order from before . 4. If you find a message of "There are some conflicts on the transaction that must be solved manually.", choose cansel . 5. Continue 3. and 4. Actual Results: Software Manager crashes by SEGV, prints messages, and core dumped . Expected Results: You choose packages normally. Please see also https://dl.dropbox.com/u/86335040/openSUSE/SoftwareManagerSEGV.png https://dl.dropbox.com/u/86335040/openSUSE/Screenshot_from_2013-02-24_22%3A04%3A55.png https://dl.dropbox.com/u/86335040/openSUSE/Screenshot_from_2013-02-24%2021%3A31%3A14.png
YaST maintainers, Please see also these reports: https://bugzilla.novell.com/show_bug.cgi?id=786650 https://bugzilla.novell.com/show_bug.cgi?id=773049 https://bugzilla.novell.com/show_bug.cgi?id=779821
openSUSE 12.3, Gnome 3.6, Yast Software management still crashes even when not picking up random packages, instead it happens when upgrading/removing packages packages. After the module crashes i get the following output: YaST got signal 11 at YCP file PackagesUI.ycp:301 /sbin/yast2: line 431: 3139 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
lets handle it in one bug report *** This bug has been marked as a duplicate of bug 842567 ***