[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 --- Comment #17 from Serena Star --- This is getting dire at this point. I cannot log into my Outlook (dot) com account on Debian 12. I have 2 factor authentication on and have tried using an app password but I keep getting an error about "Login failed, server replied: A04 NO AUTHENTICATE failed." We need OAUTH2 logins supported immediately on Kontact. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 Serena Star changed: What|Removed |Added CC||lionsshark...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 485470] New: Kontact as a Flatpak clashes with Debian installation
https://bugs.kde.org/show_bug.cgi?id=485470 Bug ID: 485470 Summary: Kontact as a Flatpak clashes with Debian installation Classification: Applications Product: kontact Version: 5.24.4 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: lionsshark...@gmail.com Target Milestone: --- *** 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 was messing around with Kontact in Flatpak to compare feature parity with the older version shipped in Debian 12. The Flatpak tends to take in accounts from Akonadi already in the Debian installation instead of being a completely isolated instance separate from Debian. STEPS TO REPRODUCE 1. Have Kontact installed from apt on Debian with accounts already set up 2. Install Kontact as a Flatpak 3. Flatpak version recognizes the accounts from the Debian/Apt version and somehow interacts with the Debian Akonadi database 4. Sync, but unsuccessfully. All account info (even from accounts freshly created in the flatpak version) does not sync in the flatpak version and no data populates. OBSERVED RESULT Flatpak version of the app is devoid of data for all recognized accounts. All changes and syncing is visible on the Debian version. The Flatpak version is functionally useless when the Debian database exists. EXPECTED RESULT The Flatpak should be completely independent of the Debian installation. When installed for the first time, the Flatpak should have no accounts set up and when an account is set up, it should populate accordingly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian 12 with Kernel 6.1.0-18-amd64 (64-bit) (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION On Debian version, I set up my Akonadi database to use SQLite instead of MySQL. -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 482266] Cannot move tasks to Google or Microsoft 365 task lists
https://bugs.kde.org/show_bug.cgi?id=482266 --- Comment #1 from Serena Star --- I am using Debian 12.5 If this has been fixed in a later version, please let me know and you can close the issue. I know Debian ships old versions. -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 482266] New: Cannot move tasks to Google or Microsoft 365 task lists
https://bugs.kde.org/show_bug.cgi?id=482266 Bug ID: 482266 Summary: Cannot move tasks to Google or Microsoft 365 task lists Classification: Applications Product: zanshin Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: er...@kde.org Reporter: lionsshark...@gmail.com CC: mbe...@ipsquad.net Target Milestone: already done Created attachment 166327 --> https://bugs.kde.org/attachment.cgi?id=166327&action=edit Zanshin tasks being unable to be moved to Google or Microsoft SUMMARY *** I cannot move a task from the inbox to a Google Tasks list or a Microsoft Office 365 list. I can create Google Tasks in KOrganizer fine. *** STEPS TO REPRODUCE 1. Create task 2. Press M to move 3. Try to move task to a Google or Microsoft account but it is greyed OBSERVED RESULT I cannot move tasks into a Google or Microsoft task list EXPECTED RESULT I should be able to move tasks into Google task lists (to match KOrganizer functionality) and possibly Microsoft task lists (depending on limitations of Exchange sync) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel - 6.1.0-18-amd64 (64-bit) (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 477599] New: Setting Merkuro Month View to "Basic Month Grid" messes up week view
https://bugs.kde.org/show_bug.cgi?id=477599 Bug ID: 477599 Summary: Setting Merkuro Month View to "Basic Month Grid" messes up week view Classification: Applications Product: Merkuro Version: 23.08.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: lionsshark...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 163527 --> https://bugs.kde.org/attachment.cgi?id=163527&action=edit Week view as described in summary SUMMARY *** Setting Merkuro Month View to "Basic Month Grid" messes up week view. Instead, it shows the same day across the entire week view and the y-axis is set to hours of the day. *** STEPS TO REPRODUCE 1. Change "Month View Mode" to "Basic month grid" while in the week view 2. Look at base calendar widget 3. Week view appears as described in Summary OBSERVED RESULT The same day is shown across the entire week view and the y-axis is set to hours of the day. EXPECTED RESULT This setting should not affect or break the week view at all. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.6.2-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Picture of what I see in week view is attached. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 464247] Article images too large to fit in viewport
https://bugs.kde.org/show_bug.cgi?id=464247 Serena Star changed: What|Removed |Added CC||em.bugs.kde@jjussi.com --- Comment #2 from Serena Star --- *** Bug 426128 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 426128] Pictures are not scaled
https://bugs.kde.org/show_bug.cgi?id=426128 Serena Star changed: What|Removed |Added Status|REPORTED|RESOLVED CC||lionsshark...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Serena Star --- Pretty sure this is a duplicate *** This bug has been marked as a duplicate of bug 464247 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 464247] Article images too large to fit in viewport
https://bugs.kde.org/show_bug.cgi?id=464247 Serena Star changed: What|Removed |Added CC||lionsshark...@gmail.com --- Comment #1 from Serena Star --- I have the same issue on my device. I can zoom to the smallest size and high resolution images will still appear to be massive in the feed viewer of Akregator -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 476967] New: Plasma Integration Firefox extension does not work on LibreWolf
https://bugs.kde.org/show_bug.cgi?id=476967 Bug ID: 476967 Summary: Plasma Integration Firefox extension does not work on LibreWolf Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: lionsshark...@gmail.com Target Milestone: --- Created attachment 163134 --> https://bugs.kde.org/attachment.cgi?id=163134&action=edit Plasma Browser Extension Error SUMMARY *** Plasma Integration Firefox extension does not work on LibreWolf, extension popup has error. *** STEPS TO REPRODUCE 1. Install Plasma Browser Integration on LibreWolf 2. Play YouTube video 3. Add-on popup shows error mentioned in "Observed Result" OBSERVED RESULT Plasma Browser Integration popup says the following after playing media on LibreWolf. "Failed to connect to the native host. Make sure the 'plasma-browser-integration' package is installed correctly and that you are running Plasma 5.13 or later. No such native application org.kde.plasma.browser_integration" EXPECTED RESULT My media should appear in the media player widget of my KDE Plasma and the browser extension should work fine on LibreWolf since it is a fork of Firefox. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.6.1-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Plasma Integration works perfectly on Firefox -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 --- Comment #33 from Serena Star --- Created attachment 162332 --> https://bugs.kde.org/attachment.cgi?id=162332&action=edit First Google Groupware works, 2nd doesn't My first Google Groupware account works perfectly but the 2nd one fails, and shows nothing. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 --- Comment #32 from Serena Star --- Tried to revisit this issue by trying to set up my primary google account. I have one account working, but the 2nd one says "not configured" and then "Can't fetch password". I tried adding the "[network] section" to the broken 2nd account but it fixes nothing. Bringing up the configuration window for Google Groupware just shows it all unpopulated. I can log into my 2nd Google account as many times as I want to no avail. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471352] Discover crashes while looking for updates when OpenDesktop account is signed in
https://bugs.kde.org/show_bug.cgi?id=471352 --- Comment #4 from Serena Star --- Created attachment 161901 --> https://bugs.kde.org/attachment.cgi?id=161901&action=edit Discover Terminal Output -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471352] Discover crashes while looking for updates when OpenDesktop account is signed in
https://bugs.kde.org/show_bug.cgi?id=471352 Serena Star changed: What|Removed |Added CC||alydar...@outlook.com Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Serena Star --- (In reply to Nate Graham from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. Can you please attach a backtrace of the crash using the > coredumpctl command-line program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? > Thanks! Now it doesn't crash anymore on Discover version 5.27.8, but I do notice that when I am logged into an open desktop account, my fans on my gaming laptop spin up heavy, as if something resource-intensive was running, specifically when the program searches for updates. I will attach what appears when I run Discover in terminal. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 473897] New: Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 Bug ID: 473897 Summary: Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured" Classification: Frameworks and Libraries Product: Akonadi Version: 5.24.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Google Resource Assignee: kdepim-b...@kde.org Reporter: alydar...@outlook.com CC: c...@carlschwan.eu, dvra...@kde.org Target Milestone: --- SUMMARY *** Cannot sync calendar events from Google Accounts. When account is newly set up, "Configured account does not exist" error appears, refreshing gives "Resource is not configured". Calendars do not show up anywhere. *** STEPS TO REPRODUCE 1. Add Google Groupware account 2. Configure and save 3. "Resource is not configured" appears. Managing this resource brings up google login in browser again. 4. Refresh to see "Resource is not configured" 5. Calendars do not appear/sync OBSERVED RESULT Calendars do not appear/sync EXPECTED RESULT Calendars sync successfully, resource says "Ready" SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel - 6.4.12-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 471966] New: Using KRunner sometimes stops meta key from opening launcher
https://bugs.kde.org/show_bug.cgi?id=471966 Bug ID: 471966 Summary: Using KRunner sometimes stops meta key from opening launcher Classification: Plasma Product: krunner Version: 5.27.6 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lionsshark...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY *** After KRunner is used, pressing the meta key to open your launcher (kickoff/"start menu", to be clear) sometimes does not work anymore. Alt+F1 command always works to open launcher when it is the assigned keyboard shortcut. Putting the computer to sleep and bringing it back up fixes the bug. *** STEPS TO REPRODUCE 1. Run KRunner 2. Close KRunner 3. Try to open launcher with Meta key 4. Launcher does not open, nothing happens OBSERVED RESULT Pressing the meta key to open your launcher does not work after KRunner is opened. EXPECTED RESULT KRunner having been opened in the past should not affect the user's ability to open their launcher with the meta key. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel 6.4.1-arch2-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 471803] New: Kirigami makes colored icons black shadows
https://bugs.kde.org/show_bug.cgi?id=471803 Bug ID: 471803 Summary: Kirigami makes colored icons black shadows Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.107.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: lionsshark...@gmail.com CC: notm...@gmail.com Target Milestone: Not decided Created attachment 160004 --> https://bugs.kde.org/attachment.cgi?id=160004&action=edit Shadowy icons from Oxygen in Kasts and KClock SUMMARY *** When using an icon theme that has colored action icons (I use Oxygen icons), Kirigami apps make them look like black shadows instead of their proper, colored icons. *** STEPS TO REPRODUCE 1. Use icon theme with colored "Actions" icons 2. Run app that uses Kirigami 3. Actions icons are black shadowy versions of what they should look like. OBSERVED RESULT Kirigami apps render colored action icons (such as the ones from Oxygen) as black filled versions of what they should look like, resembling a shadow. I think it has to do with the fact that Breeze (the default icon theme) has simple, outline icons for actions. EXPECTED RESULT All actions icons should appear as their default colored selves. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel - 6.3.9-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471352] New: Discover crashes while looking for updates when OpenDesktop account is signed in
https://bugs.kde.org/show_bug.cgi?id=471352 Bug ID: 471352 Summary: Discover crashes while looking for updates when OpenDesktop account is signed in Classification: Applications Product: Discover Version: 5.27.6 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: KNewStuff Backend Assignee: plasma-b...@kde.org Reporter: lionsshark...@gmail.com CC: aleix...@kde.org, lei...@leinir.dk Target Milestone: --- SUMMARY *** Discover crashes when logged in to an OpenDesktop account in the System Settings "Online Accounts" section. Complains about "client_id" and "log_attica_plugin" *** STEPS TO REPRODUCE 1. Have OpenDesktop account logged in on System Settings > Online Accounts 2. Run Discover 3. Discover crashes while searching for updates, specifically for items from KNewStuff OBSERVED RESULT Discover uses many system resources searching for updates while complaining about an OpenDesktop account, eventually crashing just before the update check finishes. EXPECTED RESULT Discover should check for updates successfully and not complain about OpenDesktop accounts. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel - 6.3.9-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Errors I see (spammed) when running `plasma-discover` in terminal: `"client_id is missing or invalid"` `log_attica_plugin: We got an OpenDesktop account, but it seems to be lacking the id token. This means an old SignOn OAuth2 plugin was used for logging in. The plugin may have been upgraded in the meantime, but an account created using the old plugin cannot be used, and you must log out and back in again.' Regarding the second error, I had just removed and re-logged into my OpenDesktop account yesterday. My OAuth should not have expired this fast. This bug is similar to #437282 but I face a crash when launching Discover specifically toward the end of the update check. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 471276] Some newsletters format weirdly or do not load at all
https://bugs.kde.org/show_bug.cgi?id=471276 --- Comment #3 from Serena Star --- I have attached copies of each of the problematic emails so you can try it on your system -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 471276] Some newsletters format weirdly or do not load at all
https://bugs.kde.org/show_bug.cgi?id=471276 --- Comment #2 from Serena Star --- Created attachment 159796 --> https://bugs.kde.org/attachment.cgi?id=159796&action=edit TLDR Email -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 471276] Some newsletters format weirdly or do not load at all
https://bugs.kde.org/show_bug.cgi?id=471276 --- Comment #1 from Serena Star --- Created attachment 159795 --> https://bugs.kde.org/attachment.cgi?id=159795&action=edit NBC Email -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 471276] New: Some newsletters format weirdly or do not load at all
https://bugs.kde.org/show_bug.cgi?id=471276 Bug ID: 471276 Summary: Some newsletters format weirdly or do not load at all Classification: Applications Product: kmail2 Version: 5.23.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: lionsshark...@gmail.com Target Milestone: --- Created attachment 159794 --> https://bugs.kde.org/attachment.cgi?id=159794&action=edit Screenshot of NBC email selected but showing broken TLDR email instead SUMMARY *** Some email newsletters I receive such as ones from TLDR News and my local NBC news station either format weirdly or do not load. TLDR News emails appear with a white header (that includes Subject, From, To, and Date) that does not respect system font. Local NBC emails do not load when selected and show the previously viewed email instead. *** STEPS TO REPRODUCE 1. Click email from TLDR or NBC 2. Loads with weird (fallback-like) formatting for TLDR; does not load at all and shows previously selected email for NBC OBSERVED RESULT TLDR emails appear with a white background and Arial-looking font that seems to be some kind of fallback. NBC emails do not load and show the previously selected email instead. EXPECTED RESULT Both emails should show all content with proper system theming. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel - 6.3.8-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 469466] New: Scrolling on Plasma Launchers other than "Application Launcher" (Kickoff 2?) is buggy on Wayland
https://bugs.kde.org/show_bug.cgi?id=469466 Bug ID: 469466 Summary: Scrolling on Plasma Launchers other than "Application Launcher" (Kickoff 2?) is buggy on Wayland Classification: Plasma Product: plasma-wayland-protocols Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alydar...@outlook.com CC: aleix...@kde.org Target Milestone: --- Created attachment 158758 --> https://bugs.kde.org/attachment.cgi?id=158758&action=edit Screen Capture of Menu Scrolling Issues SUMMARY *** When using an app launcher other than Application Launcher 2.0 (This would include "Legacy Application Launcher" (Legacy Kickoff), "Application Dashboard", and "Application Launcher (Unibody)"), scrolling in the menus is buggy on Wayland. The scroll speed is super slow and instantly goes back to the top of the screen when the bottom of the list is reached. This does not happen on Xorg. *** STEPS TO REPRODUCE 1. Use a launcher other than "Application Launcher 2.0" 2. Scroll in a vertical menu to the bottom of the list 3. Scrolling is very slow and it will pop back to the top of the list when the bottom is reached. OBSERVED RESULT Scrolling is very slow pops back to the top of the list when the bottom is reached in launchers other than "Application Launcher 2.0" EXPECTED RESULT Scrolling should be faster and consistent to the way it works in "Application Launcher 2.0". Scrolling to the bottom of a vertical list should not send a user back to the top. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Apologies if I did not place this bug under the correct product. I have made a screen recording to show the problems I face. It is attached. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 467260] New: Amarok fails to launch, incompatible with ffmpeg 59
https://bugs.kde.org/show_bug.cgi?id=467260 Bug ID: 467260 Summary: Amarok fails to launch, incompatible with ffmpeg 59 Classification: Applications Product: amarok Version: 2.9.71 Platform: Archlinux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: alydar...@outlook.com Target Milestone: kf5 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. Launch Amarok in terminal 2. Fails to launch 3. Gives error "amarok: error while loading shared libraries: libavformat.so.59: cannot open shared object file: No such file or directory" OBSERVED RESULT Fails to start, Gives error "amarok: error while loading shared libraries: libavformat.so.59: cannot open shared object file: No such file or directory" EXPECTED RESULT Amarok launches and does not insta-crash. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Because I'm on Arch, I get Amarok from the AUR. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464964] New: Cannot expand widgets or menus beyond a certain height on the desktop
https://bugs.kde.org/show_bug.cgi?id=464964 Bug ID: 464964 Summary: Cannot expand widgets or menus beyond a certain height on the desktop Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: alydar...@outlook.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 155748 --> https://bugs.kde.org/attachment.cgi?id=155748&action=edit A video showing the bug happening. Widgets, activities, and desktop issues are shown. SUMMARY *** On my desktop, I can't expand any widgets, the Widgets menu, or the Activities menu beyond a certain height on the desktop. The desktop also does not allow selection beyond that point. *** STEPS TO REPRODUCE 1. Create widget 2. Move or expand it to the bottom of the screen 3. Hit "invisible wall" OBSERVED RESULT There is some sort of "invisible wall" that prevents some desktop elements from expanding beyond it to the bottom of the screen. EXPECTED RESULT I should be able to have desktop elements expand to my bottom panels SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux with `6.1.8-arch1-1 (64 bit)` Kernel KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION The alt-tab task switcher (which by default, appears at the left of the screen) touches the bottom of the screen, but the widgets menu and activities menu (which also appear in the same location) does not expand to the bottom of the screen. I only use one display. -- You are receiving this mail because: You are watching all bug changes.
