[kwin] [Bug 450917] [x11] kickoff and other applets are considered as "windows" in overview effect
https://bugs.kde.org/show_bug.cgi?id=450917 --- Comment #2 from alinajafia...@gmail.com --- In latest release (5.27), i can confirm the the bug has fixed successfully. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 459722] Konsole crashed during resize
https://bugs.kde.org/show_bug.cgi?id=459722 bellersenm+bugs@gmail.com changed: What|Removed |Added CC||bellersenm+bugs.kde@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 462695] Automatic DisplayPort screen dimming/sleep and system sleep stops working on Wayland
https://bugs.kde.org/show_bug.cgi?id=462695 --- Comment #42 from Paul Worrall --- *** Bug 466267 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466267] Power management not working as expected
https://bugs.kde.org/show_bug.cgi?id=466267 Paul Worrall changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Paul Worrall --- Resolved on Neon User Edition by an upgrade to the libkf5idletime5 package. A similar fix has been released on Fedora (see bug 462695). Marking as a duplicate of that bug as the fix is the same. *** This bug has been marked as a duplicate of bug 462695 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465941] Crashes when copy pasting null image
https://bugs.kde.org/show_bug.cgi?id=465941 myin changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |LATER --- Comment #6 from myin --- So what I have tested now is: - In Windows (VM): nothing happens - In another Linux machine: nothing happens I guess the normal behaviour is that nothing should happen when I paste an inherit alpha layer as a new document. Pasting in the same documents works normally. My initial guess that it might be a Linux problem doesn't seem to be the case. It only occurs on my main Linux machine. So this bug doesn't seem to be very important and is also a pretty rare use case, so I will close it for now. Thanks for looking into it though! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 465916] Valgrind crashing with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=465916 Paul Floyd changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Paul Floyd --- You should also be able to run Valgrind from your build directory with ./vg-in-place Your crash is quite early in Valgrind startup. I don't use android at all so I can't help much. Can you debug Valgrind as per the instructions in README_DEVELOPERS? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 410102] Valgrind ir sanity check failure crash
https://bugs.kde.org/show_bug.cgi?id=410102 --- Comment #6 from Paul Floyd --- (In reply to Tom Hughes from comment #5) > Reopening bug wrongly closed by KDE janitor. I think that these bugs should be closed by the janitor. We have hundreds or bugzi items that are years old, the OP never answered requests for more information. I don't think that there is any realistic chance of either getting the information from the OP or anyone else. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 465413] media controller doesn't show
https://bugs.kde.org/show_bug.cgi?id=465413 --- Comment #3 from lucid illusions --- (In reply to bart from comment #2) > There were some improvements in the media controller applet in plasma 5.27. > I don't seem to have the problem anymore myself since upgrading. If you can > upgrade, can you check whether it's also solved in plasma 5.27 for you? Interestingly, if I start Kasts - I don't see the controller, but if I start anything else in parallel say YouTube -- then I can actually see Kasts and control it as well. If I were to close Kasts and start again a. if YouTube tab is still there, then Kasts appears on media player controller b. if no other media player is running, Kasts doesn't trigger the media player controller. Device details. OS: Arch Linux x86_64 Kernel: 6.1.12-1-lts DE: Plasma 5.27.1 KDE Frameworks Version: 5.103.0 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 425445] memcheck cannot display the error line number
https://bugs.kde.org/show_bug.cgi?id=425445 Tom Hughes changed: What|Removed |Added Ever confirmed|0 |1 CC||t...@compton.nu Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #5 from Tom Hughes --- Reopening bug wrongly closed by KDE janitor. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 410102] Valgrind ir sanity check failure crash
https://bugs.kde.org/show_bug.cgi?id=410102 Tom Hughes changed: What|Removed |Added Resolution|WORKSFORME |--- CC||t...@compton.nu Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #5 from Tom Hughes --- Reopening bug wrongly closed by KDE janitor. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 133766] Would like more flexible suppression format
https://bugs.kde.org/show_bug.cgi?id=133766 Tom Hughes changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||t...@compton.nu Resolution|WORKSFORME |--- --- Comment #5 from Tom Hughes --- Reopening bug wrongly closed by KDE janitor. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 466230] The eyedropper in the colorpicker widget does not work when compositor is disabled
https://bugs.kde.org/show_bug.cgi?id=466230 Fushan Wen changed: What|Removed |Added Summary|The eyedropper in the |The eyedropper in the |colorpicker widget does not |colorpicker widget does not |work|work when compositor is ||disabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466299] Window previews for task manager icons showed the wrong colours when using the llvmpipe driver
https://bugs.kde.org/show_bug.cgi?id=466299 Fushan Wen changed: What|Removed |Added Product|plasmashell |kwin CC||qydwhotm...@gmail.com Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Target Milestone|1.0 |--- Keywords||wayland Component|Task Manager and Icons-Only |wayland-generic |Task Manager| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466231] Some games create extra Wayland window in the taskbar
https://bugs.kde.org/show_bug.cgi?id=466231 Fushan Wen changed: What|Removed |Added Keywords||wayland Product|kwin|plasmashell Component|wayland-generic |Task Manager and Icons-Only ||Task Manager Target Milestone|--- |1.0 Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466231] Some games create extra Wayland window in the taskbar
https://bugs.kde.org/show_bug.cgi?id=466231 Fushan Wen changed: What|Removed |Added CC||qydwhotm...@gmail.com --- Comment #2 from Fushan Wen --- Are they native Linux games? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 452614] Monitor Set to Portrait Reverts Back to Landscape on Reboot (Wayland).
https://bugs.kde.org/show_bug.cgi?id=452614 --- Comment #34 from mr.jwlu...@gmail.com --- (In reply to Nate Graham from comment #32) > Sorry to hear that. > > Can you paste the output of `kscreen-doctor -o` before rebooting, and > afterwards? Here is some more info. Hope it helps. Night, I go to work tomorrow to do web dev but I hope this help. https://imgur.com/a/j8Wpa9R -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 452614] Monitor Set to Portrait Reverts Back to Landscape on Reboot (Wayland).
https://bugs.kde.org/show_bug.cgi?id=452614 --- Comment #33 from mr.jwlu...@gmail.com --- (In reply to Nate Graham from comment #32) > Sorry to hear that. > > Can you paste the output of `kscreen-doctor -o` before rebooting, and > afterwards? Here you go. Before Reboot KScreen-Doctor Ouput with Screens Aligned correctly: Output: 1 DP-1 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 2560,560 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown Output: 2 DP-2 enabled connected priority 2 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 0,560 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown Output: 3 DP-3 enabled connected priority 3 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 5120,0 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown After Reboot KScreen-Doctor Ouput with Screen Miss-aligned: Output: 1 DP-1 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 2560,560 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown Output: 2 DP-2 enabled connected priority 2 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 0,560 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown Output: 3 DP-3 enabled connected priority 3 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@165* 2:2560x1440@144 3:2560x1440@120 4:2560x1440@75 5:1920x1200@60 6:1920x1080@60 7:1920x1080@60 8:1600x1200@60 9:1680x1050@60 10:1400x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1440x900@60 15:1280x960@60 16:1280x800@60 17:1152x864@60 18:1280x720@60 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:800x600@75 23:800x600@72 24:800x600@60 25:640x480@75 26:640x480@73 27:640x480@60 28:640x480@60 29:640x480@60 30:720x400@70 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 5120,0 1440x2560 Scale: 1 Rotation: 8 Overscan: 0 Vrr: Automatic RgbRange: unknown -- You are receiving this mail because:
[kate] [Bug 466321] java LSP servers can throw errors due to spaces in file URI
https://bugs.kde.org/show_bug.cgi?id=466321 Waqar Ahmed changed: What|Removed |Added Version Fixed In||23.04 Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||7857680283e3f0cf3554260e4ab ||987e7f562119a CC||waqar@gmail.com --- Comment #1 from Waqar Ahmed --- This is already fixed in master -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 465877] After plasma 5.26=>5.27 update, most KDE apps often crash when monitors enter powersaving mode.
https://bugs.kde.org/show_bug.cgi?id=465877 --- Comment #6 from Daniel Ellis --- (In reply to Daniel Ellis from comment #5) > (In reply to David Edmundson from comment #4) > > >The X11 connection broke (error 1). Did the X11 server die? > > > > Did the X11 server die? > > > > Please look for your X11 log files and coredumps > > I have gone from 100% repro yesterday to no repros today - only change was I > took 5.27.1 updates. > I will update if I get another repro. My issue appears to have actually been: https://bugs.kde.org/show_bug.cgi?id=464590 Which was fixed by: http://commits.kde.org/libkscreen/d42dea00822c1cfb7478d1d55746e0750156918b -- 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
xiota changed:
What|Removed |Added
CC||k...@mentalfossa.com
--- Comment #6 from xiota ---
Potential workaround. Edit
`{~/.local,/usr}/share/plasma/plasmoids/org.kde.activeWindowControl/contents/ui/AppMenu.qml`
with the following change:
- import org.kde.private.activeWindowControl 1.0 as
ActiveWindowControlPrivate;\
+ import org.kde.plasma.private.appmenu 1.0 as
ActiveWindowControlPrivate;\
--
You are receiving this mail because:
You are watching all bug changes.
[Active Window Control] [Bug 404359] Application menu does not show
https://bugs.kde.org/show_bug.cgi?id=404359 xiota changed: What|Removed |Added CC||k...@mentalfossa.com --- Comment #14 from xiota --- Workaround if downloading this applet with Discover. Edit `~/.local/share/plasma/plasmoids/org.kde.activeWindowControl/contents/ui/AppMenu.qml` with the following change: - import org.kde.private.activeWindowControl 1.0 as ActiveWindowControlPrivate;\ + import org.kde.plasma.private.appmenu 1.0 as ActiveWindowControlPrivate;\ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466334] When panel opacity is "adaptive", there's delay between virtual desktop switching and Task Manager updates
https://bugs.kde.org/show_bug.cgi?id=466334 --- Comment #1 from Jin Liu --- One thing to note: the panel's floating/de-floating animation doesn't create similar delay, albeit similar implementation to the opacity code. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458009] Can't right click panel after specific alt-tabs
https://bugs.kde.org/show_bug.cgi?id=458009 Jin Liu changed: What|Removed |Added CC||ad.liu@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440087] Properties sum up file sizes wrong with symlinks
https://bugs.kde.org/show_bug.cgi?id=440087 felipesco...@hotmail.com changed: What|Removed |Added CC|felipesco...@hotmail.com| -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440087] Properties sum up file sizes wrong with symlinks
https://bugs.kde.org/show_bug.cgi?id=440087 felipesco...@hotmail.com changed: What|Removed |Added CC||felipesco...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465983] Orientation of a DNG file not correct in the thumb bar
https://bugs.kde.org/show_bug.cgi?id=465983 --- Comment #5 from KaiB --- Tested with digiKam-8.0.0-beta1-20230223T182313-x86-64.appimage Confim this bug resolved. Also that the previously not-correctly oriented thumbnails are corrected with a refresh. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 466145] Spectacle uses last used delay for screenshots triggered by shortcuts
https://bugs.kde.org/show_bug.cgi?id=466145 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/spectacle/-/merge_requests/206 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466334] When panel opacity is "adaptive", there's delay between virtual desktop switching and Task Manager updates
https://bugs.kde.org/show_bug.cgi?id=466334 Jin Liu changed: What|Removed |Added Summary|When panel opacity is |When panel opacity is |"adaptive", there's delay |"adaptive", there's delay |between virtual desktop |between virtual desktop |switching and Icon manager |switching and Task Manager |updates |updates -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466334] New: When panel opacity is "adaptive", there's delay between virtual desktop switching and Icon manager updates
https://bugs.kde.org/show_bug.cgi?id=466334 Bug ID: 466334 Summary: When panel opacity is "adaptive", there's delay between virtual desktop switching and Icon manager updates Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ad.liu@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY When panel opacity is set to "adaptive", and desktop 1 has a window touching the panel (panel is opaque), desktop has no window touching the panel (panel is translucent), then when switching between these desktops, Icon Task Manager updates about PlasmaCore.Units.longDuration (200ms) later after the desktop switch. Worse, when both desktops have a window touching the panel (panel is opaque in both desktops), task manager updates about 2*PlasmaCore.Units.longDuration (400ms) later after the desktop switch. When both desktops have no window touching the panel (panel is translucent in both desktops), there's no such delay. Also, when panel opacity is set to "opaque" or "translucent", there's no such delay. STEPS TO REPRODUCE 1. Edit panel, set opacity to "adaptive". 2. Create 2 virtual desktops. 3. In desktop 1, maximize a window. 4. In desktop 2, minimize all windows. 5. Switch between desktops. Notice the delay between desktop switching and task manager updating. 6. In desktop 2, maximize a window. 7. Switch between desktops. Notice the even longer delay between desktop switching and task manager updating. 8. In both desktops, minimize all windows. 9. Switch between desktops. Notice no such delay. 10. Set panel opacity to "opaque" or "translucent". 11. Repeat step 1-9. Notice no such delay. EXPECTED RESULT Task manager updates the same time as virtual desktop switches, regardless of panel opacity setting. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION The relevent code: plasma-desktop/desktoppackage/contents/views/Panel.qml line 120, line 185 Seems that: 1. Task Manager updates after the opacity animation, thus the delay. 2. When panel is opaque in both desktops, the opacity animation somehow runs twice (although not visible), thus twice the delay. It can be fixed by letting Task Manager (and other applets) updates before the opacity animation, but I don't know how. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465941] Crashes when copy pasting null image
https://bugs.kde.org/show_bug.cgi?id=465941 Bug Janitor Service changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 446372] Changing polling time makes "Network & System" sections in the main page blank
https://bugs.kde.org/show_bug.cgi?id=446372 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 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.
[kwin] [Bug 419880] Chromium/electron app repainting bug
https://bugs.kde.org/show_bug.cgi?id=419880 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.
[kwin] [Bug 421041] KWin does not react properly when screen size is shrinked from nvidia-settings
https://bugs.kde.org/show_bug.cgi?id=421041 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[valgrind] [Bug 425445] memcheck cannot display the error line number
https://bugs.kde.org/show_bug.cgi?id=425445 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 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.
[kpat] [Bug 466229] Spider segfaulting, new solver (417bdc2ec) bug?
https://bugs.kde.org/show_bug.cgi?id=466229 --- Comment #3 from Duncan <1i5t5.dun...@cox.net> --- (In reply to Stephan Kulow from comment #2) > Hi, can you export KDE_DEBUG=1 before starting it from console? Then > something useful should appear in coredumpctl (typing from memory as I'm not > having a computer around). Kernel CONFIG_COREDUMP=n, so coredumpctl never gets the cores from the kernel. I could change that if necessary (tho would rather not deal with figuring out all that config), but what about running via gdb instead? Meanwhile , dmesg does say SolverThread SIGSEGV ... error 6 in kpat ... Currently the gdb likely isn't much help due to stripped binaries, but here's what I get ATM... A bunch of New Thread ... Thread exited pairs, apparently one per move, I guess for the solver threads. Then at the SIGSEGV... [New Thread 0x7fffd99fc6c0 (LWP 13533)] Thread 381 "SolverThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffd99fc6c0 (LWP 13533)] 0x555d762e in ?? () (gdb) bt #0 0x555d762e in ?? () #1 0x555d8546 in ?? () #2 0x555d9726 in ?? () #3 0x555da057 in ?? () #4 0x5558eab7 in ?? () #5 0x764cb05f in ?? () from /usr/lib64/libQt5Core.so.5 #6 0x75ee042d in ?? () from /usr/lib64/libc.so.6 #7 0x75f5943c in ?? () from /usr/lib64/libc.so.6 (gdb) I'll have to look up again how to build unstripped, with debugging enabled (IIRC gentoo/kde has a guide I'll need to reread, I've done it once before for something and it wasn't difficult) to fill in the ??s. Hopefully this weekend... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406918] Freeze on certain effects (NVidia)
https://bugs.kde.org/show_bug.cgi?id=406918 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #15 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.
[valgrind] [Bug 410102] Valgrind ir sanity check failure crash
https://bugs.kde.org/show_bug.cgi?id=410102 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 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.
[kwin] [Bug 418423] Firefox window titlebar black after a while
https://bugs.kde.org/show_bug.cgi?id=418423 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|DOWNSTREAM |WORKSFORME --- Comment #12 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.
[plasmashell] [Bug 465454] plasmashell crash google chrome youtube behind web proxy
https://bugs.kde.org/show_bug.cgi?id=465454 --- Comment #8 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.
[krita] [Bug 465503] Extended Display creating problem in pointer identification
https://bugs.kde.org/show_bug.cgi?id=465503 --- 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.
[valgrind] [Bug 133766] Would like more flexible suppression format
https://bugs.kde.org/show_bug.cgi?id=133766 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 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.
[plasmashell] [Bug 465442] Crashes when logging in with Wayland session. Works just fine with X11 session
https://bugs.kde.org/show_bug.cgi?id=465442 --- Comment #4 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.
[lattedock] [Bug 466333] New: Latte Dock Crashes While Removing Applications
https://bugs.kde.org/show_bug.cgi?id=466333 Bug ID: 466333 Summary: Latte Dock Crashes While Removing Applications Classification: Plasma Product: lattedock Version: 0.10.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: lotusteadra...@gmail.com Target Milestone: --- Application: latte-dock (0.10.8) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-200.fc37.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 37 (Thirty Seven)" DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: While removing an application from the Latte Dock, the dock crashed. The crash does not seem to be reproducible. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7f74cef6f588 in QWindow::parent() const () from /lib64/libQt5Gui.so.5 #5 0x7f74cef59985 in QPlatformWindow::parent() const () from /lib64/libQt5Gui.so.5 #6 0x7f74ca218542 in QXcbWindow::hide() () from /lib64/libQt5XcbQpa.so.5 #7 0x7f74cef75f07 in QWindowPrivate::setVisible(bool) () from /lib64/libQt5Gui.so.5 #8 0x5638d943c124 in Latte::Layout::GenericLayout::containmentDestroyed(QObject*) () #9 0x7f74ce8d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7f74ce8cbee3 in QObject::destroyed(QObject*) () from /lib64/libQt5Core.so.5 #11 0x7f74ce8cdc5b in QObject::~QObject() () from /lib64/libQt5Core.so.5 #12 0x7f74d0db6e1d in Plasma::Containment::~Containment() () from /lib64/libKF5Plasma.so.5 #13 0x7f74ce8c7f71 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7f74cf7aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f74ce89d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f74ce8a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #17 0x7f74ce8eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #18 0x7f74cce64cbf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #19 0x7f74cceba598 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #20 0x7f74cce61f40 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #21 0x7f74ce8ee5fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7f74ce89bf3a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7f74ce8a4002 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #24 0x5638d93fb9a4 in main () [Inferior 1 (process 146798) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466330] NeoChat Crashes at launch
https://bugs.kde.org/show_bug.cgi?id=466330 Clay Weber changed: What|Removed |Added CC||c...@claydoh.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466332] New: Clicking on a .desktop file from applications:/ opens in text editor instead of launching application
https://bugs.kde.org/show_bug.cgi?id=466332 Bug ID: 466332 Summary: Clicking on a .desktop file from applications:/ opens in text editor instead of launching application 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: shaner...@email.com Target Milestone: --- Clicking on a .desktop file from applications:/ opens in text editor instead of executing Occurs in folderview plasmoid / konqueror / dolphin STEPS TO REPRODUCE: 1. Open one of the above mentioned applications / widgets 2. Set the path to applications:/ 3. Navigate to desired application 4. Click on application OBSERVED RESULT: Desktop file is opened in text editor EXPECTED RESULT Desktop file should be executed SOFTWARE/OS VERSIONS Various *buntus, including Neon, fresh installs Linux/KDE Plasma: KDE Plasma Version: 5.25 / 5.26 / 5.27 KDE Frameworks Version: Whatever was current since 5.25 Qt Version: Whatever was current since 5.25 ADDITIONAL INFORMATION Have tried different settings under Konqueror/Dolphin->Preferences->General->Confirmations, makes no difference Tried copying older folderview plasmoid from (working) 5.24 to test, but it doesn't run correctly -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466331] New: Application Menu and Icon Only Task Manager become uninteractable after right click opening from favorites.
https://bugs.kde.org/show_bug.cgi?id=466331 Bug ID: 466331 Summary: Application Menu and Icon Only Task Manager become uninteractable after right click opening from favorites. Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: bryantc...@gmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. Open the Application Menu aka Kicker 2. Right click any application you have Favorited 3. Select any option in the right click menu that would result in opening the application OBSERVED RESULT When I try to open an application from my Favorites in the application menu via right clicking and selecting one of the various options available that would open the application an interesting bug happens. The application will open like normal, but you will no longer be able to interact with the task manager or the application menu. You CAN open the application menu via the super key, but you will be unable to interact with it in anyway. The only way to be able to interact with the menu/taskbar again is to close the application you started that way. Which will cause two different potential things to happen it will either snap to the desktop and minimize all other windows or go back randomly to one of the other windows you had open. EXPECTED RESULT Opening the application properly and being able to interact with my DE like normal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION This problem started after the 5.103 update for the Plasma Frameworks am guessing this is because of the 5.26.4 Plasma version since my Fedora 37 test system which is running Plasma version 5.27.0 and frameworks version 5.103.0 is not experiencing this issue. If I get time I will see whether I can replicate this issue on another Fedora 36 system. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466285] Click the notification popup button doesn't work
https://bugs.kde.org/show_bug.cgi?id=466285 zyf0330 changed: What|Removed |Added CC||zyf034...@gmail.com --- Comment #2 from zyf0330 --- Created attachment 156663 --> https://bugs.kde.org/attachment.cgi?id=156663=edit demo I don't think this problem is related to kdeconnect, at least part of. Please see my attachment video. I use `notify-send` to show a notification with a button. When I click button, notify-send should exit and print button, but it doesn't. And when I click notification, it blinks and hide. This problem doesn't exist when I boot into Ubuntu. But after some time, it occurs. I don't know what happened. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466330] NeoChat Crashes at launch
https://bugs.kde.org/show_bug.cgi?id=466330 Aranjedeath changed: What|Removed |Added Version|unspecified |23.01.0 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466330] New: NeoChat Crashes at launch
https://bugs.kde.org/show_bug.cgi?id=466330 Bug ID: 466330 Summary: NeoChat Crashes at launch Classification: Applications Product: NeoChat Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: orangewi...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: neochat (23.01) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.19.0-32-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: I use KDE NEON, and they released the 5.27.1 update. After that update (Tuesday this week), neochat reliably crashes on launch. Another person on IRC confirmed this behavior. [17:57:30] crashed on very first message recieved previous to this update, kde plasma 5.27.0, Neochat launched without issue. The crash can be reproduced every time. -- Backtrace: Application: NeoChat (neochat), signal: Segmentation fault [KCrash Handler] #4 QString::QString (other=..., this=, this=, other=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1093 #5 operator() (e=..., __closure=) at ./src/neochatroom.cpp:470 #6 Quotient::switchOnType, NeoChatRoom::eventToString(const Quotient::RoomEvent&, Qt::TextFormat, bool) const::, NeoChatRoom::eventToString(const Quotient::RoomEvent&, Qt::TextFormat, bool) const::, NeoChatRoom::eventToString(const Quotient::RoomEvent&, Qt::TextFormat, bool) const::, NeoChatRoom::eventToString(const Quotient::RoomEvent&, Qt::TextFormat, bool) const::, NeoChatRoom::eventToString(const Quotient::RoomEvent&, Qt::TextFormat, bool) const::, NeoChatRoom::eventToString(const Quotient::RoomEvent&, Qt::TextFormat, bool) const::, NeoChatRoom::eventToString(const Quotient::RoomEvent&, Qt::TextFormat, bool) const::, NeoChatRoom::eventToString(const Quotient::RoomEvent&, Qt::TextFormat, bool) const::, NeoChatRoom::eventToString(const Quotient::RoomEvent&, Qt::TextFormat, bool) const::, NeoChatRoom::eventToString(const Quotient::RoomEvent&, Qt::TextFormat, bool) const::, NeoChatRoom::eventToString(const Quotient::RoomEvent&, Qt::TextFormat, bool) const::, QString> (fn1=..., event=...) at /usr/include/libquotient/Quotient/events/event.h:620 #7 NeoChatRoom::eventToString(Quotient::RoomEvent const&, Qt::TextFormat, bool) const [clone .constprop.0] (this=0x5582f582fdd0, evt=..., format=Qt::RichText, removeReply=true) at ./src/neochatroom.cpp:658 #8 0x5582f102a928 in MessageEventModel::data (this=0x5582fa089480, idx=..., role=0) at ./src/models/messageeventmodel.cpp:476 #9 0x7f32ee65cb4d in QAbstractItemModel::itemData(QModelIndex const&) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x5582f102d030 in MessageEventModel::data (this=0x5582fa089480, idx=..., role=) at ./src/models/messageeventmodel.cpp:757 #11 0x7f32ee685e79 in QSortFilterProxyModel::data(QModelIndex const&, int) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x5582f1068248 in CollapseStateProxyModel::data (this=0x5582f98ff6e0, index=..., role=276) at ./src/models/collapsestateproxymodel.cpp:28 #13 0x7f32ef95b4f7 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #14 0x7f32f05a79f6 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7f32f05a8592 in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7f32f0583b05 in QV4::QQmlContextWrapper::lookupInParentContextHierarchy(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7f32f05c754c in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x7f32f05ccb9f in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #19 0x7f32f055eaee in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x7f32f06eb3a5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7f32f06f16a8 in QQmlBinding::evaluate(bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7f32f06f59db in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7f32f06f3664 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7f32f0700fca in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7f32f0696235 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7f32f069684d in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from
[kde] [Bug 466329] New: The main window display doesn't update.
https://bugs.kde.org/show_bug.cgi?id=466329 Bug ID: 466329 Summary: The main window display doesn't update. Classification: I don't know Product: kde Version: unspecified Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jeanas...@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. Opened file, working properly the previous day 2. Added reference images 3. File wouldn't update with painting or any other action OBSERVED RESULT Display didn't update, but work was updated on layer docker thumbnails EXPECTED RESULT My painting would continue to update as I paint and change layers, and it didn't. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Krita v 5.1.0, then updated to 5.1.5 with same results. Using appimage for both version. Running Linux Mint 20.3 Cinnamon (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I was able to copy/paste layers into a new file and it worked perfectly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444243] On X11, Notifications disappear below current window on click
https://bugs.kde.org/show_bug.cgi?id=444243 zyf0330 changed: What|Removed |Added Status|CONFIRMED |REPORTED Ever confirmed|1 |0 --- Comment #18 from zyf0330 --- (In reply to zyf0330 from comment #17) > Created attachment 155759 [details] > notification disappears > > I meet this problem too. It seems this problem is gone. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466328] New: crashes upon changing the view
https://bugs.kde.org/show_bug.cgi?id=466328 Bug ID: 466328 Summary: crashes upon changing the view Classification: Applications Product: NeoChat Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: ryan...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: neochat (23.01) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.15.0-60-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: When changing to see a message, and sometimes when a message comes in, neochat will crash. Not sure if this is related to #456903 (closed) Additionally, the icons for each chat are excessively large on a desktop view, something like 512x512 pixels and I don't think they look like expected. The crash can be reproduced every time. -- Backtrace: Application: NeoChat (neochat), signal: Segmentation fault [KCrash Handler] #4 0x7f1995bb29b4 in QString::operator=(QString const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x5592272f0efe in ?? () #6 0x559227296928 in ?? () #7 0x7f1995ce6e79 in QSortFilterProxyModel::data(QModelIndex const&, int) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x5592272d4248 in ?? () #9 0x7f199533f4f7 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #10 0x7f1997b979f6 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7f1997b98975 in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7f1997bb8125 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7f1997bbcb9f in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7f1997b4eaee in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7f1997cdb3a5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7f1997ce16a8 in QQmlBinding::evaluate(bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7f1997ce59db in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x7f1997ce3664 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #19 0x7f1997cf0fca in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x7f1997c86235 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7f1997c8684d in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7f1995353363 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #23 0x7f19981ac375 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #24 0x7f19981bb6ee in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #25 0x7f19981aab38 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #26 0x7f19981af13e in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #27 0x7f19981af49a in QQuickItemView::modelUpdated(QQmlChangeSet const&, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #28 0x7f1995d55108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f199532603a in QQmlInstanceModel::modelUpdated(QQmlChangeSet const&, bool) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #30 0x7f1995346e7c in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #31 0x7f199534d4c2 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #32 0x7f199534d8c8 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #33 0x7f199535905d in QQmlDelegateModel::_q_modelReset() () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #34 0x7f1995359ca3 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #35 0x7f1995d54e46 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7f1995cb6191 in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7f1995cee30a in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7f1995d55108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x7f1995cb6191 in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #40 0x7f1995cee30a in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #41 0x7f1995d55108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #42 0x7f1995cb6191 in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #43
[konsole] [Bug 466327] New: It is expected to add a function of opening more windows and executing custom commands at startup
https://bugs.kde.org/show_bug.cgi?id=466327 Bug ID: 466327 Summary: It is expected to add a function of opening more windows and executing custom commands at startup Classification: Applications Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bookmark Assignee: konsole-de...@kde.org Reporter: yhm.1...@163.com Target Milestone: --- Created attachment 156662 --> https://bugs.kde.org/attachment.cgi?id=156662=edit more windows I am a Chinese user who uses Kubuntu. In the process of using Konsole, the first thing I do when I go to the company every day is to turn on the computer, then open Konsole, and then open multiple terminal windows, and then execute in each window Some specific operations, such as the first window, I need to open my docker environment, the second window I need to perform operations into the docker container, the third window I want to switch to my local working directory, the fourth window The window I want to switch to the working directory where I work in the company, the fifth window I want to remotely link to my server through the expect script, and so on. So I expect you to add a function, which is to add a function in the settings that you can customize to open multiple windows when you start Konsole, and you can specify to execute some custom commands or scripts when each window is opened. Personally, I feel that this is a very practical function, and I really hope that you can add it, thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466287] Timers cannot have negative intervals crash on startup
https://bugs.kde.org/show_bug.cgi?id=466287 --- Comment #6 from amyspark --- Update: I tried defining locally`-no-feature-bearermanagement` to remove the affected component, since it's already deprecated in Qt5 and removed in Qt6. However, that breaks build because PyQt5 itself hard expects that component to be present to build its API. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 465996] Audio Applet "Show virtual devices" broken for newly created applets after 5.27.0
https://bugs.kde.org/show_bug.cgi?id=465996 Tom Dzmelyk changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Tom Dzmelyk --- Reproduced this on Arch Linux plasma 5.27.1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 465996] Audio Applet "Show virtual devices" broken for newly created applets after 5.27.0
https://bugs.kde.org/show_bug.cgi?id=465996 Tom Dzmelyk changed: What|Removed |Added Summary|Audio Applet ignores|Audio Applet "Show virtual |setting for virtual |devices" broken for newly |sources/sinks on 2nd screen |created applets after ||5.27.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466326] New: Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings
https://bugs.kde.org/show_bug.cgi?id=466326 Bug ID: 466326 Summary: Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings Classification: Plasma Product: kwin Version: 5.27.0 Platform: NixOS OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: brian.p.tip...@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. Hot swap monitor with a KVM like device or enabling/disabling a monitor in settings 2. 3. OBSERVED RESULT System hangs and a hard reboot is needed to get back to a working state. Sometimes can get to a TTY by CTRL-ALT-F1 EXPECTED RESULT Disabling or enabling monitors as needed SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 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.
[kwin] [Bug 449317] (SEGV) KWin Wayland crashed in KWin::Workspace::geometry when existing fullscreen in VirtualBox
https://bugs.kde.org/show_bug.cgi?id=449317 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465456] kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen
https://bugs.kde.org/show_bug.cgi?id=465456 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466120] Window Class mode invisibly includes all windows, so you can access them using the keyboard
https://bugs.kde.org/show_bug.cgi?id=466120 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367666] Add option to change wallpaper for lock screen, login screen, and desktop all at once
https://bugs.kde.org/show_bug.cgi?id=367666 --- Comment #9 from Nate Graham --- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2458 has landed for Plasma 6, which allows this from the context menu. Still need to add a config UI somewhere in System Settings or the desktop wallpaper dialog to do it too. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466325] New: No way to enable/disable apps running in the background
https://bugs.kde.org/show_bug.cgi?id=466325 Bug ID: 466325 Summary: No way to enable/disable apps running in the background Classification: Applications Product: systemsettings Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_flatpak Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com CC: joshiesuha...@gmail.com Target Milestone: --- When a flatpak app is running in the background (e.g. as a tray icon once the main window is closed) on Wayland, a notification shows up asking if the user wants to keep it running in the background or not. You can test this with Telegram or KSnip, a notification shows up once you press the X close button and it goes to the tray. If the user disallows the app from running in the background, they can easily revert this setting using Flatseal (it's one of the last options at the bottom of the page), but they cannot with the Flatpak KCM. This is particularly problematic when combined with a separate but destructive issue where applications notify they're running in the background when they're actually not (this is the case with Firefox, for instance), so the notification appears when the window is still in the foreground. Once the user disallows Firefox from running in the background, the moment they try to open it, it closes again, making it impossible to use. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 437337] When the app crashes, last-used sets of tabs is lost
https://bugs.kde.org/show_bug.cgi?id=437337 Nate Graham changed: What|Removed |Added Version Fixed In||23.04 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #27 from Nate Graham --- Not fixed by the fix for Bug 465850, in case anyone was wondering. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465850] Effective desktop size is wrong for certain scale values
https://bugs.kde.org/show_bug.cgi?id=465850 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.2 -- 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 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463135] Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 --- Comment #8 from ryan --- (In reply to Halcyoen from comment #7) > i have what i think is the same issue on kde neon. the issue appears > whenever i press ctrl+alt or ctrl+shift. after this my canvas input command > for the color sampler (alt+left click) or resizing the brush (alt+right > click) stops working. the quickest way to "unblock" my canvas inputs is by > pressing ctrl again. > > this only seems to happen in the version downloaded from the official repos > though. i do not experience this issue on windows, not with the appimage > version and not with the flatpak version. is it tied to plasma somehow? > > as for the bug where you lose input after holding alt and selecting a new > brush preset, it seems to go back quite some time. at least krita 4.2. the > OS wouldnt let me open krita 4.0 for some reason. The problem happens to me with a fresh Ubuntu install on a virtual machine. I have used Kde for roughly 3 years now, and the problem has been consistent with every version past krita 5.0.2. In 5.0.2, there appears to be some version of this bug, but like you described, the key locking disappears after a short period of time. It's annoying, but still usable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452730] Shadows around Windows are not rendered proportionally (Scale-Factor 200%+, wayland, qt)
https://bugs.kde.org/show_bug.cgi?id=452730 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.2 -- 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 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464823] Soft hyphens are incorrectly displayed as normal spaces
https://bugs.kde.org/show_bug.cgi?id=464823 --- Comment #4 from Kurt Hindenburg --- Git commit feb44c226fc6ca8e57f37a189442474e63383688 by Kurt Hindenburg, on behalf of Matan Ziv-Av. Committed on 24/02/2023 at 00:46. Pushed by hindenburg into branch 'master'. Make behaviour of characters with problematic width configurable Add a profile option to follow Unicode standard for the display width of characters, where this width differs from glibc's wcwidth. Currently the only character affected by this is soft hyphen (unicode 0x00ad). Konsole generally follows wcwidth() function when determining the display width of characters, since this is behaviour expected by libreadline, and doing otherwise corrupts lines containing problematic characters. When such characters are used more for display, then on the command line, following the Unicode standard may be prefferable. The default for this option is disabled - that is follow wcwidth(). M +6-0doc/manual/index.docbook M +8-2src/Screen.cpp M +4-0src/Screen.h M +1-0src/profile/Profile.cpp M +4-0src/profile/Profile.h M +3-1src/session/SessionManager.cpp M +1-0src/terminalDisplay/TerminalDisplay.cpp M +16 -0src/widgets/EditProfileAppearancePage.ui M +8-0src/widgets/EditProfileDialog.cpp M +1-0src/widgets/EditProfileDialog.h https://invent.kde.org/utilities/konsole/commit/feb44c226fc6ca8e57f37a189442474e63383688 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466094] Incorrect cursor rendering with screen scaling enabled
https://bugs.kde.org/show_bug.cgi?id=466094 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version Fixed In||5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466324] New: Decoration in upper leftmost corner of maximized GTK application window inaccessible
https://bugs.kde.org/show_bug.cgi?id=466324 Bug ID: 466324 Summary: Decoration in upper leftmost corner of maximized GTK application window inaccessible Classification: Plasma Product: kwin Version: 5.27.1 Platform: Neon OS: Other Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: 3f15f...@opayq.com Target Milestone: --- I have my window close decoration set to the upper left of windows. When a KDE application is maximized, the close button is accessible & works. If it is a GTK application, e.g. Firefox, VMware Workstation, etc, the button does not respond visually or functionally. The decoration just to the right of the upper leftmost works fine. For me, that's the minimize button. I have no Plasma trigger set to the upper left corner of screen. STEPS TO REPRODUCE 1. Place a close button as the leftmost decoration on windows. 2. Run a GTK app. 3. Maximize GTK app. 4. Try to click the close button. OBSERVED RESULT The button gives no visual feedback when the mouse is over or clicking the button. The button is not functional. EXPECTED RESULT The button would respond. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.27 (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics platform: Wayland ADDITIONAL INFORMATION The workaround is to restore the window & click the button. Other than this small bug, the Wayland implementation is amazing. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 466274] Album artwork does not refresh when podcast subscription originated from a sync that pulled from the server.
https://bugs.kde.org/show_bug.cgi?id=466274 --- Comment #18 from benmorde...@protonmail.com --- Created attachment 156661 --> https://bugs.kde.org/attachment.cgi?id=156661=edit workaround result -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461911] Mouse cursor can go 1 pixel beyond screen edges, which breaks Fitts' law for those screen edges and makes hover-enabled UI elements touching them flicker
https://bugs.kde.org/show_bug.cgi?id=461911 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 466274] Album artwork does not refresh when podcast subscription originated from a sync that pulled from the server.
https://bugs.kde.org/show_bug.cgi?id=466274
--- Comment #17 from benmorde...@protonmail.com ---
I found a work around.
Within FeedListDelegrate.qml, line 212
// Rounded edges
layer.enabled: false //test ben
layer.effect: OpacityMask {
maskSource: Item {
width: img.width
height: img.height
Rectangle {
anchors.centerIn: parent
width: img.adapt ? img.width : Math.min(img.width,
img.height)
height: img.adapt ? img.height : width
radius: Kirigami.Units.smallSpacing - borderWidth
}
}
}
}
Changing the line commented //test ben caused images to work again in Kasts.
Screenshot coming shortly.
--
You are receiving this mail because:
You are watching all bug changes.
[kup] [Bug 445391] Selecting a SMB network share results in "backup destination cannot be reached"
https://bugs.kde.org/show_bug.cgi?id=445391 Simon Persson changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/kup/commit/13b10dad891d2 ||81e2a0c6aac7c15211bb8dbd692 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Simon Persson --- Git commit 13b10dad891d281e2a0c6aac7c15211bb8dbd692 by Simon Persson. Committed on 24/02/2023 at 00:28. Pushed by persson into branch 'master'. Add warnings to user about problems with filesystem destination Related: bug 458327 M +50 -1kcm/backupplanwidget.cpp M +3-0kcm/backupplanwidget.h https://invent.kde.org/system/kup/commit/13b10dad891d281e2a0c6aac7c15211bb8dbd692 -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 458327] No indication that destination must exist for backup to proceed
https://bugs.kde.org/show_bug.cgi?id=458327 Simon Persson changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/kup/commit/13b10dad891d2 ||81e2a0c6aac7c15211bb8dbd692 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Simon Persson --- Git commit 13b10dad891d281e2a0c6aac7c15211bb8dbd692 by Simon Persson. Committed on 24/02/2023 at 00:28. Pushed by persson into branch 'master'. Add warnings to user about problems with filesystem destination Related: bug 445391 M +50 -1kcm/backupplanwidget.cpp M +3-0kcm/backupplanwidget.h https://invent.kde.org/system/kup/commit/13b10dad891d281e2a0c6aac7c15211bb8dbd692 -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 454773] Way to run plan from command line/cron etc.
https://bugs.kde.org/show_bug.cgi?id=454773 Simon Persson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/syst ||em/kup/commit/f4243be1af1dd ||3126f10767f4966e5936a55a2d9 --- Comment #1 from Simon Persson --- Git commit f4243be1af1dd3126f10767f4966e5936a55a2d9 by Simon Persson. Committed on 23/02/2023 at 21:55. Pushed by persson into branch 'master'. Add a public method saveNewBackup M +7-0daemon/kupdaemon.cpp M +1-0daemon/kupdaemon.h https://invent.kde.org/system/kup/commit/f4243be1af1dd3126f10767f4966e5936a55a2d9 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 466077] Filelight in a Flatpak (Flathub) can not open / and won't interact well when opened from Dolphin
https://bugs.kde.org/show_bug.cgi?id=466077 --- Comment #20 from Harald Sitter --- I wonder, I wonder. Maybe there should be an "opt-out" of sandboxing? Konsole is also supremely annoying to make reasonable as a flatpak, and so is dolphin frankly and kate. We kinda can make them work but it's all very clunky and cumbersome. In the snap world they have what's called classic mode where the snap gets access to everything, it's a portable app without confinement effectively. If flatpak could mount the actual unaltered root of the host under /host that would allow us to at least bend our app code so it transparently translates /* to /host/* under the hood thereby escaping the confinement. Though perhaps upstream has some better ideas on how to solve this. In any case, I think what we really need is something like snap's classic mode whatever the implementation details may be. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #251 from nkwkel...@gmail.com --- (In reply to Nate Graham from comment #250) > That's almost certainly a different bug, especially if you're using the > Wayland session. Update to Plasma 5.27.2 once it's released in a few days > and see if that helps. If it doesn't, please submit a new bug report. Thanks! I am using Xorg session. Will check again once 5.27.2 is out. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436667] Pinned apps with a preferred://[something] URI that resolves to nothing should be hidden
https://bugs.kde.org/show_bug.cgi?id=436667 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |d6a49375b9a5832bb77dbd794b5 |df7bc69d9f38ccd58137775019e |1ca4b08df278b |ec90db6d26dc7 Version Fixed In|5.27.1 |5.27.2 --- Comment #6 from Fushan Wen --- Git commit df7bc69d9f38ccd58137775019eec90db6d26dc7 by Fushan Wen. Committed on 24/02/2023 at 00:07. Pushed by fusionfuture into branch 'Plasma/5.27'. libtaskmanager: filter out invalid preferred launcher tasks FIXED-IN: 5.27.2 (cherry picked from commit d6a49375b9a5832bb77dbd794b51ca4b08df278b) M +6-0libtaskmanager/launchertasksmodel_p.h M +1-1libtaskmanager/tasktools.cpp https://invent.kde.org/plasma/plasma-workspace/commit/df7bc69d9f38ccd58137775019eec90db6d26dc7 -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466282] Add a live environment mode so Plasma Welcome is useful on live media
https://bugs.kde.org/show_bug.cgi?id=466282 Nate Graham changed: What|Removed |Added Summary|RFE: Add a live environment |Add a live environment mode |mode so Plasma Welcome is |so Plasma Welcome is useful |useful on live media|on live media -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466282] RFE: Add a live environment mode so Plasma Welcome is useful on live media
https://bugs.kde.org/show_bug.cgi?id=466282 --- Comment #8 from Nate Graham --- Yeah, sounds like we'll need to do that. Now onto the question of what it should display in live user mode. I guess we should have a custom page with a brief welcome to the distro as well as plasma, with a button to launch the installer, alongside a button to see the normal pages for a tour of Plasma. The app that the button launches would be controlled by a desktop file, which could also be specified in the config file (or that could be a CMake option, and then it would be unused outside of the live environment mode). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 463719] Shortcut for "OK" when using "Insert Text" annotation tool
https://bugs.kde.org/show_bug.cgi?id=463719 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Albert Astals Cid --- If you mean this https://i.imgur.com/vjFVUfb.png Alt+O ? -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466282] RFE: Add a live environment mode so Plasma Welcome is useful on live media
https://bugs.kde.org/show_bug.cgi?id=466282 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-welcome/-/merge_requests/65 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 466323] New: The KDE session crashes after I unlock it.
https://bugs.kde.org/show_bug.cgi?id=466323 Bug ID: 466323 Summary: The KDE session crashes after I unlock it. Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: sbv-comp...@mailbox.org Target Milestone: --- Application: akonadiserver (5.22.2 (22.12.2)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-zen1-1-zen x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: After an elapsed time with a locked session, KDE crashes (or seems to be crashed) after unlock the session, since all the apps that were open stop working during the unlock or before. The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x556a47da15c3 in ?? () #5 0x7f9a8dab1bb0 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #6 0x7f9a8da8df2c in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #7 0x7f9a8da8ea53 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #8 0x7f9a8dad4e88 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f9a8be6e82b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #10 0x7f9a8bec5cc9 in ?? () from /usr/lib/libglib-2.0.so.0 #11 0x7f9a8be6d0e2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #12 0x7f9a8dad8c6c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #13 0x7f9a8da866ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #14 0x7f9a8da91219 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #15 0x556a47d96f4d in ?? () #16 0x7f9a8d23c790 in ?? () from /usr/lib/libc.so.6 #17 0x7f9a8d23c84a in __libc_start_main () from /usr/lib/libc.so.6 #18 0x556a47d99cf5 in ?? () [Inferior 1 (process 1655) detached] The reporter indicates this bug may be a duplicate of or related to bug 462606. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 462749] Menus not functioning. Program is not usable.
https://bugs.kde.org/show_bug.cgi?id=462749 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #5 from Albert Astals Cid --- I wasted my time in installing Ubuntu in a VirtualMachine, all looks good here https://i.imgur.com/1u7fHQA.png If it doesn't for you i'd say it's a local configuration issue, go ask in user support forums. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466267] Power management not working as expected
https://bugs.kde.org/show_bug.cgi?id=466267 thera...@netzero.com changed: What|Removed |Added CC||thera...@netzero.com --- Comment #3 from thera...@netzero.com --- Operating System: openSUSE Tumbleweed 20230222 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-1 (64-bit) Graphics Platform: Wayland I don't find the entry about DimDisplay but I do get the message about Charge thresholds not supported whenever I make changes in powerdevil. And like the OP, Energy Saving or Suspend has no effect. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465718] Primary screen not respected by panel
https://bugs.kde.org/show_bug.cgi?id=465718 --- Comment #7 from Nate Graham --- Git commit e450f11c595718136f28e2f43df9135bbf8a8b11 by Nate Graham. Committed on 23/02/2023 at 23:28. Pushed by ngraham into branch 'master'. kcm: slightly re-word "primary screen" explanation for clarity Emphasize that it's the desktop that's bound to the monitor, and any panels in that desktop come along for the ride. The old wording could be interpreted to mean that any old panel moved along with it. M +1-1kcm/package/contents/ui/OutputPanel.qml https://invent.kde.org/plasma/kscreen/commit/e450f11c595718136f28e2f43df9135bbf8a8b11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466208] Display configuration for external display is lost after reboot (wayland)
https://bugs.kde.org/show_bug.cgi?id=466208 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #6 from Nate Graham --- (In reply to Nate Graham from comment #1) > To debug this further, can you please provide the following information? > 1. What GPU does the laptop use? > 2. Before reboot, can you verify that the internal screen is marked as > disabled in System Settings' Display and Monitor page? Or is it enabled? > 3. After reboot, can you verify that the internal screen is marked as > enabled in System Settings' Display and Monitor page? Or is it disabled? > 3. Can you attach the output of `kscreen-doctor -o` in a terminal window > before reboot, and after reboot? Can you please answer these questions? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466208] Display configuration for external display is lost after reboot (wayland)
https://bugs.kde.org/show_bug.cgi?id=466208 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DOWNSTREAM |--- --- Comment #5 from Nate Graham --- Aha, indeed that's not NVIDIA. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466282] RFE: Add a live environment mode so Plasma Welcome is useful on live media
https://bugs.kde.org/show_bug.cgi?id=466282 --- Comment #6 from Oliver Beard --- (In reply to Adam Williamson from comment #5) > No, that can't work. It has to be something that can be poked by a script > during startup, basically - some kind of config file entry, magic file, > something like that. Config would work! It could be a simple key in plasma-welcomerc, like LiveUser=true that causes the autostart helper to use a different mode. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 Nate Graham changed: What|Removed |Added CC||rondo...@gmail.com --- Comment #17 from Nate Graham --- *** Bug 466191 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466191] A few minutes after the computer is active in a KDE 5.27 session with Linux Kernel 6.2 on Manjaro, the power management settings stop working
https://bugs.kde.org/show_bug.cgi?id=466191 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #5 from Nate Graham --- Aha, the backtrace in there tells me that the crash is the same as the one in Bug 466181, which is already fixed for Plasma 5.27.2. *** This bug has been marked as a duplicate of bug 466181 *** -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466282] RFE: Add a live environment mode so Plasma Welcome is useful on live media
https://bugs.kde.org/show_bug.cgi?id=466282 --- Comment #5 from Adam Williamson --- No, that can't work. It has to be something that can be poked by a script during startup, basically - some kind of config file entry, magic file, something like that. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466282] RFE: Add a live environment mode so Plasma Welcome is useful on live media
https://bugs.kde.org/show_bug.cgi?id=466282 --- Comment #4 from Nate Graham --- If compiling the app differently in the live environment is okay, we could add a CMake flag you can compile it with that will cause the autostart helper to launch the app in live user mode, rather than welcome mode. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 452614] Monitor Set to Portrait Reverts Back to Landscape on Reboot (Wayland).
https://bugs.kde.org/show_bug.cgi?id=452614 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #32 from Nate Graham --- Sorry to hear that. Can you paste the output of `kscreen-doctor -o` before rebooting, and afterwards? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466068] Wrong ICC profile handling when moving app from one display to another
https://bugs.kde.org/show_bug.cgi?id=466068 amyspark changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #3 from amyspark --- Actually, on second thought, this is a bit more insidious... merge request incoming. It affects more than just the canvas. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465994] Memory consumption keeps increasing when a screen switched off by nvidia-settings
https://bugs.kde.org/show_bug.cgi?id=465994 Nate Graham changed: What|Removed |Added Assignee|plasma-b...@kde.org |kscreen-bugs-n...@kde.org Component|generic-performance |common Product|plasmashell |KScreen --- Comment #3 from Nate Graham --- KScreen watches for external changes, such as those done by nvidia-settings. Likely what's happening is that somehow the changes being done by nvidia-settings are triggering a condition in kscreen that never stops doing something. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 Nate Graham changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #25 from Nate Graham --- . -- You are receiving this mail because: You are watching all bug changes.
