Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#16422 closed bug (fixed)

Terminal crashes after setting font size and colors

Reported by: roiredxsoto Owned by: waddlesplash
Priority: normal Milestone:
Component: Kits/Interface Kit Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by humdinger)

Good day,

Issue:

  • Expected behavior: Launch terminal, change font size. Save as defaults. Close Terminal. Launch Terminal again, everything is fine.
  • Observed behavior: Launch terminal, change font size. Save as defaults. Close Terminal. Launch Terminal again, Terminal crashes.

Removing files from /boot/home/config/settings/Terminal (files Default and Windows) resets the Terminal to default state and allows terminal to Boot without issues. Actually,

Changing the colors does not affect at all. Only changing font size causes the issue.

This issue started to happen just now, after update to 54446. Never noticed it before.

~> uname -a Haiku hawku 1 hrev54446 Jul 20 2020 06:41:14 x86_64 x86_64 Haiku

Attached is the report thrown by the Terminal

Attachments (1)

Terminal-1753-debug-20-07-2020-11-43-08.report (12.1 KB ) - added by roiredxsoto 4 years ago.
Terminal crash bug report

Download all attachments as: .zip

Change History (9)

by roiredxsoto, 4 years ago

Terminal crash bug report

comment:1 by humdinger, 4 years ago

Component: - GeneralApplications/Terminal
Description: modified (diff)
Owner: changed from nobody to jackburton
Version: R1/beta2R1/Development

Not reproducible with Beta2, 32bit (hrev54154+116).

comment:2 by waddlesplash, 4 years ago

Component: Applications/TerminalKits/Interface Kit
Owner: changed from jackburton to waddlesplash
Status: newassigned

Actually an Interface Kit bug, seems to be my fault.

comment:3 by roiredxsoto, 4 years ago

Ok. Let me know if I can provide any more info. Thanks. Regards, RR

comment:4 by waddlesplash, 4 years ago

This should be fixed in hrev54472, please test.

comment:5 by roiredxsoto, 4 years ago

Good day @waddlesplash,

Looks like it's fixed now on hrev54473. I presume you can close the ticket as solved.

Thanks a lot.
Regards,
RR

comment:6 by waddlesplash, 4 years ago

Resolution: fixed
Status: assignedclosed

comment:7 by nielx, 4 years ago

Milestone: UnscheduledR1/beta3

Assign fix to milestone:R1/beta3, as it looks like this fix will be part of that release.

As we started with the previous beta, we would like to use the Milestone field for fixed tickets to log from which release the improvement will be out. Therefore it is very much appreciated to assign the milestone when closing a ticket as fixed.

comment:8 by nielx, 4 years ago

Milestone: R1/beta3

Reverting ticket update, it seems to be a fix to a regression added _after_ milestone:R1/beta2, so it would be incorrect to add this to the list of fixes in milestone:R1/beta3.

My apologies for the noise.

Note: See TracTickets for help on using tickets.