[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #23 from Joe S --- (In reply to Mykola Krachkovsky from comment #21) > If you use openSUSE Tubleweed, you can either > 1. Install older KRDC (krdc5 — 23.08.4) from this repo: > https://download.opensuse.org/repositories/home:/wolfi323:/branches:/KDE:/ > Frameworks5/openSUSE_Tumbleweed/ > Which could be installed simultaneously with KRDC based on KF6. > OR > 2. Install develompent version from > https://download.opensuse.org/repositories/KDE:/Unstable:/Applications/ > KDE_Unstable_Frameworks_openSUSE_Factory/ > But in my experience this version has problems with mouse input with scaling > or multiple screens (not sure) on wayland session at least. Thanks for providing those options. I missed getting krdc 23.* version from the TW history repos before it was gone and was not aware of those. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #20 from Joe S --- (In reply to Tilman Vogel from comment #17) > Broken on openSUSE Tumbleweed 20240524. > Thanks to https://bugs.kde.org/show_bug.cgi?id=482950#c10 for the workaround! Some additional details using other linux distros. In all cases I am attempting to connect to the TW 20240524 test machine from the other test machine. Using a Debian 12 ( BookWorm ) test machine which is using plasma 5.27.5 and krdc 22.12.3 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a Debian SID ( Trixie ) test machine which is using plasma 5.27.10 and krdc 23.08.3 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. After updating Debian SID test machine to latest version which is using plasma 5.27.11 and krdc 23.08.3 I retested to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a EndeavourOS test machine which is using plasma 6.0.5 and krdc 24.05.0 to the TW test machine running TW 20240524 FAILS and just displays the BLUE screen but displayed the following messages KRDC: Starting RDP session [12:45:38:623] [1674:1674] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_RGBA32 [12:45:38:623] [1674:1674] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32 [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded pulse backend for rdpsnd [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpsnd [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel audin [12:45:38:626] [1674:1674] [INFO][com.freerdp.channels.audin.client] - Loaded pulse backend for audin [12:45:38:626] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx Using a Manjaro test machine which is using plasma 6.0.5 and krdc 24.0.5.0 to the TW test machine running TW 20240524 FAILS and coredumps Using a openSUSE MicroOS KDE test machine which is using plasma 6.0.4 and krdc 24.02.2 to the TW test machine running TW 20240524 FAILS and coredumps. Using a Ubuntu 23.10 test machine which is using plasma 5.27.8 and krdc 23.08.1 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a Windows 11 test machine and the Microsoft Remote Desktop client to the TW test machine running TW 20240524 WORKS and the desktop is displayed. So in summary, these tests show that The problem is occurs with other Linux distros that are using plasma 6 and krdc 24.* The problem does NOT occur with other Linux distros that are still using plasma 5 and krdc 23.* Even the Windows 11 RDP client WORKS I'm not sure what other information the developers could possibly need to get this problem addressed. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 Joe S changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #19 from Joe S --- (In reply to Tilman Vogel from comment #17) > Broken on openSUSE Tumbleweed 20240524. > Thanks to https://bugs.kde.org/show_bug.cgi?id=482950#c10 for the workaround! Some additional details using other linux distros. In all cases I am attempting to connect to the TW 20240524 test machine from the other test machine. Using a Debian 12 ( BookWorm ) test machine which is using plasma 5.27.5 and krdc 22.12.3 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a Debian SID ( Trixie ) test machine which is using plasma 5.27.10 and krdc 23.08.3 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. After updating Debian SID test machine to latest version which is using plasma 5.27.11 and krdc 23.08.3 I retested to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a EndeavourOS test machine which is using plasma 6.0.5 and krdc 24.05.0 to the TW test machine running TW 20240524 FAILS and just displays the BLUE screen but displayed the following messages KRDC: Starting RDP session [12:45:38:623] [1674:1674] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_RGBA32 [12:45:38:623] [1674:1674] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32 [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded pulse backend for rdpsnd [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpsnd [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel audin [12:45:38:626] [1674:1674] [INFO][com.freerdp.channels.audin.client] - Loaded pulse backend for audin [12:45:38:626] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx Using a Manjaro test machine which is using plasma 6.0.5 and krdc 24.0.5.0 to the TW test machine running TW 20240524 FAILS and coredumps Using a openSUSE MicroOS KDE test machine which is using plasma 6.0.4 and krdc 24.02.2 to the TW test machine running TW 20240524 FAILS and coredumps. Using a Ubuntu 23.10 test machine which is using plasma 5.27.8 and krdc 23.08.1 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a Windows 11 test machine and the Microsoft Remote Desktop client to the TW test machine running TW 20240524 WORKS and the desktop is displayed. So in summary, these tests show that The problem is occurs with other Linux distros that are using plasma 6 and krdc 24.* The problem does NOT occur with other Linux distros that are still using plasma 5 and krdc 23.* Even the Windows 11 RDP client WORKS I'm not sure what other information the developers could possibly need to get this problem addressed. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #18 from Joe S --- (In reply to Tilman Vogel from comment #17) > Broken on openSUSE Tumbleweed 20240524. > Thanks to https://bugs.kde.org/show_bug.cgi?id=482950#c10 for the workaround! Doesn't work for me on TW 20240430 using Accelleration "Disable All Accelleration". Here's the messages for krdc kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_rdpplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_testplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_vncplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed qt.core.qobject.connect: QObject::connect: No such signal KBookmarkManager::changed(QString,QString) KRDC: Starting RDP session [10:35:56:292] [18533:18533] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_RGBA32 [10:35:56:292] [18533:18533] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGR24 [10:35:56:308] [18533:18533] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded pulse backend for rdpsnd [10:35:56:309] [18533:18533] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpsnd [10:35:56:309] [18533:18533] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel audin [10:35:56:318] [18533:18533] [INFO][com.freerdp.channels.audin.client] - Loaded pulse backend for audin [10:35:58:532] [18533:18613] [ERROR][com.freerdp.core.update] - UPDATE_TYPE Bitmap [1] failed [10:35:58:532] [18533:18613] [ERROR][com.freerdp.core.rdp] - DATA_PDU_TYPE_UPDATE - update_recv() failed [10:35:58:532] [18533:18613] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 [10:35:58:532] [18533:18613] [ERROR][com.freerdp.core] - freerdp_check_fds() failed - 0 [10:36:00:951] [18533:18533] [ERROR][com.freerdp.core] - freerdp_abort_connect:freerdp_set_last_error_ex ERRCONNECT_CONNECT_CANCELLED [0x0002000B] And then I'm disconnected. Doesn't work for me on TW 20240430 using Accelleration Force RemoteFX. Here's the messages for krdc kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_rdpplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_testplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_vncplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed qt.core.qobject.connect: QObject::connect: No such signal KBookmarkManager::changed(QString,QString) KRDC: Starting RDP session [10:38:17:156] [18740:18740] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_RGBA32 [10:38:17:156] [18740:18740] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32 [10:38:17:175] [18740:18740] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded pulse backend for rdpsnd [10:38:17:176] [18740:18740] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpsnd [10:38:17:176] [18740:18740] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel audin [10:38:17:180] [18740:18740] [INFO][com.freerdp.channels.audin.client] - Loaded pulse backend for audin [10:38:19:330] [18740:18817] [WARN][com.freerdp.channels.rdpdr.client] - Checking ExtendedPDU::RDPDR_USER_LOGGEDON_PDU, client supported, server not found and then it hangs on the Blue Screen. Whereas "xfreerdp -u -v --dynamic-resolution" works fine and displays the desktop. NOTE: I have been trying to resolve these issues for almost 3 MONTHS now. They started for me when TW switched to KDE Plasma 6. The messages above are from my main machine ( where I originally found the problem ) which is running TW 20240430 now, HOWEVER, months ago I setup 2 test machines with brand new TW installations and replicated the problem there on brand new installations completely eliminating any issue with my main machine. Over the last 3 months, I have updated those
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #15 from Joe S --- (In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #13) > I had to downgrade to krdc-23.08.4 to continue using it because of this same > problem. And some weeks ago I had to downgrade to freerdp-2.11.2 too, > because OpenSuSE Tumbleweed pushed a new version of freerdp which changes > several command line parameters, causing it to be incompatible with krdc 23 Where did you get krdc 23.08 or did you compile yourself ? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #14 from Joe S --- (In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #13) > I had to downgrade to krdc-23.08.4 to continue using it because of this same > problem. And some weeks ago I had to downgrade to freerdp-2.11.2 too, > because OpenSuSE Tumbleweed pushed a new version of freerdp which changes > several command line parameters, causing it to be incompatible with krdc 23 Where did you get the older version of krdc or did you compile yourself ? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #11 from Joe S --- This problem just seems to get worse with each update. I have replicated it on a Tumbleweed vm running the latest build 20240507. My KDE Neon test environment updated to the last version just displays the blue screen that everyone else is complaining about. Those are NEW fresh installations that were updated to the latest builds so nothing in the current environment where the problem was originally found comes into play. Trying to connect using krdc 24.02.2 now just core dumps systemd-coredump[758]: [] Process 744 (krdc) of user 1000 dumped core. Stack trace of thread 744: #0 0x7fee3c013bf1 n/a (libkrdc_rdpplugin.so + 0xebf1) #1 0x7fee3c01948d n/a (libkrdc_rdpplugin.so + 0x1448d) #2 0x7fee43ddc245 _ZN15HostPreferences10showDialogEP7QWidget (libkrdccore.so.5 + 0xb245) #3 0x5619e047d93b n/a (krdc + 0x3293b) #4 0x5619e0467017 n/a (krdc + 0x1c017) #5 0x7fee4162a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #6 0x7fee4162a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #7 0x5619e04672d5 n/a (krdc + 0x1c2d5) Stack trace of thread 745: #0 0x7fee4170578f __poll (libc.so.6 + 0x10578f) #1 0x7fee405ce2ff n/a (libglib-2.0.so.0 + 0x5f2ff) #2 0x7fee405cea0c g_main_context_iteration (libglib-2.0.so.0 + 0x5fa0c) #3 0x7fee421c0a8c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEve> #4 0x7fee41f9979b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0> #5 0x7fee42074cb4 _ZN7QThread4execEv (libQt6Core.so.6 + 0x274cb4) #6 0x7fee41d7b6fa n/a (libQt6DBus.so.6 + 0x386fa) #7 0x7fee420ecea9 n/a (libQt6Core.so.6 + 0x2ecea9) #8 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #9 0x7fee4171400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 747: #0 0x7fee4168effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x7fee41691d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x7fee35d10e5b n/a (iris_dri.so + 0x110e5b) #3 0x7fee35d06e67 n/a (iris_dri.so + 0x106e67) #4 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x7fee4171400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 746: #0 0x7fee4170578f __poll (libc.so.6 + 0x10578f) #1 0x7fee3f6ed8aa n/a (libxcb.so.1 + 0xe8aa) #2 0x7fee3f6ef41c xcb_wait_for_event (libxcb.so.1 + 0x1041c) #3 0x7fee3dd34e30 n/a (libQt6XcbQpa.so.6 + 0x5de30) #4 0x7fee420ecea9 n/a (libQt6Core.so.6 + 0x2ecea9) #5 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #6 0x7fee4171400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 748: #0 0x7fee4168effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x7fee41691d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x7fee35d10e5b n/a (iris_dri.so + 0x110e5b) #3 0x7fee35d06e67 n/a (iris_dri.so + 0x106e67) #4 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x7fee4171400c __clone3 (libc.so.6 + 0x
[krdc] [Bug 483638] TAB key not functional inside rdp windows client
https://bugs.kde.org/show_bug.cgi?id=483638 Joe S changed: What|Removed |Added CC||jmscdba+...@gmail.com --- Comment #5 from Joe S --- I have been trying to resolve the same problem with the tab key not working in a RDP sessions but I am connecting to xrdp on a linux server. As an example, if I run konsole in the rdp session and type ls -al and press the tab key it does not show the matches immediately ( .inputrc has set-show-all-if-ambiguous on ). If I connect using xfreerdp instead of krdc, then the tab key works perfectly in konsole. The konsole client is NOT the problem because I can replicate the tab key broken using libreoffice calc too. Start libreoffice calc ( cursor is in cell A1 ), press tab, nothing happens if you are using krdc client. Switch to using xfreerdp instead of krdc and the tab key works correctly in the rdp session moving the cursor to B1. IMHO, it seems like the tab key is being "consumed" by something instead of the current process. I say this because when using krdc and pressing tab ( whether in konsole or libreoffice calc ) those applications no longer respond to keystrokes, however, if you click on anything else ( the desktop background, another app, the taskbar ) to switch focus and then click back on the application ( either konsole or libreoffice calc ) then keystrokes are accepted again and until you press tab key again. My platform is openSUSE Tumbleweed 20240329 but I have replicated on 20240412 too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 Joe S changed: What|Removed |Added CC||jmscdba+...@gmail.com --- Comment #44 from Joe S --- We have been suffering with these tiling changes for 1 year now and they persist in plasma 6. Use use Meta+LeftArrow and Meta+RArrow all the time but I often end up with the situation where they are consider adjacent windows and resizing one resizes both. We NEED a way to disable this adjacent window resizing or a way to restore the old behavior where adjacent windows do NOT affect each other. I end up closing the apps to break the connection and reopening a total waste of time especially if I am in the middle of something. Resizing the apps does not always work and I sometimes have a situation where I have an app in the bottom left corner and another window that is the right 50% of the screen and I try to resize the window that is on the right 50% and the app in the left corner springs back to using the left 50% of the screen. I was SO MUCH time dealing with this, it is beyond frustrating Please provide a way to disable the new tiling OR at a minimum how to disable the adjacent window resizing. Even Microsoft Windows provides the basic functionality to turn OFF the adjacent snapping which I immediately do. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 Joe S changed: What|Removed |Added CC||jmscdba+...@gmail.com --- Comment #6 from Joe S --- I am having a similar problem and have spent DAYS debugging what is going on although my situation is slightly different, I think it may point to the root cause. I am running Tumbleweed 20240319 which has krdc 24.02.0-1.1 but I have replicated the problem on a test machine which is running TW 20240328 ( the latest ) and using krdc 24-02.1-1.1. In my case, initially I have no problems using krdc to connect to the xrdp server. BUT, I need to rename the server that is hosting xrdp and after I rename the server from OLD-NAME to NEW-NAME then BOTH krdc 24.02.0-1.1 and krdc 24.02.1-1.1 experience the BLUE screen and do not get the desktop. Although either krdc version has the blue screen problem, I have no problems remotely connecting using xfreerdp or remmina to the NEW-NAME server and ping and ssh also work using the NEW-NAME. Even Windows 10 clients can connect to NEW-NAME with no issues. Generally the other clients display a unknown certificate error but after you accept and continue then your are logged in and the desktop is displayed. If I rename the server back to OLD-NAME then krdc starts working again. If I rename the server back to NEW-NAME then krdc gets the blue screen again and yet EVERYTHING else works fine with NEW-NAME. I even went as far as building a new VM with a fresh TW install and that VM experiences the same issues. On TW, xrdp uses /usr/bin/xrdp-keygen to generate /etc/xrdp/rsakeys.ini which has the key/cert used by the xrdp connections. If you generate your own key/cert and then modify /etc/xrdp/xrdp.ini to set the certificate= and file_key= lines to the generated files and then restart the xrdp service, then all clients work with NEW-NAME ( after accepting the unknown certificate ) except for krdc. For krdc it displays the unknown certificate message ( unlike when using the keys from rsakeys.ini ) but after selecting Continue you are still left with the blue screen. At one point I even heard the login sound play but still no desktop is displayed with krdc. Since everything else works fine with the NEW-NAME for the server EXCEPT for krdc that seems to point to it being the problem. NOTE: I have renamed xrdp servers in the past and have not run into this problem. Hopefully my detailed analysis helps you to identify what is wrong with krdc. Please let me know if you want more details. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440358] Konsole cannot permanent disable or hide main and session toolbars
https://bugs.kde.org/show_bug.cgi?id=440358 Joe S changed: What|Removed |Added Version|unspecified |21.04.3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440358] New: Konsole cannot permanent disable or hide main and session toolbars
https://bugs.kde.org/show_bug.cgi?id=440358 Bug ID: 440358 Summary: Konsole cannot permanent disable or hide main and session toolbars Product: konsole Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: jmscdba+...@gmail.com Target Milestone: --- SUMMARY I am running OpenSuse TumbleWeed. Earlier this year konsole added Main and Session toolbars which could be enabled/disabled via "Settings / Toolbars Shown" I disabled both of those toolbars. Somewhere between TW 20210623 and 20210704 both of those toolbars appeared again but the "Settings / Toolbars Shown" option no longer exists. Right Clicking in the Menu Bar allows you to enable/disable the Main ToolBar and/or the Session ToolBar but those changes are not persistent and after you close the konsole window and reopen they are back. There appears to be no way to permanently disable them again. Yesterday I updated to TW 20210726 but there is still no option that I can find to permanently disable the Main and Session ToolBars. Please add back the "Settings / Toolbars Shown" option or provide another method to permanently disable both Toolbars. STEPS TO REPRODUCE 1. Open konsole 2. Settings / Toolbars Shown option does not exist 3. Right Click on Menu and disable Main and Session Toolbar 4. Close and reopen konsole 5. Both toolbars are back OBSERVED RESULT Settings / Toolbars Shown option does not exist Right Click on Menu and disable Main and Session Toolbar hides them temporarily but they come back when konsole is closed and reopened. EXPECTED RESULT Main and Session toolbars should stay hidden once they are disabled. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSuse Tumbleweed build 20210726 (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel version 5.13.4-1 -- You are receiving this mail because: You are watching all bug changes.
