[Ruqola] [Bug 481400] Login using Personal Access Token
https://bugs.kde.org/show_bug.cgi?id=481400 --- Comment #2 from Laurent Montel --- Can you create PAT in your server ? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 480919] KStars 369 can't open in macOS Big Sure
https://bugs.kde.org/show_bug.cgi?id=480919 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||mutla...@ikarustech.com --- Comment #1 from Jasem Mutlaq --- Minimum requirements for macOS is now Sonoma. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 463624] Search generates crash
https://bugs.kde.org/show_bug.cgi?id=463624 Jasem Mutlaq changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470256] Multi-modifier Modifier-only shortcuts
https://bugs.kde.org/show_bug.cgi?id=470256 --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kguiaddons/-/merge_requests/115 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480998] In KDE Neon testing external monitor with a capability of 120 hz displays only 60 when trying to set 120.
https://bugs.kde.org/show_bug.cgi?id=480998 --- Comment #5 from Nikolay --- (In reply to Zamundaaa from comment #3) > Okay. Could you try again with KWIN_DRM_PREFER_COLOR_DEPTH=24 in > /etc/environment ? Internal monitor works without bugs when I switch from 165 gz to 96 or less -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480998] In KDE Neon testing external monitor with a capability of 120 hz displays only 60 when trying to set 120.
https://bugs.kde.org/show_bug.cgi?id=480998 --- Comment #4 from Nikolay --- (In reply to Zamundaaa from comment #3) > Okay. Could you try again with KWIN_DRM_PREFER_COLOR_DEPTH=24 in > /etc/environment ? Thanks! It works, my external monitor is now working correctly at 120 Hz, but the internal monitor still displays graphical errors when I switch virtual desktops or the dock at the bottom changes its position -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 481565] New: The konsole closes unexpectedly
https://bugs.kde.org/show_bug.cgi?id=481565 Bug ID: 481565 Summary: The konsole closes unexpectedly Classification: Applications Product: konsole Version: 23.08.1 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: mbaru...@gmail.com Target Milestone: --- Created attachment 165949 --> https://bugs.kde.org/attachment.cgi?id=165949=edit crash log SUMMARY *** The konsole closes unexpectedly *** STEPS TO REPRODUCE 1. Open the console in the morning 2. Come back the next morning 3. Console closed OBSERVED RESULT Console closed EXPECTED RESULT The console continues to work SOFTWARE/OS VERSIONS PRETTY_NAME="Ubuntu 23.10" NAME="Ubuntu" VERSION_ID="23.10" VERSION="23.10 (Mantic Minotaur)" VERSION_CODENAME=mantic ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=mantic LOGO=ubuntu-logo 6.5.0-17-generic ADDITIONAL INFORMATION /var/log/syslog 2024-02-20T09:26:43.343691+03:00 max-note plasmashell[194427]: Unable to find file for pid 8340 expected at "kcrash-metadata/8340.ini" 2024-02-20T09:26:43.345512+03:00 max-note kwin_x11[2900]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 52456, resource id: 79691860, major code: 18 (ChangeProperty), minor code: 0 2024-02-20T09:26:43.360962+03:00 max-note plasmashell[8340]: QSocketNotifier: Invalid socket 12 and type 'Read', disabling... 2024-02-20T09:26:43.361171+03:00 max-note plasmashell[8340]: QSocketNotifier: Invalid socket 14 and type 'Read', disabling... 2024-02-20T09:26:43.361516+03:00 max-note kded5[2897]: Service ":1.135" unregistered 2024-02-20T09:26:44.369449+03:00 max-note plasmashell[8340]: Unable to start Dr. Konqi 2024-02-20T09:26:44.369555+03:00 max-note plasmashell[8340]: Re-raising signal for core dump handling. 2024-02-20T09:26:45.511232+03:00 max-note systemd[1]: Started whoopsie.service - crash report submission. 2024-02-20T09:26:45.520982+03:00 max-note whoopsie[561349]: [09:26:45] Using lock path: /var/lock/whoopsie/lock 2024-02-20T09:26:45.523224+03:00 max-note systemd[1]: whoopsie.service: Deactivated successfully. 2024-02-20T09:26:45.950199+03:00 max-note kded5[2897]: "/var/crash" 2024-02-20T09:26:45.950380+03:00 max-note kded5[2897]: running "/usr/share/kubuntu-notification-helper/whoopsie-upload-all" 2024-02-20T09:26:45.967753+03:00 max-note kded5[561360]: kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' 2024-02-20T09:26:45.968625+03:00 max-note kded5[561360]: kdeinit5: Launched KLauncher, pid = 561361, result = 0 2024-02-20T09:26:46.090841+03:00 max-note kded5[561361]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) 2024-02-20T09:26:46.091475+03:00 max-note kded5[561360]: kdeinit5: opened connection to :0 2024-02-20T09:26:46.105380+03:00 max-note kded5[561360]: kdeinit5: Got EXEC_NEW '/usr/share/kubuntu-notification-helper/whoopsie-upload-all' from launcher. 2024-02-20T09:26:46.105501+03:00 max-note kded5[561360]: kdeinit5: preparing to launch '/usr/share/kubuntu-notification-helper/whoopsie-upload-all' 2024-02-20T09:26:46.107995+03:00 max-note kded5[2897]: "/var/crash/_usr_bin_konsole.1000.crash" 2024-02-20T09:26:46.108089+03:00 max-note kded5[2897]: "/var/crash" 2024-02-20T09:26:46.108153+03:00 max-note kded5[2897]: running "/usr/share/kubuntu-notification-helper/whoopsie-upload-all" 2024-02-20T09:26:46.108519+03:00 max-note kded5[561360]: kdeinit5: Got EXEC_NEW '/usr/share/kubuntu-notification-helper/whoopsie-upload-all' from launcher. 2024-02-20T09:26:46.108586+03:00 max-note kded5[561360]: kdeinit5: preparing to launch '/usr/share/kubuntu-notification-helper/whoopsie-upload-all' 2024-02-20T09:26:46.182781+03:00 max-note kded5[561375]: INFO: whoopsie-upload-all already running 2024-02-20T09:26:46.195577+03:00 max-note kded5[561374]: ERROR: whoopsie is not running 2024-02-20T09:26:46.197455+03:00 max-note kded5[561360]: kdeinit5: PID 561375 terminated. 2024-02-20T09:26:46.212771+03:00 max-note kded5[561360]: kdeinit5: PID 561374 terminated. 2024-02-20T09:26:48.894910+03:00 max-note kded5[2897]: "/var/crash/_usr_bin_konsole.1000.crash" 2024-02-20T09:26:57.343432+03:00 max-note kded5[2897]: message repeated 17 times: [ "/var/crash/_usr_bin_konsole.1000.crash"] 2024-02-20T09:26:57.466643+03:00 max-note systemd[1]: Started whoopsie.service - crash report submission. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390830] Files in plasma vault indexed and available when the vault is closed
https://bugs.kde.org/show_bug.cgi?id=390830 soredake changed: What|Removed |Added CC|katyaberezy...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390830] Files in plasma vault indexed and available when the vault is closed
https://bugs.kde.org/show_bug.cgi?id=390830 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om --- Comment #14 from Adam Fontenot --- > IMO, baloo needs to ignore all FUSE mounts My merge request that needs review does this, if I'm not mistaken. It's still possible to manually opt in. That may fix this issue. https://invent.kde.org/frameworks/baloo/-/merge_requests/96/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481561] No error message when renaming fails
https://bugs.kde.org/show_bug.cgi?id=481561 --- Comment #3 from Jin Liu --- (In reply to fanzhuyifan from comment #2) > Humm I get the error message on source build of dolphin, btrfs, arch linux. > However after the error message is shown the displayed name incorrectly > shows the new name, instead of the old name. I've seen that, too. Try to create a file "a", and rename it to "012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789" (300 chars). No errors on master. -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 476186] Screen recording quality is terrible
https://bugs.kde.org/show_bug.cgi?id=476186 --- Comment #9 from Adam Fontenot --- Created attachment 165948 --> https://bugs.kde.org/attachment.cgi?id=165948=edit illustration of crf 20 vs 31 in a fullscreen recording As a quick illustration, I've taken two fullscreen (60 fps 1080p) screencasts with comparable details (I scrolled up and down this page in my browser for a bit), at both CRF 31 (the default) and CRF 20 (with my patch). The result illustrates the way that VP9 cheats on flat fields quite well. This area of the screen shown in the image is basically static in the video, and contains large regions of a single color. The encoder cheats a lot here, with a result that is visibly much worse with CRF 31. For common screencast use cases, like recording bugs and features, this is a worst case scenario of sorts, since you'd like to see relatively crisp looking text and icons. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481308] Multiple issues with kscreenlocker in plasma 6 RC2
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #3 from pmarget...@gmail.com --- Sorry for the late reply, I couldn't find this bug report (search is set to a certain set of possible bug states, one of which is not NEEDSINFO. Problem persists with qt 6.7 beta 3 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481308] Multiple issues with kscreenlocker in plasma 6 RC2
https://bugs.kde.org/show_bug.cgi?id=481308 pmarget...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from pmarget...@gmail.com --- (In reply to Nate Graham from comment #1) > Do you have an NVIDIA GPU? No, amd 6700 XT, using amdgpu drivers -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 476186] Screen recording quality is terrible
https://bugs.kde.org/show_bug.cgi?id=476186 --- Comment #8 from Adam Fontenot --- (In reply to Noah Davis from comment #7) > From all the reading of encoder documentation I've done in the past, 31 is > not low, it's average and actually looks decent when doing fullscreen > recording. In my own tests, there was not a significant difference in > quality between 20 CRF and 31 CRF when doing fullscreen recording either. > For me, fullscreen is 1080p@60Hz or 4K@60Hz. For some reason, recording a > smaller region has a strong negative effect on recording quality, so we may > need to scale quality with region size inversely. I think the issue is more likely to lie elsewhere. There are very few actual frames in my screencast, which is an issue not only for seeking, but also for the efficiency of the encoder. This is probably not as noticeable with full motion 24 fps or 60 fps video, but in the case of my screencast, there are only 90 actual frames in the file, because KPipeWire seems to be dropping duplicate frames rather than sending them to the encoder. In a 15.35 second clip with a nominal framerate of 60 fps, you expect to see 921 frames. So ffmpeg has only encoded 1 in 10 frames, due to the missing duplicates. The low number of frames means that the quality of the video depends on the quality of the individual frames much more. At a relatively low quality CRF like 31, the encoder is probably cheating too much on these frames. This is combined with the fact that video encoders are optimized for full motion video, not screencasts, so their quality metrics cheat heavily on flat fields (regions of nearly solid color) because they can be smoothed out and encoded at a very small size. That's clearly visible in my screencast. The recommendation for CRF 31 seems to come from Google, and I'm skeptical of their figures. They consistently underestimate bitrates needed for reasonable quality, as is readily apparent if you watch their encodes for YouTube. Interestingly, they recommend a CRF of 15 for 4K video, so VP9's CRF metric does not seem particularly consistent. For what it's worth, their example encode of "Tears of Steel" (the open source Blender film) at CRF 31 and 1080p strikes me as rather poor, and that has the advantage of being a two-pass encode. [1] I'm not trying to be overly debate-y here; there's not going to be a single one-size-fits-all value for all resolutions and all use cases. The correct approach is probably to allow setting the CRF directly in the Spectacle settings and passing the value to KPipeWire. [1] https://developers.google.com/media/vp9/settings/vod/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481522] Share KDE's virtual desktop (in addition of actual physical screen)
https://bugs.kde.org/show_bug.cgi?id=481522 fanzhuyi...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from fanzhuyi...@gmail.com --- Setting to confirmed since this sounds like a reasonable feature and use case -- but if I understand correctly, this seems to require very big changes to kwin. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481561] No error message when renaming fails
https://bugs.kde.org/show_bug.cgi?id=481561 --- Comment #2 from fanzhuyi...@gmail.com --- Humm I get the error message on source build of dolphin, btrfs, arch linux. However after the error message is shown the displayed name incorrectly shows the new name, instead of the old name. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481561] No error message when renaming fails
https://bugs.kde.org/show_bug.cgi?id=481561 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- CC: https://invent.kde.org/frameworks/kio/-/merge_requests/1551 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481522] Share KDE's virtual desktop (in addition of actual physical screen)
https://bugs.kde.org/show_bug.cgi?id=481522 --- Comment #1 from Benedict --- Reading a forum thread on screen sharing/capture at https://forum.manjaro.org/t/obs-cant-capture-screen-on-kde-plasma-wayland/147820 It seems that under Wayland, screen sharing is handled by Pipewire and xdg-desktop-portal-kde. So it seems like the requirements would be (1) KDE's virtual desktop will probably need to be renderable both when active and in background (2) KDE's virtual desktops to be a source that Pipewire can capture (3) xdg-desktop-portal-kde recognize virtual desktops as source I'd say this is a useful feature that is possible to implement without too much effort. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 479935] Crashed after initial install on first attempt to connect to Mac
https://bugs.kde.org/show_bug.cgi?id=479935 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.
[krita] [Bug 480915] https://www.reddit.com/r/krita/comments/19epys0/why_isnt_krita_reading_the_pressure_on_my_tablet/
https://bugs.kde.org/show_bug.cgi?id=480915 --- 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.
[kwin] [Bug 475444] Crash after re-login after weird multi-screen bug
https://bugs.kde.org/show_bug.cgi?id=475444 --- 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.
[dolphin] [Bug 480793] Dolphin crashed after I had changed the system colour theme
https://bugs.kde.org/show_bug.cgi?id=480793 --- Comment #3 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.
[plasmashell] [Bug 472971] plasmashell crash immediately after login when browsing categories in application menu
https://bugs.kde.org/show_bug.cgi?id=472971 --- Comment #5 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.
[neon] [Bug 475258] Since 3 days cannot update the system
https://bugs.kde.org/show_bug.cgi?id=475258 --- Comment #5 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.
[neon] [Bug 472941] DBus Backend error: could not contact the helper. Connection Error: Did not receive reply
https://bugs.kde.org/show_bug.cgi?id=472941 --- Comment #3 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.
[neon] [Bug 472136] Plasma 6 X11 - 2023-07-10 Update to System Tray, (notifications, clock, etc) causing icons / applications to not properly load
https://bugs.kde.org/show_bug.cgi?id=472136 --- 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.
[neon] [Bug 472135] Plasma 6 X11 - 2023-07-10 Neon Unstable update - black screen / reload when using krunner, (Meta+[application name])
https://bugs.kde.org/show_bug.cgi?id=472135 --- 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.
[plasmashell] [Bug 452759] OSD of keyboard layout unnecessarily appears when I start to type on Wayland
https://bugs.kde.org/show_bug.cgi?id=452759 --- Comment #20 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.
[plasmashell] [Bug 481563] Plasma Crash
https://bugs.kde.org/show_bug.cgi?id=481563 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #1 from fanzhuyi...@gmail.com --- Thank you for your bug report! Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), as this version of the KDE software is out of support from KDE, and so it's possible that the bug exists only in Debian at this point. Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream. Thanks for understanding! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481562] 23:51:57.852 UTC systemd-coredump@0-1187-0.service Process 751 (kwin_wayland) of user 1000 dumped core.
https://bugs.kde.org/show_bug.cgi?id=481562 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |BACKTRACE Severity|critical|crash Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols that we need to figure out exactly what's going wrong. Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481564] Launching Firefox crashed PlasmaShell.
https://bugs.kde.org/show_bug.cgi?id=481564
--- Comment #1 from `{third: "Beedell", first: "Roke"}`{.JSON5}
<4wy78...@rokejulianlockhart.addy.io> ---
Created attachment 165947
--> https://bugs.kde.org/attachment.cgi?id=165947=edit
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 481564] New: Launching Firefox crashed PlasmaShell.
https://bugs.kde.org/show_bug.cgi?id=481564 Bug ID: 481564 Summary: Launching Firefox crashed PlasmaShell. Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: 4wy78...@rokejulianlockhart.addy.io CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.7.2-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: I relaunched https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64/MozillaFirefox-122.0.1-1.1.x86_64.rpm quickly after quitting it, which appeared to coincide with PlasmaShell reloading and DrKonqi appearing. The crash does not seem to be reproducible. -- Backtrace (Reduced): #6 0x7fe6091ffcdb in os_malloc_aligned (alignment=64, size=184) at ../src/util/os_memory_aligned.h:58 #7 align_calloc (alignment=64, size=184) at ../src/util/u_memory.h:68 #8 si_create_sampler_view(pipe_context*, pipe_resource*, pipe_sampler_view const*) (ctx=0x55b1db5c3600, texture=0x7fe4ac183880, state=0x7fe5653fdd10) at ../src/gallium/drivers/radeonsi/si_state.c:4555 #9 0x7fe608fde214 in tc_create_sampler_view(pipe_context*, pipe_resource*, pipe_sampler_view const*) (_pipe=0x55b1e048b9b0, resource=, templ=) at ../src/gallium/auxiliary/util/u_threaded_context.c:2246 #10 0x7fe608badce6 in st_create_texture_sampler_view_from_stobj (glsl130_or_later=false, format=, texObj=0x7fe4ac16a6e0, st=0x55b1ddb1f180) at ../src/mesa/state_tracker/st_sampler_view.c:491 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 476186] Screen recording quality is terrible
https://bugs.kde.org/show_bug.cgi?id=476186 --- Comment #7 from Noah Davis --- (In reply to Adam Fontenot from comment #6) > Created attachment 165924 [details] > screencast illustrating poor recording quality > > I see this on the latest beta (kpipewire 5.92.3, spectacle 24.01.95) with > VP9 recording. As requested I'm attaching a video, which is a short > recording I made of Crosswords [1] to illustrate a bug with that program. > > These are clearly encoding artifacts stemming from the very low CRF used by > default (31) for VP9. I was able to mostly fix the issue by changing the > default quality to 20, which seems like a much more reasonable default. > > [1] https://gitlab.gnome.org/jrb/crosswords >From all the reading of encoder documentation I've done in the past, 31 is not low, it's average and actually looks decent when doing fullscreen recording. In my own tests, there was not a significant difference in quality between 20 CRF and 31 CRF when doing fullscreen recording either. For me, fullscreen is 1080p@60Hz or 4K@60Hz. For some reason, recording a smaller region has a strong negative effect on recording quality, so we may need to scale quality with region size inversely. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481563] New: Plasma Crash
https://bugs.kde.org/show_bug.cgi?id=481563 Bug ID: 481563 Summary: Plasma Crash Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jackcumm...@hotmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-17-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: I had three applications open when the crash occured: 1) Firefox with maybe 70+ tabs open 2) Thunderbird - I had just been using Thuderbirds, whatsapp extension 3) Dolphin - with 5 tabs open I think I was just moving from the whatsapp tab in Thunderbird to the email tabs (using Quickfolders extension). Possibly I was moving to Firefox. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 588092 (plasmashell) UID: 1000 (jack) GID: 1000 (jack) Signal: 11 (SEGV) Timestamp: Tue 2024-02-20 09:30:15 HKT (16min ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (jack) Boot ID: 96bcafdaad0642ada3ee5a76ee69e983 Machine ID: 4dab1c9f3e4e4b43ba010ca1a6a7eb26 Hostname: BigOne Storage: /var/lib/systemd/coredump/core.plasmashell.1000.96bcafdaad0642ada3ee5a76ee69e983.588092.170839261500.zst (present) Size on Disk: 35.4M Message: Process 588092 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.19-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.19-1~deb12u1.amd64 Stack trace of thread 588092: #0 0x7f06630aed14 __GI___pthread_sigmask (libc.so.6 + 0x8fd14) #1 0x7f066305b239 __GI___sigprocmask (libc.so.6 + 0x3c239) #2 0x7f0665737e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f0665738b3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f066305b050 __restore_rt (libc.so.6 + 0x3c050) #5 0x7f0663b25c80 _ZN6QColoraSERKS_ (libQt5Gui.so.5 + 0x325c80) #6 0x7f0664075a0a _ZN11KIconColorsC1ERK8QPalette (libKF5IconThemes.so.5 + 0x16a0a) #7 0x7f0664083526 _ZN11KIconLoader16setCustomPaletteERK8QPalette (libKF5IconThemes.so.5 + 0x24526) #8 0x7f06562b9f67 n/a (libcorebindingsplugin.so + 0x41f67) #9 0x7f06562b955f n/a (libcorebindingsplugin.so + 0x4155f) #10 0x7f0665269a92 _ZN19QQuickWindowPrivate11polishItemsEv (libQt5Quick.so.5 + 0x269a92) #11 0x7f066520bbcd n/a (libQt5Quick.so.5 + 0x20bbcd) #12 0x7f0665276e20 _ZN12QQuickWindow5eventEP6QEvent (libQt5Quick.so.5 + 0x276e20) #13 0x7f0664362fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #14 0x7f06634b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #15 0x7f066392c3e8 _ZN15QPlatformWindow20deliverUpdateRequestEv (libQt5Gui.so.5 + 0x12c3e8) #16 0x7f06634dd6f0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd6f0) #17 0x7f0664362fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #18 0x7f06634b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #19 0x7f06634b4681 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b4681) #20 0x7f066350a153 n/a (libQt5Core.so.5 + 0x30a153) #21 0x7f0661f4a7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #22 0x7f0661f4aa38 n/a (libglib-2.0.so.0 + 0x54a38) #23 0x7f0661f4aacc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #24 0x7f0663509836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #25 0x7f06634b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b)
[kwin] [Bug 481562] New: 23:51:57.852 UTC systemd-coredump@0-1187-0.service Process 751 (kwin_wayland) of user 1000 dumped core.
https://bugs.kde.org/show_bug.cgi?id=481562 Bug ID: 481562 Summary: 23:51:57.852 UTC systemd-coredump@0-1187-0.service Process 751 (kwin_wayland) of user 1000 dumped core. Classification: Plasma Product: kwin Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: rustmil...@proton.me Target Milestone: --- 23:51:57.852 UTC systemd-coredump@0-1187-0.service Process 751 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 751: #0 0x789da5aab32c n/a (libc.so.6 + 0x8d32c) #1 0x789da5a5a6c8 raise (libc.so.6 + 0x3c6c8) #2 0x789da5a424b8 abort (libc.so.6 + 0x244b8) #3 0x789da7b8afee n/a (libepoxy.so.0 + 0xbbfee) #4 0x789da7b8e9d2 n/a (libepoxy.so.0 + 0xbf9d2) #5 0x789da8631ae7 n/a (libkwin.so.5 + 0x431ae7) #6 0x789da8633919 _ZN4KWin9EglDmabufD1Ev (libkwin.so.5 + 0x433919) #7 0x789da8634e71 _ZN4KWin18AbstractEglBackendD2Ev (libkwin.so.5 + 0x434e71) #8 0x789da857677d n/a (libkwin.so.5 + 0x37677d) #9 0x789da83c061b _ZN4KWin10Compositor4stopEv (libkwin.so.5 + 0x1c061b) #10 0x789da83b9198 _ZN4KWin10Compositor12reinitializeEv (libkwin.so.5 + 0x1b9198) #11 0x789da6ac8e27 n/a (libQt5Core.so.5 + 0x2c8e27) #12 0x789da851213a _ZN4KWin9Workspace15slotReconfigureEv (libkwin.so.5 + 0x31213a) #13 0x789da6ac8e27 n/a (libQt5Core.so.5 + 0x2c8e27) #14 0x789da6aca95f _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2ca95f) #15 0x789da6abb8de _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2bb8de) #16 0x789da61578ff _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1578ff) #17 0x789da6a93ef8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x293ef8) #18 0x789da6ae255b _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2e255b) #19 0x789da6ae2a41 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e2a41) #20 0x5b69019c9ed2 n/a (kwin_wayland + 0x137ed2) #21 0x789da6a92c04 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x292c04) #22 0x789da6a940a3 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2940a3) #23 0x5b69018e540b n/a (kwin_wayland + 0x5340b) #24 0x789da5a43cd0 n/a (libc.so.6 + 0x25cd0) #25 0x789da5a43d8a __libc_start_main (libc.so.6 + 0x25d8a) #26 0x5b69018e7015 n/a (kwin_wayland + 0x55015) Stack trace of thread 766: #0 0x789da5b190bf __poll (libc.so.6 + 0xfb0bf) #1 0x789da476c2f6 n/a (libglib-2.0.so.0 + 0xb82f6) #2 0x789da470c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #3 0x789da6ae2d0c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e2d0c) #4 0x789da6a92c04 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x292c04) #5 0x789da68ef576 _ZN7QThread4execEv (libQt5Core.so.5 + 0xef576) #6 0x789da8911a9a n/a (libQt5DBus.so.5 + 0x17a9a) #7 0x789da68eb79a n/a (libQt5Core.so.5 + 0xeb79a) #8 0x789da5aa955a n/a (libc.so.6 + 0x8b55a) #9 0x789da5b26a3c n/a (libc.so.6 + 0x108a3c) Stack trace of thread 790: #0 0x789da5b190bf __poll (libc.so.6 + 0xfb0bf) #1 0x789da476c2f6 n/a (libglib-2.0.so.0 + 0xb82f6) #2 0x789da470c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #3 0x789da6ae2d0c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e2d0c) #4 0x789da6a92c04 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x292c04) #5 0x789da68ef576 _ZN7QThread4execEv (libQt5Core.so.5 + 0xef576) #6 0x789da68eb79a n/a (libQt5Core.so.5 + 0xeb79a) #7 0x789da5aa955a n/a (libc.so.6 + 0x8b55a) #8 0x789da5b26a3c n/a (libc.so.6 + 0x108a3c) Stack trace of thread 787: #0 0x789da5aa5ebe n/a (libc.so.6 + 0x87ebe) #1 0x789da5aa8750 pthread_cond_wait (libc.so.6 + 0x8a750) #2 0x789d9da8686c n/a (radeonsi_dri.so + 0x8686c) #3 0x789d9da9e83c n/a (radeonsi_dri.so + 0x9e83c) #4 0x789da5aa955a n/a (libc.so.6 + 0x8b55a) #5 0x789da5b26a3c n/a (libc.so.6 + 0x108a3c) Stack trace of thread 805: #0 0x789da5b190bf __poll (libc.so.6 + 0xfb0bf) #1 0x789da476c2f6 n/a (libglib-2.0.so.0 + 0xb82f6) #2 0x789da470c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #3 0x789da6ae2d0c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e2d0c) #4 0x789da6a92c04 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x292c04) #5 0x789da68ef576 _ZN7QThread4execEv (libQt5Core.so.5 + 0xef576) #6 0x789da78c5a20 n/a (libQt5Qml.so.5 +
[systemsettings] [Bug 478959] "Outputs could not be saved due to error." error message seen when trying to modify settings right after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=478959 mashkal2...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475864] Error on switch from yandex browser to desktop
https://bugs.kde.org/show_bug.cgi?id=475864 a...@ziposoft.com changed: What|Removed |Added Attachment #164842|New crash information added |Plasma crash due to "small description|by DrKonqi |window previews" enabled in ||task manager --- Comment #11 from a...@ziposoft.com --- Comment on attachment 164842 --> https://bugs.kde.org/attachment.cgi?id=164842 Plasma crash due to "small window previews" enabled in task manager I was getting seemingly random crashes in plasma when switch tasks or even moving the mouse between monitors. I found that is was cased by the "small window previews" enabled in task manager. I simply disabled that and problem went away. Crash is probably during generation of certain window previews. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481561] No error message when renaming fails
https://bugs.kde.org/show_bug.cgi?id=481561 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353407] Where is the shelf for the panel in Plasma 5?
https://bugs.kde.org/show_bug.cgi?id=353407 J.M. 'Peng' Hardin changed: What|Removed |Added CC||peng.thinkb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481548] After switching to new Hugo based website, Welcome Page News section is not fetching non-English news properly
https://bugs.kde.org/show_bug.cgi?id=481548 --- Comment #3 from Tyson Tan --- Created attachment 165946 --> https://bugs.kde.org/attachment.cgi?id=165946=edit English/Japanse/Chinese becomes English/English/English -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481548] After switching to new Hugo based website, Welcome Page News section is not fetching non-English news properly
https://bugs.kde.org/show_bug.cgi?id=481548 --- Comment #2 from Tyson Tan --- No, it's not like I'm against always showing English, but currently for example if you set to show English, Chinese and Japanese, you get English, English, English. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481561] New: No error message when renaming fails
https://bugs.kde.org/show_bug.cgi?id=481561 Bug ID: 481561 Summary: No error message when renaming fails Classification: Applications Product: dolphin Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ad.liu@gmail.com CC: kfm-de...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Select a file. 2. Press F2. 3. Enter a very long file name (longer than 255 chars) OBSERVED RESULT No error message EXPECTED RESULT Dolphin tells me that renaming failed. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kgraphviewer] [Bug 481560] New: Segmentation fault (core dumped) kgraphviewer
https://bugs.kde.org/show_bug.cgi?id=481560 Bug ID: 481560 Summary: Segmentation fault (core dumped) kgraphviewer Classification: Applications Product: kgraphviewer Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kle...@gmail.com Reporter: jro.joh...@gmail.com Target Milestone: --- SUMMARY *** Installed kgraphviewer (2.4.3) from `sudo snap install kgraphviewer`. *** $ kgraphviewer & [1] 39919 [1]+ Segmentation fault (core dumped) kgraphviewer Error: Layout type: "dot" not recognized. Use one of: Error: Layout was not done PID: 42145 (kgraphviewer) UID: 1000 (jro) GID: 1000 (jro) Signal: 11 (SEGV) Timestamp: Mon 2024-02-19 17:37:26 MST (4min 13s ago) Command Line: /snap/kgraphviewer/23/usr/bin/kgraphviewer Executable: /snap/kgraphviewer/23/usr/bin/kgraphviewer Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/snap.kgraphviewer.kgraphviewer-303899a2-6099-47af-b160-48b9914b7acd.scope Unit: user@1000.service User Unit: snap.kgraphviewer.kgraphviewer-303899a2-6099-47af-b160-48b9914b7acd.scope Slice: user-1000.slice Owner UID: 1000 (jro) Boot ID: dd6243447c424c68bc4dba3496cb39f6 Machine ID: b96b91023fbc491a9f55351c6084071f Hostname: heterodoxe Storage: /var/lib/systemd/coredump/core.kgraphviewer.1000.dd6243447c424c68bc4dba3496cb39f6.42145.170838944600.zst (present) Disk Size: 5.9M Message: Process 42145 (kgraphviewer) of user 1000 dumped core. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemX11Plugin.so without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/liblcms2.so.2.0.15 without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libQt5Pdf.so.5.15.15 without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2 without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libLLVM-15.so.1 with build-id: 5d46c4221e9c32a1695da30bd95956dd9ce00984 Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libxcb-res.so.0.0.0 without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libqsvg.so without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libqpdf.so without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libqjpeg.so without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libqico.so without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libqgif.so without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so with build-id: d04a40e4062a8d444ff6f23d4fe768215b2e32c7 Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libKF5Kirigami2.so.5.110.0 without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/qt5/plugins/styles/breeze.so without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libpciaccess.so.0.11.1 with build-id: 4c93da952f83c1d085d4bdead692db544c79b004 Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.13 with build-id: 1cf4a22fbe15a77baca28e9c824592b8b5d852ff Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libdrm_intel.so.1.0.0 with build-id: 1779f1456c23659361ed9d209f046fb4a63dd16c Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0 with build-id: 4fabac4e8f6392c94a93bbda25393bb8718ca39d Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libdrm_amdgpu.so.1.0.0 with build-id: 577e88c58f5655f637a2265b4a3f2aa4cf055d56 Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libKF5Style.so.5.110.0 without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libbreezecommon5.so.5.27.8 without build-id. Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1.0.1 with build-id: 677c2af4488b7abfdb6b7a3468b68b6c8ee88b1b Found module /snap/kgraphviewer/23/kf5/usr/lib/x86_64-linux-gnu/libxcb-present.so.0.0.0 with build-id: a4f415af56b06f1f38d5a0339dd9828ff136b115 Found module
[plasmashell] [Bug 481559] Buggy settings panel of digital clock.
https://bugs.kde.org/show_bug.cgi?id=481559 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481558] plasmashell crashes when restarting it via systemctl
https://bugs.kde.org/show_bug.cgi?id=481558 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481555] HDD doesn't spin down properly on shutdown
https://bugs.kde.org/show_bug.cgi?id=481555 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- This sounds like a local configuration issue. I would suggest asking for help on the distro forums. It is quite unlikely that KDE software is the root cause of this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481559] Buggy settings panel of digital clock.
https://bugs.kde.org/show_bug.cgi?id=481559 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from fanzhuyi...@gmail.com --- Can't reproduce on arch source build, wayland. Does this also happen with a new user account? What theme is this? -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 481546] Crash at the end of a game with 2 CPU players
https://bugs.kde.org/show_bug.cgi?id=481546 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Resolution|DOWNSTREAM |--- Status|NEEDSINFO |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/games/knights/-/merge_requests/23 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481559] New: Buggy settings panel of digital clock.
https://bugs.kde.org/show_bug.cgi?id=481559 Bug ID: 481559 Summary: Buggy settings panel of digital clock. Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: mooodyhun...@outlook.com Target Milestone: 1.0 Created attachment 165945 --> https://bugs.kde.org/attachment.cgi?id=165945=edit The Settings Dialog 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. Right click any digital clock applet 2. Click "Configure Digital Clock" 3. Click one of "Astronomical Events", "Holidays" and "Calendar Events" OBSERVED RESULT All three entries being 'selected', and I cannot adjust their settings EXPECTED RESULT Only one entry is selected, right hand side shows appropriate settings panel, respectively Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × 13th Gen Intel® Core™ i9-13900HX Memory: 62.6 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4050 Laptop GPU/PCIe/SSE2 Manufacturer: LENOVO Product Name: 82WK System Version: Legion Y9000P IRX8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481331] Dragging a window on screen 1 to screen 2 actually moves it to a different virtual desktop
https://bugs.kde.org/show_bug.cgi?id=481331 Dashon changed: What|Removed |Added CC||sparky123558w...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481558] New: plasmashell crashes when restarting it via systemctl
https://bugs.kde.org/show_bug.cgi?id=481558
Bug ID: 481558
Summary: plasmashell crashes when restarting it via systemctl
Classification: Plasma
Product: plasmashell
Version: 5.93.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: mooodyhun...@outlook.com
Target Milestone: 1.0
Application: plasmashell (5.93.0)
Qt Version: 6.7.0
Frameworks Version: 5.249.0
Operating System: Linux 6.7.5-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.93.0 [CoredumpBackend]
-- Information about the crash:
I sometimes restart plasmashell via 'systemctl restart --user
plasma-plasmashell', but it doesn't always restart without issue.
The crash can be reproduced sometimes.
-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/bin/plasmashell...
[New LWP 39816]
[New LWP 40096]
[New LWP 40045]
[New LWP 40090]
[New LWP 40086]
[New LWP 40052]
[New LWP 42751]
[New LWP 42754]
[New LWP 45427]
[New LWP 42752]
[New LWP 40166]
[New LWP 40125]
[New LWP 39820]
[New LWP 45428]
[New LWP 40098]
[New LWP 40097]
[New LWP 39894]
[New LWP 40088]
[New LWP 40051]
[New LWP 40164]
[New LWP 40165]
[New LWP 40050]
[New LWP 40160]
[New LWP 40162]
[New LWP 40161]
[New LWP 42753]
[New LWP 39895]
[New LWP 40130]
[New LWP 40089]
[New LWP 39994]
[New LWP 45429]
Downloading separate debug info for /usr/lib/libkworkspace6.so.5...
Downloading separate debug info for /usr/lib/libLayerShellQtInterface.so.6...
Downloading separate debug info for /usr/lib/libKF6UserFeedbackCore.so.6...
Downloading separate debug info for /usr/lib/libffi.so.8...
Downloading separate debug info for /usr/lib/libb2.so.1...
Downloading separate debug info for /usr/lib/libvorbisfile.so.3...
Downloading separate debug info for /usr/lib/libvorbis.so.0...
Downloading separate debug info for /usr/lib/libogg.so.0...
Downloading separate debug info for /usr/lib/libnghttp3.so.9...
Downloading separate debug info for /usr/lib/libpsl.so.5...
Downloading separate debug info for /usr/lib/libunistring.so.5...
Downloading separate debug info for
/usr/lib/qt6/plugins/platforms/libqwayland-generic.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/wayland-shell-integration/libxdg-shell.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/wayland-graphics-integration-client/../../../libQt6WaylandEglClientHwIntegration.so.6...
Downloading separate debug info for /usr/lib/libEGL_nvidia.so.0...
Downloading separate debug info for /usr/lib/libnvidia-glsi.so.545.29.06...
Downloading separate debug info for /usr/lib/libnvidia-eglcore.so.545.29.06...
Downloading separate debug info for /usr/lib/libnvidia-gpucomp.so.545.29.06...
Downloading separate debug info for /usr/lib/libnvidia-egl-gbm.so.1...
Downloading separate debug info for
/usr/lib/qt6/plugins/imageformats/../../../libmng.so.2...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/packagestructure/plasma_lookandfeel.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/packagestructure/plasma_shell.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/packagestructure/plasma_applet.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/packagestructure/plasma_layouttemplate.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/plasma/containmentactions/org.kde.paste.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/plasma/containmentactions/org.kde.contextmenu.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/plasma/containmentactions/org.kde.switchdesktop.so...
Downloading separate debug info for /usr/lib/libtaskmanager.so.6...
Downloading separate debug info for
/usr/lib/qt6/plugins/plasma/applets/org.kde.plasma.panelspacer.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/plasma/applets/org.kde.plasma.systemtray.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/plasma/applets/org.kde.plasma.appmenu.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/plasma/applets/org.kde.plasma.private.systemtray.so...
Downloading separate debug info for /usr/lib/libQt6Sql.so.6...
Downloading separate debug info for
/usr/lib/qt6/plugins/plasma/applets/org.kde.plasma.notifications.so...
Downloading separate debug info for
/usr/lib/qt6/qml/org/kde/plasma/activityswitcher/libactivityswitcherextensionplugin.so...
Downloading separate debug info for
/usr/lib/qt6/qml/org/kde/private/desktopcontainment/desktop/libdesktopplugin.so...
Downloading separate debug info for
[KScreen] [Bug 481467] Set refresh rate not applied when screen turn on after idle
https://bugs.kde.org/show_bug.cgi?id=481467 Zamundaaa changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #10 from Zamundaaa --- Then this could either be a bug in your monitor's firmware, or a bug in the driver. Please make a bug report at https://gitlab.freedesktop.org/drm/amd/-/issues about this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #10 from Zamundaaa --- yes, please do report it to Mesa. Other compositors have different renderer architectures, use other buffer formats (10 bit per color with KWin vs 8 bit per color with others), different effects and so on and will trigger different driver code paths and thus different driver bugs than KWin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 Zamundaaa changed: What|Removed |Added CC||ashco...@gmail.com --- Comment #61 from Zamundaaa --- *** Bug 481554 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481554] Wayland + Nvidia - Extreme stuttering doing anything
https://bugs.kde.org/show_bug.cgi?id=481554 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Zamundaaa --- This is a bug in the NVidia driver, and will only be resolved with a future driver release *** This bug has been marked as a duplicate of bug 452219 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #9 from airisama...@gmail.com --- ? but I feel like it's more about the way the driver is used since gnome, sway and cinnamon has almost no graphical glitches so maybe reporting there is not the right move although it kinda of gets better every new version of mesa so, to clarify you line of thought, you just use their api's and expect it to work? if yes then maybe I should report it there -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481467] Set refresh rate not applied when screen turn on after idle
https://bugs.kde.org/show_bug.cgi?id=481467 --- Comment #9 from Bernhard --- (In reply to Zamundaaa from comment #8) > Interesting, that means KWin's internal state considers the mode to be > 120Hz... What does drm_info say? It should have a "MODE_ID" field where it > states the exact refresh rate that the driver is actually trying to drive. Oof, that one also states says 120Hz when my monitor reports 144Hz ├───CRTCs │ ├───CRTC 0 │ │ ├───Object ID: 85 │ │ ├───Legacy info │ │ │ ├───Mode: 3840x2160@120.02 driver phsync pvsync │ │ │ └───Gamma size: 256 │ │ └───Properties │ │ ├───"ACTIVE" (atomic): range [0, 1] = 1 │ │ ├───"MODE_ID" (atomic): blob = 150 │ │ │ └───3840x2160@120.02 driver phsync pvsync │ │ ├───"OUT_FENCE_PTR" (atomic): range [0, UINT64_MAX] = 0 │ │ ├───"VRR_ENABLED": range [0, 1] = 0 │ │ ├───"DEGAMMA_LUT": blob = 0 │ │ ├───"DEGAMMA_LUT_SIZE" (immutable): range [0, UINT32_MAX] = 4096 │ │ ├───"CTM": blob = 0 │ │ ├───"GAMMA_LUT": blob = 0 │ │ └───"GAMMA_LUT_SIZE" (immutable): range [0, UINT32_MAX] = 4096 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481467] Set refresh rate not applied when screen turn on after idle
https://bugs.kde.org/show_bug.cgi?id=481467 --- Comment #8 from Zamundaaa --- Interesting, that means KWin's internal state considers the mode to be 120Hz... What does drm_info say? It should have a "MODE_ID" field where it states the exact refresh rate that the driver is actually trying to drive. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481557] Krita 5.2.2 text tool cuts off last character
https://bugs.kde.org/show_bug.cgi?id=481557 wolthera changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Hm... I can't reproduce that here in 5.3 on kde neon (even with Cantarell), can you share what's in the SVG source tab? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 480797] "PrefersNonDefaultGPU" setting can nonsensically end up preferring the less powerful integrated GPU in cases where the more powerful GPU is the default one
https://bugs.kde.org/show_bug.cgi?id=480797 --- Comment #12 from burne...@gmail.com --- Mine would probably be the most common use-case on desktop PCs that use both dedicated and integrated graphics. How this has managed to fly under the radar this far I can only guess; possibly a combination of: - Most Linux gamers currently using setups without dual graphics (i.e. no iGPU) - People with dual graphics disabling their unneeded iGPU -- though this is not the default on such systems, it's a BIOS setting one has to go out of their way to change - Steam being smart enough to ignore this setting in most use-cases -- I've only had this cause issues with Lutris in past, and there it is likely attributed to a poorly named "Use discrete graphics" option in the Lutris settings which in reality should be "Prefer non-default graphics": https://github.com/lutris/lutris/issues/4416 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481557] Krita 5.2.2 text tool cuts off last character
https://bugs.kde.org/show_bug.cgi?id=481557 connorpick...@gmail.com changed: What|Removed |Added CC||connorpick...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481557] New: Krita 5.2.2 text tool cuts off last character
https://bugs.kde.org/show_bug.cgi?id=481557 Bug ID: 481557 Summary: Krita 5.2.2 text tool cuts off last character Classification: Applications Product: krita Version: 5.2.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: connorpick...@gmail.com Target Milestone: --- Created attachment 165944 --> https://bugs.kde.org/attachment.cgi?id=165944=edit screenshot of display problem SUMMARY Every time I use the text tool, the final character of my text is cut off. Even the initial placeholder text displays as "Placeholder Tex" in the document view. It is correct in the text-edit window. Documents that I created before this error appeared now have the same behavior. The last character of any text is cut off. STEPS TO REPRODUCE 1. Use the Text tool to add text. 2. 3. OBSERVED RESULT Document view always cuts off last character, regardless of font family or contents of text. EXPECTED RESULT Should display the entire text. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 39 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION My office computer and home computer, both up-to-date Fedora 39 installations, both display the same behavior. When I downgrade to 5.1.5, there is no problem. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481467] Set refresh rate not applied when screen turn on after idle
https://bugs.kde.org/show_bug.cgi?id=481467 --- Comment #7 from Bernhard --- (In reply to Zamundaaa from comment #6) > Okay, that looks correct. Does it change after the screen turns off and on > again? No, it does not, it always says 120Hz. The file is in fact identical when diffed. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481467] Set refresh rate not applied when screen turn on after idle
https://bugs.kde.org/show_bug.cgi?id=481467 --- Comment #6 from Zamundaaa --- Okay, that looks correct. Does it change after the screen turns off and on again? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 480797] "PrefersNonDefaultGPU" setting can nonsensically end up preferring the less powerful integrated GPU in cases where the more powerful GPU is the default one
https://bugs.kde.org/show_bug.cgi?id=480797 --- Comment #11 from Zamundaaa --- Sorry, what I mentioned before was wrong. The "PrefersNonDefaultGPU" key is just very badly named, it's intended to be "PrefersPowerfulGPU" per the spec. See https://invent.kde.org/frameworks/kio/-/merge_requests/1556 for a proper fix For being able to correct the "default gpu" being wrong if your firmware messes up, that's a different issue / feature request, and one to take care of in KWin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #8 from Zamundaaa --- Okay. In case that doesn't exist yet, I'd still recommend you to make a bug report about the driver issue you have problems with here: https://gitlab.freedesktop.org/mesa/mesa/-/issues -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481045] Crash (sometimes) in QQmlMetaType::propertyCache when going to a different KCM in Energy Saving > Advanced Power Settings
https://bugs.kde.org/show_bug.cgi?id=481045 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kcmutils/-/merge_requests/201 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480964] XWayland crash while scrolling using mouse after 2024-02-04 update
https://bugs.kde.org/show_bug.cgi?id=480964 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #5 from Zamundaaa --- You'd need to debug Xwayland, not the app itself. To do that you'd need to use an ssh session from a different PC though, as halting Xwayland for debugging can sometimes also freeze kwin, so you could never unfreeze it from the same PC. Before we go there though, if coredumpctl doesn't work, it's likely the issue is caused by an assert, or by a Wayland error. Those will be visible in the log, so you should check it for a hint about what happened. If you execute journalctl --user --boot 0 --follow (and leave it running) and then trigger the Xwayland crash, you should see some message about the crash in the terminal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480885] High CPU usage for window under cursor \ plasma shell (if over desktop) and kwin_wayland when moving mouse cursor
https://bugs.kde.org/show_bug.cgi?id=480885 Zamundaaa changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #5 from Zamundaaa --- Can't reproduce; I get around 5% combined CPU usage kwin_wayland + plasmashell when moving the cursor over the desktop with a 12k DPI mouse. If you can consistently see this high CPU usage, you could try finding out what's causing it in kwin with hotspot (https://github.com/KDAB/hotspot). Just record a trace of the kwin_wayland process, and check if any single function call looks conspicuous in the flame graph. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #7 from airisama...@gmail.com --- anyway don't sweat about this and just make sure the MESA_LOADER_DRIVER_OVERRIDE=llvmpipe env still works on future updates. it's not a big deal -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 481009] Cannot open LabPlot2 after installation via DMG
https://bugs.kde.org/show_bug.cgi?id=481009 Stefan Gerlach changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Stefan Gerlach --- We now have signed installer for x86_64 and arm64. Due to a bug in XCode they only work on macOS 14 (Sonoma). The installer can be found on the SourceForge page https://sourceforge.net/projects/labplot/files/labplot/2.10/ Any comments or bug reports are welcome. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481045] Crash (sometimes) in QQmlMetaType::propertyCache when going to a different KCM in Energy Saving > Advanced Power Settings
https://bugs.kde.org/show_bug.cgi?id=481045 --- Comment #6 from Jakob Petsovits --- (In reply to Jakob Petsovits from comment #5) > "Partial" success: (...). However, it will crash when trying > to close it because apparently QQmlEngine keeps other references to those > objects around and they will derefence a freed object on QQmlEngine > destruction. Looks like that crash (featuring QQuickPopup) is independent from the sub-page crash of this issue, it also occurs when no sub-pages were opened in the first place, or when opening a different KCM than PowerDevil, before and after my reparenting/deletion changes. I'll submit an MR with the "partial" fix and maybe we'll figure out the other crash in a different bug report. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 481556] New: Is it possible to configure contact preview
https://bugs.kde.org/show_bug.cgi?id=481556 Bug ID: 481556 Summary: Is it possible to configure contact preview Classification: Applications Product: kaddressbook Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dzevers...@posteo.de Target Milestone: --- SUMMARY *** Unfortunately, I could not found where I have to enter feature requests. Furthermore, I could not find feature request support in help page. Thus, I submitted it as bug report. *** STEPS TO REPRODUCE 1. open kaddressbook 2. select any contact 3. you can see the preview on the right side 4. I wish to add some fields to this preview, e.g. contact group/label OBSERVED RESULT n/a EXPECTED RESULT n/a SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Tuxedo OS2 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 fanzhuyi...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473602] On X11, various applications crash in QXcbBackingStoreImage::flushPixmap when screens change
https://bugs.kde.org/show_bug.cgi?id=473602 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/e9004f723a |ma/kwin/-/commit/437fba0f44 |72b6df09ae14c2936a4c209849e |eca82105a0c63df6d2521a1eb05 |367 |9c6 --- Comment #37 from Zamundaaa --- Git commit 437fba0f44eca82105a0c63df6d2521a1eb059c6 by Xaver Hugl. Committed on 19/02/2024 at 21:24. Pushed by zamundaaa into branch 'Plasma/5.27'. placementtracker: don't set geometry to geometry restores It can cause problems when the geometry restore value is invalid (cherry picked from commit 86db3b43364cd60503e37b91437e0bc25ddfc40d) M +6-13 src/placementtracker.cpp M +1-1src/window.h https://invent.kde.org/plasma/kwin/-/commit/437fba0f44eca82105a0c63df6d2521a1eb059c6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473602] On X11, various applications crash in QXcbBackingStoreImage::flushPixmap when screens change
https://bugs.kde.org/show_bug.cgi?id=473602 Zamundaaa changed: What|Removed |Added Version Fixed In||5.27.11 CC||xaver.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #6 from airisama...@gmail.com --- because of the graphical glitches if I recall correctly the output says it ran out shaders or instructions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481489] kms_swrast DRI not working on i915
https://bugs.kde.org/show_bug.cgi?id=481489 --- Comment #5 from Zamundaaa --- What do you mean with "sometimes you just have to switch to llvmpipe"? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435671] Zoom icons do not use magnifying glass iconography
https://bugs.kde.org/show_bug.cgi?id=435671 --- Comment #40 from Philip Murray --- The +/- symbols in the first four 16px icons, for zoom-(in/out)-(x/y), are smaller than I'd like, but the axis takes up space & then there isn't space to make a 5x5 symbol, hence they are 3x3. I could move the axis to the side & remove their 'notches' but then it is unclear what they are. The zoom-1-to-2 and zoom-2-to-1 don't look quite as nice at 16px. I have used proper double/halving of the rectangles within the zoom circle, but I could make it the small rectangle bigger? but then it wouldn't exactly be a doubling of the dimension. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 --- Comment #10 from Albert Astals Cid --- Git commit 8a6d86ab1961b51ffc9f86ef2ebcbe86a8d4ae3c by Albert Astals Cid, on behalf of Sune Vuorela. Committed on 19/02/2024 at 21:39. Pushed by aacid into branch 'master'. Better user strings for signature settings M +9-4generators/poppler/pdfsettingswidget.cpp https://invent.kde.org/graphics/okular/-/commit/8a6d86ab1961b51ffc9f86ef2ebcbe86a8d4ae3c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481554] Wayland + Nvidia - Extreme stuttering doing anything
https://bugs.kde.org/show_bug.cgi?id=481554 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481553] Dolphin crashes at start
https://bugs.kde.org/show_bug.cgi?id=481553 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481553] Dolphin crashes at start
https://bugs.kde.org/show_bug.cgi?id=481553 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435671] Zoom icons do not use magnifying glass iconography
https://bugs.kde.org/show_bug.cgi?id=435671 --- Comment #39 from Philip Murray --- Created attachment 165943 --> https://bugs.kde.org/attachment.cgi?id=165943=edit Same as before but with 16px versions included -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469878] unhandled instruction bytes: 0x62 0xF1 0x7F 0x48 0x7F 0x44 0x24 0x1 0x83 0xE7
https://bugs.kde.org/show_bug.cgi?id=469878 Martin Kjær Jørgensen changed: What|Removed |Added CC||m...@lagy.org --- Comment #3 from Martin Kjær Jørgensen --- (In reply to tusooa from comment #1) > ==9898== Memcheck, a memory error detector > ==9898== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. > ==9898== Using Valgrind-3.20.0-5147d671e4-20221024 and LibVEX; rerun with -h > for copyright info > ==9898== Command: ls > ==9898== > --9898-- Valgrind options: > --9898---v > --9898-- Contents of /proc/version: > --9898-- Linux version 6.1.27-gentoo-r1-x86_64 (REDACTED@REDACTED) > (x86_64-pc-linux-gnu-gcc (Gentoo 12.2.1_p20230428-r1 p2) 12.2.1 20230428, > GNU ld (Gentoo 2.39 p6) 2.39.0) #1 SMP PREEMPT_DYNAMIC Wed May 10 18:30:00 > EDT 2023 > --9898-- > --9898-- Arch and hwcaps: AMD64, LittleEndian, > amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand-rdseed > --9898-- Page sizes: currently 4096, max supported 4096 > --9898-- Valgrind library directory: /usr/libexec/valgrind > --9898-- Reading syms from /bin/ls > --9898--object doesn't have a symbol table > --9898-- Reading syms from /lib64/ld-linux-x86-64.so.2 > --9898-- Considering /usr/lib/debug/lib64/ld-linux-x86-64.so.2.debug .. > --9898-- .. CRC is valid > --9898-- Reading syms from /usr/libexec/valgrind/memcheck-amd64-linux > --9898--object doesn't have a symbol table > --9898--object doesn't have a dynamic symbol table > --9898-- Scheduler: using generic scheduler lock implementation. > --9898-- Reading suppressions file: /usr/libexec/valgrind/default.supp > ==9898== embedded gdbserver: reading from > /tmp/vgdb-pipe-from-vgdb-to-9898-by-user-on-??? > ==9898== embedded gdbserver: writing to > /tmp/vgdb-pipe-to-vgdb-from-9898-by-user-on-??? > ==9898== embedded gdbserver: shared mem > /tmp/vgdb-pipe-shared-mem-vgdb-9898-by-user-on-??? > ==9898== > ==9898== TO CONTROL THIS PROCESS USING vgdb (which you probably > ==9898== don't want to do, unless you know exactly what you're doing, > ==9898== or are doing some strange experiment): > ==9898== /usr/libexec/valgrind/../../bin/vgdb --pid=9898 ...command... > ==9898== > ==9898== TO DEBUG THIS PROCESS USING GDB: start GDB like this > ==9898== /path/to/gdb ls > ==9898== and then give GDB the following command > ==9898== target remote | /usr/libexec/valgrind/../../bin/vgdb --pid=9898 > ==9898== --pid is optional if only one valgrind process is running > ==9898== > vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7F 0x48 0x7F 0x44 > 0x24 0x1 0x83 0xE7 > vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 > vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE > vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 > ==9898== valgrind: Unrecognised instruction at address 0x401c126. > ==9898==at 0x401C126: _dl_start (rtld.c:566) > ==9898==by 0x401B1D7: ??? (in /lib64/ld-linux-x86-64.so.2) > ==9898== Your program just tried to execute an instruction that Valgrind > ==9898== did not recognise. There are two possible reasons for this. > ==9898== 1. Your program has a bug and erroneously jumped to a non-code > ==9898==location. If you are running Memcheck and you just saw a > ==9898==warning about a bad jump, it's probably your program's fault. > ==9898== 2. The instruction is legitimate but Valgrind doesn't handle it, > ==9898==i.e. it's Valgrind's fault. If you think this is the case or > ==9898==you are not sure, please let us know and we'll try to fix it. > ==9898== Either way, Valgrind will now raise a SIGILL signal which will > ==9898== probably kill your program. > ==9898== > ==9898== Process terminating with default action of signal 4 (SIGILL): > dumping core > ==9898== Illegal opcode at address 0x401C126 > ==9898==at 0x401C126: _dl_start (rtld.c:566) > ==9898==by 0x401B1D7: ??? (in /lib64/ld-linux-x86-64.so.2) > ==9898== > ==9898== HEAP SUMMARY: > ==9898== in use at exit: 0 bytes in 0 blocks > ==9898== total heap usage: 0 allocs, 0 frees, 0 bytes allocated > ==9898== > ==9898== All heap blocks were freed -- no leaks are possible > ==9898== > ==9898== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) > zsh: illegal hardware instruction valgrind -v ls Did you work around your AXV512 issue? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481555] New: HDD doesn't spin down properly on shutdown
https://bugs.kde.org/show_bug.cgi?id=481555 Bug ID: 481555 Summary: HDD doesn't spin down properly on shutdown Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: mashkal2...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY When shutting down the PC, an internal HDD has the power abruptly cut before it can spin down. STEPS TO REPRODUCE 1. Shut down the PC OBSERVED RESULT HDD gets power cut before it stops spinning. This is audible - it sounds exactly like an external HDD being unplugged while it's running. EXPECTED RESULT HDD spins down gradually before losing power ADDITIONAL INFORMATION Started happening a few weeks ago. Not sure what the root cause is. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 --- Comment #11 from Dominic --- (In reply to fanzhuyifan from comment #10) > For the original reporter -- which Qt version are you using? Is this also > fixed for you on Qt 6.6.2? Yes it is, I haven't had any crashes on any of the modules, it's resolved for me, is anyone else still getting crashes? (qt version is 6.6.2) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481541] Pressing the Super(Win) key also opens the KDE application menu, when the mouse, and the keyboard are captured (VMware and Virtualbox)
https://bugs.kde.org/show_bug.cgi?id=481541 --- Comment #9 from neokitty --- (In reply to fanzhuyifan from comment #7) > Would you be able to provide the [ModifierOnlyShortcuts] section in > ~/.config/.kwinrc? > > Do you also have shortcuts for switching virtual desktops, for example? Are > those grabbed? (default to Ctrl+Fx, > Meta+Ctrl+Arrow) > > Thanks! when i press it in vmware, it changes the virtual desktop in the host, when i do the same but in virtualbox it doesnt. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481541] Pressing the Super(Win) key also opens the KDE application menu, when the mouse, and the keyboard are captured (VMware and Virtualbox)
https://bugs.kde.org/show_bug.cgi?id=481541 --- Comment #8 from neokitty --- Created attachment 165942 --> https://bugs.kde.org/attachment.cgi?id=165942=edit There are no such section -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 480797] "PrefersNonDefaultGPU" setting can nonsensically end up preferring the less powerful integrated GPU in cases where the more powerful GPU is the default one
https://bugs.kde.org/show_bug.cgi?id=480797 --- Comment #10 from Berk Elyesa Yıldırım --- So it's technically correct, and not caused by plasma as well To set intel as the default gpu, you should connect to the motherboard display out, but then your purpose of using your amd card for desktop rendering doesn't apply. Maybe there can be an "ignore non-default gpu" global toggle in plasma to support such use cases, though; which would stick with the default gpu, i.e. your amd one here. Adding that as && pre conditional for KIO::hasDiscreteGpu() bool might be the easiest solution? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481554] New: Wayland + Nvidia - Extreme stuttering doing anything
https://bugs.kde.org/show_bug.cgi?id=481554 Bug ID: 481554 Summary: Wayland + Nvidia - Extreme stuttering doing anything Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ashco...@gmail.com Target Milestone: --- SUMMARY *** On a hybrid setup (External monitors connected to NVIDIA GPU, laptop display connected to internal intel GPU), there is extreme stuttering of the UI, GLXGears will run at 1/2 the refresh rate of the displays. *** (Note, on plasma 5.x, using `KWIN_DRM_USE_MODIFIERS=0` would resolve this issue, but in 6.x, either this env. variable is ignored, or does nothing) I've attached a video showing this issue, both my external monitors are 120Hz, and the laptops own display is 144Hz, so theoretically, the minimum framerate I should get is 120Hz, but, you can see when doing anything like moving windows around, the glxgear window stutters and framerate drops significantly1. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481533] Some pinned popups move weirdly when floating panel defloats
https://bugs.kde.org/show_bug.cgi?id=481533 Niccolò Venerandi changed: What|Removed |Added Ever confirmed|0 |1 CC||nicc...@venerandi.com Status|REPORTED|CONFIRMED --- Comment #1 from Niccolò Venerandi --- Agh, can confirm -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481553] New: Dolphin crashes at start
https://bugs.kde.org/show_bug.cgi?id=481553 Bug ID: 481553 Summary: Dolphin crashes at start Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: nicolas.fe...@gmx.de CC: kfm-de...@kde.org Target Milestone: --- #0 QTimer::stop (this=0x0) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qtimer.cpp:240 #1 0x757d7c88 in QWidget::event (this=0xcf1760, event=0x7fffcfe0) at /home/nico/workspace/qt6/qtbase/src/widgets/kernel/qwidget.cpp:9375 #2 0x75781a71 in QApplicationPrivate::notify_helper (this=, receiver=0xcf1760, e=0x7fffcfe0) at /home/nico/workspace/qt6/qtbase/src/widgets/kernel/qapplication.cpp:3298 #3 0x7455f1b8 in QCoreApplication::notifyInternal2 (receiver=0xcf1760, event=0x7fffcfe0) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qcoreapplication.cpp:1134 #4 0x7455f379 in QCoreApplication::sendEvent (receiver=, event=) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qcoreapplication.cpp:1575 #5 0x757d2cff in QWidgetPrivate::hide_helper (this=this@entry=0xd1c9e0) at /home/nico/workspace/qt6/qtbase/src/widgets/kernel/qwidget.cpp:8240 #6 0x757d6bba in QWidgetPrivate::setVisible (this=0xd1c9e0, visible=) at /home/nico/workspace/qt6/qtbase/src/widgets/kernel/qwidget.cpp:8433 #7 0x0046ea63 in DolphinViewContainer::DolphinViewContainer (this=this@entry=0xcd8400, url=..., parent=) at /home/nico/kde/src/dolphin/src/dolphinviewcontainer.cpp:82 #8 0x0047923c in DolphinTabPage::createViewContainer (this=this@entry=0xce3330, url=...) at /home/nico/kde/src/dolphin/src/dolphintabpage.cpp:458 #9 0x0047b03d in DolphinTabPage::DolphinTabPage (this=this@entry=0xce3330, primaryUrl=..., secondaryUrl=..., parent=parent@entry=0xa1dad0) at /home/nico/kde/src/dolphin/src/dolphintabpage.cpp:35 #10 0x0047dc90 in DolphinTabWidget::openNewTab (this=this@entry=0xa1dad0, primaryUrl=, secondaryUrl=, position=position@entry=DolphinTabWidget::NewTabPosition::FollowSetting) at /home/nico/kde/src/dolphin/src/dolphintabwidget.cpp:169 #11 0x0047def3 in DolphinTabWidget::openNewActivatedTab (this=0xa1dad0, primaryUrl=, secondaryUrl=) at /home/nico/kde/src/dolphin/src/dolphintabwidget.cpp:157 #12 0x0047e58b in DolphinTabWidget::openDirectories (this=0xa1dad0, dirs=..., splitView=splitView@entry=false) at /home/nico/kde/src/dolphin/src/dolphintabwidget.cpp:226 #13 0x00451e6c in DolphinMainWindow::openDirectories (this=this@entry=0x8056a0, dirs=..., splitView=splitView@entry=false) at /home/nico/kde/src/dolphin/src/dolphinmainwindow.cpp:248 #14 0x0044aa33 in main (argc=, argv=) at /home/nico/kde/src/dolphin/src/main.cpp:204 SOFTWARE/OS VERSIONS KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 6.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481020] Turn off individual sources/backends
https://bugs.kde.org/show_bug.cgi?id=481020 --- Comment #2 from matterhorn...@proton.me --- (In reply to Nate Graham from comment #1) > The way you can do this is by uninstalling the PackageKit backend. Can you > see if that meets your needs? It does meet my personal needs. But a toggle in the GUI would be more user-friendly, more elegant, and more discoverable, no pun intended :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481045] Crash (sometimes) in QQmlMetaType::propertyCache when going to a different KCM in Energy Saving > Advanced Power Settings
https://bugs.kde.org/show_bug.cgi?id=481045 --- Comment #5 from Jakob Petsovits --- "Partial" success: If we forcibly delete each subPage of KQuickConfigModule (e.g. by deleting any object returned by takeLast() in ~KQuickConfigModule(), or by parenting a subPage to the already slated-for-deletion d->engine->rootObject()), then page transitions stop crashing while System Settings operates. However, it will crash when trying to close it because apparently QQmlEngine keeps other references to those objects around and they will derefence a freed object on QQmlEngine destruction. Hopefully there's a way to remove these subPage items from the QQmlEngine in some other way that leaves no dangling pointers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481488] Plasmashell crashes when attempting to use Open With -> Other Application... through the notification
https://bugs.kde.org/show_bug.cgi?id=481488 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-integration/-/merge_requests/139 -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 481546] Crash at the end of a game with 2 CPU players
https://bugs.kde.org/show_bug.cgi?id=481546 --- Comment #2 from dawid.trend...@gmail.com --- (In reply to Albert Astals Cid from comment #1) > Can you reproduce this all the time? > > Are you working on it like on the other crash or you need help with this one? I was able to reproduce it all the time. I am working on it. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 456643] Collapsing/uncollapsing room category moves slider all the way up
https://bugs.kde.org/show_bug.cgi?id=456643 James Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/neochat/-/commit/fc6ea0 ||b7791a694e57abdab74f1a47173 ||9769631 --- Comment #2 from James Graham --- Git commit fc6ea0b7791a694e57abdab74f1a471739769631 by James Graham, on behalf of Tobias Fella. Committed on 19/02/2024 at 20:09. Pushed by nvrwhere into branch 'master'. Port RoomList to TreeView Use a tree model for the room list closes network/neochat#156 M +6-0src/CMakeLists.txt A +97 -0src/enums/neochatroomtype.h [License: LGPL(v2.0+)] M +1-91 src/models/roomlistmodel.cpp M +2-53 src/models/roomlistmodel.h A +323 -0src/models/roomtreemodel.cpp [License: LGPL(v2.0+)] A +94 -0src/models/roomtreemodel.h [License: LGPL(v2.0+)] M +5-108 src/models/sortfilterroomlistmodel.cpp M +0-53 src/models/sortfilterroomlistmodel.h A +161 -0src/models/sortfilterroomtreemodel.cpp [License: GPL(v2.0+)] C +4-3src/models/sortfilterroomtreemodel.h [from: src/models/sortfilterroomlistmodel.h - 092% similarity] M +2-2src/neochatconnection.cpp M +1-1src/neochatroom.cpp M +1-1src/neochatroom.h M +1-2src/qml/ChooseRoomDialog.qml M +4-1src/qml/ExploreComponent.qml M +1-2src/qml/QuickSwitcher.qml M +13 -25 src/qml/RoomDelegate.qml M +128 -197 src/qml/RoomListPage.qml M +1-6src/qml/RoomPage.qml A +83 -0src/qml/RoomTreeSection.qml [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] M +8-0src/runner.cpp M +1-1src/runner.h M +2-1src/spacehierarchycache.cpp https://invent.kde.org/network/neochat/-/commit/fc6ea0b7791a694e57abdab74f1a471739769631 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 476291] Neochat forgets that I scrolled down
https://bugs.kde.org/show_bug.cgi?id=476291 James Graham changed: What|Removed |Added CC||sfal...@cloverleaf-linux.or ||g --- Comment #1 from James Graham --- *** Bug 481088 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 481088] Neochat Doesn't remember scroll position
https://bugs.kde.org/show_bug.cgi?id=481088 James Graham changed: What|Removed |Added CC||james.h.graham@protonmail.c ||om Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from James Graham --- *** This bug has been marked as a duplicate of bug 476291 *** -- You are receiving this mail because: You are watching all bug changes.
