[Bug 421794] New: YaST got signal 11 at YCP file Popup.ycp:343
https://bugzilla.novell.com/show_bug.cgi?id=421794 Summary: YaST got signal 11 at YCP file Popup.ycp:343 Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: wharms@bfs.de QAContact: jsrain@novell.com Found By: --- Created an attachment (id=236435) --> (https://bugzilla.novell.com/attachment.cgi?id=236435) yast2 log file last minutes until crash YaST got signal 11 at YCP file Popup.ycp:343 /sbin/yast2: line 421: 31505 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS while trying to setup a new source ... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=421794
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=421794
User lslezak@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c1
Ladislav Slezak
https://bugzilla.novell.com/show_bug.cgi?id=421794
User wharms@bfs.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c2
--- Comment #2 from a b
https://bugzilla.novell.com/show_bug.cgi?id=421794
User lslezak@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c3
Ladislav Slezak
https://bugzilla.novell.com/show_bug.cgi?id=421794
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c4
Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=421794
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c5
--- Comment #5 from Stefan Hundhammer
The problem seems to be in YWidget::isValid()
Uh - no, that's where a previous problem gets _reported_. Typically this kind of thing is due to memory corruption. This in turn might be the result of libraries that are not as binary compatible as they should. Did anybody who is in a position to reproduce the problem run valgrind? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=421794
User wharms@bfs.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c6
--- Comment #6 from a b
rpm -qa | grep yast2 yast2-storage-lib-2.16.26-0.1 yast2-storage-2.16.26-0.1 yast2-x11-2.15.12-15.1 yast2-installation-2.16.50-3.1 yast2-http-server-2.16.9-10.1 yast2-transfer-2.16.1-76.1 yast2-pam-2.16.2-17.1 yast2-registration-2.16.7-4.1 yast2-users-2.16.33-6.1 yast2-add-on-2.16.8-6.1 yast2-2.16.71-6.1 yast2-tftp-server-2.16.0-26.1 yast2-ntp-client-2.16.9-11.1 yast2-samba-client-2.16.9-3.1 autoyast2-installation-2.16.19-0.1 yast2-country-data-2.16.26-6.1 yast2-ncurses-2.16.27-8.1 yast2-xml-2.16.1-14.1 yast2-ldap-client-2.16.16-6.1 yast2-core-2.16.51-6.1 yast2-vm-2.16.5-7.1 yast2-irda-2.16.1-25.1 yast2-online-update-2.16.15-6.1 yast2-dns-server-2.16.4-14.1 yast2-inetd-2.16.0-27.1 yast2-gtk-2.16.14-1.2 yast2-metapackage-handler-0.8.5-16.1 yast2-nfs-common-2.16.1-6.1 yast2-support-2.16.1-6.1 yast2-mouse-2.16.1-26.1 yast2-runlevel-2.16.5-15.1 yast2-bootloader-2.16.20-0.1 yast2-control-center-gnome-2.13.3-11.1 yast2-trans-stats-2.15.0-87.1 yast2-libyui-2.16.48-3.1 yast2-sound-2.16.11-6.1 yast2-firewall-2.16.2-25.1 yast2-update-2.16.10-4.1 yast2-nis-server-2.16.4-22.1 yast2-samba-server-2.16.3-15.1 yast2-pkg-bindings-2.16.40-0.2 yast2-slp-2.16.0-25.1 yast2-perl-bindings-2.16.7-14.1 yast2-nfs-client-2.16.1-26.1 yast2-country-2.16.26-6.1 yast2-tv-2.16.6-7.1 yast2-iscsi-client-2.16.14-6.1 yast2-backup-2.16.5-7.1 yast2-phone-services-2.16.0-27.1 yast2-dhcp-server-2.16.7-38.1 yast2-control-center-qt-2.16.2-11.1 yast2-schema-2.15.0-227.1 yast2-theme-openSUSE-2.16.38-2.1 yast2-repair-2.16.12-4.1 yast2-qt-2.16.53-5.1 yast2-sysconfig-2.16.0-28.1 yast2-packager-2.16.53-3.1 yast2-nfs-server-2.16.1-6.1 yast2-network-2.16.48-3.1 yast2-restore-2.16.2-26.1 yast2-profile-manager-2.16.1-27.1 yast2-control-center-2.16.2-11.1 yast2-ncurses-pkg-2.16.14-0.2 autoyast2-2.16.19-0.1 yast2-ycp-ui-bindings-2.16.47-5.1 yast2-hardware-detection-2.16.1-49.1 yast2-apparmor-2.16.4-4.1 yast2-security-2.16.1-16.1 yast2-online-update-frontend-2.16.15-6.1 yast2-mail-2.16.6-2.1 yast2-qt-pkg-2.16.47-0.2 yast2-trans-de-2.16.17-0.1 yast2-ldap-2.16.0-52.1 yast2-kerberos-client-2.16.11-9.1 yast2-tune-2.16.2-2.1 yast2-sudo-2.16.1-27.1 yast2-scanner-2.16.10-13.1 yast2-nis-client-2.16.3-6.1 yast2-printer-2.16.32-3.1
-- 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.
https://bugzilla.novell.com/show_bug.cgi?id=421794
User wharms@bfs.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c7
--- Comment #7 from a b
https://bugzilla.novell.com/show_bug.cgi?id=421794
User wharms@bfs.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c8
a b
https://bugzilla.novell.com/show_bug.cgi?id=421794
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c9
Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=421794
User rpmcruz@alunos.dcc.fc.up.pt added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c10
Ricardo Cruz
https://bugzilla.novell.com/show_bug.cgi?id=421794
User wharms@bfs.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c11
a b
https://bugzilla.novell.com/show_bug.cgi?id=421794
User rpmcruz@alunos.dcc.fc.up.pt added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c12
--- Comment #12 from Ricardo Cruz
https://bugzilla.novell.com/show_bug.cgi?id=421794
User rpmcruz@alunos.dcc.fc.up.pt added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c13
--- Comment #13 from Ricardo Cruz
https://bugzilla.novell.com/show_bug.cgi?id=421794
User rpmcruz@alunos.dcc.fc.up.pt added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c14
--- Comment #14 from Ricardo Cruz
https://bugzilla.novell.com/show_bug.cgi?id=421794
User rpmcruz@alunos.dcc.fc.up.pt added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c15
--- Comment #15 from Ricardo Cruz
https://bugzilla.novell.com/show_bug.cgi?id=421794
User rpmcruz@alunos.dcc.fc.up.pt added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c16
--- Comment #16 from Ricardo Cruz
What's strange in ab's stack is that YWidget::isValid() is called from YDialog::waitForEvent(int), but there must have been a YDialog::filterInvalidEvents() call in between the two. I'm going to assume miracle or compiler optimization and will focus in the test case we have.
Okay, I can reproduce ab's stack in a 32-bit system. Weird. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=421794
User rpmcruz@alunos.dcc.fc.up.pt added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c17
--- Comment #17 from Ricardo Cruz
https://bugzilla.novell.com/show_bug.cgi?id=421794
User rpmcruz@alunos.dcc.fc.up.pt added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c18
Ricardo Cruz
https://bugzilla.novell.com/show_bug.cgi?id=421794
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c19
--- Comment #19 from Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=421794
User rpmcruz@alunos.dcc.fc.up.pt added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c20
Ricardo Cruz
https://bugzilla.novell.com/show_bug.cgi?id=421794
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c21
--- Comment #21 from Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=421794
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c22
--- Comment #22 from Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=421794
User mmeeks@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c23
--- Comment #23 from Michael Meeks
https://bugzilla.novell.com/show_bug.cgi?id=421794
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c24
--- Comment #24 from Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=421794
User rpmcruz@alunos.dcc.fc.up.pt added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c25
--- Comment #25 from Ricardo Cruz
With the changes from comment #22, this should not happen any more. But I'd rather be safe than sorry.
filterInvalidEvents() is important mostly for making sure that events belonging to a dialog that is now in the background are not delivered when a new dialog is now open. This is a rare situation, but it might happen:
(1) Dialog A open (2) User clicks on widgets in dialog A (but not delivered yet - no UserInput()) (3) Dialog B opens on top of dialog A (4) UserInput() in dialog B
Yeah, I bet that's what happen to ab, as from comment 13. It wouldn't happen in the Qt UI because you guys don't let Qt process user events when in YUI::idleLoop() which is the only instance when cpu is given to the toolkit but events aren't processed. But it's a good idea to safeguard Qt as well to prepare for any future disruption as well as for possible events that may be triggered by a timeout or anything triggered internally. Thanks for the libyui changes btw! -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=421794
User rpmcruz@alunos.dcc.fc.up.pt added comment
https://bugzilla.novell.com/show_bug.cgi?id=421794#c26
Ricardo Cruz
participants (1)
-
bugzilla_noreply@novell.com