Bug 344289

cat /etc/SuSE-release
openSUSE 10.3.1 (i586) Alpha0
VERSION = 10.3.1

rpm -qa | grep yast
yast2-backup-2.15.5-0.1
yast2-gtk-2.15.9-53
yast2-storage-lib-2.16.5-5
yast2-ncurses-2.16.2-3
yast2-control-center-2.15.6-11
yast2-apparmor-2.1-48
yast2-runlevel-2.16.0-9
yast2-nis-client-2.16.0-17
yast2-repair-2.16.2-8
yast2-metapackage-handler-0.7.3-7
yast2-dhcp-server-2.15.5-41
yast2-control-center-gnome-2.13.2-121
yast2-trans-ru-2.15.25-6
yast2-transfer-2.14.0-128
yast2-sound-2.16.1-11
yast2-nfs-client-2.15.0-46
yast2-x11-2.15.11-50
yast2-tv-2.16.0-21
yast2-network-2.16.10-2
yast2-users-2.16.3-5
yast2-samba-server-2.16.0-21
yast2-xml-2.16.0-3
yast2-add-on-2.16.0-16
yast2-sudo-2.15.3-112
yast2-control-center-qt-2.15.6-11
yast2-theme-openSUSE-2.15.14-26
yast2-trans-stats-2.15.0-41
yast2-pkg-bindings-2.16.4-3
yast2-ldap-2.15.1-102
yast2-storage-2.16.5-5
yast2-ca-management-2.16.3-7
yast2-nfs-server-2.15.4-46
yast2-support-2.15.3-36
yast2-bootloader-2.16.2-11
yast2-kerberos-client-2.16.0-17
yast2-tune-2.15.7-45
yast2-samba-client-2.16.1-7
yast2-registration-2.16.0-9
yast2-dns-server-2.16.0-6
yast2-inetd-2.15.1-66
yast2-core-2.16.7-3
yast2-trans-de-2.15.28-6
yast2-mouse-2.16.0-7
yast2-pam-2.16.0-18
yast2-sysconfig-2.15.3-79
yast2-fingerprint-reader-2.16.1-15
yast2-ntp-client-2.16.2-3
yast2-installation-2.16.4-2
yast2-packager-2.16.9-4
yast2-hardware-detection-2.15.8-55
yast2-qt-2.16.3-3
yast2-2.16.12-2
yast2-update-2.16.1-10
yast2-firewall-2.15.8-29
yast2-iscsi-client-2.16.2-3
yast2-ldap-client-2.16.4-3
yast2-profile-manager-2.16.0-8
yast2-ldap-server-2.15.5-98
yast2-ftp-server-2.15.9-49
yast2-trans-en_US-2.15.5-14
yast2-slp-2.15.0-53
yast2-printer-2.16.5-2
yast2-irda-2.15.1-116
yast2-tftp-server-2.14.0-126
yast2-security-2.15.1-46
autoyast2-2.16.2-8
yast2-online-update-frontend-2.16.5-3
yast2-mail-2.15.23-28
yast2-schema-2.15.0-156
yast2-perl-bindings-2.16.0-23
yast2-country-2.16.2-5
yast2-bluetooth-2.15.4-39
yast2-scanner-2.15.5-64
autoyast2-installation-2.16.2-8
yast2-restore-2.16.0-9
yast2-online-update-2.16.5-3
yast2-http-server-2.15.7-53

Desktop is Gnome, yast UI is Qt

Created attachment 184861 [details]
yast2 logs

A segfault "at YCP file Wizard.ycp:1002" is not a problem
in the yast2-scanner package.

It might be a problem of the package which contains Wizard.ycp
(the yast2 RPM contains /usr/share/YaST2/modules/Wizard.ycp)
but the actual reason might be also somewhere else.

Comment #1 shows "openSUSE 10.3.1 (i586) Alpha0"
but the report is for "openSUSE 11.0".
I close it now as INVALID because it looks like nonsense.

Ooops!
Right now I learned that "openSUSE 10.3.1" means in fact
"openSUSE 11.0 pre-release" so that it seems to be correct
that the report is for "openSUSE 11.0".

Now at 

cat /etc/SuSE-release
openSUSE 11.0 (i586) Alpha0
VERSION = 11.0
uname -r
2.6.24-rc3-git1-2-default
rpm -qa | grep yast
yast2-backup-2.15.5-0.1
yast2-gtk-2.15.9-53
yast2-transfer-2.14.0-130
yast2-ntp-client-2.16.2-5
yast2-theme-openSUSE-2.15.14-28
yast2-ca-management-2.16.3-9
yast2-qt-2.16.5-3
yast2-trans-de-2.15.28-7
yast2-printer-2.16.6-3
yast2-2.16.14-3
yast2-profile-manager-2.16.0-10
yast2-ldap-server-2.15.5-100
yast2-nis-client-2.16.0-19
yast2-samba-client-2.16.1-9
yast2-sound-2.16.1-13
yast2-packager-2.16.10-3
yast2-security-2.15.1-48
yast2-ncurses-2.16.3-3
yast2-installation-2.16.5-3
yast2-control-center-gnome-2.13.2-122
yast2-tftp-server-2.14.0-128
yast2-pkg-bindings-2.16.4-5
yast2-users-2.16.3-7
yast2-bluetooth-2.15.4-41
yast2-trans-stats-2.15.0-42
yast2-x11-2.15.11-52
yast2-online-update-2.16.5-5
yast2-ldap-2.15.1-104
yast2-registration-2.16.0-11
yast2-inetd-2.15.1-68
yast2-dns-server-2.16.0-8
yast2-tune-2.15.7-47
yast2-samba-server-2.16.0-23
yast2-country-2.16.2-7
yast2-mouse-2.16.0-9
yast2-sysconfig-2.15.3-81
yast2-storage-2.16.6-3
yast2-scanner-2.15.5-66
yast2-firewall-2.15.8-31
yast2-trans-ru-2.15.25-7
yast2-control-center-2.16.0-3
yast2-sudo-2.15.3-114
yast2-perl-bindings-2.16.0-25
autoyast2-installation-2.16.2-10
yast2-nfs-client-2.15.0-48
yast2-nfs-server-2.15.4-48
yast2-storage-lib-2.16.6-3
yast2-fingerprint-reader-2.16.1-17
yast2-control-center-qt-2.16.0-3
yast2-restore-2.16.0-11
yast2-xml-2.16.0-4
yast2-core-2.16.10-2
yast2-ftp-server-2.15.9-51
yast2-runlevel-2.16.0-11
yast2-metapackage-handler-0.7.3-9
yast2-tv-2.16.0-23
yast2-update-2.16.1-12
yast2-kerberos-client-2.16.0-19
yast2-bootloader-2.16.2-13
yast2-pam-2.16.0-20
yast2-add-on-2.16.0-18
yast2-irda-2.15.1-118
yast2-network-2.16.10-4
yast2-trans-en_US-2.15.5-15
yast2-support-2.15.3-38
yast2-hardware-detection-2.16.0-3
yast2-iscsi-client-2.16.2-5
yast2-slp-2.15.0-55
yast2-mail-2.15.23-30
yast2-schema-2.15.0-156
yast2-repair-2.16.2-10
yast2-online-update-frontend-2.16.5-5
yast2-apparmor-2.1-50
yast2-http-server-2.15.7-55
autoyast2-2.16.2-10
yast2-dhcp-server-2.15.5-43
yast2-ldap-client-2.16.4-5

and problem persists

Why is it again assigned to me?
Read comment #3!

The affected line (mentioned in the log) is:

if ( UI::WidgetExists(`id(`next ) ) )

Stefan, I guess a mod-UI migration issue (with qt)

I just checked the isolated code snippets, and they work fine for me: UI::WidgetExists() as well as UI::WizardCommand(`EnableNextButton(...)).

The reported case above I can't test because I don't have the relevant hardware.

Johannes, please check if you can reproduce the problem with the current version. To me this looks very much like inconsistent library versions or something like that. AFAIK we didn't release any official Alpha etc. yet.

We cannot reproduce it.

We think the reason is whatever transient inconsistency in the
YaST machinery which can happen when you use a system
based upon whatever "factory" snapshot.

For example when a new YaST base packages are submitted,
it takes some time until all dependant YaST modules are
re-built so that your particular "factory" snapshot
might have some newest YaST base packages but some old
dependant YaST modules installed.

I close the report now as WONTFIX.

Please reopen it or file a new report if it still happens
for an explicite "alpha" or "beta" openSUSE release.