[plasmashell] [Bug 484540] Panel settings have regressed, "windows can cover" is a missing option and is gravely missed.
https://bugs.kde.org/show_bug.cgi?id=484540 benjamin weber changed: What|Removed |Added CC||benji.we...@gmail.com --- Comment #2 from benjamin weber --- Dodge windows is not currently a replacement for windows can cover. Dodge appears to autohide if windows are close, whereas windows can cover kept the panel visible behind. Take this example https://benjiweber.co.uk/b/allscreens.png This panel now either covers the bottom of the chrome window , or disappears completely, making it useless. Whereas before the chrome could cover the panel in one place and the large amounts of panel on either side remain well usable. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484771] Windows 10 Machines without Samba 1 Enabled does not appear in Dolphin Network Discovery if wsdd package is also installed
https://bugs.kde.org/show_bug.cgi?id=484771 josebarg2...@hotmail.com changed: What|Removed |Added CC||josebarg2...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983 --- Comment #11 from Igor Kushnir --- (In reply to frmdstryr from comment #10) > There may be an better/easier way to fix it since it seems like a race > condition because there is a watch on create and dirty it so the job appears > to be running twice in parallel. Sorry, haven't noticed the suggestion about a better fix before reviewing your merge request. I think the Meson configure job creates the file. The MESON_FAILED_CONFIGURATION branch in MesonBuilder::configure() is taken. But I don't know how to fix this properly. Detect the configure loop and break it somehow? Would that be better than the relatively simple and safe file hash sum approach in the merge request? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484767] Discover crashes every time I try to search for a package
https://bugs.kde.org/show_bug.cgi?id=484767 Antonio Rojas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 473472 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 473472] Discover crashes in KNSResultsStream::setRequest() when refreshing updates
https://bugs.kde.org/show_bug.cgi?id=473472 Antonio Rojas changed: What|Removed |Added CC||yuraposta...@proton.me --- Comment #23 from Antonio Rojas --- *** Bug 484767 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483008] Turning off external monitor causes kwin crash
https://bugs.kde.org/show_bug.cgi?id=483008 --- Comment #20 from agap...@hotmail.com --- It seems that I am still getting kwin_wayland crashes even after updating to plasma 6.03 on arch. Backtrace is attached -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483008] Turning off external monitor causes kwin crash
https://bugs.kde.org/show_bug.cgi?id=483008 --- Comment #21 from agap...@hotmail.com --- Created attachment 167957 --> https://bugs.kde.org/attachment.cgi?id=167957&action=edit Kwin_wayland crash on Plasma 6.03 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 484772] New: unable to have a functional kscreenlocker apart from the default one :breeze
https://bugs.kde.org/show_bug.cgi?id=484772 Bug ID: 484772 Summary: unable to have a functional kscreenlocker apart from the default one :breeze Classification: Plasma Product: kscreenlocker Version: 6.0.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: cherifkah...@gmail.com Target Milestone: --- each time that i select a kscreenlocker (sddm) module that i've downloaded frome the store and compatible with plasma 6.0.2-3, it doesn't work STEPS TO REPRODUCE 1. install a kscreen module frome the store 2. select it 3. close/reboot your session/device 4. observe a stock ksceenlocker picture OBSERVED RESULT i have issue info related with qt6quick not found and the default start screen (sddm) EXPECTED RESULT be able to selecte and use any compatible ksceenlocker with plasma 6.0.XX SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.2-zen2-1-zen (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480862] Unable to assign numpad keys to shortcuts on Wayland
https://bugs.kde.org/show_bug.cgi?id=480862 Andres changed: What|Removed |Added Version|5.93.0 |6.0.3 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #6 from Andres --- Still not fixed on 6.0.3. Shouldn't the fix be in there? Operating System: Garuda Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.2-3-cachyos (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484715] crash upon opening past files
https://bugs.kde.org/show_bug.cgi?id=484715
Vera Tymchenko changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #2 from Vera Tymchenko ---
I'm not sure installing AppImage on this machine is a good idea.
Nevertheless, I have uninstalled snap to try the APT version at least, only to
learn there are only VERY outdated apt versions in backports like 5.0.2. I have
installed snap again and now it starts and immediately crashes after I see
briefly splash picture.
If I start it from the command line, the console output looks like this:
$ krita
Qt: Session management error: Could not open network socket
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: iris
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: iris
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: swrast
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: iris
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: iris
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: swrast
Qt: Session management error: Could not open network socket
Invalid profile : "/snap/krita/100/usr/share/color/icc/colord/Crayons.icc"
Invalid profile : "/snap/krita/100/usr/share/color/icc/colord/x11-colors.icc"
Cannot mix incompatible Qt library (5.15.11) with this library (5.15.12)
Aborted (core dumped)
It says there is coredump but it's certainly not in the usual place of
/var/crash so I can't provide it.
And /snap sub-tree doesn't have it either
$ ll /snap/krita/current/var/
total 0
drwxr-xr-x 3 root root 26 maalis 29 10:49 ./
drwxr-xr-x 13 root root 195 maalis 29 10:49 ../
drwxr-xr-x 3 root root 27 maalis 29 10:49 lib/
I would like to avoid AppImage as in the past they were poorly behaving on this
system.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 484773] New: "open folders during drag operations" doesn't work as expected between windows/views on wayland
https://bugs.kde.org/show_bug.cgi?id=484773 Bug ID: 484773 Summary: "open folders during drag operations" doesn't work as expected between windows/views on wayland Classification: Applications Product: dolphin Version: 24.02.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: martin.cor...@ed.ac.uk CC: kfm-de...@kde.org Target Milestone: --- SUMMARY In Wayland: When dragging an item from one view (F3) or window to another, the folder does not open, even if "View->Open folders during drag operations" has been selected in dolphin config. Works as expected in X, and within a view. STEPS TO REPRODUCE 1. Select "View->Open folders during drag operations" 2. Either press F3 (for two views), or open two windows. 3. Drag a file from one view/window over a folder in the other. OBSERVED RESULT Folder is highlighted but nothing further happens. EXPECTED RESULT After a delay, the folder should open and show its contents. SOFTWARE/OS VERSIONS Arch Linux: kernel 6.8.2-zen2-1-zen KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 484727] KDE Connect's "Receiving File (Finished)" notification displays and opens incorrect file name for renamed copies
https://bugs.kde.org/show_bug.cgi?id=484727 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/network/kdeconnect-kde/-/merge_requests/663 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480862] Unable to assign numpad keys to shortcuts on Wayland
https://bugs.kde.org/show_bug.cgi?id=480862 Nicolas Fella changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Nicolas Fella --- You need Qt 6.6.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480862] Unable to assign numpad keys to shortcuts on Wayland
https://bugs.kde.org/show_bug.cgi?id=480862 Nicolas Fella changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461123] "The screen locker is broken and unlocking is not possible anymore" with console output saying "Creating a fake screen in order for Qt not to crash"
https://bugs.kde.org/show_bug.cgi?id=461123 Eumel changed: What|Removed |Added CC||blaueshawaiih...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 473472] Discover crashes in KNSResultsStream::setRequest() when refreshing updates
https://bugs.kde.org/show_bug.cgi?id=473472 yuraposta...@proton.me changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #24 from yuraposta...@proton.me --- I'm reporter of bug 484767 which was marked as duplicate. I have Discover version 6.0.3 and this bug has NOT been resolved. I still get crashes when I search for any package. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479952] Raising primary screen's scale factor and then plugging in a previously-attached secondary screen results in gaps between them
https://bugs.kde.org/show_bug.cgi?id=479952 --- Comment #4 from fanzhuyi...@gmail.com --- https://invent.kde.org/plasma/kwin/-/issues/217 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 484772] unable to have a functional kscreenlocker apart from the default one :breeze
https://bugs.kde.org/show_bug.cgi?id=484772 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from fanzhuyi...@gmail.com --- Please report this to the developers of these 3rd party kscreenlocker/sddm modules. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484769] gap between application's window and the plasma panels
https://bugs.kde.org/show_bug.cgi?id=484769 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||fanzhuyi...@gmail.com --- Comment #6 from fanzhuyi...@gmail.com --- If the visibility mode of the panel is always visible, maximized windows won't overlap with the strip taken up by the panel, and this is intentional. You can set the visibility mode to windows go below so that maximized windows can go below the panels. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484774] New: Removing last (1 of 1 entries) from the Clipboard is impossible
https://bugs.kde.org/show_bug.cgi?id=484774 Bug ID: 484774 Summary: Removing last (1 of 1 entries) from the Clipboard is impossible Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: cherifkah...@gmail.com Target Milestone: 1.0 Created attachment 167958 --> https://bugs.kde.org/attachment.cgi?id=167958&action=edit clipboard apllet SUMMARY on wayland it is IMPOSSIBLE to remove the last entry in the clipboar applet. or at least I should say that there is always one line left after clearing the history STEPS TO REPRODUCE 1. open a wayland session 2. copy several times differents entries 3. clear the historic of your clipboard 4. observe a line that remains OBSERVED RESULT one line always keeps in the clipboard historic EXPECTED RESULT clear the clipboard = an empty clipboard applet SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.2-zen2-1-zen (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION as i said it occures only with wayland, no matter that wl-clipboard pkg is installed of not -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484774] Removing last (1 of 1 entries) from the Clipboard is impossible
https://bugs.kde.org/show_bug.cgi?id=484774 Cherkah changed: What|Removed |Added CC||cherifkah...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482468] Plasma 6 Floating Panel unfloat distance is more than the designed 12px
https://bugs.kde.org/show_bug.cgi?id=482468 fanzhuyi...@gmail.com changed: What|Removed |Added CC||alisson@outlook.com --- Comment #4 from fanzhuyi...@gmail.com --- *** Bug 484761 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484761] Floating panel switches to anchored style too early when a window is near
https://bugs.kde.org/show_bug.cgi?id=484761 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 482468 *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484756] Plasma 6 - Focus issue with Jetbrains product
https://bugs.kde.org/show_bug.cgi?id=484756 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- Possibly related reports on archlinuxcn forums: https://bbs.archlinuxcn.org/viewtopic.php?pid=59224 https://bbs.archlinuxcn.org/viewtopic.php?id=14151 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482198] System Monitor crashes when discarding changes on edit page
https://bugs.kde.org/show_bug.cgi?id=482198 Dashon changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #9 from Dashon --- I was retesting various bugs that were fixed in 6.0.3 which just landed in Arch and this problem is still happening. The reproduction steps by the OP are still reproducible. Qt 6.6.3 is in the testing repositories and will probably land soon, so maybe that is a requirement for this actually being fixed. Anyways to reiterate the reproduction steps for this are as follows: 1. Open system monitor 2. Click on "Edit Page" 3. Click on "Discard Changes" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484472] Overview effect crashes kwin
https://bugs.kde.org/show_bug.cgi?id=484472 Guido changed: What|Removed |Added Summary|Overview effect crashs kwin |Overview effect crashes ||kwin --- Comment #7 from Guido --- The bug affects also 6.0.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484472] Overview effect crashes kwin
https://bugs.kde.org/show_bug.cgi?id=484472 --- Comment #8 from Guido --- The bug affects also kwin 6.0.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484769] gap between application's window and the plasma panels
https://bugs.kde.org/show_bug.cgi?id=484769 --- Comment #7 from Cherkah --- it do works in auto-hide which is better than always to have on eye on the dock panel (visually intrusive and limits the use of the maximized view) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] Bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 --- Comment #15 from Michał Dybczak --- I just updated to Plasma 6.0.3. The easiest way to spot the bug is to run a YouTube video that has black stripes (different format than monitor) above and below the video, so when the see-through line is present, it can be very clearly visible. In this case, it still is. My monitor is 1440p with 130% scale, Wayland. The see-through line below the panel is still there. As far I can tell, nothing has changed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484769] gap between application's window and the plasma panels
https://bugs.kde.org/show_bug.cgi?id=484769 --- Comment #8 from fanzhuyi...@gmail.com --- (In reply to Cherkah from comment #7) > it do works in auto-hide which is better than always to have on eye on the > dock panel (visually intrusive and limits the use of the maximized view) Or dodge windows -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484769] gap between application's window and the plasma panels
https://bugs.kde.org/show_bug.cgi?id=484769 --- Comment #9 from Cherkah --- (In reply to fanzhuyifan from comment #8) > (In reply to Cherkah from comment #7) > > it do works in auto-hide which is better than always to have on eye on the > > dock panel (visually intrusive and limits the use of the maximized view) > > Or dodge windows doesn't work in dodge -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482371] Dragging Widget from Desktop to Panel Causes Widget to get Stuck on the Desktop
https://bugs.kde.org/show_bug.cgi?id=482371 --- Comment #12 from Dashon --- Decided to grab Qt 6.6.3 from the testing repos and so far that doesn't solve the issue either. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482198] System Monitor crashes when discarding changes on edit page
https://bugs.kde.org/show_bug.cgi?id=482198 Dashon changed: What|Removed |Added Version|6.0.0 |6.0.3 --- Comment #10 from Dashon --- Qt 6.6.3 Doesn't solve the problem either -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 481461] Clicking checkbox to select content to share does not work
https://bugs.kde.org/show_bug.cgi?id=481461 kde.quote...@passinbox.com changed: What|Removed |Added CC||kde.quote...@passinbox.com --- Comment #8 from kde.quote...@passinbox.com --- Experiencing the same issue with KDE neon user edition 6.0. Clicking the checkbox does not enable the share button SOFTWARE/OS VERSIONS Operating System: KDE neon KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Out of curiosity I tested KDE neon Unstable Edition. The checkbox and the share button got fully removed there. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.1.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 475133] Opening a file while another one is already open won't set focus to the file tab
https://bugs.kde.org/show_bug.cgi?id=475133 --- Comment #3 from Dan Dascalescu --- @Pedro: I've set the Focus stealing prevention to "Extreme" and still see the issue in Krusader 2.8.0. Not sure how to tell the default mode for KrViewer. But the issue persists if I press F4 on .txt files, which launched KrViewer in text editing mode. @Toni: I've looked at the build steps and unfortunately I'm short on time right now to follow them (from experience, hunting for the deps was a time-consuming and error prone operation). A suggestion to make building easier for non-contributors would be to add a copy/pasteable `sudo apt/dnf install` line that would install/update all required dependencies, and another one for optional dependencies. Or even better, a copy/pasteable code section with all the installation steps, that could be run unattended (still 🤞 that there will be no errors). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 Jurica Vukadin changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #18 from Jurica Vukadin --- Still seeing this with Arch 6.0.3 packages. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 433816] Crash recovery is not working
https://bugs.kde.org/show_bug.cgi?id=433816 diekuhran...@web.de changed: What|Removed |Added CC||diekuhran...@web.de Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #14 from diekuhran...@web.de --- Can you please report whether the problem still exists? Or can we close the bug report? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 441397] Rendering error
https://bugs.kde.org/show_bug.cgi?id=441397 diekuhran...@web.de changed: What|Removed |Added CC||diekuhran...@web.de Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from diekuhran...@web.de --- Can you please report whether the problem still exists? Or can we close the bug report? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 444717] Different audio volumes in editor window and rendered video
https://bugs.kde.org/show_bug.cgi?id=444717 diekuhran...@web.de changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from diekuhran...@web.de --- Can you please report whether the problem still exists? Or can we close the bug report? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446022] Failed exporting a video.
https://bugs.kde.org/show_bug.cgi?id=446022 diekuhran...@web.de changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||diekuhran...@web.de --- Comment #1 from diekuhran...@web.de --- Can you please report whether the problem still exists? Or can we close the bug report? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455187] Ultra slow, takes about 20 times longer to encode and then crashes.
https://bugs.kde.org/show_bug.cgi?id=455187 diekuhran...@web.de changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||diekuhran...@web.de Resolution|--- |WAITINGFORINFO --- Comment #1 from diekuhran...@web.de --- Can you please report whether the problem still exists? Or can we close the bug report? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463096] There is no way to adjust the screen size
https://bugs.kde.org/show_bug.cgi?id=463096 diekuhran...@web.de changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||diekuhran...@web.de Status|REPORTED|NEEDSINFO --- Comment #1 from diekuhran...@web.de --- Can you please report whether the problem still exists? Or can we close the bug report? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463131] There is no way to adjust the screen size
https://bugs.kde.org/show_bug.cgi?id=463131 diekuhran...@web.de changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||diekuhran...@web.de --- Comment #1 from diekuhran...@web.de --- Can you please report whether the problem still exists? Or can we close the bug report? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482198] System Monitor crashes when discarding changes on edit page
https://bugs.kde.org/show_bug.cgi?id=482198 --- Comment #11 from Dashon --- I went and built plasma system monitor from git master and the issue has indeed been fixed. Either something is wrong with the arch package for plasma-system-monitor version 6.0.3 or something wasn't cherry picked to the 6.0.3 bug fix release. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 472453] krfb asserts in PWFrameBuffer::cursorPosition
https://bugs.kde.org/show_bug.cgi?id=472453 Antti Savolainen changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484745] inconsistent date for Dynamic Media:Shot Date in case of .mov video
https://bugs.kde.org/show_bug.cgi?id=484745 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.4.0 Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/digikam/-/commit/a355c ||119ecc28b09c3519a88c7d30be7 ||86d0398e Resolution|--- |FIXED --- Comment #4 from Maik Qualmann --- Git commit a355c119ecc28b09c3519a88c7d30be786d0398e by Maik Qualmann. Committed on 30/03/2024 at 19:12. Pushed by mqualmann into branch 'master'. fix date representation of "Xmp.xmpDM.shotDate" FIXED-IN: 8.4.0 M +1-1NEWS M +1-1core/libs/metadataengine/dmetadata/dmetadata_video.cpp https://invent.kde.org/graphics/digikam/-/commit/a355c119ecc28b09c3519a88c7d30be786d0398e -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI
https://bugs.kde.org/show_bug.cgi?id=482819 Fabian Vogt changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||fab...@ritter-vogt.de Resolution|--- |WAITINGFORINFO --- Comment #20 from Fabian Vogt --- (In reply to Matt Fagnani from comment #8) > I bisected this problem with qca from 2.3.7 to 2.3.8. The following first > bad commit involved loading legacy openssl providers. > > 14eb1ae746c3c75afaef02b487ac65b3de85ad15 is the first bad commit > commit 14eb1ae746c3c75afaef02b487ac65b3de85ad15 > Author: Fabian Vogt > Date: Fri Dec 22 13:36:00 2023 +0100 > > plugins/qca-ossl: Actually try loading the legacy provider > > OSSL_PROVIDER_available returns true only for loaded providers, not > whether > a provider can be loaded. Use OSSL_PROVIDER_try_load instead, which also > allows to keep the default fallback provider. > > plugins/qca-ossl/qca-ossl.cpp | 24 +--- > 1 file changed, 5 insertions(+), 19 deletions(-) My theory is that without this commit, using kwalletd6 with OpenSSL >= 3.0 will just fail early enough that the broken code path is not even reached. Comment 19 is one major reason why that would be the case. You could confirm that by creating an OpenSSL config which forces loading of default and legacy providers: $ cat openssl.cnf openssl_conf = openssl_init [openssl_init] providers = provider_sect [provider_sect] default = default_sect legacy = legacy_sect [default_sect] activate = 1 [legacy_sect] activate = 1 And then trying kwallet6 with old qca + "OPENSSL_CONF=openssl.cnf kwallet6". Locally I extracted the createSessionAlgorithmDhAes method into a standalone executable (like comment 15, but more) and ran ltrace on that to get an overview on the used code paths in qca and libcrypto. The call most likely to fail is qca-ossl.cpp:DHKeyMaker::run() -> DH_generate_key, so I simulated that by hardcoding a failure code at that point. The result is a segfault identical to the one observed here. Please do an ltrace of kwalletd6 by running "ltrace -fCl 'libcrypto*' kwalletd6" and quote the output here. If some call fails, that should be visible. Question is why it fails on your system while it does not fail here. Maybe there's an additional check for the parameter length in your OpenSSL version? Upstream only checks for < 512: https://github.com/openssl/openssl/blob/56e63f570bd5a479439bc6f6a2499f6b86ded341/crypto/dh/dh_key.c#L286 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 484775] New: Kontact Does Not Start After Upgrade to Plasma 6.0.3
https://bugs.kde.org/show_bug.cgi?id=484775 Bug ID: 484775 Summary: Kontact Does Not Start After Upgrade to Plasma 6.0.3 Classification: Applications Product: kontact Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: rosad...@yahoo.com 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 After upgrading to Plasma 6.0.3, Kontact fails to start. It was working fine in 6.0.2. In the command line, after typing "Kontact," the following message appears: Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/bin/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/libexec/qt6/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/libexec/qt6/qtwebengine_dictionaries' KCrash: Application 'kontact' crashing... crashRecursionCounter = 2 Segmentation fault (core dumped) Also, I am not getting the "new mail" notifications that I used to get, even with Kontact closed. STEPS TO REPRODUCE 1. Click on Kontact icon in panel 2. Nothing happens 3. OBSERVED RESULT Kontact does not start EXPECTED RESULT Kontact starts SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: opensuse Tumbleweed (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION Stopped getting the "new mail" notifications. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484713] servicemenu exec: not authorized to execute
https://bugs.kde.org/show_bug.cgi?id=484713 --- Comment #5 from andrei+1_multi.kde@adresa.email --- (In reply to Méven Car from comment #4) > Do you have an error message in the console if you launch dolphin from the > command line ? I did run dolphin.exe from cmd but it goes to background and no messages are printed in the console. i did not find any parameter to keep it in foreground/attached to console. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484762] DigiKam doesn't recognize XMP video tags.
https://bugs.kde.org/show_bug.cgi?id=484762 --- Comment #6 from Santiago Figarola --- (In reply to Maik Qualmann from comment #4) > Then you need to enable the option for “Sidecar filenames compatible with > commercial programs”. After re-reading the metadata, everything will be > available. > > Maik One question: is it possible to make DigiKam write to the item and sidecar, ONLY when the item is a video? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 484759] Transaction report fails to update when I expand the date range to include a large number of transactions
https://bugs.kde.org/show_bug.cgi?id=484759 --- Comment #1 from Ben Cooksley --- The content of attachment 167943 has been deleted for the following reason: Removing confidential information -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484776] New: Crash immediately after Debian reboot.
https://bugs.kde.org/show_bug.cgi?id=484776 Bug ID: 484776 Summary: Crash immediately after Debian reboot. Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: 11...@bk.ru CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-18-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Well, right after the reboot, I jumped into Dr.konki segmentation fault in plasma. Debian has been installed for a long time, there are many programs. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 4714 (plasmashell) UID: 1000 (viktor) GID: 1000 (viktor) Signal: 11 (SEGV) Timestamp: Sat 2024-03-30 22:06:09 MSK (1min 13s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (viktor) Boot ID: 878ea999e89f42c083d55b5546344a00 Machine ID: 7f7d846d0467439bb8c3596e908bca2a Hostname: debian-pc Storage: /var/lib/systemd/coredump/core.plasmashell.1000.878ea999e89f42c083d55b5546344a00.4714.171182556900.zst (present) Size on Disk: 9.5M Message: Process 4714 (plasmashell) 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 4911: #0 0x7f05b8ca9e2c __pthread_kill_implementation (libc.so.6 + 0x8ae2c) #1 0x7f05b8c5afb2 __GI_raise (libc.so.6 + 0x3bfb2) #2 0x7f05bb341b46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f05b8c5b050 __restore_rt (libc.so.6 + 0x3c050) #4 0x7f05b8ca9e2c __pthread_kill_implementation (libc.so.6 + 0x8ae2c) #5 0x7f05b8c5afb2 __GI_raise (libc.so.6 + 0x3bfb2) #6 0x7f05b8c5b050 __restore_rt (libc.so.6 + 0x3c050) #7 0x7f05b8d1b15f __GI___poll (libc.so.6 + 0xfc15f) #8 0x7f05b7b6a9ae n/a (libglib-2.0.so.0 + 0x549ae) #9 0x7f05b7b6aacc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #10 0x7f05b9109836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #11 0x7f05b90b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #12 0x7f05b8ecab87 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcab87) #13 0x7f05ba928555 n/a (libQt5Qml.so.5 + 0x328555) #14 0x7f05b8ecbd43 n/a (libQt5Core.so.5 + 0xcbd43) #15 0x7f05b8ca8134 start_thread (libc.so.6 + 0x89134) #16 0x7f05b8d287dc __clone3 (libc.so.6 + 0x1097dc) Stack trace of thread 5562: #0 0x7f05b8ca4e96 __futex_abstimed_wait_common64 (libc.so.6 + 0x85e96) #1 0x7f05b8ca783c __pthread_cond_wait_common (libc.so.6 + 0x8883c) #2 0x7f05b8ed19bc _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd19bc) #3 0x7f05b8ecf0a5 n/a (libQt5Core.so.5 + 0xcf0a5) #4 0x7f05b8ecbd43 n/a (libQt5Core.so.5 + 0xcbd43) #5 0x7f05b8ca8134 start_thread (libc.so.6 + 0x89134) #6 0x7f05b8d287dc __clone3 (libc.so.6 + 0x1097dc) Stack trace of thread 4734: #0 0x7f05b8d1727f __GI___libc_write (libc.so.6 + 0xf827f) #1 0x7f05b8c9ffc5 _IO_new_file_write (libc.so.6 + 0x80fc5) #2 0x7f05b8c9f380 new_do_write (libc.so.6 + 0x80380) #3 0x7f05b8ca0fd9 _IO_new_do_write (libc.so.6 + 0x81fd9) #4 0x7f05b8ca063e _IO_new_file_xsputn (libc.so.6 + 0x8163e) #5 0x7f05b8c7b9dd outstring_func (libc.so.6 + 0x5c9dd) #6 0x7f05b8d359ef ___fprintf_chk (libc.so.6 + 0x1169ef) #7 0x7f05b8ec7fb9 n/a (libQt5Core.so.5 + 0xc7fb9) #8 0x7f05b8ec3b50 n/a (libQt5Core.so.5 + 0xc3b50) #9 0
[plasmashell] [Bug 484774] Removing last (1 of 1 entries) from the Clipboard is impossible
https://bugs.kde.org/show_bug.cgi?id=484774 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from fanzhuyi...@gmail.com --- Could you share a screenshot if you go to configure clipboard - general? In particular, do you have Keep selection and clipboard the same selected? FWIW can't reproduce on git master, wayland, arch linux. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 484775] Kontact Does Not Start After Upgrade to Plasma 6.0.3
https://bugs.kde.org/show_bug.cgi?id=484775 --- Comment #1 from Pedro Rosado --- When to Dr. Konqui and this is what I got: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. PID: 21681 (kontact) UID: 1000 (pedro) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Sat 2024-03-30 00:08:46 EDT (15h ago) Command Line: /usr/bin/kontact Executable: /usr/bin/kontact Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.kontact-a4bdb5ac41514e8fb51c2a1a23411e1d.scope Unit: user@1000.service User Unit: app-org.kde.kontact-a4bdb5ac41514e8fb51c2a1a23411e1d.scope Slice: user-1000.slice Owner UID: 1000 (pedro) Boot ID: d41297dae5794aae8bbb5c60c6f072c9 Machine ID: d5b0a1173265414caab9d70458ec02b9 Hostname: localhost.localdomain Storage: /var/lib/systemd/coredump/core.kontact.1000.d41297dae5794aae8bbb5c60c6f072c9.21681.171177172600.zst (present) Size on Disk: 7.2M Message: Process 21681 (kontact) of user 1000 dumped core. Stack trace of thread 21709: #0 0x7ff8ab8949ec __pthread_kill_implementation (libc.so.6 + 0x949ec) #1 0x7ff8ab841176 raise (libc.so.6 + 0x41176) #2 0x7ff8adc60b93 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x6b93) #3 0x7ff8ab841240 __restore_rt (libc.so.6 + 0x41240) #4 0x7ff88cf2b98d n/a (crocus_dri.so + 0x72b98d) #5 0x7ff88cf2bb49 n/a (crocus_dri.so + 0x72bb49) #6 0x7ff88d390686 n/a (crocus_dri.so + 0xb90686) #7 0x7ff88d390819 n/a (crocus_dri.so + 0xb90819) #8 0x7ff88cf3957b n/a (crocus_dri.so + 0x73957b) #9 0x7ff84d2e39ef n/a (r600_drv_video.so + 0x2e39ef) #10 0x7ff84d2e3ce8 n/a (r600_drv_video.so + 0x2e3ce8) #11 0x7ff84d284461 n/a (r600_drv_video.so + 0x284461) #12 0x7ff84d23eac5 n/a (r600_drv_video.so + 0x23eac5) #13 0x7ff84d06a49b n/a (r600_drv_video.so + 0x6a49b) #14 0x7ff899a9f26b vaTerminate (libva.so.2 + 0x726b) #15 0x7ff8a3f34dee n/a (libQt6WebEngineCore.so.6 + 0x2f34dee) #16 0x7ff8a3f3fc6e n/a (libQt6WebEngineCore.so.6 + 0x2f3fc6e) #17 0x7ff8a3f4341c n/a (libQt6WebEngineCore.so.6 + 0x2f4341c) #18 0x7ff8a7557248 n/a (libQt6WebEngineCore.so.6 + 0x6557248) #19 0x7ff8a5741ac5 n/a (libQt6WebEngineCore.so.6 + 0x4741ac5) #20 0x7ff8a5755d6a n/a (libQt6WebEngineCore.so.6 + 0x4755d6a) #21 0x7ff8ab892bb2 start_thread (libc.so.6 + 0x92bb2) #22 0x7ff8ab91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 21700: #0 0x7ff8ab914486 epoll_wait (libc.so.6 + 0x114486) #1 0x7ff89ed33c74 n/a (libevent-2.1.so.7 + 0x2cc74) #2 0x7ff89ed2c051 event_base_loop (libevent-2.1.so.7 + 0x25051) #3 0x7ff8a5775f51 n/a (libQt6WebEngineCore.so.6 + 0x4775f51) #4 0x7ff8a572055c n/a (libQt6WebEngineCore.so.6 + 0x472055c) #5 0x7ff8a56e8890 n/a (libQt6WebEngineCore.so.6 + 0x46e8890) #6 0x7ff8a57409dc n/a (libQt6WebEngineCore.so.6 + 0x47409dc) #7 0x7ff8a573024d n/a (libQt6WebEngineCore.so.6 + 0x473024d) #8 0x7ff8a5741ab8 n/a (libQt6WebEngineCore.so.6 + 0x4741ab8) #9 0x7ff8a5755d6a n/a (libQt6WebEngineCore.so.6 + 0x4755d6a) #10 0x7ff8ab892bb2 start_thread (libc.so.6 + 0x92bb2) #11 0x7ff8ab91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 21689: #0 0x7ff8ab88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x7ff8ab891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x7ff88c9111bb n/a (crocus_dri.so + 0xbb) #3 0x7ff88c9071c7 n/a (crocus_dri.so + 0x1071c7) #4 0x7ff8ab892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x7ff8ab91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 21705: #0 0x7ff8ab88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x7ff8ab892065 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x92065) #2 0x7ff8a57551dc n/a (libQt6WebEngineCore.so.6 + 0x47551dc) #3 0x7ff8a577c091 n/a (libQt6WebEngineCore.so.6 + 0x477c091) #4 0x7ff8a570030f n/a (libQt6WebEngineCore.so.6 + 0x470030f)
[kontact] [Bug 484775] Kontact Does Not Start After Upgrade to Plasma 6.0.3
https://bugs.kde.org/show_bug.cgi?id=484775 --- Comment #2 from Pedro Rosado --- My apologies. I'm still getting the new mail notifications. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482468] Plasma 6 Floating Panel unfloat distance is more than the designed 12px
https://bugs.kde.org/show_bug.cgi?id=482468 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #5 from Bharadwaj Raju --- (In reply to João Sousa from comment #3) > Thank you for the clarification. So I guess that design setting changed from > the Plasma 5 panel then? Any reason why? The reason is written as a comment in that code. It avoids an issue (https://bugs.kde.org/show_bug.cgi?id=476743) with KWin's snap-to-panel behavior. > The panel floating mode seems to be designed with a default 8px gap distance > from screen edges (and not 9px as I have mentioned on my report). Any chance > that this 8px value can be used instead for the "property int > defloatDistance"? That would potentially allow the use of an identical value > of 8 px as minimal tiling window padding? I tested multiple values, including 8px. It wasn't enough, I found we needed a 12px distance to avoid the snap-to-panel behavior from activating. Other potential solutions can be investigated. Nate suggested disabling the snapping completely when in floating mode. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484762] DigiKam doesn't recognize XMP video tags.
https://bugs.kde.org/show_bug.cgi?id=484762 --- Comment #7 from Maik Qualmann --- We already have a bug report as a request to create a configuration for this. But if you don't activate writing metadata with ExifTool and activate "Only in read-only entries" as an option for writing in sidecar, it should work. Read-only means not only that the files are read-only, but also that Exiv2 cannot write this file type. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484774] Removing last (1 of 1 entries) from the Clipboard is impossible
https://bugs.kde.org/show_bug.cgi?id=484774 --- Comment #2 from Cherkah --- > ... do you have Keep selection and clipboard the same selected? yes i do. And you're right: untick it (Keep selection and clipboard the same selected) give me the possibility to really clear my clipboard history (100% empty) ! But how can it be? either i lose a really important clipboard feature or i keep on entry which can be an password security issue (i use keepassxc/kwallet ) !! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477676] Fractional Scaling breaks chromium/electron apps running in native wayland when scaling down below 100%
https://bugs.kde.org/show_bug.cgi?id=477676 ryu.ketsu...@outlook.com changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from ryu.ketsu...@outlook.com --- I'm sorry but this issue still persists. I have recorded a quick video showing the issue in case it was not clear before: https://youtu.be/U-poT2q7AmY It is still happening for me but on Plasma 6.0.2, fractional scaling on 65%. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477676] Fractional Scaling breaks chromium/electron apps running in native wayland when scaling down below 100%
https://bugs.kde.org/show_bug.cgi?id=477676 ryu.ketsu...@outlook.com changed: What|Removed |Added Version|git-stable-Plasma/5.27 |6.0.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477676] Fractional Scaling breaks chromium/electron apps running in native wayland when scaling down below 100%
https://bugs.kde.org/show_bug.cgi?id=477676 ryu.ketsu...@outlook.com changed: What|Removed |Added CC||ryu.ketsu...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484774] Removing last (1 of 1 entries) from the Clipboard is impossible
https://bugs.kde.org/show_bug.cgi?id=484774 --- Comment #3 from fanzhuyi...@gmail.com --- (In reply to Cherkah from comment #2) > > ... do you have Keep selection and clipboard the same selected? > > yes i do. And you're right: untick it (Keep selection and clipboard the same > selected) give me the possibility to really clear my clipboard history (100% > empty) ! > > But how can it be? either i lose a really important clipboard feature or i > keep on entry which can be an password security issue (i use > keepassxc/kwallet ) !! Please provide your complete settings so we could investigate further. I still can't reproduce when Keep selection and clipboard the same is selected. If nothing is selected, clearing history correctly clears everything. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484758] Displayed dates on Metadata panels come from different dates found in a video file from Ricoh GR II (inconsistency ?)
https://bugs.kde.org/show_bug.cgi?id=484758 --- Comment #8 from Maik Qualmann --- I don't see any real problems here, the Exif metadata block with "2024:03:30 14:34:10" comes directly from ExifTool. We get the Xmp metadata from the "creation_time" from the FFmpeg API, which is probably the QuickTime date. Maik -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484332] Discover crash when click on Installed
https://bugs.kde.org/show_bug.cgi?id=484332 Adam922 changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #3 from Adam922 --- Sorry it was fixed by https://invent.kde.org/frameworks/knewstuff/-/commit/8e80d1c0 just knewstuff didn't release a new version yet. Arch Linux patched it and it's working. https://gitlab.archlinux.org/archlinux/packaging/packages/knewstuff/-/commit/16edd30861a69fdd7517ad23b59b79f07a4ebbc0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483363] Kate has crashed after using rename (F2) context menu option
https://bugs.kde.org/show_bug.cgi?id=483363 --- Comment #10 from Waqar Ahmed --- > sometimes replacing "kwargs.get" with gibberish unexpectedly opens other > scripts (in the path? loaded by LSP? not sure, this is weird. one example of > such file is > "/usr/lib/python3.11/site-packages/jedi/third_party/typeshed/stdlib/3/typing.pyi") > and replaces some *different* keywords with said gibberish in them... i > really don't get this behavior. It tries to replace all references I guess I have been unable to reproduce the crash so far with kate (master) + pylsp v1.10.1 with given steps The server seems super slow to rename stuff, so that might trigger a crash in Kate given we have tons of pointers around these things. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439790] Exported Kate theme reports (incorrect) error message when the theme is imported.
https://bugs.kde.org/show_bug.cgi?id=439790 Waqar Ahmed changed: What|Removed |Added Summary|Exported kate theme reports |Exported Kate theme reports |(incorrect) error message |(incorrect) error message |wmen the theme is imported. |when the theme is imported. CC||waqar@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483575] Delay time between click and menu appearing
https://bugs.kde.org/show_bug.cgi?id=483575 --- Comment #2 from giuseppelovare...@gmail.com --- Created attachment 167959 --> https://bugs.kde.org/attachment.cgi?id=167959&action=edit A short screencast showing the unexpected behavior -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484774] Removing last (1 of 1 entries) from the Clipboard is impossible
https://bugs.kde.org/show_bug.cgi?id=484774 --- Comment #4 from Cherkah --- ok what kind of info settings do you need. Tell me how can i provide them to you (dr.konqui, inxi, neofetch...) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484768] Icon of a uninstalled app should be removed from desktop
https://bugs.kde.org/show_bug.cgi?id=484768 Titouan Camus changed: What|Removed |Added Ever confirmed|0 |1 CC||titouan-ca...@orange.fr Status|REPORTED|CONFIRMED --- Comment #1 from Titouan Camus --- I can reproduce. Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483575] Delay time between click and menu appearing
https://bugs.kde.org/show_bug.cgi?id=483575 --- Comment #3 from giuseppelovare...@gmail.com --- Thank you for testing it out! Actually, I think that the issue is most visible when you set the animation speed to instantaneous. I attached a screen recording of the hamburger menu behavior in systemsettings. It is a slight delay (and maybe you'll think that I am crazy), but I hope to make my point crystal clear with this. Wish you a great weekend, folks! :) PS the interface is in Italian. The slider is the "animation speed" one. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 445351] Akregator always wants to recover the session on boot
https://bugs.kde.org/show_bug.cgi?id=445351 tomas nackaerts changed: What|Removed |Added CC||tomas.nackae...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[buildsystem] [Bug 483781] kde-builder Runtime Error: Invalid variable qt-install-dir
https://bugs.kde.org/show_bug.cgi?id=483781 Thomas Bertels changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Thomas Bertels --- Works fine with the latest version. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484762] DigiKam doesn't recognize XMP video tags.
https://bugs.kde.org/show_bug.cgi?id=484762 --- Comment #8 from Santiago Figarola --- (In reply to Maik Qualmann from comment #7) > We already have a bug report as a request to create a configuration for this. > But if you don't activate writing metadata with ExifTool and activate "Only > in read-only entries" as an option for writing in sidecar, it should work. > Read-only means not only that the files are read-only, but also that Exiv2 > cannot write this file type. > > Maik Alright. Thank you so much. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 462360] When the plasmoid is placed on the panel, it offers no way to access settings
https://bugs.kde.org/show_bug.cgi?id=462360 Alexander changed: What|Removed |Added CC||alexader...@gmail.com --- Comment #1 from Alexander --- Created attachment 167960 --> https://bugs.kde.org/attachment.cgi?id=167960&action=edit Settings button exists -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 462360] When the plasmoid is placed on the panel, it offers no way to access settings
https://bugs.kde.org/show_bug.cgi?id=462360 Alexander changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Alexander --- It does exist. See my attachment. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 462360] When the plasmoid is placed on the panel, it offers no way to access settings
https://bugs.kde.org/show_bug.cgi?id=462360 Alexander changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #3 from Alexander --- (In reply to Alexander from comment #2) > It does exist. See my attachment. Wait no. I see what you mean - not resolved -- You are receiving this mail because: You are watching all bug changes.
[kstart] [Bug 484777] New: autostart order arrows + hierarchy
https://bugs.kde.org/show_bug.cgi?id=484777 Bug ID: 484777 Summary: autostart order arrows + hierarchy Classification: Plasma Product: kstart Version: git-stable-Plasma/5.27 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: pentelja...@o2.pl Target Milestone: --- Created attachment 167961 --> https://bugs.kde.org/attachment.cgi?id=167961&action=edit and can you make possible in autostart arrows to move priority in apps, and and. i wish to start first task manager in left corner but not always is fast enough than other apps. thanks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484758] Displayed dates on Metadata panels come from different dates found in a video file from Ricoh GR II (inconsistency ?)
https://bugs.kde.org/show_bug.cgi?id=484758 --- Comment #9 from mahikeulbody --- We could reasonably expect the dates into the XMP-Exif-specific Properties sub-panel to be the same as in Exif Panel. Having said that, I don't think this minor "bug" deserves much more attention. This report was more of a warning in case this behavior would not be what was intended. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398338] Compilation failure on Musl due to use of vasprintf
https://bugs.kde.org/show_bug.cgi?id=398338 Jonáš Vidra changed: What|Removed |Added CC||vidra.jo...@seznam.cz Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|UPSTREAM|--- --- Comment #2 from Jonáš Vidra --- This bug is still present in Okular 23.08.5. The error was fixed upstream in https://github.com/jlaurens/synctex/pull/39 but reappeared, because the fix was only applied to one branch. I filed a new upstream bug here: https://github.com/jlaurens/synctex/issues/80 There are two related pull requests currently open: https://invent.kde.org/graphics/okular/-/merge_requests/722 https://invent.kde.org/graphics/okular/-/merge_requests/723 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 445889] plasma browser integration failed to connect to native host despite being up to date
https://bugs.kde.org/show_bug.cgi?id=445889 karimelsayad1...@gmail.com changed: What|Removed |Added CC||karimelsayad1...@gmail.com --- Comment #2 from karimelsayad1...@gmail.com --- I've got the same problem. I'm using Tumbleweed Details Operating System: openSUSE Tumbleweed 20240328 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 31.2 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475109] The color picker plugin doesn't work properly.
https://bugs.kde.org/show_bug.cgi?id=475109 Bug Janitor Service changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kate/-/merge_requests/1439 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 484778] New: Feature Request: Cancel Ring my phone
https://bugs.kde.org/show_bug.cgi?id=484778 Bug ID: 484778 Summary: Feature Request: Cancel Ring my phone Classification: Applications Product: kdeconnect Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: bugs.kde@s.bjoern-tantau.de CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY I just lost my phone and Ring my phone revealed it to be under my bed. I couldn't be bothered to retrieve it for tonight and wanted to leave it until tomorrow. But it just kept ringing and I couldn't stop it. STEPS TO REPRODUCE 1. Select Ring my phone 2. Furiously try to stop the ringing 3. Lose mind OBSERVED RESULT Phone keeps ringing. EXPECTED RESULT A new button to stop the phone from ringing without picking it up would be nice. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I was able to retrieve my phone by now, so I lowered the severity from critical to wishlist. ;-) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 484779] New: Impossible do select/deselect all
https://bugs.kde.org/show_bug.cgi?id=484779 Bug ID: 484779 Summary: Impossible do select/deselect all Classification: Plasma Product: Plasma Workspace Wallpapers Version: 5.27.80 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: maksim.mur...@gmail.com Target Milestone: --- In wallpapers selector impossible do select all, if for example I want only couple wallpapers in rotation by default it selects all, and quite opposite. Also is not possible order by selected, an by groups (check box exists but not indication which images with which) Also will be really great if possible grouping wallpapers by mouse, not only by folders -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482306] Keyboard brightness at 0% after closing lid
https://bugs.kde.org/show_bug.cgi?id=482306 --- Comment #13 from Jakob Petsovits --- (In reply to Anthony Vital from comment #12) > Here's a small patch that fixes the issue against the 6.0 branch (I have no > easy way to try the master branch, but it should be the same). > So the issue seems to be that after the lid is closed and the brightness set > to 0, powerdevil receives a signal keyboardBrightnessChanged, and saves this > value for restoration. This patch ensures we store this value only if the > lid is open. > This check existed in the 5.27 branch, I'm not sure why it was removed. Thanks for the patch, great find. I tested this on my ThinkPad, latest master branch, and it indeed makes a difference there as well. I did a little bit of digging in the commit history, my reading is that the removal of this condition was probably unintentional. It got removed together with another condition in the same line that did indeed have to disappear due to a refactoring. More details and perhaps also a confirmation of this theory in the merge request that will get linked by the bot in the next comment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484780] New: icons-only task manager shows also applications of other screen
https://bugs.kde.org/show_bug.cgi?id=484780 Bug ID: 484780 Summary: icons-only task manager shows also applications of other screen Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: germano.massu...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 On the second screen, the icons-only task manager shows also applications of first screen, despite "Show only task from the current screen" option is enabled. I noticed that the other kind of task manager (the one which is NOT icons-only) works well instead, showing only the applications opened on the second screen - Plasma 6.0.2 - Qt 6.6.2 - Fedora 40 KDE -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482306] Keyboard brightness at 0% after closing lid
https://bugs.kde.org/show_bug.cgi?id=482306 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #14 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/powerdevil/-/merge_requests/343 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482122] In split view the location bar of right side adds a drag-able separator in toolbar
https://bugs.kde.org/show_bug.cgi?id=482122 Amol Godbole changed: What|Removed |Added CC||amolagodb...@gmail.com --- Comment #3 from Amol Godbole --- The developers say this behavior is intentional, so as to allow more space for checking the path (see https://invent.kde.org/system/dolphin/-/merge_requests/750). Do you find the moveable separator feature useful, or do you find it strange and inconvenient? Your input is welcome! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484781] New: Sound crash with HDMI output
https://bugs.kde.org/show_bug.cgi?id=484781 Bug ID: 484781 Summary: Sound crash with HDMI output Classification: Applications Product: dolphin Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: maksim.mur...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Sound completely crashed in and show no outputs. If I connect HDMI output device and disable it in "Display settings" this lead to empty sound outputs! I still can use HDMI on reconnect, but no standard output soundcard anymore in list. Reason why I'm trying to do so, I want connect HDMI headphones, but HDMI itself incapable transfer sound without video, do it created 'virtual monitor' which unfortunate counts with system (no way setup it like 1 pixel size), or split it from board for not used spaces by windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482875] Desktop icons reset positions to alphabetical order after a long time from auto shut-off of screen (Wayland)
https://bugs.kde.org/show_bug.cgi?id=482875 --- Comment #7 from linuxboy --- Hello, Note: the bug persists in version 6.03. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482875] Desktop icons reset positions to alphabetical order after a long time from auto shut-off of screen (Wayland)
https://bugs.kde.org/show_bug.cgi?id=482875 linuxboy changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483363] Kate has crashed after using rename (F2) context menu option
https://bugs.kde.org/show_bug.cgi?id=483363 --- Comment #11 from rjx_ <7c6s4b+cc6efdty3b...@sharklasers.com> --- Quick update: After trying various things (removing optional dependencies for py-lsp for example), i isolated the case to my ~/.config/katerc - migrated from the old Qt 5 version of kate - being the culprit here. Will try to isolate it to some (set of?) settings or sanitize a bit and attach the config here, but a tad later. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484782] New: Dolphin save point only on exit
https://bugs.kde.org/show_bug.cgi?id=484782 Bug ID: 484782 Summary: Dolphin save point only on exit Classification: Applications Product: dolphin Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: maksim.mur...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Dolphin does save layout on, program correct exit, but in reality you need it most on sudden crashes, or kills. For now it pickup save from previous successful shutdown. Which is can be not exactly what user want. Make more sense save layout exactly after it active, as many IDEs does for keep work save. Save on change no on exist. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484783] New: Krita recorder causes freehand selection and shapes to complete early before brush stroke is complete
https://bugs.kde.org/show_bug.cgi?id=484783 Bug ID: 484783 Summary: Krita recorder causes freehand selection and shapes to complete early before brush stroke is complete Classification: Applications Product: krita Version: 5.2.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: menjah_transacti...@live.com 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 Krita recorder is on, it seems that lasso selections and brush strokes are interrupted by the recorder, causing selections to complete early before pen tip is raised off tablet. Similar with non-freehand shape brushes, like rectangle circle etc STEPS TO REPRODUCE 1. enable recorder set to small seconds interval 2. try using freehand selection/ lasso, rectangle, circle etc tool 3. usually, the selection will complete itself before your pen lifts from the surface OBSERVED RESULT Shapes, freehand selection tool, complete early when recorder is on EXPECTED RESULT recorder should not interrupt selection SOFTWARE/OS VERSIONS Windows: 12 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484753] Touchpad not found under X11
https://bugs.kde.org/show_bug.cgi?id=484753 Axel Braun changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Axel Braun --- I guess, at least it is Model: "Synaptics TM3512-010" How can I find out? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484332] Discover crash when click on Installed
https://bugs.kde.org/show_bug.cgi?id=484332 Antonio Rojas changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #4 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 473472 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484783] Krita recorder causes freehand selection and shapes to complete early before brush stroke is complete
https://bugs.kde.org/show_bug.cgi?id=484783 --- Comment #1 from LKS --- https://youtu.be/smtdxuQpros Here's a short video of the issue -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 473472] Discover crashes in KNSResultsStream::setRequest() when refreshing updates
https://bugs.kde.org/show_bug.cgi?id=473472 --- Comment #25 from Antonio Rojas --- *** Bug 484332 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 484289] Crash upon saving when you delete newly created folder in file dialog
https://bugs.kde.org/show_bug.cgi?id=484289 Waqar Ahmed changed: What|Removed |Added Ever confirmed|0 |1 CC||waqar@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Waqar Ahmed --- Crash is in kio #0 0x7fa9fd94bb48 in QSortFilterProxyModel::parent(QModelIndex const&) const (/usr/lib/libQt6Core.so.6+0x34bb48) #1 0x7fa9fd914d63 in QAbstractItemModelPrivate::rowsAboutToBeRemoved(QModelIndex const&, int, int) (/usr/lib/libQt6Core.so.6+0x314d63) #2 0x7fa9fd94b56c (/usr/lib/libQt6Core.so.6+0x34b56c) #3 0x7fa9fd94c820 (/usr/lib/libQt6Core.so.6+0x34c820) #4 0x7fa9fd790ca8 (/usr/lib/libQt6Core.so.6+0x190ca8) #5 0x7fa9fd91ed19 in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) (/usr/lib/libQt6Core.so.6+0x31ed19) #6 0x7faa00c7795d in KDirModelPrivate::_k_slotDeleteItems(KFileItemList const&) kio/src/widgets/kdirmodel.cpp:631:12 #7 0x7faa00c85765 in KDirModel::setDirLister(KDirLister*)::$_2::operator()(KFileItemList const&) const kio/src/widgets/kdirmodel.cpp:465:12 #8 0x7faa00c85765 in QtPrivate::FunctorCall, QtPrivate::List, void, KDirModel::setDirLister(KDirLister*)::$_2>::call(KDirModel::setDirLister(KDirLister*)::$_2&, void**) /usr/include/qt6/QtCore/qobjectdefs_impl.h:137:13 #9 0x7faa00c85765 in void QtPrivate::Functor::call, void>(KDirModel::setDirLister(KDirLister*)::$_2&, void*, void**) /usr/include/qt6/QtCore/qobjectdefs_impl.h:339:13 #10 0x7faa00c85765 in QtPrivate::QCallableObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) /usr/include/qt6/QtCore/qobjectdefs_impl.h:522:21 #11 0x7fa9fd790ca8 (/usr/lib/libQt6Core.so.6+0x190ca8) #12 0x7faa0030838c in KCoreDirLister::itemsDeleted(KFileItemList const&) kio/src/core/KF6KIOCore_autogen/include/moc_kcoredirlister.cpp:694:5 #13 0x7faa0030838c in KCoreDirListerPrivate::emitItemsDeleted(KFileItemList const&) kio/src/core/kcoredirlister.cpp:2520:19 #14 0x7faa002fcc92 in KCoreDirListerCache::itemsDeleted(QList const&, KFileItemList const&) kio/src/core/kcoredirlister.cpp:1900:17 #15 0x7faa002fc5d2 in KCoreDirListerCache::slotFilesRemoved(QList const&) kio/src/core/kcoredirlister.cpp:848:13 #16 0x7faa002dd5f1 in KCoreDirListerCache::slotFilesRemoved(QList const&) kio/src/core/kcoredirlister.cpp:798:5 #17 0x7faa0032ceb3 in QtPrivate::FunctorCall, QtPrivate::List const&>, void, void (KCoreDirListerCache::*)(QList const&)>::call(void (KCoreDirListerCache::*)(QList const&), KCoreDirListerCache*, void**) /usr/include/qt6/QtCore/qobjectdefs_impl.h:145:13 #18 0x7faa0032ceb3 in void QtPrivate::FunctionPointer const&)>::call const&>, void>(void (KCoreDirListerCache::*)(QList const&), KCoreDirListerCache*, void**) /usr/include/qt6/QtCore/qobjectdefs_impl.h:182:13 #19 0x7faa0032ceb3 in QtPrivate::QCallableObject const&), QtPrivate::List const&>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) /usr/include/qt6/QtCore/qobjectdefs_impl.h:520:21 #20 0x7fa9fd790ca8 (/usr/lib/libQt6Core.so.6+0x190ca8) #21 0x7faa0039cc34 in OrgKdeKDirNotifyInterface::FilesRemoved(QList const&) kio/src/core/KF6KIOCore_autogen/include/moc_kdirnotify.cpp:343:5 #22 0x7faa0039cc34 in OrgKdeKDirNotifyInterface::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) kio/src/core/KF6KIOCore_autogen/include/moc_kdirnotify.cpp:208:21 #23 0x7faa0039dc6d in OrgKdeKDirNotifyInterface::qt_metacall(QMetaObject::Call, int, void**) kio/src/core/KF6KIOCore_autogen/include/moc_kdirnotify.cpp:294:13 #24 0x7fa9fed860cd (/usr/lib/libQt6DBus.so.6+0x390cd) #25 0x7fa9fd77c2c6 in QObject::event(QEvent*) (/usr/lib/libQt6Core.so.6+0x17c2c6) #26 0x7fa9fe6f438a in QApplicationPrivate::notify_helper(QObject*, QEvent*) (/usr/lib/libQt6Widgets.so.6+0xf438a) #27 0x7fa9fd739817 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/lib/libQt6Core.so.6+0x139817) #28 0x7fa9fd739b9a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (/usr/lib/libQt6Core.so.6+0x139b9a) #29 0x7fa9fd9758a3 (/usr/lib/libQt6Core.so.6+0x3758a3) #30 0x7fa9fbb0df68 (/usr/lib/libglib-2.0.so.0+0x59f68) #31 0x7fa9fbb6c3a6 (/usr/lib/libglib-2.0.so.0+0xb83a6) #32 0x7fa9fbb0c161 in g_main_context_iteration (/usr/lib/libglib-2.0.so.0+0x58161) #33 0x7fa9fd9739c3 in QEventDispatcherGlib::processEvents(QFlags) (/usr/lib/libQt6Core.so.6+0x3739c3) #34 0x7fa9fd743d6d in QEventLoop::exec(QFlags) (/usr/lib/libQt6Core.so.6+0x143d6d) #35 0x7fa9fe941de2 in QDialog::exec() (/usr/lib/libQt6Widgets.so.6+0x341de2) #36 0x7fa9f29450be in KDEPlatformFileDialogHelper::exec() plasma/plasma-integration/qt6/src/platformtheme/kdeplatformfiledialoghelper.cpp:352:15 #37 0x7fa9fe941ce4 in QDialog::exec()
[frameworks-kio] [Bug 484289] Crash upon saving when you delete newly created folder in file dialog
https://bugs.kde.org/show_bug.cgi?id=484289 Waqar Ahmed changed: What|Removed |Added Version|23.08.5 |git master Component|general |Open/save dialogs Product|kate|frameworks-kio Assignee|kwrite-bugs-n...@kde.org|kio-bugs-n...@kde.org CC||kdelibs-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 473472] Discover crashes in KNSResultsStream::setRequest() when refreshing updates
https://bugs.kde.org/show_bug.cgi?id=473472 yuraposta...@proton.me changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #26 from yuraposta...@proton.me --- OK I looked into Bug 484332 and after updating my Arch knewstuff package the issue was also fixed for me as well. Sry for changing the bug status. -- You are receiving this mail because: You are watching all bug changes.
