[plasmashell] [Bug 486059] ICon-only task manager icons small on startup. entering and exiting edit mode fixes it
https://bugs.kde.org/show_bug.cgi?id=486059 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com --- Comment #1 from Ben Daines --- Same issue here. Plasma 6.0.4 on Manjaro. Turns out trying to take a screen shot is another method to "fix" it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487259] Decorations and window content do not move together
https://bugs.kde.org/show_bug.cgi?id=487259 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487259] New: Decorations and window content do not move together
https://bugs.kde.org/show_bug.cgi?id=487259 Bug ID: 487259 Summary: Decorations and window content do not move together Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: aurorae Assignee: kwin-bugs-n...@kde.org Reporter: benjamindai...@gmail.com Target Milestone: --- Created attachment 169637 --> https://bugs.kde.org/attachment.cgi?id=169637=edit Screencast of moving a window around, demonstrating the issue. Wayland session, Manjaro (up to date as of 5/18/24), Plasma 6. After updating to Plasma 6, window decorations are slightly detached from window contents. Small cursor movements (drag) will move the titlebar a pixel or two before the contents start to move. Title bar can also end up a pixel or two misplaced when a drag operation is completed. I am using Klassy decorations, but I did confirm the issue is present with Breeze (both window style and decoration applied) Filing under aurorae, but this could be a kwin problem (I have nothing to support the assumption) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446166] Changing window decorations to anything not default causes a system performance hit
https://bugs.kde.org/show_bug.cgi?id=446166 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com --- Comment #3 from Ben Daines --- Does this happen with one of the newer themes? (Klassy, or there's a few breeze forks out there) -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 487201] System Monitor crashes when opening details sidepanel
https://bugs.kde.org/show_bug.cgi?id=487201 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 487201] New: System Monitor crashes when opening details sidepanel
https://bugs.kde.org/show_bug.cgi?id=487201 Bug ID: 487201 Summary: System Monitor crashes when opening details sidepanel Classification: Applications Product: plasma-systemmonitor Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: benjamindai...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- [ben@pluto ~]$ plasma-systemmonitor qrc:/qt/qml/org/kde/ksysguard/page/EditablePage.qml?page=history.page:223:9: QML Loader: Binding loop detected for property "height" file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth" file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding: Binding loop detected for property "target" qrc:/qt/qml/org/kde/ksysguard/page/EditablePage.qml?page=overview.page:223:9: QML Loader: Binding loop detected for property "height" file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth" file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding: Binding loop detected for property "target" Segmentation fault (core dumped) Manjaro 24, Plasma 6. plasma-systemmonitor crashes when trying to open the details side panel via the Applications tab. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483505] System restart required message should be more clear to the user
https://bugs.kde.org/show_bug.cgi?id=483505 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483505] New: System restart required message should be more clear to the user
https://bugs.kde.org/show_bug.cgi?id=483505 Bug ID: 483505 Summary: System restart required message should be more clear to the user Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_baloo Assignee: plasma-b...@kde.org Reporter: benjamindai...@gmail.com CC: baloo-bugs-n...@kde.org Target Milestone: --- SUMMARY When manually adding directories to be either indexed or not indexed, a message is displayed at the top of the screen after clicking apply saying that "the system must be restarted for changes to take effect." The user is here presented with a restart button with a spinning arrows icon that seems to indicate that the entire system will be restarted if the button is clicked. The biggest issue is that (under Plasma 5 Wayland) work will be lost when the session is ended if this button does indeed restart the entire system to make changes to the indexed directories. Supposedly this is fixed with Plasma 6, so that may be a non-issue. However, needing to restart the entire system seems quite intrusive when I can confirm that merely restarting the user service for kde-baloo is plenty to what needs to be done. I purpose that this message should be worded better, either specify that you do in fact mean the computer or the session rather than just "system." The indexing system? The computer system? The what? More to the point of sanity, I would hope that this message can be clarified as "the indexing service needs to be restarted..." and that button can be made to simply restart the baloo service for the current session without requiring the session to be ended or the computer rebooted. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 480579] No support for emoji in text annotations
https://bugs.kde.org/show_bug.cgi?id=480579 --- Comment #4 from Ben Daines --- (In reply to Noah Davis from comment #1) > (In reply to Ben Daines from comment #0) > > SUMMARY > > When annotating a screenshot, there is no support for emoji characters (or > > very limited... no proper support anyway) when adding text to a screen > > shot. > > > > EXPECTED RESULT > > Text annotations should be updated to support emoji characters / fonts. > > What do you mean by "no support"? Do you mean emoji characters won't render > at all or do you get ugly line art emojis? The latter is an unfortunately a > common Linux system configuration issue. Most of the guides I've seen tell > you to manually modify ~/.config/fontconfig/fonts.conf They do not render at all. If I remember correctly you just get a blank square. Whatever font is being used doesn't seem to have emoji characters. This is despite my having installed emoji fonts that work elsewhere. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 480579] No support for emoji in text annotations
https://bugs.kde.org/show_bug.cgi?id=480579 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 480579] New: No support for emoji in text annotations
https://bugs.kde.org/show_bug.cgi?id=480579 Bug ID: 480579 Summary: No support for emoji in text annotations Classification: Applications Product: Spectacle Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: benjamindai...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY When annotating a screenshot, there is no support for emoji characters (or very limited... no proper support anyway) when adding text to a screen shot. EXPECTED RESULT Text annotations should be updated to support emoji characters / fonts. -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 479562] Timers should show time remaining
https://bugs.kde.org/show_bug.cgi?id=479562 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 479562] New: Timers should show time remaining
https://bugs.kde.org/show_bug.cgi?id=479562 Bug ID: 479562 Summary: Timers should show time remaining Classification: Applications Product: KClock Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: espi...@gmail.com Reporter: benjamindai...@gmail.com CC: hanyo...@protonmail.com Target Milestone: --- SUMMARY *** Currently when a timer is running, the user is shown the time that has elapsed since the timer was started, and the amount of time that the timer was set for. Typically timers show T- for the time remaining. KClock does this differently, perhaps incorrectly... a setting would be nice and, personally, I would find the remaining time more useful than the total time or the time that has elapsed. The current design makes me do math to get the information that I want / need. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 --- Comment #49 from Ben Daines --- (In reply to holyzolly from comment #47) > Ok so thinking about why we don't know who gets affected and why workaround > work for some people and for some won't. > Somebody mentioned it's display related. > Then my assumption is it is HDR related, with all the good news in this > subject! > (It is so in my case also, on my old laptop, no issue. Here on desktop I've > got a 4K-HDR capable screen [that can also emulate HDR, don't know if that > info is important]) > So here the question for all reading this: > > 1.) If you are affected: Do you have a capable HDR screen connected? > 2.) If you are not affected: you don't an HDR capable screen connected, I > assume? > 3.) If you could work around it with the known workarounds? Do you have an > HDR capable screen connected? > > Please report and I hope this will help solve the issue... :) No HDR screens, it seems to be an issue with ddcutil not knowing how to deal with unrecognized screens. Have not used any workaround, just downgraded to packages before the issue existed. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 --- Comment #45 from Ben Daines --- (In reply to Altamush Nayyer Khan from comment #44) > I don't think disconnecting any monitor or any hardware that you require to > get work done smoothly is a solution. That is the reason why I never thought > about disconnecting any of my monitors. There is already a temporary > solution for it that was posted on the Arch Wiki. > > I will link to it. It solved my problem. Hopefully it will also solve yours. > > https://bbs.archlinux.org/viewtopic.php?pid=2136605#p2136605 Thanks. I'll give that a try instead of downgrading packages after the next distro update that doesn't fix it. As an aside, why do people make YouTube videos for console related topics? The internet has the ability to contain text -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 --- Comment #43 from Ben Daines --- (In reply to Ben Daines from comment #42) > (In reply to Altamush Nayyer Khan from comment #41) > > (In reply to Ben Daines from comment #40) > > > (In reply to Markus from comment #39) > > > > For me, powerdevil only crashes when an Apple Cinema Display (model > > > > A1267) > > > > > > I am also having the issue with an Apple Cinema Display connected via DVI > > > as > > > my second display (desktop system with display port for the primary > > > display). Mine is older than yours, the A1082 23" aluminum LCD from 2004 > > > > I have heard that the bug is caused due to specific monitor or device > > configurations. I am not very sure about this. I just read it on the Arch > > Forums that a person just removed one of their monitors and the problem > > disappeared. > > "Just don't use your monitor" hardly sounds like a solution. I do realize you're trying to offer a workaround, however I've rolled back the powerdevil & ddcutil packages as a temporary solution. Hopefully this will be fixed before Plasma 6 is released, as I imagine rolling back those packages might not work quite so well after a major update like Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 --- Comment #42 from Ben Daines --- (In reply to Altamush Nayyer Khan from comment #41) > (In reply to Ben Daines from comment #40) > > (In reply to Markus from comment #39) > > > For me, powerdevil only crashes when an Apple Cinema Display (model A1267) > > > > I am also having the issue with an Apple Cinema Display connected via DVI as > > my second display (desktop system with display port for the primary > > display). Mine is older than yours, the A1082 23" aluminum LCD from 2004 > > I have heard that the bug is caused due to specific monitor or device > configurations. I am not very sure about this. I just read it on the Arch > Forums that a person just removed one of their monitors and the problem > disappeared. "Just don't use your monitor" hardly sounds like a solution. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com --- Comment #40 from Ben Daines --- (In reply to Markus from comment #39) > For me, powerdevil only crashes when an Apple Cinema Display (model A1267) I am also having the issue with an Apple Cinema Display connected via DVI as my second display (desktop system with display port for the primary display). Mine is older than yours, the A1082 23" aluminum LCD from 2004 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452119] With an Intel iGPU, animations aren't as smooth on Wayland versus Xorg
https://bugs.kde.org/show_bug.cgi?id=452119 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com --- Comment #73 from Ben Daines --- (In reply to syed.talha.khalid from comment #72) > (In reply to Zamundaaa from comment #71) > > Git commit 4ad5670ddfcd7400c8b84c12cbf8bd97a0590f43 by Xaver Hugl. > > Committed on 07/12/2023 at 14:17. > > Pushed by zamundaaa into branch 'master'. > > > > backends/drm: set dma-fence deadlines if available > > > > This tells the kernel when a buffer should be done rendering, which allows > > it to for example increase GPU clocks in order to hopefully hit our > > deadlines. > > That in turn should reduce the amount of dropped frames > > > > M +27 -10 src/backends/drm/drm_buffer.cpp > > M +3-0src/backends/drm/drm_buffer.h > > M +9-0src/backends/drm/drm_commit.cpp > > M +1-0src/backends/drm/drm_commit.h > > M +1-0src/backends/drm/drm_commit_thread.cpp > > > > https://invent.kde.org/plasma/kwin/-/commit/ > > 4ad5670ddfcd7400c8b84c12cbf8bd97a0590f43 > > Is it possible we can get this fix integrated in the current version of > KWin? > I think this is the major show stopper for Intel iGPU user on KDE Wayland. That would be pretty sweet. Plasma 6 release is still months away and distros will take even longer to include Plasma 6 on their own schedules. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 474167] [wayland] Firefox launching with incorrect DPI & GTK theming
https://bugs.kde.org/show_bug.cgi?id=474167 --- Comment #1 from Ben Daines --- Just mentioning that this is still an issue with the latest git build and I have still been unable to figure out why it's happening or found any kind of workaround for it. I don't see anything in the Firefox.desktop file that looks suspicious to me. Very strange. If anyone has any ideas as to what I can poke around in to try to find a work around until this can be addressed, please let me know. Thanks :) PS Latte is still the best dock / mouse-based launcher for KDE, and is (imo) essential to Plasma. PPS Also, I would like to clarify that it is the entire Firefox UI that has the wrong DPI, not just the mouse cursor. I am not sure that is clear from the initial posting. Linux/KDE Plasma: 6.5.5-1-MANJARO (64-bit) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Graphics Platform: Wayland (Mesa Intel HD Graphics 5500) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 467292] Interacting with widget makes icons of currently running apps disappear
https://bugs.kde.org/show_bug.cgi?id=467292 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com --- Comment #2 from Ben Daines --- This seems related to the issue I'm having where unpinned, running apps disappear and then reappear sometimes when the dock is shown after auto-hide. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 474167] [wayland] Firefox launching with incorrect DPI & GTK theming
https://bugs.kde.org/show_bug.cgi?id=474167 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 474167] New: [wayland] Firefox launching with incorrect DPI & GTK theming
https://bugs.kde.org/show_bug.cgi?id=474167 Bug ID: 474167 Summary: [wayland] Firefox launching with incorrect DPI & GTK theming Classification: Plasma Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: benjamindai...@gmail.com Target Milestone: --- SUMMARY *** If I am using Wayland and I launch Firefox from latte, Firefox ignores my GTK theme settings and fires up with the default Adwatia theme and a slightly enlarged mouse pointer. However, if I launch Firefox from the plasma menu it fires up properly with my chosen theme and a properly scaled pointer. *** STEPS TO REPRODUCE 1. Start Wayland Session 2. Launch firefox from pinned app icon in Latte (make sure an instance of firefox is not already running) OBSERVED RESULT Firefox launches with incorrect DPI settings and with default Adwadia theme, ignoring set GTK theme from system settings EXPECTED RESULT Firefox should launch with correct DPI and theme according to system settings, as it does when launched from the application menu or other Plasma launcher. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.4.12-1-MANJARO (64-bit) (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472585] New: Option to hide application icon
https://bugs.kde.org/show_bug.cgi?id=472585 Bug ID: 472585 Summary: Option to hide application icon Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Window List Assignee: plasma-b...@kde.org Reporter: benjamindai...@gmail.com CC: uhh...@gmail.com Target Milestone: 1.0 An option to hide the application icon and just display the current application name in the window list plasmoid would be very nice. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 470234] New: New UI not straightforward when set to use same capture method as previous use
https://bugs.kde.org/show_bug.cgi?id=470234 Bug ID: 470234 Summary: New UI not straightforward when set to use same capture method as previous use Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: benjamindai...@gmail.com CC: k...@david-redondo.de Target Milestone: --- With the new UI it seems that if you have "use last used capture method" selected and spectacle launches in "rectangular region" mode, there's no clear way to get to the main UI of the app in order to change the selection method. I ended up having to hit "copy" to take a screenshot and return to the main window in order to make a screen recording. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451861] New: "History" tab should start logging with app launch
https://bugs.kde.org/show_bug.cgi?id=451861 Bug ID: 451861 Summary: "History" tab should start logging with app launch Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: benjamindai...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- "History" tab should start recording data a program launch, currently it does not until the tab is clicked on. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418948] New: Easier toggle for scroll bar mini-map
https://bugs.kde.org/show_bug.cgi?id=418948 Bug ID: 418948 Summary: Easier toggle for scroll bar mini-map Product: kate Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: benjamindai...@gmail.com Target Milestone: --- Should be a check box in the top level of the view menu to toggle this feature on and off rather than needing to do it from the application settings -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 411598] New: Quietly sync existing notifications when phone connects
https://bugs.kde.org/show_bug.cgi?id=411598 Bug ID: 411598 Summary: Quietly sync existing notifications when phone connects Product: kdeconnect Version: 1.3.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: benjamindai...@gmail.com Target Milestone: --- SUMMARY currently when a phone connects with existing notifications, kdeconnect spams them all for a good few minutes if there are a good amount of notifications. This also causes a system slowdown. Kdeconnect should add all existing notifications quietly to the panel without creating a popup for each one. Only new notifications are required to pop up on the screen. STEPS TO REPRODUCE 1. Set up kdeconnect and have uncleared notifications on the phone 2. put system to sleep 3. wake up system 4. observe the horror Thanks. 3. OBSERVED RESULT EXPECTED RESULT 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.
[kdeconnect] [Bug 411598] Quietly sync existing notifications when phone connects
https://bugs.kde.org/show_bug.cgi?id=411598 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401738] Notifications do not appear after external display is disconnected.
https://bugs.kde.org/show_bug.cgi?id=401738 --- Comment #1 from Ben Daines --- Stil present in 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405016] Dock stays visible when moving mouse in and out quickly
https://bugs.kde.org/show_bug.cgi?id=405016 --- Comment #3 from Ben Daines --- I'll play around with it when I get some free time. Thanks for leaving the bug open. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405016] Dock stays visible when moving mouse in and out quickly
https://bugs.kde.org/show_bug.cgi?id=405016 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405016] Dock stays visible when moving mouse in and out quickly
https://bugs.kde.org/show_bug.cgi?id=405016 Ben Daines changed: What|Removed |Added Summary|Dock stays visible when |Dock stays visible when |moving mouse in and our |moving mouse in and out |quickly |quickly -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405016] New: Dock stays visible when moving mouse in and our quickly
https://bugs.kde.org/show_bug.cgi?id=405016 Bug ID: 405016 Summary: Dock stays visible when moving mouse in and our quickly Product: latte-dock Version: 0.8.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: benjamindai...@gmail.com Target Milestone: --- Created attachment 118495 --> https://bugs.kde.org/attachment.cgi?id=118495=edit Latte layout attached, in case that helps(?) SUMMARY I've noticed that quite frequently, but inconsistently latte will stay visible when set to auto-hide when moving the mouse in & out quickly when set to auto hide. This will also happen with the hover-to-preview window preview open. Unfortunately, as it isn't very consistent behavior, I can't give you very useful steps to reproduce. However, it happens a lot. I'm sure if you were to set your dock to auto hide the behavior would exhibit itself at least once. STEPS TO REPRODUCE 1. Have latte set to auto hide 2. Complete an action quickly (seems like you need to actually do something, ie. launch something or do something via contextual menu). 3. Be frustrated at lack of polish. OBSERVED RESULT Dock stays visible, sometimes zoomed as if the cursor was hovering over an item, or even with a window preview open. EXPECTED RESULT Dock should hide when cursor is not "in" it at all times, unless a contextual menu is open. SOFTWARE/OS VERSIONS Windows: N/A MacOS: N/A Linux/KDE Plasma: Manjaro (current stable 18.something) (available in About System) KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403788] Firefox - No option to open private window
https://bugs.kde.org/show_bug.cgi?id=403788 Ben Daines changed: What|Removed |Added Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403788] Firefox - No option to open private window
https://bugs.kde.org/show_bug.cgi?id=403788 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403788] Firefox - No option to open private window
https://bugs.kde.org/show_bug.cgi?id=403788 --- Comment #3 from Ben Daines --- Created attachment 117753 --> https://bugs.kde.org/attachment.cgi?id=117753=edit Chromium .desktop -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403788] Firefox - No option to open private window
https://bugs.kde.org/show_bug.cgi?id=403788 --- Comment #2 from Ben Daines --- Created attachment 117752 --> https://bugs.kde.org/attachment.cgi?id=117752=edit Firefox .desktop -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403788] Firefox - No option to open private window
https://bugs.kde.org/show_bug.cgi?id=403788 --- Comment #1 from Ben Daines --- Created attachment 117751 --> https://bugs.kde.org/attachment.cgi?id=117751=edit Chrome Context Menu -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403788] New: Firefox - No option to open private window
https://bugs.kde.org/show_bug.cgi?id=403788 Bug ID: 403788 Summary: Firefox - No option to open private window Product: latte-dock Version: 0.8.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: benjamindai...@gmail.com Target Milestone: --- Created attachment 117750 --> https://bugs.kde.org/attachment.cgi?id=117750=edit Firefox Context Menu SUMMARY When right clicking Firefox in the dock there is no option to open a new private window (or a new window for that matter), just the generic "start new instance" STEPS TO REPRODUCE 1. Add Firefox to the plasmoid 2. Right click 3. Observe the lack of afore mentioned option OBSERVED RESULT No option is provided to open a new private window EXPECTED RESULT The desktop actions listed in Firefox's .desktop file should be listed when right clicking the launcher in Latte. They are present when this is done with Chromium, but not for Firefox. The appropriate desktop action is in the .desktop file for Firefox, but they are not picked up by Latte. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION I'm attaching screenshots of the results I'm seeing, as well as the .desktop files for Firefox and Chromium -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 395583] Cannot login after lock screen which went to sleep
https://bugs.kde.org/show_bug.cgi?id=395583 --- Comment #9 from Ben Daines --- (In reply to cantabile from comment #8) > Hi. I have this problem too. > > I can't tell what triggers it. Sometimes the lock screen works correctly, > sometimes only the lock screen's background picture, the clock, and the > mouse cursor will appear. I hibernate often, and I'm pretty sure that the > lock screen always works correctly right after resuming from hibernation. > > Even though the password input field doesn't appear, I can type the password > to unlock the screen. I can tell it works even though the lock screen's > background picture doesn't vanish, because after I press Enter the mouse > cursor changes into I-beam if I left KWrite open, for example. > > And of course the Ctrl-Alt-F2 followed by Ctrl-Alt-F1 workaround mentioned > by the others works. Before or after I type the password. > > A detail I didn't see mentioned above: one time when the lock screen was > "malfunctioning", I left the computer alone for a few minutes, and noticed > that the time displayed on the lock screen was not updated. It was stuck at > whatever the time was when I first woke up the screen. So it's not just that > the password input field and the button below it don't appear. The program's > graphics seem to be frozen completely. > > My system is an oldish laptop with "Intel Corporation Mobile GME965/GLE960 > Integrated Graphics Controller". > > The operating system is plain Arch Linux, currently running plasma-desktop > 5.14.4-2, plasma-framework 5.53.0-1, qt5-base 5.12.0-1, xf86-video-intel > 1:2.99.917+855+g746ab3bb-1, mesa 18.3.1-1. (But I've had this problem for > months.) Just going to chime in and say this is the same behavior I am seeing too. It will go for a good long while working, and then suddenly I'll start having issues again. Ctl+Alt+F2/1 fixes it as well. I am also running intel graphics and Arch. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 402370] Multi monitor config lost while returning from standby
https://bugs.kde.org/show_bug.cgi?id=402370 --- Comment #1 from Ben Daines --- This is using X, not Wayland. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 402370] Multi monitor config lost while returning from standby
https://bugs.kde.org/show_bug.cgi?id=402370 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 402370] New: Multi monitor config lost while returning from standby
https://bugs.kde.org/show_bug.cgi?id=402370 Bug ID: 402370 Summary: Multi monitor config lost while returning from standby Product: KScreen Version: 5.14.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: benjamindai...@gmail.com Target Milestone: --- SUMMARY I'm running the latest release on Manjaro with dual screens set up. The issue I'm having is that when the displays go to standby, then wake back up, Plasma doesn't seem to remember my config. My DVI display wakes up first, Plasma detects it, snaps into single display config, then the HDMI display wakes up, Plasma detects it, and then snaps back into my configured display layout. Plasma should just remember the layout, in fact, as the computer is still running and the displays haven't actually been disconnected, there's really no need for Plasma to re-detect displays at all. STEPS TO REPRODUCE 1. run multiple displays (one waking up quicker than the other may be important, I'm not sure) 2. displays should go into standby 3. displays wake up OBSERVED RESULT Plasma re-detects attached displays twice. EXPECTED RESULT Plasma should not need to re-detect displays at all, computer should be just as I left it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 4.19.6-1-MANJARO (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION DVI screen is an aluminum Apple Cinema Display. HDMI screen is a Dell 27" Both screens are connected to the same AMD video card running amdgpu driver. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 401876] Text is way too small
https://bugs.kde.org/show_bug.cgi?id=401876 --- Comment #2 from Ben Daines --- (In reply to Laurent Montel from comment #1) > Heu... > configure->apparence -> font... Oh wow I'm an idiot. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 401876] New: Text is way too small
https://bugs.kde.org/show_bug.cgi?id=401876 Bug ID: 401876 Summary: Text is way too small Product: akregator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: benjamindai...@gmail.com Target Milestone: --- Text is way too small in the internal browser. Please provide a setting. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401780] Add option to disable emails from automatically opening URLs
https://bugs.kde.org/show_bug.cgi?id=401780 --- Comment #2 from Ben Daines --- Sure looks to be the same. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401780] Add option to disable emails from automatically opening URLs
https://bugs.kde.org/show_bug.cgi?id=401780 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401780] New: Add option to disable emails from automatically opening URLs
https://bugs.kde.org/show_bug.cgi?id=401780 Bug ID: 401780 Summary: Add option to disable emails from automatically opening URLs Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: benjamindai...@gmail.com Target Milestone: --- I've noticed that some emails will automatically open web pages upon opening the email. Unfortunately I cannot share an example email as it contains way too much personal information. This situation is not only annoying (I assure you it's extremely annoying), but is a security risk as well. An option to disable it should be added. I'm not HTML wizard, but it seems like this line in the header may be what's doing it. https://www.w3schools.com/tags/att_meta_http_equiv.asp -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 401738] New: Notifications do not appear after external display is disconnected.
https://bugs.kde.org/show_bug.cgi?id=401738 Bug ID: 401738 Summary: Notifications do not appear after external display is disconnected. Product: frameworks-knotifications Version: 5.52.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: benjamindai...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY If you use a laptop with an external display, then disconnect the external display notifications are no longer shown. STEPS TO REPRODUCE 0. Have notifications set to show in upper right corner, primary display is to the left and internal laptop display is secondary to the right. 1. Connect external display 2. remove external display OBSERVED RESULT Notifications no longer pop up when back in "laptop mode" EXPECTED RESULT Notifications should work properly SOFTWARE/OS VERSIONS KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 401738] Notifications do not appear after external display is disconnected.
https://bugs.kde.org/show_bug.cgi?id=401738 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401541] Background tasks should not block opening emails
https://bugs.kde.org/show_bug.cgi?id=401541 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401541] New: Background tasks should not block opening emails
https://bugs.kde.org/show_bug.cgi?id=401541 Bug ID: 401541 Summary: Background tasks should not block opening emails Product: kmail2 Version: 5.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: benjamindai...@gmail.com Target Milestone: --- SUMMARY When kmail is doing something in the background, such as applying filters, emails cannot be opened. This is super aggravating and should not be the case. There's times where it's faster to go get my phone and open an email rather than waiting on kmail to figure itself out. Please re-prioritize the download / opening of emails to preempt anything else kmail is doing. Version 5.9.3 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 400539] Option to disable unread count
https://bugs.kde.org/show_bug.cgi?id=400539 --- Comment #2 from Ben Daines --- (In reply to Michail Vourlakos from comment #1) > Tasks -> Show progress information for tasks Hmmm is it a plasma limitation that they're linked? Can progress indicators be separated from unread counts? -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 400539] Option to disable unread count
https://bugs.kde.org/show_bug.cgi?id=400539 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 400539] New: Option to disable unread count
https://bugs.kde.org/show_bug.cgi?id=400539 Bug ID: 400539 Summary: Option to disable unread count Product: latte-dock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: benjamindai...@gmail.com Target Milestone: --- Created attachment 116017 --> https://bugs.kde.org/attachment.cgi?id=116017=edit email unread notification Large unread counts with small icons creates an unsightly cutoff. I have a lot of unread emails, and no intentions of changing that so the unread count is pretty useless anyway. It would be nice to be able to turn it off. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399312] Panel will not auto hide when placed on the bottom of a screen with another screen below it
https://bugs.kde.org/show_bug.cgi?id=399312 Ben Daines changed: What|Removed |Added Resolution|INTENTIONAL |FIXED --- Comment #2 from Ben Daines --- Well that's unfortunate. Wouldn't it be possible to have auto hiding working if there's a gap between the two screens? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399312] New: Panel will not auto hide when placed on the bottom of a screen with another screen below it
https://bugs.kde.org/show_bug.cgi?id=399312 Bug ID: 399312 Summary: Panel will not auto hide when placed on the bottom of a screen with another screen below it Product: plasmashell Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: benjamindai...@gmail.com Target Milestone: 1.0 When a panel is placed at the bottom of the screen and set to auto hide, it will not auto hide when there is a second monitor placed below. Screenshot of my monitor layout attached below. Please note the primary display and the layout of the two monitors. Should be fairly easy to reproduce. Running the latest stable release. Thanks. https://i.imgur.com/1QVN5xx.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399312] Panel will not auto hide when placed on the bottom of a screen with another screen below it
https://bugs.kde.org/show_bug.cgi?id=399312 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398042] New: Usability issues with animations and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=398042 Bug ID: 398042 Summary: Usability issues with animations and virtual desktops Product: latte-dock Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: benjamindai...@gmail.com Target Milestone: --- The animations for adding / removing items from the plasmoid can cause usability issues and frustration when switching virtual desktops. If latte is set to display running tasks (not just launchers) and to only show tasks from the current desktop, when switching to another desktop and immediately going to launch something from latte, you catch the process of the dock shrinking / growing which moves what you're trying to click across the screen. Better way to handle this would be to remove animations when switching desktops, then it would be as if that desktop's dock had been there all along. Even with animations set to 3x, this is still an issue. I'd rather not disable animations entirely though. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397193] Latte fails to show window thumbnails with multiple application windows
https://bugs.kde.org/show_bug.cgi?id=397193 --- Comment #4 from Ben Daines --- Seems fixed to me. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397193] New: Latte fails to show window thumbnails with multiple application windows
https://bugs.kde.org/show_bug.cgi?id=397193 Bug ID: 397193 Summary: Latte fails to show window thumbnails with multiple application windows Product: latte-dock Version: 0.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: benjamindai...@gmail.com Target Milestone: --- Created attachment 114312 --> https://bugs.kde.org/attachment.cgi?id=114312=edit broken window thumbnails The one thing that's making latte less usable than a standard task switcher for me is that it is not creating window thumbnails when a running application has multiple windows open. For example, I should be able to choose which firefox window to switch to by hovering over the launcher, then choosing a thumbnail. However, as you can see, those thumbnails fail to load. Thumbnails work just fine for programs with only one window open. Currently I must either use alt-tab to find the window I want, or click the launcher icon, then move the cursor a (comparatively) great distance across the screen to pick the window. What makes this super strange is that occasionally, the thumbnails will work as expected, but if I move the cursor out of the dock, then back, the thumbnails will be gone again. Seems to be somewhat random. Not sure if it matters, but I do have the dock set to auto hide. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397193] Latte fails to show window thumbnails with multiple application windows
https://bugs.kde.org/show_bug.cgi?id=397193 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 395583] Cannot login after lock screen which went to sleep
https://bugs.kde.org/show_bug.cgi?id=395583 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com --- Comment #3 from Ben Daines --- Same issue here. Also Arch-based (Manjaro). It has nothing to do with your DVI adapter, as I'm seeing the same thing on a laptop with only an internal display. Seems to unlock properly every time when opening the lid, but if the machine goes to sleep and is woken back up with the keyboard or power button plasma will fail to unlock. If the screen is locked, but the machine has not gone to sleep, there doesn't seem to be any issues unlocking. Being that both of us are running Arch, this may be an Arch issue. However, I did not see anyone complaining about it on their forums, and there doesn't seem to be a bug report. Hopefully someone running a distro other than Arch can confirm this. Piotr, has this resolved itself with any subsequent updates? -- You are receiving this mail because: You are watching all bug changes.
