[plasmashell] [Bug 483509] system monitor widget horizontal bars fails to display more than 1 sensor when in panel
https://bugs.kde.org/show_bug.cgi?id=483509
A. R. Kristiansen changed:
What|Removed |Added
CC||k...@68degrees.no
--- Comment #2 from A. R. Kristiansen ---
Putting this as a comment here instead of making a new bug report because it
seems related to this, but if I should make a new report just let me know.
Does it still hide all the sensors for you?
In my case, I can only get two to appear after
https://bugs.kde.org/show_bug.cgi?id=481949 was fixed, any horizontal bar
beyond the third simply gets hidden, but is visible in the full view. This is
on an AMD GPU in Wayland, though I'm unsure if it's related.
In Plasma 5.2X and earlier versions, I used to have a system monitor applet in
my panel showing CPU, GPU, and RAM usage as horizontal bars. These three bars
were stacked just fine. During the transition from Qt5 to Qt6, this applet
broke (bug 481949) and was eventually fixed. However, after its fix, it only
shows two horizontal bars instead of three (or possibly more).
This happens on a fresh install of Plasma 6.0 and 6.1 Beta, with all settings
set to default (on a new installation of Arch Linux).
I spawned a nested instance of KWin Wayland using gdb, and made a new panel,
added a System Monitor to it, and added three sensors (CPU, GPU, and RAM usage
%).
This was the output:
Arrived mimeData QList() QList("text/x-plasmoidservicename") at 1151 , 20
adding "org.kde.plasma.systemmonitor"
This plugin does not support setting window opacity
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:46:
TypeError: Cannot read property 'updateRateLimit' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:45:
TypeError: Cannot read property 'totalSensors' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:41:
TypeError: Cannot read property 'highPrioritySensorIds' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:33:
TypeError: Cannot read property 'title' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:46:
TypeError: Cannot read property 'updateRateLimit' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:45:
TypeError: Cannot read property 'totalSensors' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:41:
TypeError: Cannot read property 'highPrioritySensorIds' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:33:
TypeError: Cannot read property 'title' of null
KPackageStructure of KPluginMetaData(pluginId:"org.kde.merkuro.contact",
fileName: "/usr/share/plasma/plasmoids/org.kde.merkuro.contact/metadata.json")
does not match requested format "Plasma/Applet"
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/config/ConfigAppearance.qml:18:1:
QML ConfigAppearance: Created graphical object was not placed in the graphics
scene.
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/config/ConfigAppearance.qml:
Setting initial properties failed: ConfigAppearance does not have a property
called cfg_chartFace
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/config/ConfigAppearance.qml:
Setting initial properties failed: ConfigAppearance does not have a property
called cfg_chartFaceDefault
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/config/ConfigAppearance.qml:
Setting initial properties failed: ConfigAppearance does not have a property
called cfg_sensorColors
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/config/ConfigAppearance.qml:
Setting initial properties failed: ConfigAppearance does not have a property
called cfg_sensorColorsDefault
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/config/ConfigAppearance.qml:
Setting initial properties failed: ConfigAppearance does not have a property
called cfg_sensorIds
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/config/ConfigAppearance.qml:
Setting initial properties failed: ConfigAppearance does not have a property
called cfg_sensorIdsDefault
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/config/ConfigAppearance.qml:
Setting initial properties failed: ConfigAppearance does not have a property
called cfg_textOnlySensorIds
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/config/ConfigAppearance.qml:
Setting initial properties failed: ConfigAppearance does not have a property
called cfg_textOnlySensorIdsDefault
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/config/Confi
[Merkuro] [Bug 459850] Trigger notification on login if calendar event occurred while logged out
https://bugs.kde.org/show_bug.cgi?id=459850 A. R. Kristiansen changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from A. R. Kristiansen --- I don't seem to be having this issue anymore, so I'll close it. Maybe it even was a case of PEBKAC. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451744] Implement toggle for "Sticky corners", preventing mouse cursor moving between monitors in corners
https://bugs.kde.org/show_bug.cgi?id=451744 --- Comment #8 from A. R. Kristiansen --- (In reply to fanzhuyifan from comment #7) Perfect, thank you SO very much! Can't wait to give this a try. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481949] System Monitor applet in panel breaks when trying to draw horizontal bars
https://bugs.kde.org/show_bug.cgi?id=481949 --- Comment #1 from A. R. Kristiansen --- Note, I'm setting the version to master because it works fine in 5.93.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481949] New: System Monitor applet in panel breaks when trying to draw horizontal bars
https://bugs.kde.org/show_bug.cgi?id=481949 Bug ID: 481949 Summary: System Monitor applet in panel breaks when trying to draw horizontal bars Classification: Plasma Product: plasmashell Version: master Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: k...@68degrees.no CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 166168 --> https://bugs.kde.org/attachment.cgi?id=166168=edit Video of different erroneous behaviours with the System Monitor Sensor applet in a panel SUMMARY When the System Monitor Sensors applet is placed in a panel, it is completely unable to draw horizontal bars correctly. More than one bar disappears after briefly being displayed in a broken manner, a single bar is displayed but in all black. I've attached a video that showcases the behaviour. STEPS TO REPRODUCE 1. Add a System Monitor Sensor applet to a panel. 2. Configure it to show one or more horizontal bars. OBSERVED RESULT A single bar is nonfunctional, 2+ bars simply disappear. EXPECTED RESULT Horizontal bars representing the configured sensors with their chosen colours. SOFTWARE/OS VERSIONS Linux: 6.7.6 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I would like to be more helpful, but my attempts at generating actually useful information for this bug with GDB have been unsuccessful. Assistance would be appreciated. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480963] Kwin spams QObject::startTimer related warning in systemd journal during user input
https://bugs.kde.org/show_bug.cgi?id=480963 --- Comment #6 from A. R. Kristiansen --- Hi thecookie, thanks for confirming it's not just me. I'll happily try to help and do what you requested David, but I'm not a developer, just a user, so it might take a bit of time to get that figured out I'll be looking up info on how to use breakpoints later, I also asked for help with it in the KDE Bugs Matrix room. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480963] Kwin spams QObject::startTimer related warning in systemd journal during user input
https://bugs.kde.org/show_bug.cgi?id=480963 --- Comment #3 from A. R. Kristiansen --- Yes, it seems tricky to reproduce, I'm keeping journalctl -f open while I use my computer to see if I can catch it. If it doesn't happen again for a while I'll just close this as a fluke, if that's preferable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480963] Kwin spams QObject::startTimer related warning in systemd journal during user input
https://bugs.kde.org/show_bug.cgi?id=480963 --- Comment #1 from A. R. Kristiansen --- I also can't reproduce this on a clean boot, but I have seen it a few times before the past week or so. Just can't figure out what triggers it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480963] New: Kwin spams QObject::startTimer related warning in systemd journal during user input
https://bugs.kde.org/show_bug.cgi?id=480963 Bug ID: 480963 Summary: Kwin spams QObject::startTimer related warning in systemd journal during user input Classification: Plasma Product: kwin Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@68degrees.no Target Milestone: --- Created attachment 165621 --> https://bugs.kde.org/attachment.cgi?id=165621=edit My kwinrc SUMMARY In Plasma 6 RC2, once I start typing or moving my cursor, kwin spams "QObject::startTimer: Timers cannot have negative intervals" in the systemd journal. Several of these pop up every second. If I don't move my mouse or use the keyboard, it stops. STEPS TO REPRODUCE 1. On a systemd based computer, sign in to a Plasma 6 RC2 session 2. Execute journalctl -f in a terminal 3. Move the mouse or type anywhere while observing the journal OBSERVED RESULT Almost hundreds of QObject::startTimer related warnings can pop up each second. EXPECTED RESULT Nothing special should be logged during input. SOFTWARE/OS VERSIONS Linux kernel: 6.7.4 KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Beta 2 ADDITIONAL INFORMATION Tried two different mice just in case. This does NOT happen on my Lenovo IdeaPad 5 Pro 16ACH6, which is also using Arch Linux with the same software versions mentioned above. I have not had time to test in a Neon Unstable environment yet. I will do so later today. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478881] Konsole does not respect the rows of "initial terminal size"
https://bugs.kde.org/show_bug.cgi?id=478881 A. R. Kristiansen changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from A. R. Kristiansen --- Closing because I just figured out this is a side effect of https://bugs.kde.org/show_bug.cgi?id=478804 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 478967] Wrong contrast on screenshots in the Wayland session
https://bugs.kde.org/show_bug.cgi?id=478967 A. R. Kristiansen changed: What|Removed |Added Platform|Other |Arch Linux Keywords||wayland OS|Other |Linux -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 478967] Wrong contrast on screenshots in the Wayland session
https://bugs.kde.org/show_bug.cgi?id=478967 --- Comment #2 from A. R. Kristiansen --- Sorry for the excessive e-mails, but I wanted to add I can reproduce this on Neon Unstable, downloaded 23rd of December 2023. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 478967] Wrong contrast on screenshots in the Wayland session
https://bugs.kde.org/show_bug.cgi?id=478967 --- Comment #1 from A. R. Kristiansen --- Created attachment 164425 --> https://bugs.kde.org/attachment.cgi?id=164425=edit Final Fantasy 14 screenshot taken with Spectacle which is darker Forgot to add to the main post, I'm using a Radeon RX 6700 XT, Mesa 23.3. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 478967] New: Wrong contrast on screenshots in the Wayland session
https://bugs.kde.org/show_bug.cgi?id=478967 Bug ID: 478967 Summary: Wrong contrast on screenshots in the Wayland session Classification: Applications Product: Spectacle Version: 24.01.85 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: k...@68degrees.no CC: k...@david-redondo.de Target Milestone: --- Created attachment 164424 --> https://bugs.kde.org/attachment.cgi?id=164424=edit Final Fantasy 14 screenshot taken with the in-game screenshot tool SUMMARY In the Wayland session, screenshots taken with Spectacle increases the contrast of what is actually displayed on screen, making the resulting screenshot darker than what it's supposed to be. It's not just in the screenshot itself; activating rectangle select mode slightly increases the contrast on all screens, until a screenshot is taken and the Spectacle process has terminated. To demonstrate, I'm going to add two images taken in Final Fantasy 14. The first one is taken using the in-game screenshot tool, the second is with Spectacle (capture single monitor mode), notice how the screenshot taken with Spectacle is noticeably darker in some areas, especially the darker areas. It's most noticeable in the shadows, and in darker scenes this is especially problematic. STEPS TO REPRODUCE 1. Begin a Plasma Wayland session. 2. Take a screenshot with Spectacle. 3. Compare the result with what you captured. OBSERVED RESULT The contrast is wrong, and the resulting screenshot is darker than it should be. EXPECTED RESULT A lossless PNG without any modifications or defects. SOFTWARE/OS VERSIONS Linux: 6.6.8 KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7 Beta 1 ADDITIONAL INFORMATION Also happens on Qt 6.6, does not happen in the X11 session. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #57 from A. R. Kristiansen --- Ok, will do. Thank you for the advice =) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #55 from A. R. Kristiansen --- Just tried in the X11 session, and I can't reproduce there. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #54 from A. R. Kristiansen --- Just reproduced this on Neon unstable. I'm on an AMD Radeon RX 6700 XT, Wayland session. The issue persists with QT_QUICK_BACKEND=software, for what it's worth. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #53 from A. R. Kristiansen --- Created attachment 164414 --> https://bugs.kde.org/attachment.cgi?id=164414=edit Final Fantasy 14 screenshot taken with Spectacle which is darker -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #52 from A. R. Kristiansen --- Created attachment 164413 --> https://bugs.kde.org/attachment.cgi?id=164413=edit Final Fantasy 14 screenshot taken with the in-game screenshot tool -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 A. R. Kristiansen changed: What|Removed |Added CC||k...@68degrees.no --- Comment #51 from A. R. Kristiansen --- I'm actually having a somewhat opposite issue with Spectacle, but I'm wondering if it's somehow related to this, so I'm commenting here instead of creating a new ticket. In my perception, screenshots taken with Spectacle increases the contrast of what is actually displayed on screen. It's not just in the screenshot itself, activating rectangle select mode slightly lowers the contrast ratio on all screens, until a screenshot is taken and the Spectacle process has terminated. To demonstrate, I'm going to add two images taken in Final Fantasy 14. The first one is taken using the in-game screenshot tool, the second is with Spectacle (capture single monitor mode), notice how the screenshot taken with Spectacle is noticeably darker in some areas, especially the darker areas. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460714] Global Edit Mode toolbar is hidden behind Panel Edit Mode toolbar when Panel is on top screen edge
https://bugs.kde.org/show_bug.cgi?id=460714 A. R. Kristiansen changed: What|Removed |Added CC||k...@68degrees.no --- Comment #6 from A. R. Kristiansen --- In Plasma 5.91.0, setting the top panel to "Auto hide" completely hides the edit mode toolbar under the panel as well. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478804] Plugins are always shown on start and unable to keep them disabled/hidden
https://bugs.kde.org/show_bug.cgi?id=478804 --- Comment #12 from A. R. Kristiansen --- Can probably close this and https://bugs.kde.org/show_bug.cgi?id=478866 as "resolved, upstream"? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478804] Plugins are always shown on start and unable to keep them disabled/hidden
https://bugs.kde.org/show_bug.cgi?id=478804 --- Comment #10 from A. R. Kristiansen --- (In reply to duha.bugs from comment #9) > Sorry I should have clarified: I use stable Arch Linux and compile KDE from > source. Ok, that makes a lot more sense. No worries =) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478804] Plugins are always shown on start and unable to keep them disabled/hidden
https://bugs.kde.org/show_bug.cgi?id=478804 --- Comment #8 from A. R. Kristiansen --- (In reply to duha.bugs from comment #7) > I cannot reproduce with my system: > Operating System: Arch Linux > KDE Plasma Version: 5.91.90 > KDE Frameworks Version: 5.248.0 > Qt Version: 6.6.1 > Kernel Version: 6.6.7-arch1-1 (64-bit) Really? I'm on Arch too, but the Plasma Beta 2 packages in the repos require Qt 6.7. Without it I can't even log in. (Also I assume you meant Plasma 5.91.0 and Frameworks 5.247.0) As a side note, this is also being discussed on the forums. It seems like it would probably have been better if the packages were built for Qt 6.6 instead of jumping right onto 6.7 Beta. https://bbs.archlinux.org/viewtopic.php?pid=2138565#p2138565 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478881] Konsole does not respect the rows of "initial terminal size"
https://bugs.kde.org/show_bug.cgi?id=478881 A. R. Kristiansen changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478881] New: Konsole does not respect the rows of "initial terminal size"
https://bugs.kde.org/show_bug.cgi?id=478881 Bug ID: 478881 Summary: Konsole does not respect the rows of "initial terminal size" Classification: Applications Product: konsole Version: 24.01.85 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: td21rz...@mozmail.com Target Milestone: --- SUMMARY When opening Konsole, it ignores the rows defined in a profile's initial terminal size. For example, my profile is set to spawn with 80 colums and 25 rows. When opening a new Konsole window, it spawns with a size of 80x64. This is on a 1920x1080 monitor, lower resolutions will make it adapt the rows. (1600x900 = 56 rows) STEPS TO REPRODUCE 1. Disable "Remember window size" in Konsole settings. 2. Create a Konsole profile and define an "initial terminal size". 3. Close and re-open Konsole. OBSERVED RESULT Konsole opens with the correct columns, but not rows. EXPECTED RESULT Both columns and rows should be respected when Konsole spawns. SOFTWARE/OS VERSIONS Linux: 6.6.8 KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0 Beta 1 ADDITIONAL INFORMATION "Remember window size" is disabled. I have three 1080p monitors, the issue persists when Konsole is spawned on all three. Regenerating konsolerc does not fix the issue. Possibly related: https://bugs.kde.org/show_bug.cgi?id=478804 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478804] Plugins are always shown on start and unable to keep them disabled/hidden
https://bugs.kde.org/show_bug.cgi?id=478804 A. R. Kristiansen changed: What|Removed |Added CC||td21rz...@mozmail.com --- Comment #6 from A. R. Kristiansen --- Regenerating konsolerc didn't work for this one. And yes agree, not good to show these by default, but something tells me they didn't / don't intend for these plugins to be opened by default =) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478866] Every panel is enabled in every new window in Beta 2 - Places, Information, Folders, and Terminal
https://bugs.kde.org/show_bug.cgi?id=478866 A. R. Kristiansen changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from A. R. Kristiansen --- I found the culprit. In dolphinrc, the [General] section has a setting called "RememberOpenedTabs" If set to false, Dolphin opens every panel on every new window opened, and does not remember which ones you close. If set to true, or if the string does not exist, panels act like you would expect them to. In "Configure Dolphin" (CTRL+SHIFT+,) this setting is in "Interface" -> "Folders & Tabs" -> "Show on startup:" If that setting is set to a specific folder, any folder, the panel behaviour breaks. I have no idea why setting this to false interferes with the panels! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478866] Every panel is enabled in every new window in Beta 2 - Places, Information, Folders, and Terminal
https://bugs.kde.org/show_bug.cgi?id=478866 --- Comment #4 from A. R. Kristiansen --- (In reply to Yao Mitachi from comment #3) > How odd, deleting that file does allow Dolphin to remember what panels I > last had open... even though I didn't see anything relevant to which panels > were open. Yeah, same here, not at first glance anyway. That's what I do when I have any kind of issue in KDE apps, just regenerate their config files. Then, if that fixes it, I try to remove config entries from the original file one by one until I find the culprit. Will give that a shot later today if nobody beats me to it. > And now, my I wonder if regenerating that file makes Dolphin > reset some values that are stored elsewhere? Does the issue remain if you put the original config file back in place? (If you kept it.) BTW, thank you for the link to the Konsole issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478866] Every panel is enabled in every new window in Beta 2 - Places, Information, Folders, and Terminal
https://bugs.kde.org/show_bug.cgi?id=478866 A. R. Kristiansen changed: What|Removed |Added CC||td21rz...@mozmail.com --- Comment #2 from A. R. Kristiansen --- Also applies to other apps with panels, such as Konsole. Every time I open Konsole, both the "SSH Manager" and "Quick Commands" plugins are enabled. Konsole also does not respect its default size as set in the profile. (80x25, instead defaults to 80x64) Regenerating "/home/(user)/.config/dolphinrc" fixes the issue. Haven't figured out which setting is the culprit yet, or if regenerating "konsolerc" fixes the Konsole issue. Pressed for time atm =) Arch Linux Kernel: 6.6.8 KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0beta2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470975] Floating panel does not defloat when maximizing window
https://bugs.kde.org/show_bug.cgi?id=470975 --- Comment #2 from A. R. Kristiansen --- Created attachment 163942 --> https://bugs.kde.org/attachment.cgi?id=163942=edit The effect on floating panel after changing monitor configurations -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470975] Floating panel does not defloat when maximizing window
https://bugs.kde.org/show_bug.cgi?id=470975 A. R. Kristiansen changed: What|Removed |Added Ever confirmed|0 |1 CC||td21rz...@mozmail.com Status|REPORTED|CONFIRMED --- Comment #1 from A. R. Kristiansen --- Can confirm, if the number of available monitors change, a floating panel will no longer de-float when touched by a window. As a result, it partially obscures maximised windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477880] System Monitor applet popup is tremendously enormous and non-resizeable
https://bugs.kde.org/show_bug.cgi?id=477880 --- Comment #1 from A. R. Kristiansen --- Another thing I tried was to delete plasma-org.kde.plasma.desktop-appletsrc, restart Plasma, and make a new applet, but the problem persisted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477882] System Monitor applet in a panel crashes plasmashell if it displays a table
https://bugs.kde.org/show_bug.cgi?id=477882 --- Comment #1 from A. R. Kristiansen --- Created attachment 163735 --> https://bugs.kde.org/attachment.cgi?id=163735=edit Backtrace generated with GDB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477882] System Monitor applet in a panel crashes plasmashell if it displays a table
https://bugs.kde.org/show_bug.cgi?id=477882 A. R. Kristiansen changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477882] New: System Monitor applet in a panel crashes plasmashell if it displays a table
https://bugs.kde.org/show_bug.cgi?id=477882
Bug ID: 477882
Summary: System Monitor applet in a panel crashes plasmashell
if it displays a table
Classification: Plasma
Product: plasmashell
Version: 5.90.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: System Monitor
Assignee: plasma-b...@kde.org
Reporter: td21rz...@mozmail.com
CC: ahiems...@heimr.nl, notm...@gmail.com
Target Milestone: 1.0
SUMMARY
When using the System Monitor applet docked on a panel, plasmashell crashes if
it tries to display either of the two process table views.
If this setting is successfully saved, Plasmashell will crash on a loop until
the offending setting is removed from:
~/.config/plasma-org.kde.plasma.desktop-appletsrc
("Applications Table" or "Process Table")
STEPS TO REPRODUCE
1. Make a System Monitor applet on a panel
2. Configure it to display a table
OBSERVED RESULT
Plasmashell crashes, and on a loop if that setting is saved.
EXPECTED RESULT
Ideally this applet shouldn't even try to display a table in a space as small
as a panel, it should display them in the popup window if anything.
SOFTWARE/OS VERSIONS
Linux: 6.6.3
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 477880] New: System Monitor applet popup is tremendously enormous and non-resizeable
https://bugs.kde.org/show_bug.cgi?id=477880 Bug ID: 477880 Summary: System Monitor applet popup is tremendously enormous and non-resizeable Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: td21rz...@mozmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 163733 --> https://bugs.kde.org/attachment.cgi?id=163733=edit Comparison between 5.90 and 5.27 SUMMARY The System Monitor Sensor popup when docked on a panel is huge, and cannot be resized. It uses way too much space for the information it needs to display. Doesn't matter which Display Style it uses. STEPS TO REPRODUCE 1. Setup System Monitor Sensor to show some exciting information. 2. Dock it to a panel. 3. Click on it. OBSERVED RESULT Gargantuan popup! And no way to make it smaller. EXPECTED RESULT A small, sweet, perhaps even cute, but resizeable popup. SOFTWARE/OS VERSIONS Linux: 6.6.3 KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION A comparison between Beta 1 and 5.27.9 is attached. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477727] Can't use mouse input while pen is detected by tablet
https://bugs.kde.org/show_bug.cgi?id=477727 A. R. Kristiansen changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from A. R. Kristiansen --- Unfortunately she couldn't get colour picking and mouse usage in Krita to work the way she wanted to and uninstalled it, so I'll close the ticket. I'm very sorry for the inconvenience. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477727] Can't use mouse input while pen is detected by tablet
https://bugs.kde.org/show_bug.cgi?id=477727 --- Comment #2 from A. R. Kristiansen --- Hi wolthera, yes. This is when the pen is just hovering. Thank you, that was a really quick response! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477727] New: Can't use mouse input while pen is detected by tablet
https://bugs.kde.org/show_bug.cgi?id=477727 Bug ID: 477727 Summary: Can't use mouse input while pen is detected by tablet Classification: Applications Product: krita Version: 5.2.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: td21rz...@mozmail.com Target Milestone: --- SUMMARY With a Wacom Intuos Pro, Krita does not accept any mouse inputs as long as the tablet detects the pen tip or "eraser". To use the mouse, the pen must be removed from the tablet, which slows down the workflow significantly. STEPS TO REPRODUCE 1. Hover a pen over a drawing tablet 2. Try to use a mouse input, such as this custom keybind: "right click to sample foreground colour from merged image" OBSERVED RESULT Mouse inputs are discarded. EXPECTED RESULT Mouse to function normally even if the pen is near the tablet. SOFTWARE/OS VERSIONS Krita 5.2.1 (Windows Installer from Krita.org) Windows 10 Enterprise LTSC, 21H2, 19044.3208 ADDITIONAL INFORMATION Bug filed on behalf of a friend using Krita on Windows. She is left handed, and uses a mouse with her right hand. Being able to use a tablet and mouse simultaneously is a critical part of her workflow. -- You are receiving this mail because: You are watching all bug changes.
