https://bugzilla.novell.com/show_bug.cgi?id=483942 User locilka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483942#c483211 Summary: UI::DumpWidgetTree call Aborts if no dialog exists Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: kmachalkova@novell.com ReportedBy: locilka@novell.com QAContact: jsrain@novell.com CC: abittner@stud.fh-heilbronn.de, tgoettlicher@novell.com Found By: Development Created an attachment (id=278500) --> (https://bugzilla.novell.com/attachment.cgi?id=278500) YaST log Sounds like a feature but in some circumstances it is a bug. This has been originally reported as bug #483211: Description: Automatic Configuration calls several YaST scripts, one of the scripts accidentally closes the current dialog and tries to debug what has happened by calling a debugging function UI::DumpWidget to get something useful to logs. However, UI::DumpWidget finds out there's no dialog present and aborts. Sadly - in the middle of second stage installation. Solution: Debugging function should not abort YaST. From YaST point of view, it should log an error and just keep going. Test file dump.ycp: ------------------------------------- { UI::OpenDialog(`Label("yes/no")); UI::CloseDialog(); UI::DumpWidgetTree(); } ------------------------------------- Test: /usr/lib/YaST2/bin/y2base ./dump.ycp qt terminate called after throwing an instance of 'YUINoDialogException' what(): No dialog existing YaST got signal 6 at YCP file /yast/test/dump.ycp:4 Aborted -- 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.