Bug 429496 - Profile Manager doesn't show the Default/fallback profile
Summary: Profile Manager doesn't show the Default/fallback profile
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-22 12:00 UTC by Patrick Silva
Modified: 2021-08-05 17:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2020-11-22 12:00:06 UTC
1. create a new user account on your system (or you can just delete the Konsole settings in your current user account and skip to step 4. I'm not sure.)
2. logout
3. start Plasma session with the new user account
4. open Konsole
5. click on "Settings" menu, choose "Edit current profile..."
6. click on "Appearance" in the left side
7. click on "Choose..." button
8. set font style to Bold and font size to 16
9. click on "Ok" button, click on "Ok" button again (notice that font settings
were not applied yet - another bug?)
10. restart Konsole
11. open "File" menu, hover over "New tab": submenu lists two options, "Default" and "Profile 1"
12. click on "Settings" menu, choose "Manage profiles...": the only profile listed
is "Profile 1". There is no profile called "Default".

EXPECTED RESULT:
"New tab" submenu of "File" menu should only list profiles present
in "Manage profiles..." window.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.20.80
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.1
Comment 1 Ahmad Samir 2020-11-22 13:51:44 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?
Comment 2 Patrick Silva 2020-11-22 14:05:48 UTC
(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.
Comment 3 Ahmad Samir 2020-11-22 14:17:31 UTC
(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
Comment 4 Patrick Silva 2020-11-22 14:26:09 UTC
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
Comment 5 Ahmad Samir 2020-11-22 15:00:38 UTC
OK. Please open a separate report for the signals' issue, and let's keep this one for the Default profile issue.

Thanks :)
Comment 6 Patrick Silva 2021-08-05 17:26:54 UTC
(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.