![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1206949 http://bugzilla.opensuse.org/show_bug.cgi?id=1206949#c11 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |lslezak@suse.com, | |shundhammer@suse.com --- Comment #11 from Michael Andres <ma@suse.com> --- (In reply to Stefan Hundhammer from comment #9)
According to the y2log, all 3 callbacks are registered as they should be.
To me this leaves only one conclusion: The end callback was never called, so the pop-up remained open.
@YAST, Huha, Ladislav: Please keep in mind that any! ZYPP Report might be interrupted by an Exception and so not be able to complete the intended workflow sequence. We try to avoid this, but this may always happen. There are just 2 methods you can rely on always being called (from a Reports Ctor/Dtor): virtual void ReceiveReport<Tp>::reportbegin(); virtual void ReceiveReport<Tp>::reportend(); So at least a reportend() should trigger cleanup that must be performed on your side (like a popdown) no matter how a workflow ended. --- Apart from this there is indeed an unintended change in the ProgressReports behaviour. We'll try to figure out why and fix it. -- You are receiving this mail because: You are on the CC list for the bug.