Opened 10 years ago

Last modified 20 months ago

#3362 assigned bug

[InstallerCD] Artifacts after leaving KDL (easy)

Reported by: Adek336 Owned by: nobody
Priority: low Milestone: R1
Component: Servers/app_server Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

The screen does not redraw itself after leaving KDL in installer CD. Even if F12 will be disabled, a panic might occur in the installer and the user may want continue anyway, then he'd get the ugly artifact (although installing operating systems after a kernel panic is risky business)

Attachments (1)

img_1881.jpg (67.6 KB) - added by Adek336 10 years ago.

Download all attachments as: .zip

Change History (7)

Changed 10 years ago by Adek336

Attachment: img_1881.jpg added

comment:1 Changed 10 years ago by idefix

I think that's because Tracker isn't running. I get the same effect on my Haiku hrev28974 installation when I quit Tracker and then enter and leave KDL.

comment:2 Changed 8 years ago by diver

Component: - GeneralAdd-Ons
Version: R1/pre-alpha1R1/Development

Still here in hrev42124. See also #1421.
It seems that invalidate_on_exit kernel debugger add-on should take this situation into account.

comment:3 in reply to:  2 Changed 8 years ago by mmlr

Replying to diver:

Still here in hrev42124. See also #1421.
It seems that invalidate_on_exit kernel debugger add-on should take this situation into account.

The debugger add-on can't do much about it, it just sends the app_server the notification that KDL was exited. The app_server then marks the whole screen as invalid to trigger a redraw. But since there aren't any windows that actually fill the area behind the installer window this area just isn't redrawn. When booted to the desktop, the Tracker desktop window is there to fill the full area (unless you quit the Tracker as was mentioned above).

The app_server could check for such a situation, or it could just always fill with the desktop background (as it already does when booting). It's not really critical. Far more critical would be to actually fix all the issues that trigger the KDL in the first place...

comment:4 Changed 7 years ago by diver

Component: Add-OnsServers/app_server

comment:5 Changed 4 years ago by pulkomandy

Priority: normallow
Summary: [InstallerCD] Artifacts after leaving KDL[InstallerCD] Artifacts after leaving KDL (easy)

Marking as easy since this sounds like there shouldn't be too much work involved. Also setting priority to low, as I'm even surprised we bothered to implement invalidate_on_exit at all.

comment:6 Changed 20 months ago by axeld

Owner: changed from axeld to nobody
Status: newassigned
Note: See TracTickets for help on using tickets.