https://bugzilla.novell.com/show_bug.cgi?id=258742 ------- Comment #30 from mvidner@novell.com 2007-04-10 01:28 MST ------- Created an attachment (id=129953) --> (https://bugzilla.novell.com/attachment.cgi?id=129953&action=view) valgrind.tar.gz drwxr-xr-x 0 2007-04-10 09:14:15 logs/ -rw------- 37494 2007-04-06 13:08:46 logs/valgrind.log.nonet -rw------- 27769 2007-04-06 12:56:16 logs/valgrind.log.net drwxr-xr-x 0 2007-04-10 09:14:26 diffs/ -rw-r--r-- 474 2007-04-10 07:13:54 diffs/installation.ycp.diff -rw-r--r-- 717 2007-04-10 07:16:22 diffs/YaST2.call.diff We have two bugs mixed here: (A) network not being started in certain cases (B) segfault (conditioned by A). If (A) needs to be reopened, please use a separate bugzilla entry. Concerning the segfault it seems that the problem really is somewhere under yast2-qt (qt, xorg, ...?). I patched yast to run under valgrind, optionally with network. I also added an early call to the package manager in hope to trigger the bug but that did not work. When yast runs with network, there is a valgrind error early on but then it runs fine. If network is not enabled, another error occurs and presumably is the immediate cause of the segfault. I think that the first error, which is a misplaced write, corrupts some memory area that is used only in the case without network. -- 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, or are watching someone who is.