[kwin] [Bug 466055] New: Custom tiling lacks the ability to quickly click-and-drag to resize windows
https://bugs.kde.org/show_bug.cgi?id=466055 Bug ID: 466055 Summary: Custom tiling lacks the ability to quickly click-and-drag to resize windows Classification: Plasma Product: kwin Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Custom Tiling Assignee: kwin-bugs-n...@kde.org Reporter: spamless.9v...@simplelogin.com CC: notm...@gmail.com Target Milestone: --- The older not-Aero-Snap feature has the ability to move the cursor to the edge of two windows in order to quickly resize them, however this is not true for the custom tiling feature implemented in 5.27. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 459859] KRunner erroneously executes command when user is deleting input
https://bugs.kde.org/show_bug.cgi?id=459859 --- Comment #7 from Alexander Lohnau --- @David Korth That code is only relevant for the history, like having an empty query and pressing the arrow-down key in KRunner. But I was quite confused by that too when I started working with KRunner :) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 459859] KRunner erroneously executes command when user is deleting input
https://bugs.kde.org/show_bug.cgi?id=459859 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/milou/-/merge_requests/52 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466054] New: Integrate input method panel into system tray
https://bugs.kde.org/show_bug.cgi?id=466054 Bug ID: 466054 Summary: Integrate input method panel into system tray Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Kimpanel Assignee: plasma-b...@kde.org Reporter: ryuichi.ya...@gmail.com CC: wen...@gmail.com Target Milestone: 1.0 Created attachment 156477 --> https://bugs.kde.org/attachment.cgi?id=156477=edit fcitx5-unikey is in use Currently the input method panel applet is separated from the system tray applet, and they use different spacing lengths between their icons. As the result, the margin between icons in a panel is inconsistent as shown in the attachment. I'm not sure if it's possible, but I would love to see them integrated in one applet and the icons aligned in a consistent manner. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433569] When using Header colors, color change for titlebar and window header isn't synchronized when window becomes active or inactive
https://bugs.kde.org/show_bug.cgi?id=433569 Luka Rasputin changed: What|Removed |Added CC||nanobla...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 459859] KRunner erroneously executes command when user is deleting input
https://bugs.kde.org/show_bug.cgi?id=459859 Alexander Lohnau changed: What|Removed |Added Assignee|plasma-b...@kde.org |alexander.loh...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 461823] Update notification offline on some computers
https://bugs.kde.org/show_bug.cgi?id=461823 Petr Svoboda changed: What|Removed |Added Product|neon|Discover Assignee|neon-b...@kde.org |plasma-b...@kde.org Version|unspecified |5.27.0 Platform|Other |Neon CC||aleix...@kde.org Component|general |Notifier -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 459859] KRunner erroneously executes command when user is deleting input
https://bugs.kde.org/show_bug.cgi?id=459859
David Korth changed:
What|Removed |Added
CC||gerbils...@gerbilsoft.com
--- Comment #5 from David Korth ---
Can still reproduce in 5.27.0.
In RunCommand.qml:
function runCurrentIndex(event) {
var entry = runnerManager.history[currentIndex]
if (entry) {
// If user presses Shift+Return to invoke an action, invoke the first
runner action
if (event && event.modifiers === Qt.ShiftModifier
&& currentItem.additionalActions &&
currentItem.additionalActions.length > 0) {
runAction(0);
return
}
queryField.text = entry
queryField.forceActiveFocus();
}
}
I'm not able to debug this myself (no experience with QML), but it seems like
the access to runnerManager.history[] might be blocking until something's
present in the list?
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 466053] New: Keyboard layout switch hotkeys work improperly and inconsistently with more than two layouts
https://bugs.kde.org/show_bug.cgi?id=466053 Bug ID: 466053 Summary: Keyboard layout switch hotkeys work improperly and inconsistently with more than two layouts Classification: Plasma Product: plasmashell Version: 5.24.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Keyboard Layout Assignee: plasma-b...@kde.org Reporter: lashk...@landau.ac.ru CC: butir...@gmail.com Target Milestone: 1.0 Created attachment 156476 --> https://bugs.kde.org/attachment.cgi?id=156476=edit My settings (in Russian, unfortunately). I have four layouts (English (default), Russian, Hebrew and Yiddish) with a layout loop of maximum 2 layouts. I assigned the keyboard combinations (hotkeys) for each layout (Meta+1, Meta+2, Meta+3, Meta+4 correspondingly). When I switch to Hebrew (Meta+3) or Yiddish (Meta+4) I cannot return to Russian with Meta+2. Instead, Meta+3 works as turning to Russian and Meta+4 works as turning to Hebrew from Yiddish. Meta+2 doesn't work at all. It seams that the keys are associated to the order of languages in a cycle rather that with the languages themselves. I tried to change hotkeys, but it helps nothing. In previous versions (in OpenSUSE up to 15.3) everything worked properly. My ~/.config/kxkbrc looks like: [$Version] update_info=kxkb.upd:remove-empty-lists,kxkb.upd:add-back-resetoptions,kxkb_variants.upd:split-variants [Layout] DisplayNames=,,, LayoutList=us,ru,il,yi LayoutLoopCount=2 Model=asus_laptop Options=grp:rctrl_toggle,lv3:ralt_switch_multikey ResetOldOptions=true ShowFlag=true ShowLabel=false ShowLayoutIndicator=true ShowSingle=false SwitchMode=Window Use=true VariantList=intl-unicode,ru_local,lyx,israeli STEPS TO REPRODUCE 1. Set several (n) languages in the keyboard layouts configuration. 2. Set layout loop to mm with the corresponding hotkey. 5. Try to switch to any language number l<=m with the corresponding hotkey. OBSERVED RESULT Nothing happens or the language is switched randomly. EXPECTED RESULT The language is switched to the language l. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE 15.4 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I use slightly modified xkb rules and symbol settings to adjust my habits with the Russian keyboard and to use the Yiddish keyboard. It has never caused any problems. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 465814] Ctrl+Tab order should be separate per split view
https://bugs.kde.org/show_bug.cgi?id=465814 --- Comment #4 from Grósz Dániel --- (In reply to Waqar Ahmed from comment #3) > We have decided to keep the behaviour for now. See linked MR: > https://invent.kde.org/utilities/kate/-/merge_requests/1113 Regarding the comments there (not sure if I should respond here or there): I didn't propose changing the Documents sidebar at all (I like its current behavior of opening any file you click in the focused split), only the Ctrl+Tab behavior. VSCode has tabs, and Ctrl+Tab works like I proposed (separate orders, and only showing the tabs in the current split view). Qt Creator doesn't have a concept of which files are open in a given split view, but the Ctrl+Tab order is per-split there too. Visiting a file in one split doesn't bring it forward in the Ctrl+Tab order of another split. KDevelop, OTOH, works like Kate currently; there, the equivalent of my proposal is a confirmed request since 2013: Bug 323218. Eclipse seems to behave rather differently, such that views can be arranged in many ways, and it seems to have a single Ctrl+Tab order, but it will switch to a different (split) view if necessary, rather than open a file in the current view. In LyX (not a plain text editor, but also has tabs and splits), Ctrl+Tab switches in the order tabs are on the tab bar, per-split, rather than in the order they have been last used. (Kate has different shortcuts for this by default.) However, I was wrong that the current Kate Ctrl+Tab behavior started last year: I built 21.12 and it also worked like this. I guess I thought it started with 22.04 because the most noticeable effect—Ctrl+Tab reopening a tab I just closed with Ctrl+W—didn't happen until then because closing a tab closed it everywhere. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 466052] New: Define global configurable default formatting settings for such things as dates, thousands and decimal separators, etc.
https://bugs.kde.org/show_bug.cgi?id=466052 Bug ID: 466052 Summary: Define global configurable default formatting settings for such things as dates, thousands and decimal separators, etc. Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- SUMMARY *** It is annoying to always get an error when creating new import profile when the typical US date format of M-D-Y in CSV files is at odds with the program default Y-M-D Can the format settings that are typically region dependent be added to the Settings/Configure KMM dialog someplace? Keeping the ability to override the default is fine, but it would be much friendlier to have a programmable default. *** SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 466051] New: focus lost when typing in Indicator boxes when creating import profile
https://bugs.kde.org/show_bug.cgi?id=466051 Bug ID: 466051 Summary: focus lost when typing in Indicator boxes when creating import profile Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- Created attachment 156475 --> https://bugs.kde.org/attachment.cgi?id=156475=edit screenshot of issue SUMMARY *** When configuring a new CSV Profile, Focus is lost when typing in the 'Indicator for Credit/Debit' boxes after typing each character. Cursor moves to the top left field of the input file and typed characters replace that content. *** STEPS TO REPRODUCE 1. create a new input profile for a CSV file 2. start typing a new keyword in the 'Indicator for Credit' or 'Indicator for Debit' entry boxes (noticed in the Amount tab) OBSERVED RESULT notice that the first character is correctly displayed and further characters appear in the row 1 column 1 input file EXPECTED RESULT all characters typed show up in the box in which they are typed SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 456713] plasma-kded.service hangs for around a minute or more on system shutdown
https://bugs.kde.org/show_bug.cgi?id=456713 RM changed: What|Removed |Added CC||r...@richardmay.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 RM changed: What|Removed |Added CC||r...@richardmay.net -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465987] Power Module (power devil or whatever) won't start at all with latest plasma.
https://bugs.kde.org/show_bug.cgi?id=465987 Vasiliy Glazov changed: What|Removed |Added CC||vasc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 401725] Cannot display menu on certain applictaions (e.g. LyX, Kate)
https://bugs.kde.org/show_bug.cgi?id=401725 --- Comment #5 from Litao Lu --- (In reply to Justin Zobel from comment #2) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! Sorry for the late reply, I still can reproduce this issue ``` ~ $ LANG=C pacman -Si plasma5-applets-active-window-control Repository : community Name: plasma5-applets-active-window-control Version : 1.7.3-3 Operating System: Arch Linux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: OMEN by HP Laptop 16-c0xxx ``` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465973] Display distorts when switching to 5120x1440 resolution
https://bugs.kde.org/show_bug.cgi?id=465973 --- Comment #1 from adavila89+...@protonmail.com --- Created attachment 156474 --> https://bugs.kde.org/attachment.cgi?id=156474=edit Picture of what the display renders -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457049] Global hotkeys are not working when Chrome/Chromium PWA window is focused on wayland
https://bugs.kde.org/show_bug.cgi?id=457049 --- Comment #6 from Oded Arbel --- Upstream bug seems to have been fixed? I haven't verified yet. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457565] Multiscreen: Window's shadow and outline bleed over when window is maximized or tiled to an edge adjacent to another screen
https://bugs.kde.org/show_bug.cgi?id=457565 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466050] Triggering selection mode by accident
https://bugs.kde.org/show_bug.cgi?id=466050 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466050] New: Triggering selection mode by accident
https://bugs.kde.org/show_bug.cgi?id=466050 Bug ID: 466050 Summary: Triggering selection mode by accident Classification: Applications Product: dolphin Version: 22.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Selection Mode Assignee: kfm-de...@kde.org Reporter: r...@rekurs.io CC: felixer...@kde.org Target Milestone: --- SUMMARY While I'm sure this feature is great for touchscreen users, as a heavy keyboard user I find myself triggering selection mode exclusively by accident. The thing is, why would I ever want to use selection mode if I'm not limited to touch controls? On a keyboard it's more or less worthless and even with a mouse, ctrl/shift + left click and right click for actions works fine. Some possible solutions come to mind. A. Add an option to fully disable selection mode. B. Do not trigger selection mode with keyboard. It could still be triggered with mouse or touch. C. Put selection mode on some shortcut that won't be constantly hit by accident. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431304] Plasma Crash after login
https://bugs.kde.org/show_bug.cgi?id=431304 1625b8e2-65c6-4d45-8747-c9f9f9896...@01392.anonaddy.me changed: What|Removed |Added Platform|Fedora RPMs |Gentoo Packages Status|RESOLVED|REPORTED Resolution|DOWNSTREAM |--- CC||1625b8e2-65c6-4d45-8747-c9f ||9f9896...@01392.anonaddy.me --- Comment #2 from 1625b8e2-65c6-4d45-8747-c9f9f9896...@01392.anonaddy.me --- crashed on startup, nothing accessible, can't even open terminal, only able to get here by clicking on the link in the crash reporter -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463651] PNG support for HDR clamps the dynamic range to SDR
https://bugs.kde.org/show_bug.cgi?id=463651 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[calligrastage] [Bug 291535] Calligra start up dialog too small
https://bugs.kde.org/show_bug.cgi?id=291535 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 462265] Plasma NetworkManager doesn't apply IPv6 configuration to OpenVPN
https://bugs.kde.org/show_bug.cgi?id=462265 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 456865] Long event changes overlap with other events
https://bugs.kde.org/show_bug.cgi?id=456865 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461288] Next scheduled loan due date changes to wrong date
https://bugs.kde.org/show_bug.cgi?id=461288 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 466044] Default project filters should include .github directory
https://bugs.kde.org/show_bug.cgi?id=466044 --- Comment #1 from Alex Lowe --- I've made a merge request to fix this: https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/443 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 466049] Selection color has low contrast with some transparent backgrounds
https://bugs.kde.org/show_bug.cgi?id=466049 Lucas changed: What|Removed |Added Version|unspecified |22.12.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 466049] New: Selection color has low contrast with some transparent backgrounds
https://bugs.kde.org/show_bug.cgi?id=466049 Bug ID: 466049 Summary: Selection color has low contrast with some transparent backgrounds Classification: Applications Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: l...@hotmail.com.br Target Milestone: --- Created attachment 156473 --> https://bugs.kde.org/attachment.cgi?id=156473=edit low contrast selection STEPS TO REPRODUCE 1. Set breeze color scheme 2. Set blur on and transparency to 20% 3. Put the window above a white surface OBSERVED RESULT Selection is invisible EXPECTED RESULT Selection is visible SOFTWARE/OS VERSIONS Linux/KDE Plasma KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466048] New: [Regression] Bismuth tiling manager does not detect windows on Wayland
https://bugs.kde.org/show_bug.cgi?id=466048 Bug ID: 466048 Summary: [Regression] Bismuth tiling manager does not detect windows on Wayland Classification: Plasma Product: kwin Version: git master Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: cd+kde@terminal.space Target Milestone: --- SUMMARY As of Plasma 5.27, the Bismuth Tiling addon (https://github.com/Bismuth-Forge/bismuth/issues/473) does not detect windows properly on wayland. It only sporadically detects when windows are opened, and it never detects when windows are closed. Therefore these windows don't get tiled. Note that X11 still works properly STEPS TO REPRODUCE 1. Tried on both 5.27 and git master 2. Install the KDE bismuth addon 3. Enable the addon in settings 4. Logout/login just to be safe 5. Open and close applications (such as dolphin, system settings etc). OBSERVED RESULT Bismuth does not detect the presence of the windows EXPECTED RESULT Windows are tiled or untiled as appropriate SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466047] UI: Text, Icons, Install/Remove buttons projecting out of their app's card boxes in Home tab and search results
https://bugs.kde.org/show_bug.cgi?id=466047 --- Comment #1 from Himprakash Deka --- Created attachment 156472 --> https://bugs.kde.org/attachment.cgi?id=156472=edit Search Result: Look at the heading text of each app touching top border and the Install/Remove button protruding out through the bottom border in default Breeze theme -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466047] New: UI: Text, Icons, Install/Remove buttons projecting out of their app's card boxes in Home tab and search results
https://bugs.kde.org/show_bug.cgi?id=466047 Bug ID: 466047 Summary: UI: Text, Icons, Install/Remove buttons projecting out of their app's card boxes in Home tab and search results Classification: Applications Product: Discover Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: himpraka...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 156471 --> https://bugs.kde.org/attachment.cgi?id=156471=edit Icons, text or both projecting out of card boxes of several apps specifically GIMP, GCompris, KMyMoney, Kdenlive, SuperTux, 0 A.D. etc. SUMMARY *** Just updated to Plasma 5.27 and noticed this. Look at the attached screenshot. *** STEPS TO REPRODUCE 1. Just open Discover and go to Home tab OBSERVED RESULT In Home tab, Icons, text or both are projecting out through the bottom border of their app's card boxes for several apps specifically GIMP, GCompris, KMyMoney, Kdenlive, SuperTux, 0 A.D. etc and icons touching the bottom border for several others. In search results, Install/Remove buttons projecting out through the bottom border of their app's card boxes for all apps. In Breeze Application style, text even touches the top border. EXPECTED RESULT Icons should be resized to fit in the vertical center and excess text should be replaced by "…" Install/Remove buttons should be padded from the bottom border. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Not using scaling and display is in native resolution. Also happening in default Breeze Icon theme for some apps. Search result problem most severe in Breeze application style. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407289] KDEConnect crashes upon trying to 'Add storage location' from 'Filesystem expose settings'
https://bugs.kde.org/show_bug.cgi?id=407289 --- Comment #16 from Himprakash Deka --- As pointed out by @nastyagrifon, it was due to a package named "com.google.android.documentsui" being uninstalled or disabled. This package is the file/folder chooser used by KDE Connect and many other apps. This bug can be reproduced by uninstalling or disabling that package. After restoring or installing that package though, the bug is solved. However, KDE Connect should still not crash and instead ask the user which app to use for choosing the folder or at least show an error message that the package is not present. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466046] New: Multiple Monitors with matching names cannot be told apart under Display Configuration applet.
https://bugs.kde.org/show_bug.cgi?id=466046 Bug ID: 466046 Summary: Multiple Monitors with matching names cannot be told apart under Display Configuration applet. Classification: Plasma Product: KScreen Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Plasma Applet Assignee: kscreen-bugs-n...@kde.org Reporter: km...@tuta.io Target Milestone: --- Created attachment 156470 --> https://bugs.kde.org/attachment.cgi?id=156470=edit My three MSI Optix G24C monitors, all easily confused for one another. SUMMARY I have three identical monitors, but the only thing in the display configurator that actually produces a physically different name under Display Configuration is the "Identify" button that brings up the OSD, only because the OSD displays the physical DisplayPort plug next to the name. It wasn't really an issue before, but in 5.27, with the new Display Priorities menu, that replaced the Primary Monitor button, to actually set my display priorities, I now need to do some guesswork as to which monitor is which. STEPS TO REPRODUCE 1. Have two or more matching monitors, or monitors that otherwise report the same name in software 2. Open Display Configuration menu 3. Attempt to interpret which monitor is which, especially in the Priorities menu. OBSERVED RESULT All monitors are indistinguishable due to having the same name. EXPECTED RESULT Appended numbers when name match detected, or Port ID, displayed after name. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (EndeavourOS) KDE Plasma Version: 5.27.0 KDE Frameworks Version 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 452552] Add report format with full entry details per page
https://bugs.kde.org/show_bug.cgi?id=452552 Robby Stephenson changed: What|Removed |Added Version Fixed In||3.5 Latest Commit||https://invent.kde.org/offi ||ce/tellico/commit/426ded342 ||d12a6c153a6e80ade9bc31b33ce ||19c8 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Robby Stephenson --- Git commit 426ded342d12a6c153a6e80ade9bc31b33ce19c8 by Robby Stephenson. Committed on 19/02/2023 at 02:21. Pushed by rstephenson into branch 'master'. Add new report template showing one entry per page. Use the configured entry template. Extract the contents and concatenate with page separation. FIXED-IN: 3.5 M +4-0ChangeLog M +77 -9src/reportdialog.cpp M +2-0src/reportdialog.h M +3-0src/translators/htmlexporter.cpp M +2-0src/translators/htmlexporter.h https://invent.kde.org/office/tellico/commit/426ded342d12a6c153a6e80ade9bc31b33ce19c8 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466045] New: NeoChat crashed at Quotient::Room::connection() when entering a room
https://bugs.kde.org/show_bug.cgi?id=466045
Bug ID: 466045
Summary: NeoChat crashed at Quotient::Room::connection() when
entering a room
Classification: Applications
Product: NeoChat
Version: unspecified
Platform: openSUSE
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: General
Assignee: fe...@posteo.de
Reporter: qydwhotm...@gmail.com
CC: c...@carlschwan.eu
Target Milestone: ---
Application: neochat (23.03.70)
Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.1.10-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.80 [KCrashBackend]
-- Information about the crash:
When I clicked a room in the list, NeoChat crashed.
The crash can be reproduced sometimes.
-- Backtrace:
Application: NeoChat (neochat), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 Quotient::Room::connection() const (this=0x0) at
/usr/src/debug/libQuotient-0.6.11/lib/room.cpp:2263
#7 0x7f7588142589 in Quotient::Room::user(QString const&) const
(this=, userId=...) at
/usr/src/debug/libQuotient-0.6.11/lib/room.cpp:619
#8 0x7f7588149777 in Quotient::Room::roomMembername(QString const&) const
(this=this@entry=0x0, userId=...) at
/usr/src/debug/libQuotient-0.6.11/lib/room.cpp:1520
#9 0x7f75881497e4 in Quotient::Room::safeMemberName(QString const&) const
(this=this@entry=0x0, userId=...) at
/usr/src/debug/libQuotient-0.6.11/lib/room.cpp:1527
#10 0x5607bed473fb in UserListModel::findUserPos(Quotient::User*) const
(this=this@entry=0x5607c31c6ff0, user=user@entry=0x5607c514eb00) at
/usr/src/debug/neochat-1.0.80git.20230215T182251~f186be7/src/models/userlistmodel.cpp:215
#11 0x5607bed49d0d in UserListModel::refresh(Quotient::User*, QVector
const&) (this=this@entry=0x5607c31c6ff0, user=user@entry=0x5607c514eb00,
roles=...) at
/usr/src/debug/neochat-1.0.80git.20230215T182251~f186be7/src/models/userlistmodel.cpp:170
#12 0x5607bed49f25 in UserListModel::avatarChanged(Quotient::User*,
Quotient::Room const*) (context=, user=0x5607c514eb00,
this=0x5607c31c6ff0) at
/usr/src/debug/neochat-1.0.80git.20230215T182251~f186be7/src/models/userlistmodel.cpp:209
#13 UserListModel::avatarChanged(Quotient::User*, Quotient::Room const*)
(this=0x5607c31c6ff0, user=0x5607c514eb00, context=) at
/usr/src/debug/neochat-1.0.80git.20230215T182251~f186be7/src/models/userlistmodel.cpp:206
#14 0x7f758611338d in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffcb66f9730, r=0x5607c31c6ff0, this=0x5607c792c570) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#15 doActivate(QObject*, int, void**) (sender=0x5607c514eb00,
signal_index=5, argv=0x7ffcb66f9730) at kernel/qobject.cpp:3923
#16 0x7f758610c80f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7f75881f4140,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcb66f9730)
at kernel/qobject.cpp:3983
#17 0x7f7588118997 in Quotient::User::avatarChanged(Quotient::User*,
Quotient::Room const*) (this=, _t1=,
_t2=) at
/usr/src/debug/libQuotient-0.6.11/build/Quotient_autogen/ZJOKMXDKB7/moc_user.cpp:361
#18 0x7f758611338d in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffcb66f9830, r=0x5607c514eb00, this=0x5607cee55c70) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#19 doActivate(QObject*, int, void**) (sender=0x5607ceb31780,
signal_index=10, argv=0x7ffcb66f9830) at kernel/qobject.cpp:3923
#20 0x7f758610c80f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7f75881f4340,
local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffcb66f9830)
at kernel/qobject.cpp:3983
#21 0x7f7588117522 in Quotient::BaseJob::success(Quotient::BaseJob*)
(this=, _t1=) at
/usr/src/debug/libQuotient-0.6.11/build/Quotient_autogen/3INUWTIJ2C/moc_basejob.cpp:542
#22 0x7f758817ff49 in Quotient::BaseJob::finishJob() (this=0x5607ceb31780)
at /usr/src/debug/libQuotient-0.6.11/lib/jobs/basejob.cpp:646
#23 0x7f758611338d in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffcb66f9970, r=0x5607ceb31780, this=0x5607ca780c00) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#24 doActivate(QObject*, int, void**) (sender=0x5607cadffa20,
signal_index=10, argv=0x7ffcb66f9970) at kernel/qobject.cpp:3923
#25 0x7f758610c80f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x5607cadffa20, m=m@entry=0x7f7587730320
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3983
#26 0x7f75876cfd73 in QNetworkReply::finished()
(this=this@entry=0x5607cadffa20) at .moc/moc_qnetworkreply.cpp:404
#27
[kdevelop] [Bug 466044] New: Default project filters should include .github directory
https://bugs.kde.org/show_bug.cgi?id=466044 Bug ID: 466044 Summary: Default project filters should include .github directory Classification: Applications Product: kdevelop Version: 5.10.221202 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: file tree Assignee: kdevelop-bugs-n...@kde.org Reporter: len...@gmail.com Target Milestone: --- Created attachment 156469 --> https://bugs.kde.org/attachment.cgi?id=156469=edit Project filter configuration with the requested filter SUMMARY By default, the project view's filters exclude all hidden files with some specific overrides such as `.travis.yml` and `.gitlab-ci.yml`. It would be nice if a default project filter included `.github*` for both files and folders so github configuration and CI files are similarly accessible. STEPS TO REPRODUCE 1. Clone a git repository that uses GitHub workflows (e.g. https://github.com/charliermarsh/ruff) 2. Open the project in KDevelop OBSERVED RESULT .github directory is available EXPECTED RESULT .github directory is not SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION The requested filter is shown in the attached screenshot -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 156947] KHTML in KDE 4 fails Acid3 test
https://bugs.kde.org/show_bug.cgi?id=156947 Alex Lowe changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #9 from Aleksey Kontsevich --- (In reply to Nate Graham from comment #8) > If you can reproduce it, please get a backtrace and file a new bug report. After cache cleaning it sometimes crashes but now it restarts immediately after the crash so it is less annoying. However crash reporter does not appear now, so I can't report the stack. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466043] Editing messages is broken
https://bugs.kde.org/show_bug.cgi?id=466043 --- Comment #1 from Nicolas Fella --- Created attachment 156468 --> https://bugs.kde.org/attachment.cgi?id=156468=edit Video -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466043] New: Editing messages is broken
https://bugs.kde.org/show_bug.cgi?id=466043 Bug ID: 466043 Summary: Editing messages is broken Classification: Applications Product: NeoChat Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: nicolas.fe...@gmx.de CC: c...@carlschwan.eu Target Milestone: --- When editing a message, either by pressing the up arrow key or the edit button on hover the message text disappears and two buttons are shown in the message bubble. The message can't be edited See screen recording. Neochat commit 79a9eb0de0b81eaec211bd42cad9188060c5f05d -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433969] Unable to add ufw firewall rules with port ranges
https://bugs.kde.org/show_bug.cgi?id=433969 Paulo Marcos changed: What|Removed |Added CC||contato-myghi63@protonmail. ||com --- Comment #4 from Paulo Marcos --- I'm also having the same limitation with plasma-firewall 5.27.0-1 (Arch Linux) It's the same problem on both firewalld and ufw. I wanted to open 1714:1764 ports through plasma-firewall, but ended up doing that via CLI. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #24 from Matt Keith --- Also to add, I am running fedora 37 kde spin with the 5.27 release of kde plasma under wayland -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #23 from Matt Keith --- (In reply to Nick from comment #21) > I'm not sure if this is exactly the right issue, but I seem to be > experiencing something like this ever since upgrading from Fedora KDE 36 to > Fedora KDE 37. > I have an Asus XG27AQ at 144hz using DisplayPort, and an Asus VS239 at 60hz > using HDMI. Both are plugged in to a 6700XT. > > The last version of KDE on Fedora KDE 36 was 5.25.5, and my monitors would > stay asleep as expected. > After upgrading to Fedora KDE 37 which brought KDE 5.26.3, as long as both > monitors are powered on, they immediately wake up after entering sleep. > If I turn off the HDMI monitor, the DisplayPort monitor stays asleep. If I > turn off the DisplayPort monitor, the HDMI monitor wakes up after entering > sleep. > This persisted with 5.26.4, and at the moment with 5.26.5. > > On Wayland in all instances. Disabling kscreen2 doesn't help. > At the end of Fedora KDE 36, I had kernel 6.0.7. Fedora KDE 37 brought that > to 6.0.8. I'm now on 6.1.6. I am experiencing this issue as well I have a framework laptop with the display open. a radeon rx5700 connected by a razer chroma egpu enclosure. A monitor connected to the video card by the display port. The computer locks when idle but both the laptop and the monitor stay on all night. =/ Are there any logs I could attach that might be relevant and useful? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466042] Crash when opening file
https://bugs.kde.org/show_bug.cgi?id=466042 --- Comment #1 from Nicolas Fella --- This seems to happen when running kate with any non-existent file -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466042] New: Crash when opening file
https://bugs.kde.org/show_bug.cgi?id=466042
Bug ID: 466042
Summary: Crash when opening file
Classification: Applications
Product: kate
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: nicolas.fe...@gmx.de
Target Milestone: ---
Application: kate (23.03.70)
(Compiled from sources)
Qt Version: 5.15.7
Frameworks Version: 5.104.0
Operating System: Linux 6.1.11-200.fc37.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 37 (KDE Plasma)
DrKonqi: 5.27.80 [KCrashBackend]
-- Information about the crash:
In the korganizer source folder run "kate
prefs/koprefsdialoggroupscheduling.cpp:40"
The crash can be reproduced every time.
-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 0x7f4937918284 in QStandardItem::rowCount (this=0x36ca240) at
itemmodels/qstandarditemmodel.cpp:1595
#6 0x7f490816ef0e in KateProject::registerUntrackedDocument
(this=0x3a43ff0, document=0x388d940) at
/home/nico/kde/src/kate/addons/project/kateproject.cpp:546
#7 0x7f490816eb7d in KateProject::registerDocument (this=0x3a43ff0,
document=0x388d940) at
/home/nico/kde/src/kate/addons/project/kateproject.cpp:522
#8 0x7f49081558a3 in KateProjectPlugin::slotDocumentUrlChanged
(this=0xccfdd0, document=0x388d940) at
/home/nico/kde/src/kate/addons/project/kateprojectplugin.cpp:297
#9 0x7f490815e3dd in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(KateProjectPlugin::*)(KTextEditor::Document*)>::call (f=(void
(KateProjectPlugin::*)(KateProjectPlugin * const, KTextEditor::Document *))
0x7f4908155810
,
o=0xccfdd0, arg=0x7ffdd1f11bf0) at
/home/nico/kde/usr/include/QtCore/qobjectdefs_impl.h:152
#10 0x7f490815d707 in QtPrivate::FunctionPointer::call,
void> (f=(void (KateProjectPlugin::*)(KateProjectPlugin * const,
KTextEditor::Document *)) 0x7f4908155810
,
o=0xccfdd0, arg=0x7ffdd1f11bf0) at
/home/nico/kde/usr/include/QtCore/qobjectdefs_impl.h:185
#11 0x7f490815c629 in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x393b7b0,
r=0xccfdd0, a=0x7ffdd1f11bf0, ret=0x0) at
/home/nico/kde/usr/include/QtCore/qobjectdefs_impl.h:418
#12 0x7f49370e7ac2 in QtPrivate::QSlotObjectBase::call (a=0x7ffdd1f11bf0,
r=0xccfdd0, this=0x393b7b0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x388d940, signal_index=14, argv=0x7ffdd1f11bf0)
at kernel/qobject.cpp:3923
#14 0x7f49398c026b in KTextEditor::Document::documentUrlChanged
(this=0x388d940, _t1=0x388d940) at
/home/nico/kde/build/ktexteditor/src/KF5TextEditor_autogen/OGSBNZGFXN/moc_document.cpp:527
#15 0x7f4939986652 in KTextEditor::DocumentPrivate::slotUrlChanged
(this=0x388d940, url=...) at
/home/nico/kde/src/ktexteditor/src/document/katedocument.cpp:6087
#16 0x7f49399a1ec9 in QtPrivate::FunctorCall,
QtPrivate::List, void, void (KTextEditor::DocumentPrivate::*)(QUrl
const&)>::call (f=(void
(KTextEditor::DocumentPrivate::*)(KTextEditor::DocumentPrivate * const, const
QUrl &)) 0x7f4939986614 , o=0x388d940, arg=0x7ffdd1f11db0) at
/home/nico/kde/usr/include/QtCore/qobjectdefs_impl.h:152
#17 0x7f493999fa0b in QtPrivate::FunctionPointer::call, void> (f=(void
(KTextEditor::DocumentPrivate::*)(KTextEditor::DocumentPrivate * const, const
QUrl &)) 0x7f4939986614 , o=0x388d940, arg=0x7ffdd1f11db0) at
/home/nico/kde/usr/include/QtCore/qobjectdefs_impl.h:185
#18 0x7f493999b099 in QtPrivate::QSlotObject,
void>::impl (which=1, this_=0x3f60800, r=0x388d940, a=0x7ffdd1f11db0, ret=0x0)
at /home/nico/kde/usr/include/QtCore/qobjectdefs_impl.h:418
#19 0x7f49370e7ac2 in QtPrivate::QSlotObjectBase::call (a=0x7ffdd1f11db0,
r=0x388d940, this=0x3f60800) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#20 doActivate (sender=0x388d940, signal_index=10, argv=0x7ffdd1f11db0)
at kernel/qobject.cpp:3923
#21 0x7f493a19bdcf in KParts::ReadOnlyPart::urlChanged (this=0x388d940,
_t1=...) at
/home/nico/kde/build/kparts/src/KF5Parts_autogen/include/moc_readonlypart.cpp:268
#22 0x7f493a19a1a5 in KParts::ReadOnlyPart::setUrl (this=0x388d940,
url=...) at /home/nico/kde/src/kparts/src/readonlypart.cpp:60
#23 0x7f493a19a4bd in KParts::ReadOnlyPart::openUrl (this=0x388d940,
url=...) at /home/nico/kde/src/kparts/src/readonlypart.cpp:139
#24 0x7f49399747a2 in KTextEditor::DocumentPrivate::openUrl
(this=0x388d940, url=...) at
/home/nico/kde/src/ktexteditor/src/document/katedocument.cpp:2828
#25 0x7f4939ebd5ab in KateDocManager::openUrl (this=0x7ffdd1f12de0,
url=..., encoding=..., docInfo=...) at
/home/nico/kde/src/kate/apps/lib/katedocmanager.cpp:174
#26 0x7f4939ebd486 in KateDocManager::openUrls
[Powerdevil] [Bug 348529] When screen is locked, turn off screen with a shorter timeout
https://bugs.kde.org/show_bug.cgi?id=348529 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465338] Minor Text Display Issue
https://bugs.kde.org/show_bug.cgi?id=465338 --- Comment #5 from Fred --- (In reply to Rob from comment #4) > Ok this build should include fixes for both the QML rendering bug displayed > here and the port selector not showing up bug. > > www.indilib.org/jdownloads/kstars/beta/kstars-3.6.3.dmg > > Please try it out and let me know if it fixes it. Hi Rob - responded over on the INDI forum as well but things look good and it appears that all the text and information is now displaying correctly! Thanks for your work on this! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449105] Dragging a window that was opened maximized moves the mouse cursor to the top left corner of the window
https://bugs.kde.org/show_bug.cgi?id=449105 --- Comment #15 from ghoste --- (In reply to Alessandro Astone from comment #14) > After living a long time with this bug assuming it'd eventually be fixed I > finally decided to take look it up on the bug tracker... and to my surprise > it does not have a lot of attention? > It's been happening forever on all my machines, where display scaling, gtk > vs qt, multiple monitors vs single monitor, all don't matter. I can assume > everyone is affected. > Super annoying. I would argue this a 15-minute bug. I'm running 5.27 and it's still an issue. It's not functionality breaking but you do notice it quickly and it's quite annoying. I'm seeing it right now when opening new Firefox windows. It's happened on every system I've tried including Intel, AMD, NVIDIA Graphics, Virtualbox too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466029] Big icons in task switcher when previews are disabled can get blurry, despite qualitative enough icons available
https://bugs.kde.org/show_bug.cgi?id=466029 Porkepix changed: What|Removed |Added Summary|Big icons in task switcher |Big icons in task switcher |when previews are disabled |when previews are disabled |get be blurry, despite |can get blurry, despite |qualitative enough icons|qualitative enough icons |available |available -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466036] kded5 crash after resume from blank
https://bugs.kde.org/show_bug.cgi?id=466036 Nicolas Fella changed: What|Removed |Added Product|kded-appmenu|KScreen Component|Titlebar menu button/popup |common Assignee|plasma-b...@kde.org |kscreen-bugs-n...@kde.org CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466041] New: Data must be copied twice before being pasted on Wayland when history size is set to 1 entry
https://bugs.kde.org/show_bug.cgi?id=466041 Bug ID: 466041 Summary: Data must be copied twice before being pasted on Wayland when history size is set to 1 entry Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: aut...@cyfox.net Target Milestone: 1.0 SUMMARY When running a Plasma Wayland session with the clipboard configured to have a history size of only one entry, text and images can't be pasted after being copied unless the last thing copied was identical. STEPS TO REPRODUCE 1. Start a Plasma Wayland session. 2. Configure Clipboard and set "History size" to 1 entry. 3. Copy text or an image once. 4. Try to paste it one or more times. 5. Copy the same text or image again. 6. Try to paste it one or more times. OBSERVED RESULT Nothing is pasted until the same text or image has been copied twice in a row. Clicking the clipboard applet shows whatever was copied, but pasting doesn't work. EXPECTED RESULT The text or image that was copied is pasted every time. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION This bug doesn't happen on X11, and it doesn't happen when the history size is two or more. It happens regardless of how the data is copied (Ctrl+C, context menu, "copy to clipboard" button, or wl-copy). I've only tested with text and images. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 465763] The installation folder can not be changed
https://bugs.kde.org/show_bug.cgi?id=465763 Ivan Čukić changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] resizing a window leads to malformed decoration under Aurorae
https://bugs.kde.org/show_bug.cgi?id=465790 k...@arbi.in changed: What|Removed |Added CC||k...@arbi.in --- Comment #7 from k...@arbi.in --- Created attachment 156467 --> https://bugs.kde.org/attachment.cgi?id=156467=edit Composite of 3 stages of window resizing, demonstrating bug I am also observing this behavior intermittently/unpredictably after updating to 5.27.0. Thus far, it has been triggered inconsistently and only by unlocking my session. *Sometimes* unlocking my session will trigger this on open windows. Not all windows are affected. Non-exhaustively: Dolphin, Spectacle, system settings have never been affected. Firefox (wayland mode), Konsole, Spotify, Signal desktop have all been affected at least once. If I can collect more information on how to trigger this, I will update. Resizing the window when it is in this state appears to rescale the window decorations by a multiple of the change in window size, if that makes sense. As though (forgive my psuedo-code for the sake of expressing the idea): window_decoration_sz = window_sz * unknown_constant. Attached (with an extremely professional "window relative scale measurement image" included) is a set of 3 images taken immediately after unlocking my system; the first is without any resizing, the second is with a small amount of resizing (1 "mm"), the third is after the same amount (1 "mm") of resizing. If I grow the window from its baseline instead of shrinking it, the decorations expand outside the right edge of the drawable area and are clipped. Also confirming that switching themes fixes it for all windows. Closing & re-opening affected windows entirely also corrects the issue for only that window. Minimizing and restoring the window does not resolve the issue, nor does maximizing and restoring. Operating System: Arch Linux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen Threadripper 1900X 8-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Display scale: 100% Window decoration theme: Reactionary I can't tell if this happens with other themes like Breeze, because it's difficult to reproduce the issue on-demand and switching themes corrects it immediately. I will be keeping an eye on my system as this happens to determine if there's a more consistent way to reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 466040] New: Konversation dumps core on exit
https://bugs.kde.org/show_bug.cgi?id=466040 Bug ID: 466040 Summary: Konversation dumps core on exit Classification: Applications Product: konversation Version: 1.9.22122 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: leguen.yann...@gmail.com Target Milestone: --- Created attachment 156466 --> https://bugs.kde.org/attachment.cgi?id=156466=edit Backtrace SUMMARY *** Konversation works normally but dumps core on exit. I use a Wayland session, I haven't tried on X11. *** STEPS TO REPRODUCE 1. Start Konversation and use it. 2. Quit Konversation. 3. Konversation doesn't terminate gracefully and dumps core (as shown by coredumpctl). SOFTWARE/OS VERSIONS Linux: Archlinux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449105] Dragging a window that was opened maximized moves the mouse cursor to the top left corner of the window
https://bugs.kde.org/show_bug.cgi?id=449105 Alessandro Astone changed: What|Removed |Added CC||ales.ast...@gmail.com --- Comment #14 from Alessandro Astone --- After living a long time with this bug assuming it'd eventually be fixed I finally decided to take look it up on the bug tracker... and to my surprise it does not have a lot of attention? It's been happening forever on all my machines, where display scaling, gtk vs qt, multiple monitors vs single monitor, all don't matter. I can assume everyone is affected. Super annoying. I would argue this a 15-minute bug. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 259917] the simulate option cannot be selected and the 'remove image' option is greyed out
https://bugs.kde.org/show_bug.cgi?id=259917 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||aa...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #9 from Albert Astals Cid --- What about the OP? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 259917] the simulate option cannot be selected and the 'remove image' option is greyed out
https://bugs.kde.org/show_bug.cgi?id=259917 Albert Astals Cid changed: What|Removed |Added CC|terauck-...@yahoo.com.au| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461911] Mouse cursor can go 1 pixel beyond screen edges
https://bugs.kde.org/show_bug.cgi?id=461911 Alessandro Astone changed: What|Removed |Added CC||ales.ast...@gmail.com --- Comment #10 from Alessandro Astone --- Can reproduce on Wayland with default 100% scaling. It happens on the right and bottom edges. Plasma 5.27.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465829] The plasma panel will redraw the top boarder on top of any maximised application when it is set to "Windows can cover". The panel will also display additional boarder line w
https://bugs.kde.org/show_bug.cgi?id=465829 --- Comment #4 from Bill --- (In reply to Nate Graham from comment #2) > Is the line blue? Hi Nate, It is not blue. Colour of the line seems to change based on the accent colour. I have attached the screenshot in an attempt to show what border line? outline? I mentioned in the bug report. Please let me know if you need any more information. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 466039] Newly created keyboard shortcut wrongly considered ambiguous
https://bugs.kde.org/show_bug.cgi?id=466039 --- Comment #2 from Bernd --- Created attachment 156465 --> https://bugs.kde.org/attachment.cgi?id=156465=edit Search for 'snap' -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 466039] Newly created keyboard shortcut wrongly considered ambiguous
https://bugs.kde.org/show_bug.cgi?id=466039 --- Comment #1 from Bernd --- Created attachment 156464 --> https://bugs.kde.org/attachment.cgi?id=156464=edit Search for Alt+M -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 466039] New: Newly created keyboard shortcut wrongly considered ambiguous
https://bugs.kde.org/show_bug.cgi?id=466039 Bug ID: 466039 Summary: Newly created keyboard shortcut wrongly considered ambiguous Classification: Applications Product: kdenlive Version: 22.12.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: bern...@yahoo.com Target Milestone: --- Created attachment 156463 --> https://bugs.kde.org/attachment.cgi?id=156463=edit Error message SUMMARY A newly created keyboard shortcut for turning snap on and off is considered ambiguous and not executed while creating it didn't trigger a warning and searching for the same shortcut shows only one assignment (see screenshots) STEPS TO REPRODUCE 1. Open Settings > Configure Keyboard Shortcuts 2. Search for Snap and assign new keyboard shortcut (e.g. Alt+M) 3. Hit Alt+M (sometimes first hit doesn't do anything and error message comes up when used a second time) OBSERVED RESULT Error message about shortcut being ambiguous EXPECTED RESULT Snap feature turned off or on SOFTWARE/OS VERSIONS Linux: Pop!_OS 22.04 LTS (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.102. Qt Version: 5.15.8 (built against 5.15.8) ADDITIONAL INFORMATION Using appimage -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465829] The plasma panel will redraw the top boarder on top of any maximised application when it is set to "Windows can cover". The panel will also display additional boarder line w
https://bugs.kde.org/show_bug.cgi?id=465829 --- Comment #3 from Bill --- Created attachment 156462 --> https://bugs.kde.org/attachment.cgi?id=156462=edit If you look at right at the top of the panel It shows the line I mentioned which shows up when watching full screen videos in browser. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464804] "Meta" key is rendered incorrectly when using modifier only shortcuts
https://bugs.kde.org/show_bug.cgi?id=464804 Patrick Silva changed: What|Removed |Added CC||natalie_clar...@yahoo.de --- Comment #4 from Patrick Silva --- *** Bug 465968 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465968] Setting meta as shortcut key shows weird symbols
https://bugs.kde.org/show_bug.cgi?id=465968 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 464804 *** -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 466038] New: wayland: file open dialog using portal does not show the selection
https://bugs.kde.org/show_bug.cgi?id=466038 Bug ID: 466038 Summary: wayland: file open dialog using portal does not show the selection Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.27.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: slartibar...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- Use the env.Var GTK_USE_PORTAL=1 and start firefox or chromium-freeworld, then open a file with Ctrl-O. The open-file Portal dialog comes up. Problems: - the current selection is not highlighted any more (this can be fixed by resizing the dialog) - hovering with the mouse over a file shows the correct preview - use the cursor keys to move the selection (this is still working, that is, i see the selected file in the 'name' input field: no visible selection is shown in the file list, and if you move way to the bottom, so that the list-pane needs to scroll, you get garbled content (it still scrolls somehow) For now, this dialog is unusable. If i start firefox like this: GTK_USE_PORTAL=0 firefox the 'native' file-open dialog works ok. I cannot run GTK_USE_PORTAL=0 chromium-freeworld though, this always uses portal Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 31,1 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 System Version: ThinkPad T470p -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 465071] Content rating: text is cut off when it's too big
https://bugs.kde.org/show_bug.cgi?id=465071 viniciusdaros2...@gmail.com changed: What|Removed |Added CC||viniciusdaros2...@gmail.com --- Comment #1 from viniciusdaros2...@gmail.com --- Created attachment 156461 --> https://bugs.kde.org/attachment.cgi?id=156461=edit print from the discover with cripped text -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 466036] kded5 crash after resume from blank
https://bugs.kde.org/show_bug.cgi?id=466036 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 259917] the simulate option cannot be selected and the 'remove image' option is greyed out
https://bugs.kde.org/show_bug.cgi?id=259917 North changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 259917] the simulate option cannot be selected and the 'remove image' option is greyed out
https://bugs.kde.org/show_bug.cgi?id=259917 --- Comment #8 from North --- Reported -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466037] New: sudden shift of unselected elements while the program were on and I was switching on/off some layers
https://bugs.kde.org/show_bug.cgi?id=466037 Bug ID: 466037 Summary: sudden shift of unselected elements while the program were on and I was switching on/off some layers Classification: I don't know Product: kde Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: stefaniaerre...@gmail.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. turn on layer 2. the layer with the drawing and other layers are modified without im not doing anything but on/off layers 3. opened other layers in the same group, and the ending was the same 4. I cried. OBSERVED RESULT The drawing on three different layer, that were in the same group layer with other layers that haven't been modificated, has been modificated without any action i did, just I opened notes on the pc and writed and a part of the drawing on different layers seemed to be selected and moved. This bug happened in a few seconds while I was turning on/off some layers in that group EXPECTED RESULT The drawing should have stayed the same SOFTWARE/OS VERSIONS Windows: 10 Pro Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I showed the drawings a second ago, and nothing appened, then i just tried to switch on a layer, an that was randomly moved, and the autosave saved the drawing as it was, with the problem. I created the account after the bug, so there isn't the history Sorry for my clumsy english, I come from Italy -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466035] Multi monitor setup crashes when monitors are (hard) powered off
https://bugs.kde.org/show_bug.cgi?id=466035 --- Comment #1 from Richard --- Short update: It crashes only if the primary monitor is hard powered off. Powering off the secondary monitor does nothing. (tested with both) -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 466036] New: kded5 crash after resume from blank
https://bugs.kde.org/show_bug.cgi?id=466036 Bug ID: 466036 Summary: kded5 crash after resume from blank Classification: Plasma Product: kded-appmenu Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Titlebar menu button/popup Assignee: plasma-b...@kde.org Reporter: dxq7...@gmail.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 *** kded5 crash after resume from blank ``` Application: kded5 (kded5), signal: Segmentation fault [KCrash Handler] #4 0x7f49d62ad270 in KScreen::Output::id() const () from /lib64/libKF5Screen.so.8 #5 0x7f49d62a01f8 in KScreen::Config::setOutputPriority(QSharedPointer const&, unsigned int) () from /lib64/libKF5Screen.so.8 #6 0x7f49d62a9ca2 in KScreen::SetConfigOperation::start() () from /lib64/libKF5Screen.so.8 #7 0x7f4a11907d00 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #8 0x7f4a127a544e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #9 0x7f4a118dc1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #10 0x7f4a118df181 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #11 0x7f4a11934413 in ?? () from /lib64/libQt5Core.so.5 #12 0x7f4a1051ba90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #13 0x7f4a1051be48 in ?? () from /lib64/libglib-2.0.so.0 #14 0x7f4a1051bedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #15 0x7f4a11933c16 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #16 0x7f4a118dac5b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7f4a118e2dc6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #18 0x55f59658b976 in ?? () #19 0x7f4a1102caf0 in __libc_start_call_main () from /lib64/libc.so.6 #20 0x7f4a1102cbb9 in __libc_start_main_impl () from /lib64/libc.so.6 #21 0x55f59658bb75 in ?? () [Inferior 1 (process 2368) detached] ``` STEPS TO REPRODUCE 1. settings -> power management -> display off after 1 minute 2. resume display after the screen black 3. get kded5 crash error, tray icon not working and maybe others OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: archlinux/opensuse tumbleweed (available in About System) KDE Plasma Version:plasma 5.27.0 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.
[KScreen] [Bug 466035] Multi monitor setup crashes when monitors are (hard) powered off
https://bugs.kde.org/show_bug.cgi?id=466035 Richard changed: What|Removed |Added CC||rs...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466035] Multi monitor setup crashes when monitors are (hard) powered off
https://bugs.kde.org/show_bug.cgi?id=466035 Richard changed: What|Removed |Added Summary|Multi monitors setup|Multi monitor setup crashes |crashes when monitors are |when monitors are (hard) |(hard) powered off |powered off -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466035] New: Multi monitors setup crashes when monitors are (hard) powered off
https://bugs.kde.org/show_bug.cgi?id=466035 Bug ID: 466035 Summary: Multi monitors setup crashes when monitors are (hard) powered off Classification: Plasma Product: KScreen Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: OSD Assignee: kscreen-bugs-n...@kde.org Reporter: rs...@mailbox.org Target Milestone: --- Created attachment 156460 --> https://bugs.kde.org/attachment.cgi?id=156460=edit Journal output SUMMARY I have a dual monitor setup (4k primary + FHD). Both monitors are connected to a power strip with a switch. When I turn them off and on again, KDE disables the primary 4k monitor and only the FHD monitor is active. The other monitor goes black and only the mouse is visible. (This does not happen when I switch off the monitors using the power button.) When I press CTL+ALT to switch to the console, both monitors are reactivated, but only in console mode. When I restart sddm in this mode, sddm is displayed correctly on both monitors. When I log in, the primary 4k monitor is disabled and the desktop launches on the FHD monitor. When I try to enable the 4k monitor via the KDE display manager, nothing happens, or the monitor is enabled and KDE crashes, then reverts back to the FHD monitor. When I reboot, nothing changes. If I start the nvidia x server settings and enable the 4k monitor, it works again. This bug appeared last year. Affected versions are definitely 5.27, 5.26 and 5.25. There are probably more affected versions, but I cannot remember which version broke it. It worked fine in the past. The issue appeared with Neon 20.04 and stayed with 22.04. The only clue I have is that the German translation of the display manager utility was missing after the update when the bug first appeared. I have attached the journal log between the point where I turn off the monitors, turn them back on and log in via console to save the log. STEPS TO REPRODUCE 1. Hard power off the monitors 2. Turn them on again OBSERVED RESULT Primary 4k monitor gets disabled Secondary FHD monitor becomes primary EXPECTED RESULT Monitor setup restored SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-32-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: AX370-Gaming 5 Nvidia driver: 510.47.03-0ubuntu1 ADDITIONAL INFORMATION xrandr output when it is working: Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767 DVI-D-0 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 510mm x 290mm 1920x1080 60.00*+ 1680x1050 59.95 1600x900 60.00 1440x900 59.89 1400x1050 59.98 1280x1024 75.0260.02 1280x800 59.81 1280x720 60.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.3256.25 640x480 75.0059.94 HDMI-0 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm 3840x2160 60.00*+ 30.00 1920x1080 60.0059.94 1600x900 60.00 1280x1024 60.02 1280x800 59.81 1280x720 60.0059.94 1152x864 59.96 1024x768 60.00 800x600 60.32 720x480 59.94 640x480 59.9459.93 DP-3 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 433460] When logging into a Wayland session after having previously used the X11 session, all outputs have their scales reset to 100%
https://bugs.kde.org/show_bug.cgi?id=433460 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415364] Setting to disable when mouse is plugged in is missing when using Libinput driver
https://bugs.kde.org/show_bug.cgi?id=415364 Patrick Silva changed: What|Removed |Added CC||volody...@teleport.dp.ua --- Comment #14 from Patrick Silva --- *** Bug 465991 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465991] No autodisable touchpad function when connecting a mouse
https://bugs.kde.org/show_bug.cgi?id=465991 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 415364 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 464340] Rendu crashed
https://bugs.kde.org/show_bug.cgi?id=464340 --- Comment #3 from jean --- Bonjour l'équipe , sur vos conseil , j'ai téléchargé la version 2.12.1 , le rendu est un peu long , mais crash quand même , voici le commentaire : Rendering of C:/Users/Jean/Videos/KDEnlive Dossier NE RIEN JETER/Dossier Anniv Damien/Anniv Damien 1.vob crashed [mp3 @ 01fef314ccc0] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef314d700] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef314ccc0] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef33c4280] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef33c4280] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef33dcd80] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef33c4280] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef33ac480] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef4303d40] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef7c60d00] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef4303d40] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef7c60d00] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef4303d40] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef7c60d00] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef4543680] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef4303d40] Estimating duration from bitrate, this may be inaccurate [dvd @ 01fef2a79500] VBV buffer size not set, using default size of 230KB If you want the mpeg file to be compliant to some specification Like DVD, VCD or others, make sure you set the correct buffer size [dvd @ 01fef2a79500] buffer underflow st=0 bufi=2011 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=2011 size=47284 Current Frame: 9, percentage: 0 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=4035 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=6059 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=8083 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=10107 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=12131 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=14155 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=16179 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=18203 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=20227 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=22251 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=24275 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=26299 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=28323 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=30347 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=32371 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=34395 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=36419 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=38443 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=40467 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=42491 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=44515 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=46539 size=47284 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=1269 size=11864 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=3293 size=11864 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=5317 size=11864 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=7341 size=11864 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=9365 size=11864 [dvd @ 01fef2a79500] buffer underflow st=0 bufi=11389 size=11864 Current Frame: 11, percentage: 0 [mp3 @ 01fef4de7b00] Estimating duration from bitrate, this may be inaccurate [mp3 @ 01fef4de6fc0] Estimating duration from bitrate, this may be inaccurate Current Frame: 53, percentage: 0 [h264 @ 01fef4d5e9c0] Missing reference picture, default is 2147483647 [h264 @ 01fef4d5e9c0] Missing reference picture, default is 2147483647 [h264 @ 01fef4d5f580] Missing reference picture, default is 2147483647 [h264 @ 01fef4d5f580] Missing reference picture, default is 2147483647 [h264 @ 01fef4d5f980] Missing reference picture, default is 2147483647 [h264 @ 01fef4d5e9c0] Missing reference picture, default is 0 [h264 @ 01fef4d5e9c0] decode_slice_header error [h264 @ 01fef4d5f580] Missing reference picture, default is 0 [h264 @ 01fef4d5f580] decode_slice_header error [h264 @ 01fef4d5f980] Missing reference picture, default is 0 [h264 @ 01fef4d5f980] decode_slice_header error [h264 @ 01fef4d5fd80] Missing reference picture, default is 65562 Current Frame:
[kwin] [Bug 460404] [Regression]: Kwin 5.26.0 uses software renderer instead of GLX
https://bugs.kde.org/show_bug.cgi?id=460404 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463272] Gap between panel and tooltips of the task manager
https://bugs.kde.org/show_bug.cgi?id=463272 Patrick Silva changed: What|Removed |Added CC||tima...@proton.me --- Comment #2 from Patrick Silva --- *** Bug 466010 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466010] Task Bar Window Preview Position Breaks on Windows with Player Controls
https://bugs.kde.org/show_bug.cgi?id=466010 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 463272 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464132] One pixel overlap when enabling screen
https://bugs.kde.org/show_bug.cgi?id=464132 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466029] Big icons in task switcher when previews are disabled get be blurry, despite qualitative enough icons available
https://bugs.kde.org/show_bug.cgi?id=466029 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 205241] Snow Leopard 10.6 support
https://bugs.kde.org/show_bug.cgi?id=205241 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #93 from Paul Floyd --- Snow Leopard is too old. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 252919] Bogus error about invalid Mach-O file for i386 files on SnowLeopard
https://bugs.kde.org/show_bug.cgi?id=252919 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED CC||pjfl...@wanadoo.fr --- Comment #2 from Paul Floyd --- The oldest mac I can access is 10.7 so I'm closing this. -- You are receiving this mail because: You are watching all bug changes.
[kubrick] [Bug 466034] New: Wrong color pallete
https://bugs.kde.org/show_bug.cgi?id=466034 Bug ID: 466034 Summary: Wrong color pallete Classification: Applications Product: kubrick Version: 1.1.221190 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: iandw...@gmail.com Reporter: blendy...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY *** Default color pallete isn't correct (according to the most common color distribution for cubes) *** STEPS TO REPRODUCE 1. Open Kubrick OBSERVED RESULT Color pallete is wrong (white next to yellow) EXPECTED RESULT Collor pallete is not wrong SOFTWARE/OS VERSIONS Linux: 6.1.9-arch1-1 X11 | 64bit KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.18.8 ADDITIONAL INFORMATION Also wrong in screenshots (in discover) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] line glitches with 125% and 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=465158 Martin Polden changed: What|Removed |Added CC||mpol...@mpolden.no -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management sometimes stops working
https://bugs.kde.org/show_bug.cgi?id=462695 Martin Polden changed: What|Removed |Added CC||mpol...@mpolden.no -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 465814] Ctrl+Tab order should be separate per split view
https://bugs.kde.org/show_bug.cgi?id=465814 Waqar Ahmed changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||waqar@gmail.com Status|ASSIGNED|RESOLVED --- Comment #3 from Waqar Ahmed --- We have decided to keep the behaviour for now. See linked MR: https://invent.kde.org/utilities/kate/-/merge_requests/1113 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466033] New: Monitor doesn't get signal after wake up
https://bugs.kde.org/show_bug.cgi?id=466033 Bug ID: 466033 Summary: Monitor doesn't get signal after wake up Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mmarrerole...@gmail.com Target Milestone: --- My monitor doesn't get signal after wake up. Only after I kill de X server (Ctrl + Alt + Backspace) it get signal back again. STEPS TO REPRODUCE 1. Sleep PC. 2. Turn off monitor. 3. Wake up PC. 4. Turn on monitor. OBSERVED RESULT Monitor doesn't get signal EXPECTED RESULT Monitor get signal SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-32-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i3-8100 CPU @ 3.60GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B22 System Version: 2.0 ADDITIONAL INFORMATION I'd tried unplug and plug back again the monitor, to all the graphic outputs and even the motherboard output, but it doesn't solved the issue. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management sometimes stops working
https://bugs.kde.org/show_bug.cgi?id=462695 slartibar...@gmail.com changed: What|Removed |Added CC||slartibar...@gmail.com --- Comment #19 from slartibar...@gmail.com --- same here, wayland with plasma 5.27.0 on fedora 37 Setting screen-dim to 1 minute, sreen energy saving to 2 min and waiting: - after 1 min, neither laptop screen nor the display-port attached 2nd 4k monitor are getting dim (in x11, only the laptop was dimmed, not the dp-attached monitor) - after 2 min, no poweroff of laptop nor dp-attached screen. - sometime later, the screen-lock comes active. I found no combination of settings that really turn off both displays as they did in 5.26.x Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 31,1 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 Manufacturer: LENOVO -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 465491] Interval schedules: save backup asap after missed schedule time
https://bugs.kde.org/show_bug.cgi?id=465491 Simon Persson changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Summary|Kup on daily interval |Interval schedules: save |schedule - no backup after |backup asap after missed |suspend |schedule time --- Comment #4 from Simon Persson --- OK, excellent. Then it actually behaves as designed then. I agree that saving a new backup as soon as possible after a missed schedule would be good to have, and users would be right to expect it. For anyone who has time and interest to help fix this problem: The current scheduler goes to sleep with a duration which is the remaining time until next "backup save time". The solution here could be to instead just sleep 5 minutes and then upon wake up, check if it's time to save a new backup. If not, go back to sleep for another five minutes. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 466032] New: Konsole crashed while dragging
https://bugs.kde.org/show_bug.cgi?id=466032 Bug ID: 466032 Summary: Konsole crashed while dragging Classification: Applications Product: konsole Version: 22.12.2 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: citra...@protonmail.com Target Milestone: --- Application: konsole (22.12.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-arch1-1 x86_64 Windowing System: X11 Distribution: EndeavourOS DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: I was dragging the Konsole window with several tabs open. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 0x7f4bfc0a08ec in ?? () from /usr/lib/libc.so.6 #5 0x7f4bfc051ea8 in raise () from /usr/lib/libc.so.6 #6 0x7f4bfc03b53d in abort () from /usr/lib/libc.so.6 #7 0x7f4bfc2d30e2 in std::__glibcxx_assert_fail (file=, line=, function=, condition=) at /usr/src/debug/gcc/gcc/libstdc++-v3/src/c++11/debug.cc:60 #8 0x7f4bfddd79e0 in Konsole::Screen::setSelectionEnd(int, int, bool) () from /usr/lib/libkonsoleprivate.so.1 #9 0x7f4bfde34c1b in Konsole::TerminalDisplay::extendSelection(QPoint const&) () from /usr/lib/libkonsoleprivate.so.1 #10 0x7f4bfde399e8 in Konsole::TerminalDisplay::mouseMoveEvent(QMouseEvent*) () from /usr/lib/libkonsoleprivate.so.1 #11 0x7f4bfd5af80f in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x7f4bfd578b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #13 0x7f4bfd57e379 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7f4bfc88df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #15 0x7f4bfd57c377 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f4bfd5cd505 in ?? () from /usr/lib/libQt5Widgets.so.5 #17 0x7f4bfd5cf2ae in ?? () from /usr/lib/libQt5Widgets.so.5 #18 0x7f4bfd578b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #19 0x7f4bfc88df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #20 0x7f4bfcd3efbc in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #21 0x7f4bfcd28885 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #22 0x7f4bf632e8d0 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #23 0x7f4bfac6e82b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0x7f4bfacc5cc9 in ?? () from /usr/lib/libglib-2.0.so.0 #25 0x7f4bfac6d0e2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0x7f4bfc8d8c6c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #27 0x7f4bfc8866ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #28 0x7f4bfc891219 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #29 0x55f7f38d6b65 in ?? () #30 0x7f4bfc03c790 in ?? () from /usr/lib/libc.so.6 #31 0x7f4bfc03c84a in __libc_start_main () from /usr/lib/libc.so.6 #32 0x55f7f38d7425 in ?? () [Inferior 1 (process 7007) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
