[kwin] [Bug 484037] Primary display loses its resolution configuration when resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=484037 --- Comment #20 from Kalzi --- I still get this issue. I did report it, too, and my report was marked as duplicate of this one. One thing that gets me out of it is the command that was provided by Zamunda kscreen-doctor output.1.mode.0 This issue only happens on the display that is connected with DP -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #19 from Kalzi --- (In reply to Zamundaaa from comment #16) > You can set a mode with kscreen-doctor with > > kscreen-doctor output.1.mode.0 > (0 is the number of the mode in the list you want) or > > kscreen-doctor output.1.mode.3840x2160@60 I can try for sure, but the screen is so zoomed in I can't barely see or control anything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 Kalzi changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #14 from Kalzi --- (In reply to Zamundaaa from comment #13) > hmm, those outputs looks all correct - kscreen-doctor knows it's in the > small mode, and it's sent to other wayland clients correctly as well. If you > set the correct mode with kscreen-doctor, does that work at least? If not, > can you set a different resolution first and then the correct one? I'm not sure I know how to set it with screen-doctor. Also, this issue only happens on the monitor that is connected via display port, if that helps at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #12 from Kalzi --- (In reply to Zamundaaa from comment #9) > (In reply to Michael Butash from comment #4) > > Is it DP output to DP input, or some mode conversion to HDMI? > > > > I have this happen almost clockwork after a suspend awaken, reboot, even > > just a glitch of the power to the dock or something, and seems to come > > largely from having to use DP on dock to HDMI on TV conversion. Often I'll > > see the display after reset come up instead of my Samsung TV's I use to > > display as generic "NVidia 640x480", and is usually all xrandr sees as well, > > indicating like the conversion chip in the cable/adapter glitches and EDID > > data doesn't resolve correctly on the host. I often have to end up > > unplugging physically and resetting the DP end of the cable/adapter to fix > > it. > That's a NVidia driver bug, the proprietary driver has some issues with > reading the EDID sometimes. You can report it at > https://forums.developer.nvidia.com/c/gpu-graphics/linux/148 > > > (In reply to Kalzi from comment #8) > > I have attached three txt files that have the output of drm_info for before, > > during and after > > Okay, so the driver reports the correct mode list, and KWin has actually set > the 640x480 mode. Can you also attach the output of > > kscreen-doctor -o > and > > wayland-info > while the output is wrongly in that 640x480 mode? > > What I suspect is happening is that the driver temporarily reports 640x480 > as the only supported mode at some point after the display goes to standby, > and KWin doesn't automatically switch back to the correct mode (which > shouldn't be very complicated to fix). If the display settings doesn't let > you set the right mode though, there might be more going on attached both. Hope it helps. I still can't change the resolution on the blown out screen, I'd have to find a way to be able to get to the normal screen to change the correct resolution from there -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #11 from Kalzi --- Created attachment 169253 --> https://bugs.kde.org/attachment.cgi?id=169253=edit waylandinfo -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #10 from Kalzi --- Created attachment 169252 --> https://bugs.kde.org/attachment.cgi?id=169252=edit kscreen-doctor-while -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #8 from Kalzi --- (In reply to Zamundaaa from comment #3) > Please attach the output of drm_info before, and after triggering the issue I have attached three txt files that have the output of drm_info for before, during and after -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #7 from Kalzi --- Created attachment 169251 --> https://bugs.kde.org/attachment.cgi?id=169251=edit drm_info_after -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #6 from Kalzi --- Created attachment 169250 --> https://bugs.kde.org/attachment.cgi?id=169250=edit drm_info_during -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #5 from Kalzi --- Created attachment 169249 --> https://bugs.kde.org/attachment.cgi?id=169249=edit drm_info_before -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 486504] Primary display changes to a very low resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #2 from Kalzi --- Created attachment 169135 --> https://bugs.kde.org/attachment.cgi?id=169135=edit another screenshot -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 486504] Primary display changes to a very low resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #1 from Kalzi --- Created attachment 169134 --> https://bugs.kde.org/attachment.cgi?id=169134=edit another screenshot -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 486504] New: Primary display changes to a very low resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 Bug ID: 486504 Summary: Primary display changes to a very low resolution after suspend (wayland only) Classification: Plasma Product: xdg-desktop-portal-kde Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kalzwa...@yahoo.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- Created attachment 169133 --> https://bugs.kde.org/attachment.cgi?id=169133=edit screenshot to explain the issue *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I have two 27" 4k monitors. The primary monitor switches to a very low resolution after I wake it up from suspend (640x480). This happens every single time. Things will show so massive that I can't really do much on the display. The cursor is also stuck on that same monitor. I then scramble around to find the panel and get to the display configurations and switch the monitors around so I can get my cursor to the other screen where I can get there and change the resolution to the correct one. Also, changing the resolution on the affected monitor doesn't do anything. The "apply" button stays grayed out. The primary monitor is a Dell and is connected to my RX580 GPU through DP STEPS TO REPRODUCE 1. Run wayland and have 2 4k monitors 2. suspend the machine and let it sit for a while 3. wake it up OBSERVED RESULT Resolution switches to very low res EXPECTED RESULT Normal res SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: A520I AC System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 483841] Monitors inappropriately become mirrored after wake from suspend
https://bugs.kde.org/show_bug.cgi?id=483841 --- Comment #9 from Kalzi --- (In reply to Nate Graham from comment #1) > After you move the screens so they're not overlapping anymore, does it > thereafter continue to work? Or do they somehow get overlapped/mirrored > again in the future? I just go an email that states that I needed to provide more info on this bug, or it will be deleted. Could you please advise on what else I'd need to provide? Thanks -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 483841] Monitors inappropriately become mirrored after wake from suspend
https://bugs.kde.org/show_bug.cgi?id=483841 --- Comment #7 from Kalzi --- (In reply to Nate Graham from comment #6) > Oh, sorry for missing that. > > Can you comment on the hardware setup? desktop vs laptop, how are the > monitors connected, what are their makes, models, resolutions, etc. I have a desktop PC (info below). Two 27" 4k monitors, a Dell and a Sceptre. Dell is connecting via a DP and the other one HDMI. >From var/log/Xorg.0.log: Monitor name: DELL P2715Q Sceptre is not being fully detected, but the model is there and it is u27 There are a ton of other info. Please let me know what you are looking for in particular and I will get it for you. Here is the system info Operating System: EndeavourOS KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.8.4-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: A520I AC -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 483841] Monitors inappropriately become mirrored after wake from suspend
https://bugs.kde.org/show_bug.cgi?id=483841 --- Comment #5 from Kalzi --- (In reply to Kalzi from comment #4) > (In reply to Nate Graham from comment #3) > > Thanks. > > > > Does this happen on Wayland too, or only X11? > > Apologies for the late reply, I didn't see the email, but yes, it happens on > Wayland, too. I have mentioned that in the body of my bug request :) bug report* -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 483841] Monitors inappropriately become mirrored after wake from suspend
https://bugs.kde.org/show_bug.cgi?id=483841 --- Comment #4 from Kalzi --- (In reply to Nate Graham from comment #3) > Thanks. > > Does this happen on Wayland too, or only X11? Apologies for the late reply, I didn't see the email, but yes, it happens on Wayland, too. I have mentioned that in the body of my bug request :) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 483841] Monitors overlap in settings and become mirrored after wake from suspend
https://bugs.kde.org/show_bug.cgi?id=483841 --- Comment #2 from Kalzi --- (In reply to Nate Graham from comment #1) > After you move the screens so they're not overlapping anymore, does it > thereafter continue to work? Or do they somehow get overlapped/mirrored > again in the future? They continue to work normal until the PC suspends then I wake it up. Then they're mirrored. It doesn't happen every single time lately, probably every 3rd or 4th time, and it's a simple fix, as I just need to get into the settings and move the monitors next to each other and apply and keep changes -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483841] New: Monitors overlap in settings and become mirrored after wake from suspend
https://bugs.kde.org/show_bug.cgi?id=483841 Bug ID: 483841 Summary: Monitors overlap in settings and become mirrored after wake from suspend Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: kalzwa...@yahoo.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Not sure how to explain this accurately, but here goes: Often times when I wake my system from suspend, my monitors mirror each other instead of extending. Nothing fix them at all, no rebooting or anything else does, until I discovered(by accident/luck) that they sit on top of each other in the display & monitor settings. I tried dragging the monitor in the settings and there it is, the other monitor sitting underneath it. Then just put them next to each other like they are in the real world and then hit "Apply" and it worked. This happens on both wayland and X11. STEPS TO REPRODUCE 1. Have more than one monitor 2. suspend and wake up the machine OBSERVED RESULT Monitors in Display & monitors setting sit on top of each other causing the monitors to mirror each other instead of extending EXPECTED RESULT Monitors should not mirror on their own by sitting on top of each other in the settings SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: EndeavourOS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: A520I AC System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483654] New: Primary monitor switches to 480 resolution after suspend
https://bugs.kde.org/show_bug.cgi?id=483654 Bug ID: 483654 Summary: Primary monitor switches to 480 resolution after suspend Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: kalzwa...@yahoo.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** This happens on wayland only. I have two 27" 4k monitors. The primary one switches to 480p after every suspend and things become massive that I can barely do anything. Rebooting doesn't fix it. Sometimes, I do manage to get to the display settings, but changing the res back to 2160 doesn't bring the "apply" button back, it stays greyed out. My only solution is to switch to x11 then back to wayland. Even then that may work or may not. I have both monitors at 127% scaling, btw. STEPS TO REPRODUCE 1. 4k monitor and switch to wayland 2. suspend and wake the machine OBSERVED RESULT Resolution sets to 480p and can't be reverted back to the screen's native res EXPECTED RESULT Resolution to stay set at the monitor's native resolution and not switch to 480p where things become massive SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: EndeavourOS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: A520I AC System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482879] List of available downloads is not visible in the menu when downloading plasmoids from the store
https://bugs.kde.org/show_bug.cgi?id=482879 --- Comment #1 from Kalzi --- The product is not the settings, btw. That's just the easiest for me to file a bug -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482879] New: List of available downloads is not visible in the menu when downloading plasmoids from the store
https://bugs.kde.org/show_bug.cgi?id=482879 Bug ID: 482879 Summary: List of available downloads is not visible in the menu when downloading plasmoids from the store Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwincompositing Assignee: kwin-bugs-n...@kde.org Reporter: kalzwa...@yahoo.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 166717 --> https://bugs.kde.org/attachment.cgi?id=166717=edit screenshot to explain the issue SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I was trying to install "open as root" for dolphin through the store and the menu that shows the choices where I can click install is cut off from the bottom and is rendering the whole store essentially useless since I can't install anything now. The screenshot will hopefully explain it better. Please comment if you would like me to explain it more. Bottom line is, I can't download anything from the kde store for dolphin context menu STEPS TO REPRODUCE 1. configure dolphin in settings 2. click on "download new service" 3. search for anything and try to install it OBSERVED RESULT menu is cut off where all the available options to install are not visible EXPECTED RESULT Being able to install services for dolphin SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: EndeavourOS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: A520I AC System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482604] "Get new widget">"Download New Plasma widgets" window opens too small every time
https://bugs.kde.org/show_bug.cgi?id=482604 --- Comment #1 from Kalzi --- This happens on both wayland and x11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482604] New: "Get new widget">"Download New Plasma widgets" window opens too small every time
https://bugs.kde.org/show_bug.cgi?id=482604 Bug ID: 482604 Summary: "Get new widget">"Download New Plasma widgets" window opens too small every time Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwincompositing Assignee: kwin-bugs-n...@kde.org Reporter: kalzwa...@yahoo.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 166519 --> https://bugs.kde.org/attachment.cgi?id=166519=edit small window SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Whenever I right click on the panel and try to add a widget by downloading a new one from the KDE store, the store window opens too small where the search button shows in another bar under it to search. I have to tab twice to just search, once in the magnifying glass then in the search bar that shows up. If enlarge the window, that doesn't happen because the search bar shows up at a certain window size. STEPS TO REPRODUCE 1. Right click on the panel and choose "add widgets" 2. Click on "get new widgets 3. Click on "Download plasma widgets" OBSERVED RESULT KDE widgets store window is too small EXPECTED RESULT KDE store widget window should open in a size that makes the search bar to show as a complete box, not only the magnifying glass icon SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: EndeavourOS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: A520I AC System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482560] New: Screen brightness widget treat both of my monitors (that are two different brands) as one
https://bugs.kde.org/show_bug.cgi?id=482560 Bug ID: 482560 Summary: Screen brightness widget treat both of my monitors (that are two different brands) as one Classification: Plasma Product: Powerdevil Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kalzwa...@yahoo.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I have a dell and sceptre monitors. Both are 27". I used to have a widget called ddcci-plasmoid that helped me change the brightness on the monitors individually. It does not work with plasma 6 for now, so I am now resorting to the built in plasma widget "display brightness" and it treats both monitors as one and the brightness increases on both monitors at the same time when I adjust the slider. Is there a way to make it display two different sliders for each monitor? STEPS TO REPRODUCE 1. have two different brand monitors 2. adjust the brightness from the display brightness widget 3. observe the outcome. OBSERVED RESULT both screens change brightness EXPECTED RESULT each screen should change brightness individually SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: EndeavourOS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: A520I AC System Version: -CF KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 474203] New: Wayland session does not save scaling or the monitors' order
https://bugs.kde.org/show_bug.cgi?id=474203 Bug ID: 474203 Summary: Wayland session does not save scaling or the monitors' order Classification: Plasma Product: KScreen Version: 5.27.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: OSD and Plasma applet Assignee: kscreen-bugs-n...@kde.org Reporter: kalzwa...@yahoo.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Have two 4k monitors 2. Log into wayland 3. Change the scaling to 175% or 200% or whatever works for you. 4. Log out and log back in OBSERVED RESULT Scaling goes back to 100% after logging out then logging back in and the monitors' order resets and the mouse does not move across the screens as it should EXPECTED RESULT Scaling saves to whatever I set it to, even after a log out/log in or a reboot SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I have two 27" 4k monitors. A dell to my right and a sceptre to my left. I set the scaling to 175% on both. also I have the Dell as my primary that is sitting to my right and also I have it to the right in the settings, too. Eevery time I log out or reboot, that order resets. The dell moves to the left in the settings and the other monitor goes to the right. Scaling goes back to 100%. Also, the Sceptre becomes the primary. And this happens every signle time. I have even reinsalled the whole system thinking it would fix it, it didn't. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 462179] New: Creating a task/event does not sent a desktop notification
https://bugs.kde.org/show_bug.cgi?id=462179 Bug ID: 462179 Summary: Creating a task/event does not sent a desktop notification Classification: Applications Product: kalendar Version: 22.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: kalzwa...@yahoo.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 153978 --> https://bugs.kde.org/attachment.cgi?id=153978=edit Kalendar log SUMMARY When I create a task or an event and set it to remind me at a certain time, I get nothing even though I set a time and priority STEPS TO REPRODUCE 1. Create a task or an event 2. Set its priority 3. Set a reminder for that task/event OBSERVED RESULT No desktop notification EXPECTED RESULT Creating a task/event and setting a reminder for it, should send a notification to the desktop with sound Operating System: EndeavourOS KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 5.15.79-1-lts (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Inspiron 7573 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 462042] New: Add Yahoo as an authentication method so yahoo accounts can be added to kmail
https://bugs.kde.org/show_bug.cgi?id=462042 Bug ID: 462042 Summary: Add Yahoo as an authentication method so yahoo accounts can be added to kmail Classification: Applications Product: kmail2 Version: 5.21.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kalzwa...@yahoo.com Target Milestone: --- SUMMARY *** Adding yahoo emails to kmail is impossible, as the app opens up a Google login webpage Trying to change the authentication method to others like "Plain", "login" etc. doesn't do anything. I have even disabled my 2FA on my yahoo account, it is still not working. It shows the account as "ready" in the settings with a green check, but there is nothing coming through. *** STEPS TO REPRODUCE 1. Add a yahoo account to kmail is the only step you need to reproduce this issue OBSERVED RESULT Authentication opens a Google sign in web page even though Yahoo is the account being added to kmail EXPECTED RESULT To be able to add yahoo accounts to kmail - To open an actual yahoo authentication window to sing in and add the yahoo account SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Inspiron 7573 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #26 from Kalzi --- That bug* -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #25 from Kalzi --- (In reply to Nate Graham from comment #24) > > *** This bug has been marked as a duplicate of bug 457284 *** Not sure if this could be considered a duplicate of that big. That one is about the wallpaper being black. This one, the laptop is almost dead, nothing on the screen and nothing is active. Not even a cursor. Ttys don't work at all. Only fix is to hard power it off. I see that crossed the other bug. So not sure if it is still considered a duplicate or not. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #23 from Kalzi --- (In reply to Zamundaaa from comment #22) > Yes, these PCIe errors definitely seem suspicious. They seem to happen other > stuff with NVidia as well: > https://forums.developer.nvidia.com/t/pcie-bus-error-severity-corrected-on- > jetson-nano/155780 Yeah, I've found this page before. I thought I had nvidia disabled with optimus manager. I'm not sure then. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #21 from Kalzi --- Created attachment 151113 --> https://bugs.kde.org/attachment.cgi?id=151113=edit dmesg.log from wayland This is driving me crazy. Now it stopped happening on wayland and started on xorg. Here is the log. It didn't happen, but it shows some errors from PCI and other stuff that could be helpful -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #19 from Kalzi --- (In reply to Kalzi from comment #18) > (In reply to Zamundaaa from comment #17) > > No, you'd still get a movable cursor and you'd also get a message about the > > lockscreen being broken. > > > > Instead of using the terminal in weston, you could also just start it from a > > tty and initiate suspend like this: > > > weston; sleep 10 && systemctl suspend > > Ok, so I was kind of a dumbass. Lol > I was able to launch the terminal. Ran [systemctl suspend] and I'll keep > testing to see if it happens on weston. Ok, it doesn't happen when I systemctl suspend from the desktop of weston. Rebooted from terminal while on weston, laptop rebooted to the lock screen, I didn't sign in, I closed the lid, waited a while, and opened it to a black screen. Does it have anything to do with SDDM not liking anything Wayland/weston? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #18 from Kalzi --- (In reply to Zamundaaa from comment #17) > No, you'd still get a movable cursor and you'd also get a message about the > lockscreen being broken. > > Instead of using the terminal in weston, you could also just start it from a > tty and initiate suspend like this: > > weston; sleep 10 && systemctl suspend Ok, so I was kind of a dumbass. Lol I was able to launch the terminal. Ran [systemctl suspend] and I'll keep testing to see if it happens on weston. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #16 from Kalzi --- (In reply to Zamundaaa from comment #15) > The terminal icon on the top left should be clickable. Note that libinput > defaults to disabling tap to click for some reason; if your touchpad has > buttons or can be physically pressed down, you need to do that for anything > to happen. > In the terminal you can execute "systemctl suspend" to cause it to suspend My trackpad doesn't have clickable buttons, but I can still click the corners, and it works, but it never did on Weston. Btw, I was searching around and found this on some Arch forums. Could it be related to this? https://bbs.archlinux.org/viewtopic.php?id=166964 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #14 from Kalzi --- (In reply to Zamundaaa from comment #13) > You can test quite easily if powertop is at fault by not executing it. Any > problems caused by it should also happen on Xorg though... > In the log you attached there is still no warnings or anything useful. > > The next thing to check would thus be if this also happens with other > Wayland compositors. Easiest to test is usually Weston; after installing it > you can use it by choosing it in the bottom left of the login screen as an > alternative to Plasma X11 / Wayland OK, I installed Weston from the Manjaro repos, and it gave me a very basic "desktop" that has nothing but time and date on the top right and terminal icon on the top left. Nothing is clickable. Right click doesn't work. Touchpad doesn't work either. Add to that my 4k display, which made the whole display so tiny. Unless, you have a specific version of weston that has a complete different interface, I don't know -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #12 from Kalzi --- Created attachment 150727 --> https://bugs.kde.org/attachment.cgi?id=150727=edit kwin2.log There is the log after adding that command to /etc/environment -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #11 from Kalzi --- (In reply to Zamundaaa from comment #10) > hmm, that log contains nothing of relevance, probably because debug logging > is disabled. Can you put > > QT_LOGGING_RULES="kwin_wayland_*.debug=true" > into /etc/environment, reboot and try again? Alright, I just did. It has been so much better, btw. I am now suspecting that it is caused by powertop, because I always run > sudo power --auto-tune and that does some changes to these Good Enable SATA link power management for host1 Good Enable SATA link power management for host2 Good Enable SATA link power management for host0 Good Enable Audio codec power management Good Bluetooth device interface status Good NMI watchdog should be turned off Good Autosuspend for unknown USB device 1-7 (8087:0a2a) Good Autosuspend for USB device xHCI Host Controller [usb2] Good Autosuspend for USB device Integrated_Webcam_HD [CN0CW54MLOG007AK0384A00] Good Autosuspend for USB device xHCI Host Controller [usb1] Good Runtime PM for I2C Adapter i2c-3 (i915 gmbus dpc) Good Runtime PM for I2C Adapter i2c-1 (Synopsys DesignWare I2C adapter) Good Runtime PM for I2C Adapter i2c-4 (i915 gmbus dpb) Good Runtime PM for I2C Adapter i2c-2 (SMBus I801 adapter at f040) Good Runtime PM for I2C Adapter i2c-0 (Synopsys DesignWare I2C adapter) Good Runtime PM for I2C Adapter i2c-5 (i915 gmbus dpd) Good Runtime PM for disk sda Good Runtime PM for PCI Device Intel Corporation Sunrise Point-LP PMC Good Runtime PM for PCI Device Intel Corporation Sunrise Point-LP PCI Express Root Port #1 Good Runtime PM for PCI Device Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 Good Runtime PM for PCI Device Intel Corporation Sunrise Point LPC Controller/eSPI Controller Good Runtime PM for PCI Device Intel Corporation Sunrise Point-LP Integrated Sensor Hub -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #9 from Kalzi --- Created attachment 150654 --> https://bugs.kde.org/attachment.cgi?id=150654=edit kwin.log Alright. I have reproduced, but this time the screen wasn't black, it was just frozen. Keyboard and cursor don't do anything. Got the kwin log and attached it here. kwin killall didn't fix it, it just refreshed the screen. I rebooted my laptop through ssh from my phone -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #8 from Kalzi --- BTW, I tried to ssh after I rebooted then closed the lid without logging into the desktop. So, maybe because there is no internet connection? I logged in then closed the lid, and I'll see if it happens again then I'll try again, because then there should be a network connection then I can ssh into it (hopefully). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #7 from Kalzi --- (In reply to Kalzi from comment #6) > (In reply to Zamundaaa from comment #5) > > that's quite odd. If you enable ssh, you could also ssh in with a second > > computer or your phone while the laptop isn't working and save the current > > log with > > > journalctl --user-unit plasma-kwin_wayland > ~/kwin.log > > then you can also try > > > killall -9 kwin_wayland > > and see if the laptop reacts to your inputs again. > > Of course it just chose to work because someone is actually is trying to > help me 臘 > It happened every single time before reporting this bug. I don't know if any > of the commands you've given me did anything, but I'm not getting anything > so far. I'll keep trying until I'm able to reproduce it and ssh into it from > my phone. Alright, so it happened again. I can't even ssh into the laptop when this happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #6 from Kalzi --- (In reply to Zamundaaa from comment #5) > that's quite odd. If you enable ssh, you could also ssh in with a second > computer or your phone while the laptop isn't working and save the current > log with > > journalctl --user-unit plasma-kwin_wayland > ~/kwin.log > then you can also try > > killall -9 kwin_wayland > and see if the laptop reacts to your inputs again. Of course it just chose to work because someone is actually is trying to help me 臘 It happened every single time before reporting this bug. I don't know if any of the commands you've given me did anything, but I'm not getting anything so far. I'll keep trying until I'm able to reproduce it and ssh into it from my phone. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #4 from Kalzi --- (In reply to Zamundaaa from comment #3) > yes. The "--boot -1" means that it'll fetch the log from the last boot Ok, so ran the second command > kwriteconfig5 --file startkderc --group General --key systemdBoot true Restarted laptop - closed lid before logging in - waited a while - opened lid - blackscreen - forced shutdown - started laptop - logged into wayland session Ran command >journalctl --boot -1 --user-unit plasma-kwin_wayland and this is what I got >Specifying boot ID or boot offset has no effect, no persistent journal was >found -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #2 from Kalzi --- (In reply to Zamundaaa from comment #1) > After you reproduce the bug, can you run > > journalctl --boot -1 --user-unit plasma-kwin_wayland > and upload the output here? > > Note that systemd startup is still off by default in 5.24; in order to get > logging to work you'll need to enable it with > > kwriteconfig5 --file startkderc --group General --key systemdBoot true > and reboot before triggering the bug. When this happens, I'd have to force shutdown the laptop by holding down the power button. Will the journalctl command still give me the log I'm looking for given that I'd just basically rebooted? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456723] New: Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 Bug ID: 456723 Summary: Laptop wakes up to a completely black screen after every suspend on wayland Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kalzwa...@yahoo.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** This happens only on wayland, and it doesn't matter which KDE Plasma version I'm on. Every time I close the lid and the let the laptop sit for a while then wake it up, I'm greeted with a black screen. No cursor, no indicator, no sign of any life beside the power button light and the keybaord backlight. It doesn't work no matter how long I wait and I can't even get into TTY. Only way to get out of it by force shutting off laptop from power button. STEPS TO REPRODUCE 1. Switch to wayland 2. Close the lid and wait a while 3. Open lid OBSERVED RESULT Complete black screen EXPECTED RESULT For lockscreen to show up SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Kernel Version: 5.15.53-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Nvidia/intel hybrid graphics with nvidia diabled by optimus manager / nvidia Geforce mx130 - I do have a wifi USB module plugged into my laptop -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439797] System Settings crashes in KCMLookandFeel::knsEntryChanged() when I try to update a global theme via GHNS window of Global Theme KCM
https://bugs.kde.org/show_bug.cgi?id=439797 Kalzi changed: What|Removed |Added CC|kalzwa...@yahoo.com | -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446905] Default application menu doesn't slide when clicked, it just appears.
https://bugs.kde.org/show_bug.cgi?id=446905 --- Comment #3 from Kalzi --- (In reply to Kalzi from comment #2) > (In reply to Michail Vourlakos from comment #1) > > This is expected. At your left edge you have enabled the parabolic-zoom > > effect. If you disabled then it work as you would expect it. When the > > parabolic effect is enabled it is expected the popup window to be "in the > > air" so all borders are enabled at that case. > > Where do I find the parabolic-zoom effect? I can't find it. Never mind, I found it. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446905] Default application menu doesn't slide when clicked, it just appears.
https://bugs.kde.org/show_bug.cgi?id=446905 --- Comment #2 from Kalzi --- (In reply to Michail Vourlakos from comment #1) > This is expected. At your left edge you have enabled the parabolic-zoom > effect. If you disabled then it work as you would expect it. When the > parabolic effect is enabled it is expected the popup window to be "in the > air" so all borders are enabled at that case. Where do I find the parabolic-zoom effect? I can't find it. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446905] New: Default application menu doesn't slide when clicked, it just appears.
https://bugs.kde.org/show_bug.cgi?id=446905 Bug ID: 446905 Summary: Default application menu doesn't slide when clicked, it just appears. Product: lattedock Version: 0.10.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: kalzwa...@yahoo.com Target Milestone: --- Created attachment 144493 --> https://bugs.kde.org/attachment.cgi?id=144493=edit Video to showcase the bug SUMMARY *** The default application menu doesn't slide when clicked, it just appears. It happens even with the "popup margin" disabled. When I add a gap to the system try, it starts showing up, not sliding, but when I disable the popup gap, the system try goes back to sliding but the application menu doesn't, it just removes the gap. *** STEPS TO REPRODUCE 1. Have a dock and a panel 2. Add the applications menu to the dock and the system try widget to the panel. The system tray will slide like normal when clicked, but the applications menu doesn't. 3. Now, right click on the panel, hover over layouts, then choose "edit layouts", choose the current layout then hit details, increase the number on the "popup gap", you will notice that now the system tray will just appear just like the application menu. Now, disable the popup gap, then the system tray will go back to sliding, but the application menu still just appears, no sliding. I've attached a little video to showcase this. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) Operating System: Manjaro Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.6-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Latte-Dock 0.10.4-1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446166] New: Changing window decorations to anything not default causes a system performance hit
https://bugs.kde.org/show_bug.cgi?id=446166 Bug ID: 446166 Summary: Changing window decorations to anything not default causes a system performance hit Product: systemsettings Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kalzwa...@yahoo.com Target Milestone: --- SUMMARY Every time I use a third party window decoration, the system starts chugging as if the frame rate drops to the 20s or so. I am almost certain that this is related to the 4k screen (and possibly the GPU) I have, as it gets a lot better when I lower the resolution to 1080p. It doesn't go away completely on 1080p, but it gets a lot better. Also, it is mostly noticeable on the "slide back" and minimizing the windows effects. "Slide back" either glitches before it moves, or it is just straight up choppy (depends on the decorations), Minimizing windows is the same, it pauses halfway for a split second then minimizes. It even affects the experience on the web browser, because the scrolling of web pages gets slow, too. This has happened on every single distro with KDE Plasma I've ever used, so I guess that eliminates the "distro specific issue" possible argument. Also, a side note, the "window decorations" section of the settings has terrible scrolling. It jumps between scrolls, as if it gets stuck or something, every time I scroll. Thought I would mention that, too, since I think they are related. Please let me know if you need a separate bug report for it. STEPS TO REPRODUCE 1. Install a third party window decoration and start using the system 2. Switch to 1080p resolution and notice the issue gets a lot better. OBSERVED RESULT System slows down/chugs when changing window decorations to something that is not default. EXPECTED RESULT Same performance (a little less is ok) when using third party decorations. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445767] Global menu items overlap with the clock on the panel when the opened app has too many menu options
https://bugs.kde.org/show_bug.cgi?id=445767 --- Comment #1 from Kalzi --- Created attachment 143743 --> https://bugs.kde.org/attachment.cgi?id=143743=edit Overlapped text in the panel -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445767] New: Global menu items overlap with the clock on the panel when the opened app has too many menu options
https://bugs.kde.org/show_bug.cgi?id=445767 Bug ID: 445767 Summary: Global menu items overlap with the clock on the panel when the opened app has too many menu options Product: systemsettings Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kalzwa...@yahoo.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When opening an app that has too many menu options (Bleachbit in this case), the global menu overlaps with the clock in the panel, it goes under/above the clock which mixes the text to where it becomes a jumble mess in that area. See attached screenshot, please! STEPS TO REPRODUCE 1. Add "global menu" widget and put it in the panel (latte panel in my case) 2. Install Bleachbit (or any app that has too many menu options) 3. Make sure you have something visible in the center of the panel (like the clock widget or something) OBSERVED RESULT Global menu options for Bleachbit are overlapped with the clock. It is not that clear if the menu options go above or under the clock, but it is all jumbled up EXPECTED RESULT I think that the system/panel/or the global menu should detect that an app has too many options, and that there is another widget in the way, then wrap the rest of the options under a drop-down menu with a little arrow to indicate that there are more options for this menu. I think that this would be ideal for situations like this. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444984] Latte dock autohides on an empty desktop even though "autohide" isn't enabled, "dodge active" enabled only
https://bugs.kde.org/show_bug.cgi?id=444984 --- Comment #7 from Kalzi --- (In reply to Michail Vourlakos from comment #6) > Are you sure you are using Latte 0.10.3? > If you run latte-dock -v in command prompt what version does it show? Yes, I'm sure. I have 0.10.3 installed. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444984] Latte dock autohides on an empty desktop even though "autohide" isn't enabled, "dodge active" enabled only
https://bugs.kde.org/show_bug.cgi?id=444984 --- Comment #5 from Kalzi --- (In reply to Michail Vourlakos from comment #4) > 1. Have you enabled PLASMA_USE_QT_SCALING=true in your system? > > 2. it is one of those bugs that without a proper way/steps to reproduce in > my system it is too difficult to find out what breaks. > > I will leave it open for a few weeks in case more info are found. > 1. Have you enabled PLASMA_USE_QT_SCALING=true in your system? > Yes, always have it. It is a must for me, otherwise things will look crazy on my desktop. I will just wait and see what happens. I will report back if it happens again. Thanks -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444984] Latte dock autohides on an empty desktop even though "autohide" isn't enabled, "dodge active" enabled only
https://bugs.kde.org/show_bug.cgi?id=444984 --- Comment #3 from Kalzi --- (In reply to Michail Vourlakos from comment #1) > I use the same setup and I dont have any such issue in my system. > It occured to me only when I use PLASMA_USE_QT_SCALING=true but that > scenario was fixed in 0.10.3 . > > we need a way to reproduce reliably. e.g. when does it occur? do you know if > it occurs when using a multi-screen environment? maybe when changing screen > resolution? maybe occasionally after startup? etc... I apologize for the late reply. I normally know that someone commented via an email, but I haven't received an email until today. -It happens randomly. I cannot reproduce it, it just happens at random times. It hasn't happened this whole week. -I only have one screen and I never change the resolution. It is always 4k. It doesn't happen after start up, it just happens at random times, and I'd have to kill latte then launch it again to fix it. If you have a certain command that you'd like me to run after it happens to collect some logs, let me know, and I'll be happy to run it and post the logs here. Thank you -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444984] New: Latte dock autohides on an empty desktop even though "autohide" isn't enabled, "dodge active" enabled only
https://bugs.kde.org/show_bug.cgi?id=444984 Bug ID: 444984 Summary: Latte dock autohides on an empty desktop even though "autohide" isn't enabled, "dodge active" enabled only Product: lattedock Version: 0.10.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: kalzwa...@yahoo.com Target Milestone: --- SUMMARY Every couple of days, Latte dock starts just autohiding on an empty desktop even though only "dodge active" is enabled, not "autohide" STEPS TO REPRODUCE 1. Edit the dock 2. Set it to "dodge active" (not sure about others as I don't use them) 3. It will auto hide on an empty desktop every couple of days until I kill it through ksysgaurd. OBSERVED RESULT It auto-hides on an empty desktop, and I'd have to kill the app then restart it EXPECTED RESULT It should only auto-hide when there is an active window, as chosen in the settings. SOFTWARE/OS VERSIONS Windows: macOS: Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.10-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Latte dock is 0.10.3 that I had to download from the AUR website, not from Manjaro's pamac, because it is not available there even if I searched in the AUR from there. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444403] Battery percentage text is white on white background when changing the pallette to "Smart Colors Based On Desktop Background"
https://bugs.kde.org/show_bug.cgi?id=03 --- Comment #2 from Kalzi --- (In reply to Michail Vourlakos from comment #1) > This is applet responsibility, so latte can not do something more. For > systray workarounds, it is suggested to use > https://github.com/psifidotos/plasma-systray-latte-tweaks That did it for me. Thank you so much -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444403] New: Battery percentage text is white on white background when changing the pallette to "Smart Colors Based On Desktop Background"
https://bugs.kde.org/show_bug.cgi?id=03 Bug ID: 03 Summary: Battery percentage text is white on white background when changing the pallette to "Smart Colors Based On Desktop Background" Product: lattedock Version: 0.10.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: kalzwa...@yahoo.com Target Milestone: --- Created attachment 142885 --> https://bugs.kde.org/attachment.cgi?id=142885=edit Battery percentage text is white text on white background SUMMARY When editting latte dock, and setting the "pallette" under appearance to "Smart Colors Based On Desktop Background" the battery percentage text becomes white text on white background, and it is rendered invisible. This happens no matter the theme, light or dark default breeze (I guess it wouldn't probably matter here since the dock would be changing color based on the desktop background). STEPS TO REPRODUCE 1. Edit latte dock 2. click on appearance and set the "pallette" to "Smart Colors Based On Desktop Background" from the drop down menu 3. OBSERVED RESULT Battery percentage text is white on a white background and is invisible. EXPECTED RESULT Battery percentage text should be dark text on a white background and vice versa following the set system theme. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.13.19-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Please see attached screenshot -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #33 from Kalzi --- nevermind*. there really needs to be "edit comment" on this site. lol -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #32 from Kalzi --- Never, it is not availble on manjaro for some reason, even though i searched the AUR through pamac GUI. I had to download the file from the actual aur webiste. It is working now. Thank you so much -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #31 from Kalzi --- (In reply to Michail Vourlakos from comment #29) > (In reply to Mathias C. from comment #28) > > The dock now works perfectly. Thank you very much!! > > > > This has been a great experience of bug reporting and fixing!! Thank you for > > the great work!! > > Nice! and now we can have a 0.10.3 release! :) Thank you so much for your hard work. Have you pushed it to the AUR yet? Or is it something you don't do, and the AUR community does. Because I still don't have the update there. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #30 from Kalzi --- (In reply to Mathias C. from comment #28) > The dock now works perfectly. Thank you very much!! > > This has been a great experience of bug reporting and fixing!! Thank you for > the great work!! I don't know if this comment is directed at me, the developer or both, but I love KDE and I am determined to help make it the best possible. :) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #26 from Kalzi --- (In reply to Michail Vourlakos from comment #23) > Can someone test the provided solution? because v0.10.3 is going to be > released the next days and it is going to include these fixes. I will test. I'm on manjaro, if that matters. Just let me know when, and I'll do it. (In reply to Michail Vourlakos from comment #25) > (In reply to Kalzi from comment #24) > > (In reply to Michail Vourlakos from comment #23) > > > Can someone test the provided solution? because v0.10.3 is going to be > > > released the next days and it is going to include these fixes. > > > > I will test. I'm on manjaro, if that matters. > > Just let me know when, and I'll do it. > > The patches are already merged, I would just want someone to test them > before I release 0.10.3 I'll test it when I get home. Could you provide a link, please. And is it just a matter of a get clone then install? Or how do I go about it? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #24 from Kalzi --- (In reply to Michail Vourlakos from comment #23) > Can someone test the provided solution? because v0.10.3 is going to be > released the next days and it is going to include these fixes. I will test. I'm on manjaro, if that matters. Just let me know when, and I'll do it. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #18 from Kalzi --- (In reply to Michail Vourlakos from comment #16) > (In reply to Mathias C. from comment #15) > > (In reply to Michail Vourlakos from comment #14) > > > (In reply to Mathias C. from comment #13) > > > > This is not really a "per-screen" scaling problem. The issue is present > > > > even > > > > when I use the single display on my laptop. > > > > > > > > And yes, I also tried to create a layout with a "always visible" bottom > > > > dock, and the problem remains: the dock is completely unresponsive > > > > although > > > > it stays visible. > > > > > > > > Also, latte-dock worked perfectly until the update to 0.10, so I would > > > > not > > > > say it's plasma related, but rather a potential regression in latte. > > > > > > If I am able to reproduce this in my single screen system I will take a > > > look > > > then. > > > > > > Send me the exact steps to setup my screen settings to reproduce the issue > > > please. > > > > Thank you very much!! > > > > Basically, just set a global scaling in the display settings (I tried both > > 200% and 175% as I have a hidpi panel). > > That means Plasma is going to set the variable QT_SCREEN_SCALE_FACTORS, > > which in junction with PLASMA_USE_QT_SCALING (necessary for the Plasma menus > > to respect the scaling) makes the bottom dock unresponsive to any click. > > no no, I mean exact steps for everything: > 1. I just have to set Plasma Scaling from plasma systemsetttings to 175% ? > > dont I have to setup PLASMA_USE_QT_SCALING somehow etc. etc. ? Set the scale to 200 or 175 in the settings, add PLASMA_USE_QT_SCALING to .bash_profile, .profile or /etc/environment log out and log in. Install latte and try it. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #17 from Kalzi --- (In reply to Mathias C. from comment #10) > Investigating this further, I manage to replicate the issue on the second > user. The problem is the variable QT_SCREEN_SCALE_FACTORS. If you set any > global scaling in the Plasma settings, that variable get set and latte-dock > stops working. > Moreover, more specifically, what does not work is the bottom dock. I > created a layout with a top panel and a bottom dock, and only the latte > results unresponsive. I can confirm that. I've managed to put a latte dock to the side and it was responsive. I couldn't put one up or right (because honestly the settings menu that I managed to get on latte is kind of confusing). It's only the bottom one that is not responsive. I only have PLASMA_USE_QT_SCALING enabled, I've never seen nor used the QT_SCREEN_SCALE_FACTORS. Unless, it gets set automatically when changing the scaling in the settings to 200, which is something I've always had to do because of the 4k screen and never had an issue with latte dock even on 0.10. It seems like the issue started happening after the incremental updates of 0.10+ -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 444301] New: Akonadi opens gmail login webpage when adding a yahoo account
https://bugs.kde.org/show_bug.cgi?id=444301 Bug ID: 444301 Summary: Akonadi opens gmail login webpage when adding a yahoo account Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Account Wizard Assignee: kdepim-b...@kde.org Reporter: kalzwa...@yahoo.com Target Milestone: --- SUMMARY Trying to add my two yahoo accounts and one gmail account, but every time I add my yahoo accounts, a window opens with a gmail account log in prompt. I am trying to add a yahoo account, I don't know why it keeps opening a gmail log in prompt webpage STEPS TO REPRODUCE 1. install kmail 2. Start adding a yahoo account and go through the steps 3. OBSERVED RESULT Akonadi opens a gmail login prompt instead of a yahoo one when adding a yahoo account to kmail EXPECTED RESULT Akonadi should open a yahoo login prompt instead of a gmail one SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87 Qt Version: 5.15.2 ADDITIONAL INFORMATION This is happening on a Manjaro install. It is still running kde 5.22.5. kmail version:21.08.2-1 Akonadi version: 21.08.2-1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #8 from Kalzi --- (In reply to Mathias C. from comment #7) > I just found how to "fix" it on my system. > > 1. Open a terminal and run 'unset PLASMA_USE_QT_SCALING' > 2. Run 'latte-dock' in the same terminal > > I have an hidpi screen and I need that variable to have Plasma following the > dpi scaling of the system on X11. Oh shoot! I have that enabled. But I need that line to make the UI look normal. I have a 4k screen, too, and removing that line makes things look out of place :/ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #6 from Kalzi --- (In reply to Mathias C. from comment #5) > Hi all, > I have the exact same issue since I updated to Latte 0.10.*. These are the > details of my system: > > Disto: Archlinux > KDE Plasma Desktop: 5.22.* and 5.23.* > KDE Frameworks Version: 5.87 > Qt Version: 5.15.2 > > I already deleted any folder relative to latte-dock configuration and > nothing solved. Thanks for confirming. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #4 from Kalzi --- (In reply to Michail Vourlakos from comment #3) > no idea how you fall into this situation, is that a Plasma Desktop ? Yes, that is. All three distros are plasma. Manjaro being a version earlier 5.22.5. There is another user on reddit who confirmed they have the same issue. I've encouraged them to confirm here, too. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #2 from Kalzi --- I have now tried it on a third distro, Manjaro, that is still running kde plasma 5.22.5. It is still doing the same exact thing. Brand new install. Also, attached a video showing the bug. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 --- Comment #1 from Kalzi --- Created attachment 142763 --> https://bugs.kde.org/attachment.cgi?id=142763=edit Video shows the dock This shows how I can't do anything with the dock. Also, this is Manjaro, the third distro I've tried -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444222] New: Latte doesn't work. Can't interact with it. Just autohides
https://bugs.kde.org/show_bug.cgi?id=444222 Bug ID: 444222 Summary: Latte doesn't work. Can't interact with it. Just autohides Product: lattedock Version: 0.10.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: kalzwa...@yahoo.com Target Milestone: --- SUMMARY The dock just never works. Tried it on kde neon and endeavour OS and it is doing the same thing. After installation, I'd launch it, then it launches for a couple of seconds then disappears as if it were set to "autohid" and I can never bring it back up. It would only pop up again when I open another application, again, for a couple of seconds, then hides again. If I try to catch it before it hides with a right click, the menu that shows up is just a regular desktop right click. I can never interact with the dock. STEPS TO REPRODUCE 1. Just download it and run it. OBSERVED RESULT Can't interact with the dock at all. EXPECTED RESULT A dock that works and stays on the screen unless it is set to autohide. Also, a dock that can be interacted with. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443530] Notification is cut off at the bottom of the screen.
https://bugs.kde.org/show_bug.cgi?id=443530 --- Comment #4 from Kalzi --- (In reply to Nate Graham from comment #3) > Oh sweet! Thanks for checking. You are welcome! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 443492] Krunner and panel editing tool are not centered on the screen
https://bugs.kde.org/show_bug.cgi?id=443492 --- Comment #4 from Kalzi --- (In reply to Nate Graham from comment #3) > It does, but you'll only get the right visual results if the resolution you > choose matches the physical resolution of the screen. :) Well, then we have no beef. lol I am back to 4k resolution after your recommendation, and you were right, the battery life is the same. Thank you -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443530] Notification is cut off at the bottom of the screen.
https://bugs.kde.org/show_bug.cgi?id=443530 --- Comment #2 from Kalzi --- (In reply to Nate Graham from comment #1) > Hmm, that's weird. I remember you saying in another bug report that you're > using PLASMA_USE_QT_SCALING=1. Can you reproduce the issue if you make this > condition happen either in the Plasma Wayland session, or without that > environment variable set? This doesn't happen on 5.23. I think the upgrade fixed it. I just tried to reproduce it, but the notifications stack shows up just fine. I have even tried moving the panel to different edges of the screen, and it was still working well. I think it is safe to mark this bug as resolved. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 443492] Krunner and panel editing tool are not centered on the screen
https://bugs.kde.org/show_bug.cgi?id=443492 --- Comment #2 from Kalzi --- (In reply to Nate Graham from comment #1) > Does it work in the Plasma Wayland session? > > Also, does it work on either X11 or Wayland in Plasma 5.23? I have found out why it was happening. I had my resolution set to 1800 instead of 2160. There is only one resolution on wayland, so I couldn't tell you. I still think krunner and the panel editing menu should adjust based on the resolution of the screen. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 443935] New: kmail crashed while adding my email accounts
https://bugs.kde.org/show_bug.cgi?id=443935 Bug ID: 443935 Summary: kmail crashed while adding my email accounts Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Account Wizard Assignee: kdepim-b...@kde.org Reporter: kalzwa...@yahoo.com Target Milestone: --- Application: accountwizard (0.2) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.11.0-37-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.0 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Just adding my email accounts and it just crashed for no reason. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Account Assistant (accountwizard), signal: Segmentation fault [New LWP 42834] [New LWP 42835] [New LWP 42836] [New LWP 42837] [New LWP 42838] [New LWP 42863] [New LWP 42868] [New LWP 42869] [New LWP 42870] [New LWP 42871] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7febb70d6aff in __GI___poll (fds=0x7ffdad73be38, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7febb15debc0 (LWP 42832))] Thread 11 (Thread 0x7feb7145f700 (LWP 42871)): #0 0x7febb70d6aff in __GI___poll (fds=0x7feb54003a20, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7febb4bf236e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7febb4bf24a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7febb804e5eb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7feb54000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7febb7ff287b in QEventLoop::exec(QFlags) (this=this@entry=0x7feb7145e9e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7febb7e0c292 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7febb7e0d42c in QThreadPrivate::start(void*) (arg=0x559da22ec2f0) at thread/qthread_unix.cpp:329 #7 0x7febb55a7609 in start_thread (arg=) at pthread_create.c:477 #8 0x7febb70e3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7feb71c60700 (LWP 42870)): #0 0x7febb4c3f508 in g_mutex_unlock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7febb4bf1d30 in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7febb4bf2312 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7febb4bf26f3 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7feb71f39f8a in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x7febb4c1bad1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7febb55a7609 in start_thread (arg=) at pthread_create.c:477 #7 0x7febb70e3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7feb72ffd700 (LWP 42869)): #0 0x7febb70d6aff in __GI___poll (fds=0x559da22d8ae0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7febb4bf236e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7febb4bf24a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7febb4bf24f1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7febb4c1bad1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7febb55a7609 in start_thread (arg=) at pthread_create.c:477 #6 0x7febb70e3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7feb737fe700 (LWP 42868)): #0 0x7febb70d6aff in __GI___poll (fds=0x7feb64000b60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7febb4bf236e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7febb4bf24a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7febb804e5eb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7feb64005f60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7febb7ff287b in QEventLoop::exec(QFlags) (this=this@entry=0x7feb737fd9e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7febb7e0c292 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7febb7e0d42c in QThreadPrivate::start(void*) (arg=0x559da2227ad0) at thread/qthread_unix.cpp:329 #7 0x7febb55a7609 in start_thread (arg=) at pthread_create.c:477 #8 0x7febb70e3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7feb727fc700 (LWP 42863)): #0 0x7febb70d6aff in __GI___poll (fds=0x7feb5c004200, nfds=1, timeout=-1) at
[systemsettings] [Bug 439797] System Settings crashes in KCMLookandFeel::knsEntryChanged() when I try to update a global theme via GHNS window of Global Theme KCM
https://bugs.kde.org/show_bug.cgi?id=439797 --- Comment #4 from Kalzi --- Created attachment 142555 --> https://bugs.kde.org/attachment.cgi?id=142555=edit Settings crashes when downloading a new theme This bug still happens on 5.23 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439797] System Settings crashes in KCMLookandFeel::knsEntryChanged() when I try to update a global theme via GHNS window of Global Theme KCM
https://bugs.kde.org/show_bug.cgi?id=439797 --- Comment #3 from Kalzi --- Created attachment 142554 --> https://bugs.kde.org/attachment.cgi?id=142554=edit New crash information added by DrKonqi systemsettings5 (5.23.0) using Qt 5.15.3 - What I was doing when the application crashed: Tried to download Nordic theme. Half way then the system settings crashed. This happens every single time. It was happening on 5.22+ and now on 5.23, too. -- Backtrace (Reduced): #4 0x7f697ef269cd in QDir::fromNativeSeparators(QString const&) () at /usr/include/c++/9/bits/atomic_base.h:318 #5 0x7f697ef3ab67 in QFileInfoPrivate::QFileInfoPrivate(QString const&) (file=..., this=0x555fd36e1920) at /usr/include/c++/9/bits/atomic_base.h:279 #6 QFileInfo::QFileInfo(QString const&) (this=0x7ffcfffaeb78, file=...) at io/qfileinfo.cpp:347 #7 0x7f6929add114 in KCMLookandFeeloperator() (__closure=, __closure=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:117 #8 KCMLookandFeel::knsEntryChanged(KNSCore::EntryWrapper*) (this=0x555fd1340f40, wrapper=) at ./kcms/lookandfeel/kcm.cpp:126 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439797] System Settings crashes in KCMLookandFeel::knsEntryChanged() when I try to update a global theme via GHNS window of Global Theme KCM
https://bugs.kde.org/show_bug.cgi?id=439797 Kalzi changed: What|Removed |Added CC||kalzwa...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 443788] Attempting to share via email when there are no suitable email clients installed causes the calling app to crash in Purpose::EmailJob::start()
https://bugs.kde.org/show_bug.cgi?id=443788 --- Comment #6 from Kalzi --- This is an absolutely useless comment, but yaaay, this is my first official contribution to KDE Plasma that has been confirmed and assigned. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443788] New: Sharing a file/folder via email causes the screen to panic
https://bugs.kde.org/show_bug.cgi?id=443788 Bug ID: 443788 Summary: Sharing a file/folder via email causes the screen to panic Product: kwin Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: kalzwa...@yahoo.com Target Milestone: --- SUMMARY When right-click on a desktop icon/folder, hover over "share" and choose "send via email", the desktop would blink, goes black for a second then "refreshes". I don't think that this is a normal behavior. I think that there should be a message that tells me "there isn't an email app" or something like that, since I don't have an email app. STEPS TO REPRODUCE 1. No email app installed 2. Right-click on a folder/file on the desktop 3. Hover over "share" and choose "share via email" OBSERVED RESULT Screen would blink/panic, goes black for a brief second, then acts like it just "refreshed". EXPECTED RESULT When trying to share a folder/file (or any shareable thing) via email, and the system detects that there isn't an email app installed, a message should pop up notifying the user that there isn't an email app, and the share cannot be completed. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon User Edition (available in About System) KDE Plasma Version: 5.23 KDE Frameworks Version: 5.87 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 443530] New: Notification is cut off at the bottom of the screen.
https://bugs.kde.org/show_bug.cgi?id=443530 Bug ID: 443530 Summary: Notification is cut off at the bottom of the screen. Product: frameworks-knotifications Version: 5.86.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: kalzwa...@yahoo.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 142286 --> https://bugs.kde.org/attachment.cgi?id=142286=edit Screenshot showing the cut off notification pop up SUMMARY Notification is cut off at the bottom of the screen. STEPS TO REPRODUCE 1. Example, connect protonvpn (or any vpn provider) 2. System will give several notifications about the vpn connecion. 3. Bottom notification is cut off by the bottom of the screen. OBSERVED RESULT half visible notification pop up EXPECTED RESULT fully visible notification pop up SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon User (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 443492] New: Krunner and panel editing tool are not centered on the screen
https://bugs.kde.org/show_bug.cgi?id=443492 Bug ID: 443492 Summary: Krunner and panel editing tool are not centered on the screen Product: krunner Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: kalzwa...@yahoo.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 142260 --> https://bugs.kde.org/attachment.cgi?id=142260=edit Krunner not centered to the screen SUMMARY Krunner and panel editing tool are not centered on the screen. Krunner has only two settings, "top" and "center", and they both only move it vertically to the top or the middle of the screen, nothing horizontal. STEPS TO REPRODUCE 1. Open Krunner or right click on the panel and click "edit panel", you will see that both krunner and the editing tool on the top sit to the right of the screen, not centered 2. 3. OBSERVED RESULT EXPECTED RESULT Both Krunner and panel editing tool should be center to the window when invoked SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon User Edition (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I do have PLASMA_USE_QT_SCALING=1 enabled because I have a 4k screen, and without that line, things would look out of place. Especially menus icons and the panel. The panel would be too small that I have to scale it to 114 to have it a nice size. -- You are receiving this mail because: You are watching all bug changes.
