[kate] [Bug 405273] Changing the Schema resets the user defined font size to the default font size
https://bugs.kde.org/show_bug.cgi?id=405273 --- Comment #1 from Richard Bowen --- I'm using Plasma on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405274] The Ctrl+Shift+, shortcut for opening the Configure Kate dialog doesn't work
https://bugs.kde.org/show_bug.cgi?id=405274 --- Comment #3 from Richard Bowen --- Yea, on Wayland. Will mention that from now on. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405274] The Ctrl+Shift+, shortcut for opening the Configure Kate dialog doesn't work
https://bugs.kde.org/show_bug.cgi?id=405274 Richard Bowen changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405274] The Ctrl+Shift+, shortcut for opening the Configure Kate dialog doesn't work
https://bugs.kde.org/show_bug.cgi?id=405274 Richard Bowen changed: What|Removed |Added Summary|The Shortcut for opening|The Ctrl+Shift+, shortcut |the Configure Kate dialog, |for opening the Configure |Ctrl+Shift+, doesn't work |Kate dialog doesn't work -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405274] New: The Shortcut for opening the Configure Kate dialog, Ctrl+Shift+, doesn't work
https://bugs.kde.org/show_bug.cgi?id=405274 Bug ID: 405274 Summary: The Shortcut for opening the Configure Kate dialog, Ctrl+Shift+, doesn't work Product: kate Version: 18.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: rgb@gmail.com Target Milestone: --- SUMMARY The Ctrl+Shift+, shortcut to open the 'Configure Kate' setting dialog doesn't work. STEPS TO REPRODUCE 1. Click Ctrl+Shift+, 2. Observe the window not appear OBSERVED RESULT The Kate settings dialog doesn't get opened when the Ctrl+Shift+, combo is clicked. EXPECTED RESULT The Kate settings dialog opens when the Ctrl+Shift+, combo is clicked. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Linux archlinux 5.0.0-arch1-1-ARCH (available in About System) KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405273] Changing the Schema resets the user defined font size to the default font size
https://bugs.kde.org/show_bug.cgi?id=405273 Richard Bowen changed: What|Removed |Added Summary|Changing the Schema resets |Changing the Schema resets |the set font size to the|the user defined font size |default font size |to the default font size -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405273] New: Changing the Schema resets the set font size to the default font size
https://bugs.kde.org/show_bug.cgi?id=405273 Bug ID: 405273 Summary: Changing the Schema resets the set font size to the default font size Product: kate Version: 18.12.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: rgb@gmail.com Target Milestone: --- SUMMARY Changing the Kate Schema changes the custom font size (for example 11) to to the Kate's default font size (9). This happens both from the View > Schema menu entry, and when it is set globally in settings. STEPS TO REPRODUCE 1. Click Ctrl++/Ctrl+- or use the global settings dialog (Configure Kate...) to increase/decrease the font size. It should be something other than the default. 11 is a noticeable size. 2. Change the Kate schema from the View > Schema menu or from the globally from the Configure Kate settings dialog. 3. Observe the font size revert to the default font size. OBSERVED RESULT The custom, user set font size gets changed to the default font size when a Schema is changed. EXPECTED RESULT Whenever a schema is changed, it should respect the user defined settings, namely the font size in this case. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Linux archlinux 5.0.0-arch1-1-ARCH (available in About System) KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION I noticed that for the default schema, the change in font size change is registered for that schema only. Are the schemas that decoupled that they don't share application data such as the font size set by the user? -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 399452] Kamoso requires 2 runs before the application window shows up
https://bugs.kde.org/show_bug.cgi?id=399452 Richard Bowen changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 399452] Kamoso requires 2 runs before the application window shows up
https://bugs.kde.org/show_bug.cgi?id=399452 --- Comment #2 from Richard Bowen --- Alright, closing this bug report as it seems to be resolved. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 399452] Kamoso requires 2 runs before the application window shows up
https://bugs.kde.org/show_bug.cgi?id=399452 --- Comment #1 from Richard Bowen --- This appears to be resolved for me. Anyone else experience the reported issue with the latest KDE upgrade? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399489] Moving items to different locations on the desktop is hard
https://bugs.kde.org/show_bug.cgi?id=399489 --- Comment #2 from Richard Bowen --- No I'm not holding down any modifier keys. A correction, there is only one icon that shows and that's the red cancel icon shown in the image. When the item is in a drop area it shows no icon. Did you try dragging a single item as well. Dragging a single or multiple (2 in my case) results in the same issue. If it works for you maybe it is fixed upstream. Anyone else can verify? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 Richard Bowen changed: What|Removed |Added CC||rgb@gmail.com --- Comment #1 from Richard Bowen --- Have a similar issue. Cant move a specific folder above trash. Whenever I try, the items remain in the same position. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399489] Moving items to different locations on the desktop is hard
https://bugs.kde.org/show_bug.cgi?id=399489 Richard Bowen changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399489] New: Moving items to different locations on the desktop is hard
https://bugs.kde.org/show_bug.cgi?id=399489 Bug ID: 399489 Summary: Moving items to different locations on the desktop is hard Product: plasmashell Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: rgb@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 115473 --> https://bugs.kde.org/attachment.cgi?id=115473&action=edit Non drop area on screen Moving items to different locations on the desktop is hard SUMMARY Items cannot be dropped on intermediate areas on desktop. When an item is dragged and dropped at a different location on the desktop, if the green plus icon isn't shown on the screen, the item can neither be dropped at the new location nor nearby; it just gets placed back at it's original location. STEPS TO REPRODUCE 1. Add a file/folder to the desktop (if Home or Trash are available they can be used) 2. Move an item to multiple locations on the desktop 3. Observe the various areas on the desktop the item can't be dropped and how often it flickers between the 'drop icon' and 'no-drop icon' 4. Drop the item somewhere where the drop icon is red. OBSERVED RESULT When dragging an item to a different location on the desktop, the cursor has to be positioned at a very specific location on the desktop before the item can be dropped. Otherwise, when the item is dropped, it gets placed back at it's original location. EXPECTED RESULT When an item is dropped anywhere on the desktop, it gets placed in the nearest slot. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION It appears that desktop uses a grid, where items can only be placed on certain slots in that grid. If the item can't be dropped on areas between the slots, then possibly auto-placing the item in the closes location would work better. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 399453] Kamoso uses light button variant with Breeze Dark workspace theme
https://bugs.kde.org/show_bug.cgi?id=399453 Richard Bowen changed: What|Removed |Added Summary|Kamoso uses light button|Kamoso uses light button |variant with Breeze Dark|variant with Breeze Dark |desktop theme |workspace theme -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 399453] Kamoso uses light button variant with Breeze Dark desktop theme
https://bugs.kde.org/show_bug.cgi?id=399453 Richard Bowen changed: What|Removed |Added Summary|Kamoso uses light button|Kamoso uses light button |variant with breeze dark|variant with Breeze Dark |desktop theme |desktop theme -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 399453] New: Kamoso uses light button variant with breeze dark desktop theme
https://bugs.kde.org/show_bug.cgi?id=399453 Bug ID: 399453 Summary: Kamoso uses light button variant with breeze dark desktop theme Product: kamoso Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: rgb@gmail.com Target Milestone: --- SUMMARY Kamoso uses light button variant with breeze dark workspace theme. STEPS TO REPRODUCE 1. Enable the Breeze Dark workspace theme 2. Launch Kamoso 3. Observe toolbar icons OBSERVED RESULT Toolbar icons use the light theme button variant. EXPECTED RESULT Toolbar uses the dark theme button variant. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION There is also an icon on the toolbar that bleeds into the title bar. right above the Burst button. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 399452] Kamoso requires 2 runs before the application window shows up
https://bugs.kde.org/show_bug.cgi?id=399452 Richard Bowen changed: What|Removed |Added Summary|Kamoso Takes 2 runs before |Kamoso requires 2 runs |the application window |before the application |shows up|window shows up -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 399452] New: Kamoso Takes 2 runs before the application window shows up
https://bugs.kde.org/show_bug.cgi?id=399452 Bug ID: 399452 Summary: Kamoso Takes 2 runs before the application window shows up Product: kamoso Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: rgb@gmail.com Target Milestone: --- SUMMARY When Kamoso is first executed it doesn't show the application window. Another execution is required before the application launches normally. Following the successful first launch Kamoso launches normally. STEPS TO REPRODUCE 1. Restart your computer 2. Launch Kamoso (It will not run on this launch) 3. Launch it again 4. Kamoso should launch on first run from here on out for this desktop session until the next restart. OBSERVED RESULT Kamoso takes to an additional execution after the first to launch the application window. Following the first application window launch Kamoso launches normally. EXPECTED RESULT When Kamoso is executed for the very first time, the application window appears. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393813] Better organize Plasma and KDE application configuration files
https://bugs.kde.org/show_bug.cgi?id=393813 --- Comment #4 from Richard Bowen --- It's just that other applications/desktop environments organize their config files in a folder structure in ~/.config. The categorization simplifies things a bit (eg. ~/.config/plasma/) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393813] Better organize Plasma and KDE application configuration files
https://bugs.kde.org/show_bug.cgi?id=393813 --- Comment #2 from Richard Bowen --- True it isn't an issue, but now I know the situation. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393813] New: Better organize Plasma and KDE application configuration files
https://bugs.kde.org/show_bug.cgi?id=393813 Bug ID: 393813 Summary: Better organize Plasma and KDE application configuration files Product: systemsettings Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rgb@gmail.com Target Milestone: --- Created attachment 112392 --> https://bugs.kde.org/attachment.cgi?id=112392&action=edit KDE related config files ~/.config path The ~/.config directory is used by Plasma and KDE application for storing config files however these config files are all not organized in a directory(s) and a result the ~/.config path has a lot of KDE related config files. This is a proposal to create a directory structure in ~/.config to better organize those files. An alternative could be to store the config files (or values) in another way. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393812] Ability to select a default text editor in the "Default Applications" System Settings Module
https://bugs.kde.org/show_bug.cgi?id=393812 --- Comment #1 from Richard Bowen --- ..with ease and not having to set the editor as default for each filetype. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393812] New: Ability to select a default text editor in the "Default Applications" System Settings Module
https://bugs.kde.org/show_bug.cgi?id=393812 Bug ID: 393812 Summary: Ability to select a default text editor in the "Default Applications" System Settings Module Product: systemsettings Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rgb@gmail.com Target Milestone: --- This would be useful for changing the default text editor. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 393485] Redundant terminal tool view when a Project is open
https://bugs.kde.org/show_bug.cgi?id=393485 --- Comment #2 from Richard Bowen --- Created attachment 112314 --> https://bugs.kde.org/attachment.cgi?id=112314&action=edit Double active terminal views Another conflict with the double terminal view is: If project was closed with "Current Project" terminal view in an active state in the last project session AND if Kate was closed with the "Terminal tool view" plugin active in the last regular session THEN When a new project session is opened, both terminal views are activated. (Kate saves the state of these widgets) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 393485] Redundant terminal tool view when a Project is open
https://bugs.kde.org/show_bug.cgi?id=393485 --- Comment #1 from Richard Bowen --- The extra terminal view is handy. It's like a second tab. :P -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 393485] New: Redundant terminal tool view when a Project is open
https://bugs.kde.org/show_bug.cgi?id=393485 Bug ID: 393485 Summary: Redundant terminal tool view when a Project is open Product: kate Version: 18.04.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: rgb@gmail.com Target Milestone: --- Created attachment 112226 --> https://bugs.kde.org/attachment.cgi?id=112226&action=edit "Terminal" tool view and "Current Project" tool view When the "Terminal tool view" plugin is enabled and a project is opened, there are two terminal widgets shown; "Terminal" and the one in "Current Project". A possible solution would be to check for the "Current Project" terminal tool view and disable the "Terminal" plugin. Steps to reproduce: 1. Enable the "Terminal tool view" plugin 2. Open a project in Kate 3. Click the "Current Project" button 4. Click on the "Terminal" plugin button -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393292] qupzilla still shown in query string when searching duckduckgo
https://bugs.kde.org/show_bug.cgi?id=393292 --- Comment #3 from Richard Bowen --- Ok cool. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393292] New: qupzilla still shown in query string when searching duckduckgo
https://bugs.kde.org/show_bug.cgi?id=393292 Bug ID: 393292 Summary: qupzilla still shown in query string when searching duckduckgo Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: rgb@gmail.com Target Milestone: --- Created attachment 112112 --> https://bugs.kde.org/attachment.cgi?id=112112&action=edit qupzilla in query string To reproduce: 1. Launch Falkon, 2. search for something from the URL bar, 3. see attachment -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 393290] New: Konqueror does not close properly when application is exited
https://bugs.kde.org/show_bug.cgi?id=393290 Bug ID: 393290 Summary: Konqueror does not close properly when application is exited Product: konqueror Version: 5.0.97 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: rgb@gmail.com Target Milestone: --- When closing konqueror from the title bar and with Ctrl+q, it does not close properly. It operates like a program that is running in the background but it has no icon in the system tray, and any attempt to reopen it fails. The process has to be killed before it can be reopened normally. Steps to Reproduce: 1. Open konqueror from the terminal, 2. close it, 3. try to reopen it. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 392940] Persistent tool views on startup even when not selected
https://bugs.kde.org/show_bug.cgi?id=392940 Richard Bowen changed: What|Removed |Added Version|unspecified |5.2.1 Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 392940] New: Persistent tool views on startup even when not selected
https://bugs.kde.org/show_bug.cgi?id=392940 Bug ID: 392940 Summary: Persistent tool views on startup even when not selected Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: rgb@gmail.com Target Milestone: --- Created attachment 111928 --> https://bugs.kde.org/attachment.cgi?id=111928&action=edit persistent tool views after startup with menubar showing the tool views are unchecked This only seems to occur when there is no active project. Once a tool view is toggled, it will persist on new starts of KDevelop, unless the KDevelop config file (~/.config/kdeveloprc) is removed, or a project is imported/created. To Reproduce: 0. close all projects (if open) 1. toggle any/all of the tool views on, then off 2. close KDevelop 3. reopen KDevelop 4. see attachment KDevelop version: 5.2.1 Platform: Linux archlinux 4.15.15-1-ARCH -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359227] Need a shortcut to switch from text editor to konsole
https://bugs.kde.org/show_bug.cgi?id=359227 Richard Bowen changed: What|Removed |Added CC||rgb@gmail.com --- Comment #6 from Richard Bowen --- (In reply to Kevin Funk from comment #5) > Ah. I see. That's indeed a problem. Don't know how to work-around. > > Ideas/patches welcome! Maybe Ctrl+Meta+T could work, assuming it is not bound to something already. -- You are receiving this mail because: You are watching all bug changes.
