[konsole] [Bug 403324] Can only drag tabs from one window into another when using single-process mode
https://bugs.kde.org/show_bug.cgi?id=403324 --- Comment #12 from tcanabr...@kde.org --- probably related to wayland. can you test on a x11 session? On Thu, 30 May 2024 at 20:00 TraceyC wrote: > https://bugs.kde.org/show_bug.cgi?id=403324 > > --- Comment #11 from TraceyC --- > When my system was running Plasma 5, with "Run all konsole windows in a > single > process" enabled, I was able to drag tabs from one konsole window to > another. I > had been using a shortcut to launch the initial instance. > > Now that my system is running Plasma 6, even with that setting enabled, I > can > no longer drag tabs between konsole windows, regardless of how I launch > them. > > - From krunner > - From kickstart > - By entering `konsole` in a konsole window > - Using File - New Window in konsole > > When I drag a tab out of a window, it will only detach to a new window. > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487771] kwin_x11 crashed 3 times when logging back in with momentary blurred graphic artifacts
https://bugs.kde.org/show_bug.cgi?id=487771 --- Comment #3 from k...@assez.biz --- Created attachment 170003 --> https://bugs.kde.org/attachment.cgi?id=170003=edit New crash information added by DrKonqi kwin_x11 (5.27.5) using Qt 5.15.8 crashed while simply moving windows around -- Backtrace (Reduced): #7 0x7f46660bfb67 in KWin::EffectsHandlerImpl::prePaintWindow(KWin::EffectWindow*, KWin::WindowPrePaintData&, std::chrono::duration >) () from /lib/x86_64-linux-gnu/libkwin.so.5 #8 0x7f466615c1d3 in KWin::WorkspaceScene::preparePaintSimpleScreen() () from /lib/x86_64-linux-gnu/libkwin.so.5 #9 0x7f466615c685 in KWin::WorkspaceScene::prePaint(KWin::SceneDelegate*) () from /lib/x86_64-linux-gnu/libkwin.so.5 #10 0x7f466607b1ef in KWin::Compositor::prePaintPass(KWin::RenderLayer*) () from /lib/x86_64-linux-gnu/libkwin.so.5 #11 0x7f466607e37f in KWin::Compositor::composite(KWin::RenderLoop*) () from /lib/x86_64-linux-gnu/libkwin.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487659] can't input decimals without the leading 0
https://bugs.kde.org/show_bug.cgi?id=487659 fanzhuyi...@gmail.com changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487659] can't input decimals without the leading 0
https://bugs.kde.org/show_bug.cgi?id=487659 --- Comment #5 from fanzhuyi...@gmail.com --- First bad commit is https://invent.kde.org/utilities/kcalc/-/commit/c7864e9547b2ef2e9e318a88c78ba51f10fbc5e3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487806] Adjusting scaling on Wayland leads to incorrectly scaled wallpaper or background
https://bugs.kde.org/show_bug.cgi?id=487806 --- Comment #1 from pikaph...@tutanota.com --- I couldn't upload the video reproducing the issue here, so: https://streamable.com/mh7gat -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487806] New: Adjusting scaling on Wayland leads to incorrectly scaled wallpaper or background
https://bugs.kde.org/show_bug.cgi?id=487806 Bug ID: 487806 Summary: Adjusting scaling on Wayland leads to incorrectly scaled wallpaper or background Classification: Plasma Product: kwin Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pikaph...@tutanota.com Target Milestone: --- SUMMARY Adjusting scaling on Wayland leads to incorrectly scaled wallpaper or background in KDE Plasma 6.1 Beta (6.0.90). STEPS TO REPRODUCE 1. Use Plasma Wayland session. 1. Change scaling. OBSERVED RESULT Incorrectly scaled background. EXPECTED RESULT Correctly scaled background / No black spaces. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-arch1-1 (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487659] can't input decimals without the leading 0
https://bugs.kde.org/show_bug.cgi?id=487659 fanzhuyi...@gmail.com changed: What|Removed |Added CC||abderrahman.naj...@gmail.co ||m --- Comment #4 from fanzhuyi...@gmail.com --- *** Bug 487784 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487784] Input error when using fractions without zero
https://bugs.kde.org/show_bug.cgi?id=487784 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 487659 *** -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487659] can't input decimals without the leading 0
https://bugs.kde.org/show_bug.cgi?id=487659 fanzhuyi...@gmail.com changed: What|Removed |Added Summary|cant type as .4, must be|can't input decimals |0.4.|without the leading 0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478321] When performing Virtual Desktop Switch Gestures too fast, the current desktop moves by 2 steps
https://bugs.kde.org/show_bug.cgi?id=478321 fanzhuyi...@gmail.com changed: What|Removed |Added Summary|Trackpad gesture to change |When performing Virtual |desktops is too fast|Desktop Switch Gestures too ||fast, the current desktop ||moves by 2 steps Status|REPORTED|CONFIRMED CC||fanzhuyi...@gmail.com Ever confirmed|0 |1 Version|5.90.0 |6.0.5 --- Comment #2 from fanzhuyi...@gmail.com --- Can reproduce on laptop touchpad. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478321] Trackpad gesture to change desktops is too fast
https://bugs.kde.org/show_bug.cgi?id=478321 fanzhuyi...@gmail.com changed: What|Removed |Added CC||phoenix_8...@hotmail.com --- Comment #1 from fanzhuyi...@gmail.com --- *** Bug 487790 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487790] When performing Virtual Desktop Switch Gestures too fast, the current desktop moves by 2 steps
https://bugs.kde.org/show_bug.cgi?id=487790 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 478321 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487805] New: Silently switches back to X11 at every reboot
https://bugs.kde.org/show_bug.cgi?id=487805 Bug ID: 487805 Summary: Silently switches back to X11 at every reboot Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: php4...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY The first time I booted after upgrading from 5.x to 6.x, I got presented with the login screen which includes a selector for the session where you can select either X11 or Wayland. I selected Wayland. After that, when I boot it does NOT show the login screen (I think I had set it that way, and that's what I want anyway) but it starts with X11 instead of Wayland. STEPS TO REPRODUCE 1. log out 2. log in and choose Wayland 3. restart OBSERVED RESULT Restarts without login screen, and switches back to X11. EXPECTED RESULT Should remember my preference and start with Wayland 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.
[dolphin] [Bug 487798] No dark mode
https://bugs.kde.org/show_bug.cgi?id=487798 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 448865 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448865] [Request] Dark Mode for Windows 10/11
https://bugs.kde.org/show_bug.cgi?id=448865 fanzhuyi...@gmail.com changed: What|Removed |Added CC||asko...@gmail.com --- Comment #3 from fanzhuyi...@gmail.com --- *** Bug 487798 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448865] [Request] Dark Mode for Windows 10/11
https://bugs.kde.org/show_bug.cgi?id=448865 fanzhuyi...@gmail.com changed: What|Removed |Added CC||lluisfor...@gmail.com --- Comment #2 from fanzhuyi...@gmail.com --- *** Bug 462796 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462796] Dolphin on Windows 11 do not apply dark-mode
https://bugs.kde.org/show_bug.cgi?id=462796 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 448865 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487800] Plasm shell crashes after I eject Extenal SD card reader
https://bugs.kde.org/show_bug.cgi?id=487800 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com Resolution|--- |BACKTRACE --- Comment #2 from fanzhuyi...@gmail.com --- Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols that we need to figure out exactly what's going wrong. Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469192] On X11 with multiple screens, Plasma frequently starts up with no containment (AKA black background with cursor, no context menu possible) on one of the screens until plasma
https://bugs.kde.org/show_bug.cgi?id=469192 --- Comment #25 from php4...@gmail.com --- Oh wait, no, I'm again on X11 for some reason. The first time I booted after upgrading KDE, there was a login screen at startup with a selector for X11 or Wayland and I chose Wayland. That first session was disastrous, and after several a couple of reboots (always choosing Wayland when asked), everything seemed to work fine again and it never showed me the login screen, nor the option to choose, but apparently it f***ing forgot my preference and switched back to X11 without asking or warning. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469192] On X11 with multiple screens, Plasma frequently starts up with no containment (AKA black background with cursor, no context menu possible) on one of the screens until plasma
https://bugs.kde.org/show_bug.cgi?id=469192 --- Comment #24 from php4...@gmail.com --- I am still observing black, empty desktop at startup half of the times, on KDE 6 with Wayland, as described in #475831. Either this issue is not specific to X11 and also affects Wayland, or 475831 is not a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487771] kwin_x11 crashed 3 times when logging back in with momentary blurred graphic artifacts
https://bugs.kde.org/show_bug.cgi?id=487771 k...@assez.biz changed: What|Removed |Added CC||k...@assez.biz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487605] XWayland Vulkan fifo vsync limits at doubled maximum refresh rate with VRR since KWin 6.1 beta 1
https://bugs.kde.org/show_bug.cgi?id=487605 --- Comment #5 from tempel.jul...@gmail.com --- If I didn't make a mistake applying these commits on top of beta 1, it's not fixed for me. Also mpv with --video-sync=display-resample reports erroneous doubled refresh rate in fullscreen with VRR set to auto in kwin. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487802] New: Spectacle not taking screenshots correctly KDE6
https://bugs.kde.org/show_bug.cgi?id=487802 Bug ID: 487802 Summary: Spectacle not taking screenshots correctly KDE6 Classification: Applications Product: Spectacle Version: 24.05.0 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: shaashwatsar...@gmail.com CC: k...@david-redondo.de Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When spectacle is asked to take a new screenshot, it fails to do so. STEPS TO REPRODUCE 1. Just launch spectacle (if set to take new screenshot on launch), or launch and then explicitly take a screenshot 2. Wait 3. See error OBSERVED RESULT Error message: An error occurred while taking a screenshot. KWin screenshot request failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Potentially relevant information: - Method: CaptureScreen - Method specific arguments: "eDP-1" KWin screenshot request failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Potentially relevant information: - Method: CaptureScreen - Method specific arguments: "HDMI-1" Sometimes it fails to take any screenshot at all, and sometimes it takes a delayed screenshot of another window/screen (not the active window) even if that window is behind the active window EXPECTED RESULT It should have taken a screenshot as instructed SOFTWARE/OS VERSIONS Linux: Arch Linux, kernel linux-lts 6.6.25-1-lts (64-bit) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Graphics platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 487801] New: File Sharing issues on mobile
https://bugs.kde.org/show_bug.cgi?id=487801 Bug ID: 487801 Summary: File Sharing issues on mobile Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: ed.bl...@simplelogin.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- File sharing from mobile (android and ios) to pc (both windows and kde neon) works but from pc to mobile, mobile to mobile don't work, I have granted the folder for kde connect before, and tried resetting the app, reinstalling, none works, the shared files won't save to mobile devices I have updated both ios and android version to the latest, issue remains unsolved -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 486862] Window should be always on top
https://bugs.kde.org/show_bug.cgi?id=486862 --- Comment #2 from iodream...@gmail.com --- (In reply to Arjen Hiemstra from comment #1) > It is not possible for an application on Wayland to set that state and I > don't want to introduce differences in behaviour between Wayland and X11. If > you want it always on top you can add a KWin window rule to enforce that. I understand that this could be impossible to implement for now, especially on Wayland, but could this bug report at least stay open rather than closed completely? I really feel like the task manager is one of those areas that are inferior on Linux compared to something like Windows because regular users could not even access it if they get into a situation like i described in this post and good software should support not just power users. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487796] New: When in "unify outputs" mode for dual screen setup, Overview effect does not show applications on the secondary monitor
https://bugs.kde.org/show_bug.cgi?id=487796 Bug ID: 487796 Summary: When in "unify outputs" mode for dual screen setup, Overview effect does not show applications on the secondary monitor Classification: Plasma Product: kwin Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: leon.ha...@protonmail.com Target Milestone: --- SUMMARY When using "unify outputs" mode for dual monitors (i.e. duplicate), opening overview effect does not show the applications on the secondary monitor. Additionally, desktops on the top do not have any preview. The overview works as intended on the main screen. Within the overview effect, you can still switch desktops on the secondary monitor, and it switches them also on the main. So it seems its the problem with desktop and application previews on the secondary monitor. STEPS TO REPRODUCE 1. Have 2 monitors and set them on the "unify outputs" 2. Open overview effect OBSERVED RESULT Desktop and application previews do not show on the secondary monitor, only the main one. EXPECTED RESULT Both monitors should show the overview effect in the same way, with desktop and application previews. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.8.10-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 474766] CPU temp shows 0
https://bugs.kde.org/show_bug.cgi?id=474766 duncanyo...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #16 from duncanyo...@gmail.com --- I did, and it was closed for no reason. https://bugs.kde.org/show_bug.cgi?id=484019 this one too https://bugs.kde.org/show_bug.cgi?id=452763 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487795] New: Plasma Workspace: startplasma on Wayland Display limited to 1024x768
https://bugs.kde.org/show_bug.cgi?id=487795 Bug ID: 487795 Summary: Plasma Workspace: startplasma on Wayland Display limited to 1024x768 Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: tob...@g3ro.eu Target Milestone: --- SUMMARY Followup to https://discuss.kde.org/t/startplasma-wayland-options/15366 I could not find the Workspace category here, thats why I filed it in this category. When I try to start startplasma on an existing Wayland Display, the Wayland window is limited to 1024x768. Command tried (as user): WAYLAND_DISPLAY=wayland-1 /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland When I try the same on an X-Display, I can adjust the size, though the original size is still 1024x768. Now I would like to have two things: 1. The window size should be equal the Wayland Display size. 2. I would like to have or if existing know some options that I can give to "startplasma" to configure things and know how to do so. OBSERVED RESULT Window size limited. EXPECTED RESULT Window size should not be limited. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.6.32-1-lts (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa Intel® Graphics ADDITIONAL INFORMATION Might be similar to: https://bugs.kde.org/show_bug.cgi?id=436497 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487794] New: Cannot perform anny updates due to on broken package
https://bugs.kde.org/show_bug.cgi?id=487794 Bug ID: 487794 Summary: Cannot perform anny updates due to on broken package Classification: Applications Product: Discover Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (interactive) Assignee: plasma-b...@kde.org Reporter: kristian.olofs...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY i have 50+ updates in Discover, if try to update all i get an error with the following text: Package failed to install:Error while installing package: trying to overwrite /usr/share/man/man7/libpipewire-module-access.7.gz, which is also in package pipewire-bin 1.0.7-1~ubuntu22.04 if i only try to update a non pipwire package i get the same result i.e. i cannot update anything using Discover... STEPS TO REPRODUCE 1. Try to update 2. 3. OBSERVED RESULT Fail on any update EXPECTED RESULT Success when updating SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i7-1260P Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: XPS 9320 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 487793] New: Notes don't work anymore
https://bugs.kde.org/show_bug.cgi?id=487793 Bug ID: 487793 Summary: Notes don't work anymore Classification: Plasma Product: kdeplasma-addons Version: git-stable-Plasma/6.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: notes Assignee: plasma-b...@kde.org Reporter: tob...@g3ro.eu Target Milestone: --- SUMMARY When I try to click on the Note symbole, it shows only a small icon, but not the text anymore. The files under: ~/.local/share/plasma_notes still exist. The file ~/.config/plasma-org.kde.plasma.desktop-appletsrc still seems to show the correct NoteID. Though the files are barely usable outside of notes right now, because of HTML code everywhere. Sidenote: It would be nice to have a plain text version for easier backup or switch to another app etc. As a workaround for others, see: https://stackoverflow.com/questions/19878056/sed-remove-tags-from-html-file STEPS TO REPRODUCE 1. see above. 2. 3. OBSERVED RESULT Notes don't appear. EXPECTED RESULT Notes should appear. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.6.32-1-lts (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa Intel® Graphics ADDITIONAL INFORMATION Followup to: https://invent.kde.org/plasma/kdeplasma-addons/-/issues/14 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 478411] SSL Certificate Error
https://bugs.kde.org/show_bug.cgi?id=478411 --- Comment #1 from mik...@mailbox.org --- I just want to add that the latest version on Flathub still doesn’t work at all. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482262] Gwenview: Color Picker is missing: On Plasma 6, the "Select Color" menu won't show when you click on color palette => the three-dot button.
https://bugs.kde.org/show_bug.cgi?id=482262 --- Comment #1 from athaswildwhisper55232.untainted...@aleeas.com --- Seems as of Plasma 6, gwenview is OK. However, the color picker in the "Annotate" menu, in which I edit an image file, when I click the color palette => the "..." button still does not work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462116] Plasma crashed after inserted STLinkV2
https://bugs.kde.org/show_bug.cgi?id=462116 --- Comment #3 from oc.yaki...@gmail.com --- Sorry. I 'm not using plasmashell now, so I can't check. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 442876] Spectacle is quite slow in taking screenshots
https://bugs.kde.org/show_bug.cgi?id=442876 bombela+...@gmail.com changed: What|Removed |Added CC||bombela+...@gmail.com --- Comment #6 from bombela+...@gmail.com --- Same here, KDE/wayland. Spectacle has a delay oscillating between 1.2s to almost 3s. spectacle --version (takes 390ms to print the version) spectacle 23.08.5 plasmashell --version (takes 280ms to print the version) plasmashell 5.27.11 The fact that KDE executable take that long to print a simple version string is quite worrisome, though it doesn't explain the whole delay with spectacle, it is most likely compounding. With that said, this is a sad trend in software over the years (more lag and delays for no reason). The following examples are taken on power save mode (ie: battery power). When powered, it is usually 50% faster. Thinkpad T14 AMD gen2. xterm --help: 11ms alacritty --version (0.13.2): 8ms konsole --version (23.08.05): 270ms grep --version: 5ms ripgrep --version: 5ms kicad-cli --version (8.0.2): 240ms gnome-disks --help: 32ms kcalc --version (23.08.05): 250ms qalc --version (4.9.0): 19ms vlc --version (3.0.20): 17ms dragon --version (23.08.5): 250ms -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487788] New: Empty folder with artifacts after navigating to empty forlder
https://bugs.kde.org/show_bug.cgi?id=487788 Bug ID: 487788 Summary: Empty folder with artifacts after navigating to empty forlder Classification: Applications Product: dolphin Version: 24.05.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: tribunal2...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 169979 --> https://bugs.kde.org/attachment.cgi?id=169979=edit Empty folder with artifacts SUMMARY Navigating empty folder is not correct STEPS TO REPRODUCE 1. Open folder with some files 2. Navigate to empty folder OBSERVED RESULT Got artifacts from previous folder EXPECTED RESULT There are no artifacts, only "The folder is empty" must be shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro/KDE KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Looks like dubpicate very old bug https://bugs.kde.org/show_bug.cgi?id=300640 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 300640] After changing to an empty folder in details mode from a folder in icons mode, pieces of headers are shown above the icons of the previous folder
https://bugs.kde.org/show_bug.cgi?id=300640 tribunal2...@gmail.com changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED CC||tribunal2...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487786] New: can't save any filetype in any folder "error: Cannot open file for writing." (i have full permissions for the folder and all other programs can save to it.)
https://bugs.kde.org/show_bug.cgi?id=487786 Bug ID: 487786 Summary: can't save any filetype in any folder "error: Cannot open file for writing." (i have full permissions for the folder and all other programs can save to it.) Classification: Applications Product: krita Version: 5.2.2 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: mr.flaresp...@gmail.com Target Milestone: --- Created attachment 169975 --> https://bugs.kde.org/attachment.cgi?id=169975=edit usage log file *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY can't save/export file in any folder, despite having full permissions for my preferred folder. STEPS TO REPRODUCE 1. open krita on my computer i guess 2. try to save anything/let autosave try to save 3. error: cannot open file for writing OBSERVED RESULT literally cannot save at all (or even export), in any folder (unless i start the program in administrator mode) EXPECTED RESULT i'd like to be able to save my progress/export my art. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION i have tested other programs such as gimp, and they can save files in the same folder that krita is unable to. please do not dismiss this as "not a bug" like the other similar report, it is clearly a krita specific problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437162] Ship or allow support for better colour correction
https://bugs.kde.org/show_bug.cgi?id=437162 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|7.50|7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 481240] pick label from Image Quality Sort is not automatically written to the file
https://bugs.kde.org/show_bug.cgi?id=481240 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|8.4.0 |8.3.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 481240] pick label from Image Quality Sort is not automatically written to the file
https://bugs.kde.org/show_bug.cgi?id=481240 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version Fixed In|481240 |8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482262] Gwenview: Color Picker is missing: On Plasma 6, the "Select Color" menu won't show when you click on color palette => the three-dot button.
https://bugs.kde.org/show_bug.cgi?id=482262 athaswildwhisper55232.untainted...@aleeas.com changed: What|Removed |Added Summary|Gwenview: On Plasma 6, the |Gwenview: Color Picker is |"Select Color" menu won't |missing: On Plasma 6, the |show when you click on |"Select Color" menu won't |color palette => the|show when you click on |three-dot button. |color palette => the ||three-dot button. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #21 from caulier.gil...@gmail.com --- Hi, Ok next build will arrive this evening. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 238587] Hierarchal date based folder creation upon import of images.
https://bugs.kde.org/show_bug.cgi?id=238587 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 487477] Stock price refresh not working anymore
https://bugs.kde.org/show_bug.cgi?id=487477
--- Comment #4 from firefox-...@web.de ---
I wasn't precise enough, I haven't been using the Wizard but the settings
dialog (see attachment).
The script gives:
$ /home/foo/Projekte/Python/kmymoney_update_price/kmymoney_update_price.py
DE000A1EWWW0
Symbol: DE000A1EWWW0
Price: 12.12
Date: 13.05.2024
kmymoney's output:
reading file
start parsing file
startDocument
reading securities
endDocument
Cost center model created with items 0
Payees model created with items 0
created tmpfile
kf.kio.core: Invalid URL:
QUrl("/home/foo/Projekte/Python/kmymoney_update_price/kmymoney_update_price.py
DE000A1EWWW0")
kf.kio.workers.file: readData() returned -1
kmymoney_webpricequote: quotedata ""
Does it mean QUrl cannot cope (anymore) with a local address? I've also tried
file:///home/...
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 487477] Stock price refresh not working anymore
https://bugs.kde.org/show_bug.cgi?id=487477 --- Comment #3 from firefox-...@web.de --- Created attachment 169968 --> https://bugs.kde.org/attachment.cgi?id=169968=edit settings dialog -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487781] New: Task Manager placed on incorrect monitor when selecting primary display
https://bugs.kde.org/show_bug.cgi?id=487781 Bug ID: 487781 Summary: Task Manager placed on incorrect monitor when selecting primary display Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: boysa...@0xa.pw CC: qydwhotm...@gmail.com Target Milestone: 1.0 Created attachment 169967 --> https://bugs.kde.org/attachment.cgi?id=169967=edit Display Assignment Settings *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Use "Change Screen Priorities" under Display & Monitor in System Settings, set display that should be primary to the top of the list 2. Click apply OBSERVED RESULT Task Manager (taskbar) at bottom of display is placed on a different display than the one that was set to primary. EXPECTED RESULT Task Manager (taskbar) at bottom of display should be placed on the same display that is marked as "Primary" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro, kernel 6.9.2-1-MANJARO (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION System Info: Intel i7-12700K 32GB DDR4-4000 Nvidia RTX 3090 running proprietary driver version 550.78, nvidia_drm.modeset=1 in kernel options -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487728] Plasma panel/widgets freeze randomly with explicit sync, can be unfreezed by going into overview
https://bugs.kde.org/show_bug.cgi?id=487728 --- Comment #3 from kodatar...@yahoo.com --- Apologies for another reply, but I found an even easier way to reproduce it, launch mpv get it to the screen where the panel dodges windows, make it fullscreen = desktop/panels/widgets/etc have frozen, make it back windowed everything is flawless like in 6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487728] Plasma panel/widgets freeze randomly with explicit sync, can be unfreezed by going into overview
https://bugs.kde.org/show_bug.cgi?id=487728 --- Comment #2 from kodatar...@yahoo.com --- Just a small update, I was able to trigger a reproducible state 100% on plasma 6.1 beta: Have 2 panels on 2 different monitors, both floating, the one on your second monitor to dodge windows(being hidden underneath them). Open browser on main monitor where floating panel just maximizes then super+shift+right/left arrow to move it to the monitor where it hides the panel, boom the desktop/widgets/panels freeze and opening overview a few times fixes this state. I also noticed these in my journalctl kwin_core: Failed to focus 0x434 (error 8) kwin_core: Failed to focus 0x385 (error 3) kwin_core: Failed to focus 0x385 (error 3) -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore
https://bugs.kde.org/show_bug.cgi?id=487566 --- Comment #22 from fanzhuyi...@gmail.com --- (In reply to Phil Brown from comment #21) > Comment on attachment 169966 [details] > demo3 > > OK, so you have it calculating a result with every keystroke, unlike every > other calculator since the invention of the electronic calculator That was intentionally implemented in https://invent.kde.org/utilities/kcalc/-/merge_requests/84 as a feature. Please keep the discussion here on topic about chaining results into the next calculation, which seems to be fully implemented in the demos. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487544] Saving a TIFF file, then closing and reopening Krita 5.2.2+, causes a crash when it tries to load the TIFF file in the file preview window
https://bugs.kde.org/show_bug.cgi?id=487544 foodric...@gmail.com changed: What|Removed |Added Summary|Saving a TIFF file, then|Saving a TIFF file, then |closing and reopening Krita |closing and reopening Krita |5.2.3+, causes a crash when |5.2.2+, causes a crash when |it tries to load the TIFF |it tries to load the TIFF |file in the file preview|file in the file preview |window |window -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487775] New: Cannot delete directories from the projects panel
https://bugs.kde.org/show_bug.cgi?id=487775 Bug ID: 487775 Summary: Cannot delete directories from the projects panel Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: erentar2...@gmail.com Target Milestone: --- Created attachment 169962 --> https://bugs.kde.org/attachment.cgi?id=169962=edit No delete option for directories *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. open kate by running `kate .` from a code folder 2. create a directory by right-clicking on the projects pane 3. right click on the created directory, no delete option. 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.
[kwordquiz] [Bug 487774] New: Opening Tab-Separated CSV Files From Terminal
https://bugs.kde.org/show_bug.cgi?id=487774 Bug ID: 487774 Summary: Opening Tab-Separated CSV Files From Terminal Classification: Applications Product: kwordquiz Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: pe...@peterandlinda.com Reporter: promike1...@gmail.com CC: aa...@kde.org Target Milestone: --- SUMMARY When attempting to run KWordQuiz from the terminal and opening a tab-separated CSV file using the command kwordquiz -g flash -- /path/to/file.csv or kwordquiz -g flash --+ /path/to/file.csv, the options did not work as expected. Additionally, using the --+ option resulted in the error message "kwordquiz: Unknown option '+'". No difference was observed when using the -g flash, -g mc, or -g qa options. STEPS TO REPRODUCE Run kwordquiz -g flash -- /path/to/file.csv or kwordquiz -g flash --+ /path/to/file.csv from the terminal. OBSERVED RESULT The options -g flash -- /path/to/file.csv and -g flash --+ /path/to/file.csv did not work as expected. Using the --+ option resulted in the error message "kwordquiz: Unknown option '+'". EXPECTED RESULT The command kwordquiz -g flash -- /path/to/file.csv or kwordquiz -g flash --+ /path/to/file.csv should open the specified tab-separated CSV file for the flashcard session as intended. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Kernel Version: 6.6.30-2-lts (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i3-2350M CPU @ 2.30GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 3000 System Version: 1.0 KWordQuiz Version: 24.02.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487771] kwin_x11 crashed 3 times when logging back in with momentary blurred graphic artifacts
https://bugs.kde.org/show_bug.cgi?id=487771 k...@assez.biz changed: What|Removed |Added Summary|kwin_x11 crashed when |kwin_x11 crashed 3 times |logging back in with|when logging back in with |momentary blurred graphic |momentary blurred graphic |artifacts |artifacts --- Comment #1 from k...@assez.biz --- As stated, crashed 3 times in a row when logging back in, but the crashes almost all happened at once, within 1s or 2s. I only catched the "Report Bug" on the last of the 3 subsequent crashes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487771] New: kwin_x11 crashed when logging back in with momentary blurred graphic artifacts
https://bugs.kde.org/show_bug.cgi?id=487771 Bug ID: 487771 Summary: kwin_x11 crashed when logging back in with momentary blurred graphic artifacts Classification: Plasma Product: kwin Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@assez.biz Target Milestone: --- Application: kwin_x11 (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-21-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Happened after logging back in after ~4h idling, nothing special, few apps already running in background. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault PID: 8281 (kwin_x11) UID: 1000 (shdw) GID: 1000 (shdw) Signal: 11 (SEGV) Timestamp: Wed 2024-05-29 18:34:42 EDT (48s ago) Command Line: /usr/bin/kwin_x11 --replace Executable: /usr/bin/kwin_x11 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_x11.service Unit: user@1000.service User Unit: plasma-kwin_x11.service Slice: user-1000.slice Owner UID: 1000 (shdw) Boot ID: fcc6c7602e9447119e2f9ee11d180bae Machine ID: 08af5a160a73489cbc34c69efa52ef57 Hostname: e15-debian Storage: /var/lib/systemd/coredump/core.kwin_x11.1000.fcc6c7602e9447119e2f9ee11d180bae.8281.171702208200.zst (present) Size on Disk: 8.5M Message: Process 8281 (kwin_x11) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.22-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.22-1~deb12u1.amd64 Stack trace of thread 8281: #0 0x7efc8cffcd14 __GI___pthread_sigmask (libc.so.6 + 0x8fd14) #1 0x7efc8cfa9239 __GI___sigprocmask (libc.so.6 + 0x3c239) #2 0x7efc8fb20e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7efc8fb21b3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7efc8cfa9050 __restore_rt (libc.so.6 + 0x3c050) #5 0x558d7671d5a6 n/a (kwin_x11 + 0xb25a6) #6 0x558d7671dd5b n/a (kwin_x11 + 0xb2d5b) #7 0x7efc8fd46b67 _ZN4KWin18EffectsHandlerImpl14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin.so.5 + 0x21cb67) #8 0x7efc8fde31d3 _ZN4KWin14WorkspaceScene24preparePaintSimpleScreenEv (libkwin.so.5 + 0x2b91d3) #9 0x7efc8fde3685 _ZN4KWin14WorkspaceScene8prePaintEPNS_13SceneDelegateE (libkwin.so.5 + 0x2b9685) #10 0x7efc8fd021ef _ZN4KWin10Compositor12prePaintPassEPNS_11RenderLayerE (libkwin.so.5 + 0x1d81ef) #11 0x7efc8fd0537f _ZN4KWin10Compositor9compositeEPNS_10RenderLoopE (libkwin.so.5 + 0x1db37f) #12 0x7efc8fd07293 _ZN4KWin13X11Compositor9compositeEPNS_10RenderLoopE (libkwin.so.5 + 0x1dd293) #13 0x7efc8e4c7f4f n/a (libQt5Core.so.5 + 0x2e8f4f) #14 0x7efc8fcba0c2 _ZN4KWin10RenderLoop14frameRequestedEPS0_ (libkwin.so.5 + 0x1900c2) #15 0x7efc8fd0eed3 _ZN4KWin17RenderLoopPrivate8dispatchEv (libkwin.so.5 + 0x1e4ed3) #16 0x7efc8e4c7f4f n/a (libQt5Core.so.5 + 0x2e8f4f) #17 0x7efc8e4cbd6a _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2ecd6a) #18 0x7efc8e4bc50d _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd50d) #19 0x7efc8d718fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #20 0x7efc8e4906f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #21 0x7efc8e4e7c31 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x308c31) #22 0x7efc8e4e84c4 n/a (libQt5Core.so.5 + 0x3094c4) #23 0x7efc8bc1e7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #24 0x7efc8bc1ea38 n/a (libglib-2.0.so.0 + 0x54a38) #25 0x7efc8bc1eacc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #26 0x7efc8e4e8836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #27 0x7efc8e48f17b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #28 0x7efc8e4972d6
[kwin] [Bug 487701] kwin_wayland crash when screen goes blank for a while with Plasma 6.0.90
https://bugs.kde.org/show_bug.cgi?id=487701 ollil...@unitybox.de changed: What|Removed |Added Summary|Plasmashell crash when |kwin_wayland crash when |screen goes blank for a |screen goes blank for a |while with Plasma 6.0.90|while with Plasma 6.0.90 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487701] Plasmashell crash when screen goes blank for a while with Plasma 6.0.90
https://bugs.kde.org/show_bug.cgi?id=487701 ollil...@unitybox.de changed: What|Removed |Added Target Milestone|1.0 |--- Component|generic-crash |wayland-generic Product|plasmashell |kwin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487701] Plasmashell crash when screen goes blank for a while with Plasma 6.0.90
https://bugs.kde.org/show_bug.cgi?id=487701 ollil...@unitybox.de changed: What|Removed |Added Assignee|plasma-b...@kde.org |ollil...@unitybox.de --- Comment #4 from ollil...@unitybox.de --- Created attachment 169960 --> https://bugs.kde.org/attachment.cgi?id=169960=edit Backtrace from crashing kwin_wayland Since i found out that "kwin_wayland" is crashing i made a backtrace with "gdb -q /usr/bin/kwin_wayland". I think that the Problem is "kwin_wayland" -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487769] New: Discover reports no packages installed
https://bugs.kde.org/show_bug.cgi?id=487769 Bug ID: 487769 Summary: Discover reports no packages installed Classification: Applications Product: Discover Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: drjohnpa...@gmail.com CC: aleix...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Discover reports 0 items installed STEPS TO REPRODUCE 1. While upgrading from Kubuntu 23.01 to 24.04, I unchecked the "Unsupported sources" button in Discover. That caused it to lose track of the installed software, which now shows Installed: 0. 2. 3. OBSERVED RESULT Discover sees no installed packages. EXPECTED RESULT It should show the installed packages I have. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Kernel: 6.8.0-31-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487701] Plasmashell crash when screen goes blank for a while with Plasma 6.0.90
https://bugs.kde.org/show_bug.cgi?id=487701 ollil...@unitybox.de changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487701] Plasmashell crash when screen goes blank for a while with Plasma 6.0.90
https://bugs.kde.org/show_bug.cgi?id=487701 --- Comment #3 from ollil...@unitybox.de --- I forgot something, dmesg says: [ 172.436605] kwin_wayland[1197]: segfault at 58 ip 7f2619081ab4 sp 7fff52b0c408 error 4 in libkwin.so.6.0.90[7f2618f4d000+55b000] likely on CPU 31 (core 15, socket 0) [ 172.436614] Code: b2 7c ef ff 66 90 5b c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa c6 47 5c 01 c3 90 66 0f 1f 44 00 00 f3 0f 1e fa <8b> 47 58 ff 4f 54 85 c0 75 06 80 7f 5c 00 75 0c c3 66 66 2e 0f 1f -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487701] Plasmashell crash when screen goes blank for a while with Plasma 6.0.90
https://bugs.kde.org/show_bug.cgi?id=487701 --- Comment #2 from ollil...@unitybox.de --- Created attachment 169959 --> https://bugs.kde.org/attachment.cgi?id=169959=edit Backtrace of plasmashell crashing Today i recompiled my system with cflags "-march=znver3 -O2 -mtune=znver3 -pipe -g -ggdb" and FEATURES="parallel-install parallel-fetch fixlafiles nostrip" so that everything is compiled with debug symbols. I startet gdb with "gdb -q /usr/bin/plasmashell" But in the logfile there comes only the output "no stack". These are the last lines in gdb before plasmashell crashes: Thread 0x7fff956006c0 (LWP 2693) exited] [Thread 0x7fff8b4006c0 (LWP 2692) exited] [Thread 0x7fff72a006c0 (LWP 2591) exited]org.kde.pulseaudio: No object for name "alsa_output.pci-_09_00.1.hdmi-stereo" [New Thread 0x7fffa2a006c0 (LWP 2685)] [New Thread 0x7fff8b4006c0 (LWP 2686)] [New Thread 0x7fff956006c0 (LWP 2687)] [Thread 0x7fff956006c0 (LWP 2687) exited] [Thread 0x7fff8b4006c0 (LWP 2686) exited] [Thread 0x7fffa2a006c0 (LWP 2685) exited] [New Thread 0x7fffa2a006c0 (LWP 2691)] [New Thread 0x7fff8b4006c0 (LWP 2692)] [New Thread 0x7fff956006c0 (LWP 2693)] org.kde.pulseaudio: No object for name "alsa_output.pci-_09_00.1.hdmi-stereo" The Wayland connection broke. Did the Wayland compositor die? [Thread 0x7fff734006c0 (LWP 2590) exited] [Thread 0x7fff73e006c0 (LWP 2589) exited] [Thread 0x7fff7e0006c0 (LWP 2588) exited] [Thread 0x7fff7ea006c0 (LWP 2587) exited] [Thread 0x7fff7f4006c0 (LWP 2586) exited] [Thread 0x7fff70a006c0 (LWP 2585) exited] [Thread 0x7fff714006c0 (LWP 2576) exited] [Thread 0x7fff71e006c0 (LWP 2572) exited] [Thread 0x7fff7d0006c0 (LWP 2571) exited] [Thread 0x7fffc56006c0 (LWP 2532) exited] [Thread 0x7fffc60006c0 (LWP 2531) exited] [Thread 0x7fffc6a006c0 (LWP 2530) exited] [Thread 0x7fffc74006c0 (LWP 2528) exited] [Thread 0x7fffcf4006c0 (LWP 2525) exited] [Thread 0x7fffcfe006c0 (LWP 2524) exited] [Thread 0x7fffe4c006c0 (LWP 2523) exited] [Thread 0x7fffd7e006c0 (LWP 2519) exited] [Thread 0x7fffdd2006c0 (LWP 2505) exited] [Thread 0x7fffe74006c0 (LWP 2491) exited] [Thread 0x7fffe7e006c0 (LWP 2490) exited] [Thread 0x7fffed6006c0 (LWP 2489) exited] [Thread 0x70373a00 (LWP 2486) exited] [Thread 0x7fffa2a006c0 (LWP 2691) exited] [New process 2486] [Inferior 1 (process 2486) exited with code 0377] I hope it helps. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 487767] New: Add finish or close button to the automatic crash handler
https://bugs.kde.org/show_bug.cgi?id=487767 Bug ID: 487767 Summary: Add finish or close button to the automatic crash handler Classification: Applications Product: drkonqi Version: master Platform: Other OS: Linux Status: REPORTED Keywords: junior-jobs Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: duha.b...@gmail.com Target Milestone: --- Created attachment 169958 --> https://bugs.kde.org/attachment.cgi?id=169958=edit missing_button The "Automatic Crash handler" could use a "finish" or "close" button after sending a automatic report. It is a bit unexpected that this window can only be closed by the window decoration. See image attached. -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 485560] Google Calendar Stuck in Retrieving Task List
https://bugs.kde.org/show_bug.cgi?id=485560 m.f.alexandre...@gmail.com changed: What|Removed |Added Version Fixed In||24.05 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from m.f.alexandre...@gmail.com --- I believe this bug has been fixed, as of version 24.05. I've tested for a few days, and everything seems to be working very well. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 487766] Manpages formatting issues
https://bugs.kde.org/show_bug.cgi?id=487766 bjoe...@arcor.de changed: What|Removed |Added CC||bjoe...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 487766] Manpages formatting issues
https://bugs.kde.org/show_bug.cgi?id=487766 --- Comment #1 from bjoe...@arcor.de --- Created attachment 169957 --> https://bugs.kde.org/attachment.cgi?id=169957=edit examples in helpcenter (left) and in PDF/Okular (right) -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 487766] New: Manpages formatting issues
https://bugs.kde.org/show_bug.cgi?id=487766
Bug ID: 487766
Summary: Manpages formatting issues
Classification: Applications
Product: khelpcenter
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kde-doc-engl...@kde.org
Reporter: bjoe...@arcor.de
Target Milestone: ---
Created attachment 169956
--> https://bugs.kde.org/attachment.cgi?id=169956=edit
lists in helpcenter (left) and PDF/Okular (right)
Some manpages in Help Center show formatting issues. I found this issue in
khelpcenter-24.02.2 (this version can't be selected here).
STEPS TO REPRODUCE
1. Ensure that man-pages are installed (tested with man-pages-6.8)
2. Search for "man:string_copying" in KDE start menu
3. Compare displayed manpage with the "man string_copying" command or with PDF
manpage ("man -Tpdf string_copying > string_copying.pdf")
OBSERVED RESULT
The lists in the manpage have extra newlines (lists.png)
In examples section the source code is hard to read because of missing
newslines (examples.png).
EXPECTED RESULT
The formatted manpages should look similar to PDF version or text version.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 5.116.0
Qt Version: 6.7.0
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 487765] New: Kate Icon in Dock very often asks for attention
https://bugs.kde.org/show_bug.cgi?id=487765 Bug ID: 487765 Summary: Kate Icon in Dock very often asks for attention Classification: Applications Product: kate Version: 24.05.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: tob...@g3ro.eu Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Whenever I use multiple instances of Kate, the Kate icon in the Dock very often turns yellow/orange and turns into foreground and wants attention, for no apparent reason. It seems that the "internal console" (called "output" in german) (button on the bottom left in Kate) is blinking too. I always have to click on the icon so it goes back into background. This is quite annoying. I file this bug here, because I don't have this problem with other programs, only with Kate. STEPS TO REPRODUCE 1. see above OBSERVED RESULT See above. EXPECTED RESULT No behaviour like above. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.6.32-1-lts (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa Intel® Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485520] Redundant unlock button appears after password when resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=485520 ftfeob+kdebugtrac...@gmail.com changed: What|Removed |Added CC||ftfeob+kdebugtracker@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 76082] smooth scrolling in all apps
https://bugs.kde.org/show_bug.cgi?id=76082 kde.aerospace...@aleeas.com changed: What|Removed |Added CC||kde.aerospace...@aleeas.com --- Comment #146 from kde.aerospace...@aleeas.com --- Smooth scrolling does seem to work now in most apps, but in the dolphin sidebar, it does not. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487759] New: Vulkan wayland native windows go crazy when in fullscreen at random.
https://bugs.kde.org/show_bug.cgi?id=487759 Bug ID: 487759 Summary: Vulkan wayland native windows go crazy when in fullscreen at random. Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: c9lyw0...@mozmail.com Target Milestone: --- Created attachment 169953 --> https://bugs.kde.org/attachment.cgi?id=169953=edit Example with Minecraft running on Vulkan thanks to the vulkanmod (should work properly) SUMMARY Apps open in random screens instead of the main (and focused) one, and they flicker a lot while focused. STEPS TO REPRODUCE 1. launch your favorite Vulkan app with Wayland native mode 2. set it in fullscreen. 3. done. OBSERVED RESULT The apps open on wrong (random) screens, and flicker while in fullscreen. Sometimes they don't have an issue, sometimes they do. It's random... Hardly trackable because of lack of ways to get logs. EXPECTED RESULT The apps should run normally, without flickering. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Void-Linux 6.9.2 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION - I can't find a way to get logs. - The issue doesn't seem to happen with my Void-Linux laptop, that runs the exact same config. - Dmesg prints nothing - the vulkan loader debug mode (VK_LOADER_DEBUG=all) prints nothing as well - Vulkan validation layers print nothing as well. I try my luck here, after trying on the Void-Linux github repo, then vulkan-loader repo. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 282099] Easier installation (compare to Building Digikam for Dummies on Ubuntu and other linux based distro´s).
https://bugs.kde.org/show_bug.cgi?id=282099 caulier.gil...@gmail.com changed: What|Removed |Added Summary|easier installation |Easier installation |(compare to Building|(compare to Building |Digikam for Dummies on |Digikam for Dummies on |Ubuntu and other linux |Ubuntu and other linux |based distro´s) |based distro´s). Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478375] Cannot update database with digikam mysql executables. Brew mysql executables work partially.
https://bugs.kde.org/show_bug.cgi?id=478375 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479307] digiKam: no pictures to pick after application starts
https://bugs.kde.org/show_bug.cgi?id=479307 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|8.4.0 | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479307] digiKam: no pictures to pick after application starts
https://bugs.kde.org/show_bug.cgi?id=479307 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479675] Missing Thumbnails with External Drive
https://bugs.kde.org/show_bug.cgi?id=479675 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486236] Cannot change a time zone.
https://bugs.kde.org/show_bug.cgi?id=486236 --- Comment #6 from gigastarcra...@proton.me --- (In reply to gigastarcraft2 from comment #5) > (In reply to David Edmundson from comment #4) > > >"Failed to set current time > > >"org.freedesktop.PolicyKit1.Error.NotAuthorized" "Authorizing for > > >'org.freedesktop.timedate1.set-time': not authorized"" > > > > It's using a systemd path. I assume you don't have systemd? > > No, I use Artix OpenRC. I get warning "System policy prevents changing > timezone" I tried changing time zone using following commands: Configure the system clock Set the time zone: ln -sf /usr/share/zoneinfo/Region/City /etc/localtime Run hwclock to generate /etc/adjtime: hwclock --systohc https://wiki.artixlinux.org/Main/Installation#Configure_the_system_clock and it worked! Thus I think it is KDE bug and not Artix. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478797] Metabug: issues with Panel in "Auto-Hide" or "Dodge Windows" modes inappropriately hiding or un-hiding in various circumstances
https://bugs.kde.org/show_bug.cgi?id=478797 --- Comment #7 from fanzhuyi...@gmail.com --- If you want to report a concrete bug, please don't report it here. Instead, please open a new bug report (after checking that it hasn't been reported). Then, in the new bug report, go to the Blocks field and enter the bug number of this bug (478797). If you don't know how to do that, don't worry, someone will do that for you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487750] Kwin never notifies the systemd watchdog and gets killed
https://bugs.kde.org/show_bug.cgi?id=487750 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 487709] When Konsole calls firefox the text is uneven.
https://bugs.kde.org/show_bug.cgi?id=487709 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |DOWNSTREAM Status|NEEDSINFO |RESOLVED --- Comment #4 from fanzhuyi...@gmail.com --- This appears to be an issue with the local configuration (e.g., maybe font config?) or a firefox issue rather than an issue with konsole. So marking this as DOWNSTREAM. Perhaps a better place to ask for help would be the arch forums (assuming you are using arch). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #17 from caulier.gil...@gmail.com --- Hi Maik, The Windows installer is now up-to-date... Gilles -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487749] New: Application Dashboard, Application Menu panel icons have unusually large padding on their sides
https://bugs.kde.org/show_bug.cgi?id=487749 Bug ID: 487749 Summary: Application Dashboard, Application Menu panel icons have unusually large padding on their sides Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: joey.joey...@gmail.com Target Milestone: 1.0 Created attachment 169940 --> https://bugs.kde.org/attachment.cgi?id=169940=edit screenshots of the bug SUMMARY See title above STEPS TO REPRODUCE 1. Place Application Dashboard or Application Menu applet on a panel 2. 3. OBSERVED RESULT Panel icons of both have larger side padding than Application Launcher (kickoff) EXPECTED RESULT Icon padding of both should be the same size as kickoff's SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 2 × AMD A9-9420e RADEON R5, 5 COMPUTE CORES 2C+3G Memory: 7.2 GiB of RAM Graphics Processor: AMD Radeon R5 Graphics Manufacturer: Dell Inc. Product Name: Inspiron 3180 System Version: 1.1.0 ADDITIONAL INFORMATION See images in zip attached below -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478797] Metabug: issues with Panel in "Auto-Hide" or "Dodge Windows" modes inappropriately hiding or un-hiding in various circumstances
https://bugs.kde.org/show_bug.cgi?id=478797 --- Comment #4 from fanzhuyi...@gmail.com --- (In reply to LDWilliams from comment #3) > the icons only task manager is Not auto hiding on the main monitor, but > does when the panel is moved to a secondary window. Please open a new bug report for that and mark it as blocking this one. Also note that if the auto-hide panel is on a shared edge between monitors, auto-hide will only start working on wayland in plasma 6.1, and currently there are no plans to implement this on X11 (see BUG 351175). Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480355] Add Telex as an additional Vietnamese keyboard layout variant
https://bugs.kde.org/show_bug.cgi?id=480355 --- Comment #4 from ea.vj...@aleeas.com --- The xkeyboard-config maintainers closed the request, stating "it is an input method, not a layout": https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/437#note_2431565 I'm not entirely sure what the differences are, but it sounds like an input method is more complicated than a layout. Does this mean Plasma cannot have Vietnamese Telex as an option? Gnome has it. Right now, I'm using fcitx5 to be able to type using Telex, but some applications don't work with it. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 487741] New: KDE Connect failed to send file from phone via WiFi, noticed crash after cancelling sending
https://bugs.kde.org/show_bug.cgi?id=487741 Bug ID: 487741 Summary: KDE Connect failed to send file from phone via WiFi, noticed crash after cancelling sending Classification: Applications Product: kdeconnect Version: 23.08.4 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: opensuse.lietuviu.ka...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (23.08.4) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.14.21-150500.55.65-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.5" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: I tried to small video (~15MB) to laptop via KDE Connect in same WiFi network. Only few kB sent and thrn hanged. After minute I press cancel trasfer and then noticed crash report. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDE Connect tarnyba (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x in () #5 0x7fa59cede8bf in checkWarnMessage(QIODevice const*, char const*, char const*) (device=device@entry=0x55884828c170, function=function@entry=0x7fa59d0b1e32 "read", what=what@entry=0x7fa59d0b08f4 "device not open") at io/qiodevice.cpp:98 #6 0x7fa59cedf9d7 in QIODevice::read(char*, long long) (this=this@entry=0x55884828c170, data=0x558848620d88 "q\260\222\at\\\331\334\260\260g\230,\375sz\026\336\377\254\251I\017\341S~\341\235\372\3375k\254\017\227\021B(\351K\t\025\243+*C-\240)\372\353XY\2160\321\210", maxSize=maxSize@entry=16384) at io/qiodevice.cpp:1051 #7 0x7fa59cee64da in QNonContiguousByteDeviceIoDeviceImpl::readPointer(long long, long long&) (this=0x5588485861a0, maximumLength=, len=@0x7fff2d62a570: 140349281151488) at io/qnoncontiguousbytedevice.cpp:318 #8 0x7fa59c5db3f3 in QNetworkAccessFileBackend::uploadReadyReadSlot() (this=0x558848563c90) at access/qnetworkaccessfilebackend.cpp:193 #9 0x7fa59cff6785 in doActivate(QObject*, int, void**) (sender=0x5588485861a0, signal_index=3, argv=0x7fff2d62a6b0) at kernel/qobject.cpp:3935 #10 0x7fa59cfed4ab in QObject::event(QEvent*) (this=0x5588485861a0, e=0x5588484a90c0) at kernel/qobject.cpp:1347 #11 0x7fa59db6e53c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x5588481c8540, receiver=receiver@entry=0x5588485861a0, e=e@entry=0x5588484a90c0) at kernel/qapplication.cpp:3640 #12 0x7fa59db752ff in QApplication::notify(QObject*, QEvent*) (this=, receiver=0x5588485861a0, e=0x5588484a90c0) at kernel/qapplication.cpp:3164 #13 0x7fa59cfb9013 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5588485861a0, event=0x5588484a90c0) at kernel/qcoreapplication.cpp:1064 #14 0x7fa59cfb91ee in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=receiver@entry=0x5588485861a0, event=event@entry=0x5588484a90c0) at kernel/qcoreapplication.cpp:1462 #15 0x7fa59cfbba31 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x5588481ad0d0) at kernel/qcoreapplication.cpp:1821 #16 0x7fa59cfbbfb8 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1680 #17 0x7fa59d01c2b3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5588482ac3c0) at kernel/qeventdispatcher_glib.cpp:277 #18 0x7fa59acc182b in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #19 0x7fa59acc1bd0 in () at /usr/lib64/libglib-2.0.so.0 #20 0x7fa59acc1c5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #21 0x7fa59d01b95c in QEventDispatcherGlib::processEvents(QFlags) (this=0x5588482b1240, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7fa59cfb787a in QEventLoop::exec(QFlags) (this=this@entry=0x7fff2d62ac60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:235 #23 0x7fa59cfc10b7 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1375 #24 0x55884783de3f in main () [Inferior 1 (process 5360) detached] The reporter indicates this bug may be a duplicate of or related to bug 481411. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486236] Cannot change a time zone.
https://bugs.kde.org/show_bug.cgi?id=486236 --- Comment #5 from gigastarcra...@proton.me --- (In reply to David Edmundson from comment #4) > >"Failed to set current time "org.freedesktop.PolicyKit1.Error.NotAuthorized" > >"Authorizing for 'org.freedesktop.timedate1.set-time': not authorized"" > > It's using a systemd path. I assume you don't have systemd? No, I use Artix OpenRC. I get warning "System policy prevents changing timezone" -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 89299] prevent paste of newline characters
https://bugs.kde.org/show_bug.cgi?id=89299 gudvinr+...@gmail.com changed: What|Removed |Added CC||gudvinr+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487738] crash: Data too big for buffer
https://bugs.kde.org/show_bug.cgi?id=487738 --- Comment #1 from p...@pfortin.com --- See attachment; crash report included: May 28 13:41:20 kwin_wayland_wrapper[40581]: Data too big for buffer (4108 > 4096) at the time I clicked on the notification icon and instantly crashed. As always: # coredumpctl --reverse No coredumps found. While wayland is missing features, my last use of X11 was too unstable for normal use. PS: Hitting Enter (for new line) in attachment description submitted report before I was done editing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487695] Windows always open on all activities since 6.0.5 - also can't move windows to other activities
https://bugs.kde.org/show_bug.cgi?id=487695 bastimeyer...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from bastimeyer...@gmail.com --- Looks like this was a build issue on my end. I've re-built everything and the issue is now gone. It didn't even make sense considering the commit histories of all the repos involved (kwin / plasma-workspace, and dependencies). Sorry for the unnecessary noise. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487738] New: crash: Data too big for buffer
https://bugs.kde.org/show_bug.cgi?id=487738 Bug ID: 487738 Summary: crash: Data too big for buffer Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: p...@pfortin.com Target Milestone: 1.0 Created attachment 169934 --> https://bugs.kde.org/attachment.cgi?id=169934=edit output of "journalctl -b -1 -g plasma > /tmp/plasmashell_crashes" *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY After some time, plasmashell starts crashing. When it starts, it just keeps getting worse, until every mouse click or mouse over triggers a crash. In this case, got a notification at a time I was too busy to read; then clicked notifications icon in systray --> instant crash. STEPS TO REPRODUCE 1. use the system -- 3 screens, panels on each screen. Only main screen has full panel. 2. mouse over|click any panel 3. OBSERVED RESULT crash & auto-restart (though not always -- need to issue plasmashell --replace) Journal log (see attachment for surrounding messages) May 28 13:41:20 kwin_wayland_wrapper[40581]: Data too big for buffer (4108 > 4096). May 28 13:41:20 kwin_wayland_wrapper[40581]: error in client communication (pid 2425188) EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Operating System: Mageia 10 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.6.2 Kernel Version: 6.6.28-server-1.mga10 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700K Memory: 125.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: Dell Inc. Product Name: XPS 8950 ADDITIONAL INFORMATION Once the crashes start, they become worse. The first was when I clicked the notification icon; then, it was emacs, desktop selection, or just moving mouse over taskbar (anywhere). -- You are receiving this mail because: You are watching all bug changes.
[klines] [Bug 487737] New: Disabling Show Next feature only affects the scoring system until the user restarts the game
https://bugs.kde.org/show_bug.cgi?id=487737 Bug ID: 487737 Summary: Disabling Show Next feature only affects the scoring system until the user restarts the game Classification: Applications Product: klines Version: 1.6.21123 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dim...@gmail.com Reporter: gosta...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY The bug happens when the Show Next feature is disabled. Immediately after disabling the Show Next feature, scores are awarded correctly (11 for 5 removed marbles). After starting New Game (Game -> New), scores are awarded incorrectly as if Show Next was enabled (10 for 5 removed marbles). STEPS TO REPRODUCE 1. Launch Kolor Lines. Disable Settings -> Show Next. (If it was already disabled, enable it and then disable again.) 2. Play the game and observe that completing a line of 5 marbles gives score 11. 3. Restart the game (Game -> New). 4. Play the game and observe that completing a line of 5 marbles gives score 10 now, even though Show Next is still disabled. OBSERVED RESULT Disabling "Settings -> Show Next" only affects the scoring system until the user restarts the game. EXPECTED RESULT Disabling "Settings -> Show Next" affects the scoring system for all subsequent games, until the user enables "Settings -> Show Next" again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487728] Plasma panel/widgets freeze randomly with explicit sync, can be unfreezed by going into overview
https://bugs.kde.org/show_bug.cgi?id=487728 --- Comment #1 from kodatar...@yahoo.com --- Just wanted to make a note that I was able to test other compositors which do have explicit sync(gnome & gamescope) in their own separate session and neither exhibit any problems. This was the reason I opened a different thread from my previous one and more on what the issue is more correctly. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 487733] New: Make annotations compatible with other readers like Kobo Elipsa and Google Drive
https://bugs.kde.org/show_bug.cgi?id=487733 Bug ID: 487733 Summary: Make annotations compatible with other readers like Kobo Elipsa and Google Drive Classification: Applications Product: okular Version: 24.05.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: elia...@protonmail.ch Target Milestone: --- SUMMARY Currently it is possible to read annotations done on Kobo Elipsa in Okular. But the other way around is not true. Most annotations done in Okular are invisible to Kobo Elipsa. The only visible annotation is the free-line. Why not make other kinds of annotations (highlights, text additions) compatible as well? It would be very useful if they were. Or is it something that Kobo needs to implement? -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 485810] Videos played in a detached window
https://bugs.kde.org/show_bug.cgi?id=485810 --- Comment #4 from wheniwasatrues...@gmail.com --- (In reply to wheniwasatruestar from comment #2) > Same on my side too. > PlasmaTube version: 24.02.2 > > Operating System: Archlinux > KDE Plasma Version: 6.0.4 > KDE Framework Version: 6.2.0 > Qt Version: 6.7.0 > Kernel Version: 6.8.9-arch1-2 (64 bit) > Graphics Platform: Wayland > Processors: 12x AMD Ryzen 5 7640U w/ Radeon 760M Graphics > Memory: 14.9 GiB of Ram Still the same on 24.05.0 of PlasmaTube. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487728] New: Plasma panel/widgets freeze randomly with explicit sync, can be unfreezed by going into overview
https://bugs.kde.org/show_bug.cgi?id=487728 Bug ID: 487728 Summary: Plasma panel/widgets freeze randomly with explicit sync, can be unfreezed by going into overview Classification: Plasma Product: kwin Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kodatar...@yahoo.com Target Milestone: --- SUMMARY the plasma panel and widgets would randomly freeze when kwin has explicit sync patched in STEPS TO REPRODUCE 1. use kwin with explicit sync, panel & widgets would randomly freeze, open overview a few times to unfreeze OBSERVED RESULT panel & widgets - random freeze EXPECTED RESULT To continue working correctly SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-273-tkg-eevdf (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 Kwin patched with explicit sync from aur: https://aur.archlinux.org/packages/kwin-explicit-sync On a side note: this also affects 6.1 beta as well -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 283373] digiKam shows splashscreen but won't start with no crash report generated.
https://bugs.kde.org/show_bug.cgi?id=283373 caulier.gil...@gmail.com changed: What|Removed |Added Summary|digikam shows splashscreen, |digiKam shows splashscreen |but won't start - no crash |but won't start with no |report genereted|crash report generated. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 283373] digikam shows splashscreen, but won't start - no crash report genereted
https://bugs.kde.org/show_bug.cgi?id=283373 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466031] Per-virtual-desktop tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466031 kv3f5...@mailer.me changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466019 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466019] Allow saving tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466019 kv3f5...@mailer.me changed: What|Removed |Added CC||kv3f5...@mailer.me See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466031 --- Comment #6 from kv3f5...@mailer.me --- I think that implicitly saving the layout per activity / virtual desktop would be the way to go. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Per-screen virtual desktops
https://bugs.kde.org/show_bug.cgi?id=107302 kv3f5...@mailer.me changed: What|Removed |Added CC||kv3f5...@mailer.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466031] Per-virtual-desktop tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466031 kv3f5...@mailer.me changed: What|Removed |Added CC||kv3f5...@mailer.me --- Comment #8 from kv3f5...@mailer.me --- The tiling setup is also the same in all activities. We might want to differentiate tilings in those at least, as they represent a stronger division in general. -- You are receiving this mail because: You are watching all bug changes.
