Summary: | Profile Manager doesn't show the Default/fallback profile | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Patrick Silva <bugseforuns> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | a.samirh78, nate |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Patrick Silva
2020-11-22 12:00:06 UTC
This is intentional; the "Default" profile is created using the default settings directly from the C++ code, it doesn't have a .profile like other ones. When you modify the default profile, if you didn't enter a name, then something generic like "Profile 1" (or "Profile 2" ... etc) is used when saving. The "Default" (fallback) profile is supposed to be always available in case the user wants to start with a fresh profile. I see two issues here: - Changing the appearance settings doesn't seem to get applied to the default profile - It looks a bit confusing if the "Default" profile is available in the context menus, but not in the the Profile Manager; I think we should show it, and just disable the "Edit" button for it (with a tooltip explaining that it's a static/read-only fallback profile) Does changing the font settings for profiles other than Default get applied after saving the settings? (In reply to Ahmad Samir from comment #1) > Does changing the font settings for profiles other than Default get applied > after saving the settings? I have just changed font settings of "Profile 1" created after my steps and again the changes only had effect after restarting Konsole. (In reply to Patrick Silva from comment #2) > (In reply to Ahmad Samir from comment #1) > > Does changing the font settings for profiles other than Default get applied > > after saving the settings? > > I have just changed font settings of "Profile 1" created after my steps > and again the changes only had effect after restarting Konsole. Could you run konsole from another terminal and see if you get something like: QObject::connect: signal not found in Konsole::ProfileManager https://invent.kde.org/utilities/konsole/-/merge_requests/183 yes, here is the output: $ konsole QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileList QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileManager OK. Please open a separate report for the signals' issue, and let's keep this one for the Default profile issue. Thanks :) (In reply to Ahmad Samir from comment #1) > I think we should show it, and just disable the "Edit" button for it (with a tooltip explaining > that it's a static/read-only fallback profile) implemented in Konsole 21.08 RC. |