[konsole] [Bug 476429] Right click on mouse freezes entire konsole application
https://bugs.kde.org/show_bug.cgi?id=476429 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from fanzhuyi...@gmail.com --- Hi, thank you for your bug report! The version against which you reported the bug is quite old and no longer supported. Could you verify if you could reproduce the bug on the latest version of the software? (konsole 23.08.2) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 476519] Keyboard shortcut for volume control changes the volume of the incorrect default audio output device when no open applications uses the audio system (obs, mpv, pavucontrol, et
https://bugs.kde.org/show_bug.cgi?id=476519 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||fanzhuyi...@gmail.com --- Comment #2 from fanzhuyi...@gmail.com --- Seems to be a duplicate of 456310. *** This bug has been marked as a duplicate of bug 456310 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 456310] Keyboard volume control keys don't change the volume of the default sink
https://bugs.kde.org/show_bug.cgi?id=456310 fanzhuyi...@gmail.com changed: What|Removed |Added CC||rakijaistheb...@abv.bg --- Comment #10 from fanzhuyi...@gmail.com --- *** Bug 476519 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476563] Lockscreen shows black screen without possibility to back to normal
https://bugs.kde.org/show_bug.cgi?id=476563 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- Hi, thank you for your bug report! Have you configured your system to automatically sleep/suspend instead of just locking? Sometimes computers have issues with waking up from suspend/sleep. Do you also encounter this issue when you manually lock the screen? Just select lock, don't select sleep or suspend. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 476560] Broken kate docs translation
https://bugs.kde.org/show_bug.cgi?id=476560 --- Comment #1 from Oliver Kellogg --- I have removed the kate subdirectory from svn+ssh://s...@svn.kde.org/home/kde/trunk/l10n-kf6/eo/docs until I can sort out the issues. This should be reflected to https://invent.kde.org/utilities/kate on the next scripty sync. Sorry for the inconvenience. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476554] a window will appear on all virtual desktops when showing desktop grid randomly
https://bugs.kde.org/show_bug.cgi?id=476554 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from fanzhuyi...@gmail.com --- Hi, thank you for your bug report! Are you on Wayland or X11? I can't seem to reproduce this issue on Wayland. I also noticed that in the screenshots, the mpv window seems to be fullscreen. Does this only happen for you on fullscreen apps? (I tried setting it full screen but I can't seem to reproduce the issue) Also, any other information that could help with reproducing the bug is greatly appreciated. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457910] Desktop grid arrow keys navigate between windows not desktops
https://bugs.kde.org/show_bug.cgi?id=457910 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476571] New: Creating Filter Layer based off current selection then changing its Blending mode will produce artifacts and weird behavior
https://bugs.kde.org/show_bug.cgi?id=476571 Bug ID: 476571 Summary: Creating Filter Layer based off current selection then changing its Blending mode will produce artifacts and weird behavior Classification: Applications Product: krita Version: 5.2.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: dorijan.sa...@gmail.com Target Milestone: --- Created attachment 162874 --> https://bugs.kde.org/attachment.cgi?id=162874=edit Results - Initial Filter Layer effect vs Changing blending mode vs Workaround SUMMARY Not certain if this is a bug or a limited functionality of how Filter Layer's transparency (alpha) works in Krita but the results are weird and could be caused by a bug. If Filter Layer is added while having an active selection (in order to affect only selected area) then changing its Blending Mode (for example from default Copy to Overlay) creates box artifact around affected area and further if turning visibility of affected layers (layers below the added filter layer) the effect spreads to entire affected layers. STEPS TO REPRODUCE 1. Create Paint Layer and draw something (rectangle for example) with any color except pure white or black (as the result may not be visible based on used blend mode) 2. Create a selection selecting a portion of added pixels on paint layer (portion of the rectangle) 3. Add Filter Layer (Gradient Map, HSV adjustment or literally any filter) 4. Change Filter Layer Blending Mode from default Copy to Overlay or something (some may have a visible issue based on colors used) OBSERVED RESULT After Changing the Blending Mode of created Filter Layer, the alpha(?) of that Filter Layer (not entire added filter effect) will spread around initially affected selection in a box shape and further turning visibility of affected Layer/layers below will spread the effect to entire affected layer (the rectangle from example). EXPECTED RESULT After Changing the Blending Mode of created Filter Layer, only Blending Mode within initially affected Selection should change. SOFTWARE/OS VERSIONS Windows: Windows 10 Pro, Version 2009 KDE Plasma Version: nowhere to be found within Krita Help > About KDE KDE Frameworks Version: same as above Qt Version: 5.15.7 ADDITIONAL INFORMATION Currently Installed Krita version 5.2.1 but the issue seems to go further back (tried 5.0 up to 5.2.1 and had same results). Used RGB/Alpha 8-bit Color Space, but results are the same in other Models/Depths too. WORKAROUND Only way I could find where alpha of Filter Layer doesn't partially bleed past selection is to Add Transparency Mask based on said selection to the Filter Layer after changing blending mode. This produces close to desired result where changing blending mode will stick to selection (currently transparency mask). However if the transparency mask is added before changing from copy to another Blend will again reproduce only partial bleed where in order to get full change I have to turn visibility of affected layer off/on, same if I go back to copy from any other blending mode. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476559] لا يمكن استخدام الكيبورد و الموس جميع في أن واد
https://bugs.kde.org/show_bug.cgi?id=476559 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Halla Rempt --- Please report bugs in English. Also, read https://docs.krita.org/en/untranslatable_pages/reporting_bugs.html to learn how to make useful bug reports. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476570] New: Bad frametime with Nvidia 545.29.02 on X11
https://bugs.kde.org/show_bug.cgi?id=476570 Bug ID: 476570 Summary: Bad frametime with Nvidia 545.29.02 on X11 Classification: Plasma Product: kwin Version: 5.27.9 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: duncanyo...@gmail.com Target Milestone: --- SUMMARY Since updating to 545.29.03 kwin seems to have bad frametimes, making everything seem stuttery or laggy. There are moments where it will be smooth, but then it goes right back to stuttering. *** 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. Use Nvidia card with 545.29.02 2. Watch any kwin animation or move a window, etc. OBSERVED RESULT Stutter/lag EXPECTED RESULT Smooth animations SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.9 (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 6.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION X11 Not my thread, but I don't appear to be the only one encountering this issue. https://www.reddit.com/r/archlinux/comments/17nrbcg/everything_is_stuttery_after_the_last_upgrade_on/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475261] when i used dock(comic manager) and create a new page, krita crashed.
https://bugs.kde.org/show_bug.cgi?id=475261 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475930] brush doesn't change after resizing
https://bugs.kde.org/show_bug.cgi?id=475930 --- 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 475019] Wayland / dual monitor: sometimes wallpaper and right clickable area minimizes on bigger screen
https://bugs.kde.org/show_bug.cgi?id=475019 --- Comment #10 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 476569] New: kwin gles backend not working with ANGLE
https://bugs.kde.org/show_bug.cgi?id=476569 Bug ID: 476569 Summary: kwin gles backend not working with ANGLE Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: egl Assignee: kwin-bugs-n...@kde.org Reporter: kde-y...@qq.com Target Milestone: --- I'm trying to run kwin using ANGLE. It provides libEGL that only supports gles. Compositing does not work. Please workaround it. ``` user@archlinux-114514 ~> export KWIN_COMPOSE=O2ES user@archlinux-114514 ~> export QT_XCB_GL_INTEGRATION=xcb_egl user@archlinux-114514 ~> export KWIN_OPENGL_INTERFACE=egl user@archlinux-114514 ~> export LD_PRELOAD=/home/user/src/angle/out/Release/libEGL.so user@archlinux-114514 ~> glmark2-es2 === glmark2 2023.01 === OpenGL Information GL_VENDOR: Google Inc. (AMD) GL_RENDERER:ANGLE (AMD, Vulkan 1.3.246 (AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO) (0x164E)), radv-23.1.6) GL_VERSION: OpenGL ES 3.1.0 (ANGLE 2.1.1 git hash: 75c0b859a0ab) Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0 Surface Size: 800x600 windowed === [build] use-vbo=false: FPS: 10585 FrameTime: 0.094 ms === glmark2 Score: 10584 === user@archlinux-114514 ~> kwin_x11 --replace Cannot find EGLConfig, returning null config Cannot find EGLConfig, returning null config kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker" kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate" kwin_scene_opengl: eglInitialize failed kwin_scene_opengl: Error during eglInitialize 12296 kwin_core: choose config failed kwin_core: Creating egl surface failed kwin_scene_opengl: Creating the OpenGL rendering failed: "Could not initialize rendering context" ``` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 403636] Media Pause button doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=403636 Logan Turner changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 476568] Play/Pause, Previous or Next Track buttons don't work
https://bugs.kde.org/show_bug.cgi?id=476568 Logan Turner changed: What|Removed |Added Version|unspecified |5.111.0 Assignee|unassigned-b...@kde.org |kdelibs-b...@kde.org Component|general |general Product|kde |frameworks-kglobalaccel -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476568] New: Play/Pause, Previous or Next Track buttons don't work
https://bugs.kde.org/show_bug.cgi?id=476568 Bug ID: 476568 Summary: Play/Pause, Previous or Next Track buttons don't work Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: loganturner...@gmail.com Target Milestone: --- Created attachment 162873 --> https://bugs.kde.org/attachment.cgi?id=162873=edit The screenshot here shows multiple entries for the same buttons. The media keys bug (https://bugs.kde.org/show_bug.cgi?id=403636) has seemingly reappeared in the latest KDE Plasma release. Upon login, media keys are detected and funtion normally. However, after closing the app and reopening it or another media player, the keys stop responding. I have tested this with both my Keychron K2 V2 keyboard and JBL T660NC headphones. For some reason, there are multiple entries for playing and pausing media. Changing these shortcuts does not affect the bug as it persists regardless. These keys were fully functional in the previous version. System info: OS: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Locale: en_NZ.UTF-8 Kernel: 6.5.8-zen1-1-zen CPU: Intel Core i5-1135G7 (4C 8T) GPU: Intel Iris Xe (80 exe. units) Memory: 16GB 3200MHz DDR4 SODIMM (2x 8GB) System: HP ProBook 430 G8 (567F3PA) STEPS TO REPRODUCE 1. Open media app and play media 2. Press the Play/Pause, Previous or Next Track buttons 3. Check if the media player reacts. Retry using the software UI. OBSERVED RESULT Media playback can be controlled using the software GUI, but not using the media keys (I have checked that FN lock is disabled, and the other system keys work as normal. EXPECTED RESULT The physical media keys control media playback properly, as they did in 5.27.8. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 476567] Moving the mouse within the screen lock grace period breaks the locker in some cases
https://bugs.kde.org/show_bug.cgi?id=476567 Prajna Sariputra changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 476567] New: Moving the mouse within the screen lock grace period breaks the locker in some cases
https://bugs.kde.org/show_bug.cgi?id=476567 Bug ID: 476567 Summary: Moving the mouse within the screen lock grace period breaks the locker in some cases Classification: Plasma Product: kscreenlocker Version: git-master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: putr...@gmail.com Target Milestone: --- SUMMARY With a Plasma 6 session compiled using kdesrc-build, if the screen locks automatically but I move the mouse within the "Allow unlocking within password" time period the screen will either freeze after unlocking or just go black, and when that happens I have to use the `loginctl unlock-session` command from another TTY. So far it appears that the screen locker only does that after I've locked the session manually and/or I've suspended the system at least once, the problem doesn't occur on a fresh reboot. The problem also doesn't occur if I move the mouse after the grace period, and disabling that grace period completely also works around the problem. STEPS TO REPRODUCE 1. Set up the system to lock automatically after 1 minute and allow unlocking without a password for 10 seconds (optional for easier testing) 2. Wait until the screen locks automatically 3. Move the mouse within 10 seconds (or under whatever time is set for the unlock without password setting) OBSERVED RESULT The screen is not properly unlocked, and the session is inaccessible without using the `loginctl unlock-session` command. EXPECTED RESULT The screen should unlock without asking for a password. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Kernel Version: 6.5.9-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION kscreenlocker is at commit 6777145016231427cccb4721de1e469a1512715c when I compiled it. The logs look the same as a manual unlock, except for the authentication failure message from bug 465266. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476566] Wine drag & drop coordinates off with Wayland fractional scaling
https://bugs.kde.org/show_bug.cgi?id=476566 David Warner changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476566] New: Wine drag & drop coordinates off with Wayland fractional scaling
https://bugs.kde.org/show_bug.cgi?id=476566 Bug ID: 476566 Summary: Wine drag & drop coordinates off with Wayland fractional scaling Classification: Plasma Product: kwin Version: 5.27.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: david.p.war...@gmail.com Target Milestone: --- Created attachment 162872 --> https://bugs.kde.org/attachment.cgi?id=162872=edit foobar2000 screenshot SUMMARY Drag & drop coordinates in Wine apps are wrong when Wayland fractional scaling is enabled. STEPS TO REPRODUCE 1. Set monitor to 150% scaling (Wayland session). 2. Install foobar2000, select Album List + Properties layout. 3. Drag file(s) from Dolphin to foobar2000 playlist area. OBSERVED RESULT The drop target area is off by a factor of 1.5. For example, if the playlist area top left corner is positioned at (640,360), the mouse needs to be moved to (960,540) for the drop reticle to appear. EXPECTED RESULT The mouse coordinates should match the drop target coordinates. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Wine DPI scaling doesn't make seem to make a difference (configured via winecfg). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471639] Transition to night color starts way too early in "Current Location" mode
https://bugs.kde.org/show_bug.cgi?id=471639 --- Comment #10 from Sanjay Swain --- Also probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=469730 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471639] Transition to night color starts way too early in "Current Location" mode
https://bugs.kde.org/show_bug.cgi?id=471639
Sanjay Swain changed:
What|Removed |Added
CC||sanjayswain...@gmail.com
--- Comment #9 from Sanjay Swain ---
(In reply to Ivan Garcia from comment #8)
> (In reply to Ivan Garcia from comment #6)
> > (In reply to Nate Graham from comment #4)
> > > The geolocator should print the location it calculated. Can you verify
> > > that
> > > it's correct?
> >
> > It calculates the location correctly. It also shows the times where it is
> > going to change color accurately as well. The issue is that it does not
> > honor the settings. As everyone stated here, if you set it to "manual" night
> > light works as expected.
>
> It does not show on the screenshot but night color is active (4500k) even
> though it was only 5:01PMEST
Is it still a issue? And if it is please can you send the output of following
commands:
> qdbus org.kde.KWin /ColorCorrect GetAll org.kde.kwin.ColorCorrect
and
> qdbus org.kde.KWin /ColorCorrect GetAll org.kde.kwin.ColorCorrect | awk
> '/Time/ {print $1, strftime("%T", $2)
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 471238] Night Color Constantly on
https://bugs.kde.org/show_bug.cgi?id=471238
Sanjay changed:
What|Removed |Added
CC||sanjayswain...@gmail.com
--- Comment #4 from Sanjay ---
(In reply to David Wu from comment #3)
> I just noticed today that Night Light was turned off in the morning.
> However, it got turned back on at around 14:50.
>
> I'm thinking the locale is being mixed up with another location besides
> Toronto (which is what is being set, see the image above)
Is it still a issue? And if it is please can you send the output of following
commands:
> qdbus org.kde.KWin /ColorCorrect GetAll org.kde.kwin.ColorCorrect
and
> qdbus org.kde.KWin /ColorCorrect GetAll org.kde.kwin.ColorCorrect | awk
> '/Time/ {print $1, strftime("%T", $2)}'
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 476565] Can't disable the popup menu when switching the tab list (Ctrl+Tab)
https://bugs.kde.org/show_bug.cgi?id=476565 --- Comment #1 from moni...@tutanota.com --- Created attachment 162871 --> https://bugs.kde.org/attachment.cgi?id=162871=edit Screenshot from Notepad++ -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476565] New: Can't disable the popup menu when switching the tab list (Ctrl+Tab)
https://bugs.kde.org/show_bug.cgi?id=476565 Bug ID: 476565 Summary: Can't disable the popup menu when switching the tab list (Ctrl+Tab) Classification: Applications Product: kate Version: 23.08.1 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: moni...@tutanota.com Target Milestone: --- Created attachment 162870 --> https://bugs.kde.org/attachment.cgi?id=162870=edit Screenshot from Kate So that the switching is like in browsers. For example, Notepad++ has an option, but I can’t find a similar setting in Kate. I removed the hotkeys from «Settings» → «Configure Keyboard Shortcuts» → «tabswitcher» → «Last Used Views» and set «Ctrl+Tab» and «Ctrl+Shift+Tab» to «Kate» → «Next Tab» and «Previous Tabю». But the only problem that remains is that when you press «Ctrl+Tab» on the last open tab, it does not jump to the first initial tab (you cannot press only «Ctrl+Tab» to switch to all tabs in a circle), you have to press «Ctrl+Shift+Tab» to return to previous tabs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476547] List header in system tray config dialog is misplaced or not aligned with tray items
https://bugs.kde.org/show_bug.cgi?id=476547 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/3476 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 kimibl...@icloud.com changed: What|Removed |Added CC||kimibl...@icloud.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476564] Black square after very first open of combobox
https://bugs.kde.org/show_bug.cgi?id=476564 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com Keywords||qt6, wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476564] New: Black square after very first open of combobox
https://bugs.kde.org/show_bug.cgi?id=476564 Bug ID: 476564 Summary: Black square after very first open of combobox Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY After very first open of ComboBox in any KDE application I get black square. After open it again all is normal and I can see the list of entries. I tested this in System Settings. STEPS TO REPRODUCE 1. open System Settings 2. go to Screen Locking 3. click Configure 4. click combobox at "Wallpaper type" OBSERVED RESULT black square below "Image" EXPECTED RESULT list of entries SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240 Qt Version: 6.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476554] a window will appear on all virtual desktops when showing desktop grid randomly
https://bugs.kde.org/show_bug.cgi?id=476554 jmestreracl...@gmail.com changed: What|Removed |Added Summary|a window will appear all|a window will appear on all |virtual desktops when |virtual desktops when |showing desktop grid|showing desktop grid |randomly|randomly -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448078] Global Menu does not work in Qt6
https://bugs.kde.org/show_bug.cgi?id=448078 kimibl...@icloud.com changed: What|Removed |Added CC||kimibl...@icloud.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476563] New: Lockscreen shows black screen without possibility to back to normal
https://bugs.kde.org/show_bug.cgi?id=476563 Bug ID: 476563 Summary: Lockscreen shows black screen without possibility to back to normal Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Since couple days I experience very annoying issue, shortly described below. Lockscreen (triggered after N minutes of inactivity) shows black screen and I cannot back to normal / unlock the screen. At least I don't know how to back to normal and don't know any workaround. I can see black screen and can move mouse cursor. BTW. Alt+F2 doesn't work. My solution is only restart of PC, which is very annoying. My settings are as following: Lock screen automatically After: 5 minutes Allow unlocking without password: 5 seconds STEPS TO REPRODUCE 1. Login to plasma 2. Do nothing couple minutes 3. After lock screen is involving immediately move the mouse OBSERVED RESULT Black screen with mouse cursor EXPECTED RESULT Back to normal screen, because the try of unlocking happened before 5 sec. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240 Qt Version: 6.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476563] Lockscreen shows black screen without possibility to back to normal
https://bugs.kde.org/show_bug.cgi?id=476563 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com Keywords||qt6, wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433284] Shortcut for switching input method (Windows + Space) does not work when using kimpanel-ibus-panel
https://bugs.kde.org/show_bug.cgi?id=433284 David Warner changed: What|Removed |Added CC||david.p.war...@gmail.com --- Comment #16 from David Warner --- IBus 1.5.29 better integrates with Wayland, and the Super+Space shortcut works now in Wayland apps, though not XWayland apps. https://bugzilla.redhat.com/show_bug.cgi?id=2076596 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476561] KPhotoAlbum crashes when changes in Annotation window are not saved and then user right clicks "Show" in Viewer window
https://bugs.kde.org/show_bug.cgi?id=476561 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 --- Comment #7 from Andreas Schleth --- Created attachment 162869 --> https://bugs.kde.org/attachment.cgi?id=162869=edit KPA with German UI and some custom categories (Tokens are the "A+" icon) I think the very last commit did not work out as intended (?): As far as I understand (I may be wrong), the categories in the main window should have been sorted in a consistent way: Categories first and then the other items - preferably always in the same order Notice the different positions of "Folder/Ordner" and "Tokens/Kürzel" in the two screenshots of the same DB with different LANG settings. KPA-Version: v5.11.0-166-g7c4b2886 Does this go back to the time when the default category names were translated? Most other of my databases have the term "Tokens" instead of "Kürzel" irrespective of LANG setting. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 --- Comment #6 from Andreas Schleth --- Created attachment 162868 --> https://bugs.kde.org/attachment.cgi?id=162868=edit KPA with English UI and some custom categories (Tokens are the "A+" icon) -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 411184] QCA: Channel binding support
https://bugs.kde.org/show_bug.cgi?id=411184 --- Comment #2 from Neustradamus --- I have done a ticket for RFC 9266: Channel Bindings for TLS 1.3: - https://bugs.kde.org/show_bug.cgi?id=476562 I think that you have seen the jabber.ru MITM: - https://notes.valdikss.org.ru/jabber.ru-mitm/ - https://snikket.org/blog/on-the-jabber-ru-mitm/ - https://www.devever.net/~hl/xmpp-incident - https://blog.jmp.chat/b/certwatch -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 476562] New: RFC 9266: Channel Bindings for TLS 1.3
https://bugs.kde.org/show_bug.cgi?id=476562 Bug ID: 476562 Summary: RFC 9266: Channel Bindings for TLS 1.3 Classification: Frameworks and Libraries Product: qca Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: neustrada...@hotmail.com CC: aa...@kde.org, br...@frogmouth.net, jus...@karneges.com Target Milestone: --- Can you add the support of RFC 9266: Channel Bindings for TLS 1.3? - https://datatracker.ietf.org/doc/html/rfc9266 Little details, to know easily: - tls-unique for TLS =< 1.2 - tls-server-end-point - tls-exporter for TLS = 1.3 I think that you have seen the jabber.ru MITM: - https://notes.valdikss.org.ru/jabber.ru-mitm/ - https://snikket.org/blog/on-the-jabber-ru-mitm/ - https://www.devever.net/~hl/xmpp-incident - https://blog.jmp.chat/b/certwatch Thanks in advance. Linked to: - https://bugs.kde.org/show_bug.cgi?id=411184 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476131] KPhotoAlbum crashes after using Toggle full-screen preview, deleting image, resizing annotations window and then using Toggle full-screen preview again
https://bugs.kde.org/show_bug.cgi?id=476131 Victor Lobo changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #2 from Victor Lobo --- Thank you! The fix works. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476561] New: KPhotoAlbum crashes when changes in Annotation window are not saved and then user right clicks "Show" in Viewer window
https://bugs.kde.org/show_bug.cgi?id=476561 Bug ID: 476561 Summary: KPhotoAlbum crashes when changes in Annotation window are not saved and then user right clicks "Show" in Viewer window Classification: Applications Product: kphotoalbum Version: 5.11.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Annotation Dialog Assignee: kpab...@willden.org Reporter: victor.ip.l...@gmail.com Target Milestone: --- SUMMARY KPhotoAlbum crashes when changes in Annotation window are not saved and then user right clicks "Show" in Viewer window STEPS TO REPRODUCE 1. Open KPhotoAlbum 2. Go to Thumbnail View 3. Open an Image/Video in Viewer window 4. Open Annotations window (Ctrl + 1) 5. Make some changes in Annotations window (but do cancel or save; keep the Annotations window open) 6. Go to open Viewer window and go to "Show" in right click context menu 7. Click Cancel or Discard in the "Discard Changes?"dialog box that comes up 8. Crash OBSERVED RESULT Crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Linux: openSUSE Tumbleweed 20230906; Kernel Version: 6.4.12-1-default (64-bit) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 KPhotoAlbum Version 5.11.0 (as installed from Opensuse Tumbleweed repository) Also occurs in latest git version v5.11.0-166-g7c4b2886 ADDITIONAL INFORMATION 1. Crash is reproducible every time the steps are followed. 2. Crash occurs even in the demo database. 3. Crash occurs for Images and Videos. Backtrace: Application: KPhotoAlbum (kphotoalbum), signal: Segmentation fault [KCrash Handler] #4 QMenuSloppyState::setSubMenuPopup (this=0x21ecb80, actionRect=..., resetAction=, subMenu=0x0) at widgets/qmenu.h:65 #5 0x7fc1b2d2bdb0 in QMenu::internalDelayedPopup (this=0x24edfa0) at widgets/qmenu.cpp:3676 #6 0x7fc1b1f1922b in QObject::event (this=0x24edfa0, e=0x7ffd33130830) at kernel/qobject.cpp:1369 #7 0x7fc1b2ba519e in QApplicationPrivate::notify_helper (this=, receiver=0x24edfa0, e=0x7ffd33130830) at kernel/qapplication.cpp:3640 #8 0x7fc1b1eed568 in QCoreApplication::notifyInternal2 (receiver=0x24edfa0, event=0x7ffd33130830) at kernel/qcoreapplication.cpp:1064 #9 0x7fc1b1eed72e in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #10 0x7fc1b1f45899 in QTimerInfoList::activateTimers (this=0x1b32030) at kernel/qtimerinfo_unix.cpp:643 #11 0x7fc1b1f46144 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #12 0x7fc1ae524ef0 in ?? () from /lib64/libglib-2.0.so.0 #13 0x7fc1ae526b18 in ?? () from /lib64/libglib-2.0.so.0 #14 0x7fc1ae5271cc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #15 0x7fc1b1f464a6 in QEventDispatcherGlib::processEvents (this=0x1b33940, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #16 0x7fc1b1eebffb in QEventLoop::exec (this=this@entry=0x7ffd33130a80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #17 0x7fc1b2d2b70f in QMenuPrivate::exec(QPoint const&, QAction*, std::function) (this=0x21ec920, p=..., action=0x0, positionFunction=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #18 0x7fc1b2d2b82f in QMenu::exec (this=, p=..., action=) at widgets/qmenu.cpp:2686 #19 0x004d7c81 in Viewer::ViewerWidget::contextMenuEvent (this=0x20ccee0, e=0x7ffd33130d20) at /home/victor/kphotoalbum/Viewer/ViewerWidget.cpp:561 #20 0x7fc1b2be6d68 in QWidget::event (this=this@entry=0x20ccee0, event=event@entry=0x7ffd33130d20) at kernel/qwidget.cpp:9045 #21 0x7fc1b2c91f7e in QFrame::event (this=0x20ccee0, e=0x7ffd33130d20) at widgets/qframe.cpp:550 #22 0x7fc1b2ba519e in QApplicationPrivate::notify_helper (this=this@entry=0x1a591e0, receiver=receiver@entry=0x20ccee0, e=e@entry=0x7ffd33130d20) at kernel/qapplication.cpp:3640 #23 0x7fc1b2badaaa in QApplication::notify (this=, receiver=, e=0x7ffd33130f50) at kernel/qapplication.cpp:3246 #24 0x7fc1b1eed568 in QCoreApplication::notifyInternal2 (receiver=0x21ed160, event=0x7ffd33130f50) at kernel/qcoreapplication.cpp:1064 #25 0x7fc1b1eed5b2 in QCoreApplication::forwardEvent (receiver=, event=, originatingEvent=) at kernel/qcoreapplication.cpp:1079 #26 0x7fc1b2bfff59 in QWidgetWindow::handleMouseEvent (this=this@entry=0x2528a70, event=event@entry=0x7ffd33131240) at kernel/qwidgetwindow.cpp:692 #27 0x7fc1b2c02d1f in QWidgetWindow::event (this=0x2528a70, event=0x7ffd33131240) at kernel/qwidgetwindow.cpp:300 #28 0x7fc1b2ba519e in QApplicationPrivate::notify_helper (this=, receiver=0x2528a70, e=0x7ffd33131240) at kernel/qapplication.cpp:3640 #29 0x7fc1b1eed568 in QCoreApplication::notifyInternal2 (receiver=0x2528a70, event=0x7ffd33131240) at kernel/qcoreapplication.cpp:1064 #30
[i18n] [Bug 476560] Broken kate docs translation
https://bugs.kde.org/show_bug.cgi?id=476560 Oliver Kellogg changed: What|Removed |Added Assignee|kde-i18n...@kde.org |okellogg@users.sourceforge. ||net -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 476560] Broken kate docs translation
https://bugs.kde.org/show_bug.cgi?id=476560 Oliver Kellogg changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476436] German umlaute are not shown in textfields in this PDF document
https://bugs.kde.org/show_bug.cgi?id=476436 steffen-wink...@posteo.de changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from steffen-wink...@posteo.de --- After updating today - Okular is now 23.08.2 - it is working as expected now. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 --- Comment #5 from Johannes Zarl-Zierl --- Git commit 7c4b288689dfcb4a1aaba556f8eea211eb0f1380 by Johannes Zarl-Zierl. Committed on 05/11/2023 at 00:16. Pushed by johanneszarl into branch 'master'. Fix sort order on overview page. Similar to bug #476504, with natural sort order, non-category items on the browser overview page, like "Show Thumbnails" and others, would be sorted alongside category items. These entries should be sorted after categories. Expanding on the ideal laid out in 7452e018361908b6f6b6146a8dd8de75461346ce, use a SortPriorityRole to sort these entries in a stable and (hopefully) intuitive way: 1. Categories 2. search, geo position and exiv info (sorted according to localized name) 3. Untagged images 4. "Show Thumbnails" M +7-2Browser/AbstractCategoryModel.cpp M +22 -5Browser/OverviewPage.cpp M +5-5Browser/TreeFilter.cpp M +1-2Browser/enums.h https://invent.kde.org/graphics/kphotoalbum/-/commit/7c4b288689dfcb4a1aaba556f8eea211eb0f1380 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476364] Incorrectly styled font selector
https://bugs.kde.org/show_bug.cgi?id=476364 Nicolas Fella changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-integration/-/com ||mit/53cfae46b00f7844718bb75 ||c469cfcf6efcb070d Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #5 from Nicolas Fella --- Git commit 53cfae46b00f7844718bb75c469cfcf6efcb070d by Nicolas Fella. Committed on 04/11/2023 at 23:19. Pushed by nicolasfella into branch 'master'. Implement Font dialogs QML FontDialog first queries the platform theme for an implementation. Since we don't provide one we get the default one, which is less than stellar. In Qt5 we would get a widgets-based one that works fine. We can get the Qt5 behavior back by asking for a QFontDialog (and passing DontUseNativeDialog to avoid endless recursion) M +1-0qt6/autotests/CMakeLists.txt M +1-0qt6/src/platformtheme/CMakeLists.txt A +64 -0qt6/src/platformtheme/kdeplatformfontdialoghelper.cpp [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.0)] A +32 -0qt6/src/platformtheme/kdeplatformfontdialoghelper.h [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.0)] M +3-1qt6/src/platformtheme/kdeplatformtheme.cpp https://invent.kde.org/plasma/plasma-integration/-/commit/53cfae46b00f7844718bb75c469cfcf6efcb070d -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 476560] Broken kate docs translation
https://bugs.kde.org/show_bug.cgi?id=476560 Nicolas Fella changed: What|Removed |Added CC||okellogg@users.sourceforge. ||net -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 476560] New: Broken kate docs translation
https://bugs.kde.org/show_bug.cgi?id=476560 Bug ID: 476560 Summary: Broken kate docs translation Classification: Translations Product: i18n Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: eo Assignee: kde-i18n...@kde.org Reporter: nicolas.fe...@gmx.de Target Milestone: --- Building Kate fails with [11/382] Generating po/eo/docs/kate/index.cache.bz2 FAILED: po/eo/docs/kate/index.cache.bz2 /home/nico/kde/build/kate/po/eo/docs/kate/index.cache.bz2 cd /home/nico/kde/src/kate && /home/nico/kde/usr/bin/meinproc6 --check --cache /home/nico/kde/build/kate/po/eo/docs/kate/index.cache.bz2 po/eo/docs/kate/index.docbook fundamentals.docbook:726: parser error : Entity 'Right' not defined >
[dolphin] [Bug 475659] Selection for ISO integration is missing in the Dolphin menu after the update
https://bugs.kde.org/show_bug.cgi?id=475659 Neros changed: What|Removed |Added CC||cont...@neros.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476535] Difference in allocation size for massif/tests/overloaded-new between clang++/libc++ and g++/libstdc++
https://bugs.kde.org/show_bug.cgi?id=476535 --- Comment #1 from Paul Floyd --- So I think what happens is that arena_malloc allocates requested size + alignment + overhead Then the small block up to the alignment boundary gets freed. Since the alignment was added to the arena_malloc size then even in the worst case there will be the original user requested size available. That means that "extra-heap" is made up of overhead and slop from rounding up the the alignment boundary. And from what I see the slop depends on what was allocated previously. Since libc++ and libstdc++ do different allocations the slop is different. Conclusion: I need to filter the extra-heap for these aligned allocations. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476556] Images vignettes are very low quality with PNG files
https://bugs.kde.org/show_bug.cgi?id=476556 --- Comment #3 from Maik Qualmann --- The digiKam-8.2.0 AppImage from https://files.kde.org/digikam/ fixes the problem for newly created images. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476556] Images vignettes are very low quality with PNG files
https://bugs.kde.org/show_bug.cgi?id=476556 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.2.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Maik Qualmann --- Fixed with Bug 472253. The issue only affects the low quality embedded preview image. If you set the preview to load to a full image, you'll at least see a decent image. However, the thumbnail is still affected. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 476479] baloo_file (baloo_file), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=476479 --- Comment #7 from David Kredba --- Both the mdb_copy and mdb_stat commands understand the index file structure and Baloo continues to index content of my files without complaining so I think its structure was not damaged by the crash. I will let it go. After it (maybe) will finish it I can run some searches to see if documents are found once only. Can I dump/export it to text file? There are a mdb_dump and mdb_load binaries. I will try. Are there sanity/health checks for the index file BTW? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476556] Images vignettes are very low quality with PNG files
https://bugs.kde.org/show_bug.cgi?id=476556 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The problem is fixed in digiKam-8.2.0, I'm looking for the corresponding bug entry. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447717] plasmashell crashes when hovering or clicking items on the Panel due to "zwp_linux_buffer_params_v1.add" protocol error
https://bugs.kde.org/show_bug.cgi?id=447717 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476556] Images vignettes are very low quality with PNG files
https://bugs.kde.org/show_bug.cgi?id=476556 caulier.gil...@gmail.com changed: What|Removed |Added Component|Albums-IconView |Thumbs-Engine OS|Other |Linux CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting happens at the wrong time during daylight savings time when using manual Date & Time setting
https://bugs.kde.org/show_bug.cgi?id=469730 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #36 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3474 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 Johannes Zarl-Zierl changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #4 from Johannes Zarl-Zierl --- Thanks for checking! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476559] New: لا يمكن استخدام الكيبورد و الموس جميع في أن واد
https://bugs.kde.org/show_bug.cgi?id=476559 Bug ID: 476559 Summary: لا يمكن استخدام الكيبورد و الموس جميع في أن واد Classification: Applications Product: krita Version: 5.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: oes...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. عندم اريد تغيير اسم الطبقة و الموس متصل بلبلوتوث لايمكن تغيير في جهاز تاب ميت 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.
[kwin] [Bug 476538] External monitor corrupted under Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=476538 --- Comment #5 from robg...@gmail.com --- Attached, thanks. It looks like the main difference is in Card 1 Plane 0's format modifier: Plasma has it set to DRM_FORMAT_MOD_LINEAR, while X has it set to NVIDIA_BLOCK_LINEAR_2D(h=4, k=254, g=0, s=1, c=0) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 476558] New: Crashes when pressing keyboard arrow button
https://bugs.kde.org/show_bug.cgi?id=476558 Bug ID: 476558 Summary: Crashes when pressing keyboard arrow button Classification: Applications Product: gwenview Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: agne.tallr...@protonmail.com Target Milestone: --- Application: gwenview (23.08.2) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.5.7-artix1-1 x86_64 Windowing System: X11 Distribution: Artix Linux DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: Wanted to display the next picture in current folder by pressing right arrow button. Obviously that is a bad idea for jpeg2000 images. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted [KCrash Handler] #4 0x7facbacac83c in () at /usr/lib/libc.so.6 #5 0x7facbac5c668 in raise () at /usr/lib/libc.so.6 #6 0x7facbac444b8 in abort () at /usr/lib/libc.so.6 #7 0x7facbac443dc in () at /usr/lib/libc.so.6 #8 0x7facbac54d26 in () at /usr/lib/libc.so.6 #9 0x7facb84ae13f in jas_init_library () at /usr/lib/libjasper.so.7 #10 0x7facac2566ce in () at /usr/lib/qt/plugins/imageformats/libqjp2.so #11 0x7facac257a83 in () at /usr/lib/qt/plugins/imageformats/libqjp2.so #12 0x7facbb9b951e in QImageReader::read(QImage*) () at /usr/lib/libQt5Gui.so.5 #13 0x7facbb9bb97a in QImageReader::read() () at /usr/lib/libQt5Gui.so.5 #14 0x7facbd83a7f1 in () at /usr/lib/libgwenviewlib.so.5 #15 0x7facbd833c04 in () at /usr/lib/libgwenviewlib.so.5 #16 0x7facbb2f84a1 in () at /usr/lib/libQt5Core.so.5 #17 0x7facbb2f36fa in () at /usr/lib/libQt5Core.so.5 #18 0x7facbacaa9eb in () at /usr/lib/libc.so.6 #19 0x7facbad2e7cc in () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7facacf436c0 (LWP 1201) "gwenview"): #1 0x7facb84986f9 in () at /usr/lib/libusbmuxd-2.0.so.6 #2 0x7facb84993cc in () at /usr/lib/libusbmuxd-2.0.so.6 #3 0x7facbacaa9eb in () at /usr/lib/libc.so.6 #4 0x7facbad2e7cc in () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7facad7546c0 (LWP 1197) "Gwenview::Thumb"): #1 0x7facbaca9d40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7facbb2fb484 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7facbd88ae36 in () at /usr/lib/libgwenviewlib.so.5 #4 0x7facbb2f36fa in () at /usr/lib/libQt5Core.so.5 #5 0x7facbacaa9eb in () at /usr/lib/libc.so.6 #6 0x7facbad2e7cc in () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7facadf556c0 (LWP 1187) "gwenview:sh2"): #1 0x7facbaca9d40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7faca45417f4 in () at /usr/lib/dri/iris_dri.so #3 0x7faca44c623a in () at /usr/lib/dri/iris_dri.so #4 0x7faca45416ba in () at /usr/lib/dri/iris_dri.so #5 0x7facbacaa9eb in () at /usr/lib/libc.so.6 #6 0x7facbad2e7cc in () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7facae7566c0 (LWP 1186) "gwenview:sh1"): #1 0x7facbaca9d40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7faca45417f4 in () at /usr/lib/dri/iris_dri.so #3 0x7faca44c623a in () at /usr/lib/dri/iris_dri.so #4 0x7faca45416ba in () at /usr/lib/dri/iris_dri.so #5 0x7facbacaa9eb in () at /usr/lib/libc.so.6 #6 0x7facbad2e7cc in () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7facaef576c0 (LWP 1185) "gwenview:sh0"): #1 0x7facbaca9d40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7faca45417f4 in () at /usr/lib/dri/iris_dri.so #3 0x7faca44c623a in () at /usr/lib/dri/iris_dri.so #4 0x7faca45416ba in () at /usr/lib/dri/iris_dri.so #5 0x7facbacaa9eb in () at /usr/lib/libc.so.6 #6 0x7facbad2e7cc in () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7facaf7586c0 (LWP 1184) "gwenvie:disk$0"): #1 0x7facbaca9d40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7faca45417f4 in () at /usr/lib/dri/iris_dri.so #3 0x7faca44c623a in () at /usr/lib/dri/iris_dri.so #4 0x7faca45416ba in () at /usr/lib/dri/iris_dri.so #5 0x7facbacaa9eb in () at /usr/lib/libc.so.6 #6 0x7facbad2e7cc in () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7facb54c96c0 (LWP 1182) "QDBusConnection"): #1 0x7facb94de276 in () at /usr/lib/libglib-2.0.so.0 #2 0x7facb947e162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7facbb4ea45c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7facbb49a354 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7facbb2f74d6 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7facbc797a9a in () at /usr/lib/libQt5DBus.so.5 #7 0x7facbb2f36fa in () at
[frameworks-knewstuff] [Bug 474949] Full store.kde.org description is cut off in the GHNS dialog's details page
https://bugs.kde.org/show_bug.cgi?id=474949 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/knewstuff/-/merge_requests/282 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473733] Dolphin unable to copy or move files "The file or folder Message recipient disconnected from message bus without replying does not exist."
https://bugs.kde.org/show_bug.cgi?id=473733 Graham Perrin changed: What|Removed |Added CC||grahamper...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 475825] Tokodon crash when clicking "Notifications" in sidebar
https://bugs.kde.org/show_bug.cgi?id=475825
--- Comment #7 from bru...@outlook.com ---
Here is the system log (journalctl -f) when Tokodon crashed on my machine.
Perhaps
you find something in here:
Nov 04 19:44:24 x plasmashell[2113]: 21 -- exe=/usr/bin/tokodon
Nov 04 19:44:24 x plasmashell[2113]: 17 -- platform=wayland
Nov 04 19:44:24 x plasmashell[2113]: 16 -- appname=tokodon
Nov 04 19:44:24 x plasmashell[2113]: 17 -- apppath=/usr/bin
Nov 04 19:44:24 x plasmashell[2113]: 10 -- signal=11
Nov 04 19:44:24 x plasmashell[2113]: 9 -- pid=2113
Nov 04 19:44:24 x plasmashell[2113]: 19 -- appversion=23.08.2
Nov 04 19:44:24 x plasmashell[2113]: 20 -- programname=Tokodon
Nov 04 19:44:24 x plasmashell[2113]: 71 --
bugaddress=https://bugs.kde.org/describecomponents.cgi?product=tokodon
Nov 04 19:44:24 x plasmashell[2113]: KCrash: crashing...
crashRecursionCounter = 2
Nov 04 19:44:24 x plasmashell[2113]: KCrash: Application Name = tokodon
path = /usr/bin pid = 2113
Nov 04 19:44:24 x plasmashell[2113]: KCrash: Arguments:
/usr/bin/tokodon
Nov 04 19:44:24 x plasmashell[2113]: KCrash: Attempting to start
/usr/lib/drkonqi
Nov 04 19:44:24 x kwin_wayland[988]: kf.service.services: The desktop
entry file "/usr/share/applications/qemu.desktop" has Type= "Application" but
has no Exec field.
Nov 04 19:44:24 x kwin_wayland[988]: kf.service.services: The desktop
entry file "/usr/share/applications/org.freedesktop.Xwayland.desktop" has Type=
"Application" but has no Exec field.
Nov 04 19:44:24 x kwin_wayland[988]: kf.service.services: The desktop
entry file "/usr/share/applications/bookmarks.desktop" has Type= "Application"
but has no Exec field.
Nov 04 19:44:24 x drkonqi[2387]: [QtOIIO] Plugin Initialized
Nov 04 19:44:24 x drkonqi[2387]: kf5idletime_wayland: This plugin does
not support polling idle time
Nov 04 19:44:24 x kded5[1103]: Registering ":1.84/StatusNotifierItem"
to system tray
Nov 04 19:44:24 x plasmashell[1138]: Could not find the Plasmoid for
Plasma::FrameSvgItem(0x55e4b10dd100) QQmlContext(0x55e4b19eb070)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Nov 04 19:44:24 x plasmashell[1138]: Could not find the Plasmoid for
Plasma::FrameSvgItem(0x55e4b10dd100) QQmlContext(0x55e4b19eb070)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Nov 04 19:44:24 x plasmashell[1138]: QFont::setPointSizeF: Point size
<= 0 (0.00), must be greater than 0
Nov 04 19:44:30 x kded5[1103]: Service ":1.74" unregistered
Nov 04 19:44:31 x plasmashell[2048]: Unable to start Dr. Konqi
Nov 04 19:44:31 x plasmashell[2048]: Re-raising signal for core dump
handling.
Nov 04 19:44:31 x systemd[1]: Created slice Slice
/system/systemd-coredump.
Nov 04 19:44:31 x systemd[1]: Started Process Core Dump (PID 2416/UID
0).
Nov 04 19:44:32 x systemd-coredump[2417]: [] Process 2048 (tokodon) of
user 1000 dumped core.
Stack trace of thread 2048:
#0 0x7f761deac83c n/a
(libc.so.6 + 0x8e83c)
#1 0x7f761de5c668 raise
(libc.so.6 + 0x3e668)
#2 0x7f761b17088f
_ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x788f)
#3 0x7f761de5c710 n/a
(libc.so.6 + 0x3e710)
#4 0x55809593297c n/a
(tokodon + 0x7897c)
#5 0x7f761e9bdd45 n/a
(libQt5QmlModels.so.5 + 0x3fd45)
#6 0x7f761e9b7cbb n/a
(libQt5QmlModels.so.5 + 0x39cbb)
#7 0x7f761e6b0adc
_ZNK13QMetaProperty4readEPK7QObject (libQt5Core.so.5 + 0x2b0adc)
#8 0x7f761e9c0fda n/a
(libQt5QmlModels.so.5 + 0x42fda)
#9 0x7f761e9c130b n/a
(libQt5QmlModels.so.5 + 0x4330b)
#10 0x7f7620250c0e
_ZN20QQmlIncubatorPrivate8incubateER26QQmlInstantiationInterrupt
(libQt5Qml.so.5 + 0x250c0e)
#11 0x7f7620251096
_ZN17QQmlEnginePrivate8incubateER13QQmlIncubatorP15QQmlContextData
(libQt5Qml.so.5 + 0x251096)
#12 0x7f761e9c69c2 n/a
(libQt5QmlModels.so.5 + 0x489c2)
#13 0x7f7620900259 n/a
(libQt5Quick.so.5 + 0x300259)
#14 0x7f762091648b n/a
(libQt5Quick.so.5 + 0x31648b)
[kwin] [Bug 476538] External monitor corrupted under Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=476538 --- Comment #4 from robg...@gmail.com --- Created attachment 162867 --> https://bugs.kde.org/attachment.cgi?id=162867=edit drm_info on Gnome Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476538] External monitor corrupted under Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=476538 --- Comment #3 from robg...@gmail.com --- Created attachment 162866 --> https://bugs.kde.org/attachment.cgi?id=162866=edit drm_info on Plasma X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476538] External monitor corrupted under Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=476538 --- Comment #2 from robg...@gmail.com --- Created attachment 162865 --> https://bugs.kde.org/attachment.cgi?id=162865=edit drm_info on Plasma Wayland -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 475667] cannot make new events in kalendar
https://bugs.kde.org/show_bug.cgi?id=475667 --- Comment #3 from goo --- final result of the akonadictl fsck 2>&1 | grep -iE 'found|no RID' command ``` Found 0 external files. Found 0 external parts. Found no unreferenced external files. Found 0 parts to be moved to external files Found 0 parts to be moved to database Collection "Search" (id: 1) has no RID. Collection "OpenInvitations" (id: 2) has no RID. Collection "DeclinedInvitations" (id: 3) has no RID. Found 3 collections without RID. Found 0 items without RID. Found 0 dirty items. ``` -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476557] No 'Show Menu Bar' option in rigt-click menu
https://bugs.kde.org/show_bug.cgi?id=476557 --- Comment #1 from a...@bolgarov.org --- Note that keyboard combination 'Ctrl-Shift-M still works: it shows or hides Konsole menu bar at the top of the window. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476556] Images vignettes are very low quality with PNG files
https://bugs.kde.org/show_bug.cgi?id=476556 philippe.quag...@laposte.net changed: What|Removed |Added Platform|Other |Appimage -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476557] New: No 'Show Menu Bar' option in rigt-click menu
https://bugs.kde.org/show_bug.cgi?id=476557 Bug ID: 476557 Summary: No 'Show Menu Bar' option in rigt-click menu Classification: Applications Product: konsole Version: 23.08.1 Platform: Kubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: a...@bolgarov.org Target Milestone: --- SUMMARY When you do right-click in console window, there opens a pop-up menu, but there is no 'Show Menu Bar' option. Even the KDE documentation explicitly says there should be a 'Show Menu Bar' option: https://docs.kde.org/stable5/en/konsole/konsole/commandreference.html#menubar STEPS TO REPRODUCE 1. Open konsole 2. Do a right-click OBSERVED RESULT Observe that there is no 'Show Menu Bar' option in a pop-up menu that opens. EXPECTED RESULT There should be a 'Show Menu Bar' option in a pop-up menu that opens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.10 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476556] New: Images vignettes are very low quality with PNG files
https://bugs.kde.org/show_bug.cgi?id=476556 Bug ID: 476556 Summary: Images vignettes are very low quality with PNG files Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Albums-IconView Assignee: digikam-bugs-n...@kde.org Reporter: philippe.quag...@laposte.net Target Milestone: --- Created attachment 162864 --> https://bugs.kde.org/attachment.cgi?id=162864=edit See exemple on the capture attached, with Tiff and PNG vignette, while original images are similar 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. Convert a high quality Tiff file to PNG using the batch conversion tool 2. Tiff and PNG images are visually similars 3. PNG vignettes are of very low quality, while TIFF vignettes are ok 4. Refreching the vignettes (F5) does not change anything OBSERVED RESULT 2. Tiff and PNG images are visually similars 3. PNG vignettes are of very low quality, while TIFF vignettes are ok EXPECTED RESULT Tiff and PNG images of similar good quality SOFTWARE/OS VERSIONS Ubuntu 23.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 475667] cannot make new events in kalendar
https://bugs.kde.org/show_bug.cgi?id=475667 goo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from goo --- with both backports and backport-extra enabled: uninstall, purge and autoremove used on kalendar, akonadi-server, kdepim-addons, and kdepim-runtime... then pruned my ~/.config of any mention of related settings and deleted my ~/.cache directory. restart install kalendar and kdepim-addons (kaddressbook comes along with it, and is unavoidable but the rest of the korganizer suite is not need). now i can call up kalendar from the clock widget and add events and can add my personal calendar to the clock widget using the PIM settings. Operating System: Kubuntu 22.04 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 Kernel Version: 6.2.0-36-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475973] Canvas-only mode not properly hiding menu bar
https://bugs.kde.org/show_bug.cgi?id=475973 --- Comment #1 from Alvin Wong --- Created attachment 162863 --> https://bugs.kde.org/attachment.cgi?id=162863=edit workspace to reproduce the bug I found that it only happens with this workspace active. This does not happen in both 5.2.0 and 5.2.1, so it is a regression on master. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476555] "Set destination" context menu option for bookmarks item
https://bugs.kde.org/show_bug.cgi?id=476555 Pussy Boots changed: What|Removed |Added Summary|Set bookmark destionation |"Set destination" context ||menu option for bookmarks ||item -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476555] "Set destination" context menu option for bookmarks items
https://bugs.kde.org/show_bug.cgi?id=476555 Pussy Boots changed: What|Removed |Added Summary|"Set destination" context |"Set destination" context |menu option for bookmarks |menu option for bookmarks |item|items -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476555] New: Set bookmark destionation
https://bugs.kde.org/show_bug.cgi?id=476555 Bug ID: 476555 Summary: Set bookmark destionation Classification: Applications Product: okular Version: 23.08.0 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: yuily...@gmail.com Target Milestone: --- Currently the context menu for a bookmark item allows only to: - Go to this Bookmark - Rename Bookmark - Delete Bookmark I propose a new item "Set Destination", which sets the destination of the selected bookmark to the current page. Use case: when I read a book, I use a bookmark to keep track of where I am within the book. Also useful to set the destination without removing the bookmark and creating a new one. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476548] valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold
https://bugs.kde.org/show_bug.cgi?id=476548 --- Comment #1 from Paul Floyd --- This changed fairly recently. If possible use Valgrind 3.21 while we look for a fix. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476548] valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold
https://bugs.kde.org/show_bug.cgi?id=476548 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 474742] kstars crashes (closes) immediately after starting ekos on remote computer.
https://bugs.kde.org/show_bug.cgi?id=474742 --- Comment #4 from jackb...@gmail.com --- My problem (comment 3) seems to be resolved by regenerating the dark files used for guiding. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476554] New: a window will appear all virtual desktops when showing desktop grid randomly
https://bugs.kde.org/show_bug.cgi?id=476554 Bug ID: 476554 Summary: a window will appear all virtual desktops when showing desktop grid randomly Classification: Plasma Product: kwin Version: 5.27.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: jmestreracl...@gmail.com Target Milestone: --- Created attachment 162862 --> https://bugs.kde.org/attachment.cgi?id=162862=edit occurence of the bug/issue SUMMARY Randomly, a window will appear on every virtual desktop when showing desktop grid. STEPS TO REPRODUCE 1. Create at least four (four is my setup) virtual desktops. 2. Open at least two apps. Put each window on separate virtual desktops. 3. Just keep toggling the desktop grid. OBSERVED RESULT One window (the active window?) will appear on every desktop. EXPECTED RESULT Each window should only appear on the virtual desktop they were placed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION I'm not sure how to reproduce it, it just happens randomly. It happened to me four times already. It's not been so long since I started using desktop grid. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Alex Noyle changed: What|Removed |Added CC||alexno...@icloud.com --- Comment #35 from Alex Noyle --- I am also still not seeing GTK global menus on wayland. They appear on the applications themselves, wasting a lot of space. OS: Void Linux KDE: 5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 476508] [kdesrc-build Plasma 6] Screen locker doesn't show the password entry prompt
https://bugs.kde.org/show_bug.cgi?id=476508 --- Comment #4 from duha.b...@gmail.com --- Didn't work for me, neither did the other method. But i think this is likely an issue with my setup up, maybe I have screwed up the pam files. So if you want you can close this bug and I will reopen once I am certain it is not an issue on my end (unlikely). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476553] New: RPM build of Valgrind 3.22.0 fails under RHEL8
https://bugs.kde.org/show_bug.cgi?id=476553 Bug ID: 476553 Summary: RPM build of Valgrind 3.22.0 fails under RHEL8 Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: peter.klot...@gmail.com Target Milestone: --- SUMMARY Building an RPM of Valgrind 3.22.0 does not work under Red Hat Enterprise Linux 8 STEPS TO REPRODUCE 1. Execute "rpmbuild -tb valgrind-3.22.0.tar.bz2" on a fully patched RHEL 8.8 system 2. One obtains the error messages below OBSERVED RESULT The error messages: --- /usr/bin/mkdir -p '/usr/libexec/valgrind' /usr/bin/install -c -m 644 m_gdbserver/valgrind-monitor.py m_gdbserver/valgrind-monitor-def.py '/usr/libexec/valgrind' /usr/bin/install: cannot create regular file '/usr/libexec/valgrind/valgrind-monitor.py': Permission denied /usr/bin/install: cannot create regular file '/usr/libexec/valgrind/valgrind-monitor-def.py': Permission denied make[4]: *** [Makefile:9424: install-gdbscriptsDATA] Error 1 make[4]: Leaving directory '/home/user/rpmbuild/BUILD/valgrind-3.22.0/coregrind' make[3]: *** [Makefile:9565: install-am] Error 2 make[3]: Leaving directory '/home/user/rpmbuild/BUILD/valgrind-3.22.0/coregrind' make[2]: *** [Makefile:9558: install] Error 2 make[2]: Leaving directory '/home/user/rpmbuild/BUILD/valgrind-3.22.0/coregrind' make[1]: *** [Makefile:918: install-recursive] Error 1 make[1]: Leaving directory '/home/user/rpmbuild/BUILD/valgrind-3.22.0' make: *** [Makefile:1225: install] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.Jax4dz (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.Jax4dz (%install) --- EXPECTED RESULT It should build, like 3.21.0 did. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org --- Comment #5 from Christoph Cullmann --- I don't see that we workaround that in all applications. Either it is worked around in Qt or the other people must fix that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476462] Plasma crashes unexpectedly when I click on the close button in the notification
https://bugs.kde.org/show_bug.cgi?id=476462 --- Comment #2 from curtis.c...@yandex.ru --- Created attachment 162861 --> https://bugs.kde.org/attachment.cgi?id=162861=edit New crash information added by DrKonqi plasmashell (5.27.9) using Qt 5.15.11 Plasma crashed, when PackageKit Updater notification closed via button on popup -- Backtrace (Reduced): #5 0x7f4ca4a943ed in QtQml::qmlExecuteDeferred(QObject*) () at /lib64/libQt5Qml.so.5 #6 0x7f4ca4f78e99 in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) () at /lib64/libQt5Quick.so.5 #7 0x7f4ca4f6e3a7 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () at /lib64/libQt5Quick.so.5 #8 0x7f4ca3318e5b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #9 0x7f4ca41a519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476462] Plasma crashes unexpectedly when I click on the close button in the notification
https://bugs.kde.org/show_bug.cgi?id=476462 curtis.c...@yandex.ru changed: What|Removed |Added CC||curtis.c...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450327] Night Color doesn't work at all on Plasma Wayland with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=450327 Störm Poorun changed: What|Removed |Added CC||i...@stormpoorun.net --- Comment #11 from Störm Poorun --- Nvidia has just released Gamma LUT support! https://www.nvidia.com/download/driverResults.aspx/214100/en-us/ What changes are required to utilise this rather than the current workaround? -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 475189] View an account's featured tags
https://bugs.kde.org/show_bug.cgi?id=475189 Joshua Goins changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||24.02 --- Comment #1 from Joshua Goins --- Added in 24.02! -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 474386] Neochat crashes on quit
https://bugs.kde.org/show_bug.cgi?id=474386 Tobias Fella changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/neochat/-/commit/0c60bf ||db83957042fd1b3a8236d658f44 ||370ec31 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Tobias Fella --- Git commit 0c60bfdb83957042fd1b3a8236d658f44370ec31 by Tobias Fella. Committed on 04/11/2023 at 17:03. Pushed by tfella into branch 'master'. Don't crash on quit M +2-1src/controller.cpp https://invent.kde.org/network/neochat/-/commit/0c60bfdb83957042fd1b3a8236d658f44370ec31 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476277] valgrind not able to startup in arm 64board using 32bit tool chain
https://bugs.kde.org/show_bug.cgi?id=476277 John Reiser changed: What|Removed |Added CC||jrei...@bitwagon.com --- Comment #1 from John Reiser --- This bug report itself could be improved by specifying the versions used on the "arm 64 board." Such version information typically helps a lot to reproduce the problem, which helps understand and fix it faster. In the header of this bug report, the Platform is identified as "RedHat Enterprise Linux". Please specify which release, which is contained in /etc/os-release on the arm64 board (not on the development environment). Another helpful information is given by running "/usr/bin/uname -a" Then, RedHat (and Fedora, and SuSE) uses the RPM package manager to track installed software. Please specify the package involved. This information can be found by running a query using /usr/bin/rpm on the arm64 board; something like: $ rpm -qf /lib64/ld-linux-aarch.so.3 # use the actual path for ld-linux on the arm64 board glibc-2.37-13.el9.aarch # example package name; please report the actual output from "rpm -qf /path/to/ld-linux". -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476552] New: Clipboard is sent to phone when re-enabling clipboard plugin
https://bugs.kde.org/show_bug.cgi?id=476552 Bug ID: 476552 Summary: Clipboard is sent to phone when re-enabling clipboard plugin Classification: Applications Product: kdeconnect Version: 23.08.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: ditzy_dreamland...@slmail.me CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY If I disable and re-enable the clipboard plugin after turning off clipboard autosharing it gets sent to phone. STEPS TO REPRODUCE 1. Enable clipboard plugin on pc. 2. Disable clipboard autosharing in plugin settings. 3. Disable and re-enable the clipboard plugin. OBSERVED RESULT Clipboard sent to phone. EXPECTED RESULT Clipboard not sent to phone. SOFTWARE/OS VERSIONS Phone: OnePlus Nord CE 2 Lite 5G Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 472302] Text in input doesn't wrap and become a multi-line string after hitting Shift+Enter
https://bugs.kde.org/show_bug.cgi?id=472302 Hugo Ortega_H changed: What|Removed |Added CC||hugor...@gmail.com --- Comment #5 from Hugo Ortega_H --- I just upgraded my Linux distribution and came here to see if someone had reported the problem. Also, there is no way to put a background color in the text, something that was possible in previous versions. But maybe this should be another issue report. Aside from that, I really liked the new UI. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 475825] Tokodon crash when clicking "Notifications" in sidebar
https://bugs.kde.org/show_bug.cgi?id=475825 --- Comment #6 from Joshua Goins --- Unfortunately I still don't have enough information to reproduce :/ It's not your fault, this is just the worst kind of crash. 23.08.3 is right around the corner, let's see if that might fix your issue. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476551] New: Clipboard is sent to phone when reconnecting after disabling clipboard autoshare
https://bugs.kde.org/show_bug.cgi?id=476551 Bug ID: 476551 Summary: Clipboard is sent to phone when reconnecting after disabling clipboard autoshare Classification: Applications Product: kdeconnect Version: 23.08.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: ditzy_dreamland...@slmail.me CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Disable clipboard autoshare from pc. 2. Connect phone and pc. 3. Open KDE Connect pair new device screen on phone. 4. Disconnect pc from WiFi and wait until KDE Connect disappears from systray. 5. Copy some text. 6. Connect to WiFi and refresh pair new device screen on phone to reconnect. OBSERVED RESULT Clipboard is sent to phone. EXPECTED RESULT Clipboard not sent to phone. SOFTWARE/OS VERSIONS Phone: OnePlus Nord CE 2 Lite 5G Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476340] After disabling the laptop screen while an external screen is connected, disconnecting the external screen doesn't re-activate the laptop screen
https://bugs.kde.org/show_bug.cgi?id=476340 Harald Sitter changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||sit...@kde.org --- Comment #2 from Harald Sitter --- Can reproduce with clean configs, some pre-existing degree of configs will make this not reproducible for some reason though. What appears to happen is that DrmOutput in KWin doesn't get an update with enabled=true so the builtin screen stays disabled. Curiously kscreen does however think the output is enabled, so it seems there is a communication problem between the two. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453890] Umount icon unnecessarily shown for internal drives
https://bugs.kde.org/show_bug.cgi?id=453890 --- Comment #28 from Julius R. --- I also still experience this bug. When mounting a drive with $ veracrypt or $ cryptsetup, the drive will be shown with the unmount icon. Unmounting an encrypted drive accidently can cause serious data corruption! This icon MUST go. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476550] New: The screen dimming function does not work properly.
https://bugs.kde.org/show_bug.cgi?id=476550 Bug ID: 476550 Summary: The screen dimming function does not work properly. Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jon9...@gmail.com Target Milestone: --- Created attachment 162860 --> https://bugs.kde.org/attachment.cgi?id=162860=edit Scr The screen dimming function does not work properly. I have 3 monitors and after the brightness of the monitor decreases, if I move the mouse, the same brightness is set on all monitors. Simply put, the brightness settings of the monitors are lost to a single value. I have 27 brightness on the first monitor, 27 on the second, and 100 on the third. The "Screen Fading" mode is turned on and when you exit it, the brightness of all monitors becomes 27. Operating System: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-zen2-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × Intel® Core™ i7-10700K CPU @ 3.80GHz Memory: 62.7 ГиБ of RAM Graphics Processor: NVIDIA GeForce RTX 4080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C80 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 --- Comment #15 from knuteir...@gmail.com --- (In reply to Natalie Clarius from comment #13) > > echo "org.kde.powerdevil=true" >> ~/.config/QtProject/qtlogging.ini No file or folder with that name, I manually created it but not sure if it made a difference. I figured out the bug seem to only happen on my LG C9 55" TV because when I plugged in my proper PC monitor powerdevil don't spike CPU and I am able to enter power settings. I'll add journalctl -b 0 | grep -i 'powerdevil' after fresh reboot for both monitors below. LG OLED TV: x@zxc ~> journalctl -b 0 | grep -i 'powerdevil' Nov 04 15:24:17 zxc systemd[692]: Starting Powerdevil... Nov 04 15:24:17 zxc kded5[816]: kscreen.kded: PowerDevil SuspendSession action not available! Nov 04 15:24:18 zxc dbus-daemon[529]: [system] Activating service name='org.kde.powerdevil.discretegpuhelper' requested by ':1.44' (uid=1000 pid=915 comm="/usr/lib/org_kde_powerdevil") (using servicehelper) Nov 04 15:24:18 zxc dbus-daemon[529]: [system] Successfully activated service 'org.kde.powerdevil.discretegpuhelper' Nov 04 15:24:18 zxc dbus-daemon[529]: [system] Activating service name='org.kde.powerdevil.chargethresholdhelper' requested by ':1.44' (uid=1000 pid=915 comm="/usr/lib/org_kde_powerdevil") (using servicehelper) Nov 04 15:24:18 zxc dbus-daemon[529]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper' Nov 04 15:24:18 zxc dbus-daemon[529]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.44' (uid=1000 pid=915 comm="/usr/lib/org_kde_powerdevil") (using servicehelper) Nov 04 15:24:18 zxc backlighthelper[957]: org.kde.powerdevil: no kernel backlight interface found Nov 04 15:24:18 zxc dbus-daemon[529]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Nov 04 15:24:18 zxc org_kde_powerdevil[915]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" Nov 04 15:24:18 zxc org_kde_powerdevil[915]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed Nov 04 15:24:23 zxc systemd[692]: plasma-powerdevil.service: start operation timed out. Terminating. Nov 04 15:24:23 zxc systemd[692]: plasma-powerdevil.service: Failed with result 'timeout'. Nov 04 15:24:23 zxc systemd[692]: Failed to start Powerdevil. Nov 04 15:24:23 zxc systemd[692]: plasma-powerdevil.service: Consumed 2.744s CPU time. Nov 04 15:24:23 zxc systemd[692]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 1. Nov 04 15:24:23 zxc systemd[692]: Starting Powerdevil... Nov 04 15:24:23 zxc org_kde_powerdevil[1041]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" Nov 04 15:24:23 zxc org_kde_powerdevil[1041]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed Nov 04 15:24:28 zxc systemd[692]: plasma-powerdevil.service: start operation timed out. Terminating. Nov 04 15:24:28 zxc systemd[692]: plasma-powerdevil.service: Failed with result 'timeout'. Nov 04 15:24:28 zxc systemd[692]: Failed to start Powerdevil. Nov 04 15:24:28 zxc systemd[692]: plasma-powerdevil.service: Consumed 2.758s CPU time. Nov 04 15:24:28 zxc systemd[692]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 2. Nov 04 15:24:28 zxc systemd[692]: Starting Powerdevil... Nov 04 15:24:29 zxc org_kde_powerdevil[1426]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" Nov 04 15:24:29 zxc org_kde_powerdevil[1426]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed Samsung pc monitor: x@zxc ~> journalctl -b 0 | grep -i 'powerdevil' Nov 04 15:26:21 zxc systemd[723]: Starting Powerdevil... Nov 04 15:26:21 zxc dbus-daemon[537]: [system] Activating service name='org.kde.powerdevil.discretegpuhelper' requested by ':1.41' (uid=1000 pid=922 comm="/usr/lib/org_kde_powerdevil") (using servicehelper) Nov 04 15:26:21 zxc dbus-daemon[537]: [system] Successfully activated service 'org.kde.powerdevil.discretegpuhelper' Nov 04 15:26:21 zxc dbus-daemon[537]: [system] Activating service name='org.kde.powerdevil.chargethresholdhelper' requested by ':1.41' (uid=1000 pid=922 comm="/usr/lib/org_kde_powerdevil") (using servicehelper) Nov 04 15:26:21 zxc dbus-daemon[537]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper' Nov 04 15:26:21 zxc dbus-daemon[537]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.41' (uid=1000 pid=922 comm="/usr/lib/org_kde_powerdevil") (using servicehelper) Nov 04 15:26:21 zxc backlighthelper[970]: org.kde.powerdevil: no kernel backlight interface found Nov 04 15:26:21 zxc dbus-daemon[537]: [system] Successfully activated service
