Bug 141018

I have observed the same problem.

I think this is ppc only, will check

No, I have reproduced it on i386.

Thats bad to hear. There was almost no change in i386 code since then.
May be a change in CWMTab and such is the cause

Yes it´s in  CWMTab

    bootloader/routines/dialogs.ycp:115 return_tab set to nil

Problem is somewhere here in CWMTab.ycp:

global define symbol Handle (map<string,any> widget, string key, map event) {
    list<string> all_tabs = widget["tabs_list"]:[];
    symbol h_ret = TabHandle (current_tab_map, event);
    if (h_ret != nil)
        return h_ret;
    any ret = event["ID"]:nil;
    if (is (ret, string) && contains (all_tabs, (string)ret) &&
        // At initialization, qt thinks it has switched to the same tab
        // So prevent unnecessary double initialization
        ret != current_tab_id)
    {
        if (! TabValidate (current_tab_map, event))
        {
            MarkCurrentTab ();
            return nil;
        }
        TabStore (current_tab_map, event);

        InitNewTab ((string) ret, widget);
    }
    return nil;
}

It looks like there are two events and the second has a bad "ID". 

mvidner: Could you have a look. please? May be the Hnadle function needs some more
event filtering?
I do not fully understand the code but maybe it´s related to the new fake event:

r26170 | mvidner | 2005-11-15 18:52:45 +0100 (Tue, 15 Nov 2005) | 12 lines

CWM:
- added `menu_button
- explicitly specifying an empty help produces no errors, like no_help
- actually implemented validate_help
- added validate_type: `function_no_popup so that the function bodies
  can be shared and only validate_help needs to differ
CWMTab:
- widget_names is now optional
- generate a fake event when switching to a new tab to allow a handler
  to enabled/disable widgets before the first real UserInput takes place
- prevent double tab initialization at tab set initialization

Actually the cause is the new CleanUp function of Nov 2. It was needlessly smashing current_tab_id. But thanks for the hint!

I'll join this one to the original report.

*** This bug has been marked as a duplicate of 134136 ***

wrong number

*** This bug has been marked as a duplicate of 134386 ***