Bug 203541

What kind of popup is that?

An object of type "message" inside the patch?
An "ins_notify" popup for a patch?

It is a Message object, [message]kernel-patch-message-2-1836-1 in
http://ftp.gwdg.de/pub/suse/update/10.1/repodata/patch-kernel-1836.xml

AFAIK those messages are supposed to be displayed when the respective patch is being installed, not when the user selects that patch.

That only makes sense: If you warn the user that he should reboot now, you want to do that when the kernel that is to be rebooted is installed, not before.

So this is not a problem of the PackageSelector widget, but of the online update (ex-YOU) workflow. IIRC we did have the capability to display message objects in the old YOU. I am not sure about the status of that after the ZYPP migration.

Jiri?

But yast2-ncurses DID display the popup.

But this is not about the 'reboot' information (this is shown by YOU if it finds "reboot_needed" flag in the patch). This is about the message the patch should show - and YOU has no special handling for that. The ncurses popup shown in the other bug is OnlineUpdateDialogs::MessagePopup, invoked by MessageCallback. I don't know why it wasn't shown this time, but you say in comment #4 of bug 196201 that the patch was not selected - this would be logical reason for not showing popup.

curses makes zypp select message
qt doesn't make zypp select message
Stefan please solve the bug with local zypp hackers

Really strange.

Since the message is part of a patch, I don't see how it can make any difference whether the patch is selected by the Qt UI or by the NCurses UI.

Michael, Schubi, any ideas?

According to bug #196201, this popup is a patch message, so this issue is clearly out of reach of the Qt package selector. As you can see in the screen shot in bug #196201 comment #4, this happens during patch installation, long after the package selector. That code is not specific to y2-qt or y2-ncurses.

It might be that the message (the message atom) did not get selected for installation, then it would be a solver issue, or that it did get selected, but never got displayed (hard to imagine why this should happen - unlikely IMHO), then it would be a problem of the online update workflow or libzypp.

My bets are on the solver.

Without logfiles I cannot do very much. I have tested it very often without problems.

Martin, I have tested with QT and it has worked.
(fresh 10.1 installation, kernel update with official mirror)
Feel free to reopen the bug if you can reproduce the bug and attach the logfiles.

Sorry for the late reply.

> Without logfiles I cannot do very much.

The logs are in the original bug 196201. Do you need more of them?

> I have tested with QT and it has worked.

Just to make sure: did you indeed see the "lilo" message which should appear when _installing_ the kernel, not the preinstall notification when _selecting_ it?

comment #4 : Yes, first the rebooting stuff while selecting and the the second lilo stuff after installation.

From my logfile:

2006-10-19 04:57:27 <0> aries(7284) [zypp] PathInfo.cc(_Log_Result):295 unlink /var/lib/zypp/db/languages/71095c56c641f2c4a4f189b9dfcd7a38
2006-10-19 04:57:27 <1> aries(7284) [YCP] OnlineUpdateDialogs.ycp:558 Going to open the message dialog
2006-10-19 04:57:27 <1> aries(7284) [YCP] OnlineUpdateDialogs.ycp:573 Dialog opened
2006-10-19 04:59:27 <1> aries(7284) [target] TargetImpl.cc(commit):404 Displaying the text 'If you are using the LILO bootloader, please execute
2006-10-19 04:59:27 <1> aries(7284) [target] TargetImpl.cc(commit):404 /sbin/lilo after installing the update kernel and prior to
2006-10-19 04:59:27 <1> aries(7284) [target] TargetImpl.cc(commit):404 rebooting
2006-10-19 04:59:27 <1> aries(7284) [target] TargetImpl.cc(commit):404 '

The logfiles of bug 196201 are very old. Meanwhile I have fixed the same bug in bug  192535 concerning scripts. The behaviour between message and scripts are the same in the solver. 
I have tested the newest OFFICIAL libzypp patch which are on the our mirrors.