[digikam] [Bug 414959] Send by email with Thunderbird does not work anymore
https://bugs.kde.org/show_bug.cgi?id=414959 --- Comment #24 from hp --- (In reply to Maik Qualmann from comment #22) > A snap package is not a native digiKam version. > > Maik You are correct, but that's all I get from official PPA. For security reasons, I don't want to use private PPAs -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446540] unable to load applications
https://bugs.kde.org/show_bug.cgi?id=446540 --- Comment #2 from toxictech --- i understand, thank you for your response, i will take that into consideration. On Mon, Dec 6, 2021 at 7:08 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=446540 > > Nate Graham changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > CC||n...@kde.org > Resolution|--- |NOT A BUG > > --- Comment #1 from Nate Graham --- > It appears that you are using Kali Linux, which is not appropriate for > general > use, and you will find a million and a half other little weirdnesses like > this, > because running everything as root is explicitly unsupported and never > recommended. I would encourage you to re-install your system with a more > appropriate general purpose Linux distro, such as one of the ones you can > see > at https://kde.org/distributions. > > > Thanks for understanding! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 446771] New: I cant' resume (after suspend) in wayland
https://bugs.kde.org/show_bug.cgi?id=446771 Bug ID: 446771 Summary: I cant' resume (after suspend) in wayland Product: ksmserver Version: 5.23.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jesa...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. I tried to suspend in Wayland. It works! 2. I tried to resume in Wayland. Lights gets on, system boots, backlights in monitors gets on, but there is no image in wayland. 3. I have to reset the system to get it working again OBSERVED RESULT -I have no problems in X11. Only Wayland. -I tried it disabling kscreenlocker. It is not a solution. -My graphic card is an NVIDIA 1050 TI. I use 475 series driver. (official repo in Opensuse) - Ctl+ALt +F1 (or F2...) no works, There is no way to get a terminal / session until rebooting. I connect to my PC via SSH and get this log.: # [ 173.449129] sd 2:0:0:0: [sdc] Synchronizing SCSI cache [ 173.449273] sd 2:0:0:0: [sdc] Stopping disk [ 173.452802] sd 3:0:0:0: [sdd] Synchronizing SCSI cache [ 173.452834] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 173.452881] sd 3:0:0:0: [sdd] Stopping disk [ 173.453820] sd 0:0:0:0: [sda] Stopping disk [ 173.464819] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [ 173.464871] sd 5:0:0:0: [sde] Synchronizing SCSI cache [ 173.465573] sd 1:0:0:0: [sdb] Stopping disk [ 173.465668] sd 5:0:0:0: [sde] Stopping disk [ 174.606335] ACPI: Preparing to enter system sleep state S3 [ 174.608895] PM: Saving platform NVS memory [ 174.609000] Disabling non-boot CPUs ... [ 174.610792] smpboot: CPU 1 is now offline [ 174.613232] smpboot: CPU 2 is now offline [ 174.616043] smpboot: CPU 3 is now offline [ 174.618880] smpboot: CPU 4 is now offline [ 174.620612] IRQ 136: no longer affine to CPU5 [ 174.621647] smpboot: CPU 5 is now offline [ 174.622985] IRQ 131: no longer affine to CPU6 [ 174.624016] smpboot: CPU 6 is now offline [ 174.625332] IRQ 132: no longer affine to CPU7 [ 174.626362] smpboot: CPU 7 is now offline [ 174.629762] ACPI: Low-level resume complete [ 174.629826] PM: Restoring platform NVS memory [ 174.631504] Enabling non-boot CPUs ... [ 174.631537] x86: Booting SMP configuration: [ 174.631537] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 174.633106] CPU1 is up [ 174.633124] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 174.634688] CPU2 is up [ 174.634703] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 174.636267] CPU3 is up [ 174.636283] smpboot: Booting Node 0 Processor 4 APIC 0x1 [ 174.636905] CPU4 is up [ 174.636923] smpboot: Booting Node 0 Processor 5 APIC 0x3 [ 174.637440] CPU5 is up [ 174.637455] smpboot: Booting Node 0 Processor 6 APIC 0x5 [ 174.637978] CPU6 is up [ 174.637993] smpboot: Booting Node 0 Processor 7 APIC 0x7 [ 174.638516] CPU7 is up [ 174.640493] ACPI: Waking up from system sleep state S3 [ 174.663892] sd 2:0:0:0: [sdc] Starting disk [ 174.663895] sd 3:0:0:0: [sdd] Starting disk [ 174.663919] sd 5:0:0:0: [sde] Starting disk [ 174.663922] sd 1:0:0:0: [sdb] Starting disk [ 174.663924] sd 0:0:0:0: [sda] Starting disk [ 174.666992] parport_pc 00:01: activated [ 174.669333] serial 00:02: activated [ 174.976278] usb 1-2: reset high-speed USB device number 2 using xhci_hcd [ 175.036148] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 175.036189] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 175.036219] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 175.037035] ata2.00: supports DRM functions and may not be fully accessible [ 175.037584] ata6.00: configured for UDMA/133 [ 175.038123] ata2.00: supports DRM functions and may not be fully accessible [ 175.038617] ata2.00: configured for UDMA/133 [ 175.039744] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 175.042896] ata1.00: configured for UDMA/133 [ 175.052977] ata5.00: configured for UDMA/133 [ 175.348392] acpi LNXPOWER:16: Turning OFF [ 175.348643] acpi LNXPOWER:15: Turning OFF [ 175.348889] acpi LNXPOWER:14: Turning OFF [ 175.349134] acpi LNXPOWER:13: Turning OFF [ 175.349378] acpi LNXPOWER:12: Turning OFF [ 175.349620] acpi LNXPOWER:11: Turning OFF [ 175.349863] acpi LNXPOWER:10: Turning OFF [ 175.350107] acpi LNXPOWER:0f: Turning OFF [ 175.350350] acpi LNXPOWER:0e: Turning OFF [ 175.350592] acpi LNXPOWER:0d: Turning OFF [ 175.350833] acpi LNXPOWER:0c: Turning OFF [ 175.351075] acpi LNXPOWER:0b: Turning OFF [ 175.351317] acpi LNXPOWER:0a: Turning OFF [ 175.351548] acpi LNXPOWER:09: Turning OFF [ 175.351592] acpi LNXPOWER:08: Turning OFF [ 175.351636] acpi LNXPOWER:07: Turning OFF [ 175.351681] acpi LNXPOWER:06: Turning OFF [ 175.351724] acpi LNXPOWER:05: Turning OFF [ 175.351768] acpi LNXPOWER:04:
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 Krisztián Szegi changed: What|Removed |Added CC||crosssz...@gmail.com --- Comment #21 from Krisztián Szegi --- Hi all, Excuse me for the heresy but: For two weeks, KRDC just crashed akonadi when connecting to a remote with RDP on wayland, so I had to look at different solutions: I used Remmina! I did not test KRDC regularily, but now it is "working" again. My takeaway from this experience however: - Remmina uses libfreerdp2-2, and mostly "just works" - UI-vise, KRDC is a bit outdated (indirectly, but relevant) Tony Murray > To fix this, it probably needs to use the xfreerdp libraries and draw into > the krdc window. I think that is the only way forward. Embedding freerdp or wlfreerdp is, and was - IMO - a bad design decision. But I presume a thin wrapper around (wl)freerdp was the easiest initial solution to a GUI app. Now wayland is just making this more apparent. Remmina spawns a new Remmina for each connection, (each with a connection control interface of its own, similari to Teamviewer's or Windows RDC's interface), that is just not trivially possible with the current KRDC arch on wayland. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446717] Discover shows emtpy window after startup
https://bugs.kde.org/show_bug.cgi?id=446717 --- Comment #2 from Luca Manganelli --- I've run plasma-discovery, then I clicked on the "Updates": adding empty sources model QStandardItemModel(0x5640c644ffa0) ** (process:5566): WARNING **: 07:22:34.623: Not changing AppStream cache location: No longer supported. QDir::mkpath: Empty or null file name org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property "value" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:261:18: QML QQuickItem*: Binding loop detected for property "implicitWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. took really long to fetch PackageKitBackend(0x5640c63a0cc0) <<--- I CLICKED ON UPDATES BUTTON QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:813: Error: Error while loading page: qrc:/qml/UpdatesPage.qml:94 Type TextArea unavailable file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/TextArea.qml:15 module "org.kde.sonnet" is not installed -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 446770] New: KONQUEROR CRASHES WHEN CLOSING A TAB
https://bugs.kde.org/show_bug.cgi?id=446770 Bug ID: 446770 Summary: KONQUEROR CRASHES WHEN CLOSING A TAB Product: konqueror Version: 5.0.97 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: malobazad...@gmail.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-91-generic x86_64 Windowing system: X11 Distribution: Linux Mint 20.2 -- Information about the crash: - What I was doing when the application crashed: -The app keeps crashing whenever you try to close the tab. -It happens whenever I right click on the tab I want to close and select the 'Close View' context menu button -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fecfac98000 (LWP 10357))] Thread 29 (Thread 0x7fec4b7fe700 (LWP 10554)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fec4b7fdb60, clockid=, expected=0, futex_word=0x7fec4b7fdca8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fec4b7fdb60, clockid=, mutex=0x7fec4b7fdc58, cond=0x7fec4b7fdc80) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fec4b7fdc80, mutex=0x7fec4b7fdc58, abstime=0x7fec4b7fdb60) at pthread_cond_wait.c:656 #3 0x7feccb7f9b2e in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7feccb7fa51f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7feccb7fa615 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7feccb7bbda6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7feccb7be939 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7feccb7beef8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7feccb7fcb63 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fecfd6c6609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fed00e54293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fec677fe700 (LWP 10553)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fec677fdb60, clockid=, expected=0, futex_word=0x7fec677fdca8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fec677fdb60, clockid=, mutex=0x7fec677fdc58, cond=0x7fec677fdc80) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fec677fdc80, mutex=0x7fec677fdc58, abstime=0x7fec677fdb60) at pthread_cond_wait.c:656 #3 0x7feccb7f9b2e in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7feccb7fa51f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7feccb7fa615 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7feccb7bbda6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7feccb7bec48 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7feccb7beef8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7feccb7fcb63 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fecfd6c6609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fed00e54293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7fec5629c700 (LWP 10488)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7feccffc5938) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7feccffc58e8, cond=0x7feccffc5910) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7feccffc5910, mutex=0x7feccffc58e8) at pthread_cond_wait.c:638 #3 0x7feccb7f9a5e in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7feccbe04018 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7feccbe043bd in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7feccbe01e6a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7feccb7fcb63 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fecfd6c6609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fed00e54293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7fec56b50700 (LWP 10478)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7fec56b4fcb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7fec56b4fc68, cond=0x7fec56b4fc90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7fec56b4fc90, mutex=0x7fec56b4fc68) at pthread_cond_wait.c:638 #3 0x7feccb7f9a5e in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4
[kwin] [Bug 446769] New: [Wayland] Kwin crashes randomly when sharing screen on Chromium and switching Virtual Desktops using pager widget.
https://bugs.kde.org/show_bug.cgi?id=446769 Bug ID: 446769 Summary: [Wayland] Kwin crashes randomly when sharing screen on Chromium and switching Virtual Desktops using pager widget. Product: kwin Version: 5.23.4 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: dev.bacterios...@aleeas.com Target Milestone: --- Created attachment 144417 --> https://bugs.kde.org/attachment.cgi?id=144417=edit journalctl log of the crash SUMMARY This bug happens with the Pager widget on Wayland. Not sure where it belongs exactly. Kwin crashes when I am sharing screen on Chromium (XWayland) and switching virtual desktops using pager widget. The crash happens randomly, sometimes after switching 2 3 times, sometimes it may takes more tries but it always happens. I have attached journalctl log in text file attached. Since I am running Arch, quality crash report is a pain to obtain. I was not able to reproduce if I scroll on Pager widget or if I use shortcuts to switch VDs. It happens only when I click on the VD in the Pager widget to switch. STEPS TO REPRODUCE 1. Share whole screen on Chromium (XWayland) 2. Switch VDs using pager widget by clicking on the virtual desktops. 3. Repeat step 2 until Kwin crashes. The crash always happens but you may need to switch VDs a number of times. Sometimes it happens in 2-3 times sometimes 30-40 times. OBSERVED RESULT Kwin crashes after a variable number of virtual desktop switching. EXPECTED RESULT Kwin shouldn't crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Graphics Platform: Wayland ADDITIONAL INFORMATION 1. The pager widget is on the panel. 2. Screen sharing is done using webrtc-pipewire flag in Chromium. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446588] Brush preset reimport (same file) asks for overwrite, does not recognize that the file is the same md5sum.
https://bugs.kde.org/show_bug.cgi?id=446588 --- Comment #6 from Eoin O'Neill --- dmitryk, Are you sure this isn't a bigger issue with the way the md5 sums work? ``` Entering "KisResourceLocator::importResource()" existingResource->filename() = "c)_Pencil-2_Copy.kpp" existingResource->md5Sum() = "065415ee40bbf674438590e85a31a643" resourceUrl = "paintoppresets/c)_Pencil-2_Copy.kpp" md5 = "0c415c37996944b9b14f91e1052b6481" ``` Seems like these MD5 sums should be the same but their not. The results of generateHash don't seem to equal the results of the resources md5sum function which is a bit bizarre. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446759] Implement Mixbox, a "Practical Pigment Mixing for Digital Painting"
https://bugs.kde.org/show_bug.cgi?id=446759 --- Comment #2 from Emmet O'Neill --- > [1.] I find the "non-commercial license" to be a bit vague as far as > software licensing goes. Krita is obviously free and open source software > licensed under the GPLv3, but it is also available through stores on various > platforms as a means of broadening our user base and creating a way to > support development. So, does that count as "commercial" or not? Because of > that, we would probably be wise to contact the owners of this code and get > an explicit answer (and permission) before using any of their code. > > I could be over-thinking it a bit, but I think there's an element of risk > involved with making use of code with vague licenses. I guess I was actually under-thinking it. Tiar tells me that the source code in this case is just plain incompatible with GPLv3, so it would need to be re-implemented in a GPLv3 compatible license based on the research paper. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 446768] New: Graph lines on the x axes in the speed section of network applet are gray coloured and not clearly visible
https://bugs.kde.org/show_bug.cgi?id=446768 Bug ID: 446768 Summary: Graph lines on the x axes in the speed section of network applet are gray coloured and not clearly visible Product: plasma-nm Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: ra...@raghukamath.com Target Milestone: --- Created attachment 144416 --> https://bugs.kde.org/attachment.cgi?id=144416=edit screenshot showing the gray lines on blue background SUMMARY The network manager applet shows the speed in graphs. The lines that denote the speed are in gray colour the panel is constantly in highlighted state so these gray line are shown over a blue background. They become hard to see and look odd. The contrast ratio of the lines on the background is 1.16, which as per the KDE kontrast app is bad for large or even nomal text. I am attaching a screenshot to show the issue. STEPS TO REPRODUCE 1. Open the network manager applet and click on the dropdown to see the speed section -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443222] [Wayland] adding a new screen causes lockscreen to crash. Reboot needed
https://bugs.kde.org/show_bug.cgi?id=443222 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #9 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445958] Make possible to set the app icon size when creating a theme
https://bugs.kde.org/show_bug.cgi?id=445958 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446767] New: Pressing the home button doesn't clear the search listing in the sidebar.
https://bugs.kde.org/show_bug.cgi?id=446767 Bug ID: 446767 Summary: Pressing the home button doesn't clear the search listing in the sidebar. Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY When I search for a setting in the system setting application, it filters the sidebar to show the particular settings that match my querry. After I change the settings, I press the home button to quickly go to the main page. The page changes to quick settings as it should but the search filter is still not cleared in the sidebar. I have to clear the search by using the clear text icon in the search input box. In discover pressing the home button clears the search and takes the user to home listing as expected. I think systemsettings should also follow the same behaviour. STEPS TO REPRODUCE 1. Open system settings application and search something - example task switcher 2. Now press the Home button in the top toolbar. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 446766] New: WindowsFx Update
https://bugs.kde.org/show_bug.cgi?id=446766
Bug ID: 446766
Summary: WindowsFx Update
Product: kde-cli-tools
Version: 5.23.4
Platform: unspecified
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: aleix...@kde.org
Reporter: wrightsho...@gmail.com
Target Milestone: ---
Application: kcmshell5 (5.23.4)
Qt Version: 5.15.3
Frameworks Version: 5.88.0
Operating System: Linux 5.11.0-41-generic x86_64
Windowing System: X11
Distribution: Windowsfx 11
DrKonqi: 5.23.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed: Attempting to check for
software updates
The message said the repository key was invalid
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: System Settings Module (kcmshell5), signal: Segmentation fault
[New LWP 8283]
[New LWP 8284]
[New LWP 8285]
[New LWP 8286]
[New LWP 8287]
[New LWP 8288]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f1d7be7daff in __GI___poll (fds=0x7ffe60ae8738, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
drkonqi_qmltrace_thread:1
Failed to do pygdbmi parsing: No module named 'pygdbmi'
frame={level="0",func="expression for
preferredHeight",file="/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/FormLayout.qml",fullname="/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/".
-
(beware that frames may have been optimized out)
[Current thread is 1 (Thread 0x7f1d77545980 (LWP 8281))]
Thread 7 (Thread 0x7f1d62849700 (LWP 8288)):
#0 0x7f1d7a33e7f3 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x7f1d7a33f29b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f1d7a33f4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f1d7c44b61b in QEventDispatcherGlib::processEvents
(this=0x7f1d5b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4 0x7f1d7c3ef8ab in QEventLoop::exec (this=this@entry=0x7f1d62848c00,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5 0x7f1d7c2092c2 in QThread::exec (this=this@entry=0x5579d7d850e0) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6 0x7f1d7b473549 in QQmlThreadPrivate::run (this=0x5579d7d850e0) at
qml/ftw/qqmlthread.cpp:155
#7 0x7f1d7c20a45c in QThreadPrivate::start (arg=0x5579d7d850e0) at
thread/qthread_unix.cpp:329
#8 0x7f1d7ad50609 in start_thread (arg=) at
pthread_create.c:477
#9 0x7f1d7be8a293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 6 (Thread 0x7f1d6d6ea700 (LWP 8287)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x5579d7c75ea8) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5579d7c75e58,
cond=0x5579d7c75e80) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x5579d7c75e80, mutex=0x5579d7c75e58) at
pthread_cond_wait.c:638
#3 0x7f1d6e834e7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#4 0x7f1d6e834a7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#5 0x7f1d7ad50609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f1d7be8a293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 5 (Thread 0x7f1d6deeb700 (LWP 8286)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x5579d7c75ea8) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5579d7c75e58,
cond=0x5579d7c75e80) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x5579d7c75e80, mutex=0x5579d7c75e58) at
pthread_cond_wait.c:638
#3 0x7f1d6e834e7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#4 0x7f1d6e834a7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#5 0x7f1d7ad50609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f1d7be8a293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 4 (Thread 0x7f1d6e6ec700 (LWP 8285)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x5579d7c75ea8) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5579d7c75e58,
cond=0x5579d7c75e80) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x5579d7c75e80, mutex=0x5579d7c75e58) at
pthread_cond_wait.c:638
#3 0x7f1d6e834e7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#4 0x7f1d6e834a7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#5 0x7f1d7ad50609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f1d7be8a293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 3 (Thread
[krita] [Bug 446759] Implement Mixbox, a "Practical Pigment Mixing for Digital Painting"
https://bugs.kde.org/show_bug.cgi?id=446759 Emmet O'Neill changed: What|Removed |Added CC||emmetoneill@gmail.com --- Comment #1 from Emmet O'Neill --- Looks interesting and I think everyone would welcome anything that promises even more lifelike or intuitive color mixing in Krita. I have a couple of minor questions/reservations about this, though: [1.] I find the "non-commercial license" to be a bit vague as far as software licensing goes. Krita is obviously free and open source software licensed under the GPLv3, but it is also available through stores on various platforms as a means of broadening our user base and creating a way to support development. So, does that count as "commercial" or not? Because of that, we would probably be wise to contact the owners of this code and get an explicit answer (and permission) before using any of their code. I could be over-thinking it a bit, but I think there's an element of risk involved with making use of code with vague licenses. [2.] Someone who knows more about color in Krita than I do might be able to answer this, but I wonder how this would mesh with our existing color management system. Krita supports a lot of different color models and color spaces, and we would need to make sure that this can either work across all of them or make sure that it is only enabled in the ones where it does work. Maybe it would be as simple as provide an alternate `KoMixColorsOp`, but that may still take a bit of work. Anyway, the theory behind it makes sense to me at least. I think getting some clarity on the "non-commercial" license from the developers is probably a good idea. That might be something to talk about at the next meeting. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446765] New: Screen-shots shown in the preview of grid task switcher are blurred making them look like low quality jpeg
https://bugs.kde.org/show_bug.cgi?id=446765 Bug ID: 446765 Summary: Screen-shots shown in the preview of grid task switcher are blurred making them look like low quality jpeg Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwintabbox Assignee: kwin-bugs-n...@kde.org Reporter: ra...@raghukamath.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 144415 --> https://bugs.kde.org/attachment.cgi?id=144415=edit screenshot showing the preview with blurred images SUMMARY The screenshots of applications shown in the preview of grid based task switched are blurred. I understand these are just suggestive images, but since they are blurred and look like have artefacts from bad scaling, they give the impression that a low quality jpg is used. it would be good to have more clear images. STEPS TO REPRODUCE 1. Go to system settings and search for task switcher. 2. Choose grid dropdown from the list of task switcher in the resulting page 3. Click on the image icon to see the preview of grid task switcher I am attaching a screenshot of the preview. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446758] Crash krita 5 beta 5 in macOS Big Sur 11.5 after add gradient map filter layer, changing colors and click OK in macOS color selector "Colors"
https://bugs.kde.org/show_bug.cgi?id=446758 vanyossi changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/ae98fed60 |hics/krita/commit/b9f23ff6c |da7ec70bcb9d1ba4645835b2246 |7e7a8d0bae05aaf13ad14197e83 |bf19|5144 --- Comment #3 from vanyossi --- Git commit b9f23ff6c7e7a8d0bae05aaf13ad14197e835144 by Ivan Yossi. Committed on 10/12/2021 at 02:52. Pushed by ivany into branch 'krita/5.0'. Fix crash when color selector is closed after the parent Widget (macOS) The fix is not needed on Linux since the color selector is modal. Since there is utility in having the color dialog around this patch closes the color dialog in case the parent dialog gets destroyed. Broken since refactor 18f73194ea48347cb510d19b53abc85cba19cd57 (cherry picked from commit ae98fed60da7ec70bcb9d1ba4645835b2246bf19) M +26 -17 libs/widgets/kis_color_button.cpp https://invent.kde.org/graphics/krita/commit/b9f23ff6c7e7a8d0bae05aaf13ad14197e835144 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446758] Crash krita 5 beta 5 in macOS Big Sur 11.5 after add gradient map filter layer, changing colors and click OK in macOS color selector "Colors"
https://bugs.kde.org/show_bug.cgi?id=446758 vanyossi changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/ae98fed60 ||da7ec70bcb9d1ba4645835b2246 ||bf19 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from vanyossi --- Git commit ae98fed60da7ec70bcb9d1ba4645835b2246bf19 by Ivan Yossi. Committed on 10/12/2021 at 02:51. Pushed by ivany into branch 'master'. Fix crash when color selector is closed after the parent Widget (macOS) The fix is not needed on Linux since the color selector is modal. Since there is utility in having the color dialog around this patch closes the color dialog in case the parent dialog gets destroyed. Broken since refactor 18f73194ea48347cb510d19b53abc85cba19cd57 M +26 -17 libs/widgets/kis_color_button.cpp https://invent.kde.org/graphics/krita/commit/ae98fed60da7ec70bcb9d1ba4645835b2246bf19 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446764] New: System settings crashes on startup
https://bugs.kde.org/show_bug.cgi?id=446764
Bug ID: 446764
Summary: System settings crashes on startup
Product: systemsettings
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: qydwhotm...@gmail.com
Target Milestone: ---
Application: systemsettings (5.23.80)
Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.5-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.80 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
After updating to the latest version, launch systemsettings, and the crash
handler appears.
The crash can be reproduced every time.
-- Backtrace:
Application: System Settings (systemsettings), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f438c0f0323 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f438c0a0366 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f438c0897d3 in __GI_abort () at abort.c:79
#10 0x7f438c54cfe7 in qt_message_fatal (message=...,
context=...) at global/qlogging.cpp:1914
#11 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7fff9f26a280, msg=msg@entry=0x7f438c039be8 "Failed to
initialize KCModuleQML") at global/qlogging.cpp:893
#12 0x7f438c01027e in
KCModuleQml::KCModuleQml(std::unique_ptr >, QWidget*, QList
const&) (this=, configModule=std::unique_ptr = {...}, parent=, args=, this=, configModule=std::unique_ptr = {...}, parent=, args=) at
/usr/src/debug/kcmutils-5.89.0git.20211204T165638~d82e565-ku.9.2.x86_64/src/kcmoduleqml.cpp:174
#13 0x7f438c015fe8 in KCModuleLoader::loadModule(KPluginMetaData const&,
QWidget*, QList const&) (metaData=..., parent=0x5646afd80d30,
args=...) at
/usr/src/debug/kcmutils-5.89.0git.20211204T165638~d82e565-ku.9.2.x86_64/src/kcmoduleloader.cpp:87
#14 0x7f438c018d1e in KCModuleProxyPrivate::loadModule()
(this=this@entry=0x5646afd80e70) at
/usr/src/debug/kcmutils-5.89.0git.20211204T165638~d82e565-ku.9.2.x86_64/src/kcmoduleproxy.cpp:115
#15 0x7f438c0192f8 in KCModuleProxy::realModule() const
(this=this@entry=0x5646afd80d30) at
/usr/src/debug/kcmutils-5.89.0git.20211204T165638~d82e565-ku.9.2.x86_64/src/kcmoduleproxy.cpp:59
#16 0x7f438ddeb782 in ModuleView::updatePageIconHeader(KPageWidgetItem*,
bool) (this=this@entry=0x5646af1ed050, page=page@entry=0x5646afd80cd0,
light=light@entry=true) at
/usr/src/debug/systemsettings5-5.23.80git.20211204T210925~2a64b6d8-ku.47.2.x86_64/core/ModuleView.cpp:283
#17 0x7f438dded662 in ModuleView::addModule(MenuItem*, QStringList const&)
(this=this@entry=0x5646af1ed050, item=, args=...) at
/usr/src/debug/systemsettings5-5.23.80git.20211204T210925~2a64b6d8-ku.47.2.x86_64/core/ModuleView.cpp:260
#18 0x7f438ddedee0 in ModuleView::loadModule(QModelIndex const&,
QStringList const&) (args=..., menuItem=..., this=0x5646af1ed050) at
/usr/src/debug/systemsettings5-5.23.80git.20211204T210925~2a64b6d8-ku.47.2.x86_64/core/ModuleView.cpp:218
#19 0x7f43504a4a1b in SidebarMode::initWidget()
(this=this@entry=0x5646af149eb0) at
/usr/src/debug/systemsettings5-5.23.80git.20211204T210925~2a64b6d8-ku.47.2.x86_64/sidebar/SidebarMode.cpp:861
#20 0x7f43504a5f59 in SidebarMode::mainWidget() (this=0x5646af149eb0) at
/usr/src/debug/systemsettings5-5.23.80git.20211204T210925~2a64b6d8-ku.47.2.x86_64/sidebar/SidebarMode.cpp:316
#21 0x5646acd24bc8 in SettingsBase::changePlugin() (this=0x5646aeddf150) at
/usr/src/debug/systemsettings5-5.23.80git.20211204T210925~2a64b6d8-ku.47.2.x86_64/app/SettingsBase.cpp:336
#22 0x5646acd28762 in SettingsBase::initApplication() (this=0x5646aeddf150)
at
/usr/src/debug/systemsettings5-5.23.80git.20211204T210925~2a64b6d8-ku.47.2.x86_64/app/SettingsBase.cpp:139
#23 0x7f438c798fee in QObject::event(QEvent*) (this=0x5646aeddf150,
e=0x5646af317590) at kernel/qobject.cpp:1314
#24 0x7f438dd9a149 in KXmlGuiWindow::event(QEvent*) (this=0x5646aeddf150,
ev=0x5646af317590) at
/usr/src/debug/kxmlgui-5.89.0git.20211204T170535~11c9cc80-ku.4.2.x86_64/src/kxmlguiwindow.cpp:219
#25 0x7f438d41ea7f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5646aeddf150, e=0x5646af317590) at
kernel/qapplication.cpp:3632
#26 0x7f438c76c9fa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5646aeddf150, event=0x5646af317590) at
kernel/qcoreapplication.cpp:1064
#27 0x7f438c76fa47 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x5646aec68480) at
[plasma-pa] [Bug 446011] Volume up / down animation sound cause audio to be distorted
https://bugs.kde.org/show_bug.cgi?id=446011 André Martins changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #6 from André Martins --- The issue is now fixed. I don't believe it was a bug from KDE but from alsa. Thanks for the help! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446758] Crash krita 5 beta 5 in macOS Big Sur 11.5 after add gradient map filter layer, changing colors and click OK in macOS color selector "Colors"
https://bugs.kde.org/show_bug.cgi?id=446758 vanyossi changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446758] Crash krita 5 beta 5 in macOS Big Sur 11.5 after add gradient map filter layer, changing colors and click OK in macOS color selector "Colors"
https://bugs.kde.org/show_bug.cgi?id=446758 vanyossi changed: What|Removed |Added Ever confirmed|0 |1 CC||ghe...@gmail.com Status|REPORTED|ASSIGNED --- Comment #1 from vanyossi --- I can confirm this is crashing if color selector is closed after closing gradient filter editor. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446763] New: "rounding down" of color #414550
https://bugs.kde.org/show_bug.cgi?id=446763 Bug ID: 446763 Summary: "rounding down" of color #414550 Product: kdenlive Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: gaspard...@gmail.com Target Milestone: --- Created attachment 144414 --> https://bugs.kde.org/attachment.cgi?id=144414=edit video resulting from the described steps SUMMARY Appimage version, Ubuntu 18.04. When adding a clip with the color #414550 to KDenlive, #41454f is used instead. Other colors are affected too, like #40454f changing to #3f454f, and presumably others. STEPS TO REPRODUCE 1. open a new project, any colorspace. 2. add a color clip with the color #414550 3. add the clip to the timeline 4. Render to mp4, default settings 5. measure the color of the resulting video OBSERVED RESULT The resulting video has a color of #41454f EXPECTED RESULT The resulting video should have a color of #414550 SOFTWARE/OS VERSIONS Ubuntu 18.04 / Gnome 3.28.2 KDE Plasma Version: KDE Frameworks Version: 5.81.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION This is presumably not happening at the level of the render, since both the clip and project monito window also show a value of #41454f, although the clip preview in the clip bin does show #414550 as it should. This also happens when adding a PNG as a clip, although color source is the most straightforward way to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446762] Task manager glitches in short panels
https://bugs.kde.org/show_bug.cgi?id=446762 --- Comment #1 from Orhan --- Created attachment 144413 --> https://bugs.kde.org/attachment.cgi?id=144413=edit huge empty spacer -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446762] New: Task manager glitches in short panels
https://bugs.kde.org/show_bug.cgi?id=446762 Bug ID: 446762 Summary: Task manager glitches in short panels Product: plasmashell Version: 5.23.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: diamond82ber...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 144412 --> https://bugs.kde.org/attachment.cgi?id=144412=edit no margin + no spacer SUMMARY In limited space(dock-like panel / panel sliders minimum) icons-only task manager doesn't work consistent. The empty space after manager sometimes get lost, sometimes get meaninglessly big. This makes dock-like panel experience awful STEPS TO REPRODUCE 1. Minimize panel width 2. Open some pinned and unpinned applications 3. Close some of them OBSERVED RESULT no margin between icons spacer lost huge spacer EXPECTED RESULT no spacer and consistent action -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446761] New: Add clearer option to enable 24 hour clock
https://bugs.kde.org/show_bug.cgi?id=446761 Bug ID: 446761 Summary: Add clearer option to enable 24 hour clock Product: systemsettings Version: 5.23.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_clock Assignee: p...@taniwha.com Reporter: evanmoh...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** In the current version of KDE, there is no simple toggle to enable the 24 hour clock globally. There is a way, but it is hidden away behind the undescriptive name "Default (C)". This setting is found in Settings>Regional Settings>Formats, while a person would reasonably expect to find it instead under the Date and Time section. *** OBSERVED RESULT Unintuitive process to change the time globally to the 24 hour clock. The option is found in Settings>Regional Settings>Formats under the unclear name "Default (C)". Note: this option wasn't even the default, the default option was set to "No change". EXPECTED RESULT There would be a simple toggle to enable 24 hour clock under Settings>Regional Settings>Date & Time> Date and Time. SOFTWARE/OS VERSIONS Linux: 5.15.7 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland on VMs (VMWare, VirtualBox, ...)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #20 from Andrey --- I can't test on amdgpu graphics. Anyone else please confirm. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446674] In Wayland with fractional scaling fonts and images are blurry from downscaling
https://bugs.kde.org/show_bug.cgi?id=446674 Alex changed: What|Removed |Added CC||alex...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443968] When switching activities, sometimes a tiny "Plasma Desktop Workspace" window appears
https://bugs.kde.org/show_bug.cgi?id=443968 Craig Howard changed: What|Removed |Added CC||k...@choward.ca -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 446760] New: Ark fails to open ISO that can be mounted otherwise
https://bugs.kde.org/show_bug.cgi?id=446760 Bug ID: 446760 Summary: Ark fails to open ISO that can be mounted otherwise Product: ark Version: 21.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugins Assignee: rthoms...@gmail.com Reporter: spzaku...@gmail.com CC: aa...@kde.org, elvis.angelac...@kde.org 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. Download ISO from here: https://archive.org/details/Power-Drive-DOS-1994 2. Try to open ISO with Ark 3. OBSERVED RESULT Ark says "The archive you're trying to open is corrupt." Even if you tell it to open read-only, it doesn't show anything. EXPECTED RESULT This is a valid ISO that should be capable of being opened normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.23 (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88 Qt Version: 5.15.3 ADDITIONAL INFORMATION The blog post here: https://multimedia.cx/eggs/iso-9660-compromise-part-2-finding-root/ actually diagnoses the problem, and figures out why some software fails on loading the ISO, and others don't. The actual files are also available as a ZIP file in the download link above. You can successfully mount the ISO using the right click menu option in KDE "Mount ISO". Here's the file listing I got using that option: ls -la total 705 dr-x-- 1 steve steve 2048 Nov 21 1994 . drwxr-x---+ 3 root root4096 Dec 9 18:54 .. -r 1 steve steve 14 Nov 8 1991 batch1.bat -r 1 steve steve148 Nov 8 1991 batch2.bat dr-x-- 1 steve steve 2048 Nov 2 1994 cd -r 1 steve steve 10080 Dec 22 1993 emuset.exe dr-x-- 1 steve steve 2048 Nov 8 1991 g -r 1 steve steve 19128 Nov 2 1994 install.exe -r 1 steve steve 92571 Dec 22 1993 megaem.exe -r 1 steve steve 44 Nov 1 1991 pd.bat -r 1 steve steve 566031 Nov 21 1991 pdrive.exe dr-x-- 1 steve steve 2048 Nov 17 1994 s -r 1 steve steve 19128 Nov 2 1994 sound.exe Mounting as a loop device also works: sudo mount -t iso9660 -o loop ~/Downloads/Power-Drive.iso ~/games/iso -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442844] plasmashell leaks a little bit of memory with every notification displayed (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=442844 Aleix Pol changed: What|Removed |Added Latest Commit||https://invent.kde.org/qt/q ||t/qtwayland/commit/eb422ab5 ||e07498a7a8d086f6a942ee35ab3 ||c9776 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #29 from Aleix Pol --- Git commit eb422ab5e07498a7a8d086f6a942ee35ab3c9776 by Aleix Pol. Committed on 09/12/2021 at 16:38. Pushed by aacid into branch 'kde/5.15'. Fix backport, context destruction was omitted When cherry-picking for 9df11e79b46c77d8c83f765b2a8e85b639fd55a2, this line got removed when rebasing the patch, which created a leak. Change-Id: Id00e8b194dcd910c5f01ce9d2cc318f96a4129a2 M +1-0src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp https://invent.kde.org/qt/qt/qtwayland/commit/eb422ab5e07498a7a8d086f6a942ee35ab3c9776 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 359072] web browser widget doesn't understand web shortcuts
https://bugs.kde.org/show_bug.cgi?id=359072 Felipe Kinoshita changed: What|Removed |Added CC||kinof...@gmail.com Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Felipe Kinoshita --- It does understand addresses without http:// now! :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland on VMs (VMWare, VirtualBox, ...)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #19 from nttkde --- I can still see the glitchy cursor in VirtualBox with KDE Neon guest (Plasma 5.23.4, Wayland). Host has amdgpu graphics. Someone else has similar issues in Wayland too: https://www.reddit.com/r/kde/comments/r1csff/glitchy_cursor_on_wayland/ , I'm not sure if it was in VM or not -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446759] New: Implement Mixbox, a "Practical Pigment Mixing for Digital Painting"
https://bugs.kde.org/show_bug.cgi?id=446759 Bug ID: 446759 Summary: Implement Mixbox, a "Practical Pigment Mixing for Digital Painting" Product: krita Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: jcaique...@gmail.com Target Milestone: --- Mixbox is a pigment mixing black-box. You pass RGB colors in and get the mixed RGB out. Internally, Mixbox treats the colors as if they were made of actual real-world pigments. It uses the Kubelka & Munk theory to predict the color of the resulting mixture. This way, Mixbox achieves that blue and yellow mix to green, the same way real pigments do. Source Code: https://github.com/scrtwpns/pigment-mixing The research paper: https://scrtwpns.com/mixbox.pdf Video demonstration: https://youtu.be/9egCAxhOHg4 Talk: https://youtu.be/_qa5iWdfNKg It has a non-commercial license, and according to their website "Being this simple plug-and-play module, Mixbox can be easily integrated into any painting software." So I trust that is easy to implement. (Forgive me if I didn't tag the correct component.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446758] New: Crash krita 5 beta 5 in macOS Big Sur 11.5 after add gradient map filter layer, changing colors and click OK in macOS color selector "Colors"
https://bugs.kde.org/show_bug.cgi?id=446758 Bug ID: 446758 Summary: Crash krita 5 beta 5 in macOS Big Sur 11.5 after add gradient map filter layer, changing colors and click OK in macOS color selector "Colors" Product: krita Version: 5.0.0-beta5 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: shemi...@gmail.com Target Milestone: --- Created attachment 144411 --> https://bugs.kde.org/attachment.cgi?id=144411=edit macOS report information Hi! Krita 5 beta 5 in macOS Big Sur 11.5 crashed after add gradient map filter layer and changing colors. Thanks for attention! STEPS TO REPRODUCE 1. Add filter layer 2. Choose gradient map filter 3. Change colors with macOS color selector "Colors" 4. Click OK in filter layer properties 5. Click OK in macOS color selector "Colors" OBSERVED RESULT Crash of application EXPECTED RESULT No crash SOFTWARE/OS VERSIONS krita: 5 beta 5 macOS: Big Sur 11.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446588] Brush preset reimport (same file) asks for overwrite, does not recognize that the file is the same md5sum.
https://bugs.kde.org/show_bug.cgi?id=446588 --- Comment #5 from Eoin O'Neill --- (In reply to Dmitry Kazakov from comment #3) > There seems to be two problems: > > 1) The contents of two import functions > KisResourceUserOperations::importResourceFileWithUserInput() and > ResourceImporter::importResources() has diverged, so they do different > things to check the resource deduplication. I guess this should be taken care of soon. It's strange because, during the last testing phase, I don't remember having an issue like this running through Tiar's testing parameters. Maybe I'll take a look through the importing resource pipeline today to see how easy this will be to resolve. > 3) I guess, in case the resource exists in the database, but **inactive** or > **overriden by a new version**, then the user should also be asked about > that. Though it will change the strings. That is an interesting point, and one that we won't be able to easily handle in Krita 5 since we're in a string freeze. In the case that something like this happens we should ask the user whether they want to revert a resource to the previous version, or change the "file name" to create a new branch of the resource itself. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438565] Mute audio icon appear on all pinned but not running icons when using Pipewire
https://bugs.kde.org/show_bug.cgi?id=438565 Nicolas Fella changed: What|Removed |Added CC||thescim...@gmail.com --- Comment #23 from Nicolas Fella --- *** Bug 446732 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446732] audio widget multiplies himself
https://bugs.kde.org/show_bug.cgi?id=446732 Nicolas Fella changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||nicolas.fe...@gmx.de --- Comment #3 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 438565 *** -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 446747] Kalendar crashes at startup
https://bugs.kde.org/show_bug.cgi?id=446747 --- Comment #2 from david.cais...@gmail.com --- (In reply to Claudio Cambra from comment #1) > Are you using the git master version? This might be caused by issues with > caching -- see bug #444617 for a possible workaround -- deleting > /home/your_username/.cache/KDE/kalendar/ > > https://bugs.kde.org/show_bug.cgi?id=444617 Deleting /home/my_username/.cache/KDE/kalendar/ didn't solve the issue. However, I removed the two following repositories : https://download.opensuse.org/repositories/home:KaratekHD:kirigami/openSUSE_Tumbleweed/ home:KaratekHD:kirigami https://download.opensuse.org/repositories/home:andresbs:plasma-mobile/openSUSE_Tumbleweed/ plasma-mobile and installed the application using YaST Software from : https://apps.kde.org/kalendar/ And now kalendar launches. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417616] Crash closing nested kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=417616 Alex changed: What|Removed |Added CC||alex...@protonmail.com --- Comment #1 from Alex --- I have encountered a similar crash on Fedora 35, Plasma 5.23.3, I think it happened during shutdown. #0 0x00b1 in () #1 0x7fe7f0fd7623 in QScopedPointerDeleter::cleanup(KWin::DpmsInputEventFilter*) (pointer=) at /usr/include/qt5/QtCore/qscopedpointer.h:52 #2 QScopedPointer >::~QScopedPointer() (this=0x5601b650ddc0, this=) at /usr/include/qt5/QtCore/qscopedpointer.h:107 #3 KWin::DrmBackend::~DrmBackend() (this=0x5601b650dd10, this=) at /usr/src/debug/kwin-5.23.3-1.fc35.x86_64/src/plugins/platforms/drm/drm_backend.cpp:80 #4 0x7fe7f0fd779d in KWin::DrmBackend::~DrmBackend() (this=0x5601b650dd10, this=) at /usr/src/debug/kwin-5.23.3-1.fc35.x86_64/src/plugins/platforms/drm/drm_backend.cpp:80 #5 0x7fe806443197 in KWin::Application::destroyPlatform() (this=this@entry=0x7ffe4f580760) at /usr/src/debug/kwin-5.23.3-1.fc35.x86_64/src/main.cpp:176 #6 0x7fe8064446b8 in KWin::Application::~Application() (this=0x7ffe4f580760, this=) at /usr/src/debug/kwin-5.23.3-1.fc35.x86_64/src/main.cpp:160 #7 0x5601b5da0748 in main(int, char**) (argc=, argv=) at /usr/src/debug/kwin-5.23.3-1.fc35.x86_64/src/main_wayland.cpp:746 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446704] Resource chooser's preset columns draw their horizontal slider out of viewport
https://bugs.kde.org/show_bug.cgi?id=446704 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1215 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446705] Importing the same bundle with a different filename doesn't deduplicate resources
https://bugs.kde.org/show_bug.cgi?id=446705 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1215 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446702] Bundle disable and enable with one of its tags selected doesn't repopulate the resource chooser completely
https://bugs.kde.org/show_bug.cgi?id=446702 --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1215 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446706] Layer styles can be imported twice if import is done from the Resource Libraries dialog
https://bugs.kde.org/show_bug.cgi?id=446706 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1215 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446757] New: Appimage update does not work, underlying mechanism is either not present or not executable.
https://bugs.kde.org/show_bug.cgi?id=446757 Bug ID: 446757 Summary: Appimage update does not work, underlying mechanism is either not present or not executable. Product: krita Version: 5.0.0-beta2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- SUMMARY The appimages don't seem to provide their internal update mechanism anymore. Looking at the log, we can find the following: 09 Dec 2021 23:00:18 +0100: KisAppimageUpdater: AppImageUpdate (/tmp/.mount_krita-mJKum4/usr/bin/AppImageUpdate) was not found within the Krita appimage, or is not executable Krita Version: 5.0.0-beta2 (git 5771a7d) Languages: en_US, en, en_GB, en, nl, en_US, en Hidpi: false Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.4.0-91-generic Pretty Productname: KDE neon User - Plasma 25th Anniversary Edition Product Type: neon Product Version: 20.04 Desktop: KDE -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 446710] --clipboard commandline argument not recognised
https://bugs.kde.org/show_bug.cgi?id=446710 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/spectacle/-/merge_requests/110 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446631] Brush settings model sorts options by insertion instead of by category
https://bugs.kde.org/show_bug.cgi?id=446631 amyspark changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/f713b89c5 |hics/krita/commit/916796b9f |168b7f9cd15254734cde18928d4 |e1cf4d797da78b8dfea1dda393e |235e|474f --- Comment #4 from amyspark --- Git commit 916796b9fe1cf4d797da78b8dfea1dda393e474f by L. E. Segovia. Committed on 09/12/2021 at 22:01. Pushed by lsegovia into branch 'krita/5.0'. Workaround KisPaintOpOptionListModel sorting "bug" (cherry picked from commit f713b89c5168b7f9cd15254734cde18928d4235e) M +1-1plugins/paintops/mypaint/MyPaintPaintOpSettingsWidget.cpp https://invent.kde.org/graphics/krita/commit/916796b9fe1cf4d797da78b8dfea1dda393e474f -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 446756] New: Sound volume popup doesn't show percents over 100% (with Pipewire??)
https://bugs.kde.org/show_bug.cgi?id=446756 Bug ID: 446756 Summary: Sound volume popup doesn't show percents over 100% (with Pipewire??) Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: liubomi...@gmail.com Target Milestone: --- Created attachment 144410 --> https://bugs.kde.org/attachment.cgi?id=144410=edit pipewire sound level issue SUMMARY I'm using pipewire and in the audio volume tray applet i've checked "Raise maximum volume". Raising above 100% does show real volume in the tray applet, but does not show any number more than 100% in the popup. local/gst-plugin-pipewire 1:0.3.40-1 Multimedia graph framework - pipewire plugin local/pipewire 1:0.3.40-1 Low-latency audio/video router and processor local/pipewire-alsa 1:0.3.40-1 Low-latency audio/video router and processor - ALSA configuration local/pipewire-jack 1:0.3.40-1 Low-latency audio/video router and processor - JACK support local/pipewire-pulse 1:0.3.40-1 Low-latency audio/video router and processor - PulseAudio replacement local/wireplumber 0.4.5-2 Session / policy manager implementation for PipeWire OBSERVED RESULT See screenshot - real sound level is more than 100%. EXPECTED RESULT Real sound level shown, like say 115%. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.6-zen2-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445367] Adding a bundle with resource duplicated in disabled bundle disables the resource
https://bugs.kde.org/show_bug.cgi?id=445367 amyspark changed: What|Removed |Added Blocks||446705 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=446705 [Bug 446705] Importing the same bundle with a different filename doesn't deduplicate resources -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446705] Importing the same bundle with a different filename doesn't deduplicate resources
https://bugs.kde.org/show_bug.cgi?id=446705 amyspark changed: What|Removed |Added Depends on||445367 CC||dimul...@gmail.com --- Comment #2 from amyspark --- It's a byproduct of bug 445367. The model considers duplicates too narrowly. (cc Dmitry, I'll need your review on the fix) Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=445367 [Bug 445367] Adding a bundle with resource duplicated in disabled bundle disables the resource -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 446582] Option "Press screenshot key to: Take a new Screenshot" seams doesn't work
https://bugs.kde.org/show_bug.cgi?id=446582 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #2 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #1) > Works for me. For me doesn't. I made another tests and for me it looks like messed. I mean various combination of settings gives unexpected results. Preset. Key PrintScreen is configured like "Launch Spectacle". And "screenshot key in option "When Spectacle is running"" this is PrintScreen. Let see below 3 scenarios. (not all fine) Launch Spectacle by "Application launcher" Notice that screenshot was made before My first setting is as following: 1. Three options are set like: "When launching Spectacle: Do not take a screenshot automatically" "When Spectacle is running: Open a new Spectacle Window" "Remember selected area: Until Spectacle is closed" 2. Apply, OK, close application 3. Press PrintScreen Result: Spectacle started with last took screenshot. I expected nothing in left view (ERROR) 4. Press PrintScreen Result: New instance of Spectacle was launching, so all is as expected (OK) 5. Close application (all fine) Launch Spectacle by "Application launcher" Still I have the same screenshot in buffer (I can see it in left view) My second setting is as following: 1. Three options are set like: "When launching Spectacle: Take full screen screenshot" "When Spectacle is running: Open a new Spectacle Window" "Remember selected area: Until Spectacle is closed" 2. Apply, OK, close application 3. Press PrintScreen Result: Spectacle started with foll screen screenshot, so all is as expected (OK) 4. Press PrintScreen Result: New instance of Spectacle was launching, so all is as expected (OK) 5. Close application (not all fine) Launch Spectacle by "Application launcher" I have last screenshot in buffer (I can see it in left view), so full screen My third setting is as following: 1. Three options are set like: "When launching Spectacle: Do not take a screenshot automatically" "When Spectacle is running: Take a new Screenshot" "Remember selected area: Until Spectacle is closed" 2. Apply, OK, close application 3. Press PrintScreen Result: Spectacle started with empty buffer (nothing in left view), so all is as expected 4. Press PrintScreen Result: New instance of Spectacle was launching, with empty buffer (nothing in left view). Of course I expected to Spectacle taking screenshot. (ERROR) 5. Close application Spectacle version: 22.03.70 Neon Unstable updated at 2021-12-06 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446702] Bundle disable and enable with one of its tags selected doesn't repopulate the resource chooser completely
https://bugs.kde.org/show_bug.cgi?id=446702 amyspark changed: What|Removed |Added CC||ha...@valdyas.org --- Comment #4 from amyspark --- This is caused by KisTagChooserWidget::tagChanged being invoked with a tag value of -1, because of the storage model removing the currently selected tag. The fix is to ensure that in such cases, the tag is instead reset to "All", which is also done when it is deleted by the user. However, adding the index reset on that function triggers a big (5 sec?) hangup because of what seems is a loop or race condition between the initial signal and the re-signaling caused by the forced index reset. Halla, perhaps you know other way around it? -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #19 from Frank Kruger --- Created attachment 144409 --> https://bugs.kde.org/attachment.cgi?id=144409=edit Backtrace KGet 21.08.3 Crash (In reply to Frank Kruger from comment #18) > Just tried to download current openSUSE Tumbleweed ISO via > https://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64- > Current.iso.meta4 and it crashes again. Corresponding crash report attached. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 446710] --clipboard commandline argument not recognised
https://bugs.kde.org/show_bug.cgi?id=446710 --- Comment #2 from Antonio Prcela --- Confirmed here too Interesting that it works when -c used instead of --clipboard. Will take a look as soon as I have more time -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414959] Send by email with Thunderbird does not work anymore
https://bugs.kde.org/show_bug.cgi?id=414959 --- Comment #23 from Maik Qualmann --- Here under openSUSE Tumbleweed with a KF5 Plasma Desktop and the AppImage I get this error message: /usr/lib64/thunderbird/thunderbird-bin: symbol lookup error: /lib64/libgio-2.0.so.0: undefined symbol: g_module_open_full With my native digiKam version, opening Thunderbird works without any problems. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414959] Send by email with Thunderbird does not work anymore
https://bugs.kde.org/show_bug.cgi?id=414959 --- Comment #22 from Maik Qualmann --- A snap package is not a native digiKam version. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446755] New: Hitbox For Curve Widget Vertices Too Small
https://bugs.kde.org/show_bug.cgi?id=446755 Bug ID: 446755 Summary: Hitbox For Curve Widget Vertices Too Small Product: krita Version: 4.4.8 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: joe...@gmail.com Target Milestone: --- SUMMARY The hit boxes when editing curve vertices in, for example, the Color Adjustment Filter are far too small. I'm constantly creating new points where I don't want them. I can see two possibly causes: either the hitboxes are genuinely too small, or they aren't taking DPI into account on Windows (or possibly both). SOFTWARE/OS VERSIONS Windows: 11 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433219] Can't sign into my Microsoft account in order to access OneDrive
https://bugs.kde.org/show_bug.cgi?id=433219 Maik Qualmann changed: What|Removed |Added CC||nic...@tuxfamily.org --- Comment #5 from Maik Qualmann --- *** Bug 446750 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446750] Can't export to onedrive: unable to login then crash
https://bugs.kde.org/show_bug.cgi?id=446750 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #5 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 433219 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446750] Can't export to onedrive: unable to login then crash
https://bugs.kde.org/show_bug.cgi?id=446750 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #4 from Maik Qualmann --- The problem is known and will not work with the AppImage either. OnDrive does not work with the outdated QWebKit browser. Here native digiKam with QWebEngine works. Maik -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 446754] New: Improve error codes from alloc functions under memcheck
https://bugs.kde.org/show_bug.cgi?id=446754 Bug ID: 446754 Summary: Improve error codes from alloc functions under memcheck Product: valgrind Version: 3.19 GIT Platform: Compiled Sources OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: pjfl...@wanadoo.fr Target Milestone: --- Created attachment 144408 --> https://bugs.kde.org/attachment.cgi?id=144408=edit more errno for allocs This commit commit 1c9a0bf58a47e855e6e5bf78a30bcee0af835804 Author: Mark Wielaard Date: Fri Feb 12 23:29:34 2021 +0100 PR217695 malloc/calloc/realloc/memalign failure doesn't set errno to ENOMEM started adding some errno functionality to Linux. The attached patch a) covers a couple more functions b) adds EINVAL for aligned variants c) adds FreeBSD and Solaris Not yet tested on Linux or Solaris. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446750] Can't export to onedrive: unable to login then crash
https://bugs.kde.org/show_bug.cgi?id=446750 caulier.gil...@gmail.com changed: What|Removed |Added Version|7.3.0 |7.4.0 CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- Please run the AppImage binary with the "debug" argument. This will run digiKam in the gdb debugger. When it crash, a prompt will appear. Enter "bt" to get a back-trace. To quit, enter "q". Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446753] Enable the Overview effect by default
https://bugs.kde.org/show_bug.cgi?id=446753 Vlad Zahorodnii changed: What|Removed |Added Depends on||445930 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=445930 [Bug 445930] Does not appear as an option in the Task Manager settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445930] Does not appear as an option in the Task Manager settings
https://bugs.kde.org/show_bug.cgi?id=445930 Vlad Zahorodnii changed: What|Removed |Added Blocks||446753 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=446753 [Bug 446753] Enable the Overview effect by default -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446753] Enable the Overview effect by default
https://bugs.kde.org/show_bug.cgi?id=446753 Vlad Zahorodnii changed: What|Removed |Added Depends on||444381 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=444381 [Bug 444381] KWin sometimes crashes in KWin::EffectQuickView::update() when entering overview -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444381] KWin sometimes crashes in KWin::EffectQuickView::update() when entering overview
https://bugs.kde.org/show_bug.cgi?id=444381 Vlad Zahorodnii changed: What|Removed |Added Blocks||446753 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=446753 [Bug 446753] Enable the Overview effect by default -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446753] New: Enable the Overview effect by default
https://bugs.kde.org/show_bug.cgi?id=446753 Bug ID: 446753 Summary: Enable the Overview effect by default Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: vlad.zahorod...@kde.org Target Milestone: --- Meta bug report to track issues that block enabling the overview effect by default. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414959] Send by email with Thunderbird does not work anymore
https://bugs.kde.org/show_bug.cgi?id=414959 --- Comment #21 from hp --- (In reply to Maik Qualmann from comment #20) > There is a native digiKam-7.3.0 package for Ubuntu, I have never tested it > myself. please try: > > https://mail.kde.org/pipermail/digikam-users/2021-November/032922.html > > You could try using Rob Savoury's digikam PPA here > https://launchpad.net/~savoury1/+archive/ubuntu/digikam > > Maik The Ubuntu native Snap package has the same problem beside others like no access to file manager! Hp -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 446747] Kalendar crashes at startup
https://bugs.kde.org/show_bug.cgi?id=446747 --- Comment #1 from Claudio Cambra --- Are you using the git master version? This might be caused by issues with caching -- see bug #444617 for a possible workaround -- deleting /home/your_username/.cache/KDE/kalendar/ https://bugs.kde.org/show_bug.cgi?id=444617 -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #18 from Frank Kruger --- Just tried to download current openSUSE Tumbleweed ISO via https://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Current.iso.meta4 and it crashes again. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 418968] Network speed in bits per second
https://bugs.kde.org/show_bug.cgi?id=418968 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-systemmonitor/-/merge_requests/174 -- You are receiving this mail because: You are watching all bug changes.
[kronometer] [Bug 446752] New: Add widget
https://bugs.kde.org/show_bug.cgi?id=446752 Bug ID: 446752 Summary: Add widget Product: kronometer Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: niels1...@gmail.com Target Milestone: --- For me, I would really want a widget for this application. I speak in public regularly and would find it very useful to see how long I am already speaking in the panel. This way I don't have to switch applications or use my phone as a chronometer. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446750] Can't export to onedrive: unable to login then crash
https://bugs.kde.org/show_bug.cgi?id=446750 --- Comment #2 from Nicofo --- additional info: digikam appimage 7.4.0 starts with following command line: LD_PRELOAD=/usr/lib64/libssl.so.1.1:/usr/lib64/libcrypto.so.1.1 ./digiKam-7.4.0-20211209T121203-x86-64.appimage But then the behaviour is excatly the same than 7.3.0 (empty log in window and crash if I click on "Change account"). So problem reproducible with 7.3.0 et 7.4.0. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566
--- Comment #9 from Fred ---
Created attachment 144407
--> https://bugs.kde.org/attachment.cgi?id=144407=edit
widened tag column after 'X' on false entry
It appears that the false tag entry ('men undies') will be removed from the
split transaction through 'X'. However, when confirmed and saved, it's still
there - ^confused^
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566 --- Comment #8 from Fred --- (In reply to Thomas Baumgart from comment #6) > Try to widen the tag column in the split editor. I agree, it makes a > difference if you have a split transaction or a normal one. I tried to > duplicate your problem with the latest stable version (5.12.) and have no > problems to a) remove the tag from the split and b) delete the tag > afterwards. Chances are that the problem has been fixed in the meantime. Thomas: I widened the column and when I click on the 'X' it appears that it would delete the false tag entry (see new screenshot) However when I confirm the changes (OK button), save the transaction and open it for edit again, it's still there. Was the bug reported before so that it got fixed? Thanks Fred -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #17 from Wolfgang Bauer --- PS: @Kārlis Kavacis The link in comment#0 unfortunately was obfuscated (by bugzilla I guess), so maybe you could send it to me in private? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 446751] New: Akonadi POP3 Resource failed to connect to pop3 gmail
https://bugs.kde.org/show_bug.cgi?id=446751 Bug ID: 446751 Summary: Akonadi POP3 Resource failed to connect to pop3 gmail Product: Akonadi Version: 5.19.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: POP3 Resource Assignee: kdepim-b...@kde.org Reporter: o.g.m.bell...@gmail.com CC: aa...@kde.org 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. connect to kontact / kmail 2. pick up the mail 3. OBSERVED RESULT Unable to login to the server "pop.gmail.com". Could not login to pop.gmail.com. The server terminated the connection immediately. org.kde.pim.pop3resource: == ERROR DURING POP3 SYNC == org.kde.pim.pop3resource: "Unable to login to the server \"pop.gmail.com\".\nCould not login to pop.gmail.com.\n\nThe server terminated the connectionimmediately." org.kde.pim.pop3resource: UID list from server is not valid. org.kde.pim.pop3resource: == ERROR DURING POP3 SYNC == org.kde.pim.pop3resource: "Unable to login to the server \"pop.gmail.com\".\nCould not login to pop.gmail.com.\n\nThe server terminated the connectionimmediately." EXPECTED RESULT emails are raised, of course… SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-59.37-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 7.6 Gio of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444460] Overview shows Plasma icon and re-arranges itself when a notification appears
https://bugs.kde.org/show_bug.cgi?id=60 --- Comment #5 from Nate Graham --- Yes, it's 100% reproducible for me on both the X11 and Wayland sessions by running `sleep 3 && notify-send foo bar` and then opening the overview immediately. Similarly, I can reproduce Bug 446624 by hitting the Meta key while the Overview is open. I don't have any window rules set up. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446750] Can't export to onedrive: unable to login then crash
https://bugs.kde.org/show_bug.cgi?id=446750 --- Comment #1 from Nicofo --- Created attachment 144406 --> https://bugs.kde.org/attachment.cgi?id=144406=edit Digikam 7.3.0 crash log When I click on "Change account" (see at the end of attached file): unknown: UNLINK to Onedrive /tmp/.mount_digiKaO9UeHb/AppRun: line 172: 12759 Segmentation fault (core dumped) digikam $@ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446750] New: Can't export to onedrive: unable to login then crash
https://bugs.kde.org/show_bug.cgi?id=446750 Bug ID: 446750 Summary: Can't export to onedrive: unable to login then crash Product: digikam Version: 7.3.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-OneDrive Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- Created attachment 144405 --> https://bugs.kde.org/attachment.cgi?id=144405=edit Empty login window to onedrive SUMMARY When trying to export to Onedrive, an empty window opens (see attachment). Therefore it is not possible to log in into Onedrive account. Besides that, if I close that empty window and click on "Change account" of the "Export to Onedrive" window, Digikam crashes. See logs attached SYSTEM Fedora 35 Appimage digiKam-7.3.0-x86-64.appimage Note: I also tried with latest digiKam-7.4.0-20211209T121203-x86-64.appimage -> but it crashes immediately: $ ./digiKam-7.4.0-20211209T121203-x86-64.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"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0 digikam: /tmp/.mount_digiKaJSufa6/usr/lib/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libk5crypto.so.3) I already had similar problem with Onedrive (see bug #401377) but it was solved 2 years ago. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446732] audio widget multiplies himself
https://bugs.kde.org/show_bug.cgi?id=446732 --- Comment #2 from thescim...@gmail.com --- (In reply to Chris Holland from comment #1) > Sounds like bug https://bugs.kde.org/show_bug.cgi?id=438565 > > This belongs under Product=plasmashell under the Component="Task Manager and > ..." but i'm not using pipewire -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566 --- Comment #7 from Fred --- (In reply to Jack from comment #5) > Please be a bit more specific about why you can't remove the tag. What > happens when you click on the "X" to the left of "mens undies"? Hi Jack, I can't be more specific. What happens when I click on the 'X" : Nothing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446694] desktop and panel all black
https://bugs.kde.org/show_bug.cgi?id=446694 --- Comment #4 from thescim...@gmail.com --- and no i have one monitor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446694] desktop and panel all black
https://bugs.kde.org/show_bug.cgi?id=446694 --- Comment #3 from thescim...@gmail.com --- (In reply to Nate Graham from comment #1) > What were you doing when this happened? Can you please fill in the "Steps to > reproduce" section? > > Do you have multiple monitors? > > Do you see any plasmashell crashes at the top of the output when you run > `coredumpctl --reverse` in a terminal window? If so, can you get a backtrace > from the latest one using the instructions at > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? > > Thanks! i don't know how to reproduce it i just use the menu to search thing and all crush it's casual -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #16 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #15) > If you consider them private, maybe we can arrange some way outside this > bugzilla... That also applies to Kārlis Kavacis of course. In the end, I only want to have an URL with which I can reproduce the crash. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446663] Brush stutters at the start of the stroke
https://bugs.kde.org/show_bug.cgi?id=446663 --- Comment #5 from acc4commissi...@gmail.com --- I found the biggest culprit. It was the Randomness option(the delay happens when it's set to other than 0) and the Density option(the delay happens when it's set to other than 100) that I was using. Although the delay still isn't completely gone even with optimal settings in both. There still seems to be many options contribute to the stutter at the start of the stroke(to be exact, an inherent short delay between you start a stroke and the actual stroke rendering starts). Using different Mask Type also makes differences. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #15 from Wolfgang Bauer --- (In reply to Frank Kruger from comment #14) > Yep, it solves it, kget starts and downloads as expected, without any crash. > Thx. Good. Could you maybe share the files in the old directory? If you consider them private, maybe we can arrange some way outside this bugzilla... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 446738] Multi-page thumbnail view
https://bugs.kde.org/show_bug.cgi?id=446738 --- Comment #4 from Peter Bacon --- (In reply to Nate Graham from comment #3) > Hmm, intuitiveness doesn't seem relevant here and responsiveness is > typically a factor of performance and animation easing curves, which also > aren't factors here. > > When you say "efficient", do you mean that the scroll speed is effectively > faster because each scroll "tick" moves down by three pages rather than one? Yes, sorry, I guess what it boils down to it being handy to be able to preview 10-40 pages at once (depending on monitor size and resolution) I generally keep a 2x5 grid open on the sidebar when using djview. And just never find myself using the sidebar in Okular. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #14 from Frank Kruger --- (In reply to Wolfgang Bauer from comment #13) > (In reply to Wolfgang Bauer from comment #11) > > (In reply to Frank Kruger from comment #9) > > > (In reply to Wolfgang Bauer from comment #3) > > The main question is, what triggers the crash? > > My only guess so far is that it has to do with what filesystems are mounted. > As the crash reports are all in KMountPoint::mountType() from kio. > > But comment#5 suggests it depends on the URL... > > @Frank Kruger: > Does it help if you rename the directory "~/.local/share/kget/", so that > current downloads are no longer continued? Yep, it solves it, kget starts and downloads as expected, without any crash. Thx. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 446749] New: Running 'kalarm --list' in a terminal disables upcoming alarms and doesn't list enabled alarms.
https://bugs.kde.org/show_bug.cgi?id=446749 Bug ID: 446749 Summary: Running 'kalarm --list' in a terminal disables upcoming alarms and doesn't list enabled alarms. Product: kalarm Version: 3.3.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: sz.k...@gmail.com Target Milestone: --- SUMMARY Running 'kalarm --list' in a terminal disables upcoming alarms and doesn't list enabled alarms. STEPS TO REPRODUCE 1. have KAlarm running with an alarm scheduled (a command alarm in my case), 2. open a terminal, 3. run 'kalarm --list' (no quotes) OBSERVED RESULT 1. no output on 'kalarm --list', 2. the scheduled alarm doesn't fire, 3. its "Time To" column turns blank, 4. when trying to make a new alarm, there's a warning about alarms being disabled even though all controls seem to have them enabled, 5. after restarting KAlarm, the alarm fires. EXPECTED RESULT 'kalarm --list' provides output for scripting and doesn't interfere with executions of alarms. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Graphics Platform: X11 Best regards, Szymon -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446486] No monitor serial is written in arranger in X11 session (and probably in wayland too)
https://bugs.kde.org/show_bug.cgi?id=446486 Andrew Shark changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446486] No monitor serial is written in arranger in X11 session (and probably in wayland too)
https://bugs.kde.org/show_bug.cgi?id=446486 --- Comment #6 from Andrew Shark --- I could build kscreen-git without other -git dependencies, and it worked. I tested your change, it works and looks nice. > At least when there are several same model monitors. Despite I said it earlier, I am now in doubt if this is the best way of doing this. I mean, what if we just make a setting to always show or hide serials? Because lets imagine the situation when user connects only one of identical monitors? In my case, I currently have only one P2415Q, so I do not care of its serial. But for P2217H I am unable to identify which one it is. I think that could go to a bottom of page in a checkbox "Show monitor serial numbers". And also, the title in https://invent.kde.org/plasma/kscreen/-/merge_requests/55 says > and hide connector type Why do this? I consider this information useful. I have several hdmi and several displayport connectors, and it helps to identify the connection. Because I often plug cables here and there because I experiment with gpu passthrough and other things. Maybe also place the checkbox "Show connector types" at the bottom of page? Thank you for the work. P.S. In the screenshot above I actually connected dp and hdmi to the same monitor, that is why the serials are the same. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #13 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #11) > (In reply to Frank Kruger from comment #9) > > (In reply to Wolfgang Bauer from comment #3) > The main question is, what triggers the crash? My only guess so far is that it has to do with what filesystems are mounted. As the crash reports are all in KMountPoint::mountType() from kio. But comment#5 suggests it depends on the URL... @Frank Kruger: Does it help if you rename the directory "~/.local/share/kget/", so that current downloads are no longer continued? -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #12 from Frank Kruger --- (In reply to Wolfgang Bauer from comment #11) > (In reply to Frank Kruger from comment #9) > > (In reply to Wolfgang Bauer from comment #3) > > > Hm. kget 21.08.3 doesn't crash here. > > > Is it still happening? > > > > > > The crash apparently was in kio, actually. > > > Maybe it got fixed there already? > > > > Kget 21.08.3 still crashes at start up with up-to-date openSUSE Tumbleweed > > 20211207. Shall I open a bug report there? > > No. It's likely not a distribution problem, especially as it originally was > reported from a Fedora user. > The main question is, what triggers the crash? Start kget from the console I get: Verifying Metalink/HTTP Status Mime Type: "application/metalink4+xml" No Metalink HTTP response found QWidget::insertAction: Attempt to insert null action QWidget::insertAction: Attempt to insert null action KCrash: Application 'kget' crashing... QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 25 and type 'Read', disabling... QSocketNotifier: Invalid socket 23 and type 'Read', disabling... KCrash: Attempting to start /usr/lib64/libexec/drkonqi -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #11 from Wolfgang Bauer --- (In reply to Frank Kruger from comment #9) > (In reply to Wolfgang Bauer from comment #3) > > Hm. kget 21.08.3 doesn't crash here. > > Is it still happening? > > > > The crash apparently was in kio, actually. > > Maybe it got fixed there already? > > Kget 21.08.3 still crashes at start up with up-to-date openSUSE Tumbleweed > 20211207. Shall I open a bug report there? No. It's likely not a distribution problem, especially as it originally was reported from a Fedora user. The main question is, what triggers the crash? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444460] Overview shows Plasma icon and re-arranges itself when a notification appears
https://bugs.kde.org/show_bug.cgi?id=60 --- Comment #4 from Vlad Zahorodnii --- Can you reproduce it reliably? This doesn't occur on my machine for some reason. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #10 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #8) > (In reply to Wolfgang Bauer from comment #7) > > (In reply to Kārlis Kavacis from comment #5) > > > Yeah! It's something to do with the download URL or server responses - > > > Fedora Workstation 35 ISO from Fedora home page downloads successfully > > > without crashing KGet! > > > > Would it be possible to share a particular URL that crashes kget? > > > > If I can reproduce the crash, it might help to debug this problem. ;-) > > Although, your latest crash seems to be a different one. Sorry, I didn't look well enough, It's actually still in kio too. > #7 KMountPoint::mountType (this=0x0) at > /usr/src/debug/kf5-kio-5.88.0-1.fc35.x86_64/src/core/kmountpoint.cpp:412 > #8 0x7fed7435b08f in DataSourceFactory::start() () from > /lib64/libkgetcore.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #9 from Frank Kruger --- (In reply to Wolfgang Bauer from comment #3) > Hm. kget 21.08.3 doesn't crash here. > Is it still happening? > > The crash apparently was in kio, actually. > Maybe it got fixed there already? Kget 21.08.3 still crashes at start up with up-to-date openSUSE Tumbleweed 20211207. Shall I open a bug report there? -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #8 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #7) > (In reply to Kārlis Kavacis from comment #5) > > Yeah! It's something to do with the download URL or server responses - > > Fedora Workstation 35 ISO from Fedora home page downloads successfully > > without crashing KGet! > > Would it be possible to share a particular URL that crashes kget? > > If I can reproduce the crash, it might help to debug this problem. ;-) Although, your latest crash seems to be a different one. So my question in comment#3 still stands. @Frank Kruger: what's your experience meanwhile? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 446738] Multi-page thumbnail view
https://bugs.kde.org/show_bug.cgi?id=446738 --- Comment #3 from Nate Graham --- Hmm, intuitiveness doesn't seem relevant here and responsiveness is typically a factor of performance and animation easing curves, which also aren't factors here. When you say "efficient", do you mean that the scroll speed is effectively faster because each scroll "tick" moves down by three pages rather than one? -- You are receiving this mail because: You are watching all bug changes.
