[digikam] [Bug 401386] Cannot save rotated image
https://bugs.kde.org/show_bug.cgi?id=401386 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- In her digiKam version there is a problem with the control points. Aver you can take a rotated image with "OK" and then save. Possibly take a screenshot or test the latest digiKam-6.0.0-Beta3: https://files.kde.org/digikam/ Backup your databases. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 384716] TypeScript Highlighting
https://bugs.kde.org/show_bug.cgi?id=384716 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.53 CC||nibg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379604] Preview rendering warning - AVStream.codec is deprecated
https://bugs.kde.org/show_bug.cgi?id=379604 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379682] Kdenlive saving stop working
https://bugs.kde.org/show_bug.cgi?id=379682 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400892] KWin Crashed after Present Windows All Desktops
https://bugs.kde.org/show_bug.cgi?id=400892 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400919] Desktop effects not working and system settings crashing
https://bugs.kde.org/show_bug.cgi?id=400919 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 397549] Searching for tags in Dolphin doesn't always work
https://bugs.kde.org/show_bug.cgi?id=397549 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 345817] keyboard repeat rate seems to break in konsole
https://bugs.kde.org/show_bug.cgi?id=345817 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374095] QOffscreenSurface created off the main/gui thread
https://bugs.kde.org/show_bug.cgi?id=374095 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378905] german translation issue Auswahlwerkzeug vs Abstandswerkzeug
https://bugs.kde.org/show_bug.cgi?id=378905 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401387] New: Glitch on screen when switching virtual desktop through cube effect with 'Do not animate panels' enabled
https://bugs.kde.org/show_bug.cgi?id=401387 Bug ID: 401387 Summary: Glitch on screen when switching virtual desktop through cube effect with 'Do not animate panels' enabled Product: kwin Version: 5.14.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: henriquesarmentogoulartagu...@gmail.com Target Milestone: --- Created attachment 116494 --> https://bugs.kde.org/attachment.cgi?id=116494=edit I recorded the animation, and took a screenshot (from VLC) of the bug. SUMMARY When I use shortcut keys to switch virtual desktops, with the 3D cube animation, and specifically 'Do not animate panels' enabled, a glitch appears on the top right of my screen for the duration of the effect. STEPS TO REPRODUCE 1. Choose 'Desktop Cube Animations' on desktop effects. 2. On the options, enable 'Do not animate panels' (though it's enabled by default) 3. Use shortcut keys to switch between virtual desktops. OBSERVED RESULT A glitch (which appears to be based on the desktop itself) appears on the top right of the screen. EXPECTED RESULT That shouldn't happen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION This has not been tested without shortkeys or with other animations. -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 401381] Apper crashes after any update
https://bugs.kde.org/show_bug.cgi?id=401381 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401386] New: Cannot save rotated image
https://bugs.kde.org/show_bug.cgi?id=401386 Bug ID: 401386 Summary: Cannot save rotated image Product: digikam Version: 5.7.0 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor-Tool-Rotation Assignee: digikam-bugs-n...@kde.org Reporter: lmtri...@embarqmail.com Target Milestone: --- SUMMARY Cannot save rotated image STEPS TO REPRODUCE 1. Image Editor 2. Transform 3. Free Rotation 4. use two point/automatic method to improve image OBSERVED RESULT Image rotates perfectly but option to Save is greyed-out. Rotated image cannot be saved. At least some other Transform options work fine. EXPECTED RESULT Should have the option to save rotated image. SOFTWARE/OS VERSIONS Windows: 7 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.
[Discover] [Bug 401385] New: Discover crash after opening application to install through search bar
https://bugs.kde.org/show_bug.cgi?id=401385 Bug ID: 401385 Summary: Discover crash after opening application to install through search bar Product: Discover Version: 5.13.5 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: vladislav.mcand...@gmail.com Target Milestone: --- Application: plasma-discover (5.13.5) Qt Version: 5.11.2 Frameworks Version: 5.49.0 Operating System: Linux 4.18.0-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: i was searching for an application through the kde search bar and it opened up the sugestion for it and then crashed. i was unable to do anything before it crashed. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f32bccad300 (LWP 4733))] Thread 14 (Thread 0x7f328a3fc700 (LWP 4760)): #0 0x7f32c1de6204 in __GI___libc_read (fd=26, buf=0x7f328a3fbb80, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f32bfed0180 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f32bfe8a91f in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f32bfe8adf0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f32bfe8af6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f32c22fbd2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f32c22a8d0b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f32c20f80c6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f32c2101c97 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f32c0e94f2a in start_thread (arg=0x7f328a3fc700) at pthread_create.c:463 #10 0x7f32c1df4edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f328affd700 (LWP 4756)): #0 0x7f32c1de6204 in __GI___libc_read (fd=54, buf=0x7f328affcb80, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f32bfed0180 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f32bfe8a91f in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f32bfe8adf0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f32bfe8af6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f32c22fbd2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f32c22a8d0b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f32c20f80c6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f32c2101c97 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f32c0e94f2a in start_thread (arg=0x7f328affd700) at pthread_create.c:463 #10 0x7f32c1df4edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f328b7fe700 (LWP 4754)): #0 0x7f32c1dea739 in __GI___poll (fds=0x55e20baf8d00, nfds=1, timeout=115098) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f32bfe8ae46 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f32bfe8af6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f32c22fbd2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f32c22a8d0b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f32c20f80c6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f32c2101c97 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f32c0e94f2a in start_thread (arg=0x7f328b7fe700) at pthread_create.c:463 #8 0x7f32c1df4edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f328bfff700 (LWP 4748)): #0 0x7f32c0e9b19a in futex_reltimed_wait_cancelable (private=, reltime=0x7f328bffec50, expected=0, futex_word=0x7f328c008bf4) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f32c0e9b19a in __pthread_cond_wait_common (abstime=0x7f328bffed10, mutex=0x7f328c008ba0, cond=0x7f328c008bc8) at pthread_cond_wait.c:533 #2 0x7f32c0e9b19a in __pthread_cond_timedwait (cond=0x7f328c008bc8, mutex=0x7f328c008ba0, abstime=0x7f328bffed10) at pthread_cond_wait.c:667 #3 0x7f32c210232c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f32c20fa192 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f32c2101c97 in
[kdeconnect] [Bug 401384] New: KDE Connect plugin unable to utilize alternate messaging (SMS) apps
https://bugs.kde.org/show_bug.cgi?id=401384 Bug ID: 401384 Summary: KDE Connect plugin unable to utilize alternate messaging (SMS) apps Product: kdeconnect Version: 1.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: fred_we...@charter.net Target Milestone: --- SUMMARY KDE Connect plugin unable to utilize alternate messaging (SMS) apps STEPS TO REPRODUCE 1. Install alternate SMS apps (e.g Signa) and set as phone default. 2. Restart phone and verify alternate SMS/MMS operation. 3. Receive notification and reply to SMS messages from KDE Connect desktop client. OBSERVED RESULT The (disabled) phone default messaging app is still used to send reply. EXPECTED RESULT Configured messaging app (e.g. Signal) should send reply message. SOFTWARE/OS VERSIONS Windows: N/A MacOS: N/A Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401055] Transfer is reported as successful when Dolphin crashes
https://bugs.kde.org/show_bug.cgi?id=401055 --- Comment #7 from wg9rffujwz8y2...@airmail.cc --- Created attachment 116493 --> https://bugs.kde.org/attachment.cgi?id=116493=edit New log (veracrypt HDD) > Plasma Wayland session > What about the backtrace from Dr Konqi? Do you get one? Nope. Dolphin starts fading and crashes. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 401383] New: Elisa crash after deleting Music forlder from library.
https://bugs.kde.org/show_bug.cgi?id=401383 Bug ID: 401383 Summary: Elisa crash after deleting Music forlder from library. Product: elisa Version: 0.3.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: eridanired...@yahoo.com.mx Target Milestone: --- Application: elisa (0.3.0) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.15.0-39-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: 1. Set Music forlder for Elisa 2. Wait for the library to update 3. Added Pictures folder too 4. Deleted Music folder from the list as I wanted a way to purge the database 5. Nothing was purged so I scrolled down to see if maybe the bottom items where being deleted. 6. Couldn't scroll too much as Elisa crashed. The crash can be reproduced every time. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fca9d9b6800 (LWP 16528))] Thread 12 (Thread 0x7f8a2bfff700 (LWP 16764)): #0 0x7fca9a4420b4 in __GI___libc_read (fd=59, buf=0x7f8a2bffeb70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fca940e8cd0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fca940a4027 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fca940a44e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fca940a464c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fca9ad8104b in QEventDispatcherGlib::processEvents (this=0x7f8a2b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fca9ad2530a in QEventLoop::exec (this=this@entry=0x7f8a2bffed80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x7fca9ab50bba in QThread::exec (this=this@entry=0x556dbdc72670) at thread/qthread.cpp:525 #8 0x7fca9c6f14f5 in QQmlThreadPrivate::run (this=0x556dbdc72670) at qml/ftw/qqmlthread.cpp:148 #9 0x7fca9ab5badb in QThreadPrivate::start (arg=0x556dbdc72670) at thread/qthread_unix.cpp:367 #10 0x7fca963906db in start_thread (arg=0x7f8a2bfff700) at pthread_create.c:463 #11 0x7fca9a45388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f8a3141c700 (LWP 16634)): #0 0x7fca96396ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f8a3141bc30, expected=0, futex_word=0x556dbc25bc80) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f8a3141bd00, mutex=0x556dbc25bc30, cond=0x556dbc25bc58) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x556dbc25bc58, mutex=0x556dbc25bc30, abstime=0x7f8a3141bd00) at pthread_cond_wait.c:667 #3 0x7fca9ab5c880 in QWaitConditionPrivate::wait_relative (time=3, this=0x556dbc25bc30) at thread/qwaitcondition_unix.cpp:133 #4 QWaitConditionPrivate::wait (time=3, this=0x556dbc25bc30) at thread/qwaitcondition_unix.cpp:141 #5 QWaitCondition::wait (this=this@entry=0x7fca7801be60, mutex=mutex@entry=0x556dbbdbf080, time=3) at thread/qwaitcondition_unix.cpp:215 #6 0x7fca9ab5328d in QThreadPoolThread::run (this=0x7fca7801be50) at thread/qthreadpool.cpp:146 #7 0x7fca9ab5badb in QThreadPrivate::start (arg=0x7fca7801be50) at thread/qthread_unix.cpp:367 #8 0x7fca963906db in start_thread (arg=0x7f8a3141c700) at pthread_create.c:463 #9 0x7fca9a45388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fca41ecb700 (LWP 16633)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x40c96400) at /usr/include/c++/7/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x40c96400) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #9 QtPrivate::RefCount::ref (this=0x40c96400) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #10 QString::QString (other=..., this=) at ../../include/QtCore/../../src/corelib/tools/qstring.h:953 #11 QFontEngineMulti::fallbackFamilyAt (at=, this=0x7fca38154cc0) at ../../include/QtGui/5.11.2/QtGui/private/../../../../../src/gui/text/qfontengine_p.h:484 #12 QFontEngineMulti::loadEngine (this=0x7fca38154cc0, at=) at text/qfontengine.cpp:1845 #13 0x7fca9b61290d in QFontEngineMulti::ensureEngineAt (this=this@entry=0x7fca38154cc0, at=at@entry=207) at text/qfontengine.cpp:1832 #14 0x7fca9b6457f2 in QTextLine::glyphRuns (this=this@entry=0x7fca41ec85c0, from=from@entry=0, length=) at text/qtextlayout.cpp:2355 #15
[elisa] [Bug 401383] Elisa crash after deleting Music forlder from library.
https://bugs.kde.org/show_bug.cgi?id=401383 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401370] Discover crashes when refreshing/pulling down multiple times 'Checking for updates' page
https://bugs.kde.org/show_bug.cgi?id=401370 Aleix Pol changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Aleix Pol --- Can you please provide a backtrace? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400229] Flat and Adaptive acceleration profiles both do the same thing
https://bugs.kde.org/show_bug.cgi?id=400229 Nate Graham changed: What|Removed |Added Summary|mouse sensitivity / pointer |Flat and Adaptive |speed is missing in the |acceleration profiles both |settings|do the same thing Severity|wishlist|major -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400229] mouse sensitivity / pointer speed is missing in the settings
https://bugs.kde.org/show_bug.cgi?id=400229 Damian Höster changed: What|Removed |Added Summary|mouse sensitivity / pointer |mouse sensitivity / pointer |speed missing in the|speed is missing in the |settings|settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400229] mouse sensitivity / pointer speed missing in the settings
https://bugs.kde.org/show_bug.cgi?id=400229 Damian Höster changed: What|Removed |Added Summary|mouse sensitivity still |mouse sensitivity / pointer |missing in the settings |speed missing in the ||settings -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401382] New: String "Plus tôt en" rendered as "Plu55 CESTôCEST"
https://bugs.kde.org/show_bug.cgi?id=401382 Bug ID: 401382 Summary: String "Plus tôt en" rendered as "Plu55 CESTôCEST" Product: dolphin Version: 17.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: robertvandeney...@hotmail.com Target Milestone: --- Created attachment 116492 --> https://bugs.kde.org/attachment.cgi?id=116492=edit String "Plus tôt" creates a display problem SUMMARY Encoding problem on string "Plus tôt en" STEPS TO REPRODUCE 1. French locale 2. Affichage > Afficher par groupes 3. Terminal `touch -d 10 months ago` to create old file OBSERVED RESULT "Plu55 CESTôCEST" EXPECTED RESULT "Plus tôt" ADDITIONAL INFORMATION I think it is related to some parsing on a datetime containing time zone, because I'm in CEST time zone -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400229] mouse sensitivity still missing in the settings
https://bugs.kde.org/show_bug.cgi?id=400229 --- Comment #10 from Damian Höster --- No, I can't make out a real difference either. I wonder to what the acceleration could adapt to in adaptive mode. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395351] Touchpad settings are disabled in Wayland
https://bugs.kde.org/show_bug.cgi?id=395351
tones...@hotmail.com changed:
What|Removed |Added
CC||tones...@hotmail.com
--- Comment #21 from tones...@hotmail.com ---
I'm seeing this issue with systemsettings version 5.14.3. When I try to bring
up the touchpad settings I get the following output:
kcm_touchpad: Using KWin+Wayland backend
kcm_touchpad: Devices list received successfully from KWin.
kcm_touchpad: Touchpad found: "SynPS/2 Synaptics TouchPad" ("event14")
qrc:/libinput/main.qml:27:1: "components": no such directory
QObject::connect: Cannot connect (null)::changeSignal() to
TouchpadConfigLibInput::onChange()
This seems to imply a qml issue. line 27 of
kcms/touchpad/src/kcm/libinput/main.qml is a comment, however, when looking at
kcms/mouse/kcm/libinput/main.qml line 27 attempts to import "components". It
looks like it's processing the wrong qml file.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 376359] Sort by Image Quality (assign quality tags) ignores many images
https://bugs.kde.org/show_bug.cgi?id=376359 --- Comment #9 from bugskdeorg.20.dimon3...@spamgourmet.com --- (In reply to bugskdeorg.20.dimon3000 from comment #8) Forgot to mention. I am running digikam-6.0.0-beta3-20181124T130027 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376359] Sort by Image Quality (assign quality tags) ignores many images
https://bugs.kde.org/show_bug.cgi?id=376359 --- Comment #8 from bugskdeorg.20.dimon3...@spamgourmet.com --- Hello. I found an interesting behaviour. I added some new albums to the collection. Then started categorizing the images. The algorithm seems to have scanned all the new albums, but the results were applied to a single image! During the maintenance process, the quality label on the first image of the last album was changing all the time. This might be the cause. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #87 from timo...@zoho.com --- "Bus error", thats a new one: > digikam.general: Removing old entries () > digikam.general: Check for finish: 51 packages, 0 infos to filter, > hasFinished() false > digikam.general: Check for finish: 51 packages, 0 infos to filter, > hasFinished() false > digikam.facesengine: detectMultiScale gave () > digikam.general: Found 0 faces in "2_5309997771762172030.png" QSize(1236, > 781) QSize(1236, 781) > digikam.general: Removing old entries () > digikam.facesengine: detectMultiScale: image size 475 800 searchIncrement > 1.1 grouping 3 flags 1 min size 26 26 > > digikam.general: Check for finish: 51 packages, 0 infos to filter, > hasFinished() false > > Thread 29 "Thread (pooled)" received signal SIGBUS, Bus error. > [Switching to Thread 0x7fff3effd700 (LWP 29373)] > QMapData::createNode (left=false, parent=0x0, v=..., > k=..., this=0x7fff080024b0) > at > /nix/store/yd5wgc2yaz8biynyjxsh743xyh7bnr77-qtbase-5.11.1-dev/include/QtCore/qmap.h:228 > 228 new (>key) Key(k); > (gdb) > (gdb) bt > #0 QMapData::createNode (left=false, parent=0x0, v=..., > k=..., this=0x7fff080024b0) > at > /nix/store/yd5wgc2yaz8biynyjxsh743xyh7bnr77-qtbase-5.11.1-dev/include/QtCore/qmap.h:228 > #1 QMapNode::copy (this=0x7243656d69542e32, > d=d@entry=0x7fff080024b0) > at > /nix/store/yd5wgc2yaz8biynyjxsh743xyh7bnr77-qtbase-5.11.1-dev/include/QtCore/qmap.h:258 > #2 0x76248462 in QMap::detach_helper > (this=0x3f18a18) at > /nix/store/yd5wgc2yaz8biynyjxsh743xyh7bnr77-qtbase-5.11.1-dev/include/QtCore/qmap.h:1006 > #3 QMap::detach (this=0x3f18a18) at > /nix/store/yd5wgc2yaz8biynyjxsh743xyh7bnr77-qtbase-5.11.1-dev/include/QtCore/qmap.h:364 > #4 QMap::insert (this=0x3f18a18, akey=..., avalue=...) at > /nix/store/yd5wgc2yaz8biynyjxsh743xyh7bnr77-qtbase-5.11.1-dev/include/QtCore/qmap.h:704 > #5 0x76256f91 in Digikam::DImgLoader::uniqueHashV2 (filePath=..., > img=img@entry=0x4b97c48) at > /home/timo/tmp/source/core/libs/dimg/loaders/dimgloader.cpp:364 > #6 0x76257277 in Digikam::DImgLoader::createHistoryImageId > (filePath=..., image=..., metadata=...) > at /home/timo/tmp/source/core/libs/dimg/loaders/dimgloader.cpp:276 > #7 0x76257763 in Digikam::DImgLoader::readMetadata > (this=0x7fff3effc8d0, filePath=...) at > /home/timo/tmp/source/core/libs/dimg/loaders/dimgloader.cpp:224 > #8 0x7625f251 in Digikam::JPEGLoader::load > (this=this@entry=0x7fff3effc8d0, filePath=..., > observer=observer@entry=0x4b97a60) > at /home/timo/tmp/source/core/libs/dimg/loaders/jpegloader.cpp:92 > #9 0x763b3810 in Digikam::DImg::load (this=this@entry=0x4b97c48, > filePath=..., loadFlagsInt=loadFlagsInt@entry=63, > observer=observer@entry=0x4b97a60, > rawDecodingSettings=...) at > /home/timo/tmp/source/core/libs/dimg/dimg.cpp:429 > #10 0x763b3e10 in Digikam::DImg::load (this=this@entry=0x4b97c48, > filePath=..., observer=observer@entry=0x4b97a60, rawDecodingSettings=...) > at /home/timo/tmp/source/core/libs/dimg/dimg.cpp:373 > #11 0x76468736 in Digikam::PreviewLoadingTask::execute > (this=0x4b97a50) at > /home/timo/tmp/source/core/libs/threadimageio/preview/previewtask.cpp:292 > #12 0x7647fd3e in Digikam::LoadSaveThread::run (this=0x39aa620) at > /home/timo/tmp/source/core/libs/threadimageio/fileio/loadsavethread.cpp:133 > #13 0x764a213e in Digikam::DynamicThread::Private::run > (this=0x5971220) at > /home/timo/tmp/source/core/libs/threads/dynamicthread.cpp:183 > #14 0x7fffe958e602 in ?? () from > /nix/store/r6n4b9crppc0rmrr2z46xkqa87agydqy-qtbase-5.11.1/lib/libQt5Core.so.5 > #15 0x7fffe959712b in ?? () from > /nix/store/r6n4b9crppc0rmrr2z46xkqa87agydqy-qtbase-5.11.1/lib/libQt5Core.so.5 > #16 0x751fa5a7 in start_thread () from > /nix/store/g2yk54hifqlsjiha3szr4q3ccmdzyrdv-glibc-2.27/lib/libpthread.so.0 > #17 0x7fffe6a6922f in clone () from > /nix/store/g2yk54hifqlsjiha3szr4q3ccmdzyrdv-glibc-2.27/lib/libc.so.6 > (gdb) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399975] LyX does not work well with global menu
https://bugs.kde.org/show_bug.cgi?id=399975 --- Comment #3 from Cor Blom --- Thanks for fixing this. Can the fix also be applied to the Active Window Control applet? It has the same code. Maybe this is not the right place to ask, but I do not know how else to do this. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401380] Wheel doesn't work as expected since last update
https://bugs.kde.org/show_bug.cgi?id=401380 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/694e25ef6bc260e438d |te-dock/45a582d36b111b02ac2 |beeb71504e25600197170 |a6af5e79466389a1fad10 --- Comment #2 from Michail Vourlakos --- Git commit 45a582d36b111b02ac2a6af5e79466389a1fad10 by Michail Vourlakos. Committed on 24/11/2018 at 22:54. Pushed by mvourlakos into branch 'v0.8'. restore mouse wheel actions for tasks FIXED-IN: 0.8.4 M +6-22 plasmoid/package/contents/ui/task/TaskWindows.qml https://commits.kde.org/latte-dock/45a582d36b111b02ac2a6af5e79466389a1fad10 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401380] Wheel doesn't work as expected since last update
https://bugs.kde.org/show_bug.cgi?id=401380 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/lat ||te-dock/694e25ef6bc260e438d ||beeb71504e25600197170 Version Fixed In||0.8.4 Status|REPORTED|RESOLVED --- Comment #1 from Michail Vourlakos --- Git commit 694e25ef6bc260e438dbeeb71504e25600197170 by Michail Vourlakos. Committed on 24/11/2018 at 22:52. Pushed by mvourlakos into branch 'master'. restore mouse wheel actions for tasks FIXED-IN: 0.8.4 M +6-22 plasmoid/package/contents/ui/task/TaskWindows.qml https://commits.kde.org/latte-dock/694e25ef6bc260e438dbeeb71504e25600197170 -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 401381] New: Apper crashes after any update
https://bugs.kde.org/show_bug.cgi?id=401381 Bug ID: 401381 Summary: Apper crashes after any update Product: apper Version: 1.0.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: jtfjd...@hotmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Start apper and select "Updates" 2. Have something selected to update, but not all packages shown updatable 3. Press the update button OBSERVED RESULT The packages are downloaded and updates done, and after that apper shows the circle for waiting and then crashes. EXPECTED RESULT Return to the list of remaining updates instead of crashing SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Fedora 29 (or 28) (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I first discovered this when I had upgraded my system from Fedora 27 to Fedora 28 in May, and it still persist after all the package updates during Fedora 28 and upgrading to Fedora 29. If I start apper from Konsole, it shows several rows of "kf5.kwidgetsaddons: Invalid pixmap specified." during the process, and finally KCrash: Application 'apper' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit I reported this to Fedora bugzilla ( https://bugzilla.redhat.com/show_bug.cgi?id=1615818 ) in August, and when I reported that it still happens after upgrading to F29, they replied that I should report it here. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401380] New: Wheel doesn't work as expected since last update
https://bugs.kde.org/show_bug.cgi?id=401380 Bug ID: 401380 Summary: Wheel doesn't work as expected since last update Product: latte-dock Version: 0.8.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: artem.anuf...@live.de Target Milestone: --- It's no more possible to switch between open apps by using mouse wheel. If I open an app which is docked on my dockpanel, so it shows the animation on a different icon. TO REPRODUCE: 1. open more then one window of same app (dolphin as example) 2. use mouse wheel on the icon -> EXPECT: switch between open windows -> BUG: it doesn't -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Other program with the same error message: https://pixinsight.com/forum/index.php?topic=12871.0 https://github.com/Ultimaker/Cura/issues/4220#issuecomment-435629790 Maik -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 176977] konqueror locks up with some standard compliant SVG 1.0/1.1 graphics
https://bugs.kde.org/show_bug.cgi?id=176977 --- Comment #4 from Dimitar Pashov --- Hi Andrew, it is trivial to test wether the issue still exists. Simply open the attachment in konqueror and in other programs able to render svg, and kompare. You will see that while konqueror now (v5.0.97, kdef v5.52.0, qt v5.11.2) does show the picture without locking up, it is different from what firefox and chromium show. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 401379] New: kdeinit5 crash when disconnecting device
https://bugs.kde.org/show_bug.cgi?id=401379 Bug ID: 401379 Summary: kdeinit5 crash when disconnecting device Product: frameworks-kinit Version: 5.52.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: ethou...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 116491 --> https://bugs.kde.org/attachment.cgi?id=116491=edit stackdump created by kcrash SUMMARY STEPS TO REPRODUCE 1. Plug in a phone through USB. 2. Observe some weird problems leading to breaking the connection 3. Get a crash from kdeinit5 ADDITIONAL INFORMATION Attached crash dump. Other bugs with similar description seem unrelated. This looks like an object destroyed before release or not created when expected. This is crash dump created by kcrash, although this tool weirdly did not allow me to submit a bug directly from there. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update
https://bugs.kde.org/show_bug.cgi?id=398538 Giuseppe Margarita changed: What|Removed |Added Keywords||reproducible -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update
https://bugs.kde.org/show_bug.cgi?id=398538 --- Comment #6 from Giuseppe Margarita --- STEPS TO REPRODUCE 1. You have a pulseaudio sink, let's call it "Stereo Internal Audio", linked to your sound card and it's the default after a fresh install. 2. Make a new pulseaudio sink, i.e. using PulseEffects, and let's make it the default sink. 3. Change the volume through keyboard key and PulseEffects default sink is affected correctly. 4. Let's start a song or a video file and you make sure that the default PulseEffects sink is used by the application. 5. Change the volume and you will see that PulseEffetcs sink IS NOT affected by plasma-pa. Volume is changed on the sound card sink: Stereo Internal Audio. You can also notice that nothing is changed in pulseaudio configuration: PulseEffects is still the default sink. 6. Stop the reproduction, close the mediaplayer application and change the volume again. PulseEffects is affected. OBSERVED RESULT plasma-pa does not respect the control on the default sink when an audio stream is reproduced. EXPECTED RESULT plasma-pa should always change the volume on the default sink, or at least it should let you choose the preferred sink to control even if it's not the default in the pulseaudio config, just like it's done in kmix. ADDITIONAL INFORMATION kmix is another volume manager and it lets you choose one sink to control and volume control always affects that sink even if it's not the default sink. While the behavior in plasma-pa is clearly a bug because considering that: - It does not let you choose a preferred sink to control; - It lets you switch the default pulseaudio sink changing the pulseaudio configuration and the sink to be used by all applications When you set a default sink different from the one associated to the sound card and reproduce something, it won't control the volume on default sink. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 401154] gwenview should not change image colors if system-wide color management is enabled
https://bugs.kde.org/show_bug.cgi?id=401154 --- Comment #8 from Misha Aizatulin --- Yeah, I agree it is conceptually incorrect. > Is there some programmatic way for Gwenview to check and see whether a color > profile is already in use? My guess is as good as yours I'm afraid. Try asking oyranos devs perhaps? One thing that is still puzzling is that if I set Lab.icc (the one with mad colours) to be the system profile, gwenview doesn't seem to apply it again in full. You can see it if you change Lab.icc back to sRGB - the image in gwenview remains a bit brighter, but not mad. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 401378] New: KRunner crashes right after first letter is typed
https://bugs.kde.org/show_bug.cgi?id=401378 Bug ID: 401378 Summary: KRunner crashes right after first letter is typed Product: krunner Version: 5.14.1 Platform: Slackware Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: mail.aerma...@gmail.com Target Milestone: --- Application: krunner (5.14.1) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.19.2 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: - What I was doing when the application crashed: Just typing a text. But under another user krunner works fine. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f15f75177c0 (LWP 9691))] Thread 5 (Thread 0x7f15e2126700 (LWP 9695)): #0 0x7f15fbc0a2a3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f15fce1b55b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f15fe8c4359 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f15fe8c458a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f15fce1ae9c in () at /usr/lib64/libQt5Core.so.5 #5 0x7f15fbc04107 in start_thread () at /lib64/libpthread.so.0 #6 0x7f15fc961b0f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f15ee3d6700 (LWP 9694)): #0 0x7f15fc950c54 in read () at /lib64/libc.so.6 #1 0x7f15f94b46a0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f15f947182f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f15f9471cc8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f15f9471e2c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f15fd00e2fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f15fcfbe30b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f15fce118d6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f15fe5c9455 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f15fce1ae9c in () at /usr/lib64/libQt5Core.so.5 #10 0x7f15fbc04107 in start_thread () at /lib64/libpthread.so.0 #11 0x7f15fc961b0f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f15f5d61700 (LWP 9693)): #0 0x7f15fc950c54 in read () at /lib64/libc.so.6 #1 0x7f15f94b46a0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f15f947182f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f15f9471cc8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f15f9471e2c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f15fd00e2fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f15fcfbe30b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f15fce118d6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f15fd82c505 in () at /usr/lib64/libQt5DBus.so.5 #9 0x7f15fce1ae9c in () at /usr/lib64/libQt5Core.so.5 #10 0x7f15fbc04107 in start_thread () at /lib64/libpthread.so.0 #11 0x7f15fc961b0f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f15f707e700 (LWP 9692)): #0 0x7f15fc955329 in poll () at /lib64/libc.so.6 #1 0x7f15fc59ed17 in () at /usr/lib64/libxcb.so.1 #2 0x7f15fc5a080a in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f15f73e3f09 in () at /usr/lib64/qt5/plugins/platforms/../../../libQt5XcbQpa.so.5 #4 0x7f15fce1ae9c in () at /usr/lib64/libQt5Core.so.5 #5 0x7f15fbc04107 in start_thread () at /lib64/libpthread.so.0 #6 0x7f15fc961b0f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f15f75177c0 (LWP 9691)): [KCrash Handler] #6 0xc7b0 in () #7 0x7f15e00b7af2 in () at /usr/lib64/libgobject-2.0.so.0 #8 0x7f15e0956920 in () at /usr/lib64/qt5/plugins/plasma_runner_marble.so #9 0x001c in () #10 0x0001 in () #11 0x7f15e008801c in _init () at /usr/lib64/libgobject-2.0.so.0 #12 0x7f15e0957100 in () at /usr/lib64/qt5/plugins/plasma_runner_marble.so #13 0x7f15fee408dc in _dl_init () at /lib64/ld-linux-x86-64.so.2 #14 0x7f15fee44cf3 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #15 0x7f15fc9a47cc in _dl_catch_exception () at /lib64/libc.so.6 #16 0x7f15fee44316 in _dl_open () at /lib64/ld-linux-x86-64.so.2 #17 0x7f15f95442c6 in dlopen_doit () at /lib64/libdl.so.2 #18 0x7f15fc9a47cc in _dl_catch_exception () at /lib64/libc.so.6 #19 0x7f15fc9a483f in _dl_catch_error () at /lib64/libc.so.6 #20 0x7f15f9544985 in _dlerror_run () at /lib64/libdl.so.2 #21 0x7f15f9544361 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2 #22 0x7f15fcfbc14c in () at /usr/lib64/libQt5Core.so.5 #23
[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update
https://bugs.kde.org/show_bug.cgi?id=398538 --- Comment #5 from Nate Graham --- *** Bug 400789 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 400789] plasma-pa does not change the volume on the default pulseaudio sink when audio is reproduced
https://bugs.kde.org/show_bug.cgi?id=400789 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 398538 *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386510] Show help of the active plugins in krunner
https://bugs.kde.org/show_bug.cgi?id=386510 --- Comment #9 from Nate Graham --- > For example, what command do you have to use to do a google search? I agree, this is not at all obvious. Kai, please feel free to continue your work! I'm sorry that you didn't get any feedback from VDG before, but the group is much more active now, as you can see. :) We'll happily look at your work if you can dredge it up again. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 401154] gwenview should not change image colors if system-wide color management is enabled
https://bugs.kde.org/show_bug.cgi?id=401154 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Nate Graham --- Thanks for the patch! It might be a good starting point. However... > I actually like the double-profile behaviour in about 10% of cases > (when the images are really dark) This seems conceptually incorrect, even if the result looks good. Is there some programmatic way for Gwenview to check and see whether a color profile is already in use? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 401174] Flickables should be pixelAligned by default
https://bugs.kde.org/show_bug.cgi?id=401174 Nate Graham changed: What|Removed |Added Keywords||usability Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393202] Clipped text in sidebar view with certain non-standard font sizes
https://bugs.kde.org/show_bug.cgi?id=393202 Nate Graham changed: What|Removed |Added Component|components |sidebarview Version|5.46.0 |unspecified Product|frameworks-plasma |systemsettings --- Comment #24 from Nate Graham --- Here's a patch that fixes this: https://phabricator.kde.org/D17143 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400766] Export to Onedrive: not possible to export into subfolder
https://bugs.kde.org/show_bug.cgi?id=400766 --- Comment #9 from Nicofo --- Note: I have opened bug #401377 for this new problem as it is not related to the original one (Export to Onedrive: not possible to export into subfolder) which should be fixed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] New: Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 Bug ID: 401377 Summary: Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault) Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Export-OneDrive Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY (this is the continuation of bug #400766) When exporting to Onedrive or Dropbox (not tested with others, but maybe the same), digikam crashes (Segmentation Fault). STEPS TO REPRODUCE 1. Select files > Export to Onedrive (or Dropbox) RESULT Digikam crashes. With debug, this is what happens after clicking on Export > Onedrive: Digikam::AlbumFilterModel::setSearchTextSettings: new search text settings: "" : hasResult = true , validRows = 18 Digikam::ODTalker::readSettings: Linking... Auto configuration failed 140737221753088:error:0E079065:configuration file routines:DEF_LOAD_BIO:missing equal sign:conf_def.c:362:line 40 unknown: QMutex: destroying locked mutex [Thread 0x7ffef87f8700 (LWP 22788) exited] [Thread 0x7ffef7ff7700 (LWP 22789) exited] [Thread 0x7ffef77f6700 (LWP 22790) exited] [Thread 0x7ffef6ff5700 (LWP 22791) exited] [Thread 0x7fff62158700 (LWP 22756) exited] [Thread 0x7fffd3fff700 (LWP 22742) exited] [Thread 0x7fff61957700 (LWP 22757) exited] [Thread 0x7fff61156700 (LWP 22758) exited] [Thread 0x7fff60955700 (LWP 22759) exited] [Thread 0x7fff4bfff700 (LWP 22760) exited] [Thread 0x7fff4b7fe700 (LWP 22761) exited] [Thread 0x7fff4affd700 (LWP 22762) exited] [Thread 0x7fff4a7fc700 (LWP 22763) exited] [Thread 0x7fff49ffb700 (LWP 22764) exited] [Thread 0x7fff497fa700 (LWP 22765) exited] [Thread 0x7fff23fff700 (LWP 22767) exited] [Thread 0x7fff237fe700 (LWP 22768) exited] [Thread 0x7fff22ffd700 (LWP 22769) exited] [Thread 0x7fff48ff9700 (LWP 22766) exited] [Thread 0x7fff227fc700 (LWP 22770) exited] [Thread 0x7fff217fa700 (LWP 22772) exited] [Thread 0x7fff20ff9700 (LWP 22773) exited] [Thread 0x7fff21ffb700 (LWP 22771) exited] [Thread 0x7fff0bfff700 (LWP 22774) exited] [Thread 0x7fff0affd700 (LWP 22776) exited] [Thread 0x7fff0b7fe700 (LWP 22775) exited] [Thread 0x7fff09ffb700 (LWP 22778) exited] [Thread 0x7fff097fa700 (LWP 22779) exited] [Thread 0x7fff0a7fc700 (LWP 22777) exited] [Thread 0x7fff08ff9700 (LWP 22780) exited] [Thread 0x7ffefb7fe700 (LWP 22782) exited] [Thread 0x7ffefbfff700 (LWP 22781) exited] [Thread 0x7ffefa7fc700 (LWP 22784) exited] [Thread 0x7ffefaffd700 (LWP 22783) exited] [Thread 0x7ffef97fa700 (LWP 22786) exited] [Thread 0x7ffef9ffb700 (LWP 22785) exited] [Thread 0x7ffef8ff9700 (LWP 22787) exited] Thread 4 "Digikam::ScanCo" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe0fba700 (LWP 22734)] 0x0030a10a7024 in QReadWriteLock::tryLockForWrite(int) () from /tmp/.mount_digikaE5GnU5/usr/lib/libQt5Core.so.5 (gdb) (gdb) ADDITIONAL INFORMATION This seems linked to Appimage: the problem present on Fedora 29 with digikam 5.9, 6.0 beta 1, 2 and 3 with Appimage version. No problem with RPM version (5.9). Note that there was NO such problem on Fedora 28 and appimage. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #86 from Maik Qualmann --- Git commit e2f5717e14f29b71832dd541faa27c64dedfd0c4 by Maik Qualmann. Committed on 24/11/2018 at 20:27. Pushed by mqualmann into branch 'master'. remove dynamic cast and try with Q_DECL_OVERRIDE M +11 -11 core/libs/threadimageio/fileio/loadsavetask.h M +2-4core/libs/threadimageio/preview/previewtask.cpp M +1-1core/libs/threadimageio/preview/previewtask.h https://commits.kde.org/digikam/e2f5717e14f29b71832dd541faa27c64dedfd0c4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393408] Support for extra image formats through FFMPEG codecs as HEIC, FITS, JPEG-LS [patch]
https://bugs.kde.org/show_bug.cgi?id=393408 --- Comment #17 from Nick Triantos --- (In reply to Maik Qualmann from comment #14) > The test image of Comment 11 can not be opened / processed by FFmpeg. > > Maik And just to re-confirm, I re-downloaded the image from my comment and it does open with Apple tools (such as Preview) on my Mac. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 401230] SMART attributes do not display visibly when opened
https://bugs.kde.org/show_bug.cgi?id=401230 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/par ||titionmanager/beed97ee8402e ||b6a09dec90d2d0555c27d82a903 Status|REPORTED|RESOLVED --- Comment #1 from Andrius Štikonas --- Git commit beed97ee8402eb6a09dec90d2d0555c27d82a903 by Andrius Štikonas, on behalf of Varun Patel. Committed on 24/11/2018 at 20:17. Pushed by stikonas into branch 'master'. Updated SMART widget GUI to better display SMART info. Repositioned information and resized window to clearly display information. Differential Revision: https://phabricator.kde.org/D17129 M +23 -30 src/gui/smartdialogwidgetbase.ui https://commits.kde.org/partitionmanager/beed97ee8402eb6a09dec90d2d0555c27d82a903 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400507] Add the possibility of cycling windows by repeating a shorcut combination
https://bugs.kde.org/show_bug.cgi?id=400507 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #8 from Nate Graham --- You just added it, by answering my question. :) Since the functionality you want is already provided by alt+`, you can just use that instead. If you prefer to use a different keyboard shortcut to access the functionality, you can change it, and then you will have exactly what you want. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393408] Support for extra image formats through FFMPEG codecs as HEIC, FITS, JPEG-LS [patch]
https://bugs.kde.org/show_bug.cgi?id=393408 --- Comment #16 from Nick Triantos --- One more, from a different source: https://cdn2.online-convert.com/example-file/raster%20image/heic/example.heic -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401376] New: Unnecessary confirmation for reloading
https://bugs.kde.org/show_bug.cgi?id=401376 Bug ID: 401376 Summary: Unnecessary confirmation for reloading Product: kate Version: 18.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: nicolas.fe...@gmx.de Target Milestone: --- SUMMARY When a file is changed externally and I do Reload (F5) I get a prompt asking me whether I want to reload the file or ignore the changes, which is unnecessary since my inention is to reload the file STEPS TO REPRODUCE 1. Externally modify an open file 2. Reload OBSERVED RESULT Dialog asking whether I want to reload/ignore changes appears EXPECTED RESULT File reloads immediately SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.52 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393408] Support for extra image formats through FFMPEG codecs as HEIC, FITS, JPEG-LS [patch]
https://bugs.kde.org/show_bug.cgi?id=393408 --- Comment #15 from Nick Triantos --- It looks like if you click on the "Single Image" overlay of the PNG it will fetch the HEIF image (for example, http://nokiatech.github.io/heif/content/images/cheers_1440x960.heic, http://nokiatech.github.io/heif/content/images/autumn_1440x960.heic, http://nokiatech.github.io/heif/content/images/crowd_1440x960.heic, http://nokiatech.github.io/heif/content/images/old_bridge_1440x960.heic, http://nokiatech.github.io/heif/content/images/spring_1440x960.heic, http://nokiatech.github.io/heif/content/images/summer_1440x960.heic) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #85 from timo...@zoho.com --- Didn't help :/ > digikam.dimg: > "/home/timo/Pictures/pictures/Pictures/Android/Whatsapp/IMG-20140322-WA0003.jpg" > : JPEG file identified > digikam.general: Check for finish: 51 packages, 0 infos to filter, > hasFinished() false > digikam.general: !! Wrong function called > !! > digikam.database: " ( ( (ImageTagProperties.tagid=? OR > ImageTagProperties.tagid IN (SELECT id FROM TagsTree WHERE pid=?)) AND > ImageTagProperties.property=? ) OR ( (ImageTagProperties.tagid=? OR > ImageTagProperties.tagid IN (SELECT id FROM TagsTree WHERE pid=?)) AND > ImageTagProperties.property=? ) OR ( (ImageTagProperties.tagid=? OR > ImageTagProperties.tagid IN (SELECT id FROM TagsTree WHERE pid=?)) AND > ImageTagProperties.property=? ) ) " > digikam.database: Search query: > "SELECT DISTINCT Images.id, Images.name, Images.album, > Albums.albumRoot,ImageInformation.rating, Images.category, > ImageInformation.format, ImageInformation.creationDate, > Images.modificationDate, Images.fileSize,ImageInformation.width, > ImageInformation.height,ImageTagProperties.value, > ImageTagProperties.property, ImageTagProperties.tagid FROM Images > INNER JOIN ImageTagProperties ON ImageTagProperties.imageid=Images.id > LEFT JOIN ImageInformation ON Images.id=ImageInformation.imageidINNER > JOIN Albums ON Albums.id=Images.album WHERE Images.status=1 AND ( > ( ( (ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id > FROM TagsTree WHERE pid=?)) AND ImageTagProperties.property=? ) OR ( > (ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id FROM > TagsTree WHERE pid=?)) AND ImageTagProperties.property=? ) OR ( > (ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id FROM > TagsTree WHERE pid=?)) AND ImageTagProperties.property=? ) ) );" > (QVariant(int, 275), QVariant(int, 275), QVariant(QString, > "autodetectedPerson"), QVariant(int, 275), QVariant(int, 275), > QVariant(QString, "autodetectedFace"), QVariant(int, 275), QVariant(int, > 275), QVariant(QString, "tagRegion")) > digikam.facesengine: detectMultiScale gave () > digikam.general: Found 0 faces in "IMG-20140304-WA.jpg" QSize(480, 854) > QSize(480, 854) > digikam.database: Search result: 4962 > digikam.general: Removing old entries () > digikam.facesengine: detectMultiScale: image size 800 600 searchIncrement > 1.1 grouping 3 flags 1 min size 26 26 > > Thread 24 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7fff589e4700 (LWP 1327)] > 0x7648c9b6 in Digikam::LoadingTask::progressInfo (this=0x3ec51b0, > img=, progress=0.10001) > at > /home/timo/tmp/source/core/libs/threadimageio/fileio/loadsavetask.cpp:67 > 67 if (m_thread && m_thread->querySendNotifyEvent()) > (gdb) bt > #0 0x7648c9b6 in Digikam::LoadingTask::progressInfo (this=0x3ec51b0, > img=, progress=0.10001) > at > /home/timo/tmp/source/core/libs/threadimageio/fileio/loadsavetask.cpp:67 > #1 0x7626046a in Digikam::JPEGLoader::load > (this=this@entry=0x7fff589e38d0, filePath=..., > observer=observer@entry=0x3ec51c0) > at /home/timo/tmp/source/core/libs/dimg/loaders/jpegloader.cpp:374 > #2 0x763b3810 in Digikam::DImg::load (this=this@entry=0x3ec53a8, > filePath=..., loadFlagsInt=loadFlagsInt@entry=63, > observer=observer@entry=0x3ec51c0, > rawDecodingSettings=...) at > /home/timo/tmp/source/core/libs/dimg/dimg.cpp:429 > #3 0x763b3e10 in Digikam::DImg::load (this=this@entry=0x3ec53a8, > filePath=..., observer=observer@entry=0x3ec51c0, rawDecodingSettings=...) > at /home/timo/tmp/source/core/libs/dimg/dimg.cpp:373 > #4 0x76468736 in Digikam::PreviewLoadingTask::execute > (this=0x3ec51b0) at > /home/timo/tmp/source/core/libs/threadimageio/preview/previewtask.cpp:293 > #5 0x7647fd3e in Digikam::LoadSaveThread::run (this=0x7fffbc00c400) > at /home/timo/tmp/source/core/libs/threadimageio/fileio/loadsavethread.cpp:133 > #6 0x764a213e in Digikam::DynamicThread::Private::run > (this=0x3f41490) at > /home/timo/tmp/source/core/libs/threads/dynamicthread.cpp:183 > #7 0x7fffe958e602 in ?? () from > /nix/store/r6n4b9crppc0rmrr2z46xkqa87agydqy-qtbase-5.11.1/lib/libQt5Core.so.5 > #8 0x7fffe959712b in ?? () from > /nix/store/r6n4b9crppc0rmrr2z46xkqa87agydqy-qtbase-5.11.1/lib/libQt5Core.so.5 > #9 0x751fa5a7 in start_thread () from > /nix/store/g2yk54hifqlsjiha3szr4q3ccmdzyrdv-glibc-2.27/lib/libpthread.so.0 > #10 0x7fffe6a6922f in clone () from > /nix/store/g2yk54hifqlsjiha3szr4q3ccmdzyrdv-glibc-2.27/lib/libc.so.6 > (gdb) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400229] mouse sensitivity still missing in the settings
https://bugs.kde.org/show_bug.cgi?id=400229 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- --- Comment #9 from Nate Graham --- Can you detect any difference at all between the "Flat" and "Adaptive" acceleration profiles? Sorry to sounds like such an idiot here, but I can't tell the difference myself and I'm not sure whether this is because they're actually identical, or I'm just not very sensitive to the difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395853] Global menu doesnt empty itself after window is minimized
https://bugs.kde.org/show_bug.cgi?id=395853 Nate Graham changed: What|Removed |Added Version Fixed In||5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 401170] Preview of text files is blurry with fractional display scaling
https://bugs.kde.org/show_bug.cgi?id=401170 Nate Graham changed: What|Removed |Added CC||k...@privat.broulik.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393408] Support for extra image formats through FFMPEG codecs as HEIC, FITS, JPEG-LS [patch]
https://bugs.kde.org/show_bug.cgi?id=393408 --- Comment #14 from Maik Qualmann --- The test image of Comment 11 can not be opened / processed by FFmpeg. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401374] Folder view widget does not scale elements properly when having to account for an obstacle
https://bugs.kde.org/show_bug.cgi?id=401374 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400507] Add the possibility of cycling windows by repeating a shorcut combination
https://bugs.kde.org/show_bug.cgi?id=400507 --- Comment #7 from Stu Kraji --- Sorry. I don't understand what info do I need to add? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401297] Using various functions of gnome-disks causes plasmashell to freeze/break
https://bugs.kde.org/show_bug.cgi?id=401297 --- Comment #4 from gunq...@gmail.com --- (In reply to Kai Uwe Broulik from comment #3) > Thanks, you forgot to type: thread apply all bt https://pastebin.com/raw/7xBEUEKj -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400507] Add the possibility of cycling windows by repeating a shorcut combination
https://bugs.kde.org/show_bug.cgi?id=400507 --- Comment #6 from Stu Kraji --- (In reply to Nate Graham from comment #4) > (In reply to Stu Kraji from comment #3) > > https://twitter.com/i/status/1057311612640677888 > > I'm confused. That video appears to show the use of a keyboard shortcut to > cycle between open windows of the current app, which is exactly what I > mentioned earlier that you can already do today with alt+`. What am I > missing? oh sorry. the functionality is exactly the one provided by alt+`. but we should be able to do it by pressing meta+n to go to the last window used of the app and by repeating this we should cycle the windows of that app. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 401375] New: "Reparse the project" from project settings was ignored project size
https://bugs.kde.org/show_bug.cgi?id=401375 Bug ID: 401375 Summary: "Reparse the project" from project settings was ignored project size Product: kdevelop Version: 5.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: sr-tr...@yandex.ru Target Milestone: --- If the "Reparse the project" option is activated in the project settings, after changing the settings, the background analyzer ignores the size of the project and runs a detailed analysis, which takes a very long time STEPS TO REPRODUCE 1. Open Project settings 2. Go to language support 3. Change any params 4. Apply changes OBSERVED RESULT Detail parsing project EXPECTED RESULT Fast parsing project SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArhLinux KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 401375] "Reparse the project" from project settings was ignored project size
https://bugs.kde.org/show_bug.cgi?id=401375 sr-tr...@yandex.ru changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386453] Middle click on breadcrumbs of inactive split view does not open folder in new tab
https://bugs.kde.org/show_bug.cgi?id=386453 Nate Graham changed: What|Removed |Added Version Fixed In||5.53 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386453] Middle click on breadcrumbs of inactive split view does not open folder in new tab
https://bugs.kde.org/show_bug.cgi?id=386453 Thomas Surrel changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kio ||/fc5a98db98a88ba57ed369ed04 ||cb3f0b18b5a3f6 Status|CONFIRMED |RESOLVED --- Comment #5 from Thomas Surrel --- Git commit fc5a98db98a88ba57ed369ed04cb3f0b18b5a3f6 by Thomas Surrel. Committed on 24/11/2018 at 19:40. Pushed by thsurrel into branch 'master'. [KUrlNavigator] Re-activate on mouse middle button click Summary: When using the mouse middle button to open a folder when the kurlnavigator was disabled, it was not re-activated. Test Plan: In Dolphin, open the split view and use the mouse middle button to open a folder in a new tab on the 'disabled' splitted view. Reviewers: #frameworks, elvisangelaccio, ngraham Reviewed By: elvisangelaccio, ngraham Subscribers: ngraham, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D17114 M +8-0src/filewidgets/kurlnavigator.cpp M +5-0src/filewidgets/kurlnavigator.h https://commits.kde.org/kio/fc5a98db98a88ba57ed369ed04cb3f0b18b5a3f6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401374] New: Folder view widget does not scale elements properly when having to account for an obstacle
https://bugs.kde.org/show_bug.cgi?id=401374 Bug ID: 401374 Summary: Folder view widget does not scale elements properly when having to account for an obstacle Product: plasmashell Version: 5.14.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: tyx...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY This is something I observed while testing: https://phabricator.kde.org/D16968#365437 The crux of the problem is that sometimes the folder view widget will not scale elements properly when it has to account for, say, a panel in its way. STEPS TO REPRODUCE (what works for me) 1. Align a sufficient number of icons so that you make sure they will horizontally or vertically intersect with a panel 2. Make a more drastic icon size change, e.g. from Large to Small Medium 3. Take notice of how the elements are not rendered properly OBSERVED RESULT Both the text and the icons are not rendered sharply: https://phabricator.kde.org/file/data/y6phbjgm7e4xv27af4b2/PHID-FILE-nm22uip53gci7zo7plnp/Screenshot_20181124_192928.png EXPECTED RESULT If you change the sorting mode you trigger the proper rendering: https://phabricator.kde.org/file/data/dcruq447f2n54xfqo6tn/PHID-FILE-qx4mkbznzvn75insmsv2/Screenshot_20181124_192953.png SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401372] Kwin crash when press alt+tab
https://bugs.kde.org/show_bug.cgi?id=401372 Martin Flöser changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393408] Support for extra image formats through FFMPEG codecs as HEIC, FITS, JPEG-LS [patch]
https://bugs.kde.org/show_bug.cgi?id=393408 --- Comment #13 from Maik Qualmann --- Ok, I know the page. But when I click on an image, a preview is displayed and that is a PNG image. How do I download a HEIC image there? Browser is here Chromium. Maik -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 401373] New: Disable text shape borders by default
https://bugs.kde.org/show_bug.cgi?id=401373 Bug ID: 401373 Summary: Disable text shape borders by default Product: calligrawords Version: 3.1.0 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: usability Assignee: calligra-words-bugs-n...@kde.org Reporter: matheus4...@hotmail.com Target Milestone: --- So the page gets a cleaner look, similar to MS Office and LibreOffice. -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 317637] curly brace only create an infinite loop
https://bugs.kde.org/show_bug.cgi?id=317637 --- Comment #3 from Marco Menardi --- I've tested again with versione 0.8.1 beta in debian sid, and all the wrong behaviours reported persist. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393408] Support for extra image formats through FFMPEG codecs as HEIC, FITS, JPEG-LS [patch]
https://bugs.kde.org/show_bug.cgi?id=393408 --- Comment #12 from Nick Triantos --- Thanks. Just realized my comment is only on the attachment. I found a bunch of example HEIF images here: http://nokiatech.github.io/heif/examples.html -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393408] Support for extra image formats through FFMPEG codecs as HEIC, FITS, JPEG-LS [patch]
https://bugs.kde.org/show_bug.cgi?id=393408 --- Comment #11 from Nick Triantos --- Created attachment 116490 --> https://bugs.kde.org/attachment.cgi?id=116490=edit Sample HEIC I've posted one sample pic that I took, and there are also a bunch of samples here: http://nokiatech.github.io/heif/examples.html. thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377483] Huge repainting periodicity. Or clock does not show me every second.
https://bugs.kde.org/show_bug.cgi?id=377483 --- Comment #8 from Ken Mankoff --- When I put the clock in an empty panel then it updates. I'm not surprised this is specific to my machine - seems like it would be mentioned more if it were a clean-KDE issue. If I figure out which applet is causing the clock update issue I'll post back here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401372] New: Kwin crash when press alt+tab
https://bugs.kde.org/show_bug.cgi?id=401372 Bug ID: 401372 Summary: Kwin crash when press alt+tab Product: kwin Version: 5.14.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: francescvc...@josoc.cat Target Milestone: --- Application: kwin_x11 (5.14.3) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.18.0-11-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: Pressing Alt+Tab when we are working with many applications The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x55ce8507c0a4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 [Current thread is 1 (Thread 0x7f4227320840 (LWP 18465))] Thread 6 (Thread 0x7f41ff7bf700 (LWP 18477)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f422fedafb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f422fedaf68, cond=0x7f422fedaf90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f422fedaf90, mutex=0x7f422fedaf68) at pthread_cond_wait.c:655 #3 0x7f422fde3e2a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f422fde3e49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f422f0ee164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f423193adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f4204ac4700 (LWP 18476)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7f4231842535 in __GI_abort () at abort.c:79 #8 0x7f423010a957 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7f4230110aa6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f4230110ae1 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f42302b1d03 in qTerminate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f42302b40c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f422f0ee164 in start_thread (arg=) at pthread_create.c:486 #14 0x7f423193adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f421227e700 (LWP 18475)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55ce84819638) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55ce848195e8, cond=0x55ce84819610) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55ce84819610, mutex=0x55ce848195e8) at pthread_cond_wait.c:655 #3 0x7f42128dc46b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f42128dc1d7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f422f0ee164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f423193adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f4225346700 (LWP 18471)): #0 0x7f423192e7d6 in __GI_ppoll (fds=0x7f421800eaf8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f42304ea141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f42304eb5b9 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f423049b16b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f42302ea0b6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f422e3f9545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7f42302f3c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f422f0ee164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f423193adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f42264f1700 (LWP 18469)): #0 0x7f423192e6d9 in __GI___poll (fds=0x7f42264f0c78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4230213917 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f423021553a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f42269d8159 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f42302f3c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f422f0ee164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f423193adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f4227320840 (LWP 18465)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55ce8507c0a4) at
[gwenview] [Bug 401371] New: Greyscale DNG files report wrong size in browse view
https://bugs.kde.org/show_bug.cgi?id=401371 Bug ID: 401371 Summary: Greyscale DNG files report wrong size in browse view Product: gwenview Version: 18.08.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: jtap...@gmail.com Target Milestone: --- SUMMARY When a directory contains a 16-bit greyscale DNG file (from VueScan), the dimensions displayed are twice the correct values. STEPS TO REPRODUCE 1. Open a directory containing 16-bit greyscale DNG files in browse mode OBSERVED RESULT The size displayed below the filename is twice the correct value. EXPECTED RESULT Display the correct value. SOFTWARE/OS VERSIONS See about section. ADDITIONAL INFORMATION Not sure about colour DNGs or 8-bit ones as I don't have any. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400506] Provide a Menubar
https://bugs.kde.org/show_bug.cgi?id=400506 Elia Devito changed: What|Removed |Added CC||eliadev...@yahoo.it -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 389002] All day event won't synchronize to google calendar
https://bugs.kde.org/show_bug.cgi?id=389002 --- Comment #8 from Philippe ROUBACH --- i forgot : kde app 18.08.3 -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 389002] All day event won't synchronize to google calendar
https://bugs.kde.org/show_bug.cgi?id=389002 --- Comment #7 from Philippe ROUBACH --- Linux: openSuse leap 15.0 Argon KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 same problem here -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401370] New: Discover crashes when refreshing/pulling down multiple times 'Checking for updates' page
https://bugs.kde.org/show_bug.cgi?id=401370 Bug ID: 401370 Summary: Discover crashes when refreshing/pulling down multiple times 'Checking for updates' page Product: Discover Version: 5.14.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updater Assignee: aleix...@kde.org Reporter: notux...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Launch Discover. 2. Select bottom left Checking for updates.../No Updates page. 3. Click mouse button and pull down this page or press 'Check for Updates' button in order to begin update process. 4. Without waiting for the current update process to finish - pull down the page again - Discover window becomes unresponsive. 5. Click on Discover window. OBSERVED RESULT Discover crashes EXPECTED RESULT Updates page cannot be pulled down upon update checking/process in progress SOFTWARE/OS VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.14.80 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.2 Kernel Version: 4.15.0-39-generic ADDITIONAL INFORMATION Reproduciblity: Very often -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #45 from Maik Qualmann --- OK thanks. I guessed it was Intel. You can also look into this bug 399923, it's basically the same bug report. Maik -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 401369] New: kpat crashes when grandfather is selected
https://bugs.kde.org/show_bug.cgi?id=401369 Bug ID: 401369 Summary: kpat crashes when grandfather is selected Product: kpat Version: 3.6 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: co...@kde.org Reporter: uliweh...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- Application: kpat (3.6) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.19.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: playing kpat, select new game, choose grandfather. application crashes. when i restart the app i can choose grandfather and it works fine. has been happening for weeks. Kpat is not super stable altogether anyway. seems like the solver is broken in some way. The crash can be reproduced every time. -- Backtrace: Application: KPatience (kpat), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f334c9f5940 (LWP 28224))] Thread 4 (Thread 0x7f3341c49700 (LWP 28229)): #0 0x7f334f9e64dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f33420f9f5b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f33420f9c87 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f334f9e0554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f33512d4ccf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f3343fff700 (LWP 28227)): #0 0x7ffe346b7af4 in clock_gettime () #1 0x7f33512e2876 in clock_gettime () from /lib64/libc.so.6 #2 0x7f3351d82401 in qt_clock_gettime (ts=0x7f3343ffe970, clock=1) at kernel/qelapsedtimer_unix.cpp:175 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7f3351d80c39 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f333c004cf0) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f3351d81235 in QTimerInfoList::timerWait (this=0x7f333c004cf0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f3351d8285e in timerSourcePrepareHelper (timeout=0x7f3343ffea54, src=) at kernel/qeventdispatcher_glib.cpp:161 #8 timerSourcePrepare (source=, timeout=0x7f3343ffea54) at kernel/qeventdispatcher_glib.cpp:165 #9 0x7f334eb23499 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #10 0x7f334eb23e7b in ?? () from /usr/lib64/libglib-2.0.so.0 #11 0x7f334eb2406c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #12 0x7f3351d82adb in QEventDispatcherGlib::processEvents (this=0x7f333c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #13 0x7f3351d2fadb in QEventLoop::exec (this=this@entry=0x7f3343ffec30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #14 0x7f3351b7ede6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #15 0x7f334fe73545 in ?? () from /usr/lib64/libQt5DBus.so.5 #16 0x7f3351b889b7 in QThreadPrivate::start (arg=0x7f334feedd60) at thread/qthread_unix.cpp:367 #17 0x7f334f9e0554 in start_thread () from /lib64/libpthread.so.0 #18 0x7f33512d4ccf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f3349d42700 (LWP 28226)): #0 0x7f33512ca2c9 in poll () from /lib64/libc.so.6 #1 0x7f334e0facc7 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f334e0fc8ea in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f334ad1d519 in QXcbEventReader::run (this=0x55d449091360) at qxcbconnection.h:409 #4 0x7f3351b889b7 in QThreadPrivate::start (arg=0x55d449091360) at thread/qthread_unix.cpp:367 #5 0x7f334f9e0554 in start_thread () from /lib64/libpthread.so.0 #6 0x7f33512d4ccf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f334c9f5940 (LWP 28224)): [KCrash Handler] #6 MemoryManager::new_from_block (this=0x55d44965c810, s=72) at /usr/src/debug/kpat-18.08.3-1.1.x86_64/patsolve/memory.cpp:165 #7 0x55d448446807 in Solver<22ul>::pack_position (this=this@entry=0x55d449be4a10) at /usr/include/c++/8/bits/unique_ptr.h:342 #8 0x55d448446cbe in Solver<22ul>::insert (this=this@entry=0x55d449be4a10, cluster=cluster@entry=0x7ffe34672f5c, d=0, node=node@entry=0x7ffe34672f60) at /usr/include/c++/8/bits/unique_ptr.h:342 #9 0x55d448446daa in Solver<22ul>::new_position (this=this@entry=0x55d449be4a10, parent=parent@entry=0x0, m=m@entry=0x7ffe34672fa0) at /usr/src/debug/kpat-18.08.3-1.1.x86_64/patsolve/patsolve.cpp:907 #10 0x55d44844e4b6 in Solver<22ul>::doit (this=0x55d449be4a10) at /usr/include/bits/string_fortified.h:71 #11 0x55d44844e547 in Solver<22ul>::patsolve (this=0x55d449be4a10, _max_positions=) at /usr/src/debug/kpat-18.08.3-1.1.x86_64/patsolve/patsolve.cpp:795 #12 0x55d44841d4df
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #44 from Mathieu --- Mark, Intel(R) Core(TM) i5 CPU M 480 @ 2.67GHz Thanks for all your work ! -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 401368] Top menu initially sluggish at the launch of any Jet Brains IDE, cascading menus don't work initially. Crashes observed.
https://bugs.kde.org/show_bug.cgi?id=401368 --- Comment #1 from leftcrane --- The sluggishness might have been a random glitch, but the failure to cascade on hover, inability to exit certain menus normally and crashes are reasonably consistent. This is 100% a topmenu bug, because LIM works. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #84 from timo...@zoho.com --- gcc 7.3.0. (The latest attempt is still compiling) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #43 from Maik Qualmann --- Mathieu, which CPU has your computer, Intel or AMD? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #83 from Maik Qualmann --- Hmm, the compiler does it right. It goes well thousands of times, it happens at runtime... I fantasize a bit, an Intel Spectra kernel patch problem...? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #82 from caulier.gil...@gmail.com --- timokau, Which compiler version do you use exactly ? GCC or Clang ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 351086] Feature to stretch clip for looping
https://bugs.kde.org/show_bug.cgi?id=351086 emohr changed: What|Removed |Added Flags||Brainstorm+ --- Comment #4 from emohr --- Looping a video would be a nice feature, i.e. for a logo like a spinning globe. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #81 from caulier.gil...@gmail.com --- Right. The Q_DECL_OVERRIDE can perhaps help here if it applied to SharedLoadingTask::progressInfo() virtual method declaration... But if yes, i don't understand why. The compiler must do the job properly as well... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 401368] New: Top menu initially sluggish at the launch of any Jet Brains IDE, cascading menus don't work initially. Crashes observed.
https://bugs.kde.org/show_bug.cgi?id=401368 Bug ID: 401368 Summary: Top menu initially sluggish at the launch of any Jet Brains IDE, cascading menus don't work initially. Crashes observed. Product: kded-appmenu Version: 5.14.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: top menubar Assignee: plasma-b...@kde.org Reporter: leftcr...@tutanota.com Target Milestone: --- The issue applies only to the horizontal menubar plasmoid, but not to LIM. Immediately after first launch, the user is unable cascade the top-level menu items by hovering over them. You have to click on each top-level individually to open it. Furthermore, sometimes the menus don't close (open "Help", then click anywhere outside the menubar but the Help menu stay open). I have also observed crashes plasmashell, panel and latte dock after using this. After about five minutes and a bit of switching back and forth between various windows, the top menu of JeBrains begins to work normally. It seems like the plasmoid (unlike LIM) is too hasty in constructing the menu and may be constructing it incompletely. This is probably related to the Libre Office bug, since the glitches follow the same pattern: Bug 401367 Operating System: Kubuntu 18.10 KDE Plasma Version: 5.14.3 Qt Version: 5.11.1 KDE Frameworks Version: 5.52.0 Kernel Version: 4.18.0-11-generic OS Type: 64-bit JetBrains. CLion 2018.3 Build #CL-183.4284.140, built on November 20, 2018 JRE: 1.8.0_152-release-1343-b15 amd64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Linux 4.18.0-11-generic -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 399840] Doesn't make sound in Kalarm
https://bugs.kde.org/show_bug.cgi?id=399840 David Jarvie changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from David Jarvie --- . -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 387654] Comment command should be smart enough to uncomment, too
https://bugs.kde.org/show_bug.cgi?id=387654 Nate Graham changed: What|Removed |Added Version Fixed In||19.04.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 387654] Comment command should be smart enough to uncomment, too
https://bugs.kde.org/show_bug.cgi?id=387654
Christoph Cullmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
Latest Commit||https://commits.kde.org/kte
||xteditor/c7095834d282b57e66
||c8256ef94f4e8c14032b3c
--- Comment #2 from Christoph Cullmann ---
Git commit c7095834d282b57e66c8256ef94f4e8c14032b3c by Christoph Cullmann, on
behalf of Silas Lenz.
Committed on 24/11/2018 at 16:37.
Pushed by cullmann into branch 'master'.
Expose "Toggle Comment" feature through tools menu and default shortcut
Summary:
Adds a menu item to toggle comments and adds CTRL + / as a shortcut. Also
removes "Comment"/"Uncomment" menu items (but keeps the shortcuts to avoid
breaking muscle memory).
{F6432040}
Test Plan: Test both old and new shortcuts and the new menu item.
Reviewers: #vdg, ngraham, #kate, #ktexteditor, cullmann
Reviewed By: #vdg, ngraham, #kate, #ktexteditor, cullmann
Subscribers: cullmann, ngraham, kwrite-devel, kde-frameworks-devel
Tags: #kate, #frameworks
Differential Revision: https://phabricator.kde.org/D17008
M +2-3src/data/katepart5ui.rc
M +1-0src/view/kateview.cpp
https://commits.kde.org/ktexteditor/c7095834d282b57e66c8256ef94f4e8c14032b3c
--
You are receiving this mail because:
You are watching all bug changes.
[kmahjongg] [Bug 401358] Strange name of layout for KMahjongg tiles
https://bugs.kde.org/show_bug.cgi?id=401358 staka...@eclipso.eu changed: What|Removed |Added CC||staka...@eclipso.eu --- Comment #2 from staka...@eclipso.eu --- typo whole meant to be hole. -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 401358] Strange name of layout for KMahjongg tiles
https://bugs.kde.org/show_bug.cgi?id=401358 --- Comment #1 from staka...@eclipso.eu --- Without wanting to offend, isn't this a bit "spurious" as a report? In Italian translation: Buco is a whole. For a lot of reasons that I am not going to discuss in detail, in Italian the association of a whole is round, with a very exception and that is also not a square. Now "inner circle" could have been referred to a cover of a pop group, or to a loose association a la "Rohrschach". And what is referred to as "pentagono" isn't a pentagon. And the galaxy is taken from "star gate's nanites universe?" Because my galaxies look different. So, for me personally the names are more "artistic" and do not appear to be branched to a real form. No? YMMV but that seem to me at least invalid. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #80 from Maik Qualmann --- The progressInfo() function is called from the image loaders as DImgLoaderObserver when loading image progress. We have the simple LoadingTask::progressInfo() overloaded by the SharedLoadingTask::progressInfo(). The PreviewLoadingTask is derived from the SharedLoadingTask. Therefore, progressInfo() should always be executed by the SharedLoadingTask. Maik -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 401290] Regression on import of Java classes with methods using varargs
https://bugs.kde.org/show_bug.cgi?id=401290 --- Comment #6 from Oliver Kellogg --- Okay, see https://phabricator.kde.org/D17108 -- You are receiving this mail because: You are watching all bug changes.
