Summary: | Profiles and realtime preview not working | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Sebastian Gauna <gaunas> |
Component: | emulation | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | a.samirh78, b.pedini, kdebugs, nate, rikmills, tynach2, wbauer1 |
Priority: | NOR | ||
Version: | 20.12.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Sebastian Gauna
2020-12-16 07:01:50 UTC
Yeah, I noticed this too. Glad a bug report already exists for it. This worked last month. I'm assuming Konsole - or something related - was updated recently and that's when it broke. Changes to profiles in general seem to not be applied until a new terminal is opened with that profile, either in a new window or a new tab. Start konsole from another konsole window (if you have "Run all konsole windows in a single process" enabled, you'll need to start konsole from another terminal emulator (xterm, gnome-terminal...etc)); do you get output like: 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 Applying profile QObject::connect: signal not found in Konsole::ProfileManager if so, then it's similar to https://invent.kde.org/utilities/konsole/-/merge_requests/183#note_92561 @Ahmad Samir, I did what you say and I just got: 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 That's it. Same issue here with different computers: profiles are not launching from konsole tab. Although they can be launched from konsole profiles widget. If I start konsole from the command line it shows these messages: $ 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 This can be worked around by changing/tweaking the build flags, see the MR I linked for more details. Profiles can't be launched from the konsole profile tab, but they can be launched from the menu option "New Tab" / profile_name. When I go to the "Change Profile", I am seeing some profiles duplicated, but not all of them. There are no duplicities on "Profile Managament". None of them are working on the "Change Profile" menu. Upgraded konsole & konsole-part to 4:20.12.0+p20.04+git20210103.0056-0 and these problems disappeared and no error messages at konsole launch. From site https://origin.archive.neon.kde.org/testing/pool/main/k/konsole/ Thanks! *** Bug 431264 has been marked as a duplicate of this bug. *** I just applied the update from today and Kosole was updated to v4.20.12.1 The problem seems to be solved. (In reply to rbnmndz from comment #4) > Same issue here with different computers: profiles are not launching from > konsole tab. Although they can be launched from konsole profiles widget. > > If I start konsole from the command line it shows these messages: > $ 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 I remember seeing the same error messages with 20.12.0, but they disappeared when I added https://invent.kde.org/utilities/konsole/-/commit/3f2b2d9df4ca74baa0d263c36dc70d95c149b221 to fix bug#424986. That commit is part of 20.12.1, and fixed the problems with switching profiles. But, the color schemes are still not applied immediately, you have to click Apply or Cancel first. In previous versions, selecting a different color scheme changed the colors in the window directly, they were changed back if you clicked Cancel. @Wolfgang, was that an issue with the "Default" (the fallback/built-in) profile? if so it should be fixed by https://invent.kde.org/utilities/konsole/-/commit/5ab8423139467ad97d87d00dc82a85f91c5a1492 Closing, per comment#9, if there are still issues please create a new report. |