[frameworks-kglobalaccel] [Bug 451070] New: Starting some application does not bring them to focus, when opening in other Activities
https://bugs.kde.org/show_bug.cgi?id=451070 Bug ID: 451070 Summary: Starting some application does not bring them to focus, when opening in other Activities Product: frameworks-kglobalaccel Version: 5.91.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: tervat...@gmail.com Target Milestone: --- SUMMARY I have set up Activities: www, sys, kodi, game I have applications set up, so they open up in their own Activities: - kodi opens in "kodi" activity - goverlay opens in "game" activity - steam opens in "game" activity When starting applications, either via shortcut (for example Ctrl+Alt+4 for kodi), or in Krunner, applications do start in their own activity, but the activity is not switched to automatically. Applications that DO work and switch to their own activity, are: -firefox opens in "www" activity and takes focus -Dolphin opens in "sys" activity and takes focus -Konsole opens in "sys" activity and takes focus STEPS TO REPRODUCE 1. Create an activity and name it "game" 1. Go to Window Management -> Window Rules -> Add New 2. Window class (application) -> Exact match -> steam 3. Add Property -> Size & Position -> double click Activities 4. Assign to "game" activity 5. Go to some other activity than "game" 6. Start Steam with Global Menu or Krunner or a custom shortcut (doesn't matter which) OBSERVED RESULT Steam starts up in "game" activity, but the focus is still in the other activity EXPECTED RESULT Steam starts up in "game" activity and switches automatically to "game" activity SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.11 KDE Plasma Version: 5.24.2 (Wayland) KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450794] Hidden side panel settings
https://bugs.kde.org/show_bug.cgi?id=450794 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1496 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 451069] New: VPN password input sanitizer
https://bugs.kde.org/show_bug.cgi?id=451069 Bug ID: 451069 Summary: VPN password input sanitizer Product: plasma-nm Version: 5.24.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: ilario.gottarde...@gmail.com Target Milestone: --- SUMMARY When entering a password for a VPN connection, cariage return will not be removed so a simple double click - middle button copy-paste will fail. STEPS TO REPRODUCE 1. Connect to a VPN (in my case OpenVPN) 2. copy-paste the password from a text file 3. Connection will fail because of wrong password OBSERVED RESULT Cariage return is pasted and considered a character of the password EXPECTED RESULT Invalid characters should be stripped SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.24 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I know passwords should not be saved in text files and so on, but it is like it is. The same password is used to connect to Teams and selecting it double clicking the line and pasting with middle button works as expected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451068] New: Password overwritten by 2FA pin
https://bugs.kde.org/show_bug.cgi?id=451068 Bug ID: 451068 Summary: Password overwritten by 2FA pin Product: systemsettings Version: 5.24.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_netpref Assignee: plasma-b...@kde.org Reporter: ilario.gottarde...@gmail.com Target Milestone: --- SUMMARY When logging in to my corporate VPN (openvpn) with 2FA, the password saved in the settings (not encrypted) will be overwritten by the PIN I must enter. The next time I will log in, it will fail because of wrong password, so I have to either go every time to the settings and restore the right password, or not save it at all and enter it when connecting. STEPS TO REPRODUCE 1. Configure an OpenVPN connection with username and password and save it unencrypted 2. Connect to the VPN server, entering the PIN OBSERVED RESULT The "password" field in the settings will be overwritten by the PIN and the next time you will log in you must reset it EXPECTED RESULT Password fild should remain untouched SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.24 (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION This behavious seems to NOT occour if the password is stored encrypted. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 451047] Fatal error: Error while installing package: 0.0000 while updating, unable to upgrade
https://bugs.kde.org/show_bug.cgi?id=451047 --- Comment #2 from nttkde --- Happened on KDE Neon. First try the error number was 42.??? or 47.??? I think (not sure), then 0.. sudo dpkg --configure -a sudo pkcon update was enough to fix it for me. Also https://old.reddit.com/r/kdeneon/comments/t51rnr/pkcon_update_then_fatal_error_error_while/ -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
https://bugs.kde.org/show_bug.cgi?id=372116 Celeste changed: What|Removed |Added CC||coelacant...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451054] Systemsettings don't open after latest update
https://bugs.kde.org/show_bug.cgi?id=451054 --- Comment #3 from Marek --- Created attachment 147252 --> https://bugs.kde.org/attachment.cgi?id=147252=edit QT_DEBUG_PLUGINS=1 systemsettings > /tmp/debug.txt 2>&1 The output looks OK to me. Still no indication why the plugins are not loaded. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451067] New: Mouse reversed scrolling is wrong after system wakes up
https://bugs.kde.org/show_bug.cgi?id=451067 Bug ID: 451067 Summary: Mouse reversed scrolling is wrong after system wakes up Product: kwin Version: 5.24.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: kdeaa...@iforgotmy.name Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. For Mouse settings, check Invert scroll direction 2. Suspend system 3. Wake up system 4. Scroll with the mouse wheel OBSERVED RESULT Scrolling is not inverted. EXPECTED RESULT Scrolling direction is inverted. Note: unchecking "Invert scroll direction", applying, then checking, and applying again, temporarily fixes the issue only until the system is suspended again. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450914] Wayland, games on Nvidia are force vsynced
https://bugs.kde.org/show_bug.cgi?id=450914 Samuel changed: What|Removed |Added CC||samping...@gmail.com --- Comment #3 from Samuel --- (In reply to Alexander Streng from comment #2) > Ah, I just thought that it might be a bug with kwin since I've heard that > Gnome doesn't have this issue in Wayland session 樂 Yes. GNOME Wayland doesnt have this issue. I doubt if this is really a upstream bug. https://www.youtube.com/watch?v=mATihNvCizY -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448839] [NVIDIA Wayland] Task Manager's tooltip window thumbnails are black
https://bugs.kde.org/show_bug.cgi?id=448839 --- Comment #11 from Samuel --- (In reply to Michael D from comment #10) > to me once so far. Are yours always like that? Yup. Its always like that, no matter what application I open or how many times I restart plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450065] Custom default look and feel isn't fully applying on Plasma 5.24, in particular the panel theme
https://bugs.kde.org/show_bug.cgi?id=450065 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #4 from Nate Graham --- https://bugzilla.redhat.com/show_bug.cgi?id=2053790 seems to be closed now; did you work around this with a packaging change, or was there some leftover upstream patch that needed to be cleared out? Or something else? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451066] New: VSync is forced in Plasma Wayland session with disabled in-game VSync [NVIDIA].
https://bugs.kde.org/show_bug.cgi?id=451066 Bug ID: 451066 Summary: VSync is forced in Plasma Wayland session with disabled in-game VSync [NVIDIA]. Product: kwin Version: 5.24.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: samping...@gmail.com Target Milestone: --- SUMMARY When the in-game VSync is disabled, KWin forces VSync but while in GNOME Wayland session, this doesnt happen. STEPS TO REPRODUCE 1. Open a Game which has option to disable in-game VSync. 2. Go to settings and disable VSync. 3. Check the FPS using Mangohud or DXVK HUD. The FPS is still capped to display refresh rate. OBSERVED RESULT Here is the video showcasing this VSync forced by KWin and compared to GNOME Wayland session:- https://www.youtube.com/watch?v=mATihNvCizY . You can clearly see that the FPS is capped in Plasma Wayland session while its uncapped in GNOME Wayland session with the same in-game settings (VSync disabled). EXPECTED RESULT The FPS should be uncapped like in the GNOME Wayland session when in-game VSync is disabled. SOFTWARE/OS VERSIONS Linux Kernel: 5.16.11 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91 Qt Version: 5.15.2 ADDITIONAL INFORMATION NVIDIA Proprietary Driver 510.54 YouTube Video showcasing the issue:- https://www.youtube.com/watch?v=mATihNvCizY -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 446333] `rz` keeps refreshing the file picker dialog
https://bugs.kde.org/show_bug.cgi?id=446333 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #1 from Roy --- I get the same thing, but running _Edit > Zmodem Upload_ from the main menu, without running `rz` first, uploads a file correctly for me. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450623] Upgrade to Plasma 5.24.1 using `kubuntu-ppa/backports` causes no users to appear on the users page of System Settings.
https://bugs.kde.org/show_bug.cgi?id=450623 --- Comment #6 from Nate Graham --- Or, if you like the Ubuntu core and can tolerate old non-KDE software, KDE Neon user edition might be more to your liking/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450623] Upgrade to Plasma 5.24.1 using `kubuntu-ppa/backports` causes no users to appear on the users page of System Settings.
https://bugs.kde.org/show_bug.cgi?id=450623 --- Comment #5 from Nate Graham --- Seems like files were left over from 5.24; probably more mis-packaging. In general, if you want the latest Plasma version (or the latest version of anything), Kubuntu isn't going to be the best distro for you. You might be happier with Fedora KDE, Manjaro Plasma, or openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443745] discover segmentation fault in FlatpakBackend::findSource
https://bugs.kde.org/show_bug.cgi?id=443745 landgraf...@yandex.ru changed: What|Removed |Added CC||landgraf...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 448785] plasma(wayland) crash every time at login
https://bugs.kde.org/show_bug.cgi?id=448785 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #17 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450372] Gaps in system tray battery and brightness section
https://bugs.kde.org/show_bug.cgi?id=450372 --- 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.
[krita] [Bug 450363] Pen bug
https://bugs.kde.org/show_bug.cgi?id=450363 --- 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 447938] KDE resets the desktop layout in login/bootup when the monitor is 165hz
https://bugs.kde.org/show_bug.cgi?id=447938 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450322] numpad stops working after changing keyboard delay/rate
https://bugs.kde.org/show_bug.cgi?id=450322 --- 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.
[plasmashell] [Bug 450124] The arm64 platform turned the monitor back on causing kde desktop to crash
https://bugs.kde.org/show_bug.cgi?id=450124 --- 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 450284] Kwin Zoom effect no longer working after updating to latest plasma
https://bugs.kde.org/show_bug.cgi?id=450284 --- 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.
[krita] [Bug 449379] Krita 5 random crashes
https://bugs.kde.org/show_bug.cgi?id=449379 --- 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 444510] Mouse cursor acts weird with flat acceleration profile in plasma-wayland
https://bugs.kde.org/show_bug.cgi?id=444510 pete changed: What|Removed |Added CC||hayy...@protonmail.com Version|5.23.2 |5.24.2 --- Comment #4 from pete --- I can confirm this still happens on 5.24.2. On X, the pointer moves exactly as expected with the flat acceleration profile and the speed can be adjusted with the slider. On Wayland, it seems to use the adaptive profile but both the slider and profile options appear to have no effect. I hope this is seen soon by one of our lovely devs, I can imagine it being a big deal for people new that are new to KDE on distros where Wayland is the default (15-min bug?). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451065] New: Logging out of Plasma on Wayland sometimes resulted in a black screen and plasmashell, powerdevil, and xde-desktop-portal-kde aborts
https://bugs.kde.org/show_bug.cgi?id=451065 Bug ID: 451065 Summary: Logging out of Plasma on Wayland sometimes resulted in a black screen and plasmashell, powerdevil, and xde-desktop-portal-kde aborts Product: plasmashell Version: 5.24.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: 1.0 Created attachment 147251 --> https://bugs.kde.org/attachment.cgi?id=147251=edit journal for a boot where the black screen problem happened with the xdg-desktop-portal-kde crashes. SUMMARY Logging out of Plasma 5.24.2 on Wayland in a Fedora 36 KDE Plasma installation sometimes showed a black screen with a blinking underscore _ at the top left of the screen. This black screen problem happened about 20-30% of the time when logging out. plasmashell and powerdevil aborted usually 5 times each on some such logouts with errors that the Wayland connection had broken. xdg-desktop-portal-kde aborted multiple times on other logouts with the same errors. Traces of plasmashell and xdg-desktop-portal-kde crashes are the following. Core was generated by `/usr/bin/plasmashell --no-respawn'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7efe10755f43 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7efe10705a36 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7efe106ef82f in __GI_abort () at abort.c:79 #4 0x7efe10bb4517 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #5 QMessageLogger::fatal (this=this@entry=0x7ffdf43de820, msg=msg@entry=0x7efe115ea407 "%s") at global/qlogging.cpp:893 #6 0x7efe111f60ef in init_platform (argv=, argc=, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at kernel/qguiapplication.cpp:1254 #7 QGuiApplicationPrivate::createPlatformIntegration (this=0x55f08fd64ed0) at kernel/qguiapplication.cpp:1474 #8 0x7efe111f65c8 in QGuiApplicationPrivate::createEventDispatcher (this=) at kernel/qguiapplication.cpp:1491 #9 0x7efe10db2be1 in QCoreApplicationPrivate::init (this=this@entry=0x55f08fd64ed0) at kernel/qcoreapplication.cpp:835 #10 0x7efe111f8973 in QGuiApplicationPrivate::init (this=this@entry=0x55f08fd64ed0) at kernel/qguiapplication.cpp:1520 #11 0x7efe11a8672d in QApplicationPrivate::init (this=0x55f08fd64ed0) at kernel/qapplication.cpp:513 #12 0x55f08fb330a0 in main (argc=, argv=0x7ffdf43ded88) --Type for more, q to quit, c to continue without paging--c at /usr/src/debug/plasma-workspace-5.24.2-1.fc36.x86_64/shell/main.cpp:82 Core was generated by `/usr/libexec/xdg-desktop-portal-kde'. Missing separate debuginfos, use: dnf debuginfo-install xdg-desktop-portal-kde-5.24.2-1.fc36.x86_64 --Type for more, q to quit, c to continue without paging-- Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f028b20dea3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7f028b1bda16 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7f028b1a782f in __GI_abort () at abort.c:79 #4 0x7f028b66c517 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #5 QMessageLogger::fatal (this=this@entry=0x7ffd17e9bf70, msg=msg@entry=0x7f028c89a407 "%s") at global/qlogging.cpp:893 #6 0x7f028c4a60ef in init_platform (argv=, argc=, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at kernel/qguiapplication.cpp:1254 #7 QGuiApplicationPrivate::createPlatformIntegration (this=0x56223197cb20) at kernel/qguiapplication.cpp:1474 #8 0x7f028c4a65c8 in QGuiApplicationPrivate::createEventDispatcher (this=) at kernel/qguiapplication.cpp:1491 #9 0x7f028b86abe1 in QCoreApplicationPrivate::init (this=this@entry=0x56223197cb20) at kernel/qcoreapplication.cpp:835 #10 0x7f028c4a8973 in QGuiApplicationPrivate::init (this=this@entry=0x56223197cb20) at kernel/qguiapplication.cpp:1520 #11 0x7f028d09672d in QApplicationPrivate::init
[Breeze] [Bug 442628] Breeze Dark: menubar and toolbar background not switching colours for inactive/active windows
https://bugs.kde.org/show_bug.cgi?id=442628 --- Comment #11 from Oliver Freyermuth --- (In reply to Prajna Sariputra from comment #10) > I'm now on Plasma 5.24.2 and Frameworks 5.91.0, and the issue appears to > have resolved itself somehow. Thanks, that makes me hopeful for when these versions are marked as stable on Gentoo (they are already in the repositories, but not stabilized yet). Concerning the issue, it would of course be ideal in case we'd find the causing or fixing commit to allow for potential backports to LTS distros. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 451064] New: Kalendar App doesn't sync with Google Calendar
https://bugs.kde.org/show_bug.cgi?id=451064 Bug ID: 451064 Summary: Kalendar App doesn't sync with Google Calendar Product: kalendar Version: 1.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: t...@balter.io CC: c...@carlschwan.eu Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Add new event to Kalendar app locally or new event to Google Calendar OBSERVED RESULT New event does not sync EXPECTED RESULT If the new event was created with Google Calendar, Kalendar should detect this and download the new event. If the new event was created with Kalendar, it should push the new event to Google Calendar. SOFTWARE/OS VERSIONS Linux: ArchLinux x86_64 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION When initially setting up the Google Calendar integration, all events and tasks etc appear to show as normal. When adding a new event or task to either medium (Google or Kalendar) the changes do not sync across devices. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 451063] New: Pasting a selection creates an invisible pasted layer on canvas
https://bugs.kde.org/show_bug.cgi?id=451063 Bug ID: 451063 Summary: Pasting a selection creates an invisible pasted layer on canvas Product: krita Version: nightly build (please specify the git hash!) Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- SUMMARY Pasting a selection creates an invisible pasted layer on canvas. Although the pasted layer's visibility is ON, you must toggle the layer's visibility once to make it visible. Tested with appimages of 2022-03-03: [AFFECTED] krita-5.1.0-prealpha-9a8840cd8e-x86_64.appimage [UNAFFECTED] krita-5.0.2-alpha-da37c21fd2-x86_64.appimage STEPS TO REPRODUCE 1. Create a new document 2. Fill a layer with solid color with Shift+Backspace 3. Create a selection, Ctrl+X 4. Ctrl+V, the content has been pasted into a new layer 5. You can see the pasted layer's content from the Layer docker, but nothing is shown on canvas 6. Toggle the pasted layer's visiblity once 7. Now it is visible on canvas NOTES The triggering condition of this bug seems elusive. Sometimes I can paste just fine, sometimes I had to paste inside of a group to trigger it. All tests were conducted on new documents and new instances of Krita. This bug has been around for at least a month. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426047] Crash in KQuickAddons::ConfigModule::~ConfigModule() for multiple System Settings KCMs
https://bugs.kde.org/show_bug.cgi?id=426047 --- Comment #36 from Tony --- (In reply to Nate Graham from comment #35) > From Bug 450164, it seems that installing the package that provides > qqmldata_p.h may fix it. Is anyone else able to reproduc ethat? Can't find that file on my system nor within a package on tumblewed, i have not hit this bug in a long time though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450910] Plasma config got reset when my PC crashed
https://bugs.kde.org/show_bug.cgi?id=450910 --- Comment #4 from techxga...@outlook.com --- It also can't be removed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450910] Plasma config got reset when my PC crashed
https://bugs.kde.org/show_bug.cgi?id=450910 --- Comment #3 from techxga...@outlook.com --- $ ll .config/plasma-org.kde.plasma.desktop-appletsrc* ls: cannot access '.config/plasma-org.kde.plasma.desktop-appletsrc.lock': No such file or directory ls: cannot access '.config/plasma-org.kde.plasma.desktop-appletsrc.lock': No such file or directory ls: cannot access '.config/plasma-org.kde.plasma.desktop-appletsrc.lock': No such file or directory ls: cannot access '.config/plasma-org.kde.plasma.desktop-appletsrc.lock': No such file or directory -rw--- 1 yamiyuki yamiyuki 9545 Mar 2 20:39 .config/plasma-org.kde.plasma.desktop-appletsrc -rw--- 1 yamiyuki yamiyuki 9545 Mar 2 20:39 .config/plasma-org.kde.plasma.desktop-appletsrc -rw--- 1 yamiyuki yamiyuki 9545 Mar 2 20:39 .config/plasma-org.kde.plasma.desktop-appletsrc -rw--- 1 yamiyuki yamiyuki 9545 Mar 2 20:39 .config/plasma-org.kde.plasma.desktop-appletsrc I double checked my laptop (also running Plasma) , and it didn't have repeated entries, and a lock file. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 214606] support for personal video collections
https://bugs.kde.org/show_bug.cgi?id=214606 Robby Stephenson changed: What|Removed |Added CC||wettererscheinung@bb-goetti ||ngen.de --- Comment #6 from Robby Stephenson --- *** Bug 380815 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 380815] Improving file catalog import for video-files: Video-only option + folder structure detection + Cover/srt detection
https://bugs.kde.org/show_bug.cgi?id=380815 Robby Stephenson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Robby Stephenson --- *** This bug has been marked as a duplicate of bug 214606 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450910] Plasma config got reset when my PC crashed
https://bugs.kde.org/show_bug.cgi?id=450910 --- Comment #2 from techxga...@outlook.com --- $ find . -name "*appletsrc*" ./.config/plasmoidviewer-appletsrc ./.config/plasma-org.kde.plasma.desktop-appletsrc.lock ./.config/plasma-org.kde.plasma.desktop-appletsrc ./.config/plasma-org.kde.plasma.desktop-appletsrc.lock ./.config/plasma-org.kde.plasma.desktop-appletsrc ./.config/plasma-org.kde.plasma.desktop-appletsrc.lock ./.config/plasma-org.kde.plasma.desktop-appletsrc ./.config/plasma-org.kde.plasma.desktop-appletsrc.lock ./.config/plasma-org.kde.plasma.desktop-appletsrc Not sure if that's supposed to be normal? -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 450260] bug: save/save as
https://bugs.kde.org/show_bug.cgi?id=450260 Robby Stephenson changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Robby Stephenson --- With the contributed installer for Tellico 3.4.4, it appears this bug is not present. Please re-open for Windows if you do see it re-occur. https://tellico-project.org/tellico-3-4-4-for-windows/ -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 450061] windows version: translations missing
https://bugs.kde.org/show_bug.cgi?id=450061 --- Comment #2 from Robby Stephenson --- With the contributed installer for Tellico 3.4.4, it appears translations are available in the installation. https://tellico-project.org/tellico-3-4-4-for-windows/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426937] kded5: Segmentation fault when I plug in controller with touchpad using xf86-input-libinput
https://bugs.kde.org/show_bug.cgi?id=426937 Nicolas Fella changed: What|Removed |Added CC||kyria...@mypcrevolution.com --- Comment #6 from Nicolas Fella --- *** Bug 409073 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 409073] Connecting a bluetooth device is crashing systemtray
https://bugs.kde.org/show_bug.cgi?id=409073 Nicolas Fella changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||nicolas.fe...@gmx.de --- Comment #6 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 426937 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 451013] missing dependencies for updates
https://bugs.kde.org/show_bug.cgi?id=451013 Stephen Burton changed: What|Removed |Added CC||sjburto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 451062] New: Subscripts and superscripts do not display when I export images
https://bugs.kde.org/show_bug.cgi?id=451062 Bug ID: 451062 Summary: Subscripts and superscripts do not display when I export images Product: LabPlot2 Version: 2.8.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: hda...@mail.wu.ac.th Target Milestone: --- Created attachment 147250 --> https://bugs.kde.org/attachment.cgi?id=147250=edit This is a plot of magnetic data 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. 2. 3. OBSERVED RESULT No superscripts or subscripts EXPECTED RESULT Proper titles SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451061] Menu lines become invisible until hovering them on a scaled screen (wayland)
https://bugs.kde.org/show_bug.cgi?id=451061 Andrew Shark changed: What|Removed |Added URL||https://youtu.be/qtAlEZGW3_ ||o -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451061] New: Menu lines become invisible until hovering them on a scaled screen (wayland)
https://bugs.kde.org/show_bug.cgi?id=451061 Bug ID: 451061 Summary: Menu lines become invisible until hovering them on a scaled screen (wayland) Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ash...@linuxcomp.ru CC: k...@davidedmundson.co.uk Target Milestone: 1.0 In wayland session (x11 is normal), if the screen has scaling (if no scaling, then it is normal), the menu lines are disappearing (shown as black rectangles) when you start moving mouse, until you hover a cursor over lines. Steps to reproduce: 1. Apply screen scaling, for example, make it 200%. 2. Click volume applet, then click some menu (cheeseburger icon) of any audio device or application 3. The menu will open. 4. Start moving mouse over menu elements Observed result: After step 3, the menu elements are visible (they appear on dark background, but I think that is separate bug with transparrency/blur, probably unrelated to current bug). At step 4, when you start moving mouse to the menu window, you will notice that menu lines are now invisible (shown as black rectangles). But they become visible again and stay visible after you hover over them. And the special lines like separators are not able to become visible. Expected result: At step 4 the menu lines should not become invisible. See attached video demonstation. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451059] Okular freezes for up to 10 seconds when loading a document or switching windows
https://bugs.kde.org/show_bug.cgi?id=451059 --- Comment #5 from Amaury Pouly --- (In reply to Albert Astals Cid from comment #4) > I just tried with 32 okular instances open and the canOpenDocs elapsed time > for all the instances when opening a new one never took more than 75ms > (tried 20 times or so), which makes sense, canOpenDocs should be very fast > since it do much. > > When you say "open a new document", how exactly are you opening it? > > Any peculiarity of your system that you think may cause this? Remote NFS > file system? weird libc? weird dbus rules? I usually either open it using Dolphin or using Zotero, but it can also happen just when switching between virtual desktops and not opening anything (less common though). Everything is local (not NFS), nothing particularly custom, no special dbus rules. When it happens, switching between virtual desktops is a often a trigger. For example: 1) open file A.pdf => fast 2) switch to other virtual desktop 3) open file A.pdf => slow 4) close it, open A.pdf => fast 5) switch to other virtual desktop 6) open A.pdf => slow -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450623] Upgrade to Plasma 5.24.1 using `kubuntu-ppa/backports` causes no users to appear on the users page of System Settings.
https://bugs.kde.org/show_bug.cgi?id=450623 --- Comment #4 from Freddie --- Sorry to add another comment so late, but I've decided to downgrade back to 5.22, but the before picture is still what shows when I open the users page. Do you have any idea why this might be? -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 450931] Screencasting full screen games does not work (screencast is black or frozen on last frame)
https://bugs.kde.org/show_bug.cgi?id=450931 --- Comment #4 from Aleix Pol --- Clearly. My bad, thanks Nico. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444043] Make Breeze Light and Breeze Dark Plasma themes respect accent color (not full color scheme, just accent color)
https://bugs.kde.org/show_bug.cgi?id=444043 Timothy B changed: What|Removed |Added CC||yule2...@live.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451059] Okular freezes for up to 10 seconds when loading a document or switching windows
https://bugs.kde.org/show_bug.cgi?id=451059 --- Comment #4 from Albert Astals Cid --- I just tried with 32 okular instances open and the canOpenDocs elapsed time for all the instances when opening a new one never took more than 75ms (tried 20 times or so), which makes sense, canOpenDocs should be very fast since it do much. When you say "open a new document", how exactly are you opening it? Any peculiarity of your system that you think may cause this? Remote NFS file system? weird libc? weird dbus rules? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426937] kded5: Segmentation fault when I plug in controller with touchpad using xf86-input-libinput
https://bugs.kde.org/show_bug.cgi?id=426937 Nicolas Fella changed: What|Removed |Added Product|frameworks-kded |systemsettings Version|5.74.0 |5.24.2 CC||nicolas.fe...@gmx.de Component|general |kcm_touchpad Assignee|fa...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 426937] kded5: Segmentation fault when I plug in controller with touchpad using xf86-input-libinput
https://bugs.kde.org/show_bug.cgi?id=426937 Nicolas Fella changed: What|Removed |Added CC||dh_log...@posteo.de --- Comment #5 from Nicolas Fella --- *** Bug 451045 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451045] kded5 crashes when connecting PS5 Dualsense controller via Bluetooth
https://bugs.kde.org/show_bug.cgi?id=451045 Nicolas Fella changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 426937 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451060] New: don't force user to go command-line to get SmartCard signing to work.
https://bugs.kde.org/show_bug.cgi?id=451060 Bug ID: 451060 Summary: don't force user to go command-line to get SmartCard signing to work. Product: okular Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: ludwig.m...@gmail.com Target Milestone: --- Add GUI button in Settings -> Configure Backends -> PDF: ["Add Security Device"] *** 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 *** Before I resolved my problem, the okular error message when trtying to add a signature was cryptic. It found the Certificate Database, but it didnt automatically contain the security device (just like say firefox doesnt out of the box), but Okular does not provide a GUI means of adding the security device .so module (whereas Firefox does). Currently the user is expected to have already added the to the certificate database, say through firefox, where there is a button security devices, and then add/load where you can give: * a pretty name for the security device * the location of the relevant security device library (in my case /usr/lib/opensc-pkcs11.so This can be found by running say: p11-kit list-modules and then using find / -name on the opensc .so Wondering what firefox was doing under the hood, I found it at: https://gist.github.com/PhilipSchmid/a82b9642e1ec2bf2d16823d72cffc589 so I ran the following command: modutil -dbdir $HOME/.pki/nssdb/ -add "Mijn eID" -libfile "/usr/lib/opensc-pkcs11.so" -force and probably unnecessarily also the command modutil -dbdir $HOME/.pki/nssdb/ -enable "Mijn eID" -force I say unnecessarily because according to arch-wiki instructions for FireFox and Chromium: https://wiki.archlinux.org/title/Smartcards#Configuration It seems unneccesary to run the -enable command for Chromium (whereas FireFox does these commands under the hood, and shows GUI method, what I request for Okular) I would also like to note that it doesn't seem necessary to install the government supplied middleware at all! OpenSC works. The only weird thing was that I had to select the authentication certificate, it seemed to ask an extra password for the signing certificate but my PIN code did not work! Whereas it worked for the authentication certificate... I think the middlewares of all the different countries are just de-quirking the non-compliance with smartcard standards? my apologies for my messy submisssion, I am not familiar with reporting bugs/wishes... STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451045] kded5 crashes when connecting PS5 Dualsense controller via Bluetooth
https://bugs.kde.org/show_bug.cgi?id=451045 Nicolas Fella changed: What|Removed |Added Version|5.91.0 |5.24.2 Product|frameworks-kded |systemsettings Component|general |kcm_touchpad Assignee|fa...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 451045] kded5 crashes when connecting PS5 Dualsense controller via Bluetooth
https://bugs.kde.org/show_bug.cgi?id=451045 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- #0 0x7efcc0c9334c __pthread_kill_implementation (libc.so.6 + 0x8f34c) #1 0x7efcc0c464b8 raise (libc.so.6 + 0x424b8) #2 0x7efcc1d49384 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7384) #3 0x7efcc0c46560 __restore_rt (libc.so.6 + 0x42560) #4 0x7efcc0908916 XPending (libX11.so.6 + 0x32916) #5 0x7efca69d1059 n/a (kded_touchpad.so + 0x18059) #6 0x7efcc12f1a1f n/a (libQt5Core.so.5 + 0x2bda1f) #7 0x7efcc12f3ac9 _ZN15QSocketNotifier9activatedEiNS_14QPrivateSignalE (libQt5Core.so.5 + 0x2bfac9) #8 0x7efcc12f4540 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2c0540) #9 0x7efcc1f681a6 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1791a6) #10 0x7efcc12c0b9a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28cb9a) #11 0x7efcc130b906 n/a (libQt5Core.so.5 + 0x2d7906) #12 0x7efcbfe6dee3 g_main_context_dispatch (libglib-2.0.so.0 + 0x54ee3) #13 0x7efcbfec40f9 n/a (libglib-2.0.so.0 + 0xab0f9) #14 0x7efcbfe6b455 g_main_context_iteration (libglib-2.0.so.0 + 0x52455) #15 0x7efcc130cada _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8ada) #16 0x7efcc12b8e6b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x284e6b) #17 0x7efcc12c45c7 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2905c7) #18 0x563fd9da9a62 n/a (kded5 + 0x6a62) #19 0x7efcc0c31310 __libc_start_call_main (libc.so.6 + 0x2d310) #20 0x7efcc0c313c1 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2d3c1) #21 0x563fd9daa0ce n/a (kded5 + 0x70ce) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451059] Okular freezes for up to 10 seconds when loading a document or switching windows
https://bugs.kde.org/show_bug.cgi?id=451059 --- Comment #3 from Amaury Pouly --- (In reply to Albert Astals Cid from comment #2) > I understand you don't have tabs enabled, right? Yes that's correct. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451059] Okular freezes for up to 10 seconds when loading a document or switching windows
https://bugs.kde.org/show_bug.cgi?id=451059 --- Comment #2 from Albert Astals Cid --- I understand you don't have tabs enabled, right? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451059] Okular freezes for up to 10 seconds when loading a document or switching windows
https://bugs.kde.org/show_bug.cgi?id=451059 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Severity|major |normal --- Comment #1 from Albert Astals Cid --- This is not major by any definition of major. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451059] Okular freezes for up to 10 seconds when loading a document or switching windows
https://bugs.kde.org/show_bug.cgi?id=451059 Amaury Pouly changed: What|Removed |Added CC||amaury.po...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451059] New: Okular freezes for up to 10 seconds when loading a document or switching windows
https://bugs.kde.org/show_bug.cgi?id=451059 Bug ID: 451059 Summary: Okular freezes for up to 10 seconds when loading a document or switching windows Product: okular Version: 21.12.2 Platform: Debian unstable OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: amaury.po...@gmail.com Target Milestone: --- Created attachment 147249 --> https://bugs.kde.org/attachment.cgi?id=147249=edit D-BUS log of a such an instance I have a large number of okular instances running (typically 20 or more) and very often either loading a new document or just switching between windows (or switching between virtual desktops) will make okular completely freeze for a long time. Quite regularly, the freeze is short enough to be an annoyance (a couple of seconds), but every now and then, it can freeze for 10 seconds and more. I tried to debug the code myself but I am out of my depth. I got to suspect, however, that it is related to okular asking other okular instances questions over D-BUS, specifically the canOpenDocs call. I attach a D-BUS trace showing an instance when opening a document will trigger several very slow canOpenDocs calls (5 seconds). Unfortunately, I haven't found yet a 100% recipe to reproduce it but clearly: 1) it only happens with many okular instances running 2) switching virtual desktops seems to make it worse Finally, the bug is not new, I has been happening for some time but progressively got worse as my number of open documents has increased recently. I happy to provide more logs/recompile stuff if needed, I just don't really know where to start at the moment. STEPS TO REPRODUCE 1. open lots of okular documents (I use PDFs), the size of the PDFs does not seem to matter 2. switch between windows/desktops 3. open a new document, hope to reproduce the bug, otherwise close it 4. return to step 2 OBSERVED RESULT opening/switching to a windows will take anywhere between 2 to 10 seconds EXPECTED RESULT should be almost instantenous SOFTWARE/OS VERSIONS Linux: 5.16.0-3-amd64 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451035] Area selection is only half resolution.
https://bugs.kde.org/show_bug.cgi?id=451035 --- Comment #8 from Mark van Rossum --- Thanks for checking. I'll update when it changes. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 446839] Add Steam Deck to https://kde.org/hardware
https://bugs.kde.org/show_bug.cgi?id=446839 Paul Brown changed: What|Removed |Added CC||paul.br...@kde.org --- Comment #8 from Paul Brown --- The composite image is the one that is going to work for us, as we need to isolate it and also in the other alternatives, the desktop is obscured. > but they'd like to see it and approve it first. So if you end up going that > way, can you send it to me so I can send it to them? Of course, no problem. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 426107] When annotating, viewport inappropriately shows zoomed-in full size image
https://bugs.kde.org/show_bug.cgi?id=426107 --- Comment #3 from Nate Graham --- Oh, that's great! Could we make the image fit in whatever size the window is rather than show full size by default? That would probably be sufficient to fix the issue, independently of your proposed fix for Bug 429833. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451035] Area selection is only half resolution.
https://bugs.kde.org/show_bug.cgi?id=451035 Albert Astals Cid changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Albert Astals Cid --- I have installed mate in my computer and can't reproduce there either. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 438206] Fails to build against Python 3.10
https://bugs.kde.org/show_bug.cgi?id=438206 --- Comment #12 from Sven Brauch --- Any help is certainly very welcome. I am not very active on IRC currently, but I definitely read and answer kdevelop-de...@kde.org. In principle, the task is simple: in parser/ast.h we have our own data structure for an AST, and that needs to be populated. The current way to do that is based on a... let's say, "creative" domain-specific language which describes how CPython's internal AST representation maps to ours from ast.h. C code is generated from this DSL file. You could just as well write that C code by hand -- it's not actually that much, a few hundred lines. This doesn't work any more, because CPython's representation is gone. There are certainly several different approaches to fix this, I think my suggestion above is the most straightforward one since it doesn't structurally change anything. Though, if one has to touch all this stuff *anyways*, it might be worth evaluating other parser libraries which support also e.g. proper incomplete parsing. I'd honestly opt for whatever the person doing it feels most comfortable with. I wouldn't discard approaches involving serializing/deserializing the AST (e.g. to/from XML) because of performance concerns; XML stream serialization/deserialization (i.e. if you avoid building a DOM) is extremely fast, and I'm pretty sure that the impact is negligible compared to the semantic analysis effort later on. The only thing I'd really try to avoid is spawning a process for each parse job. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 445541] Bottom of settings window is partially hidden behind Plasma panel
https://bugs.kde.org/show_bug.cgi?id=445541 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451035] Area selection is only half resolution.
https://bugs.kde.org/show_bug.cgi?id=451035 --- Comment #6 from Mark van Rossum --- This is with Mate 1.26.0. It is pretty weird... I'm a long time okular user, and I have not seen this before. It is not a deal breaker; just a minor annoyance. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 446839] Add Steam Deck to https://kde.org/hardware
https://bugs.kde.org/show_bug.cgi?id=446839 --- Comment #7 from Nate Graham --- The suggestion I received was to use https://cdn.cloudflare.steamstatic.com/steamdeck/images/fauxrassic-park.jpg, or a screencapture from https://cdn.cloudflare.steamstatic.com/steamdeck/images/video/crusader-kings.mp4 that shows Plasma. They also said we could make a composite image that uses one of the official promo screenshots with the Plasma desktop added on top of the screen, but they'd like to see it and approve it first. So if you end up going that way, can you send it to me so I can send it to them? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451017] Search by time of day
https://bugs.kde.org/show_bug.cgi?id=451017 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.0.0 Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/3150bcb ||3526738f51c3e6e61c50e07c40b ||828edf Resolution|--- |FIXED --- Comment #3 from Maik Qualmann --- Git commit 3150bcb3526738f51c3e6e61c50e07c40b828edf by Maik Qualmann. Committed on 02/03/2022 at 22:29. Pushed by mqualmann into branch 'master'. add time range search of a day FIXED-IN: 8.0.0 M +1-1NEWS M +26 -0core/libs/database/item/query/itemquerybuilder.cpp M +37 -0core/utilities/searchwindow/searchfields.h M +9-0core/utilities/searchwindow/searchfields_createfield.cpp M +134 -0core/utilities/searchwindow/searchfields_rangedate.cpp M +1-0core/utilities/searchwindow/searchgroup.cpp https://invent.kde.org/graphics/digikam/commit/3150bcb3526738f51c3e6e61c50e07c40b828edf -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449981] Plasmashell crashes randomly in PrimaryOutputWatcher::primaryOutputNameChanged()
https://bugs.kde.org/show_bug.cgi?id=449981 --- Comment #15 from NIk --- (In reply to Philipp Maierhöfer from comment #12) > The "duplicate" bug filed in https://bugs.kde.org/show_bug.cgi?id=450607 has > not been fixed in Tumbleweed 20220227. > > I'm not saying that "WORKSFORSOME" is not correct in the sense that one > possible trigger of the underlying bug may have been fixed. But I fear that > setting the status to "WORKSFORSOME" reduces the priority even further. > > Given the fact that a core component of the DE is frequently crashing in > everyday usage this might send the wrong signal. I agree, changed back to reported if thats correct. I assumed that since its actually fixed for me, consistently, it also is fixed for anyone else but they just didnt report back. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451035] Area selection is only half resolution.
https://bugs.kde.org/show_bug.cgi?id=451035 --- Comment #5 from Albert Astals Cid --- Are you using Plasma? Gnome? something else? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449981] Plasmashell crashes randomly in PrimaryOutputWatcher::primaryOutputNameChanged()
https://bugs.kde.org/show_bug.cgi?id=449981 NIk changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 426107] When annotating, viewport inappropriately shows zoomed-in full size image
https://bugs.kde.org/show_bug.cgi?id=426107 Antonio Prcela changed: What|Removed |Added CC||antonio.prc...@gmail.com --- Comment #2 from Antonio Prcela --- I've added in upstream a button to fit image into current view: https://github.com/ksnip/kImageAnnotator/pull/281 and then there is https://bugs.kde.org/show_bug.cgi?id=429833 with MR: https://invent.kde.org/graphics/spectacle/-/merge_requests/127 Or you got an idea/suggestion to do it differently? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451054] Systemsettings don't open after latest update
https://bugs.kde.org/show_bug.cgi?id=451054 David Edmundson changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- >org.kde.systemsettings.app: System Settings was unable to load any views, and >hence has nothing to display. It's saying it can't find any plugins, even the fallback. That's a setup issue. QT_DEBUG_PLUGINS=1 systemsettings might help you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451058] New: Window borders freeze after waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=451058 Bug ID: 451058 Summary: Window borders freeze after waking up from sleep Product: kwin Version: 5.24.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: aurorae Assignee: kwin-bugs-n...@kde.org Reporter: gabriel.cannabr...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** After waking up from sleep, all the window titlebars stay frozen. If I hover over the buttons, they stay the same. If I try to resize the window, the titlebar just stretches. STEPS TO REPRODUCE 1. put computer to sleep 2. wake computer up 3. stretch window border OBSERVED RESULT window borders freeze EXPECTED RESULT window borders don't freeze SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This happens with every theme I've tried it with. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 429833] Resize window while annotating to show full image (or maximize when the images is larger than the window can be)
https://bugs.kde.org/show_bug.cgi?id=429833 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/spectacle/-/merge_requests/127 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451035] Area selection is only half resolution.
https://bugs.kde.org/show_bug.cgi?id=451035 --- Comment #4 from Mark van Rossum --- THe menu gives the correct size. So to be clear: I select an area of, say, 200x200 pixels (checked with kruler), but the menu shows 100x100 pixels. And when I paste in an external program, it is indeed only 100x100. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451035] Area selection is only half resolution.
https://bugs.kde.org/show_bug.cgi?id=451035 --- Comment #3 from Albert Astals Cid --- Where are you pasting the image? Is the image not of the size that the okular menu says it will be? -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 438206] Fails to build against Python 3.10
https://bugs.kde.org/show_bug.cgi?id=438206 --- Comment #11 from Francis Herne --- To address the development comments: It's great that you're interested in contributing to kdev-python. As you can see it's kind of needed at the moment. Consider dropping by #kdevelop on Libera IRC if you want to discuss it (ping FLHerne [me] or scummos [Sven]). Tools/tests: There are quite a lot of unit/end-to-end tests. Run `ninja test` (or `make test`) after building kdev-python, or for more detailed output run the test binaries individually (e.g. build/parser/tests/pyasttest , build/duchain/tests/pyduchaintest ). parser/generated.h converts from CPython's AST structures to kdev-python's. It's generated based on parser/python39.sdef by the script conversionGenerator.py. The script pythonpythonparser.py spits out the AST as an XML representation, using the Python `ast` module API. In recent years it's been used only as a tool for debugging and development. I believe it was once used in kdevelop before it called into the C API instead, and could be resurrected as such to implement Sven's suggestion. I'm not a big fan of this idea, I suspect performance would suffer considerably. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451057] New: Multi-monitor windows all go to leftmost window after waking up from screen energy saving
https://bugs.kde.org/show_bug.cgi?id=451057 Bug ID: 451057 Summary: Multi-monitor windows all go to leftmost window after waking up from screen energy saving Product: plasmashell Version: 5.24.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: gabriel.cannabr...@gmail.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 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 *** Multi-monitor windows all go to leftmost window after waking up from screen energy saving STEPS TO REPRODUCE 1. let computer go into screen energy saving 2. wake computer up 3. there you go OBSERVED RESULT windows stay in same place as they were left in EXPECTED RESULT all windows go to leftmost monitor (i think) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION this doesn't seem to happen when the computer goes to sleep, only when the screen turns off (screen energy saving) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451056] New: Kwin-X11 Windows Resize, Position, and Move Erratically
https://bugs.kde.org/show_bug.cgi?id=451056 Bug ID: 451056 Summary: Kwin-X11 Windows Resize, Position, and Move Erratically Product: kwin Version: 5.24.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: z_mikow...@yahoo.com Target Milestone: --- SUMMARY Kwin is showing the following anomalies. These are not constant, but occur frequently (10-20 times) per day. They all appear to be associated with a scaling issue, so I have grouped them here. I will work to provide a better guide to reproduce as I find out more. Driver package is nvidia-driver-470. STEPS TO REPRODUCE 1. Run Jammy with multiple 4K monitors attached. I've tried this with a high font DPI setting (System Settings > Fonts > Force DPI = 144) and fractional scaling (System Settings > Displays > Global Scale = 150%). These symptoms occur in either setting. I have not confirmed if this works without either. 2. Launch an app such as konsole or google-chrome (the latter seems highly susceptible). 3. Tile and drag windows. This results in issues (1), (2), and (3), above. 4. Drag a tab from konsole or firefox into an empty space. The window will be placed incorrectly even if the area dragged to is completely open. 5. Turning off compositing (alt+shift+f12) results in window being sized to include a large black border (around 50px) which presumably is the shadow size. This border is ignored when tiling or using the maximize button. But it is included in window size when using vertical maximize and horizontal maximize. OBSERVED RESULT A. When moving windows, the window will not move with the cursor but will continue to move the window further downwards on the screen even as the cursor is pushed further up. In fact, the speed at which a window moves down appears proportional to the upward movement of the cursor. B. Windows that are moved as in (1) will often "slide off screen" and are inaccessible using the cursor although they still exist in the panel. Windows include IntelliJ Pro, Google Chrome, Konsole. C. Windows that have been tiled (e.g. press meta + arrow key) when moved by dragging the title bar, will vertically collapse to only the height of the title bar. After dropping this title bar, one cannot select or move it again from the screen. Windows include IntelliJ Pro, Google Chrome, Konsole D. Windows spawned by dragging a tab from one window onto an empty space (e.g. dragging a tab from a firefox browser or konsole session onto an empty space on the desktop) are placed badly - usually far away from the intended location, and sometimes off-screen as in (2). EXPECTED RESULT A and B. Moving windows should follow the cursor and not 'slide off screen' where they are inaccessible. C. Windows show maintain their size or pre-tiling size when moving, and should not collapse to title-bar height. D. Windows spawned from another window tab like konsole or firefox, should be created in the area of the cursor, not off screen. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.15.0-18-lowlatency (64-bit) Graphics Platform: X11 Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 ADDITIONAL INFORMATION Downstream Kubuntu bug: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1962621 All kwin settings are defaults. No kwin scripts are installed or used. SPECULATION Scaling is not applied correctly to window moving or sizing? Font DPI is not applied correctly to window moving or sizing? -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 438206] Fails to build against Python 3.10
https://bugs.kde.org/show_bug.cgi?id=438206 --- Comment #10 from Francis Herne --- My own thinking is that it's probably easier to fork (or, so far as possible, vendor in the most recent version of) CPython's parser code. The amount of code involved is relatively small - see https://github.com/python/typed_ast/tree/master/ast3 which is another fork. (in the past I'd considered changing kdev-python to use that typed-ast library instead of linking against the CPython parser, but it's now deprecated with the features added to CPython upstream). Sadly I haven't yet had time to work on this, but I hope to in a few weeks. Right now I'm busy buying and moving onto a houseboat... -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 446839] Add Steam Deck to https://kde.org/hardware
https://bugs.kde.org/show_bug.cgi?id=446839 --- Comment #6 from Nate Graham --- OK, let me reach out to my Valve contact about it. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 438206] Fails to build against Python 3.10
https://bugs.kde.org/show_bug.cgi?id=438206 --- Comment #9 from Øystein S. Haaland --- (In reply to Sven Brauch from comment #7) > Unfortunately Python completely removed the Parser module we were using from > their public API, so there is no easy fix for this issue. > > The most realistic option at this point is probably to write a Python > snippet which uses the "ast" module to do the parsing (which is effectively > exactly the same) and serializes the result somehow, e.g. into an XML or > ProtocolBuffer stream. Then we can execute this snippet from C++ code (this > works without creating a process using Python's C API) and deserialize it, > giving us the same data structure as before. Thanks a lot for sketching a possible route for implementing this! I would be more than willing to put some effort into this if I had the time. But maybe with some guidance it would still be possible to have some progress every now and then. The first part seem easy enough; write the code that reads a file with python code and loads it into the ast. You mention a few ways serialization can be done. Are there any examples of similar approaches already in the code base? Are there already places where de-serialization is done with one of the formats mentioned (or other formats for that matter)? Any pointers for tools/tests in the repo that can be useful for working with this would be much appreciated. Btw. would it make things easier if one used cython or mypyc to compile the python part to a c module? Again, if there is any way I could fund this work more or less directly, I would also be interested in hearing about that. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 446839] Add Steam Deck to https://kde.org/hardware
https://bugs.kde.org/show_bug.cgi?id=446839 --- Comment #5 from Carl Schwan --- I will need need a good image of the steam deck with Plasma displayed. I couldn't find any on https://www.steamdeck.com/en/press I do wonder if it would be possible for Steam to add a link to the plasma webpage or mention KDE/Plasma on their social media. If we are doing a bit of promo about their product, it would be nice if we could get a bit of promo too ;) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451035] Area selection is only half resolution.
https://bugs.kde.org/show_bug.cgi?id=451035 --- Comment #2 from Mark van Rossum --- Hi, No I don't use scaling. For the selection I use 'Area Selection'. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 451047] Fatal error: Error while installing package: 0.0000 while updating, unable to upgrade
https://bugs.kde.org/show_bug.cgi?id=451047 Dan Duris changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Dan Duris --- Fixed by manually upgrading: 1988 sudo dpkg --configure -a 1989 sudo apt --fix-broken install 1990 sudo pkcon update 1991 sudo reboot But guys, surely pkcon can be smart enough to run this combo itself when broken??? Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.14.0-1024-oem (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 30,8 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451035] Area selection is only half resolution.
https://bugs.kde.org/show_bug.cgi?id=451035 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||aa...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Albert Astals Cid --- Which of the tools in the tool menu are you using? Do you have a hidpi monitor? If so are you running at any scale factor different than 1? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 equ...@gmail.com changed: What|Removed |Added CC||equ...@gmail.com --- Comment #15 from equ...@gmail.com --- I have this issue occasionally when copying from Konsole to other apps. Selecting another block of text in Konsole and copying seems to "fix" it, until it occurs again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442191] Transform tool produces white artifacts around the edge of transformed result
https://bugs.kde.org/show_bug.cgi?id=442191 --- Comment #3 from acc4commissi...@gmail.com --- Also if I may add : it'd be nice to have liquify has the edges stick to the selection edges and stretched, so we don't have to worry about not touching the edges or matching the edges while transforming. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442191] Transform tool produces white artifacts around the edge of transformed result
https://bugs.kde.org/show_bug.cgi?id=442191 --- Comment #2 from acc4commissi...@gmail.com --- Can we get this fixed sooner if it's not that hard to fix please. It's very pesky to be forced to wrap the whole drawings when using liquify, and I can't ever use the liquify at all on complicated paintings, because it would leave blade scars on them. It slows down the workflow quite a lot. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 451013] missing dependencies for updates
https://bugs.kde.org/show_bug.cgi?id=451013 --- Comment #1 from tomas nackaerts --- I was able to fix this by running: sudo dpkg --configure -a -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451054] Systemsettings don't open after latest update
https://bugs.kde.org/show_bug.cgi?id=451054 --- Comment #1 from Marek --- I found this post with the same problem (one of their problems..): https://forum.artixlinux.org/index.php/topic,3747.msg0.html A "solution" proposed there is to install amd-ucode package, which doesn't exist for Fedora (at least not with "amd" in the name). I'm doubtful as why processor microcode package should affect systemsettings5... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451055] New: On Wayland some windows are not visible to Plasma applets
https://bugs.kde.org/show_bug.cgi?id=451055 Bug ID: 451055 Summary: On Wayland some windows are not visible to Plasma applets Product: plasmashell Version: 5.24.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dennis.lis...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Since switching to running Plasma on Wayland, I'm sometimes having a window (or a few) that seem to be "invisible" to plasmashell applets. Most often that happens with Pidgin's windows (buddy list and/or conversations window). What does not work: - they're missing from the Task Manager panel applet; - they're missing from the Window List panel applet; - they're not affected by the Minimize All Windows panel applet. What works: - normal window management (moving, resizing, maximizing, minimizing); - switching to/from them with Alt+Tab. If a window gets into this state when opened, it does not become normal later or vice versa (at least I've never seen that). I don't have reliable steps to reproduce (sometimes the windows of the same applications behave normal), but could perform steps for debugging if I knew what to do. SOFTWARE/OS VERSIONS Gentoo Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 with KDE patches (Gentoo packages) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451054] New: Systemsettings don't open after latest update
https://bugs.kde.org/show_bug.cgi?id=451054 Bug ID: 451054 Summary: Systemsettings don't open after latest update Product: systemsettings Version: 5.24.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: marek.schim...@gmail.com Target Milestone: --- SUMMARY Systemsettings doesn't work. When I tried to execute it from the terminal, I got: $ systemsettings5 org.kde.systemsettings.app: System Settings was unable to load any views, and hence has nothing to display. qt.qpa.wayland: Wayland does not support QWindow::requestActivate() $ echo $? 0 $ systemsettings5 --list The following modules are available: kcm_about-distro - Information About This System kcm_access - Configure Accessibility Options kcm_activities - Activities help you to focus on a specific task kcm_autostart - Automatically Started Applications kcm_baloofile - Configure File Search kcm_bluetooth - Manage Bluetooth devices kcm_cddb - Configure the CDDB Retrieval kcm_clock - Date and Time kcm_colord - Manage color correction of devices kcm_colors - Choose colour scheme kcm_componentchooser - Choose default Applications kcm_cookies- Configure the way cookies work kcm_cursortheme- Choose mouse cursor theme kcm_desktoppaths - Location for Personal Files kcm_desktoptheme - Choose Plasma style kcm_device_automounter - Configure automatic handling of removable storage media kcm_energyinfo - Energy Consumption Statistics kcm_feedback - Configure user feedback settings kcm_filetypes - Configure file associations kcm_fontinst - Install, manage and preview fonts kcm_fonts - Configure user interface fonts kcm_formats- Numeric, Currency and Time Formats kcm_hotkeys- Configure Input Actions settings kcm_icons - Choose icon theme kcm_joystick - Calibrate Game Controller kcm_kaccounts - Configure your internet accounts such as Google, Live, Owncloud kcm_kamera - Configure Kamera kcm_kdeconnect - Connect and sync your devices kcm_kded - Configure background services kcm_keyboard - Keyboard Hardware and Layout kcm_keys - Configure Keyboard Shortcuts kcm_kscreen- Manage and configure monitors and displays kcm_kwallet5 - KDE Wallet Configuration kcm_kwin_effects - Configure compositor settings for desktop effects kcm_kwin_scripts - Manage KWin scripts kcm_kwin_virtualdesktops - Configure navigation, number and layout of virtual desktops kcm_kwindecoration - Configure window titlebars and borders kcm_kwinoptions- Configure window actions and behaviour kcm_kwinrules - Individual Window Behaviour kcm_kwinscreenedges- Configure active screen corners and edges kcm_kwintabbox - Navigation Through Windows kcm_kwintouchscreen- Configure touch screen swipe gestures kcm_landingpage- Landing page with some basic settings kcm_launchfeedback - Application Launch Feedback kcm_lookandfeel- Choose global look and feel kcm_mouse - Mouse Controls kcm_netpref- Configure generic network preferences, like timeout values kcm_networkmanagement - Edit your Network Connections kcm_nightcolor - Adjust colour temperature at night to reduce eye strain kcm_notifications - Event Notifications and Actions kcm_plasmasearch - Configure search settings kcm_powerdevilactivitiesconfig - Per-Activity Power Management kcm_powerdevilglobalconfig - Advanced Power Management Settings kcm_powerdevilprofilesconfig - Energy Saving kcm_printer_manager- Configure your printers kcm_proxy - Configure the proxy servers used kcm_pulseaudio - Configure audio devices and volume kcm_qtquicksettings- No description available kcm_screenlocker - Configure screen locking kcm_sddm - Configure Login Manager kcm_smb- Credentials used to access SMB shares kcm_smserver - Desktop Session Login and Logout kcm_solid_actions - Manage actions available to the user when connecting new devices kcm_splashscreen -
[kate] [Bug 445541] Bottom of settings window is partially hidden behind Plasma panel
https://bugs.kde.org/show_bug.cgi?id=445541 --- Comment #9 from Christoph Cullmann --- https://invent.kde.org/utilities/kate/-/merge_requests/653 This makes all pages scrollable. Naturally even nicer would be "small" config pages, but I don't think that is easily feasible. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451008] System settings close unexpectedly when you enter the application style tab
https://bugs.kde.org/show_bug.cgi?id=451008 sergipla...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from sergipla...@gmail.com --- I have already solved the problem, the ~/.config/kdeglobals file was corrupted, I replaced it with the healthy file of a LIVE, and it was working correctly again, which I don't know is because the file was corrupted -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451053] New: Plasma shell crashed when I attached an external monitor.
https://bugs.kde.org/show_bug.cgi?id=451053 Bug ID: 451053 Summary: Plasma shell crashed when I attached an external monitor. Product: plasmashell Version: 5.24.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dha...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.2) Qt Version: 5.15.3 Frameworks Version: 5.91.0 Operating System: Linux 5.13.0-30-generic x86_64 Windowing System: Wayland Distribution: KDE neon User - 5.24 DrKonqi: 5.24.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I attached an external monitor and changed the resolution of the external monitor. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 3507] [New LWP 3508] [New LWP 3516] [New LWP 3545] [New LWP 3572] [New LWP 3707] [New LWP 3710] [New LWP 3711] [New LWP 3712] [New LWP 3714] [New LWP 3715] [New LWP 3716] [New LWP 3983] [New LWP 4010] [New LWP 4011] [New LWP 4012] [New LWP 4461] [New LWP 4462] [New LWP 4463] [New LWP 4464] [New LWP 4465] [New LWP 4466] [New LWP 4467] [New LWP 4468] [New LWP 4469] [New LWP 4484] [New LWP 4485] [New LWP 4486] [New LWP 4487] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fe3a9ccd9cf in __GI___poll (fds=0x7ffc15fe5c78, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7fe3a5e204c0 (LWP 3490))] Thread 30 (Thread 0x7fe32e7ff700 (LWP 4487)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556bcf47e0e4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556bcf47e090, cond=0x556bcf47e0b8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556bcf47e0b8, mutex=0x556bcf47e090) at pthread_cond_wait.c:638 #3 0x7fe3aa0636db in QWaitConditionPrivate::wait (deadline=..., this=0x556bcf47e090) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=this@entry=0x556bcf4a7fd8, mutex=mutex@entry=0x556bcf4a7fd0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fe3abcd7c44 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x556bcf4a7fc8) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x556bcf4a7f30) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7fe3abcd80b9 in QSGRenderThread::run (this=0x556bcf4a7f30) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7fe3aa05d543 in QThreadPrivate::start (arg=0x556bcf4a7f30) at thread/qthread_unix.cpp:331 #9 0x7fe3a9b40609 in start_thread (arg=) at pthread_create.c:477 #10 0x7fe3a9cda163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7fe31bfff700 (LWP 4486)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556bd0b82690) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556bd0b82640, cond=0x556bd0b82668) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556bd0b82668, mutex=0x556bd0b82640) at pthread_cond_wait.c:638 #3 0x7fe39263a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fe39263a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fe3a9b40609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fe3a9cda163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fe2bb7fe700 (LWP 4485)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556bd0b4f0e0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556bd0b4f090, cond=0x556bd0b4f0b8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556bd0b4f0b8, mutex=0x556bd0b4f090) at pthread_cond_wait.c:638 #3 0x7fe39263a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fe39263a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fe3a9b40609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fe3a9cda163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7fe31b7fe700 (LWP 4484)): #0 0x7fe3a9cda49e in epoll_wait (epfd=85, events=0x7fe31b7fd7f0, maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 0x7fe37805727b in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #2 0x7fe3780496f4 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #3 0x7fe372d940e0 in ?? () from /lib/x86_64-linux-gnu/libpipewire-0.3.so.0 #4
[kwin] [Bug 451052] New: Dragging files causes dragged item to flicker
https://bugs.kde.org/show_bug.cgi?id=451052 Bug ID: 451052 Summary: Dragging files causes dragged item to flicker Product: kwin Version: 5.24.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: nortex...@gmail.com Target Milestone: --- When I drag a file and move it, the dragged item wildly flickers. I would attach a video but for some reason it doesn't really show up on the OBS recording. If a video is needed, I could use my phone. This issue does not arise on X11. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 451051] New: Konversation crashed when moving a PM conversation in the list.
https://bugs.kde.org/show_bug.cgi?id=451051 Bug ID: 451051 Summary: Konversation crashed when moving a PM conversation in the list. Product: konversation Version: 1.8.21081 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: wodenc...@gmail.com Target Milestone: --- Application: konversation (1.8.21081) Qt Version: 5.15.2 Frameworks Version: 5.86.0 Operating System: Linux 5.13.0-32-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: Ubuntu 21.10 -- Information about the crash: - What I was doing when the application crashed: I was moving a PM conversation in the list up, using ALT-SHIFT, and after doing this for a couple of seconds, Konversation crashed. This has happened to me before. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konversation (konversation), signal: Segmentation fault [KCrash Handler] #4 ViewContainer::rowCount (this=0x557d069b2dc0, parent=...) at ./src/viewer/viewcontainer.cpp:388 #5 0x7ff6f70b189f in QAbstractItemModel::hasChildren (this=0x557d069b2dc0, parent=...) at itemmodels/qabstractitemmodel.cpp:1800 #6 0x7ff6f7ef8bfd in QTreeView::doItemsLayout (this=0x557d06c55060) at itemviews/qtreeview.cpp:2099 #7 0x7ff6f7eef929 in QAbstractItemViewPrivate::executePostedLayout (this=0x557d06c550c0) at ../../include/QtWidgets/5.15.2/QtWidgets/private/../../../../../src/widgets/itemviews/qabstractitemview_p.h:229 #8 QAbstractItemViewPrivate::executePostedLayout (this=0x557d06c550c0) at ../../include/QtWidgets/5.15.2/QtWidgets/private/../../../../../src/widgets/itemviews/qabstractitemview_p.h:226 #9 QTreeView::visualRect (this=this@entry=0x557d06c55060, index=...) at itemviews/qtreeview.cpp:1110 #10 0x7ff6f7e7b94c in QAbstractItemViewPrivate::setHoverIndex (this=this@entry=0x557d06c550c0, index=...) at itemviews/qabstractitemview.cpp:163 #11 0x7ff6f7e88a8b in QAbstractItemView::viewportEvent (this=0x557d06c55060, event=0x7ffeba276e70) at itemviews/qabstractitemview.cpp:1704 #12 0x7ff6f7117eca in QCoreApplicationPrivate::sendThroughObjectEventFilters (event=, receiver=) at kernel/qcoreapplication.cpp:1189 #13 QCoreApplicationPrivate::sendThroughObjectEventFilters (receiver=receiver@entry=0x557d06c558b0, event=event@entry=0x7ffeba276e70) at kernel/qcoreapplication.cpp:1178 #14 0x7ff6f7c046a2 in QApplicationPrivate::notify_helper (this=, receiver=0x557d06c558b0, e=0x7ffeba276e70) at kernel/qapplication.cpp:3626 #15 0x7ff6f711816a in QCoreApplication::notifyInternal2 (receiver=0x557d06c558b0, event=0x7ffeba276e70) at kernel/qcoreapplication.cpp:1063 #16 0x7ff6f7c0a38d in QApplicationPrivate::dispatchEnterLeave (enter=0x557d0a225310, leave=, globalPosF=...) at kernel/qapplication.cpp:2243 #17 0x7ff6f7c0b273 in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x557d0a225310, event=event@entry=0x7ffeba277080, alienWidget=alienWidget@entry=0x557d0a225310, nativeWidget=nativeWidget@entry=0x557d06c524a0, buttonDown=buttonDown@entry=0x7ff6f8157a10 , lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=true) at kernel/qapplication.cpp:2591 #18 0x7ff6f7c0b812 in QApplicationPrivate::sendSyntheticEnterLeave (this=, widget=widget@entry=0x557d088aa9d0) at kernel/qapplication.cpp:2695 #19 0x7ff6f7c46c89 in QWidgetPrivate::setVisible (this=0x557d0a20e540, visible=) at kernel/qwidget.cpp:8113 #20 0x7ff6f7c2b235 in QStackedLayout::setCurrentIndex (this=0x557d06a18480, index=57) at kernel/qstackedlayout.cpp:321 #21 0x7ff6f7c2b79f in QStackedLayout::takeAt (this=0x557d06a18480, index=57) at kernel/qstackedlayout.cpp:273 #22 0x7ff6f7c25f8e in QLayout::removeWidget (this=0x557d06a18480, widget=widget@entry=0x557d08938ba0) at kernel/qlayout.cpp:1393 #23 0x7ff6f7dbfa74 in QStackedWidget::removeWidget (this=, widget=widget@entry=0x557d08938ba0) at widgets/qstackedwidget.cpp:197 #24 0x7ff6f7de3a96 in QTabWidgetPrivate::_q_tabMoved (this=0x557d06bb51d0, from=57, to=56) at widgets/qtabwidget.cpp:811 #25 0x7ff6f714fa88 in doActivate (sender=0x557d06de0160, signal_index=9, argv=0x7ffeba277370) at kernel/qobject.cpp:3898 #26 0x7ff6f7148d67 in QMetaObject::activate (sender=sender@entry=0x557d06de0160, m=m@entry=0x7ff6f8139fc0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffeba277370) at kernel/qobject.cpp:3946 #27 0x7ff6f7dc1f53 in QTabBar::tabMoved (this=this@entry=0x557d06de0160, _t1=, _t1@entry=57, _t2=, _t2@entry=56) at .moc/moc_qtabbar.cpp:352 #28 0x7ff6f7dc5eb9 in QTabBar::moveTab (this=0x557d06de0160, from=57, to=56) at widgets/qtabbar.cpp:2054 #29 0x557d05c0ebd6 in ViewContainer::moveViewLeft (this=0x557d069b2dc0) at
[kwin] [Bug 450779] Strange background pattern/dithering on Wayland session
https://bugs.kde.org/show_bug.cgi?id=450779 Nate Graham changed: What|Removed |Added Version Fixed In||5.24.3 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
