[dolphin] [Bug 419038] New: internal not specified error in libsmbclient in Network SMB search
https://bugs.kde.org/show_bug.cgi?id=419038 Bug ID: 419038 Summary: internal not specified error in libsmbclient in Network SMB search Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: t...@atlas.cz CC: kfm-de...@kde.org Target Milestone: --- Created attachment 126902 --> https://bugs.kde.org/attachment.cgi?id=126902&action=edit tcpdump > tcpdump.txt SUMMARY STEPS TO REPRODUCE 1. in Dolphin / Network / Shared Folders SMB / -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393336] Brush rotation using tablet pen's rotation capped at 180 degrees.
https://bugs.kde.org/show_bug.cgi?id=393336 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/9675ed2c2077b7 ||3fb7fd049fbc264920f84aa24c Status|REOPENED|RESOLVED --- Comment #12 from Dmitry Kazakov --- Git commit 9675ed2c2077b73fb7fd049fbc264920f84aa24c by Dmitry Kazakov. Committed on 19/03/2020 at 21:29. Pushed by rempt into branch 'krita/4.2'. Make rotation sensor be "additive" With new curve scaling methods, using rotation as a "scaling sensor" doesn't work anymore. M +6-1plugins/paintops/libpaintop/sensors/kis_dynamic_sensors.h https://invent.kde.org/kde/krita/commit/9675ed2c2077b73fb7fd049fbc264920f84aa24c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419025] Krita closes on autosave
https://bugs.kde.org/show_bug.cgi?id=419025 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt --- Some more questions... Does this happen with newly created documents that haven't been saved? And could you also append the log file (also from the help menu)? I'm trying to prepare a special nightly build to test for you, because there must be something up with your system, though Krita of course shouldn't crash when autosaving under any circumstance... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416838] Crash when using nm-widget to connect to wifi network
https://bugs.kde.org/show_bug.cgi?id=416838 Karsten Sperling Opdal changed: What|Removed |Added CC||palette...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419039] New: [Request] Allow Keyboard Navigation when Identifying Unknown Faces
https://bugs.kde.org/show_bug.cgi?id=419039 Bug ID: 419039 Summary: [Request] Allow Keyboard Navigation when Identifying Unknown Faces Product: digikam Version: 7.0.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: kartikx2...@gmail.com Target Milestone: --- Personally, I like navigating using the keyboard. However, identifying faces in the Unknown Faces View requires the user to go back and forth between the keyboard and mouse a lot. It would be helpful (I believe), if the user could first click on an detected face, type a name, press Enter to assign it (till this step is currently supported by DigiKam), and then move around with the arrow keys, and whichever other face he wishes to apply the same tag to, he may simply press enter for it. I would like to implement this feature in DigiKam. Kartik -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415634] kontact crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=415634 Laurent Montel changed: What|Removed |Added CC||bryant.staff...@outlook.com --- Comment #18 from Laurent Montel --- *** Bug 419035 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 419035] Kontact Crashes Opening Settings
https://bugs.kde.org/show_bug.cgi?id=419035 Laurent Montel changed: What|Removed |Added Resolution|--- |DUPLICATE CC||mon...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Laurent Montel --- *** This bug has been marked as a duplicate of bug 415634 *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 406691] Can't follow symbolic links in SFTP locations
https://bugs.kde.org/show_bug.cgi?id=406691 aslam karachiwala <4s...@mythicflow.com> changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from aslam karachiwala <4s...@mythicflow.com> --- Steps to reproduce bug were provided in the original bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411729] Greek accents and dead keys do not work in Debian Stable
https://bugs.kde.org/show_bug.cgi?id=411729 --- Comment #4 from Johann Höchtl --- try to add this to /etc/environment INPUT_METHOD=ibus GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Do accents work afterwards? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419040] New: [Request] Provide Option to Select Album to apply Facial Recognition on
https://bugs.kde.org/show_bug.cgi?id=419040 Bug ID: 419040 Summary: [Request] Provide Option to Select Album to apply Facial Recognition on Product: digikam Version: 7.0.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: kartikx2...@gmail.com Target Milestone: --- Currently, the user is provided the option to select albums on which Face Detection is done, and then Face Recognition takes place on these identified faces. If the user accidentally scanned some albums during detection, then there isn't a way to remove these albums from the recognition process(If there is, I feel it could be made more intuitive, I wasn't able to find it). It would helpful if the user could select which albums, Recognition could take place on as it can save time if user only wanted to recognize a small album. Even if this can not be done, the Face Views (Under Unknown Tag) could provide an option to perhaps hide albums that the user doesn't want to see. Personally, I find it to be a little cluttered if too many albums are present there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418318] The hover state should be clarifying, but not main
https://bugs.kde.org/show_bug.cgi?id=418318 popov895 changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from popov895 --- What do you mean by saying "do something useful with the patch"? Do I need to submit the patch myself? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419040] [Request] Provide Option to Select Album to apply Facial Recognition on
https://bugs.kde.org/show_bug.cgi?id=419040 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Face recognition is performed on all unknown faces. The user has a large number of unknown faces through face detection. He doesn't even know which albums the faces come from. We had the problem that when selecting albums either the albums were double and triple or the desired faces did not go through the face recognition. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419032] [Wayland] kwin uses VR headset as monitor
https://bugs.kde.org/show_bug.cgi?id=419032 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Vlad Zahorodnii --- We ignore the "non-desktop" property set on connector objects. I assume that's the reason why HMDs are treated as monitors. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419008] Always crash in Regional Setting within System Settings
https://bugs.kde.org/show_bug.cgi?id=419008 Yaroslav Sidlovsky changed: What|Removed |Added CC||zawer...@gmail.com --- Comment #1 from Yaroslav Sidlovsky --- Created attachment 126904 --> https://bugs.kde.org/attachment.cgi?id=126904&action=edit systemsettings5-20200320-112045.kcrash.txt Same bug on Fedora 31. System info: Operating System: Fedora 31 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 Kernel Version: 5.5.9-200.fc31.x86_64 OS Type: 64-bit Processors: 4 × AMD FX(tm)-9590 Eight-Core Processor Memory: 22,4 ГиБ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418939] Crash when search faces
https://bugs.kde.org/show_bug.cgi?id=418939 --- Comment #12 from Maik Qualmann --- No crash can be seen in the log. Please use the "debug" option correctly with "-debug". Create a GDB log again. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419008] Always crash in Regional Setting within System Settings
https://bugs.kde.org/show_bug.cgi?id=419008 --- Comment #2 from Yaroslav Sidlovsky --- All required debug packages has been installed but still Dr.Konqi reports that it's not enough. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419040] [Request] Provide Option to Select Album to apply Facial Recognition on
https://bugs.kde.org/show_bug.cgi?id=419040 --- Comment #2 from Maik Qualmann --- In addition, it is already possible to perform face detection and recognition only on an album or even a single image. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419040] [Request] Provide Option to Select Album to apply Facial Recognition on
https://bugs.kde.org/show_bug.cgi?id=419040 --- Comment #3 from Kartik --- Ah, so the Facial Recognition Algorithm does not realise what albums are? It only works on the entire set of unknown faces created by the Detection process? In that case would the latter part of my initial report be helpful? The Thumbnail View page already segregates the Unknown Faces into albums (and displayed under each album header), maybe we could provide a small collapse icon on this? Thanks Kartik -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 419041] New: Animated PNG are flickering
https://bugs.kde.org/show_bug.cgi?id=419041 Bug ID: 419041 Summary: Animated PNG are flickering Product: Falkon Version: 3.1.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: m...@feuforeve.fr Target Milestone: --- SUMMARY Animated PNG are flickering. Those images may be used as animated icons on some services as an alternative to GIF images, and they are incorrectly displayed. STEPS TO REPRODUCE 1. Load a page containing APNG images. For instance this page: https://en.wikipedia.org/wiki/Animated_Portable_Network_Graphics OBSERVED RESULT Images are flickering, only the first frame is shown correctly, the other frames are not shown. EXPECTED RESULT Either: - only the first frame is shown (non-animated solution) - all frames are correctly displayed (animated solution) SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux 64 bits KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.14.1 libpng: 1.6.37 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 418814] Ripping CD fails on tracks containing question marks
https://bugs.kde.org/show_bug.cgi?id=418814 --- Comment #4 from forenk...@gmx.de --- you are right, I cannot create a file with questionmarks in the name on the ntfs drive, so it is definetly a filesystem driver issue. Damn that's a bummer. I guess you can close this as it is unrelated to k3b. Or do I need to mark this as closed? Would it be an idea to add a checkbox to remove problematic characters like that? Of course, I don't have a clue which other characters might be problematic =(. Anyway, thank you for you time and effort, I will file a bugreport to the ntfs-3g guys. Cheers, David -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 406691] Can't follow symbolic links in SFTP locations
https://bugs.kde.org/show_bug.cgi?id=406691 Harald Sitter changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from Harald Sitter --- I may have read over the not in "not caused by a chroot restriction" ^^ Anyway, I cannot reproduce this. - does this happen with every server (e.g. can you reproduce this with localhost). if not what version/type of server. does the server have settings different from the defaults? - is the symlink absolute or relative? (attach output of `readlink $wherethelinkis` maybe) - are you sure it's a symlink and not a hardlink? Please get a log of kio by running dolphin with a suitable url, then triggering the bug: > killall kioslave5; killall -9 kiod5; QT_LOGGING_RULES="log_kio_sftp=true" > KDE_FORK_SLAVES=1 dolphin --new-window '$SFTPURL' attach the entire generated output to the bug report please. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 404890] copy file failed on remote sftp host
https://bugs.kde.org/show_bug.cgi?id=404890 Harald Sitter changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #6 from Harald Sitter --- Alas, I cannot reproduce. Does this happen with any server (e.g. can you reproduce this with localhost)? Are you sure the remote directory permissions are correct? What is the server software/version? Does the server possibly have additional settings other than the defaults of the server software? Please start dolphin and generate debug output by causing the issue: > killall kioslave5; killall -9 kiod5; > QT_LOGGING_RULES="log_kio_sftp=true;log_kio_sftp.trace=true" > KDE_FORK_SLAVES=1 dolphin --new-window '$SFTPURL' then attach the output to the bug report please. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 365437] Rename local variable using "Rename" assistant breaks code
https://bugs.kde.org/show_bug.cgi?id=365437 --- Comment #7 from Igor Kushnir --- I see that my braces bug is the same as Piotr's. It is triggered by a brace inserted by a formatter just before the renamed variable. The bug is in extractFormattedTextFromContext(): endOfLeftContext = matchPrefixIgnoringWhitespace(formattedMergedText, leftContext, fuzzyCharacters); The inserted brace ends up after endOfLeftContext and sneaks into code along with the renamed variable. The bug does not depend on the source formatter - happens with all of them. I'll try to fix this bug by skipping the brace and associated extra line break, etc. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418858] "Titlebar buttons" tab of the "Window decorations" KCM only shows button icons from breeze window decoration
https://bugs.kde.org/show_bug.cgi?id=418858 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Changing it to use the current theme causes it to crash for Aurorae themes: #6 QOpenGLContext::shareGroup (this=this@entry=0x0) at kernel/qopenglcontext.cpp:1170 #7 0x7f556574294a in QOpenGLMultiGroupSharedResource::value (context=0x0, this=) at ../../include/QtGui/5.14.1/QtGui/private/../../../../../src/gui/kernel/qopenglcontext_p.h:173 #8 qt_gl_functions (context=0x0) at opengl/qopenglfunctions.cpp:191 #9 QOpenGLFunctions::initializeOpenGLFunctions (this=this@entry=0x560ed9d77830) at opengl/qopenglfunctions.cpp:576 #10 0x7f5562c1c747 in QSGBatchRenderer::Renderer::Renderer (this=0x560ed9d776c0, ctx=0x560ed8c07000) at scenegraph/coreapi/qsgbatchrenderer.cpp:989 #11 0x7f5562c76811 in QSGDefaultRenderContext::createRenderer (this=0x560ed8c07000) at scenegraph/qsgdefaultrendercontext.cpp:328 #12 0x7f5562cdf438 in QQuickWindowPrivate::syncSceneGraph (this=0x560ed8c88a20) at items/qquickwindow.cpp:444 #13 0x7f5562da0129 in QQuickRenderControl::sync (this=) at items/qquickrendercontrol.cpp:297 #14 0x7f556417f149 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #15 0x7f5564181f3b in QQuickWidget::resizeEvent(QResizeEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #16 0x7f5565cceb0e in QWidget::event (this=0x560ed7ec86d0, event=0x7ffc1d655200) at kernel/qwidget.cpp:8821 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 389917] translations builds not parallel
https://bugs.kde.org/show_bug.cgi?id=389917 Harald Sitter changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Harald Sitter --- https://phabricator.kde.org/D10776 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 419042] New: Crash in ctags with KDevelop
https://bugs.kde.org/show_bug.cgi?id=419042 Bug ID: 419042 Summary: Crash in ctags with KDevelop Product: kdevelop Version: 5.5.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: ricardo@hotmail.com Target Milestone: --- Application: kdevelop (5.5.0) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.3.0-40-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: 1. Clicked on CTags tool view 2. In "Index Targets" tab clicked on "Update Index" button. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f67d542ec00 (LWP 1638))] Thread 11 (Thread 0x7f675700 (LWP 2070)): #0 0x7f67d18270b4 in __GI___libc_read (fd=17, buf=0x7f675fffe7de, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f67abb7f021 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f67b37afa2e in pa_mainloop_prepare () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f67b37b04a0 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f67b37b0560 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f67b37be3c9 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f67abbae318 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7f67ca5546db in start_thread (arg=0x7f675700) at pthread_create.c:463 #8 0x7f67d183888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f67515b4700 (LWP 1894)): #0 0x7f67ca55a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55be956b36b0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f67ca55a9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55be956b3660, cond=0x55be956b3688) at pthread_cond_wait.c:502 #2 0x7f67ca55a9f3 in __pthread_cond_wait (cond=0x55be956b3688, mutex=0x55be956b3660) at pthread_cond_wait.c:655 #3 0x7f67d1f49d9b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f67d1f49f19 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f67c8156845 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f67c815a6f8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f67c8155b0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f67c815a752 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f67c8155b0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f67c815a752 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f67c8155b0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7f67c815a752 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7f67c8155b0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7f67c815a752 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x7f67c8155b0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x7f67c815a752 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #17 0x7f67c8155b0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #18 0x7f67c815a752 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #19 0x7f67c8155b0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #20 0x7f67c815a752 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #21 0x7f67c8155b0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #22 0x7f67c815a752 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #23 0x7f67c8155b0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #24 0x7f67c815a752 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #25 0x7f67c8155b0d in ThreadWeaver::Weaver::applyForWo
[kdevelop] [Bug 419042] Crash in ctags with KDevelop
https://bugs.kde.org/show_bug.cgi?id=419042 --- Comment #1 from rgoomes --- (In reply to rgoomes from comment #0) > Application: kdevelop (5.5.0) > > Qt Version: 5.14.1 > Frameworks Version: 5.67.0 > Operating System: Linux 5.3.0-40-generic x86_64 > Windowing system: X11 > Distribution: KDE neon User Edition 5.18 > > -- Information about the crash: > - What I was doing when the application crashed: > 1. Clicked on CTags tool view > 2. In "Index Targets" tab clicked on "Update Index" button. > > -- Backtrace: > Application: KDevelop (kdevelop), signal: Segmentation fault > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [Current thread is 1 (Thread 0x7f67d542ec00 (LWP 1638))] > > Thread 11 (Thread 0x7f675700 (LWP 2070)): > #0 0x7f67d18270b4 in __GI___libc_read (fd=17, buf=0x7f675fffe7de, > nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:27 > #1 0x7f67abb7f021 in pa_read () at > /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so > #2 0x7f67b37afa2e in pa_mainloop_prepare () at > /usr/lib/x86_64-linux-gnu/libpulse.so.0 > #3 0x7f67b37b04a0 in pa_mainloop_iterate () at > /usr/lib/x86_64-linux-gnu/libpulse.so.0 > #4 0x7f67b37b0560 in pa_mainloop_run () at > /usr/lib/x86_64-linux-gnu/libpulse.so.0 > #5 0x7f67b37be3c9 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 > #6 0x7f67abbae318 in () at > /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so > #7 0x7f67ca5546db in start_thread (arg=0x7f675700) at > pthread_create.c:463 > #8 0x7f67d183888f in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > Thread 10 (Thread 0x7f67515b4700 (LWP 1894)): > #0 0x7f67ca55a9f3 in futex_wait_cancelable (private=, > expected=0, futex_word=0x55be956b36b0) at > ../sysdeps/unix/sysv/linux/futex-internal.h:88 > #1 0x7f67ca55a9f3 in __pthread_cond_wait_common (abstime=0x0, > mutex=0x55be956b3660, cond=0x55be956b3688) at pthread_cond_wait.c:502 > #2 0x7f67ca55a9f3 in __pthread_cond_wait (cond=0x55be956b3688, > mutex=0x55be956b3660) at pthread_cond_wait.c:655 > #3 0x7f67d1f49d9b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () > at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #4 0x7f67d1f49f19 in QWaitCondition::wait(QMutex*, unsigned long) () at > /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #5 0x7f67c8156845 in > ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver:: > Thread*, bool, bool, bool) () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #6 0x7f67c815a6f8 in () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #7 0x7f67c8155b0d in > ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #8 0x7f67c815a752 in () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #9 0x7f67c8155b0d in > ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #10 0x7f67c815a752 in () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #11 0x7f67c8155b0d in > ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #12 0x7f67c815a752 in () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #13 0x7f67c8155b0d in > ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #14 0x7f67c815a752 in () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #15 0x7f67c8155b0d in > ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #16 0x7f67c815a752 in () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #17 0x7f67c8155b0d in > ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #18 0x7f67c815a752 in () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #19 0x7f67c8155b0d in > ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #20 0x7f67c815a752 in () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #21 0x7f67c8155b0d in > ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #22 0x7f67c815a752 in () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #23 0x7f67c8155b0d in > ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #24 0x7f67c815a752 in () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #25 0x7f67c8155b0d in > ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 > #26 0x7f67c815a752 in () at > /usr/lib/x86_64-linux-gnu/libKF5Threa
[Spectacle] [Bug 413361] Spectacle crashes every time when capturing a rectangular region
https://bugs.kde.org/show_bug.cgi?id=413361 Dave Morley changed: What|Removed |Added CC||davm...@davmor2.co.uk Status|REOPENED|CONFIRMED --- Comment #7 from Dave Morley --- Hi guys I can confirm that with a laptop plugged into an additional Monitor I get the following on KDE NEON (Up-to-date) spectacle kf5.kconfig.core: "\"cropRegion\" - conversion of \"0,0,0,0\" to QRect failed" And the app closes no crash report However without the additional monitor in place I get the rectangular region but with the same error. -- You are receiving this mail because: You are watching all bug changes.
[khangman] [Bug 344834] installs khangman-harmattan icons even when not building harmattan version
https://bugs.kde.org/show_bug.cgi?id=344834 Harald Sitter changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 419043] New: baloo_file_extractor seemingly hangs in infinite loop due to DB problems, hogs CPU
https://bugs.kde.org/show_bug.cgi?id=419043 Bug ID: 419043 Summary: baloo_file_extractor seemingly hangs in infinite loop due to DB problems, hogs CPU Product: frameworks-baloo Version: 5.67.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: k...@mailhell.seb7.de Target Milestone: --- SUMMARY baloo_file_extractor consumes excessive amounts of CPU time while failing to put some data into the DB; which is failing for a few hours now. This is a company workstation, hence I can't just check the users files. As a workaround we're now outright disabling baloo system-wide. > KiB Mem : 32821712 total, 240112 free, 29828712 used, 2752888 buff/cache > KiB Swap: 16779260 total, 13479084 free, 3300176 used. 2507532 avail Mem > > PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ > COMMAND > > 2247542 redacted 39 19 270,6g 13,9g 9668 S 32,9 44,3 336:46.12 > baloo_file_extr > > 2247541 redacted 39 19 270,7g 13,3g 9552 S 31,2 42,5 325:26.98 > baloo_file_extr > > 646542 root 20 0 454160 273636 272428 S 22,9 0,8 288:38.48 > systemd-journal Note the two processes for baloo_file_extract (for the same user). Might be some locking issue, or just a red herring. journalctl is full of > Mar 20 10:34:15 walle baloo_file_extractor[2247542]: org.kde.baloo.engine: > PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is > invalid > Mar 20 10:34:15 walle baloo_file_extractor[2247542]: org.kde.baloo.engine: > PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid > Mar 20 10:34:15 walle baloo_file_extractor[2247542]: org.kde.baloo.engine: > PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is > invalid > Mar 20 10:34:15 walle baloo_file_extractor[2247542]: org.kde.baloo.engine: > Transaction::commit MDB_BAD_TXN: Transaction must abort, has a child, or is > invalid EXPECTED RESULT Whatever causes the underlying database problems, the process should probably give up after a few thousand database errors and try to log a sane error message - instead of hogging the CPU. SOFTWARE/OS VERSIONS Manjaro Linux 5.4.15-2-MANJARO balooctl --version reports 5.67.0 I'm remote, plasmashell doesn't seem to have a --version or -v, but should be a recent version. The release notes at https://kde.org/announcements/kde-frameworks-5.68.0.php don't mention anything like this, and git log comments also don't look like it (I did not look at the actual commits). -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 419044] Kamoso crashing randomly
https://bugs.kde.org/show_bug.cgi?id=419044 kismaelke...@gmail.com changed: What|Removed |Added CC||kismaelke...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 419044] New: Kamoso crashing randomly
https://bugs.kde.org/show_bug.cgi?id=419044 Bug ID: 419044 Summary: Kamoso crashing randomly Product: kamoso Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: kismaelke...@gmail.com Target Milestone: --- Application: kamoso (19.12.3) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.3.0-40-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: The app crashes every once in a while when being used The crash can be reproduced every time. -- Backtrace (Reduced): #6 0x7f634bfb258f in __memmove_sse2_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:306 #7 0x7f632e580706 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.59 #8 0x7f632e58b2ea in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.59 #9 0x7f632e6fa4f3 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.59 #10 0x7f632e6c51e0 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.59 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 418994] Content disappears while zooming in PDFs
https://bugs.kde.org/show_bug.cgi?id=418994 --- Comment #5 from jan.clausse...@web.de --- No it is a normal 1080p laptop screen -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 419045] New: Inconsistencies in behavior when left clicking on toolbar
https://bugs.kde.org/show_bug.cgi?id=419045 Bug ID: 419045 Summary: Inconsistencies in behavior when left clicking on toolbar Product: Breeze Version: 5.18.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: unassigned-b...@kde.org Reporter: nortex...@gmail.com Target Milestone: --- By way of example, left clicking on kwrite, kaddressbook and ksysguard's toolbars does NOT initiate a move. Left clicking on dolphin, kmail and okular's toolbars DOES initiate a move. Left clicking on korganizer's toolbar briefly shows a move cursor and then goes back to the standard arrow cursor state. I prefer NOT initiating a move since I often click on the toolbar to focus and NOT move the window. This also seems *to me* to the sanest, most expected, and least irritating default behavior. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408781] System settings crashes when I back to "All settings" from Mouse kcm
https://bugs.kde.org/show_bug.cgi?id=408781 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #2 from David Edmundson --- >#6 0x7f3104b4d110 in () at /usr/lib/qt/plugins/kded_touchpad.so Can I get debug symbols for this please -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419031] system settings
https://bugs.kde.org/show_bug.cgi?id=419031 David Edmundson changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- #7 0x7f852b6dbdc1 in dstyle::Style::drawSlider(QStyleOptionComplex const*, QPainter*, QWidget const*) const () at /usr/lib/qt/plugins/styles/libdstyleplugin.so Crash is in some style that isn't from us. Please report to "dstyle" -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 Mikhail changed: What|Removed |Added CC||push@gmail.com --- Comment #9 from Mikhail --- Same on Manjaro. KDE 5.18.3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415147] Turning on blur background in konsole under wayland displays the blurred content next to the actual window
https://bugs.kde.org/show_bug.cgi?id=415147 garaba.flor...@protonmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from garaba.flor...@protonmail.com --- It appears to be fixed in Plasma 5.18.3, framework version 5.68, qt version 5.15.0 and konsole 19.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #128 from Luca Carlon --- What system? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 418472] Duplicating files on remote connections results in the copy having ".part" in the name
https://bugs.kde.org/show_bug.cgi?id=418472 Alexander Ewering changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Alexander Ewering --- I have provided the requested info, so I guess this should be changed to "CONFIRMED". -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 418472] Duplicating files on remote connections results in the copy having ".part" in the name
https://bugs.kde.org/show_bug.cgi?id=418472 Alexander Ewering changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |REPORTED --- Comment #6 from Alexander Ewering --- Sorry, "REPORTED" would be correct I suppose. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO --- Comment #10 from David Edmundson --- Please don't add "me too" comments unless you can add some value. At least include the output of journalctl for the login. -- If someone is convinced that this is a regression, please perform a bisect to find out what. -- There is a branch in the kwallet-pam repo called: davidedmundson/test building that will simulate the entire login process -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 419015] KRDC does not correctly detect screen resolution if display is scaled
https://bugs.kde.org/show_bug.cgi?id=419015 nikolay.shus...@gmail.com changed: What|Removed |Added Version|19.04 |19.12 --- Comment #1 from nikolay.shus...@gmail.com --- Upgraded KDE Plasma to 5.18.3, KDE framework 5.67.0, QT 5.12.4, KRDC 19.12.3, still reproducible -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 340684] Cursor doesn't react properly (it moves but can't draw) after lifting stylus pen away from tablet
https://bugs.kde.org/show_bug.cgi?id=340684 Вова changed: What|Removed |Added CC||megabill...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 414047] Apper crashes when applying updates
https://bugs.kde.org/show_bug.cgi?id=414047 Ulrich Schneider changed: What|Removed |Added CC||qoman...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419025] Krita closes on autosave
https://bugs.kde.org/show_bug.cgi?id=419025 --- Comment #3 from Boudewijn Rempt --- Git commit b0adcdbbdc9e70fe6f10174a1dd25b02aeda630c by Boudewijn Rempt. Committed on 20/03/2020 at 12:51. Pushed by rempt into branch 'master'. Remove the KoLegacyZipStore Everything in Krita that uses zip files now uses quazip M +1-20 3rdparty/ext_frameworks/CMakeLists.txt D +0-21 3rdparty/ext_frameworks/karchive.diff M +0-1libs/store/CMakeLists.txt D +0-272 libs/store/KoLegacyZipStore.cpp D +0-73 libs/store/KoLegacyZipStore.h M +2-22 libs/store/KoStore.cpp M +1-2packaging/android/androidbuild.sh https://invent.kde.org/kde/krita/commit/b0adcdbbdc9e70fe6f10174a1dd25b02aeda630c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419025] Krita closes on autosave
https://bugs.kde.org/show_bug.cgi?id=419025 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Boudewijn Rempt --- Even more questions: are you running security software other than Windows Defender, or things like sandboxie? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 418472] Duplicating files on remote connections results in the copy having ".part" in the name
https://bugs.kde.org/show_bug.cgi?id=418472 Harald Sitter changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #7 from Harald Sitter --- This looks suspiciously like a server-side problem that we can't do anything about. If I give you a diff can you build kio-extras yourself to get some more debug output? This is either a problem with libssh or the server, but it's hard to say which without some more context on the error. Is this still a problem if you disable the .part files? (run `kcmshell5 netpref` and uncheck 'mark partial files') in Comment #3 we see it successfully opening the file on the server and writing the first (and only) 8355 bytes. It'd then continue to write 0 bytes and that results in a zero byte write which would then conclude the upload. Except, instead of coming back with 0 bytes the second write raises an error which leaves you with the dangling .part file. We aren't doing anything crazy there, so I am rather thinking the server considers 0 byte writes a problem, which is stupid and wrong. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 419046] New: Too easy to delete icon themes by accident
https://bugs.kde.org/show_bug.cgi?id=419046 Bug ID: 419046 Summary: Too easy to delete icon themes by accident Product: kmymoney Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: riddervancoca...@hotmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open System Settings > Icons. 2. Click on the bottom right corner of the image representing an icon theme (where the 'waste' button is located). 3. Click apply. OBSERVED RESULT The icon theme is completely removed from the system. EXPECTED RESULT The icon theme is either put in the wastebin OR the user is asked for conformation that they want to delete this icon theme. It is very easy to accidentally click the 'delete' button if one actually wants to apply a theme, especially since the delete button is hidden until the user hovers over it. Therefore, it would be best if additional safeguards were in place. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 with KDE Backports enabled. KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402299] Refresh button in Find/Replace in Files view clears previous search
https://bugs.kde.org/show_bug.cgi?id=402299 Piotr Keplicz changed: What|Removed |Added CC||kepl...@cmc.pl Version|5.3.0 |5.5.0 --- Comment #2 from Piotr Keplicz --- The "Refresh" button in 5.5.0 still repeates the *previous* search not the current one. The current one is deleted until no searches are left. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419046] Too easy to delete icon themes by accident
https://bugs.kde.org/show_bug.cgi?id=419046 G_v_I changed: What|Removed |Added Assignee|kmymoney-de...@kde.org |plasma-b...@kde.org Component|general |general Version|unspecified |5.18.3 Product|kmymoney|systemsettings -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419047] New: Closing Face Tag Delete Dialog Box still ends up deleting face tag
https://bugs.kde.org/show_bug.cgi?id=419047 Bug ID: 419047 Summary: Closing Face Tag Delete Dialog Box still ends up deleting face tag Product: digikam Version: 7.0.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: kartikx2...@gmail.com Target Milestone: --- When we right click on a Face Tag (in People Sidebar). We are shown 2 Dialog Boxes, consecutively. 1. Confirmation Box, this works as accepted. 2. Dialog Box that asks whether to delete the associated face identity. Pressing the close button of this box, and pressing "No", performs the same function. It deletes the tag, but not the associated Identity. I think, the cancel button should instead not delete the face tag at all. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419046] Too easy to delete icon themes by accident
https://bugs.kde.org/show_bug.cgi?id=419046 G_v_I changed: What|Removed |Added Component|general |kcm_icons -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 419048] New: Baloo file extractor constantly crashes when I boot
https://bugs.kde.org/show_bug.cgi?id=419048 Bug ID: 419048 Summary: Baloo file extractor constantly crashes when I boot Product: frameworks-baloo Version: 5.54.0 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: jonathan.hau...@icloud.com Target Milestone: --- Application: baloo_file_extractor (5.54.0) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-6-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: I was booting my computer. That's all I was doing, but I happens every time. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff2fed59480 (LWP 4740))] Thread 2 (Thread 0x7ff2f09f7700 (LWP 4743)): #0 0x7ff301485644 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff30148606b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff30148625c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff3029a8743 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff30295615b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff3027a5e76 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff3038ce545 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7ff3027afa67 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff302086fa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7ff30249f4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ff2fed59480 (LWP 4740)): [KCrash Handler] #4 0x7ff30250271b in __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:288 #5 0x7ff30399f05d in () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #6 0x7ff30398c679 in Baloo::PostingDB::get(QByteArray const&) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #7 0x7ff30399c8ca in Baloo::WriteTransaction::commit() () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #8 0x7ff303992ea2 in Baloo::Transaction::commit() () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #9 0x5627a9dbdf0c in () #10 0x7ff30298c426 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7ff30298102b in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7ff3032d24c1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7ff3032d9970 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7ff302957489 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7ff3029a7b38 in QTimerInfoList::activateTimers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7ff3029a83cc in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7ff301485f2e in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7ff3014861c8 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7ff30148625c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7ff3029a8727 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7ff2fe91e401 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #22 0x7ff30295615b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7ff30295e132 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x5627a9dbb323 in () #25 0x7ff3023ca09b in __libc_start_main (main=0x5627a9dbb0e0, argc=1, argv=0x7ffe254c9de8, init=, fini=, rtld_fini=, stack_end=0x7ffe254c9dd8) at ../csu/libc-start.c:308 #26 0x5627a9dbb3ca in () [Inferior 1 (process 4740) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419022] Circle to quickly choose tool does not select tool, needs double click to stay open
https://bugs.kde.org/show_bug.cgi?id=419022 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #2 from Ahab Greybeard --- That button on your pen is the equivalent of a mouse right-click. Does your mouse behave well when you use it to bring up the popup palette in this way? If you go to Settings -> Configure Krita -> Tablet settings then press the large Open Tablet Tester buttonm you'll get the tablet tester window. Resize it to make it large and useful. Hover your pen over the grid area and press your button-2. You should get a continuous stream of records with B=2 (due to slight movements of your pen). If you quickly release button-2 and then press it again, you should get a single B=0 record before the repeated B=2 records begin again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411729] Greek accents and dead keys do not work in Debian Stable
https://bugs.kde.org/show_bug.cgi?id=411729 --- Comment #5 from tdy...@hotmail.com --- Johann, First of all I never before had to use ibus. I never had it installed on my system. Having said that, I did install number of ibus packages. As to /etc/environment: I am not sure debian is using it in buster. Mine has always been empty. Anyway, I looked around and I also messed with ~/.bashrc. Interesting thing though is that after I run ibus-setup EL ibus flag (actually I could see three selections for my choice languages) showed up, my regular keyboard flags (4)stopped working but my accents still did not work. I may be still missing something, but I am not sure ibus is the way to go, since I never had to use it before. I'll keep it for a while to see if I can get it to workit will work. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419047] Closing Face Tag Delete Dialog Box still ends up deleting face tag
https://bugs.kde.org/show_bug.cgi?id=419047 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 384485 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384485] Face Regions are deleted when unconfirmed face suggestion is rejected by user
https://bugs.kde.org/show_bug.cgi?id=384485 --- Comment #11 from Maik Qualmann --- *** Bug 419047 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418939] Crash when search faces
https://bugs.kde.org/show_bug.cgi?id=418939 --- Comment #13 from Clon --- I don't know how to create debug log. When I run face-recognition and digikam crash it cause shutdown of system. How to get log after restart? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419008] Always crash in Regional Setting within System Settings
https://bugs.kde.org/show_bug.cgi?id=419008 p.van.damme1...@gmail.com changed: What|Removed |Added CC||p.van.damme1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418939] Crash when search faces
https://bugs.kde.org/show_bug.cgi?id=418939 --- Comment #14 from caulier.gil...@gmail.com --- It crash and shutdown computer using 7.0.0-beta3 AppImage ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368351] [UGEE] Pen cursor lags behind/doesn't respond when pen is hovering above tablet screen
https://bugs.kde.org/show_bug.cgi?id=368351 Kashe changed: What|Removed |Added CC||johnsonka...@icloud.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 419048] Baloo file extractor constantly crashes when I boot
https://bugs.kde.org/show_bug.cgi?id=419048 Stefan Brüns changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Stefan Brüns --- Debians packages are outdated. Please use a distribution which provides current packages. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 --- Comment #11 from Nate Graham --- Out of curiosity, are the people experiencing this using encrypted home directories? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418939] Crash when search faces
https://bugs.kde.org/show_bug.cgi?id=418939 --- Comment #15 from Clon --- Yes. (Log is from run without crash.) -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 419038] internal not specified error in libsmbclient in Network SMB search
https://bugs.kde.org/show_bug.cgi?id=419038 Nate Graham changed: What|Removed |Added Product|dolphin |kio-extras Component|general |Samba CC||n...@kde.org Assignee|dolphin-bugs-n...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419004] Krita window doesnt show name of file that is open
https://bugs.kde.org/show_bug.cgi?id=419004 --- Comment #2 from Sonia --- Sorry, I meant right at the very top left corner of the main Krita window. Its easier to see which tab is active and with the asterisk, its a reminder to save my work...but the title or filename is replaced by a ~ On Thu, Mar 19, 2020 at 6:18 AM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=419004 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > CC||b...@valdyas.org > Resolution|--- |INTENTIONAL > > --- Comment #1 from Boudewijn Rempt --- > Yes... In tabbed mode the filename is shown in the tab. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419004] Krita window doesnt show name of file that is open
https://bugs.kde.org/show_bug.cgi?id=419004 --- Comment #3 from Sonia --- Sorry, I meant at the very top left of the main Krita window. The title or name of the file that is active is usually displayed up there and when it has an asterisk I know it needs to be saved or not. But right now it just shows up as a tilde. On Thu, Mar 19, 2020 at 6:18 AM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=419004 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > CC||b...@valdyas.org > Resolution|--- |INTENTIONAL > > --- Comment #1 from Boudewijn Rempt --- > Yes... In tabbed mode the filename is shown in the tab. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 416131] Elisa doesn't export the Album Art to the Media Player applet
https://bugs.kde.org/show_bug.cgi?id=416131 --- Comment #14 from Nate Graham --- Yeah, it's trying to install Elisa on top of the system version in /usr, which is incorrect. It looks like your ~/.kdesrc-buildrc file is misconfigured. The correct values in that file are more like this: # Install directory for KDE software kdedir ~/kde/usr # Directory for downloaded source code source-dir ~/kde/src # Directory to build KDE into before installing # relative to source-dir by default build-dir ~/kde/build Also these kinds of questions would ideally be asked in the kde-devel channel. See https://community.kde.org/Get_Involved#Getting_in_touch_and_working_together -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 416131] Elisa doesn't export the Album Art to the Media Player applet
https://bugs.kde.org/show_bug.cgi?id=416131 Matthieu Gallien changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||elisa/commit/e674a748c18b14 ||161d71538522c33838c1735f52 Resolution|--- |FIXED --- Comment #15 from Matthieu Gallien --- Git commit e674a748c18b14161d71538522c33838c1735f52 by Matthieu Gallien. Committed on 20/03/2020 at 15:00. Pushed by mgallien into branch 'release/20.04'. fix invalid URL when sending cover image in mpris for embedded covers use a base 64 encoded data url with inline image data M +21 -1src/mpris2/mediaplayer2player.cpp https://invent.kde.org/kde/elisa/commit/e674a748c18b14161d71538522c33838c1735f52 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419049] New: KWin crashes seemingly at random
https://bugs.kde.org/show_bug.cgi?id=419049 Bug ID: 419049 Summary: KWin crashes seemingly at random Product: kwin Version: 5.18.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: t.krabbe+...@protonmail.com Target Milestone: --- Application: kwin_x11 (5.18.3) Qt Version: 5.14.1 Frameworks Version: 5.68.0 Operating System: Linux 5.5.10-arch1-1 x86_64 Windowing system: X11 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Firefox was focused. Other than that I don't remember doing anything special. I've been having ominous crashes every now and again, and I *feel* like this particular crash may be related to Firefox in some way, since this particular crash caused Plasma to restart and actually keep all applications open. I believe such a crash has occured before, and Firefox was open then, as well. But I don't remember this accurately enough to be sure. The other crashes I've been experiencing have caused my system to freeze unrecoverably, so I think those are probably caused by something else. Many thanks in advance for looking at this! The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7a403490c0 (LWP 4073))] Thread 36 (Thread 0x7f7929891700 (LWP 8945)): #0 0x7f7a458f2cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7a2e64299c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f7a2e642598 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f7a458ec46f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f7a47fcc3d3 in clone () at /usr/lib/libc.so.6 Thread 35 (Thread 0x7f793d91a700 (LWP 8235)): #0 0x7f7a458f2cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7a2e64299c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f7a2e642598 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f7a458ec46f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f7a47fcc3d3 in clone () at /usr/lib/libc.so.6 Thread 34 (Thread 0x7f79366d3700 (LWP 7385)): #0 0x7f7a458f2cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7a4672bcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f7a4672bda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f7a4539d56b in () at /usr/lib/libQt5Quick.so.5 #4 0x7f7a4539d7fb in () at /usr/lib/libQt5Quick.so.5 #5 0x7f7a46725fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7f7a458ec46f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f7a47fcc3d3 in clone () at /usr/lib/libc.so.6 Thread 33 (Thread 0x7f792a092700 (LWP 7384)): #0 0x7f7a458f2cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7a2e64299c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f7a2e642598 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f7a458ec46f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f7a47fcc3d3 in clone () at /usr/lib/libc.so.6 Thread 32 (Thread 0x7f793511b700 (LWP 6065)): #0 0x7f7a47fc1bb6 in ppoll () at /usr/lib/libc.so.6 #1 0x7f7a46956023 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f7a469576ed in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f7a4690057c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f7a46724e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f7a45035f89 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f7a46725fd6 in () at /usr/lib/libQt5Core.so.5 #7 0x7f7a458ec46f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f7a47fcc3d3 in clone () at /usr/lib/libc.so.6 Thread 31 (Thread 0x7f79d27fc700 (LWP 6064)): #0 0x7f7a458f2cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7a2e64299c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f7a2e642598 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f7a458ec46f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f7a47fcc3d3 in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7f7a3dc2c700 (LWP 6007)): #0 0x7f7a458f2cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7a2e64299c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f7a2e642598 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f7a458ec46f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f7a47fcc3d3 in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7f793f6f7700 (LWP 5180)): #0 0x7f7a458f2cf5 in pthread_cond_wait@@GLIBC_2.3.2 (
[kwin] [Bug 419049] KWin crashes seemingly at random
https://bugs.kde.org/show_bug.cgi?id=419049 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Can you get debug symbols for: #9 0x7f7a46362ae7 in () at /usr/lib/libkwin4_effect_builtins.so.1 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 364708] kioexec error on sftp
https://bugs.kde.org/show_bug.cgi?id=364708 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419049] KWin crashes seemingly at random
https://bugs.kde.org/show_bug.cgi?id=419049 --- Comment #2 from Tronje Krabbe --- (In reply to David Edmundson from comment #1) > Can you get debug symbols for: > > #9 0x7f7a46362ae7 in () at /usr/lib/libkwin4_effect_builtins.so.1 I'll be happy to if you tell me how! -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 --- Comment #12 from Richard Ullger --- (In reply to Nate Graham from comment #11) > Out of curiosity, are the people experiencing this using encrypted home > directories? I myself am not using an encrypted home directory. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-sonnet] [Bug 410113] Please make this message more specific: Warning: No language dictionaries for the language
https://bugs.kde.org/show_bug.cgi?id=410113 Herrold changed: What|Removed |Added CC||herr...@owlriver.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419050] Appimage launches, but crashes as soon as a clip is added or a project is loaded
https://bugs.kde.org/show_bug.cgi?id=419050 Mathieu Hery changed: What|Removed |Added Summary|Appimage crashes launches, |Appimage launches, but |but crashes as soon as a|crashes as soon as a clip |clip is added or a project |is added or a project is |is loaded |loaded -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419050] New: Appimage crashes launches, but crashes as soon as a clip is added or a project is loaded
https://bugs.kde.org/show_bug.cgi?id=419050 Bug ID: 419050 Summary: Appimage crashes launches, but crashes as soon as a clip is added or a project is loaded Product: kdenlive Version: 19.12.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: m...@mh8.fr Target Milestone: --- SUMMARY Everything was working fine on my STEPS TO REPRODUCE 1. Launch Kdenlive 2. Add a clip or load a project 3. kdenlive crashes SOFTWARE/OS VERSIONS Linux Mint 19.3 Cinnamon (4.4.8) Kernel (5.3.0-42-generic x86_64) ADDITIONAL INFORMATION This is what I get when I launch any of the 19.12 Appimages : ~/Media$ ./kdenlive-19.12.3-x86_64.appimage No LADSPA plugins were found! Check your LADSPA_PATH environment variable. WARNING : Fails to parse "avcolour_space" WARNING : Fails to parse "avcolor_space" WARNING : Fails to parse "avdeinterlace" WARNING : Fails to parse "swscale" "avfilter.abench" is blacklisted "avfilter.acompressor" is blacklisted "avfilter.adelay" is blacklisted "avfilter.aecho" is blacklisted "avfilter.aemphasis" is blacklisted "avfilter.aeval" is blacklisted "avfilter.afade" is blacklisted "avfilter.afftfilt" is blacklisted "avfilter.agate" is blacklisted "avfilter.ametadata" is blacklisted "avfilter.arealtime" is blacklisted "avfilter.ashowinfo" is blacklisted "avfilter.channelmap" is blacklisted "avfilter.chorus" is blacklisted "avfilter.earwax" is blacklisted "avfilter.volume" is blacklisted "avfilter.volumedetect" is blacklisted "avfilter.atadenoise" is blacklisted "avfilter.avgblur" is blacklisted "avfilter.bbox" is blacklisted "avfilter.bench" is blacklisted "avfilter.blackdetect" is blacklisted "avfilter.blackframe" is blacklisted "avfilter.boxblur" is blacklisted "avfilter.bwdif" is blacklisted "avfilter.chromakey" is blacklisted "avfilter.colorkey" is blacklisted "avfilter.colormatrix" is blacklisted "avfilter.colorspace" is blacklisted "avfilter.convolution" is blacklisted "avfilter.crop" is blacklisted "avfilter.cropdetect" is blacklisted "avfilter.curves" is blacklisted "avfilter.datascope" is blacklisted "avfilter.dctdnoiz" is blacklisted "avfilter.deband" is blacklisted "avfilter.deflate" is blacklisted "avfilter.deshake" is blacklisted "avfilter.despill" is blacklisted "avfilter.doubleweave" is blacklisted "avfilter.drawbox" is blacklisted "avfilter.drawgraph" is blacklisted "avfilter.drawgrid" is blacklisted "avfilter.elbg" is blacklisted "avfilter.eq" is blacklisted "avfilter.fade" is blacklisted "avfilter.field" is blacklisted "avfilter.fieldhint" is blacklisted "avfilter.fieldorder" is blacklisted "avfilter.find_rect" is blacklisted "avfilter.floodfill" is blacklisted "avfilter.fspp" is blacklisted "avfilter.gblur" is blacklisted "avfilter.geq" is blacklisted "avfilter.hflip" is blacklisted "avfilter.hqdn3d" is blacklisted "avfilter.hqx" is blacklisted "avfilter.hue" is blacklisted "avfilter.hwdownload" is blacklisted "avfilter.idet" is blacklisted "avfilter.il" is blacklisted "avfilter.lenscorrection" is blacklisted "avfilter.loop" is blacklisted "avfilter.lumakey" is blacklisted "avfilter.lut" is blacklisted "avfilter.lutrgb" is blacklisted "avfilter.lutyuv" is blacklisted "avfilter.mcdeint" is blacklisted "avfilter.metadata" is blacklisted "avfilter.negate" is blacklisted "avfilter.nlmeans" is blacklisted "avfilter.nnedi" is blacklisted "avfilter.owdenoise" is blacklisted "avfilter.pad" is blacklisted "avfilter.perspective" is blacklisted "avfilter.phase" is blacklisted "avfilter.pixscope" is blacklisted "avfilter.pp" is blacklisted "avfilter.pp7" is blacklisted "avfilter.prewitt" is blacklisted "avfilter.realtime" is blacklisted "avfilter.removegrain" is blacklisted "avfilter.removelogo" is blacklisted "avfilter.roberts" is blacklisted "avfilter.rotate" is blacklisted "avfilter.showinfo" is blacklisted "avfilter.shuffleframes" is blacklisted "avfilter.sidedata" is blacklisted "avfilter.signalstats" is blacklisted "avfilter.sobel" is blacklisted "avfilter.stereo3d" is blacklisted "avfilter.super2xsai" is blacklisted "avfilter.swapuv" is blacklisted "avfilter.tblend" is blacklisted "avfilter.tlut2" is blacklisted "avfilter.tonemap" is blacklisted "avfilter.transpose" is blacklisted "avfilter.vectorscope" is blacklisted "avfilter.vflip" is blacklisted "avfilter.vignette" is blacklisted "avfilter.vmafmotion" is blacklisted "avfilter.w3fdif" is blacklisted "avfilter.xbr" is blacklisted "avfilter.yadif" is blacklisted "avfilter.zoompan" is blacklisted WARNING : Fails to parse "swresample" WARNING : Fails to parse "audiochannels" WARNING : Fails to parse "audioconvert" WARNING : Fails to parse "data_feed" "data_show" is blacklisted WARNING : Fails to parse "imageconvert" "mask_apply" is blacklisted "mask_start" is blacklisted "mono"
[frameworks-sonnet] [Bug 410113] Please make this message more specific: Warning: No language dictionaries for the language
https://bugs.kde.org/show_bug.cgi?id=410113 --- Comment #1 from Herrold --- I see this as well Mar 20 11:22:26 centos-8 /usr/libexec/gdm-x-session[3130]: sonnet.core: No language dictionaries for the language: "C" Mar 20 11:22:26 centos-8 /usr/libexec/gdm-x-session[3130]: sonnet.core: No language dictionaries for the language: "C" Mar 20 11:22:26 centos-8 /usr/libexec/gdm-x-session[3130]: sonnet.core: No language dictionaries for the language: "C" There are two requests here, it seems: 1. a more descriptive error message to permit running down what is needed 2. suppression of repeated messaging of the same message from bug: https://github.com/qTox/qTox/issues/5741 my values are: [herrold@centos-8 pw]$ locale LANG=en_US LC_CTYPE="C" LC_NUMERIC="C" LC_TIME="C" LC_COLLATE="C" LC_MONETARY="C" LC_MESSAGES="C" LC_PAPER="C" LC_NAME="C" LC_ADDRESS="C" LC_TELEPHONE="C" LC_MEASUREMENT="C" LC_IDENTIFICATION="C" LC_ALL=C [herrold@centos-8 pw]$ locale | grep "LC_CTYPE" LC_CTYPE="C" [herrold@centos-8 pw]$ locale | grep "LANG" LANG=en_US [herrold@centos-8 pw]$ env | grep '\' LC_ALL=C [herrold@centos-8 pw]$ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419050] Appimage launches, but crashes as soon as a clip is added or a project is loaded
https://bugs.kde.org/show_bug.cgi?id=419050 --- Comment #1 from Mathieu Hery --- SUMMARY //Summary is incomplete in above. Should be : Everything was working fine on my computer up until this week 16-18/03/2020 approx. Something must have been updated through the repos of linux mint (ubuntu based) since I do my updates daily. Since then, kdenlive simply does not work anymore. Crashes after launch as soon as I add a clip or open a project. I don't understand how this could be as I always work with the AppImage and I thought the AppImages bundled all their dependencies in the package. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server
https://bugs.kde.org/show_bug.cgi?id=390798 --- Comment #22 from Igor Poboiko --- Git commit 7afd99abbfa141f6e6dfbe69b01827af8f16ba27 by Igor Poboiko. Committed on 20/03/2020 at 16:10. Pushed by poboiko into branch 'master'. [resources/ews] Save password to wallet Summary: Seems like the password entered via the UI actually never gets saved anywhere. Just do it explicitly. Related: bug 393002, bug 402780, bug 414789 Test Plan: 1) Try to setup EWS account using autodiscovery, using Username/Password auth 2) Set Username, Password, hit "Try connect" -> it works fine 3) Hit "OK" -> observe "Authentication failure" resource error 4) Browse `akonadi-ews` via `KWalletManager` -> it's empty 5) Apply the patch, repeat 1-4 - authentication succeeds, password entry inside wallet appears Reviewers: dvratil, nowicki Reviewed By: dvratil Subscribers: kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D27813 M +1-0resources/ews/ewsconfigdialog.cpp https://commits.kde.org/kdepim-runtime/7afd99abbfa141f6e6dfbe69b01827af8f16ba27 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 402780] Akonadi doesn't work with Exchange again
https://bugs.kde.org/show_bug.cgi?id=402780 --- Comment #20 from Igor Poboiko --- Git commit 7afd99abbfa141f6e6dfbe69b01827af8f16ba27 by Igor Poboiko. Committed on 20/03/2020 at 16:10. Pushed by poboiko into branch 'master'. [resources/ews] Save password to wallet Summary: Seems like the password entered via the UI actually never gets saved anywhere. Just do it explicitly. Related: bug 393002, bug 390798, bug 414789 Test Plan: 1) Try to setup EWS account using autodiscovery, using Username/Password auth 2) Set Username, Password, hit "Try connect" -> it works fine 3) Hit "OK" -> observe "Authentication failure" resource error 4) Browse `akonadi-ews` via `KWalletManager` -> it's empty 5) Apply the patch, repeat 1-4 - authentication succeeds, password entry inside wallet appears Reviewers: dvratil, nowicki Reviewed By: dvratil Subscribers: kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D27813 M +1-0resources/ews/ewsconfigdialog.cpp https://commits.kde.org/kdepim-runtime/7afd99abbfa141f6e6dfbe69b01827af8f16ba27 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414789] Authentication failed even though server replies Auth is ok
https://bugs.kde.org/show_bug.cgi?id=414789 --- Comment #1 from Igor Poboiko --- Git commit 7afd99abbfa141f6e6dfbe69b01827af8f16ba27 by Igor Poboiko. Committed on 20/03/2020 at 16:10. Pushed by poboiko into branch 'master'. [resources/ews] Save password to wallet Summary: Seems like the password entered via the UI actually never gets saved anywhere. Just do it explicitly. Related: bug 393002, bug 390798, bug 402780 Test Plan: 1) Try to setup EWS account using autodiscovery, using Username/Password auth 2) Set Username, Password, hit "Try connect" -> it works fine 3) Hit "OK" -> observe "Authentication failure" resource error 4) Browse `akonadi-ews` via `KWalletManager` -> it's empty 5) Apply the patch, repeat 1-4 - authentication succeeds, password entry inside wallet appears Reviewers: dvratil, nowicki Reviewed By: dvratil Subscribers: kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D27813 M +1-0resources/ews/ewsconfigdialog.cpp https://commits.kde.org/kdepim-runtime/7afd99abbfa141f6e6dfbe69b01827af8f16ba27 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet
https://bugs.kde.org/show_bug.cgi?id=393002 Igor Poboiko changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://commits.kde.org/kde |https://commits.kde.org/kde |pim-runtime/b5ee6ff11cd3a7e |pim-runtime/7afd99abbfa141f |0c28305b351d28c5f244f101e |6e6dfbe69b01827af8f16ba27 Status|REOPENED|RESOLVED --- Comment #18 from Igor Poboiko --- Git commit 7afd99abbfa141f6e6dfbe69b01827af8f16ba27 by Igor Poboiko. Committed on 20/03/2020 at 16:10. Pushed by poboiko into branch 'master'. [resources/ews] Save password to wallet Summary: Seems like the password entered via the UI actually never gets saved anywhere. Just do it explicitly. Related: bug 390798, bug 402780, bug 414789 Test Plan: 1) Try to setup EWS account using autodiscovery, using Username/Password auth 2) Set Username, Password, hit "Try connect" -> it works fine 3) Hit "OK" -> observe "Authentication failure" resource error 4) Browse `akonadi-ews` via `KWalletManager` -> it's empty 5) Apply the patch, repeat 1-4 - authentication succeeds, password entry inside wallet appears Reviewers: dvratil, nowicki Reviewed By: dvratil Subscribers: kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D27813 M +1-0resources/ews/ewsconfigdialog.cpp https://commits.kde.org/kdepim-runtime/7afd99abbfa141f6e6dfbe69b01827af8f16ba27 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #129 from sima...@gmail.com --- (In reply to Luca Carlon from comment #128) > What system? Kubuntu 19.10 Qt Version: 5.12.4 I was able to install the package and the freezing hasn't occurred (yet). But I was convinced the package was to upgrade to Qt 5.12.5. The version the issue was fixed in. But I think I was mistaken, since my Qt version stayed the same. I'm a bit confused :D -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419051] New: Discover won't open
https://bugs.kde.org/show_bug.cgi?id=419051 Bug ID: 419051 Summary: Discover won't open Product: Discover Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: javama...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-38-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: In the tray I have a notification that updates are available, I click it, Discover starts to open, then crashes. If I use the application menu to start Discover, it also starts to open, then crashes. This has been happening for over a month now. Preventing my system from updating normally. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f197d6e7680 (LWP 3421))] Thread 11 (Thread 0x7f195485a700 (LWP 3513)): #0 0x7f19801f5c68 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f19801a995e in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f19801a9b73 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f19819c8653 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f198196f5cb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f19817a8a45 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f19817a9c92 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1980b7e669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f198142e323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f19557fa700 (LWP 3507)): #0 0x7f1980b856e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7f19557f9bd0, clockid=, expected=0, futex_word=0x7f1940007190) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7f1980b856e0 in __pthread_cond_wait_common (abstime=0x7f19557f9bd0, clockid=, mutex=0x7f1940007140, cond=0x7f1940007168) at pthread_cond_wait.c:520 #2 0x7f1980b856e0 in __pthread_cond_timedwait (cond=0x7f1940007168, mutex=0x7f1940007140, abstime=0x7f19557f9bd0) at pthread_cond_wait.c:656 #3 0x7f19817afd2c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f19817afe7b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f19817ad421 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f19817a9c92 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1980b7e669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f198142e323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f1955ffb700 (LWP 3506)): #0 0x7f1980b856e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7f1955ffabd0, clockid=, expected=0, futex_word=0x7f19400054b4) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7f1980b856e0 in __pthread_cond_wait_common (abstime=0x7f1955ffabd0, clockid=, mutex=0x7f1940005460, cond=0x7f1940005488) at pthread_cond_wait.c:520 #2 0x7f1980b856e0 in __pthread_cond_timedwait (cond=0x7f1940005488, mutex=0x7f1940005460, abstime=0x7f1955ffabd0) at pthread_cond_wait.c:656 #3 0x7f19817afd2c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f19817afe7b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f19817ad421 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f19817a9c92 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1980b7e669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f198142e323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f19567fc700 (LWP 3505)): #0 0x7f1981421c2f in __GI___poll (fds=0x7f194000c7f0, nfds=1, timeout=12603) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f19801a9a3e in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f19801a9b73 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f19819c8653 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f198196f5cb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f19817a8a45 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f19817a9c92 in () at /usr/lib/x86_
[Discover] [Bug 419051] Discover won't open
https://bugs.kde.org/show_bug.cgi?id=419051 javama...@gmail.com changed: What|Removed |Added CC||javama...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419051] Discover won't open
https://bugs.kde.org/show_bug.cgi?id=419051 --- Comment #1 from javama...@gmail.com --- Created attachment 126908 --> https://bugs.kde.org/attachment.cgi?id=126908&action=edit New crash information added by DrKonqi plasma-discover (5.16.5) using Qt 5.12.4 - What I was doing when the application crashed: In the tray I have a notification that updates are available, I click it, Discover starts to open, then crashes. If I use the application menu to start Discover, it also starts to open, then crashes. This has been happening for over a month now. Preventing my system from updating normally. -- Backtrace (Reduced): #6 0x7f8661f823eb in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7f8661f61899 in __GI_abort () at abort.c:79 #8 0x7f86623a0a99 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f866413c94d in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f866413da25 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419052] New: Copy a clip with speed changed it results a pasted clip with speed 0%
https://bugs.kde.org/show_bug.cgi?id=419052 Bug ID: 419052 Summary: Copy a clip with speed changed it results a pasted clip with speed 0% Product: kdenlive Version: 19.12.2 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: josema...@hotmail.com Target Milestone: --- Created attachment 126909 --> https://bugs.kde.org/attachment.cgi?id=126909&action=edit screen capture SUMMARY When copy-paste a clip that has been change the speed, only paste a clip with a speed of 0%, so it seems to be a single frame STEPS TO REPRODUCE 1. Change the speed of a clip (no matter up or down) 2. Copy the clip 3. Paste the clip in other location 4. Zoom in the paste location and it will apear a single frame. Select it to check the seep propertie is 0% 5. Sometimes it produces a crash (probably if several clips with 0% speed are pasted) 6. Right clip to change speed via textbox, but i cannot introduce numbers into it OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 419053] New: Night Color conflicts with DisplayCAL color profile
https://bugs.kde.org/show_bug.cgi?id=419053 Bug ID: 419053 Summary: Night Color conflicts with DisplayCAL color profile Product: kdeplasma-addons Version: 5.18.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Night Color Control Assignee: plasma-b...@kde.org Reporter: i...@guoyunhe.me CC: kwin-bugs-n...@kde.org, vlad.zahorod...@kde.org Target Milestone: --- Created attachment 126910 --> https://bugs.kde.org/attachment.cgi?id=126910&action=edit color profile generated by DisplayCAL SUMMARY My monitors are calibrated with DisplayCAL + DataColor Spyder 5. This means it load a color profile when the system boots. When it is time to shift night color, the color profile is reset and becomes bluish, and then gradually turns warmer. STEPS TO REPRODUCE 1. Calibrate your monitor with DisplayCAL. If you don't have a device, you can try the color profile in attachment. 2. Wait the night color start. 3. Observe the transition. OBSERVED RESULT The color was first reset to default, which is usually more cold/bluish than calibrated color, and then it turns warm gradually. EXPECTED RESULT The color should change smoothly from the calibrated color to night color. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200314 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.5.7-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 31.1 GiB ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419022] Circle to quickly choose tool does not select tool, needs double click to stay open
https://bugs.kde.org/show_bug.cgi?id=419022 --- Comment #3 from Postix --- > Does your mouse behave well when you use it > to bring up the popup palette in this way? Yes, it was works absolutely flawless. > Hover your pen over the grid area and press your button-2. > You should get a continuous stream of records > with B=2 (due to slight movements of your pen). > If you quickly release button-2 and then press it again, > you should get a single B=0 record before > the repeated B=2 records begin again. This seems to work as expected. There's a continuous stream when I press the Button 2 close to the surface. Further, here's the output, after I pressed the button only once: Pen tip brought near Stylus press X=589.78 Y=225.76 B=2 P=0.0% Stylus move X=588.91 Y=226.33 B=2 P=0.0% (DRAW) Stylus move X=587.96 Y=226.97 B=2 P=0.0% (DRAW) Stylus move X=587.10 Y=227.68 B=2 P=0.0% (DRAW) Stylus move X=586.31 Y=228.32 B=2 P=0.0% (DRAW) Stylus move X=585.67 Y=228.53 B=2 P=0.0% (DRAW) Stylus move X=585.04 Y=229.24 B=2 P=0.0% (DRAW) Stylus move X=584.80 Y=229.24 B=2 P=0.0% (DRAW) Stylus move X=584.17 Y=229.24 B=2 P=0.0% (DRAW) Stylus move X=584.09 Y=229.24 B=2 P=0.0% (DRAW) Stylus move X=584.01 Y=229.03 B=2 P=0.0% (DRAW) Stylus move X=584.01 Y=228.32 B=2 P=0.0% (DRAW) Stylus move X=584.17 Y=228.10 B=2 P=0.0% (DRAW) Stylus move X=584.80 Y=227.11 B=2 P=0.0% (DRAW) Stylus move X=585.59 Y=226.18 B=2 P=0.0% (DRAW) Stylus move X=586.62 Y=225.05 B=2 P=0.0% (DRAW) Stylus release X=586.62 Y=225.05 B=0 P=0.0% Pen tip taken away -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 418814] Ripping CD fails on tracks containing question marks
https://bugs.kde.org/show_bug.cgi?id=418814 --- Comment #5 from forenk...@gmx.de --- Ok, it turns out, that this is not a bug, but an option of the ntfs-3g driver to restrict file naming to names that are valid on Windows (makes sense). It turns out and is documented here, https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions that the question mark is invalid for file naming in Windows. I understand that it is not the duty of the k3b devs to worry about (notably) Windows file systems, however, since it is desirable to use music files that have been ripped on one platform on a possibly entirely other platform, I would suggest to consider removing the characters described in the above link to make the files more platform independent, i.e. Windows compatible. If you don't want to implement this by default, then it would be desirable to have it as an option. Cheers -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419054] New: Unhandled syscall getcpu on arm32
https://bugs.kde.org/show_bug.cgi?id=419054
Bug ID: 419054
Summary: Unhandled syscall getcpu on arm32
Product: valgrind
Version: 3.15 SVN
Platform: Other
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: igor.snu...@gmail.com
Target Milestone: ---
Created attachment 126911
--> https://bugs.kde.org/attachment.cgi?id=126911&action=edit
Patch: enabling getcpu on arm32
SUMMARY
STEPS TO REPRODUCE
1.
run the following code on an arm-32 platform (in my case, a raspberry pi).
#include
int main () {
printf("getcpu = %d\n", sched_getcpu());
return 0;
}
OBSERVED RESULT
==19515== Memcheck, a memory error detector
==19515== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==19515== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==19515== Command: ./getcpu
==19515==
--19515-- WARNING: unhandled arm-linux syscall: 345
--19515-- You may be able to write your own handler.
--19515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--19515-- Nevertheless we consider this a bug. Please report
--19515-- it at http://valgrind.org/support/bug_reports.html.
getcpu = -1
==19515==
==19515== HEAP SUMMARY:
==19515== in use at exit: 0 bytes in 0 blocks
==19515== total heap usage: 1 allocs, 1 frees, 4,096 bytes allocated
==19515==
==19515== All heap blocks were freed -- no leaks are possible
==19515==
==19515== For lists of detected and suppressed errors, rerun with: -s
==19515== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
EXPECTED RESULT
==19525== Memcheck, a memory error detector
==19525== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==19525== Using Valgrind-3.16.0.GIT and LibVEX; rerun with -h for copyright
info
==19525== Command: ./getcpu
==19525==
getcpu = 0
==19525==
==19525== HEAP SUMMARY:
==19525== in use at exit: 0 bytes in 0 blocks
==19525== total heap usage: 1 allocs, 1 frees, 4,096 bytes allocated
==19525==
==19525== All heap blocks were freed -- no leaks are possible
==19525==
==19525== For lists of detected and suppressed errors, rerun with: -s
==19525== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
ADDITIONAL INFORMATION
I reached this situation while debugging a dotnet application.
The patch is attached. By just simply uncommenting the syscall on
syswrap-arm-linux.c, it was possible to make it work and return the correct
output.
Regards.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 419022] Circle to quickly choose tool does not select tool, needs double click to stay open
https://bugs.kde.org/show_bug.cgi?id=419022 --- Comment #4 from Ahab Greybeard --- Then this is a mystery. You'll need to wait for someone else to suggest other diagnostic tests :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels uses the entire width
https://bugs.kde.org/show_bug.cgi?id=417852 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Christoph Feck --- Requested information was added with comment 2; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #130 from Luca Carlon --- No, the package is 5.12.4 patched. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419008] Always crash in Regional Setting within System Settings
https://bugs.kde.org/show_bug.cgi?id=419008 --- Comment #3 from Yaroslav Sidlovsky --- When I run "kcmshell5 kcm_translations" in the console I see following errors: file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:128:13: QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling. file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:39: TypeError: Cannot read property 'LanguageCode' of null file:///usr/share/kpackage/kcms/kcm_translations/contents/ui/main.qml:43: TypeError: Cannot read property 'display' of null KCrash: Application 'kcmshell5' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 417010] Dolphin crashes on startup with/after black desktop OpenSuse 15.1
https://bugs.kde.org/show_bug.cgi?id=417010 Christoph Feck changed: What|Removed |Added Version|18.12.3 |5.55.0 Resolution|WAITINGFORINFO |--- Product|dolphin |frameworks-kcoreaddons Component|general |general CC||kdelibs-b...@kde.org Status|NEEDSINFO |REPORTED Assignee|dolphin-bugs-n...@kde.org |mp...@kde.org --- Comment #5 from Christoph Feck --- According to comment 4 the crash is still happening. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419022] Circle to quickly choose tool does not select tool, needs double click to stay open
https://bugs.kde.org/show_bug.cgi?id=419022 --- Comment #5 from Postix --- (In reply to Ahab Greybeard from comment #4) > Then this is a mystery. You'll need to wait for someone else to suggest > other diagnostic tests :( If I press very very short, i.e. as quickly as I can, it works reliable with the pen. But if I press ~10-20 ms too long, the circle vanishes. This may be a clue! Also, this issue seems to be independed of the set sampling rate or suppression rate. There was no change when I changed on the values to either end. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416914] Connecting external monitor freezes Plasma
https://bugs.kde.org/show_bug.cgi?id=416914 --- Comment #11 from Christoph Feck --- > ptrace: Operation not permitted. Please ask for help in a forum of your distribution how to generate a backtrace for this case. gdb should be able to attach to a running process, unless the process has already exited. -- You are receiving this mail because: You are watching all bug changes.
