[systemsettings] [Bug 436627] Mouse gestures don't work in Wayland
https://bugs.kde.org/show_bug.cgi?id=436627 --- Comment #6 from george fb --- Here's a Wayfire (Wayland compositor) plugin https://github.com/dkondor/wstroke (a port of easy stroke) that adds mouse gestures, maybe it helps in some way. Tested it on Fedora and it works. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 297003] Newly created text files are not empty
https://bugs.kde.org/show_bug.cgi?id=297003 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 453250] New: Restart after update is applied even if the update fails
https://bugs.kde.org/show_bug.cgi?id=453250 Bug ID: 453250 Summary: Restart after update is applied even if the update fails Product: Discover Version: master Platform: Neon Packages OS: Other Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: kishor...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY When updating software, there is a 'restart after applying updates' checkbox. This shuts down the computer even if the update fails (so that the user can't even read the error message). STEPS TO REPRODUCE 1. Open Discover 2. Go to the updates page 3. Start an update by clicking the 'update all' button at the top right. 4. Check the 'restart after applying updates' (not sure what the exact English text is, but it appears on the bottom left of the bar under the page that shows the list of updates) box at the bottom of the page that appears after the update has started 5. Before the update finishes downloading, disconnect from the internet OBSERVED RESULTS After some time, an error message is shown (title: Error applying updates; message: "There was an error applying the following updates. Please try again later") and the computer shuts down. EXPECTED RESULTS Computer should restart only if the update was successful. SOFTWARE VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-39-generic (64-bit) Graphics Platform: X11 Processors: 2 × AMD EPYC-Rome Processor Memory: 1.9 GiB of RAM Graphics Processor: virgl Manufacturer: QEMU Product Name: Standard PC (Q35 + ICH9, 2009) System Version: pc-q35-5.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 452820] Auto shutdown PC after Discover finished updates
https://bugs.kde.org/show_bug.cgi?id=452820 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453249] Face regions get lost when the file is renamed
https://bugs.kde.org/show_bug.cgi?id=453249 --- Comment #2 from Maik Qualmann --- The name of the image is a criterion for locating an externally moved image and for reassigning the corresponding DB metadata. It would be for us to consider whether we remove the name as a criterion (possibly also the modification date) and limit ourselves to file size and a unique hash. But your main problem is that you don't write any metadata in the image. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453249] Face regions get lost when the file is renamed
https://bugs.kde.org/show_bug.cgi?id=453249 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- First you should also enable writing of facel regions/metadata in the digiKam settings under Metadata. It is also recommended to do the renaming with digiKam. Maik -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 453162] Skanlite crash when scanning one or several selections
https://bugs.kde.org/show_bug.cgi?id=453162 Kåre Särs changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Kåre Särs --- Thanks for the report. This looks very much like a bug in the sane escl backend from the backtrace. Do you get the same crash with xsane? Br, Kåre -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453249] New: Face regions get lost when the file is renamed
https://bugs.kde.org/show_bug.cgi?id=453249 Bug ID: 453249 Summary: Face regions get lost when the file is renamed Product: digikam Version: 7.6.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Database-Faces Assignee: digikam-bugs-n...@kde.org Reporter: jader...@msn.com Target Milestone: --- SUMMARY Face regions are lost when the file is renamed. I suspect that the face region isn't stored in the metadata of the file itself (which I was really hoping that it would be). I'm glad that the people tag still exists for the picture, but if some grand child is looking at the picture decades from now, it would be good if whatever software they're using can point out who is who in the picture. STEPS TO REPRODUCE 1. Add a face tag to a picture. 2. Close digiKam 3. Rename picture 4. Reopen digiKam 5. Look for faces in renamed picture OBSERVED RESULT No faces are found EXPECTED RESULT The faces which were just tagged are still visible. SOFTWARE/OS VERSIONS Windows: 11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453153] Project plugin does not list externally created files
https://bugs.kde.org/show_bug.cgi?id=453153 Lothar changed: What|Removed |Added CC||loh@googlemail.com --- Comment #1 from Lothar --- I'm also not a fan of this view, but "it works as intended" . Look at https://invent.kde.org/utilities/kate and search in old issues/merge requests To achieve your expected behavior one would need to watch all directories and that can became quickly expensive. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453248] New: Path traversal bug when saving gradients
https://bugs.kde.org/show_bug.cgi?id=453248 Bug ID: 453248 Summary: Path traversal bug when saving gradients Product: krita Version: 5.0.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: xnagyti...@gmail.com Target Milestone: --- Created attachment 148484 --> https://bugs.kde.org/attachment.cgi?id=148484=edit Screen capture SUMMARY There's a path traversal bug when saving gradients in Krita. Krita doesn't sanitize the name field used for the file names of gradients, dropping files outside of the "$XDG_DATA_HOME/krita/gradients" directory. Similar to Bug 429925. I haven't tested it thoroughly but I have a feeling this bug may also be present with other resource types. (palettes, brushes, etc.) STEPS TO REPRODUCE 1. Create or open a new document 2. Gradients toolbar button -> Add... 3. Enter "../../../../test/abcd" as the name field 4. Click OK OBSERVED RESULT See attachment. EXPECTED RESULT Sanitize the name field before using it as a file name. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435528] Specific filename for clip prevented editing the clip without warning
https://bugs.kde.org/show_bug.cgi?id=435528 Eric Jiang changed: What|Removed |Added CC||erji...@alumni.iu.edu --- Comment #8 from Eric Jiang --- I was able to add and manipulate a PNG with that filename without any issues, using the latest master version. Was not able to reproduce this bug. (Ubuntu 20.04) -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 453228] Column "Name" is sorted alphabetically, not alphanumerically with no options to change it
https://bugs.kde.org/show_bug.cgi?id=453228 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 387969 *** -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 387969] Sort files in natural sorting, like dolphin ("1 file, 2 file", etc instead "1 file, 10 file, 11 file", etc)
https://bugs.kde.org/show_bug.cgi?id=387969 Patrick Silva changed: What|Removed |Added CC||hasez...@gmail.com --- Comment #4 from Patrick Silva --- *** Bug 453228 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453247] New: Paste into Active Layer and Paste at Cursor paste at the wrong locations
https://bugs.kde.org/show_bug.cgi?id=453247 Bug ID: 453247 Summary: Paste into Active Layer and Paste at Cursor paste at the wrong locations Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- git f866b153a4 SUMMARY In Krita 5.1, if the user copies/cuts a selection and then pastes it using "Paste into Active Layer", it will paste at the center of the canvas instead of the location it was cut from. This is annoying for some use cases such as cutting something from another layer onto another layer. Also, Paste at Cursor always seems to paste at some location nowhere near the cursor but instead to some location relative to it. These operations work as expected in Krita 5.0. Note: this is with Plasma's clipboard manager Klipper. STEPS TO REPRODUCE 1. Cut a selected area of a painting. 2. Paste into Active Layer. 1. Cut a selected area of a painting. 2. Paste at Cursor using the shortcut. OBSERVED RESULT They aren't pasted where the user would expect. EXPECTED RESULT These actions should work like they did in 5.0 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.12.12 (appimage) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 452691] [Bluetooth - Bluedevil] PS4 / Dual Shock 4 Controller Crashed kded5
https://bugs.kde.org/show_bug.cgi?id=452691 nekone...@protonmail.ch changed: What|Removed |Added Keywords||needs_verification Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 452691] [Bluetooth - Bluedevil] PS4 / Dual Shock 4 Controller Crashed kded5
https://bugs.kde.org/show_bug.cgi?id=452691 nekone...@protonmail.ch changed: What|Removed |Added Platform|unspecified |Archlinux Packages OS|Microsoft Windows |Linux --- Comment #2 from nekone...@protonmail.ch --- @Dave Excuse me, but can you not hi-jack my bug report for something completely unrelated? Make your own report, please. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 453137] Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect again
https://bugs.kde.org/show_bug.cgi?id=453137 --- Comment #2 from Michael Braxner --- Yah, I actually managed to mangle the logs ... wouldn't you know it. Trying again ... 4/30/22 7:33 PM kernel input: Nat's Flex (AVRCP) as /devices/virtual/input/input31 4/30/22 7:33 PM systemd-logind Watching system buttons on /dev/input/event19 (Nat's Flex (AVRCP)) 4/30/22 7:33 PM bluetoothd /org/bluez/hci0/dev_A8_91_3D_DF_A8_F4/fd3: fd(43) ready 4/30/22 7:33 PM rtkit-daemonSupervising 0 threads of 0 processes of 0 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8884 of process 3426 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Failed with result 'signal'. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM acpid input device has been disconnected, fd 20 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. 4/30/22 7:33 PM systemd Stopped Sound Service. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM systemd Starting Sound Service... 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8889 of process 8889 owned by '1000' high priority at nice level -11. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM pulseaudio Stale PID file, overwriting. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8890 of process 8889 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 2 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSupervising 2 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8891 of process 8889 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 3 threads of 1 processes of 1 users. 4/30/22 7:33 PM systemd Started Sound Service. 4/30/22 7:33 PM pulseaudio Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)? 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSink/sbc 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSource/sbc 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSink/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSource/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSink/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSource/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSink/sbc_xq_552 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Since I just don't know what I'm doing here, I can only guess that pulseaudio showing up killed just after the device turns up as an unregistered sender ... 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE ... is responsible for the observed problem, i.e. the disconnect, probably triggered when pulseaudio restarts ... 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. So it seems either an internal pulseaudio problem, or a problem triggered by the division by 0 in the bluetooth module ... 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] or some combination of the two. Any Ideas? -- You are receiving
[Powerdevil] [Bug 453139] Kubuntu 22.04, Battery widget shows laptop as connected to power source while running on battery
https://bugs.kde.org/show_bug.cgi?id=453139 --- Comment #2 from Michael Braxner --- Just to clarify: After a COLD boot WITH the power adapter plugged in, the described behaviour does NOT occur. A subsequent restart, suspend or hibernate, either with power supply plugged in or battery alone, does NOT lead to the behaviour described. After a COLD boot ON BATTERY ALONE, the behaviour occurs invariably, and is subsequently NOT remedied by a RESTART WITH power adapter plugged in. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 453224] Nothing happens when I click on 'Next' button
https://bugs.kde.org/show_bug.cgi?id=453224 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org --- Comment #1 from Harald Sitter --- Curious. Do you have output in your journal from around that time? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 453239] Get segmentation fault (core dumped) when starting Kstars on Kubuntu 22.04 with kubuntu-ppa/backports
https://bugs.kde.org/show_bug.cgi?id=453239 Alex Argiropoulos changed: What|Removed |Added CC||alkin...@gmail.com --- Comment #1 from Alex Argiropoulos --- Confirmed on a fresh 22.04 installation. Bombs immediately, even 'kstars --version'. Probably won't help due to missing debug symbols but here is the backtrace. Thread 1 "kstars" received signal SIGSEGV, Segmentation fault. 0x7529927e in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 (gdb) bt #0 0x7529927e in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7563c046 in QGuiApplication::screenAdded(QScreen*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #2 0x756217c0 in QWindowSystemInterface::handleScreenAdded(QPlatformScreen*, bool) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #3 0x7fffef8f0528 in QXcbConnection::initializeScreens() () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fffef8c7680 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #5 0x7fffef8cadb0 in QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #6 0x77fb7523 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so #7 0x756405ef in QGuiApplicationPrivate::createPlatformIntegration() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x75641c08 in QGuiApplicationPrivate::createEventDispatcher() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #9 0x75268b07 in QCoreApplicationPrivate::init() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x75644b70 in QGuiApplicationPrivate::init() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x75d58ced in QApplicationPrivate::init() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x55716b6c in ?? () #13 0x747efd90 in __libc_start_call_main (main=main@entry=0x55716b00, argc=argc@entry=1, argv=argv@entry=0x7fffe208) at ../sysdeps/nptl/libc_start_call_main.h:58 #14 0x747efe40 in __libc_start_main_impl (main=0x55716b00, argc=1, argv=0x7fffe208, init=, fini=, rtld_fini=, stack_end=0x7fffe1f8) at ../csu/libc-start.c:392 #15 0x55762785 in ?? () -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453246] New: When I tried to draw on the canvas, it wouldn't really let me. So I closed the canvas and tried again, and the pen pressure did not work. So I closed the window and it worked
https://bugs.kde.org/show_bug.cgi?id=453246 Bug ID: 453246 Summary: When I tried to draw on the canvas, it wouldn't really let me. So I closed the canvas and tried again, and the pen pressure did not work. So I closed the window and it worked. The reason I'm bringing it up is because this happens a lot. Product: krita Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: gladysredr...@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. draw with mouse 2. attempt to draw with tablet pen 3. close the canvas/window 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.
[kate] [Bug 453175] No button and option "Show whitespace"
https://bugs.kde.org/show_bug.cgi?id=453175 --- Comment #6 from Eric Armbruster --- > In the settings there is the option to show some white space indicator. That > would I assume cover this. This is not sufficient, I think. I just checked on Windows what Notepad++ actually does. It has different visualizations for all white space characters. e.g. tabs are visualized as -> and spaces as a dot (as is currently) and even \r\n is visualized differently. https://metadataconsulting.blogspot.com/2019/06/Notepad-Control-Characters-Explained.html -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444335] Sticky keys does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=444335 --- Comment #4 from Nick W --- This bug unfortunately makes KDE completely unusable under Wayland for those that need this feature. Given that a number of major distros are pushing to make Wayland default, I'm hoping to draw attention to it before that happens. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453152] Kate crashed during session restore
https://bugs.kde.org/show_bug.cgi?id=453152 Christoph Cullmann changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |ities/kate/commit/593857184 |ities/kate/commit/3414b6269 |c8799c281c519cb0e45517c60bb |a616a0dee4237f66e2669ee |ac52|59ff --- Comment #3 from Christoph Cullmann --- Git commit 3414b6269a616a0dee4237f66e2669ee59ff by Christoph Cullmann. Committed on 30/04/2022 at 21:57. Pushed by cullmann into branch 'release/22.04'. no delayed readSessionConfig the config pointer might be invalid at that point in time if we want to delay stuff, that must be done inside readSessionConfig in the KTextEditor::View itself, after reading the stuff from the passed config M +5-21 kate/kateviewspace.cpp https://invent.kde.org/utilities/kate/commit/3414b6269a616a0dee4237f66e2669ee59ff -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453152] Kate crashed during session restore
https://bugs.kde.org/show_bug.cgi?id=453152 Christoph Cullmann changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/kate/commit/593857184 ||c8799c281c519cb0e45517c60bb ||ac52 --- Comment #2 from Christoph Cullmann --- Git commit 593857184c8799c281c519cb0e45517c60bbac52 by Christoph Cullmann. Committed on 30/04/2022 at 21:42. Pushed by cullmann into branch 'master'. no delayed readSessionConfig the config pointer might be invalid at that point in time if we want to delay stuff, that must be done inside readSessionConfig in the KTextEditor::View itself, after reading the stuff from the passed config M +5-21 apps/lib/kateviewspace.cpp https://invent.kde.org/utilities/kate/commit/593857184c8799c281c519cb0e45517c60bbac52 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453152] Kate crashed during session restore
https://bugs.kde.org/show_bug.cgi?id=453152 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Christoph Cullmann --- Ok, I think that is because we try to delay the session restore. That will not work as the pointers might be invalid later :( -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368284] There are spaces between the Arab characters and the edges of the characters are not Smooth.
https://bugs.kde.org/show_bug.cgi?id=368284 --- Comment #21 from Cristiano Guadagnino --- (In reply to emohr from comment #19) > Do you get this crash rendering with the AppImage? It looks like MLT is not > on the minimum version needed (version 7.0 or newer). Yes, I got the crash with the AppImage > If you rendered with the AppImage please check if the paths are set correct. > Goto settings -> configure Kdenlive -> environment. See the settings for the > AppImage here: > https://docs.kdenlive.org/de/user_interface/menu/settings_menu/ > configure_kdenlive.html#mlt-environment My settings are the same as those indicated in the link you posted, but for the melt executable. The link you posted indicates /usr/local/bin/melt-7, mine is /usr/bin/melt (which is a symlink to /usr/bin/melt-7). See attached screenshot in Comment 20. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368284] There are spaces between the Arab characters and the edges of the characters are not Smooth.
https://bugs.kde.org/show_bug.cgi?id=368284 --- Comment #20 from Cristiano Guadagnino --- Created attachment 148483 --> https://bugs.kde.org/attachment.cgi?id=148483=edit kdenlive appimage settings -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 367719] Error login in to Dropbox
https://bugs.kde.org/show_bug.cgi?id=367719 Amir Khan changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||ak2022...@gmail.com --- Comment #2 from Amir Khan --- *** This bug has been marked as a duplicate of bug 333520 *** -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 333520] Unable to add Dropbox storage in 4.13.0
https://bugs.kde.org/show_bug.cgi?id=333520 Amir Khan changed: What|Removed |Added CC||axel.br...@gmx.de --- Comment #17 from Amir Khan --- *** Bug 367719 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 333520] Unable to add Dropbox storage in 4.13.0
https://bugs.kde.org/show_bug.cgi?id=333520 Amir Khan changed: What|Removed |Added CC||d...@cording.id.au --- Comment #16 from Amir Khan --- *** Bug 349441 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 349441] Unable to authorise for Dropbox - User limit reached.
https://bugs.kde.org/show_bug.cgi?id=349441 Amir Khan changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||ak2022...@gmail.com --- Comment #11 from Amir Khan --- *** This bug has been marked as a duplicate of bug 333520 *** -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 349441] Unable to authorise for Dropbox - User limit reached.
https://bugs.kde.org/show_bug.cgi?id=349441 Amir Khan changed: What|Removed |Added CC||onelove.nyahbi...@gmail.com --- Comment #10 from Amir Khan --- *** Bug 360627 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 360627] Adding Dropbox account gives: This app has reached its user limit
https://bugs.kde.org/show_bug.cgi?id=360627 Amir Khan changed: What|Removed |Added CC||ak2022...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Amir Khan --- *** This bug has been marked as a duplicate of bug 349441 *** -- You are receiving this mail because: You are watching all bug changes.
[sweeper] [Bug 410404] sweeper app should sweepe historic for some kde natives applications
https://bugs.kde.org/show_bug.cgi?id=410404 Amir Khan changed: What|Removed |Added Severity|normal |wishlist CC||ak2022...@gmail.com --- Comment #1 from Amir Khan --- Importance field, second attribute set to "wishlist" -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453175] No button and option "Show whitespace"
https://bugs.kde.org/show_bug.cgi?id=453175 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Severity|normal |wishlist --- Comment #5 from Christoph Cullmann --- In the settings there is the option to show some white space indicator. That would I assume cover this. There is no explicit button to enable that in the menu. Not that sure if that really is an often changed feature to put there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453245] New: Touchpad settings override mouse settings
https://bugs.kde.org/show_bug.cgi?id=453245 Bug ID: 453245 Summary: Touchpad settings override mouse settings Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Touchpad Assignee: plasma-b...@kde.org Reporter: dakkudu...@tozya.com Target Milestone: 1.0 SUMMARY On boot, the mouse does not use its settings, and instead use the trackpad one. This issue did not appear in Kubuntu 21.10. STEPS TO REPRODUCE 1. Boot the system 2. Use the mouse OBSERVED RESULT The mouse is using the trackpad sensitivity settings. Going into the mouse settings and applying the sensitivity again fix the issue. EXPECTED RESULT The mouse and the trackpads settings get correctly applied to each other at startup SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.24.4 Qt Version: 5.15.3 ADDITIONAL INFORMATION The machine that is used is a Lenovo Legion 5 15ACH6H, using the integrated touchpad, and the mouse used is a Logitech MX Master 3, in bluetooth mode. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453244] 7.6.0 Appimage crashes on Ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453244 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.7.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Bug has already been reported and the current Ubuntu version works with digiKam-7.7.0. Read this bug report: Bug 453231 Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451386] Black Screen with Movable Cursor after Screens Resume from Sleep
https://bugs.kde.org/show_bug.cgi?id=451386 --- Comment #6 from Stephen Ackerman --- I'm wondering if this is possibly related to #453042 ? When kwin_wayland 5.24.5 makes it into Debian, I will re-test. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453244] New: 7.6.0 Appimage crashes on Ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453244 Bug ID: 453244 Summary: 7.6.0 Appimage crashes on Ubuntu 22.04 Product: digikam Version: 7.6.0 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Bundle-AppImage Assignee: digikam-bugs-n...@kde.org Reporter: eric.jaco...@free.fr Target Milestone: --- SUMMARY *** 7.6.0 Appimage crashes on Ubuntu 22.04 *** STEPS TO REPRODUCE 1. Run ./digiKam-7.6.0-x86-64.appimage 2. 3. OBSERVED RESULT -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so digikam: symbol lookup error: /lib/x86_64-linux-gnu/libgio-2.0.so.0: undefined symbol: g_module_open_full EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.04, fresh install (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION DK configured to use MySQL -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453243] New: Canvas projection often isn't updated properly after undoing/redoing
https://bugs.kde.org/show_bug.cgi?id=453243 Bug ID: 453243 Summary: Canvas projection often isn't updated properly after undoing/redoing Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- Created attachment 148482 --> https://bugs.kde.org/attachment.cgi?id=148482=edit Cutoff strokes are undoing/redoing git f866b153a4 SUMMARY In Krita 5.1, the canvas visual projection often isn't updated properly after undoing or redoing, leaving cutoff strokes. See attachment. This happens regardless of using the OpenGL canvas. This is not always reproducible. STEPS TO REPRODUCE 1. Draw a series of lines around the same spot, in 100% zoom 2. Undo lines OBSERVED RESULT The projection of the lines are often cutoff. EXPECTED RESULT The projection should accurately reflect the strokes after undo/redo. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.12.12 (appimage) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453242] kded5 keeps crashing in LocationUpdater::resetLocator() after upgrade
https://bugs.kde.org/show_bug.cgi?id=453242 --- Comment #1 from Kamil Dudka --- The cause is similar to bug #423864 comment #4: m_configWatcher->config() for some reason returns nullptr. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442654] Dragging a widget across screens drops the widget
https://bugs.kde.org/show_bug.cgi?id=442654 r0y changed: What|Removed |Added Version|git-master |5.24.4 CC||myr...@gmx.com Platform|Other |Kubuntu Packages --- Comment #3 from r0y --- I just installed a fresh Kubuntu 22.04 and the issue is still there. Sometimes, if I am very fast dragging it, it semi-shows up. It has also crashed plasmashell, so it's not something I would want to do too often. Event Calendar, as a widget, seems to handle it better than most (not sure if I am just lucky or if this even helps). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453242] New: kded5 keeps crashing in LocationUpdater::resetLocator() after upgrade
https://bugs.kde.org/show_bug.cgi?id=453242 Bug ID: 453242 Summary: kded5 keeps crashing in LocationUpdater::resetLocator() after upgrade Product: plasmashell Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Night Color Assignee: plasma-b...@kde.org Reporter: kdu...@redhat.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. I updated my Gentoo Linux machines with KDE to latest stable versions of everything. OBSERVED RESULT Suddenly nm-applet stopped working and kded5 keeps crashing approx. once per second: Apr 30 21:38:18 b360 kded5[72702]: Installing the delayed initialization callback. Apr 30 21:38:18 b360 NetworkManager[2047]: [1651347498.1476] agent-manager: agent[9abe7988027e87ba,:1.1684/org.kde.plasma.networkmanagement/1026]: agent registered Apr 30 21:38:18 b360 systemd-coredump[72705]: elfutils disabled, parsing ELF objects not supported Apr 30 21:38:18 b360 systemd-coredump[72705]: [] Process 72675 (kded5) of user 1026 dumped core. Apr 30 21:38:18 b360 systemd[1]: systemd-coredump@1617-72703-0.service: Deactivated successfully. Apr 30 21:38:18 b360 kded5[72702]: kcm_touchpad: Using X11 backend Apr 30 21:38:18 b360 kded5[72702]: kf.config.core: Use of KConfigWatcher without DBus support. You will not receive updates Apr 30 21:38:19 b360 systemd[1]: Started Process Core Dump (PID 72728/UID 0). Apr 30 21:38:19 b360 systemd-coredump[72730]: Removed old coredump core.kded5.1026.d127f538c70549308c91f1781604c632.5497.165134278100.zst. EXPECTED RESULT No crashes after update to stable release. SOFTWARE/OS VERSIONS Linux: 5.15.32-gentoo-r1-x86_64 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION (gdb) bt #0 0x7fe9d156a06c in () at /lib64/libc.so.6 #1 0x7fe9d151e792 in raise () at /lib64/libc.so.6 #2 0x7fe9d256985c in KCrash::defaultCrashHandler(int) () at /usr/lib64/libKF5Crash.so.5 #3 0x7fe9d151e830 in () at /lib64/libc.so.6 #4 KConfigBase::isGroupImmutable(QByteArray const&) const (this=0x0, aGroup=...) at /var/tmp/portage/kde-frameworks/kconfig-5.92.0/work/kconfig-5.92.0/src/core/kconfigbase.cpp:78 #5 0x7fe9d1f175f8 in KConfigGroupPrivate::KConfigGroupPrivate(QExplicitlySharedDataPointer const&, QByteArray const&) (name=..., owner=..., this=0x563740d6fe80) at /usr/include/qt5/QtCore/qshareddata.h:161 #6 KConfigGroup::KConfigGroup(QExplicitlySharedDataPointer const&, QString const&) (this=this@entry=0x7ffefe2c2c30, master=..., _group=...) at /var/tmp/portage/kde-frameworks/kconfig-5.92.0/work/kconfig-5.92.0/src/core/kconfiggroup.cpp:491 #7 0x7fe9c4012764 in LocationUpdater::resetLocator() (this=0x563740d58cf0) at /var/tmp/portage/kde-plasma/plasma-workspace-5.24.4/work/plasma-workspace-5.24.4/libcolorcorrect/kded/locationupdater.cpp:28 #8 0x7fe9c4012ffa in KPluginFactory::createInstance(QWidget*, QObject*, QList const&) (parentWidget=, parent=, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:875 #9 0x7fe9d1e99272 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) (this= 0x563740cc8150, iface=0x7fe9d2586360 "KDEDModule", parentWidget=0x0, parent=0x563740af2930, args=..., keyword=...) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.92.0/work/kcoreaddons-5.92.0/src/lib/plugin/kpluginfactory.cpp:232 #10 0x56374098a0c0 in () #11 0x56374098d0b2 in () #12 0x56374098d443 in () #13 0x56374098712a in () #14 0x7fe9d150a2fa in () at /lib64/libc.so.6 #15 0x7fe9d150a3a8 in __libc_start_main () at /lib64/libc.so.6 #16 0x563740987541 in () I do not need NightColor. If I comment out the body of LocationUpdater::resetLocator(), kded5 no longer crashes and everything seems to work as expected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453241] New: KDE Plasma Display Settings Crashes w/ upstream MESA
https://bugs.kde.org/show_bug.cgi?id=453241 Bug ID: 453241 Summary: KDE Plasma Display Settings Crashes w/ upstream MESA Product: systemsettings Version: 5.24.4 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bluestang2...@gmail.com Target Milestone: --- Application: systemsettings (5.24.4) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.17.4-200.fc35.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 35 (KDE Plasma) DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I built MESA radeonsi and radv drivers only for my 6800XT to update my copr - https://copr.fedorainfracloud.org/coprs/bluestang2006/mesa/ and now getting this crash accessing KDE Plasma desktop utilities. Reverting my copr and going to the default mesa drivers provided fixes the issue. I have not ran into this issue before until yesterday, when I compiled MESA main to update about a week old prior build. - Custom settings of the application: Custom build radeonsi and radv drivers as per my copr here - https://copr.fedorainfracloud.org/coprs/bluestang2006/mesa/build/4351293/ The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 0x7f7bd545c54c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7f7bd540fcf6 in raise () from /lib64/libc.so.6 #6 0x7f7bd53e2813 in abort () from /lib64/libc.so.6 #7 0x7f7bd53e273b in __assert_fail_base.cold () from /lib64/libc.so.6 #8 0x7f7bd5408c46 in __assert_fail () from /lib64/libc.so.6 #9 0x7f7bb329e78e in deserialize_glsl_program.part () from /usr/lib64/dri/radeonsi_dri.so #10 0x7f7bb2f778c4 in _mesa_ProgramBinary () from /usr/lib64/dri/radeonsi_dri.so #11 0x7f7bd62ff213 in QOpenGLProgramBinaryCache::setProgramBinary(unsigned int, unsigned int, void const*, unsigned int) () from /lib64/libQt5Gui.so.5 #12 0x7f7bd62fffc8 in QOpenGLProgramBinaryCache::load(QByteArray const&, unsigned int) () from /lib64/libQt5Gui.so.5 #13 0x7f7bd62d538d in QOpenGLShaderProgramPrivate::linkBinary() () from /lib64/libQt5Gui.so.5 #14 0x7f7bd62e9ed2 in QOpenGLTextureGlyphCache::resizeTextureData(int, int) () from /lib64/libQt5Gui.so.5 #15 0x7f7bd6269583 in QTextureGlyphCache::fillInPendingGlyphs() () from /lib64/libQt5Gui.so.5 #16 0x7f7bd492d6a0 in QSGDefaultGlyphNode::update() () from /lib64/libQt5Quick.so.5 #17 0x7f7bd49b8f67 in QQuickTextNode::addGlyphs(QPointF const&, QGlyphRun const&, QColor const&, QQuickText::TextStyle, QColor const&, QSGNode*) () from /lib64/libQt5Quick.so.5 #18 0x7f7bd49c82d8 in QQuickTextNodeEngine::addToSceneGraph(QQuickTextNode*, QQuickText::TextStyle, QColor const&) () from /lib64/libQt5Quick.so.5 #19 0x7f7bd49b6062 in QQuickTextNode::addTextLayout(QPointF const&, QTextLayout*, QColor const&, QQuickText::TextStyle, QColor const&, QColor const&, QColor const&, QColor const&, int, int, int, int) () from /lib64/libQt5Quick.so.5 #20 0x7f7bd49bf6b5 in QQuickText::updatePaintNode(QSGNode*, QQuickItem::UpdatePaintNodeData*) () from /lib64/libQt5Quick.so.5 #21 0x7f7bd49a9aa8 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) () from /lib64/libQt5Quick.so.5 #22 0x7f7bd49aa252 in QQuickWindowPrivate::updateDirtyNodes() () from /lib64/libQt5Quick.so.5 #23 0x7f7bd4997a79 in QQuickWindowPrivate::syncSceneGraph() () from /lib64/libQt5Quick.so.5 #24 0x7f7bd4a23fcd in QQuickRenderControl::sync() () from /lib64/libQt5Quick.so.5 #25 0x7f7bd3733c21 in QQuickWidgetPrivate::render(bool) () from /lib64/libQt5QuickWidgets.so.5 #26 0x7f7bd66a78fc in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #27 0x7f7bd6664443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #28 0x7f7bd5a867d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #29 0x7f7bd669ed16 in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) () from /lib64/libQt5Widgets.so.5 #30 0x7f7bd66a3797 in QWidgetPrivate::show_helper() () from /lib64/libQt5Widgets.so.5 #31 0x7f7bd66a6973 in QWidgetPrivate::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #32 0x7f7bd66a3719 in QWidgetPrivate::showChildren(bool) () from /lib64/libQt5Widgets.so.5 #33 0x7f7bd66a37b3 in QWidgetPrivate::show_helper() () from /lib64/libQt5Widgets.so.5 #34 0x7f7bd66a6973 in QWidgetPrivate::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #35 0x7f7bd66a3719 in QWidgetPrivate::showChildren(bool) () from /lib64/libQt5Widgets.so.5 #36 0x7f7bd66a37b3 in QWidgetPrivate::show_helper() () from
[kate] [Bug 453175] No button and option "Show whitespace"
https://bugs.kde.org/show_bug.cgi?id=453175 --- Comment #4 from Dariusz Tereszkiewicz --- I mean one button that would show or hide all types of whitespace in a text file. Such a button is available, for example, in the Notepadqq editor and LibreOffice Writer. Of course, it could be an extra button that I add manually to the toolbar and to which I manually add an icon. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435768] Difficulties creating titles with non-BMP characters
https://bugs.kde.org/show_bug.cgi?id=435768 Eric Jiang changed: What|Removed |Added CC||erji...@alumni.iu.edu --- Comment #2 from Eric Jiang --- Using kdenlive master from a couple weeks ago, I was able to create a title with "testɐﾧ test" successfully and confirmed that it was saved in the project XML as UTF-8 properly. However, opening the project XML caused the non-BMP characters to be lost. In kdenlivedoc.cpp:147, removing the line impl.setInvalidDataPolicy(QDomImplementation::DropInvalidChars); lets me save and open project files with the example string Andy provided. It was originally added in f7d6026d but not clear what specific problem led to it (mantis no longer online). Someone more knowledgeable than me should weigh in on how risky it is to change the InvalidDataPolicy. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 453240] New: kmail not downloading emails immediately on launch
https://bugs.kde.org/show_bug.cgi?id=453240 Bug ID: 453240 Summary: kmail not downloading emails immediately on launch Product: kmail2 Version: 5.20.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bingmyb...@btinternet.com Target Milestone: --- STEPS TO REPRODUCE 1. launch kmail 2. 3. OBSERVED RESULT Kmail loads but does not start downloading emails until the "check emails" delay has timed out EXPECTED RESULT Kmail to start downloading emails immediately on launch SOFTWARE/OS VERSIONS opensuse:tumbleweed:20220426 Qt: 5.15.2 KDE Frameworks: 5.93.0 - KDE Plasma: 5.24.4 - kwin 5.24.4 kmail2 5.20.0 (22.04.0) - akonadiserver 5.20.0 (22.04.0) - Kernel: 5.17.4-1-default ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 452978] URL parsing broken if URL includes port number (or address is IPv6)
https://bugs.kde.org/show_bug.cgi?id=452978 ninj...@gmail.com changed: What|Removed |Added CC||ninj...@gmail.com --- Comment #2 from ninj...@gmail.com --- The offending commit would be https://invent.kde.org/utilities/konsole/-/commit/1ee8c64b5189d9e32ae9660308b2edc0f35ea6f0 As to what the proper regex should be, the syntax for URIs is specified at https://datatracker.ietf.org/doc/html/rfc3986#appendix-A, with augmented BNF rules as defined in https://datatracker.ietf.org/doc/html/rfc2234 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 304722] Kopete 1.3.0 crashes when opening a group chat window (XMPP protocol)
https://bugs.kde.org/show_bug.cgi?id=304722 --- Comment #5 from barr...@gmail.com --- If of any use, these are the last lines when I ran Kopete from the console. Trimming everything before, as up to that point everything was working fine. Invalid Context= "UI" line for icon theme: "/usr/share/icons/Adwaita/96x96/ui/" Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/256x256/legacy/" Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/512x512/legacy/" Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/scalable/legacy/" Invalid Context= "UI" line for icon theme: "/usr/share/icons/Adwaita/scalable/ui/" kf5.kxmlgui: cannot find .rc file "historychatui.rc" for component "kopete" addGroup "No está en su lista de contactos" KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kopete path = /usr/bin pid = 767653 KCrash: Arguments: /usr/bin/kopete KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 304722] Kopete 1.3.0 crashes when opening a group chat window (XMPP protocol)
https://bugs.kde.org/show_bug.cgi?id=304722 --- Comment #4 from barr...@gmail.com --- Created attachment 148481 --> https://bugs.kde.org/attachment.cgi?id=148481=edit New crash information added by DrKonqi kopete (1.13.0) using Qt 5.12.8 - What I was doing when the application crashed: hovering over my contact list. - Custom settings of the application: XMPP account at disroot server; my account has a group chat active, as far as I know, this was a known bug a long ago. -- Backtrace (Reduced): #10 0x7f901028e06e in JabberClient::groupChatPresence(XMPP::Jid const&, XMPP::Status const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kopete_jabber.so [...] #23 0x7f9020c02c2a in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f90215faa66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f90216040f0 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f9020bd680a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 304722] Kopete 1.3.0 crashes when opening a group chat window (XMPP protocol)
https://bugs.kde.org/show_bug.cgi?id=304722 barr...@gmail.com changed: What|Removed |Added CC||barr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 453237] kmail/kontakt crash when navigate in filter dialog or add new filter
https://bugs.kde.org/show_bug.cgi?id=453237 filip changed: What|Removed |Added Component|general |mail Version|unspecified |5.20.0 --- Comment #2 from filip --- Description from original BUG 452416: I have more than one filters to delete spam mails from spam folder. Already configured filters work without any problems. When i try to enter a new filter rule e.g. "From" contains "xyz.com" with Filter action "Delete" kmail crashes always. New: Also the navigation through the mail filter definitions crashes the Applikation -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 453239] Get segmentation fault (core dumped) when starting Kstars on Kubuntu 22.04 with kubuntu-ppa/backports
https://bugs.kde.org/show_bug.cgi?id=453239 Otto changed: What|Removed |Added CC||ofba...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 453239] New: Get segmentation fault (core dumped) when starting Kstars on Kubuntu 22.04 with kubuntu-ppa/backports
https://bugs.kde.org/show_bug.cgi?id=453239 Bug ID: 453239 Summary: Get segmentation fault (core dumped) when starting Kstars on Kubuntu 22.04 with kubuntu-ppa/backports Product: kstars Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: ofba...@hotmail.com Target Milestone: --- SUMMARY Kstars do not work under Kubuntu 22.04 with kubuntu-ppa/backports Latest patches deployed as 30-APR-2022 STEPS TO REPRODUCE 1. Running Kubuntu 22.04 with kubuntu-ppa/backports 2. From command line execute kstars 3. Crash: segmentado fault (core dumped) OBSERVED RESULT My system by default uses spanish, so I get this: supersu@mac2:~$ kstars Violación de segmento (`core' generado) Translated to English: Segmentation fault (core dumped) EXPECTED RESULT kstars to start SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KStars - Kubuntu 22.04 LTS x86_64 with kubuntu-ppa/backports (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93 Qt Version: 5.15.3 ADDITIONAL INFORMATION Kernel 5.15.0-27 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 453238] New: Button size with icon is bigger than just text
https://bugs.kde.org/show_bug.cgi?id=453238 Bug ID: 453238 Summary: Button size with icon is bigger than just text Product: frameworks-plasma Version: 5.93.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: components Assignee: plasma-b...@kde.org Reporter: doncb...@gmail.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: --- Created attachment 148480 --> https://bugs.kde.org/attachment.cgi?id=148480=edit Virtual Keyboard button on left is taller SUMMARY In SDDM, the virtual keyboard button appears larger than the sessions button and keyboard layout button. The virtual keyboard button seems to become bigger when an icon is present with no way to adjust it. STEPS TO REPRODUCE 1. Run `sddm-greeter --test-mode --theme /usr/share/sddm/themes/breeze/` 2. Hover over the Virtual Keyboard and the Session or Layout button 3. OBSERVED RESULT Virtual Keyboard is taller EXPECTED RESULT Virtual Keyboard is equal with the rest SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Graphics Platform: X11 ADDITIONAL INFORMATION I believe the PlasmaComponents3 button is to blame -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 453237] kmail/kontakt crash when navigate in filter dialog or add new filter
https://bugs.kde.org/show_bug.cgi?id=453237 --- Comment #1 from filip --- Original reported in BUG 452416 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 452416] kmail crash when add new filter rule
https://bugs.kde.org/show_bug.cgi?id=452416 --- Comment #2 from filip --- (In reply to filip from comment #1) > Same Problem with the new framework and Applikation Version > See BUG report 543237 (sorry... drkonqi has created a new BUG report) New BUG report => 453237 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 452416] kmail crash when add new filter rule
https://bugs.kde.org/show_bug.cgi?id=452416 --- Comment #1 from filip --- Same Problem with the new framework and Applikation Version See BUG report 543237 (sorry... drkonqi has created a new BUG report) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 452348] Opaque plasmoidheading.svg not used even when assets are present
https://bugs.kde.org/show_bug.cgi?id=452348 --- Comment #6 from Niccolò Venerandi --- (In reply to doncbugs from comment #5) > Hmmm, I suppose I saw this coming when the introduction of opaque (solid?) > did not support all plasmoid backgrounds. Wait, no, plasmoid backgrounds *do* become opaque (solid) when a window is maximized (or, at least, they should). The issue is that whilst plasmoid backgrounds are declared in just one place for all of them it's really easy to change it just there. Whereas for PlasmoidHeading, I can only think of needing some custom code for each applet that uses it. > Is it out of the question to > design panels that properly support the different asset sets for Plasma 6 > now that we have an idea of how things might be customized? You gotta ask Marco Martin on this one; I have no idea. He knows all of the API much, much better than me. > I don't understand these 2 ideas. The fallback is generally the default > widgets/ items, so I can't see any harm in it. Not to mention, I'm pretty > sure it's just copy and paste the default one to ship something. What I meant is: we do not encourage third party themes to use custom svgs in the solid/ folder; right now we only support the panel background as far as I know. So I would say: for now, consider solid/ to be a folder *only meant* for the panel background. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 453237] New: kmail/kontakt crash when navigate in filter dialog or add new filter
https://bugs.kde.org/show_bug.cgi?id=453237
Bug ID: 453237
Summary: kmail/kontakt crash when navigate in filter dialog or
add new filter
Product: kontact
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: v8fi...@gmail.com
Target Milestone: ---
Application: kontact (5.20.0 (22.04.0))
Qt Version: 5.15.2
Frameworks Version: 5.93.0
Operating System: Linux 5.17.4-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Navigate through "Filter" dialog or add new filter rule
Same problem as in BUG 452416 in the new Framework and Application Version
The crash can be reproduced every time.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __gnu_cxx::__atomic_add (__val=1, __mem=0x10009) at
/usr/include/c++/11/ext/atomicity.h:71
#7 __gnu_cxx::__atomic_add_dispatch (__val=1, __mem=0x10009) at
/usr/include/c++/11/ext/atomicity.h:111
#8 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_add_ref_copy
(this=0x10001) at /usr/include/c++/11/bits/shared_ptr_base.h:148
#9 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::__shared_count (__r=...,
this=0x7ffcb61238d8) at /usr/include/c++/11/bits/shared_ptr_base.h:712
#10 std::__shared_ptr::__shared_ptr (this=,
this=) at /usr/include/c++/11/bits/shared_ptr_base.h:1152
#11 std::shared_ptr::shared_ptr (this=0x7ffcb61238d0)
at /usr/include/c++/11/bits/shared_ptr.h:150
#12 MailCommon::SearchRuleWidgetLister::setRuleList (aList=0x5644db2bebe8,
this=0x5644db18b650) at
/usr/src/debug/mailcommon-22.04.0-1.1.x86_64/src/search/searchpatternedit.cpp:449
#13 MailCommon::SearchPatternEdit::setSearchPattern (this=0x5644db189ca0,
aPattern=0x5644db2bebe8) at
/usr/src/debug/mailcommon-22.04.0-1.1.x86_64/src/search/searchpatternedit.cpp:639
#14 0x7f72e7c5923f in MailCommon::KMFilterDialog::slotFilterSelected
(this=0x5644da815600, aFilter=0x5644db2bebe0) at
/usr/src/debug/mailcommon-22.04.0-1.1.x86_64/src/filter/kmfilterdialog.cpp:480
#15 0x7f7377bf7453 in QtPrivate::QSlotObjectBase::call (a=0x7ffcb6123ab0,
r=0x5644da815600, this=0x5644db287500) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate (sender=0x5644da017cf0, signal_index=10,
argv=0x7ffcb6123ab0) at kernel/qobject.cpp:3886
#17 0x7f7377bf07af in QMetaObject::activate
(sender=sender@entry=0x5644da017cf0, m=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcb6123ab0)
at kernel/qobject.cpp:3946
#18 0x7f72e7c25d9b in MailCommon::KMFilterListBox::filterSelected
(_t1=, this=0x5644da017cf0) at
/usr/src/debug/mailcommon-22.04.0-1.1.x86_64/build/src/KF5MailCommon_autogen/CSB7XD6IZM/moc_kmfilterlistbox.cpp:291
#19 MailCommon::KMFilterListBox::slotSelected (this=0x5644da017cf0, aIdx=5) at
/usr/src/debug/mailcommon-22.04.0-1.1.x86_64/src/filter/kmfilterlistbox.cpp:386
#20 0x7f7377bf7453 in QtPrivate::QSlotObjectBase::call (a=0x7ffcb6123bd0,
r=0x5644da017cf0, this=0x5644db17cc60) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#21 doActivate (sender=0x5644da6dd630, signal_index=23,
argv=0x7ffcb6123bd0) at kernel/qobject.cpp:3886
#22 0x7f7377bf07af in QMetaObject::activate
(sender=sender@entry=0x5644da6dd630, m=m@entry=0x7f7378cad4a0
, local_signal_index=local_signal_index@entry=8,
argv=argv@entry=0x7ffcb6123bd0) at kernel/qobject.cpp:3946
#23 0x7f7378a2e801 in QListWidget::currentRowChanged
(this=this@entry=0x5644da6dd630, _t1=) at
.moc/moc_qlistwidget.cpp:417
#24 0x7f7378a2f67b in QListWidgetPrivate::_q_emitCurrentItemChanged
(this=, current=..., previous=...) at
itemviews/qlistwidget.cpp:1236
#25 0x7f7377bf7488 in doActivate (sender=0x5644da6eaf30,
signal_index=4, argv=0x7ffcb6123d40) at kernel/qobject.cpp:3898
#26 0x7f7377bf07af in QMetaObject::activate
(sender=sender@entry=0x5644da6eaf30, m=m@entry=0x7f7377e94e60
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffcb6123d40)
at kernel/qobject.cpp:3946
#27 0x7f7377b6b653 in QItemSelectionModel::currentChanged
(this=this@entry=0x5644da6eaf30, _t1=..., _t2=...) at
.moc/moc_qitemselectionmodel.cpp:482
#28 0x7f7377b6f039 in QItemSelectionModel::setCurrentIndex
(this=0x5644da6eaf30, index=..., command=...) at
itemmodels/qitemselectionmodel.cpp:1416
#29 0x7f73789e5a13 in QAbstractItemView::mousePressEvent
(this=0x5644da6dd630, event=) at
itemviews/qabstractitemview.cpp:1786
#30 0x7f73787b3cde in QWidget::event (this=this@entry=0x5644da6dd630,
event=event@entry=0x7ffcb61243f0) at kernel/qwidget.cpp:9020
#31
[kdenlive] [Bug 453213] Too coarse tuning of output video quality, no audio quality setting
https://bugs.kde.org/show_bug.cgi?id=453213 thwr...@gmail.com changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 453236] New: When uninstalling an application, ask whether to delete the data
https://bugs.kde.org/show_bug.cgi?id=453236 Bug ID: 453236 Summary: When uninstalling an application, ask whether to delete the data Product: Discover Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: lei...@leinir.dk Reporter: emanu@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com Target Milestone: --- It is not a bug, but a request for functionality. Flatpak has a flag to uninstallation to delete application data: flatpak uninstall App --delete-data The advantage for the user is the saving of space on non usable data. On Gnome Software they have a Mackup: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/257 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 452348] Opaque plasmoidheading.svg not used even when assets are present
https://bugs.kde.org/show_bug.cgi?id=452348 --- Comment #5 from doncb...@gmail.com --- (In reply to Niccolò Venerandi from comment #4) > Generally speaking I'd agree this is something that should be achieved; > however, the "opaque?" flag, differently from "contrast effect on?" one, > depends on which panel we're currently talking about. This means that it's > practically impossible for all PlasmoidHeaders to use the solid/ style when > they are in a widget of a opaque panel, as they can't know in which panel > they are at all. Hmmm, I suppose I saw this coming when the introduction of opaque (solid?) did not support all plasmoid backgrounds. Is it out of the question to design panels that properly support the different asset sets for Plasma 6 now that we have an idea of how things might be customized? > Right now we *do not* ship with a PlasmoidHeading.svg inside of solid/. I > would close this as a WONTFIX. I don't understand these 2 ideas. The fallback is generally the default widgets/ items, so I can't see any harm in it. Not to mention, I'm pretty sure it's just copy and paste the default one to ship something. > (Interestingly enough though, we *do* ship tooltip and dialog background > svgs in solid, but those IIRC are not used anywhere either...) I'm fairly certain about never seeing tooltip function properly, but now I'm curious as to what is showing if the dialog background isn't being used. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452739] Outline drag previews for the rectangle and ellipse tools constantly stutter around from their actual effective position, especially at high zoom levels
https://bugs.kde.org/show_bug.cgi?id=452739 tomtomtomreportin...@gmail.com changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from tomtomtomreportin...@gmail.com --- The duplicate report was previously set to confirmed, so setting this report to confirmed. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 452225] Appchooser dialog cannot find Okular
https://bugs.kde.org/show_bug.cgi?id=452225 --- Comment #7 from Harald Sitter --- There's a flag that tells the xdg portal to invoke the impl even when otherwise not needed. That flag is not passed along as best I can tell. i.e. the application can explicitly ask for the dialog but we don't know whether that is the case (in which case we'd have to show the dialog) or not (which is when we could just return a value) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453231] Digikam does not work anymore after upgrading to ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453231 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.7.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453231] Digikam does not work anymore after upgrading to ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453231 --- Comment #2 from philippe.quag...@laposte.net --- Yes, the 7.7.0 pre-release works perfectly ! Many thanks, you saved my day. Best regards, and thanks again for this wonderful software. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 Andrey changed: What|Removed |Added URL||https://invent.kde.org/util ||ities/ark/-/merge_requests/ ||115 --- Comment #4 from Andrey --- https://invent.kde.org/utilities/ark/-/merge_requests/115 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453234] Kate crashes with specific tab and menu selections
https://bugs.kde.org/show_bug.cgi?id=453234 Christoph Cullmann changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |ities/kate/commit/a2d0f284c |ities/kate/commit/a28624c87 |af5bc9ff41995351d722181c16f |7cfe6db6ae6ab257f95af36213b |5dad|25e0 --- Comment #2 from Christoph Cullmann --- Git commit a28624c877cfe6db6ae6ab257f95af36213b25e0 by Christoph Cullmann. Committed on 30/04/2022 at 16:30. Pushed by cullmann into branch 'release/22.04'. fix crash on file browser activation (cherry picked from commit a2d0f284caf5bc9ff41995351d722181c16f5dad) M +6-3addons/filebrowser/katefilebrowserplugin.cpp https://invent.kde.org/utilities/kate/commit/a28624c877cfe6db6ae6ab257f95af36213b25e0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453234] Kate crashes with specific tab and menu selections
https://bugs.kde.org/show_bug.cgi?id=453234 Christoph Cullmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/kate/commit/a2d0f284c ||af5bc9ff41995351d722181c16f ||5dad Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Christoph Cullmann --- Git commit a2d0f284caf5bc9ff41995351d722181c16f5dad by Christoph Cullmann. Committed on 30/04/2022 at 16:30. Pushed by cullmann into branch 'master'. fix crash on file browser activation M +6-3addons/filebrowser/katefilebrowserplugin.cpp https://invent.kde.org/utilities/kate/commit/a2d0f284caf5bc9ff41995351d722181c16f5dad -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453164] Accent color from wallpaper is inconsistent with multiple activities after login
https://bugs.kde.org/show_bug.cgi?id=453164 --- Comment #9 from Viorel-Cătălin Răpițeanu --- For the overlay color issue described at Observed Step 3 a new separate issue was created at: https://bugs.kde.org/show_bug.cgi?id=453235 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453235] Accent color doesn't recolor the links/folders with overlays after apply
https://bugs.kde.org/show_bug.cgi?id=453235 --- Comment #3 from Viorel-Cătălin Răpițeanu --- Created attachment 148479 --> https://bugs.kde.org/attachment.cgi?id=148479=edit Default3.png - Dolphin after appling the color change -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453235] Accent color doesn't recolor the links/folders with overlays after apply
https://bugs.kde.org/show_bug.cgi?id=453235 --- Comment #2 from Viorel-Cătălin Răpițeanu --- Created attachment 148478 --> https://bugs.kde.org/attachment.cgi?id=148478=edit Default1.png - Dolphin before appling the color change -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453235] Accent color doesn't recolor the links/folders with overlays after apply
https://bugs.kde.org/show_bug.cgi?id=453235 --- Comment #1 from Viorel-Cătălin Răpițeanu --- Created attachment 148477 --> https://bugs.kde.org/attachment.cgi?id=148477=edit Default1.png - Dolphin before color change -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453235] New: Accent color doesn't recolor the links/folders with overlays after apply
https://bugs.kde.org/show_bug.cgi?id=453235 Bug ID: 453235 Summary: Accent color doesn't recolor the links/folders with overlays after apply Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rapiteanu.cata...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY After changing the overlay color, the folders with icons overlay-ed on them as well as a folder description panel (F11 in dolphin) are not refreshed. STEPS TO REPRODUCE 1. Select 'Accent color from wallpaper' in Settings 2. Open Dolphin and go to a location where you have a folder with icons overlay-ed on it 3. Select 'Accent color from theme' in Settings OBSERVED RESULT All folders are changing their colors except for the ones with icons overlay-ed on them. Also, the file/folder description is not affected by the change (until the directory is changed) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Plasma master (Wayland session) KDE Plasma Version: 5.24.90 master KDE Frameworks Version: 5.93 master Qt Version: 5.15 ADDITIONAL INFORMATION This bug is also described in part in: https://bugs.kde.org/show_bug.cgi?id=453164 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453234] New: Kate crashes with specific tab and menu selections
https://bugs.kde.org/show_bug.cgi?id=453234 Bug ID: 453234 Summary: Kate crashes with specific tab and menu selections Product: kate Version: 22.04.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: jdavidwy...@gmail.com Target Milestone: --- Application: kate (22.04.0) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.13.0-40-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: I was exploring Kate after install. Selecting the Filesystem tab produces crash every time. Selecting menu option Settings > Configure Kate produces crash every time. The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault [New LWP 13634] [New LWP 13638] [New LWP 13639] [New LWP 13640] [New LWP 13641] [New LWP 13642] [New LWP 13643] [New LWP 13644] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fd4b9b6c9cf in __GI___poll (fds=0x7fff82fb8978, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7fd4b5b989c0 (LWP 13631))] Thread 9 (Thread 0x7fd49a7fc700 (LWP 13644)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564705c26750) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564705c26700, cond=0x564705c26728) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564705c26728, mutex=0x564705c26700) at pthread_cond_wait.c:638 #3 0x7fd4a663a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fd4a663a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fd4b8a7c609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fd4b9b79163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fd49affd700 (LWP 13643)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564705c26750) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564705c26700, cond=0x564705c26728) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564705c26728, mutex=0x564705c26700) at pthread_cond_wait.c:638 #3 0x7fd4a663a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fd4a663a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fd4b8a7c609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fd4b9b79163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fd49b7fe700 (LWP 13642)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564705c261c0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564705c26170, cond=0x564705c26198) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564705c26198, mutex=0x564705c26170) at pthread_cond_wait.c:638 #3 0x7fd4a663a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fd4a663a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fd4b8a7c609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fd4b9b79163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fd49bfff700 (LWP 13641)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564705c261c0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564705c26170, cond=0x564705c26198) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564705c26198, mutex=0x564705c26170) at pthread_cond_wait.c:638 #3 0x7fd4a663a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fd4a663a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fd4b8a7c609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fd4b9b79163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fd4a0cbe700 (LWP 13640)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564705c261c0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564705c26170, cond=0x564705c26198) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564705c26198, mutex=0x564705c26170) at pthread_cond_wait.c:638 #3 0x7fd4a663a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fd4a663a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fd4b8a7c609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fd4b9b79163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread
[frameworks-kcoreaddons] [Bug 452817] screenlocker currently not working at all
https://bugs.kde.org/show_bug.cgi?id=452817
Fabian Vogt changed:
What|Removed |Added
CC||fab...@ritter-vogt.de,
||kdelibs-b...@kde.org
Version|git-master |unspecified
Assignee|plasma-b...@kde.org |mp...@kde.org
Component|general |general
Product|kscreenlocker |frameworks-kcoreaddons
--- Comment #9 from Fabian Vogt ---
(In reply to Luca Beltrame from comment #8)
> This happens because KLibexec looks up kscreenlocker_greet in /libexec, not
> /usr/libexec.
>
> From strace I ran on a nested Wayland session:
>
> [pid 13948] execve("/libexec/kscreenlocker_greet"
>
> But in openSUSE Tumbleweed it is installed in /usr/libexec.
>
> I had a discussion about it with Fabian on IRC about a possible cause:
>
> [12:35] The relative path is formed by going from /usr/lib64/ to
> /usr/libexec
> [12:36] During runtime the shared library is opened from /lib64/
> though, so it tries /libexec
> [12:36] i.e. incompatible with usrmerge
> [12:37] At least that's my theory
Looks like my theory is correct.
libkscreenlocker is built with /usr/lib64 as full libdir path and /usr/libexec
as full libexec path, so it tries to reach the greeter by doing
$self/../libexec/kscreenlocker_greet. In a usr-merged system, /lib64 is a
symlink to /usr/lib64 (or the other way around), so
/lib64/libKScreenLocker.so.5.24.80 and /usr/lib64/libKScreenLocker.so.5.24.80
refer to the same file. As /lib64 is earlier in the library search path than
/usr/lib64, the library is loaded as /lib64/libKScreenLocker.so.5.24.80 and the
path ends up as /lib64/../libexec/.
It works after forcing /usr/lib64/ earlier in the search path than /lib64.
Moving this over to kcoreaddons as the issue is with KLibexec.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 440417] Really high CPU usage when many files are updated
https://bugs.kde.org/show_bug.cgi?id=440417 lemaitre changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #10 from lemaitre --- Oh, I missed the notification for ticket closure. Just to sum up: - Having a high number of files within a folder alone does not trigger the bug - Touching a few files in the big folder does not trigger the bug - Touching all files (a few thousands) with `touch *` DOES trigger the bug - The bug is not about empty files, it also happens with images - When I exit the folder, the CPU consumption goes down back to zero - Purging the thumbnail cache did not solve the bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453233] New: Wayland: virt-manager doesn't hide cursor in graphical console
https://bugs.kde.org/show_bug.cgi?id=453233 Bug ID: 453233 Summary: Wayland: virt-manager doesn't hide cursor in graphical console Product: kwin Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jackygu...@hotmail.com Target Milestone: --- SUMMARY This issue is exclusive to KDE/Wayland. I have tried with X11. In addition, the issue never occurred on GNOME. In virt-manager, the graphical console does not hide the cursor correctly. It should be doing this so long as the cursor is hovering on the console. However, it doesn't. STEPS TO REPRODUCE 1. Open virt-manager. 2. Open a VM. This creates a separate window. 3. Start the VM. Move the cursor over the graphical console and observe. 4. If the cursor seems fine, try minimizing, then re-opening the window. OBSERVED RESULT The host cursor is visible on the graphical console. EXPECTED RESULT The host cursor should be invisible if it is on the graphical console. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArcoLinux (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Display protocol: Wayland virt-manager version: 4.0.0 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 453193] Kalarm crashed while selecting font thickness of an alarm template
https://bugs.kde.org/show_bug.cgi?id=453193 David Jarvie changed: What|Removed |Added Version Fixed In||22.04.1 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 453193] Kalarm crashed while selecting font thickness of an alarm template
https://bugs.kde.org/show_bug.cgi?id=453193 David Jarvie changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||kalarm/commit/1e44f03153771 ||1733a38fe487fee78e0be41c698 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from David Jarvie --- Git commit 1e44f031537711733a38fe487fee78e0be41c698 by David Jarvie. Committed on 30/04/2022 at 15:31. Pushed by djarvie into branch 'release/22.04'. Bug 453193: Fix crash in font chooser after deselecting default font If the font chooser is displayed with 'use default font' selected, and 'use default font' is deselected and a style is then chosen, it crashed due to having no current font. M +2-1Changelog M +1-1src/birthdaydlg.cpp M +2-5src/editdlgtypes.cpp M +3-9src/fontcolour.cpp M +2-3src/fontcolour.h M +4-13 src/fontcolourbutton.cpp M +9-3src/fontcolourbutton.h https://invent.kde.org/pim/kalarm/commit/1e44f031537711733a38fe487fee78e0be41c698 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344170] i965: artifacts after screen look and on dual head
https://bugs.kde.org/show_bug.cgi?id=344170 --- Comment #22 from Lach Sławomir --- It looks there are no graphics glitches under wayland. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 452817] screenlocker currently not working at all
https://bugs.kde.org/show_bug.cgi?id=452817
Luca Beltrame changed:
What|Removed |Added
CC||lbeltr...@kde.org
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
--- Comment #8 from Luca Beltrame ---
This happens because KLibexec looks up kscreenlocker_greet in /libexec, not
/usr/libexec.
>From strace I ran on a nested Wayland session:
[pid 13948] execve("/libexec/kscreenlocker_greet"
But in openSUSE Tumbleweed it is installed in /usr/libexec.
I had a discussion about it with Fabian on IRC about a possible cause:
[12:35] The relative path is formed by going from /usr/lib64/ to
/usr/libexec
[12:36] During runtime the shared library is opened from /lib64/
though, so it tries /libexec
[12:36] i.e. incompatible with usrmerge
[12:37] At least that's my theory
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 453231] Digikam does not work anymore after upgrading to ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453231 caulier.gil...@gmail.com changed: What|Removed |Added Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453231] Digikam does not work anymore after upgrading to ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453231 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- This must be fixed with next 7.7.0. Please try with current AppImage pre-release : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453232] New: Can't switch audio output
https://bugs.kde.org/show_bug.cgi?id=453232 Bug ID: 453232 Summary: Can't switch audio output Product: plasmashell Version: 5.24.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rafalkozlowsk...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 148476 --> https://bugs.kde.org/attachment.cgi?id=148476=edit screenshot When plugged in jack directly in mother board and another jack port on my case i can switch between headphone or line out. In latests versions it stopped working. Plugged both jacks and only headphones working. Switching to line out ends with silence and no sound at all. Had to plug out headphones physically. Other problem is with profiles. Would be nice to see if could assign different profile to every port. Want to use on speakers 2.1 profile but then headphones wont work and had to switch also this profile. To make it clear i paste here add screenshot Problem since at least 5.24.2 version. Now tested with 5.24.4 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453175] No button and option "Show whitespace"
https://bugs.kde.org/show_bug.cgi?id=453175 --- Comment #3 from Eric Armbruster --- I hope I got this correctly now: you would like to have a button for the existing action (show non printable spaces), instead of having to select it from the menu? If so: 1. Right-click menu bar -> select main tool bar 2. Right-click tool bar -> Configure Toolbars 3. In Toolbar select Main toolbar Katepartview 4. Choose Show non printable spaces (and maybe an icon) and save I know this does not fully solve your problem, as you are asking for separate buttons for the different whitespace characters and probably would like to have the buttons on the toolbar by default. However, I currently feel that would not be a great decision: - I think most users do not need to frequently change this setting - One action is sufficient for most users - We would need to find or create a proper icon for this action, so the toolbar does not look so weird with the long text On another note, newlines are always visualized to my understanding by, well ehm, new lines. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453231] New: Digikam does not work anymore after upgrading to ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453231 Bug ID: 453231 Summary: Digikam does not work anymore after upgrading to ubuntu 22.04 Product: digikam Version: 7.6.0 Platform: Appimage OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Bundle-AppImage Assignee: digikam-bugs-n...@kde.org Reporter: philippe.quag...@laposte.net Target Milestone: --- SUMMARY Digikam does not start at all, no error message, nothing happens STEPS TO REPRODUCE 1. Launch digikam 2. 3. OBSERVED RESULT If launch from the dock, nothing appends. If launch from a terminal, here is the error message I get in the terminal: philippe@philippe-desktop:~/Applications$ ./digiKam-7.6.0-x86-64_69f78304eb7f5b3b4c99798ce9ed747c.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so digikam: symbol lookup error: /lib/x86_64-linux-gnu/libgio-2.0.so.0: undefined symbol: g_module_open_full SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04, using the .appimage package ADDITIONAL INFORMATION Tested on 2 different computers, same result on both. Very bad for me, Digikam is the cornerstone of my photographic workflow ! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 452817] screenlocker currently not working at all
https://bugs.kde.org/show_bug.cgi?id=452817 Rik Mills changed: What|Removed |Added CC||rikmi...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 452691] [Bluetooth - Bluedevil] PS4 / Dual Shock 4 Controller Crashed kded5
https://bugs.kde.org/show_bug.cgi?id=452691 Dave changed: What|Removed |Added OS|Linux |Microsoft Windows Platform|Archlinux Packages |unspecified CC||davecollier1...@gmail.com --- Comment #1 from Dave --- Hi on version 21 12 3 selected 4k, when Rendar is selected the system crashes and switches off the kdenlive prog works ok when mp3 selected -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453229] New setBlurRegion() API gives blocky/aliased blur region corners on Wayland
https://bugs.kde.org/show_bug.cgi?id=453229 --- Comment #1 from Paul McAuley --- Created attachment 148475 --> https://bugs.kde.org/attachment.cgi?id=148475=edit X11 by contrast. Screenshot of ClassiK window decoration with 20% opacity titlebars/borders and blur on, corner radius=4, shadows disabled to emphasise bug. The corners are very smooth. By contrast here is a similar screenshot on X11. It results in very smooth corners to the blur region. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453230] New: Set default profile based on system color scheme
https://bugs.kde.org/show_bug.cgi?id=453230
Bug ID: 453230
Summary: Set default profile based on system color scheme
Product: konsole
Version: 22.04.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: konsole-de...@kde.org
Reporter: aron...@gmail.com
Target Milestone: ---
It'd be great if you could set the default profile to one with a light
appearance when my color scheme is {Breeze-dark} and a different one when my
color scheme is {Other color scheme}
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 453229] New: New setBlurRegion() API gives blocky/aliased blur region corners on Wayland
https://bugs.kde.org/show_bug.cgi?id=453229 Bug ID: 453229 Summary: New setBlurRegion() API gives blocky/aliased blur region corners on Wayland Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: k...@paulmcauley.com Target Milestone: --- Created attachment 148474 --> https://bugs.kde.org/attachment.cgi?id=148474=edit Screenshot of ClassiK window decoration with 20% opacity titlebars/borders and blur on, corner radius=4, shadows disabled to emphasise bug. The corners exhibit very blocky aliasing. Hello, I have made a first attempt at implementing the new setBlurRegion() API (due to land in Plasma 5.25) in my C++ Window Decoration. This can be found on the branch at: https://github.com/paulmcauley/classik/tree/kornerbug-fix-plasma5.25 I construct my window shape using a QPainterPath (called m_windowPath) and then call setBlurRegion as follows: setBlurRegion( QRegion( m_windowPath->toFillPolygon().toPolygon() ) ) ; The results on X11 are excellent and produces very smooth corners when transparency and blur are enabled. However, on Wayland, the corners of the blur region are very blocky/aliased in appearance. Operating System: openSUSE Tumbleweed 20220421 KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.17.3-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 Manufacturer: Dell Inc. Product Name: XPS 15 9560 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 453228] New: Column "Name" is sorted alphabetically, not alphanumerically with no options to change it
https://bugs.kde.org/show_bug.cgi?id=453228
Bug ID: 453228
Summary: Column "Name" is sorted alphabetically, not
alphanumerically with no options to change it
Product: ark
Version: 21.12.3
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: elvis.angelac...@kde.org
Reporter: hasez...@gmail.com
CC: aa...@kde.org, rthoms...@gmail.com
Target Milestone: ---
Created attachment 148473
--> https://bugs.kde.org/attachment.cgi?id=148473=edit
Picture showcasing current sorting
SUMMARY
Currently, ARK sorts the Column "Name" alphabetically, not alphanumerically,
which is inconsistent with dolphin which uses alphanumeric by default
STEPS TO REPRODUCE
1. Open a file in ark that has files named like "something1.something" and
"something2.something" and "something10.something"
2. sort by column "name" (default?)
3. observe alphabetic result instead of alphanumeric
OBSERVED RESULT
alphabetic sorting ("something10.something" before "something2.something")
EXPECTED RESULT
alphanumeric (or also sometimes called "natural sorting") sorting
("something10.something" after "something2.something") or at least a option to
change the sorting algorithm
SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.17.1-3-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX Vega
extra/ark 21.12.3-1
ADDITIONAL INFORMATION
this is probably a feature request
for example i use ark commonly to quickly inspect epub files which are commonly
named "chapter[N].xhtml" or similar
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 442069] Dolphin Crashes sometimes when in folders with files that are thumbnail-able (sshfs?)
https://bugs.kde.org/show_bug.cgi?id=442069 hasez...@gmail.com changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from hasez...@gmail.com --- as a small update, since i had made this report, i did not have any dolphin crashes anymore Current System: Operating System: Manjaro Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.17.1-3-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX Vega extra/dolphin 21.12.3-1 extra/dolphin-plugins 21.12.3-1 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453227] New: KATE Crashed
https://bugs.kde.org/show_bug.cgi?id=453227
Bug ID: 453227
Summary: KATE Crashed
Product: kate
Version: 22.04.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: globalun...@disroot.org
Target Milestone: ---
Application: kate (22.04.0)
Qt Version: 5.15.2
Frameworks Version: 5.93.0
Operating System: Linux 5.17.4-1-default x86_64
Windowing System: Wayland
Distribution: openSUSE Tumbleweed
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I was editing a TXT file in Kate
NOTES:
The free app Shutter Encoder was converting videos in the background
Shutter Encoder is not designed with Wayland in mind
Krusader File Manager often gives a crash when Shutter Encoder is converting
media files as well
OS INFO:
Operating System: openSUSE Tumbleweed 20220427
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
Kernel Version: 5.17.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fc51ca04062 in QFontEngineFT::loadGlyphFor(unsigned int, QFixed,
QFontEngine::GlyphFormat, QTransform const&, bool, bool) (this=0x55c3a82162f0,
g=172, subPixelPosition=..., format=2821343536, t=...,
fetchBoundingBox=, disableOutlineDrawing=77) at
freetype/qfontengine_ft.cpp:1884
#7 0x55c3a82162f0 in ()
#8 0x7fc51ca0434d in QFontEngineFT::glyphData(unsigned int, QFixed,
QFontEngine::GlyphFormat, QTransform const&) (this=,
glyphIndex=, subPixelPosition=..., neededFormat=,
t=) at freetype/qfontengine_ft.cpp:1853
#9 0x7fc51f19c104 in QRasterPaintEngine::drawCachedGlyphs(int, unsigned
int const*, QFixedPoint const*, QFontEngine*) (this=0x55c3a88079c0,
numGlyphs=, glyphs=, positions=,
fontEngine=0x0) at painting/qpaintengine_raster.cpp:2889
#10 0x7fc51f19fb15 in QRasterPaintEngine::drawTextItem(QPointF const&,
QTextItem const&) (this=0x55c3a88079c0, p=..., textItem=...) at
../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:119
#11 0x7fc51f1b968f in QPainterPrivate::drawTextItem(QPointF const&,
QTextItem const&, QTextEngine*) (this=, p=..., _ti=...,
textEngine=0x55c3a8ac7190) at painting/qpainter.cpp:6560
#12 0x7fc51efd3de5 in QTextLine::draw(QPainter*, QPointF const&,
QTextLayout::FormatRange const*) const (this=this@entry=0x7ffd5dc81400,
p=p@entry=0x7ffd5dc81c70, pos=..., selection=selection@entry=0x0) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:138
#13 0x7fc51efd50a6 in QTextLayout::draw(QPainter*, QPointF const&,
QVector const&, QRectF const&) const (this=, p=p@entry=0x7ffd5dc81c70, pos=..., selections=..., clip=...) at
text/qtextlayout.cpp:1262
#14 0x7fc5208a81e9 in KateRenderer::paintTextLine(QPainter&,
QExplicitlySharedDataPointer, int, int, KTextEditor::Cursor
const*, QFlags) (this=0x55c3a881ff80,
paint=, range=..., xStart=0, xEnd=1392, cursor=0x7ffd5dc81c78,
flags=...) at /usr/include/qt5/QtCore/qpoint.h:133
#15 0x7fc5209078a7 in KateViewInternal::paintEvent(QPaintEvent*)
(this=0x55c3a7ec2f20, e=0x7ffd5dc81e70) at
/usr/src/debug/ktexteditor-5.93.0-1.1.x86_64/src/view/kateviewinternal.cpp:3909
#16 0x7fc51f6a1cde in QWidget::event(QEvent*) (this=0x55c3a7ec2f20,
event=0x7ffd5dc81e70) at kernel/qwidget.cpp:9020
#17 0x7fc51f65fb0f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55c3a7ec2f20, e=0x7ffd5dc81e70) at
kernel/qapplication.cpp:3632
#18 0x7fc51ea74b5a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55c3a7ec2f20, event=0x7ffd5dc81e70) at
kernel/qcoreapplication.cpp:1064
#19 0x7fc51f699ce6 in QWidgetPrivate::sendPaintEvent(QRegion const&)
(this=this@entry=0x55c3a8952230, toBePainted=...) at kernel/qwidget.cpp:5467
#20 0x7fc51f69a512 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, QFlags, QPainter*,
QWidgetRepaintManager*) (this=this@entry=0x55c3a8952230, pdev=0x55c3a8acb2a8,
rgn=..., offset=..., flags=flags@entry=...,
sharedPainter=sharedPainter@entry=0x0, repaintManager=) at
kernel/qwidget.cpp:5417
#21 0x7fc51f670ad2 in QWidgetRepaintManager::paintAndFlush()
(this=) at kernel/qwidgetrepaintmanager.cpp:1003
#22 0x7fc51f6a242d in QWidget::event(QEvent*) (this=0x55c3a7c38e60,
event=0x55c3a8ba0fd0) at kernel/qwidget.cpp:8965
#23 0x7fc5202f2569 in KXmlGuiWindow::event(QEvent*) (this=0x55c3a7c38e60,
ev=0x55c3a8ba0fd0) at
/usr/src/debug/kxmlgui-5.93.0-1.1.x86_64/src/kxmlguiwindow.cpp:220
#24
[systemsettings] [Bug 453226] New: Impossible to remove a cursor theme installed from KDE Store
https://bugs.kde.org/show_bug.cgi?id=453226 Bug ID: 453226 Summary: Impossible to remove a cursor theme installed from KDE Store Product: systemsettings Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 148472 --> https://bugs.kde.org/attachment.cgi?id=148472=edit screen recording SUMMARY After click on inline 'Remove' button of a cursor theme installed from KDE Store, apparently the cursor theme is removed. But the cursor theme will still be available for selection next time I open Cursors KCM. Please watch the attached screen recording. EXPECTED RESULT Cursors KCM is able to remove cursor themes SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 Graphics Platform: X11 ADDITIONAL INFORMATION also it's impossible to remove a cursor theme via 'Get new cursors' window -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 451226] No thumbnail for EPUB3 files
https://bugs.kde.org/show_bug.cgi?id=451226 hasez...@gmail.com changed: What|Removed |Added CC||hasez...@gmail.com --- Comment #5 from hasez...@gmail.com --- *** Bug 452411 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
