[frameworks-plasma] [Bug 428213] When IBus is launched after Qt apps, it can't enter text in those apps
https://bugs.kde.org/show_bug.cgi?id=428213 --- Comment #12 from David --- Not sure if Bug 417994 is a duplicate, since that bug doesn't affect kwrite behavior. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 450404] New: Highlighting text makes mouse pointer switch to default theme in some areas
https://bugs.kde.org/show_bug.cgi?id=450404 Bug ID: 450404 Summary: Highlighting text makes mouse pointer switch to default theme in some areas Product: okular Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- Created attachment 146834 --> https://bugs.kde.org/attachment.cgi?id=146834&action=edit okular_mouse_changes SUMMARY If I open a PDF in Okular and set some text as highlighted, then move the mouse over some empty corner, it will show the mouse cursor as the default breeze theme instead of what I have set as my mouse theme. Placing the mouse over the toolbars and similar makes it show with the correct theme, but as soon as it touches an empty corner, it will degrade to breeze. Attached is a video showing the behavior. STEPS TO REPRODUCE 1. Configure a mouse theme other than the default breeze. 2. Open a PDF with okular. 3. Zoom it out so that there will be empty corners at the left and right sides. 4. Highlight some text with okular's functionality for that. 5. Try pointing the mouse at the side corners and at the toolbars, and see how the mouse pointer is rendered. OBSERVED RESULT Uses the default breeze theme when it is inside the empty sides. EXPECTED RESULT Should always use the theme that I have configured. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.0-2-amd64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD VEGA10 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450484] New: Kate R syntax colorer puts extra underline on common operator
https://bugs.kde.org/show_bug.cgi?id=450484 Bug ID: 450484 Summary: Kate R syntax colorer puts extra underline on common operator Product: kate Version: 21.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY If I open a .R file with Kate, it will show the operator ":=" with an extra underline in the right sign, making it show **three** bars instead of two. This is very annoying since it makes it harder to read the code and makes people think they've inputted the wrong symbol. These two symbols together (:=) are very common in R code, and what's more, kate's coloring backed is offered as one of the styles for "rmarkdown" (what most people use to write tutorials, manuals, vignettes, etc. with R code), but this issue makes it a very unsuitable candidate (and it's understandably not the default BTW, even though it otherwise looks better than the default style from rmarkdown). I have on multiple ocassions decided to use a Python syntax highlighter for R code instead due to this issue alone. STEPS TO REPRODUCE 1. Save this text as a .R file and open it with Kate: library(data.table) dt <- data.table(col1 = 1:3) dt[, col1 := col1+1] OBSERVED RESULT The ":=" operator has three lines. EXPECTED RESULT The ":=" operator should have two lines. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.0-2-amd64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD VEGA10 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 450896] New: Okular doesn't take middle clicks for internal links
https://bugs.kde.org/show_bug.cgi?id=450896 Bug ID: 450896 Summary: Okular doesn't take middle clicks for internal links Product: okular Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY Middle-clicking internal PDF links to sections within a PDF doesn't work in Okular. STEPS TO REPRODUCE 1. Configure okular to have tabs for documents. 2. Open some PDF with internal links that take to some section of the same PDF. 3. Try to middle-click the internal link. OBSERVED RESULT Nothing happens. EXPECTED RESULT Should open the link in a new tab. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.0-2-amd64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD VEGA10 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 450896] Okular doesn't take middle clicks for internal links
https://bugs.kde.org/show_bug.cgi?id=450896 --- Comment #2 from David --- (In reply to Albert Astals Cid from comment #1) > Why should it? In most common applications (e.g. web browsers, file managers, terminals, etc.) a middle-click opens links in a new tab. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 454181] Ark doesn't preview HTML files anymore
https://bugs.kde.org/show_bug.cgi?id=454181 David changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from David --- (In reply to Bug Janitor Service from comment #5) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! All info is already provided. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454987] New: Unmuting firefox resets volume
https://bugs.kde.org/show_bug.cgi?id=454987 Bug ID: 454987 Summary: Unmuting firefox resets volume Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY If I mute and then unmute some youtube video in firefox, it will change the volume that I have configured for the application in the sound panel. STEPS TO REPRODUCE 1. Install: media player integration, firefox, firefox extension for the integration. 2. Put the built-in sound control widget in your panel. 3. Configure your pulseaudio or wireplumber to have independent volumes per application. 4. Launch firefox, open an incognito window, browse some random video in youtube and play it. 5. While the video is playing, open the sound widget and change the volume for firefox. 6. In the video that is playing in firefox, mute it through the youtube mute button, then unmute it from there. OBSERVED RESULT Resets firefox's volume to 100%. EXPECTED RESULT Should leave the volume where I left it. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.17.0-2-amd64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD VEGA10 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 453733] Tooltips degrade performance
https://bugs.kde.org/show_bug.cgi?id=453733
--- Comment #4 from David ---
(In reply to Michail Vourlakos from comment #3)
> just to be more detailed.. Which tooltips are creating lag? please provide a
> screenshot.
The app name tooltips. The ones you get when leaving the cursor onto an app
icon ("tiny title tooltips on hovering").
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 453733] Tooltips degrade performance
https://bugs.kde.org/show_bug.cgi?id=453733 --- Comment #5 from David --- Created attachment 149693 --> https://bugs.kde.org/attachment.cgi?id=149693&action=edit Tooltip sample -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455495] New: Volume is the same for all devices
https://bugs.kde.org/show_bug.cgi?id=455495 Bug ID: 455495 Summary: Volume is the same for all devices Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY Volume used to be remember on a per-device basis. After the last KDE updates, it isn't anymore. STEPS TO REPRODUCE 1. If using a laptop, connect some headphones or speakers so as to have at least two volume sources. If a non-laptop, try having an HDMI screen with audio or similar plus some speakers. 2. Change the general volume from its default value. 3. Disconnect the currently active sound device (e.g. the headphones) so as to make it switch to a different output source (e.g. the built-in speakers). OBSERVED RESULT Volume remains as it was set for the earlier audio device, but now applied to the new device, for which the same value is unlikely to be optimal. EXPECTED RESULT It should remember that the audio device to which it switched had a different volume the last time it was used. Different audio devices have very different meanings for different volume levels. You can make people hurt their ears badly. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.18.0-1-amd64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD VEGA10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428357] Night color does not activate after session start
https://bugs.kde.org/show_bug.cgi?id=428357 David changed: What|Removed |Added CC||kitt...@gmail.com --- Comment #11 from David --- (In reply to Nicolas Fella from comment #10) > (In reply to Maciej Mrozowski from comment #3) > > Might have something to do with https://bugs.kde.org/show_bug.cgi?id=413134 > > Yes, it indeed seems related. > > What I'm seeing is this: > > When logging into an X11 session night color activates, then after 1-2s it > deactivates again. It's still marked as enabled in the applet and > deactivating and activating again enables night color > > After going to Systemsettings > "Startup and Shutdown" > "Background > Services" and disabling "Color Daemon" it works as expected I can confirm, additionally, manually toggling the colour daemon service stops Night Color functionality immediately. There is definitely something going on there. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466614] New: Inconveniently slow scroll speed
https://bugs.kde.org/show_bug.cgi?id=466614 Bug ID: 466614 Summary: Inconveniently slow scroll speed Classification: Applications Product: okular Version: 22.12.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: nergad...@gmail.com Target Milestone: --- SUMMARY *** Touchpad two finger scroll is way too slow to the point of inconvenience. When reading something I'd rather use hand tool and awkwardly two tap and slide document up than to swipe two fingers - the usual scrolling gesture everywhere else. I'd love Okular to have customizable scroll delta when using touchpad (Mouse wheel scroll works well!). *** STEPS TO REPRODUCE :( pretty straightforward, I think 1. Install windows 11; 2. Install Okular; 3. Use two finger swipe gesture on your touchpad. OBSERVED RESULT Slow and inconsistent scrolling speed/delta for both: vertical and horizontal scrolling. EXPECTED RESULT To somewhat match scrolling speed of other Windows apps. SOFTWARE/OS VERSIONS Okular: 22.12.2 Windows: 11 22H2 and 23H1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466614] Inconveniently slow scroll speed
https://bugs.kde.org/show_bug.cgi?id=466614 David changed: What|Removed |Added CC||nergad...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466905] New: System monitor column "login" is always empty
https://bugs.kde.org/show_bug.cgi?id=466905 Bug ID: 466905 Summary: System monitor column "login" is always empty Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY If I configure the "process" section of the system monitor to show "login" as a column (the user name), the column is always empty, even though UID has the correct number. STEPS TO REPRODUCE 1. Open system monitor. 2. Go to section "Processes" in the panel at the left. 3. Click the three dots menu, select "Configure columns...", find entry "Login", and set it to "Text Only". OBSERVED RESULT Column is empty for all processes. EXPECTED RESULT Should show the user name like it says in the config. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466906] New: Cannot drag columns in system monitor pages
https://bugs.kde.org/show_bug.cgi?id=466906 Bug ID: 466906 Summary: Cannot drag columns in system monitor pages Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY I cannot drag columns in a system monitor page to re-arrange them in the order I want them. STEPS TO REPRODUCE 1. Launch system monitor. 2. Go to some section like "Processes" in the left panel. 3. Pick a column like "Name" or "CPU" and try to drag it further to the right with the mouse. OBSERVED RESULT Doesn't move. EXPECTED RESULT Should let me place the columns in the order that I want them. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466907] New: System monitor settings pop-up cannot be dragged
https://bugs.kde.org/show_bug.cgi?id=466907 Bug ID: 466907 Summary: System monitor settings pop-up cannot be dragged Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY If I try to change the settings of something in the system monitor, the pop-up window that it opens is not clickable, which is detrimental to usability as then I cannot have a clear view of what I have currently configured to show in the UI as I need to make changes. STEPS TO REPRODUCE 1. Launch system monitor. 2. Go to some section like "Processes" in the left panel. 3. Click the three dots menu, select "Configure columns...". 4. Try to drag the pop-up that opens from its header section where there should be a titlebar. OBSERVED RESULT Cannot drag the pop-up subwindow. EXPECTED RESULT Should let me drag the pop-up subwindow so that then I can see my current view before as I change the settings. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466909] New: System monitor edit mode and column ticker is very un-intuitive
https://bugs.kde.org/show_bug.cgi?id=466909 Bug ID: 466909 Summary: System monitor edit mode and column ticker is very un-intuitive Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY The way that the system monitor means to get user configuration is very un-intuitive. If I have a custom configuration for which columns to show on a page in the system monitor and I then accidentally enter "edit mode" and click "discard changes" before I am able to do anything harmful in that page, it will reset all the custom columns that I selected to the default, even though they were not changed inside the "edit mode". STEPS TO REPRODUCE 1. Launch system monitor. 2. Go to some section like "processes" in the left panel. 3. Click the three dots menu and select "Configure columns...". 4. Enable extra columns of your choice there. 5. Click the three dots menu again, but this time select "Edit Page". 6. Don't do anything there, but click "Discard Changes". OBSERVED RESULT The custom columns configuration is lost. EXPECTED RESULT The custom column configuration should be preserved, since it was configured inside a different menu. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466910] New: System monitor doesn't show detailed process information like KSysGuard did
https://bugs.kde.org/show_bug.cgi?id=466910 Bug ID: 466910 Summary: System monitor doesn't show detailed process information like KSysGuard did Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY In KSysGuard, if I right-click a process, there's an option "Detailed Information" which is very helpful when one wants to get more info out of a process. This is however not available in the new system monitor that is meant to replace KSysGuard - the closest thing it has is a pop-up with info about the columns that were configured, but this pop-up is not copy-pastable. STEPS TO REPRODUCE 1. Launch KSysGuard. 2. Right-click some process. 3. Select "Detailed Information" and make a note of all the info that it has (e.g. TTY, command that launched it, location, etc.). 4. Launch the new system monitor. 5. Try to extract all the information above in a way that could be copied to a text editor, for some entry under "applications" or "processes". OBSERVED RESULT Not possible to get detailed info and copy it to a text editor. EXPECTED RESULT Should be as helpful as KSysGuard. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466911] New: Default logout option setting disappeared after update
https://bugs.kde.org/show_bug.cgi?id=466911 Bug ID: 466911 Summary: Default logout option setting disappeared after update Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY After the last KDE updates, the section to select the default logout option (the one that is pre-selected when pressing Ctrl+Alt+Del, like "restart" or "shutdown") disappeared from the system settings. STEPS TO REPRODUCE 1. Go to system settings. 2. Try to find the setting for the default logout option. Try using the search bar if needed. OBSERVED RESULT It's not there. Also no direct shortcut to trigger the dialog with a pre-selected option of choice without adding an extra widget. EXPECTED RESULT Should have the option to change the default logout option in the same place where it used to be in the system settings. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 466912] New: Breeze dark folder icon turns to almost-noise under dark themes
https://bugs.kde.org/show_bug.cgi?id=466912 Bug ID: 466912 Summary: Breeze dark folder icon turns to almost-noise under dark themes Classification: Plasma Product: Breeze Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: david.cortes.riv...@gmail.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- SUMMARY After the latest updates to the breeze theme, now the "breeze dark" icon for folders follows the accent color of either theme or wallpaper. This might look reasonable if one selects the default breeze colors, but if one selects a dark theme, the folder icons become too dark to the point that they are hard to see (and look quite ugly too). STEPS TO REPRODUCE 1. Go to Settings -> Appearance -> Icons -> select "Breeze Dark". 2. Go to Settings -> Appearance -> Colors -> Use accent color -> select "From current color scheme". 3. Install some good color themes for dark settings, such as "Obsidian Coast" or "Dark Obsidian" (from the button "Get New Color Schemes" in this same section). 4. Apply said theme. For worst results, use "Dark Obsidian" in combination with the "breeze" application style and "breeze dark" icons. OBSERVED RESULT Icons for folders are hard to distinguish, and look bad. EXPECTED RESULT Icons for folders should not adapt their color based on themes. Or, at the very least, if they do, then the "breeze dark" icons sould play along with dark themes. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 465584] Default logout screen option missing
https://bugs.kde.org/show_bug.cgi?id=465584 --- Comment #6 from David --- (In reply to Nate Graham from comment #3) > Indeed, there is no "shut down" menu item available in the desktop context > menu. > > Nonetheless, this was an intentional change as it was considered a super > nerdy esoteric feature that confused users. What confuses me is the process that I need to follow now, since now I need to set up a widget that I don't click, assign the shortcut Ctrl+Alt+Del to that widget, remove the global shortcut in the settings, configure the widget, and place it somewhere where I don't accidentally click it. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466956] New: Corners in GTK theme Adwaita are not rounded
https://bugs.kde.org/show_bug.cgi?id=466956 Bug ID: 466956 Summary: Corners in GTK theme Adwaita are not rounded Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY If I install the new KDE package to configure GTK app themes, the "Adwaita" and "Adwaita-dark" themes that comes with it will not have rounded corners in menus. STEPS TO REPRODUCE 1. Install package "kde-config-gtk-style". 2. Go to System Settings -> Application Style -> Configure GNOME/GTK Application Style -> GTK Theme -> choose "Adwaita-dark". 3. Open some GTK app with menus, such as "evolution" or "sublime". OBSERVED RESULT Corners of menus are sharp rectangles. EXPECTED RESULT Corners of menus should be rounded like in real gnome's adwaita and adwaita-dark. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466958] New: GTK application style not applied to apps that get sudo permissions
https://bugs.kde.org/show_bug.cgi?id=466958 Bug ID: 466958 Summary: GTK application style not applied to apps that get sudo permissions Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY If I install a theme from the KDE store for GTK apps and configure plasma to use it, it will not apply it to GTK apps that ask for sudo credentials such as "synaptic. STEPS TO REPRODUCE 1. Go to System Settings -> Appearance -> Global Theme -> Configure GNOME/GTK Application Style -> click "Get New GNOME/GTK Application Styles". 2. Install some new theme from the store, such as "Materia-breeze-gtk" (in its dark variant). 3. After it gets downloaded, apply said theme. 4. Launch synaptic. 5. Enter your sudo credentials for synaptic in the pop-up window that asks for them. OBSERVED RESULT Synaptic (a) uses the adwaita theme; (b) is missing icons; (c) has poor color contrasts. EXPECTED RESULT Synaptic should use the theme that I have configured. In contrast, if I set it to the "adwaita-dark" that comes by default, it will correctly apply the theme to synaptic. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466967] New: Scaling setting for "arrangement-specific" is global
https://bugs.kde.org/show_bug.cgi?id=466967 Bug ID: 466967 Summary: Scaling setting for "arrangement-specific" is global Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY The arrangement-specific scaling setting is actually global. STEPS TO REPRODUCE 1. Turn on laptop without an external screen. 2. Go to Sytem Settings -> Display and Monitor -> Save display's properties -> select "For only this specific display arrangement". 3. Change scaling to something non-default, such as 125%. 4. Connect external screen. 5. Optionally, restart the computer with the laptop lid closed so that it starts right away with the external screen on. 6. Go to the configuration for the external screen. OBSERVED RESULT It has the same scaling that I had configured for the laptop screen and which was "only for that specific arrangement". EXPECTED RESULT Should have the scaling that I last set for this screen. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467017] New: No shortcut for "restart computer"
https://bugs.kde.org/show_bug.cgi?id=467017 Bug ID: 467017 Summary: No shortcut for "restart computer" Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY There is a shortcut (Ctrl+Alt+Del by default) to trigger the logout dialog with "Log Out" pre-selected. One can generate similar shortcuts for the same dialog with a different option pre-selected by using a widget, but there aren't any such direct shortcuts from the system settings menu to set it. STEPS TO REPRODUCE 1. Try to assign the shortcut Ctrl+Alt+Del to the logout dialog with the "Restart" option pre-selected. OBSERVED RESULT Not possible from the system settings, and not possible to configure the default option after someone decided to remove it in the latest plasma. EXPECTED RESULT Should have an easy way to have Ctrl+Alt+Del trigger the logout dialog with "Restart" pre-selected without involving external widgets. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464824] GTK don't follow global font configuration
https://bugs.kde.org/show_bug.cgi?id=464824 --- Comment #3 from David --- (In reply to glewik from comment #2) > (In reply to David from comment #0) > > SUMMARY > > After the last update of plasma/frameworks/qt/don't know what else, GTK apps > > no longer use the fonts that I have configured in the system settings. > > > > STEPS TO REPRODUCE > > 1. Go to System Settings -> Appearance -> Global Theme -> Fonts -> Adjust > > All Fonts, and set some non-default font like "Noto-Sans" to be used for > > everything. > > 2. Update KDE-related packages to the latest version. > > 3. Open some GTK app. > > > > OBSERVED RESULT > > GTK apps now use a different font family than the one I have configured in > > my system (don't know which one exactly, but looks different from QT apps > > and from how they used to look before the last update). > > > > EXPECTED RESULT > > Fonts in GTK apps should follow the settings that I have configuted for > > them. > > > > SOFTWARE/OS VERSIONS > > Operating System: Debian GNU/Linux > > KDE Plasma Version: 5.26.5 > > KDE Frameworks Version: 5.101.0 > > Qt Version: 5.15.8 > > Kernel Version: 5.18.0-4-amd64 (64-bit) > > Graphics Platform: X11 > > Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor > > Memory: 15.5 GiB of RAM > > Graphics Processor: AMD Radeon RX Vega > > Manufacturer: Acer > > Product Name: Predator PH517-61 > > System Version: V1.09 > > > > ADDITIONAL INFORMATION > > I found resolve our problem on this site > "https://bugs.kde.org/show_bug.cgi?id=466463";. When you remove this package > "xsettingsd", font-s will be display OK. Removing "xsettingsd" didn't work for me. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467021] New: Cannot close GTK window from top-right corner
https://bugs.kde.org/show_bug.cgi?id=467021 Bug ID: 467021 Summary: Cannot close GTK window from top-right corner Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY In KDE window themes like breeze and oxygen, if I maximize a window and position the mouse at the top-right corner of the screen, it will put the "X" button on focus. Thus, if I want to close a maximized app, I can conveniently move the mouse to that corner without aiming for the button, and click to close it. However, in GTK apps that have the titlebar merged with the app window, the "X" button doesn't cover the top-right pixel, so clicking on that corner of a maximized such window does nothing. STEPS TO REPRODUCE 1. Launch some GTK app that merges the titlebar into the app window, such as "gedit" or "evolution". 2. Maximize the window of said app. 3. Position the mouse at the top-right corner of the screen. 4. Click. OBSERVED RESULT Nothing happens. EXPECTED RESULT Should close the app. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467022] New: Panel widgets do not react to mouse scroll when some app's menu is on focus
https://bugs.kde.org/show_bug.cgi?id=467022 Bug ID: 467022 Summary: Panel widgets do not react to mouse scroll when some app's menu is on focus Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY If I click the menu of some app, panel widgets like the (official KDE built-in) volume control will not react to mouse scrolls anymore until the menu of the app is closed. STEPS TO REPRODUCE 1. Put the sound control widget on the panel. 2. Launch Dolphin. 3. Click the hamburger menu in Dolphin. 4. Position the mouse pointer over the sound widget. 5. Move the mouse scroll wheel so as to change the volume. OBSERVED RESULT Nothing happens while the hamburger menu is open. EXPECTED RESULT Should change the volume. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466958] GTK application style not applied to apps that get sudo permissions
https://bugs.kde.org/show_bug.cgi?id=466958 --- Comment #2 from David --- (In reply to Nate Graham from comment #1) > Any settings you change are saved to your user account. But when you run > apps using `sudo`, they get their settings from the root user account, > because they're being run as the root user. > > In general, GUI apps should not be run using `sudo`; they should be smart > enough to request elevated privileges themselves when you launch them and > use them normally. Any apps that don't do this should be fixed, and ideally > not used at all until that happens. It's not correct that it doesn't apply user settings to it: if I select built-in themes like "adwaita-dark", it does apply it to sudo-requesting apps like synaptic. Synaptic is by the way run as a user but with sudo permissions through "synaptic-pkexec". If you don't use a debian-based distro, another alternative is to try "gparted" which also requests sudo permissions. Also, I seem to recall you deliberately disabled running graphical apps like "systemsettings5" as sudo so those settings cannot be changed for the root user either. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466956] Corners in GTK theme Adwaita are not rounded
https://bugs.kde.org/show_bug.cgi?id=466956 --- Comment #2 from David --- Created attachment 157092 --> https://bugs.kde.org/attachment.cgi?id=157092&action=edit synaptic_sharp_corners Here's a picture of a menu from "synaptic" (GTK app) when using theme "adwaita-dark", having sharp corners in the menus. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466956] Corners in GTK theme Adwaita are not rounded
https://bugs.kde.org/show_bug.cgi?id=466956 --- Comment #4 from David --- (In reply to Nate Graham from comment #3) > Thanks. Because this is a GTK app displaying a GTK theme, no KDE code is > involved. It's an issue in GTK, the app, or the theme. But those corners look sharp in GNOME when using adwaita-dark. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467031] New: Icons are too spaced apart when using custom fonts
https://bugs.kde.org/show_bug.cgi?id=467031 Bug ID: 467031 Summary: Icons are too spaced apart when using custom fonts Classification: Applications Product: dolphin Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: david.cortes.riv...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 157096 --> https://bugs.kde.org/attachment.cgi?id=157096&action=edit far_from_intersecting SUMMARY If I select a non-standard font with a large size for the "General" setting, dolphin's icon view will space things very far apart even though text is nowhere near close to intersecting. STEPS TO REPRODUCE 1. Install font "SF Pro" (from apple) or similar. 2. Go to System Settings -> Appearance -> Global Theme -> Fonts -> General -> select "SF Pro Display" with size 12. 3. Open Dolphin, zoom it a bit out from the default, and set icon view. OBSERVED RESULT Entries are too spaced apart from each other. In the screenshot, it puts 3 columns of files/folders with this font, whereas with Noto Sans it puts 5 columns. EXPECTED RESULT Entries should not be spaced from each other more than necessary. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467047] New: GTK file picker ignores single/double click settings
https://bugs.kde.org/show_bug.cgi?id=467047 Bug ID: 467047 Summary: GTK file picker ignores single/double click settings Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY I have my system configured to open files and folders with a single click. However, in the latest versions of KDE software, this setting doesn't apply anymore to the GTK file picker. STEPS TO REPRODUCE 1. Go to System Settings -> Workspace Behavior -> General Behavior -> Clicking files or folders -> select "Opens them". 2. Launch an app with a GTK file picker - examples: gedit, sublime, evolution. 3. Try to save a file or add an email attachment. 4. In the file picker dialog, click some folder. OBSERVED RESULT Selects the folder. EXPECTED RESULT Should go into the folder like it would in the QT file picker and like it used to do in the GTK one in previous versions. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467048] New: Exported default shortcuts are missing entries like "copy"
https://bugs.kde.org/show_bug.cgi?id=467048 Bug ID: 467048 Summary: Exported default shortcuts are missing entries like "copy" Classification: Applications Product: kate Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY If I export the default shortcuts in Kate, it will not include entries like "Copy" and "Paste" in the file generated from the linux version, although it does have them in the file that gets generated under other platforms. STEPS TO REPRODUCE 1. Launch Kate. 2. Go to Settings -> Configure Keyboard Shortcuts -> Manage Schemes -> More Actions -> set "Current Scheme=Default", then click "Export Scheme", and save the resulting file. 3. Open the file that was just saved. OBSERVED RESULT It's missing basic things like "copy" and "paste". EXPECTED RESULT Should have things like "copy" and "paste" so that I can copy the (sane, linux) defaults into a machine with a different OS that puts ilogical default shortcuts for things like "copy". SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466956] Corners in GTK theme Adwaita are not rounded
https://bugs.kde.org/show_bug.cgi?id=466956 --- Comment #6 from David --- (In reply to Nate Graham from comment #5) > You mean they *don't* look sharp in GNOME? Even when running the app as root? Just tried in under GNOME and for this specific app (synaptic) and for others like "evolution", the corners look rectangular, but then for apps like "gedit" or "nautilus", the corners look rounded. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467056] New: New lock screen buttons are unintuitive
https://bugs.kde.org/show_bug.cgi?id=467056 Bug ID: 467056 Summary: New lock screen buttons are unintuitive Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY The new redesigned lock screen has two buttons, but it doesn't tell me what the one at the right is for when I hover the mouse. If I click it, it takes me to the old lock screen style, but entering my password there simply displays the KDE spash screen and doesn't log in, unless I manually switch TTYs back and forth which gets me to the new login screen where I can now click the first button instead of the second. STEPS TO REPRODUCE 1. Press Windows+L; or run krunner and select "Lock". 2. Start typing. 3. Notice that there's two buttons to the left of the password bar, but if I hover the mouse, it doesn't tell me what each one does and the icon for the one on the right doesn't resemble anything I'm familiar with. 4. Click the button to the right. 5. Put your user password in the new screen (which is the old lock screen style). OBSERVED RESULT Displays the splash screen with the plasma engine continuously running, but doesn't log in. EXPECTED RESULT No idea, but it should make it clear to me before I click it as a hover pop-up. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467062] New: Splash screen's 'Get New' icon is at the wrong position
https://bugs.kde.org/show_bug.cgi?id=467062 Bug ID: 467062 Summary: Splash screen's 'Get New' icon is at the wrong position Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY In the "Appearance" section of system settings, every meny entry has the button to find new things in the KDE store placed at the bottom, except for the one for splash screens which has it at the top. STEPS TO REPRODUCE 1. Go to System Settings -> Appearance -> Splash screen. 2. Try to find the button to download new splash screens. OBSERVED RESULT It's at the top. EXPECTED RESULT Should be at the bottom like in the other sections (e.g. cursors, icons, etc.) SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467064] New: Transparency in menus stops working after launching certain apps
https://bugs.kde.org/show_bug.cgi?id=467064 Bug ID: 467064 Summary: Transparency in menus stops working after launching certain apps Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- Created attachment 157119 --> https://bugs.kde.org/attachment.cgi?id=157119&action=edit kde_transparent_menu SUMMARY Some transparent menus like the po-up when clicking the clock or the application launcher will stop being transparent after certain apps are launched. STEPS TO REPRODUCE 1. Go to System Settings -> Workspace Behavior -> Desktop Effects -> untick "Background Contrast" and "Blur". 2. Click the applications launcher icon (bottom-left corner in the panel). Notice that it is transparent. 3. Launch any of the following apps: web browsers, mail clients, kcolourpaint. 4. Close said app. 5. Open the applications launcher again. OBSERVED RESULT It's not transparent anymore. EXPECTED RESULT Should be transparent. See attached pictures for before/after. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467064] Transparency in menus stops working after launching certain apps
https://bugs.kde.org/show_bug.cgi?id=467064 --- Comment #1 from David --- Created attachment 157120 --> https://bugs.kde.org/attachment.cgi?id=157120&action=edit kde_transparent_menu_breaks And this is a screenshot taken after launching one of said apps. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467064] Transparency in menus stops working after launching certain apps
https://bugs.kde.org/show_bug.cgi?id=467064 --- Comment #2 from David --- Weirdest thing here: it will keep working correctly if before opening one of the offending apps, I first switch virtual desktops back and forth. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467064] Transparency in menus stops working after launching certain apps
https://bugs.kde.org/show_bug.cgi?id=467064 --- Comment #3 from David --- Another comment: I think this bug only happens when setting an env. variable "GTK_USE_PORTAL=1". -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467064] Transparency in menus stops working after launching certain apps
https://bugs.kde.org/show_bug.cgi?id=467064 --- Comment #4 from David --- Some observations from further testing: - This only affects pop-ups that spawn out of a panel - e.g. application launcher, clock/calendar pop-up; but not things that spawn from elsewhere like window switcher effect, Ctrl+Alt+Del dialog, or the translucency desktop effect when moving windows if activated or other similar situations that trigger a transparency event. - The GTK_USE_PORTAL setting had actually no effect, it was just random chance. - The bug disappears if I set the panel itself to be translucent (right click -> Enter Edit Mode -> More Options -> Opacity -> Translucent) (my usual setting is "Opaque"). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467072] New: First display shown in settings is always laptop screen
https://bugs.kde.org/show_bug.cgi?id=467072 Bug ID: 467072 Summary: First display shown in settings is always laptop screen Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY If I have a laptop connected to an external screen and the laptop is screen is disables, when I go do the display settings, the first thing it shows me there is still the laptop screen which is disabled. STEPS TO REPRODUCE 1. Connect external screen to laptop. 2. Disable the laptop's built-in screen so that only the external screen shows output. 3. Go to System Settings -> Hardware -> Display and Monitor. OBSERVED RESULT The device that it shows me is the disabled laptop screen. EXPECTED RESULT It should show by default the screen in which I'm seeing the settings window. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 467073] New: Shift+Clicking on processes acts like Ctrl+Clicking
https://bugs.kde.org/show_bug.cgi?id=467073 Bug ID: 467073 Summary: Shift+Clicking on processes acts like Ctrl+Clicking Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY System monitor doesn't let me Shift+Click processes to select many. STEPS TO REPRODUCE 1. Launch system monitor. 2. Click on a process. 3. Shift+Click on a different process many places below. OBSERVED RESULT Should select all the processes inbetween the two. EXPECTED RESULT Selects only the two processes that were clicked, as if I had Ctrl-clicked instead of Shift-clicked SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467075] New: Bug tracker doesn't list system monitor as an application
https://bugs.kde.org/show_bug.cgi?id=467075 Bug ID: 467075 Summary: Bug tracker doesn't list system monitor as an application Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY The bug tracker doesn't list "plasma-systemmonitor" under "Applications", even though it is an application. KSysGuard in contrast is listed there. STEPS TO REPRODUCE 1. Go to bugs.kde.org 2. Click "File a bug". 3. Select "Applications". 4. Try to find the entry "plasma-systemmonitor" there. OBSERVED RESULT It's not listed there. EXPECTED RESULT Should be listed there. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467118] New: Screenshots taken after "annotate" are lost
https://bugs.kde.org/show_bug.cgi?id=467118
Bug ID: 467118
Summary: Screenshots taken after "annotate" are lost
Classification: Applications
Product: Spectacle
Version: 22.12.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: m...@baloneygeek.com
Reporter: david.cortes.riv...@gmail.com
CC: k...@david-redondo.de
Target Milestone: ---
SUMMARY
If I take a screenshot with spectacle, go to the annotation menu, and then
press "Print Screen", the new screenshot taken in that print screen will be
lost.
STEPS TO REPRODUCE
1. Press "Print screen" to trigger spectacle.
2. In the spectacle window, click "annotate" (button in the bottom panel).
3. Press "Print screen" again.
4. Select some rectangle area and press Enter.
OBSERVED RESULT
New screenshot is lost.
EXPECTED RESULT
Should open a **new** spectacle window to deal with the new screenshot.
SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-6-amd64 (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: SLIMBOOK
Product Name: Executive
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kde] [Bug 467119] New: Tooltips are oftentimes cut when they intersect with something
https://bugs.kde.org/show_bug.cgi?id=467119 Bug ID: 467119 Summary: Tooltips are oftentimes cut when they intersect with something Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- Created attachment 157149 --> https://bugs.kde.org/attachment.cgi?id=157149&action=edit hover_cut_short SUMMARY Oftentimes, tooltips that appear when hovering the mouse over something will be cut short if they intersect with some button or similar. See attached screenshot for an example. Happens in pretty much every KDE app. STEPS TO REPRODUCE (bug happens rather randomly, might work instantaneously) 1. Launch some KDE app that would have tooltips appearing when hovering the mouse over something. Examples: dolphin, spectacle. 2. Hover the mouse over buttons near the window edges that would trigger a tooltip, or near buttons that are placed close to some widget like "set zoom level" or checkbox-like icons. OBSERVED RESULT Oftentimes, the tooltip is cut. EXPECTED RESULT Tooltip should always appear in full. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467120] New: Plasma cannot start on a read-only BTRFS subvolume for /home
https://bugs.kde.org/show_bug.cgi?id=467120 Bug ID: 467120 Summary: Plasma cannot start on a read-only BTRFS subvolume for /home Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY When one uses a copy-on-write filesystem like BTRFS or ZFS, it's oftentimes helpful to boot into an old snapshot of either your root or your home. However, KDE refuses to start on a read-only home, which makes it a hassle to boot into automated snapshots as generated by e.g. snapper. STEPS TO REPRODUCE 1. Create a BTRFS subvolume for your home directory. Modify your fstab to have this newly created BTRFS subvolume mounted as /home, reboot, and log into plasma so that it creates all the needed files for a /home/ in that subvolume. 2. Create a read-only BTRFS snapshot of your home directory using snapper. 3. Modify your fstab to use that read-only snapshot as /home instead of the current one next time the computer is restarted. 4. Restart the computer. 5. Try to log in to plasma. OBSERVED RESULT Hangs in the splash screen. EXPECTED RESULT Should recognize that it's on a read-only snapshot, avoid writing to files like ~/.xsession-errors, start, and run as usual with the caveat that it's not supposed to modify any files. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467127] New: Cannot sort plasma addons by number of downloads
https://bugs.kde.org/show_bug.cgi?id=467127 Bug ID: 467127 Summary: Cannot sort plasma addons by number of downloads Classification: Applications Product: Discover Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Discover doesn't let me sort plasma addons by number of downloads like KDE settings do. STEPS TO REPRODUCE 1. Open discover. 2. Click "Application Addons" on the left panel. 3. Try to sort by most downloaded. OBSERVED RESULT Not possible. EXPECTED RESULT Should let me sort by most downloaded. This is the most logical criterion to look out when finding useful things that aren't in base plasma. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467207] New: Fonts become garbled in GTK apps
https://bugs.kde.org/show_bug.cgi?id=467207 Bug ID: 467207 Summary: Fonts become garbled in GTK apps Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- Created attachment 157191 --> https://bugs.kde.org/attachment.cgi?id=157191&action=edit garbled_fonts SUMMARY When using GTK apps like VScode or Vivaldi, the fonts in some places will become garbled at random times (see screenshot for an example in VScode, particularly the part where it's supposed to say "C/C++"). For VScode, this mostly affects the text shown when one clicks on "Settings". Other places like the editor do not suffer from this problem. For Vivaldi, this affects the names of tabs, but doesn't seem to affect anything else. Happens way more frequently and the garbling is way more noticeable in Vivaldi than in VScode. I suppose it might be related to this other bug: https://bugs.kde.org/show_bug.cgi?id=464824 STEPS TO REPRODUCE (Vivaldi) 1. Launch Vivaldi. 2. Open many websites in many tabs. 3. Browse some website as usual. 4. Look at the tab bar. STEPS TO REPRODUCE (VScode) 1. Launch VScode. 2. Click the settings icon at the bottom-right corner in the side panel. 3. Select "Settings" in the pop-up that opens. 4. Search for something in the settings, such as "cwd" or "path". 5. Watch the panel at the left that shows the categories of settings. OBSERVED RESULT After a while, fonts in the tab bar become garbled in Vivaldi, and fonts in the settings left panel become garbled in VScode. They fix themselves when making the tab active or passing the mouse over them. EXPECTED RESULT Fonts should remain well rendered. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467208] New: Dolphin doesn't find files under hidden folders regardless of settings
https://bugs.kde.org/show_bug.cgi?id=467208 Bug ID: 467208 Summary: Dolphin doesn't find files under hidden folders regardless of settings Classification: Applications Product: dolphin Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: david.cortes.riv...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If I configure dolphin to show hidden files and folders, and then search for the name of some file that's under a hidden folder, it will not show it under the search results. STEPS TO REPRODUCE 1. Launch Dolphin. 2. Go to your user's home. 3. Press Alt+., or tick "Show hidden files" in the hamburger menu. 4. Press the search button. 5. Set it to search for a file name. 6. Search for "ksmserverrc" (it's under ~/.config) OBSERVED RESULT No results are found. EXPECTED RESULT Should find the file. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467208] Dolphin doesn't find files under hidden folders regardless of settings
https://bugs.kde.org/show_bug.cgi?id=467208 --- Comment #2 from David --- (In reply to duha.bugs from comment #1) > Can you run: > balooctl config list hidden > from the Terminal? > > If the Output is "no" then this seems to be intended behavior (Works the > same for me unless I index hidden files with baloo). > See: https://bugs.kde.org/show_bug.cgi?id=391252 > > Alternative solution is to use another search tool (Open Dolphin -> click > the search icon -> More Search Tools). Ok, seems the issue is on ballo. But tying it to dolphin like this is very unintuitive - as a user, I am not aware that I need to configure baloo differently in order to make dolphin show search results with similar settings, and it doesn't offer me to switch the backend from baloo to kfind, only to launch kfind. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467216] New: Cannot search hidden files and folders without indexing them first
https://bugs.kde.org/show_bug.cgi?id=467216 Bug ID: 467216 Summary: Cannot search hidden files and folders without indexing them first Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY I want to be able to search hidden files and folders with KDE's file manager (Dolphin) like it works with Windows Explorer. But (a) it won't let me search for hidden files and folders unless I index the folders where I want this first; (b) the search settings work independently of what's configured in Dolphin. STEPS TO REPRODUCE 1. Go to System Settings -> Search -> File Search. 2. Try to enable searching hidden files and folders without building an index. OBSERVED RESULT Not possible. EXPECTED RESULT Should let me search hidden files and folders without indexing pre-selected folders beforehand, like MS Windows does. Moreover, it should recognize when I search from Dolphin whether I want hidden files/folders from the setting that I am putting in Dolphin. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 467225] New: CPU usage bar is not visible while process is in selection
https://bugs.kde.org/show_bug.cgi?id=467225 Bug ID: 467225 Summary: CPU usage bar is not visible while process is in selection Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 157200 --> https://bugs.kde.org/attachment.cgi?id=157200&action=edit system_monitor_color_invisible SUMMARY If I click a process in the system monitor, the bar with the CPU/Memory utilization becomes invisible while the entry is selected. See attached video. STEPS TO REPRODUCE 1. Launch some process that would use a large amount of CPU for a while. 2. Open system monitor. 3. Go to the processes tab. 4. Locate the process that has high CPU usage. OBSERVED RESULT The bar indicating the CPU consumption over time becomes invisible while the process is the focus of selection. EXPECTED RESULT The bar should remain visible. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 467228] New: Resource usage bars get randomly swapped between processes
https://bugs.kde.org/show_bug.cgi?id=467228 Bug ID: 467228 Summary: Resource usage bars get randomly swapped between processes Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 157201 --> https://bugs.kde.org/attachment.cgi?id=157201&action=edit bar_is_for_wrong_process SUMMARY If I have many processes spawning and closing, the system monitor at times will put the resource usage bars under the wrong process. See attached screenshot where the bars for "qemu" and "xorg" are swapped with each other. STEPS TO REPRODUCE 1. Launch system monitor. 2. Launch some process that would consume a large amount of resources. 3. Start opening and closing apps while keeping an eye on the processes page in the system monitor. OBSERVED RESULT At random times, will swap the usage bars for some applications that have nothing in common. EXPECTED RESULT Should show the bars correctly. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 467229] New: Bars in system monitor are sometimes filled from left to right
https://bugs.kde.org/show_bug.cgi?id=467229 Bug ID: 467229 Summary: Bars in system monitor are sometimes filled from left to right Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY In the previous sytem monitor (ksysguard) and in KDE widgets, the bars that indicate resource usage are filled from right to left, while in system monitor, they are sometimes filled in reverse order - that is, if there is a spike, the spike will first appear from the right of the bar, and move towards the left over time; but in the new system monitor it's the other way around some times. STEPS TO REPRODUCE 1. Launch the system monitor. 2. Open a process that would consume a large amount of CPU resources. 3. Watch the CPU bar consumption. OBSERVED RESULT Sometimes, it fills from right to left, sometimes from left to right, at times it disappears and then shows up again. EXPECTED RESULT Should always show them from right to left like it works in other places, and should keep showing them persistently. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 466958] Allow user to choose whether to install downloaded assets in home folder or systemwide
https://bugs.kde.org/show_bug.cgi?id=466958 --- Comment #5 from David --- (In reply to Alexander Lohnau from comment #4) > There was some (defunct) code that would have allowed this feature. However, > I share Nate's concern about this breaking on immutable OSs. > > THB I am not sure if this feature is even a good idea, because we are still > talking about third-party content. Also, the KPackage installation logic > does not allow system-wide installations. This would be needed in order for > KNewStuff to allow it. But KDE in any event is not even able to start when key paths like /home are read-only, so I don't get why inmutable systems would be a concern if it doesn't run in them. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 466958] Allow user to choose whether to install downloaded assets in home folder or systemwide
https://bugs.kde.org/show_bug.cgi?id=466958 --- Comment #6 from David --- Actually, reading the other bug report, it seems that now things are saved to a different folder. I recall back when the GTK settings had more available things to configure, it was possible to launch the settings as root, install themes there that were put under /home/root, configure visual style for the root user, and then when launching apps my user session but as sudo or root, they would use the theme that was configured for them. Perhaps putting these kinds of things under /home/root could be an option? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467235] New: Clicking appstream link gets discover stuck on 'Loading'
https://bugs.kde.org/show_bug.cgi?id=467235 Bug ID: 467235 Summary: Clicking appstream link gets discover stuck on 'Loading' Classification: Applications Product: Discover Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY If I click a weblink for discover like appstream://org.kde.ksysguard, it opens discover but hangs on a loading screen without showing any message of what's impeding me from installing the app. STEPS TO REPRODUCE 1. Launch discover. 2. Open this page in your web browser: https://apps.kde.org/ksysguard/ 3. Click the big button that says "Install on linux" and which has the breeze discover icon. OBSERVED RESULT Launches discover, but it gets stuck saying "Loading". EXPECTED RESULT Should let me install the app. If anything is missing, should tell me what's wrong. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467252] New: Clipboard nomenclature for next and previous is confusing
https://bugs.kde.org/show_bug.cgi?id=467252 Bug ID: 467252 Summary: Clipboard nomenclature for next and previous is confusing Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY The KDE clipboard has shortcuts for "Next History Item" and "Previous History Item", but the naming is confusing - if I think of "next" and "previous", the first thing I think is the chronological order in which I put the items into the clipboard, but in history order, this works the other way around. STEPS TO REPRODUCE 1. Try to assign shortcuts for next and previous items in the clipboard. OBSERVED RESULT Shortcuts are for "next/previous in history" which is the opposite of chronological order. EXPECTED RESULT Should have shortcuts for "next item" and "previous item" in the order that they were sent to the clipboard. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466820] Flickering when starting X11 session with 6.2.1 / 6.2.2
https://bugs.kde.org/show_bug.cgi?id=466820 --- Comment #1 from David --- If there is anything that I can provide (logs etc) please let me know which one you'll need etc. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 David changed: What|Removed |Added CC||gglol555gglol...@gmail.com --- Comment #38 from David --- I encounter this issue every time I attempt to open submenus in various applications such as Firefox, Steam, Wine, and VSCodium. Resolution: 2880x1620@200% Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 --- Comment #39 from David --- Wine apps* -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467287] New: Deleting many files takes scroll focus to wrong end
https://bugs.kde.org/show_bug.cgi?id=467287 Bug ID: 467287 Summary: Deleting many files takes scroll focus to wrong end Classification: Applications Product: dolphin Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: david.cortes.riv...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If I select many files in Dolphin in a way that moves the position within the scrolling bar downwards and then delete the files, it will not take me back to the scrolling part where my selection had started - instead, it will keep the same position, but as I deleted many files, this is now far apart from the beginning of the selection. STEPS TO REPRODUCE 1. Create a folder with lots of files. 2. Launch Dolphin. 3. Configure Dolphin to group files by type (not sure if this is entirely required) and show icons. 4. Position somewhere in the middle of the available scrolling on the right panel. 5. Start a selection rectangle by holding a mouse click and moving it downwards. 6. Let it select many files, taking the scrolling position below what it was before. 7. Delete the files with Shift+Del. OBSERVED RESULT Puts the focus on what would have been the end of the selection rectangle. As the files no longer exist, this means that it skipped a lot of files to show to me, since unseen files moved ahead of my current view. EXPECTED RESULT Should bring back the focus to where the selection rectangle began, like in windows explorer. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467047] GTK file picker ignores single/double click settings
https://bugs.kde.org/show_bug.cgi?id=467047 --- Comment #2 from David --- (In reply to Nate Graham from comment #1) > KDE doesn't control the GTK file dialog, which at some point removed the > feature to allow you to single-click; now it only accepts double-clicks. > > This annoyance is why KDE users generally prefer the KDE file dialogs over > the GTK file dialogs. :) But it somehow managed to have KDE settings applied to it on previous plasma versions. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467047] GTK file picker ignores single/double click settings
https://bugs.kde.org/show_bug.cgi?id=467047 --- Comment #4 from David --- (In reply to Nate Graham from comment #3) > I'm assuming you just upgraded Debian. That being the case, Plasma wasn't > the only thing that got upgraded; GTK did too. The feature was removed in a > GTK release at some point in the last few years. Ok, I did some experiments and turns out what changed this for me was not having an environment variable GTK_USE_PORTAL=1. Any reason why that variable isn't set by default in plasma? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467056] New lock screen buttons are unintuitive
https://bugs.kde.org/show_bug.cgi?id=467056 --- Comment #2 from David --- Created attachment 157237 --> https://bugs.kde.org/attachment.cgi?id=157237&action=edit kde_lock_screen_strange_button Attached a screenshot of the new button on the new lock screen. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 467056] Fallback theme's icons-only buttons lack tooltips
https://bugs.kde.org/show_bug.cgi?id=467056 --- Comment #4 from David --- Created attachment 157239 --> https://bugs.kde.org/attachment.cgi?id=157239&action=edit kde_sddm_is_breeze But I have my settings configured to use the default breeze theme, just without the picture. Moreover, it does display the breeze theme if I click that button to change user. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467064] Transparency in menus stops working after launching certain apps
https://bugs.kde.org/show_bug.cgi?id=467064 --- Comment #6 from David --- (In reply to Nate Graham from comment #5) > 1. Are any of the windows for those apps touching your Panel/taskbar when > this happens? > 2. Are you able to force the panel and its popups to always be opaque or > translucent using the options with the same name in the "More Options" popup > of the panel edit mode toolbar? > 3. I notice the menu background doesn't have blur. Is the "Blur" effect in > System Settings > Workspace Behavior > Desktop Effects disabled? Or does it > not even appear there? 1. It doesn't make a difference if I start them maximized (they touch the panel) or not (don't touch the panel). It also keeps being broken after I close the apps. 2. Yes, and forcing it to be transparent has the intended effect in the pop-ups, with the undesirable side effect that now the whole panel is transparent. 3. It's there, and I have it deactivated so that the pop-ups would look like in the first screenshot. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467118] Screenshots taken after "annotate" are lost
https://bugs.kde.org/show_bug.cgi?id=467118 --- Comment #2 from David --- (In reply to Nate Graham from comment #1) > By default, the Print Screen button takes a new screenshot, overwriting the > current one. If you want it to open a new window instead, there's an option > for this in the settings window. If I configure it like that, the new window will not pop-up with a screenshot of the screen at the moment it was taken. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467119] Tooltips are oftentimes cut when they intersect with something
https://bugs.kde.org/show_bug.cgi?id=467119 --- Comment #2 from David --- Created attachment 157240 --> https://bugs.kde.org/attachment.cgi?id=157240&action=edit kde_font_settings I am using debian-default fonts (which look different from the ones in your screenshot) with non-default sizes. Attached is a screenshot of the configuration. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467294] New: New spectacle window opens without new screenshot if taken while another has the annotate toolbox
https://bugs.kde.org/show_bug.cgi?id=467294 Bug ID: 467294 Summary: New spectacle window opens without new screenshot if taken while another has the annotate toolbox Classification: Applications Product: Spectacle Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: david.cortes.riv...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY >From other bug report: https://bugs.kde.org/show_bug.cgi?id=467118 STEPS TO REPRODUCE 1. Launch spectacle. 2. Click "Configure". 3. Select "While Spectacle is running" -> "Press screenshot key to" -> "Open a new Spectacle window". 4. Close spectacle. 5. Press "print screen". 6. In the spectacle window that pops up, click "Annotate". 7. Press "print screen" again. OBSERVED RESULT Opens a new spectacle window **with the old screenshot** that's being annotated in the previous window. EXPECTED RESULT Should open a new spectacle window with a snapshot of the screen at the moment I pressed the print screen button. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467118] Screenshots taken after "annotate" are lost
https://bugs.kde.org/show_bug.cgi?id=467118 --- Comment #4 from David --- (In reply to Nate Graham from comment #3) > That seems like a bug; please submit a new bug report for it. I opened a new bug report: https://bugs.kde.org/show_bug.cgi?id=458713 But in any event, this is **still** a bug under the default configuration: it says "While Spectacle is running" -> "Press screenshot key to:" -> "Take a new Screenshot". In this case, if I press the screenshot key, it doesn't take a new screenshot like it would do if the annotation toolbox was closed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467295] New: Login screen background applies to lock screen, but this is not mentioned in the settings
https://bugs.kde.org/show_bug.cgi?id=467295 Bug ID: 467295 Summary: Login screen background applies to lock screen, but this is not mentioned in the settings Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY if I configure a picture for the login screen, it also applies to the lock screen, but it doesn't tell me that it would do so. STEPS TO REPRODUCE 1. Go to System Settings -> Startup and Shutdown -> Login Screen (SDDM) -> choose "Breeze". 2. Click the picture icon on the "Breeze" option. 3. Select a picture. 4. Lock the screen with Windows+L or similar. OBSERVED RESULT Has the picture that I put for login screen, but it didn't tell me about it. EXPECTED RESULT Should inform me that this is for both login and lock. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467017] No shortcut for "restart computer"
https://bugs.kde.org/show_bug.cgi?id=467017 --- Comment #2 from David --- (In reply to Nate Graham from comment #1) > > *** This bug has been marked as a duplicate of bug 465584 *** But this is not a duplicate: it's very reasonable to want different shortcuts for "restart", "shutdown", "sleep"; regardless of what's the default logout option. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464824] GTK don't follow global font configuration
https://bugs.kde.org/show_bug.cgi?id=464824 --- Comment #5 from David --- (In reply to Nate Graham from comment #4) > Don't remove xsettings; kde-gtk-config uses it to configure GTK settings. > > David, in System Settings > Startup and Shutdown > Background Services, is > "GNOME/GTK Settings Synchronization service" running? > > Can you paste the output of running `cat ~/.config/gtk-*.0/settings.ini` in > a terminal window? The service shows as "Running". Output from settings.ini is as follows: [Settings] gtk-application-prefer-dark-theme=true gtk-button-images=true gtk-cursor-theme-name=Adwaita gtk-cursor-theme-size=24 gtk-decoration-layout=icon:minimize,maximize,close gtk-enable-animations=true gtk-font-name=Noto Sans, 11 gtk-icon-theme-name=breeze-dark gtk-menu-images=true gtk-modules=colorreload-gtk-module:window-decorations-gtk-module gtk-primary-button-warps-slider=false gtk-theme-name=Materia-Breeze-gtk gtk-toolbar-style=3 gtk-xft-dpi=98304 [Settings] gtk-application-prefer-dark-theme=true gtk-cursor-theme-name=Adwaita gtk-cursor-theme-size=24 gtk-decoration-layout=icon:minimize,maximize,close gtk-enable-animations=true gtk-font-name=Noto Sans, 11 gtk-icon-theme-name=breeze-dark gtk-modules=colorreload-gtk-module:window-decorations-gtk-module gtk-primary-button-warps-slider=false gtk-theme-name=Materia-Breeze-gtk gtk-xft-dpi=98304 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467301] New: Cannot put toolbar shortcut for new text file
https://bugs.kde.org/show_bug.cgi?id=467301 Bug ID: 467301 Summary: Cannot put toolbar shortcut for new text file Classification: Applications Product: dolphin Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: david.cortes.riv...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin has a shorthand for creating a new folder and different types of new files, but only the option for folder can be put directly in the toolbar, while the others are all grouped together under 'New'. STEPS TO REPRODUCE 1. Launch Dolphin. 2. Click the hamburger menu -> Configure -> Configure Toolbars. 3. Try to put a button for creating an empty text file. OBSERVED RESULT Not possible. EXPECTED RESULT Should have a shortcut icon for creating a new empty text file, like it has in the right-click menu. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402857] Touchpad gestures are not configurable
https://bugs.kde.org/show_bug.cgi?id=402857 --- Comment #5 from David --- (In reply to Petrov Egor from comment #4) > Sadly that in the most configurable DE touchpad gestures couldn'be > customized;( I cannot help it but agree on this one. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467064] Transparency in menus stops working after launching certain apps
https://bugs.kde.org/show_bug.cgi?id=467064 --- Comment #8 from David --- (In reply to Nate Graham from comment #7) > Any chance it starts working again if you re-enable "Background Contrast" > and "Blur"? > > What about if you use Kicker or the new Kickoff, and not the old Kickoff? But still happens when enabling "Blur" or "Background Contrast" or switching to the new application launchers. The bug also happens to tooltips when I hover the mouse over a widget and to the clock/calendar if I click it. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467216] Cannot search hidden files and folders without indexing them first
https://bugs.kde.org/show_bug.cgi?id=467216 --- Comment #2 from David --- (In reply to Nate Graham from comment #1) > > Try to enable searching hidden files and folders without building an index > That's not how the Baloo file indexing service works; it's inherently > index-based. It builds an index and when when you search for something, it > consults its index. > > If you want a non-indexed search that crawls the filesystem in real-time, > you might appreciate the KFind app. > > What's wrong with the index-based search that makes you want to not use it? (a) This search is nevertheless embedded into other apps, such as Dolphin. It doesn't give an option to switch my global KDE search backend to KFind instead of baloo. (b) I very seldom need to search files in KDE software so I don't benefit from an index. (c) This is only used in KDE software. Other software doesn't rely on it when searching. (d) I have many files. I don't want to be telling baloo what to index or what not. (e) Indexing is a resource-heavy operation, and even the GNOME indexer consumes too many resources for my setup. (f) There's little speed difference in searching for just file names with or without an index. (g) Indexes use extra space and produce extra wear and tear on my disk. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467235] Clicking appstream link gets discover stuck on 'Loading'
https://bugs.kde.org/show_bug.cgi?id=467235 --- Comment #2 from David --- (In reply to Nate Graham from comment #1) > On my Fedora KDE 37 system Discover loads in under a second. > > Does this long loading process happen when you launch Discover normally, or > only when launching it with a URL, via the button on that website? How about > if you launch it by running `xdg-open appstream://org.kde.ksysguard` in a > terminal window? By "Loading process" I mean the discover app already launched, and usable if you click other buttons, but stuck on saying "Loading" when it should show me something to install KSysGuard. This is what I get from doing executing the command in the terminal and then clicking the discover window: david@debian:~$ xdg-open appstream://org.kde.ksysguard david@debian:~$ fetch ratings! false adding empty sources model QStandardItemModel(0x557bf5fe2dc0) -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466907] System monitor settings pop-up cannot be dragged
https://bugs.kde.org/show_bug.cgi?id=466907 --- Comment #2 from David --- (In reply to Nate Graham from comment #1) > It's not a window, it's a modal popup. So I'm afraid the fact that it can't > be dragged around is by design. This is very inconvenient since I cannot see what I'm going to get out of the settings that I'm configuring, and I cannot see what I already have and what I'm missing. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467119] Tooltips are oftentimes cut when they intersect with something
https://bugs.kde.org/show_bug.cgi?id=467119 --- Comment #4 from David --- (In reply to Nate Graham from comment #3) > Hah, your settings are actually identical to my own. Can you try to find a > pattern for which tooltips get cut off and which ones don't? Are the cut-off > ones always near the right screen edge? Do you have multiple monitors? Does > it reproduce with a new user account? (a) All tooltips in QT apps get cut at random times. (b) No, happens anywhere, including in the middle of the app if they intersect with another button. (c) I have a single monitor. (d) Haven't tried with a different user, but this is a new computer that I set up without carrying any old settings under /home. Every setting I've changed was done manually through the current systemsettings5 app from plasma 5.27.2. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467295] Login screen background applies to lock screen, but this is not mentioned in the settings
https://bugs.kde.org/show_bug.cgi?id=467295 --- Comment #2 from David --- (In reply to Nate Graham from comment #1) > > if I configure a picture for the login screen, it also applies to the lock > > screen > It does not. The lock and login screens use separate images. What you are > describing is not possible if the system is working normally. Are you still > affected bu the issue we found in Bug 467056 that causes you to see the > fallback lock screen theme because the one you've got selected is broken? Yes, this applies to the fallback lock screen which I am being shown. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467350] New: Discover hangs while deleting settings and user data
https://bugs.kde.org/show_bug.cgi?id=467350 Bug ID: 467350 Summary: Discover hangs while deleting settings and user data Classification: Applications Product: Discover Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Discover hangs without telling me that it's doing something when I uninstall a flatpak app and let it delete the user data that came with it. STEPS TO REPRODUCE 1. Launch discover. 2. Search for "inkscape". 3. Click the result for "inkscape". 4. Click Sources -> Flathub. 5. Click Install. 6. Launch Inkscape, do something with it, then exit. 7. Go back to discover, uninstall inkscape in the same window from where it was installed, and after that, click the button to delete settings and user data. OBSERVED RESULT Hangs for a while, then finishes and becomes responsive again. EXPECTED RESULT Should not hang. If it's doing something, should tell what exactly it is and show me a progress bar SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467295] Login screen background applies to lock screen, but this is not mentioned in the settings
https://bugs.kde.org/show_bug.cgi?id=467295 --- Comment #4 from David --- (In reply to Nate Graham from comment #3) > So when you change the image for the SDDM login screen, no matter what you > set there, that image is displayed as the background of the fallback lock > screen? When I change the **breeze** image. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464824] GTK don't follow global font configuration
https://bugs.kde.org/show_bug.cgi?id=464824 --- Comment #7 from David --- (In reply to Nate Graham from comment #6) > It looks like the GTK config files are correct. Which GTK apps specifically > are not respecting these settings? Can you also try with Inkscape and GIMP? > Do they respect the settings? Apps that show different fonts: - Evolution - GEdit - Sublime - VScode - Vivaldi However, they don't show different fonts everywhere - for example, the menus in application bars show the fonts that I have configured, while the emails in evolution use other fonts. Same in Vivaldi - the tab names don't use my configured fonts, while other things do. It's particularly noticeable in apps like gedit or sublime (text editors), since it applies to text in the files that they open. And if you use "Noto Sans" in KDE, you can check the lowercase R letters in those apps for a starker contrast. See the picture here for example: https://github.com/microsoft/vscode-jupyter/issues/13012 I tried playing a bit with inkscape but I don't know what the app does or how to use it. As far as I could tell, the menus and the welcome page were using my configured fonts, but don't know where else it's supposed to show text. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467252] Clipboard nomenclature for next and previous is confusing
https://bugs.kde.org/show_bug.cgi?id=467252 --- Comment #2 from David --- (In reply to Nate Graham from comment #1) > They mean "Next in the list." Do you have an idea how they could be > rephrased for more clarity? Next History Item -> Previous Item Previous History Item -> Next Item Plus swapping the direction of the arrows, and maybe showing the list in reverse order so that the most recent item is at the bottom. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467359] New: Request: re-enable running Dolphin as sudo
https://bugs.kde.org/show_bug.cgi?id=467359 Bug ID: 467359 Summary: Request: re-enable running Dolphin as sudo Classification: Applications Product: dolphin Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: david.cortes.riv...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- It's been many years since the functionality for running Dolphin as sudo was artifically disabled, with the expectation that "soon" Dolphin will be able to poll for sudo privileges when it needs to, so that users wouldn't need to run it as sudo. The justification when I try to run it as sudo says: "Running Dolphin with sudo can cause bugs and expose you to security vulnerabilities. Instead use Dolphin normally and you will be prompted for elevated privileges when performing file operations that require them." But this is incorrect, since the functionality for requesting privileges still hasn't been implemented after all these years. Since this anti-feature was imposed, it has not been possible anymore to, among other things: - Delve into folders for which one has no access. Practical example: try to browse virtual machines from qemu (/var/lib/libvirt). - Delete files that are not owned by the user. Practical example: create some file in a dockerized application that someone else created (they typically run as root). - Change ownership and privileges of files, folders, or change them recursively for folders in which something underneath is not user-owned. Practical example: try moving some paths under your /home path to a separate BTRFS subvolume. - Create symlinks between files and folders under paths like /etc. Practical example: try temporarily swapping a system library with another in a non-debian system (e.g. openblas with MKL). - Drag things from a user folder to a non-user folder or vice-versa. Practical example: again playing with docker containers. Now, I need to keep several file managers in my system so that I can do the kind of things that a file manager is supposed to do, which is very inconvenient. Dolphin is a file manager. It should be able to do these things. Nemo lets me do them. So does thunar. If the replacement functionality is not there, then please please wait until the fix arrives before removing the ability of Dolphin to perform its job. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467361] New: Breeze style doesn't apply arrow settings to GTK apps
https://bugs.kde.org/show_bug.cgi?id=467361 Bug ID: 467361 Summary: Breeze style doesn't apply arrow settings to GTK apps Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY Under the new logic of GTK settings carryover where things aren't configurable independently for GTK, if I select an application style like "breeze" and configure it to show arrows on scrollbars, it will not show arrows on scrollbars of GTK apps. STEPS TO REPRODUCE 1. Go to System Settings -> Appearance -> Global Theme -> Application Style -> select "Breeze". 2. Click the edit button in the breeze rectangle. 3. Go to "scrollbars". 4. Set both "Top arrow button type" and "Bottom arrow button type" to something **other** than "No buttons". 5. Apply the settings. Optionally, restart computer at this point. 6. Launch some GTK app like "nemo" or "evolution". Put it into a situation in which it will need a scrollbar - for example, by browsing a folder with many files, or by having many emails to browse. OBSERVED RESULT Scrollbars don't have arrows. EXPECTED RESULT Scrollbars should have arrows. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-6-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467362] New: Dolphin crash while changing application styles in settings
https://bugs.kde.org/show_bug.cgi?id=467362 Bug ID: 467362 Summary: Dolphin crash while changing application styles in settings Classification: Applications Product: dolphin Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: david.cortes.riv...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 157284 --> https://bugs.kde.org/attachment.cgi?id=157284&action=edit dolphin_err_log SUMMARY Dolphin crashed while changing application styles in the settngs. Attached is the error log. STEPS TO REPRODUCE (not sure) 1. Launch a dolphin window. Open a terminal there. 2. Launch another dolphin window. 3. Go to system settings -> appearance -> global theme -> application style. 4. Change the style. 5. Go back to dolphin window and close it. 6. Change the style again. 7. Launch a new dolphin window. 8. Close it. 9. Go back to the first window and close the terminal. OBSERVED RESULT Crashes. EXPECTED RESULT Should not crash. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467235] Clicking appstream link gets discover stuck on 'Loading'
https://bugs.kde.org/show_bug.cgi?id=467235 --- Comment #4 from David --- (In reply to Nate Graham from comment #3) > Hmm, what does `appstreamcli search org.kde.ksysguard` say? > > Can you successfully search for "KsysGuard" within Discover? I can search for it in discover's search bar, but it doesn't return any results that would involve the application "ksysguard", only things like "page that looks more like ksysguard ..." for the new system monitor. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467216] Cannot search hidden files and folders with built-in search; have to use Baloo file search
https://bugs.kde.org/show_bug.cgi?id=467216 --- Comment #5 from David --- (In reply to tagwerk19 from comment #3) > (In reply to David from comment #0) > > ... enable searching hidden files and folders without building an index > This is the same as Bug 467208? > > There is a "fallback" within dolphin to do "there and then" searches when > you don't have baloo running or you have moved to a folder that baloo has > not indexed and are searching from there. It seems though that that search > does not hunt down through hidden folders as you might expect if you have > told dolphin to show hidden files. > > Probably worth fixing. > > Flaggings as confirmed on the basis of > https://bugs.kde.org/show_bug.cgi?id=467208#c4 but maybe this will end up as > a duplicate... > > The fact that dolphin falls back to its own searching is a bit of a hidden > (and sometimes confusing) feature :-/ It's not just dolphin - krunner is also connected with this. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464824] GTK don't follow global font configuration
https://bugs.kde.org/show_bug.cgi?id=464824 --- Comment #9 from David --- (In reply to Nate Graham from comment #8) > Note that VSCode isn't a GTK app; it's an electron app. Sublime has its own > font/text configuration facilities. Vivaldi I'm not 100% sure about but I am > pretty sure it's not a pure GTK app either. And web browsers in general > often have their own in-app font/text configuration facilities. > > So the only apps in that list that I would *expect* to be respecting the > font specified in the GTK files are Gedit and Evolution. Since it looks like > your config files are set up properly, it seems like this may be an issue in > those apps, or in GTK, or in how things are packaged on your machine. It > looks to me like the relevant KDE code is doing its part so at this point > I'd recommend asking for help in a Debian-specific forum. These apps were all following the KDE font config as of debian sid of 2 months ago. I think the only large things that updated during that period were KDE things like frameworks. Downgrading the software in question to previous versions doesn't solve the issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467216] Cannot search hidden files and folders with built-in search; have to use Baloo file search
https://bugs.kde.org/show_bug.cgi?id=467216 --- Comment #7 from David --- (In reply to Nate Graham from comment #6) > If you want this to work systemwide, you're essentially asking for an > entirely new optional search system to replace Baloo in all of the places > where it's currently used. > > Such a thing is possible, of course. But please realize that it's a big > request. :) Probably something that's bigger in scope than can reasonably be > encompassed by a bug report/feature request. See also > https://community.kde.org/Get_Involved/Issue_Reporting#Step_1: > _Make_sure_it's_a_valid_bug_or_feature_request. But it doesn't need to change the backed, just to let baloo search for hidden files too like it is currently doing for non-hidden files without indexing. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467235] Clicking appstream link gets discover stuck on 'Loading'
https://bugs.kde.org/show_bug.cgi?id=467235 --- Comment #6 from David --- (In reply to Nate Graham from comment #5) > Thanks. And what does `appstreamcli search org.kde.ksysguard` say? This is what it shows after I installed ksysguard from source through the cmake script: Identifier: org.kde.ksysguard [desktop-application] Name: KSysGuard Summary: Monitor running processes and system performance Homepage: https://kde.org/plasma-desktop Icon: utilities-system-monitor -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467235] Clicking appstream link gets discover stuck on 'Loading'
https://bugs.kde.org/show_bug.cgi?id=467235 --- Comment #8 from David --- (In reply to Nate Graham from comment #7) > > This is what it shows after I installed ksysguard from source through the > > cmake script: > Nono, that's not what I wanted. :) Does `appstreamcli search > org.kde.ksysguard` display the same output *before* you compile and build > ksysguard locally? If you purge all files for it, what does `appstreamcli > search org.kde.ksysguard` say? Don't know. I already installed it. The cmake script fails to execute 'make uninstall'. And it seems it left something in my user folder, because if I boot into an earlier snapshot, ksysguard still shows up in the applications launcher, but kfind doesn't find anything 'ksysguard' in my user folder outside of the folder with the source code. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467235] Clicking appstream link gets discover stuck on 'Loading'
https://bugs.kde.org/show_bug.cgi?id=467235 --- Comment #9 from David --- For comparison, if instead of ksysguard I try krita, it does end up showing something in discover. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467235] Clicking appstream link gets discover stuck on 'Loading'
https://bugs.kde.org/show_bug.cgi?id=467235 --- Comment #10 from David --- Ok, so found another app that also hangs in loading: https://apps.kde.org/amarok The link is: appstream://org.kde.amarok.desktop The command line says: Unable to find component matching org.kde.amarok! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467361] Breeze style doesn't apply scrollbar arrow settings to GTK apps' scrollbars
https://bugs.kde.org/show_bug.cgi?id=467361 --- Comment #2 from David --- (In reply to Nate Graham from comment #1) > Do you know if this worked in the past? And in the present, does GTK even > support these settings with the same level of granularity that we do? i.e. > can you manually make the GTK apps' scrollbars have the same number and > position of arrows that you can with Qt apps' scrollbars? I don't know if Breeze applied those settings to QT in the past. But back then, it was possible to choose the GTK application style and set something other than breeze. Don't remember if the arrows were applied from another theme either. I'm not familiar with other linux DEs so don't know how to configure that sort of thing either. -- You are receiving this mail because: You are watching all bug changes.
