[kde] [Bug 437935] New: Crash on show tooltip
https://bugs.kde.org/show_bug.cgi?id=437935 Bug ID: 437935 Summary: Crash on show tooltip Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bertil.bo...@gmail.com Target Milestone: --- Application: latte-dock (0.9.12) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.8.0-53-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: KDE neon User Edition 5.21 -- Information about the crash: - What I was doing when the application crashed: Hovered the mouse for tool tip - Unusual behavior I noticed: Just came out of sleep. Nvidia GPU seems problematic with sleep and hybernate. The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [New LWP 35187] [New LWP 35188] [New LWP 35193] [New LWP 35205] [New LWP 35210] [New LWP 35220] [New LWP 35221] [New LWP 35499] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x55e7900e4384) at ../sysdeps/nptl/futex-internal.h:183 [Current thread is 1 (Thread 0x7f393aedc8c0 (LWP 35182))] Thread 9 (Thread 0x7f392a352700 (LWP 35499)): [KCrash Handler] #4 QXcbConnection::glIntegration (this=0x0) at qxcbconnection.cpp:1065 #5 0x7f393a4bca27 in QXcbIntegration::createPlatformOpenGLContext (this=, context=0x7f3934011e90) at qxcbobject.h:53 #6 0x7f393f774f01 in QOpenGLContext::create (this=0x7f3934011e90) at ../../include/QtGui/5.15.2/QtGui/private/../../../../../src/gui/kernel/qguiapplication_p.h:110 #7 0x7f3940e5f988 in QSGRenderThread::sync (this=this@entry=0x55e790131600, inExpose=inExpose@entry=true, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:620 #8 0x7f3940e61a37 in QSGRenderThread::syncAndRender (this=0x55e790131600, grabImage=0x0) at scenegraph/qsgthreadedrenderloop.cpp:778 #9 0x7f3940e65c47 in QSGRenderThread::run (this=0x55e790131600) at scenegraph/qsgthreadedrenderloop.cpp:1043 #10 0x7f393effebec in QThreadPrivate::start (arg=0x55e790131600) at thread/qthread_unix.cpp:329 #11 0x7f393decc609 in start_thread (arg=) at pthread_create.c:477 #12 0x7f393eb31293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f38dfdff700 (LWP 35221)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e78f6225f4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e78f6225a0, cond=0x55e78f6225c8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55e78f6225c8, mutex=0x55e78f6225a0) at pthread_cond_wait.c:647 #3 0x7f393f004d5b in QWaitConditionPrivate::wait (deadline=..., this=0x55e78f6225a0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=this@entry=0x55e78eed5a78, mutex=mutex@entry=0x55e78eed5a70, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f3940e65814 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x55e78eed5a68) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x55e78eed59d0) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7f3940e65c89 in QSGRenderThread::run (this=0x55e78eed59d0) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7f393effebec in QThreadPrivate::start (arg=0x55e78eed59d0) at thread/qthread_unix.cpp:329 #9 0x7f393decc609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f393eb31293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f39052fb700 (LWP 35220)): #0 0x7f393eb24aff in __GI___poll (fds=0x7f38e0004240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f393d1cb36e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f393d1cb4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f393f23effb in QEventDispatcherGlib::processEvents (this=0x7f38eb60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f393f1e31eb in QEventLoop::exec (this=this@entry=0x7f39052facc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f393effda52 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f3940ae8fa9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f393effebec in QThreadPrivate::start (arg=0x55e78f679020) at thread/qthread_unix.cpp:329 #8 0x7f393decc609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f393eb31293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread
[kde] [Bug 437934] New: GTK_USE_PORTAL=1 doesn't work
https://bugs.kde.org/show_bug.cgi?id=437934 Bug ID: 437934 Summary: GTK_USE_PORTAL=1 doesn't work Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: toadfi...@tutanota.com Target Milestone: --- GTK applications use a different file dialog than the kde file dialog,but I don't like that,so I enabled GTK_USE_PORTAL=1,cause that should apply the kde file dialog for all applications. But that it doesn't work,if I put GTK_USE_PORTAL=1 in .profile and re login,then the GTK apps stile use the GTK file dialog. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437930] That it shows which api an application uses
https://bugs.kde.org/show_bug.cgi?id=437930 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from David Edmundson --- I can't envision a way to do this. Underneath they both make the same system calls to create buffers. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437267] Add ability to change capslock into a ctrl AND an esc simultaneously
https://bugs.kde.org/show_bug.cgi?id=437267 --- 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.
[lattedock] [Bug 436199] Some errors while adding widgets
https://bugs.kde.org/show_bug.cgi?id=436199 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 436129] Activity Panel Crash
https://bugs.kde.org/show_bug.cgi?id=436129 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 436193] Latte is crashed
https://bugs.kde.org/show_bug.cgi?id=436193 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 437173] smb://zach@tower.local/Scarlet/Media/Zerochan/somefile.etc smb://zach@tower.local/Scarlet/Media/Zerochan/somefile.etc
https://bugs.kde.org/show_bug.cgi?id=437173 --- 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 430864] Automatic scene split ignores last 15% of clip
https://bugs.kde.org/show_bug.cgi?id=430864 --- 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 437073] Audio Playback Muted
https://bugs.kde.org/show_bug.cgi?id=437073 --- 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 387867] Please bring back kdenlive_render.log
https://bugs.kde.org/show_bug.cgi?id=387867 --- Comment #4 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 387609] Icons, text and buttons are very small on 4k HiDPI monitors + non-KDE desktop environments
https://bugs.kde.org/show_bug.cgi?id=387609 --- Comment #12 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 393819] Application menu decoration does not work in libre office
https://bugs.kde.org/show_bug.cgi?id=393819 --- 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.
[skrooge] [Bug 437933] New: Confirm before dismissing changed operation
https://bugs.kde.org/show_bug.cgi?id=437933 Bug ID: 437933 Summary: Confirm before dismissing changed operation Product: skrooge Version: 2.24.6 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: pa...@web.de CC: steph...@mankowski.fr Target Milestone: --- SUMMARY If the user wants to create a new operation by using an existing operation as a start and forgets to click on add new operation and clicks somewhere else (another operation), Skrooge should warn the user. STEPS TO REPRODUCE 1. Click on an already existing operation as a start for creating a new operation 2. Modify the relevant entries 3. Click on another operation (without clicking on create new operation) OBSERVED RESULT All the inserted values are deleted. EXPECTED RESULT The system should ask the user whether the changed values should be dismissed, the modified operation should be changed or a new operation should be created. As this question might annoy some users, an option to (de)activate this feature might be useful. Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-5-amd64 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437932] Canvas Only Mode does not hide Titlebar or go fullscreen the first time, unless cycling Ctrl+Shift+F once
https://bugs.kde.org/show_bug.cgi?id=437932 Tyson Tan changed: What|Removed |Added Summary|Canvas Only Mode does not |Canvas Only Mode does not |hide Titlebar or go |hide Titlebar or go |fullscreen the first time, |fullscreen the first time, |unless pressing |unless cycling Ctrl+Shift+F |Ctrl+Shift+F once |once -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437932] New: Canvas Only Mode does not hide Titlebar or go fullscreen the first time, unless pressing Ctrl+Shift+F once
https://bugs.kde.org/show_bug.cgi?id=437932 Bug ID: 437932 Summary: Canvas Only Mode does not hide Titlebar or go fullscreen the first time, unless pressing Ctrl+Shift+F once Product: krita Version: 4.4.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- CONTEXT: Krita can switch to Canvas-Only mode by pressing the "Tab" key. There are options on Configure Krita -> Canvas-only settings that hides the Titlebar and goes fullscreen. EXPECTED: By default, every option on that page was checked, which means Krita should display only its canvas at fullscreen when the Tab key is pressed. REALITY: However, if a user presses Tab for the first time after they installed Krita, the Titlebar won't be hidden and Krita won't go fullscreen. It remains that way even after restarting Krita. WORKAROUND: Press Tab -> Ctrl+Shift+F x2. After doing that then switching back, Krita will now allow Titlebar to be hidden and go fullscreen at will, even after restarting it. SUSPECT: Maybe a default configuration file issue. TESTED: Krita 4.4.3 under ArchLinux (KDE Plasma) and Windows 10 (21H1). -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 437931] New: Latte dock crashs on boot
https://bugs.kde.org/show_bug.cgi?id=437931 Bug ID: 437931 Summary: Latte dock crashs on boot Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: arush@gmail.com Target Milestone: --- Application: latte-dock (0.9.91) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.7-160-tkg-bmq x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Garuda Linux -- Information about the crash: - What I was doing when the application crashed: I started my computer, logged in, and then, latte-dock crahed. This seems to happen almost everytime I log in. Note: I have this command as my latte-dock startup (in System Settings -> Startup and Shutdown -> Autostart): sleep 7 && /usr/bin/latte-dock The above is set by me, because I was experincing other issues with latte dock: https://forum.garudalinux.org/t/above-and-below-portions-of-screen-not-working-after-update/7704 The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7fa45e88f7c0 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7fa45e8c0a9c in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7fa45e8a737a in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7fa45e8acaf6 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7fa45e8ad505 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #9 0x7fa45e894582 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7fa45e9030a3 in QSGOpenGLLayer::grab() () at /usr/lib/libQt5Quick.so.5 #11 0x7fa45e9036de in QSGOpenGLLayer::updateTexture() () at /usr/lib/libQt5Quick.so.5 #12 0x7fa45ea72b17 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /usr/lib/libQt5Quick.so.5 #13 0x7fa45e894d2d in QSGRenderer::preprocess() () at /usr/lib/libQt5Quick.so.5 #14 0x7fa45e894549 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #15 0x7fa45e9030a3 in QSGOpenGLLayer::grab() () at /usr/lib/libQt5Quick.so.5 #16 0x7fa45e9036de in QSGOpenGLLayer::updateTexture() () at /usr/lib/libQt5Quick.so.5 #17 0x7fa45ea72b17 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /usr/lib/libQt5Quick.so.5 #18 0x7fa45e894d2d in QSGRenderer::preprocess() () at /usr/lib/libQt5Quick.so.5 #19 0x7fa45e894549 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #20 0x7fa45e894a74 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #21 0x7fa45e8fad53 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #22 0x7fa45e96ad01 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #23 0x7fa45e9099e7 in () at /usr/lib/libQt5Quick.so.5 #24 0x7fa45e90a3c7 in () at /usr/lib/libQt5Quick.so.5 #25 0x7fa45c8b4f7f in () at /usr/lib/libQt5Core.so.5 #26 0x7fa45bbde259 in start_thread () at /usr/lib/libpthread.so.0 #27 0x7fa45c3bd5e3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fa41552a640 (LWP 8119) "QSGRenderThread"): #1 0x7fa45bbe4270 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x7fa45c8bb00c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7fa45e907eb7 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa45e90a40b in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa45c8b4f7f in () at /usr/lib/libQt5Core.so.5 #6 0x7fa45bbde259 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa45c3bd5e3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fa415fc9640 (LWP 8098) "KCupsConnection"): #1 0x7fa45ae9b781 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #2 0x7fa45caf8caf in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fa45ca9e97c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa45c8b3da2 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fa4160a9bab in KCupsConnection::run() () at /usr/lib/libkcupslib.so #6 0x7fa45c8b4f7f in () at /usr/lib/libQt5Core.so.5 #7 0x7fa45bbde259 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa45c3bd5e3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fa416f53640 (LWP 8091) "latte-dock"): #1 0x7fa4573a1524 in () at /usr/lib/libusbmuxd-2.0.so.6 #2
[kwin] [Bug 394890] Compositing disabled on external monitor connection if background contrast effect is disabled
https://bugs.kde.org/show_bug.cgi?id=394890 slayer5...@icloud.com changed: What|Removed |Added Keywords||reproducible, usability -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394890] Compositing disabled on external monitor connection if background contrast effect is disabled
https://bugs.kde.org/show_bug.cgi?id=394890 slayer5...@icloud.com changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #21 from slayer5...@icloud.com --- Still an issue 2 years later, this is super annoying to new users and usability I can tell you that much. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394890] Compositing disabled on external monitor connection if background contrast effect is disabled
https://bugs.kde.org/show_bug.cgi?id=394890 slayer5...@icloud.com changed: What|Removed |Added CC||slayer5...@icloud.com Version|5.20.5 |5.21.5 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 383931] DVD rip to mpeg4 format fails
https://bugs.kde.org/show_bug.cgi?id=383931 Patrick Silva changed: What|Removed |Added CC||alexander.pross@googlemail. ||com --- Comment #19 from Patrick Silva --- *** Bug 435723 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 435723] Tried to rip dvd but transcode claims there is an error
https://bugs.kde.org/show_bug.cgi?id=435723 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 383931 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435728] When using scaling, cursor is unconditionally scaled even when an appropriate larger pixmap is available
https://bugs.kde.org/show_bug.cgi?id=435728 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437930] New: That it shows which api an application uses
https://bugs.kde.org/show_bug.cgi?id=437930 Bug ID: 437930 Summary: That it shows which api an application uses Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: toadfi...@tutanota.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Would be cool if you could see which api each app uses,OpenGL or Vulkan or something else. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432087] Empty space on top of User Feedback KCM can produce unnecessary scroll bar depending on screen resolution
https://bugs.kde.org/show_bug.cgi?id=432087 Patrick Silva changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=437869 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437869] Kuserfeedback KCM Shows Visual Inconsistencies
https://bugs.kde.org/show_bug.cgi?id=437869 Patrick Silva changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=432087 CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 437791] konsole window 1 line height when there is no konsolesrc
https://bugs.kde.org/show_bug.cgi?id=437791 Patrick Silva changed: What|Removed |Added CC||lv215...@anonaddy.me --- Comment #3 from Patrick Silva --- *** Bug 437887 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 437887] Window size is very small in the first startup
https://bugs.kde.org/show_bug.cgi?id=437887 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 437791 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437929] After removing panel, Apps Launcher can no longer be invoked via Touchscreen
https://bugs.kde.org/show_bug.cgi?id=437929 --- Comment #2 from PGillespie --- Doesn't work after restarting. Don't know if it's related, but I get a blue glow at the screen edge when trying to invoke the app dash, acting as though there were a hidden panel. Also, with the default panel below, if I hover over the top edge of the bottom panel with the mouse arrow, I get a similar blue glow at the bottom edge of the screen as though there were a hidden panel. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 437909] Cursor type changes to Cursor:dragging on Desktop after drag and drop from Desktop to browser
https://bugs.kde.org/show_bug.cgi?id=437909 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 428747 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428747] Cursor gets stuck as a grabbing hand when hovering over the desktop after dragging a desktop file to Firefox
https://bugs.kde.org/show_bug.cgi?id=428747 Patrick Silva changed: What|Removed |Added CC||liubomi...@gmail.com --- Comment #5 from Patrick Silva --- *** Bug 437909 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437929] After removing panel, Apps Launcher can no longer be invoked via Touchscreen
https://bugs.kde.org/show_bug.cgi?id=437929 --- Comment #1 from PGillespie --- I continue to experiment with this but now, even after re-adding the default panel, I can no longer invoke the App Dashboard from the screen edge using a touch screen gesture. Window Switching and the Desktop grid continue to function. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437929] New: After removing panel, Apps Launcher can no longer be invoked via Touchscreen
https://bugs.kde.org/show_bug.cgi?id=437929 Bug ID: 437929 Summary: After removing panel, Apps Launcher can no longer be invoked via Touchscreen Product: plasmashell Version: 5.21.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vermontp...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY After setting up the top edge of the Touch Screen to invoke the application dashboard, I removed the panel altogether (having installed Latte Tasks). It appears that removing the panel means that I can no longer invoke the application launcher or dashboard. If I reinstall the panel, then the touchscreen gesture from the top edge will successfully invoke the apps dashboard. STEPS TO REPRODUCE 1. Set any touch screen edge to invoke apps launcher or dashboard. 2. Remove panel. 3. Attempt to invoke apps from screen edge. OBSERVED RESULT Unable to launch apps launcher or dashboard (as this functionality appears to depend on the panel). EXPECTED RESULT SOFTWARE/OS VERSIONS System:Host: NEON Kernel: 5.12.8-surface x86_64 bits: 64 Desktop: KDE Plasma 5.21.90 Distro: KDE neon 20.04 Testing Edition ADDITIONAL INFORMATION Wayland Session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437928] After Touchscreen Edge Gesture, Grid doesn't respond to Touchscreen Input
https://bugs.kde.org/show_bug.cgi?id=437928 --- Comment #1 from PGillespie --- Using Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437928] New: After Touchscreen Edge Gesture, Grid doesn't respond to Touchscreen Input
https://bugs.kde.org/show_bug.cgi?id=437928 Bug ID: 437928 Summary: After Touchscreen Edge Gesture, Grid doesn't respond to Touchscreen Input Product: plasmashell Version: 5.21.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vermontp...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY After setting Right Center Edge to "Desktop Grid" via "Touchscreen Settings", and after invoking the Desktop Grid, the grid itself does not respond to touchscreen gestures like tapping, forcing the user to choose another desktop or app via the touchpad or mouse. STEPS TO REPRODUCE 1. Set (in my use case) right center edge to "Desktop Grid" in Touchscreen Settings. 2. Invoke Desktop Grid via touchscreen. 3. Attempt to interact with the desktop grid via touchscreen. OBSERVED RESULT Desktop grid does not respond to touchscreen gestures. EXPECTED RESULT SOFTWARE/OS VERSIONS System:Host: NEON Kernel: 5.12.8-surface x86_64 bits: 64 Desktop: KDE Plasma 5.21.90 Distro: KDE neon 20.04 Testing Edition ADDITIONAL INFORMATION Microsoft Surface Go 1rst Edition -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 437927] New: Position and Zoom doesn't apply to final render
https://bugs.kde.org/show_bug.cgi?id=437927 Bug ID: 437927 Summary: Position and Zoom doesn't apply to final render Product: kdenlive Version: git-master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: colin@vpzom.click Target Milestone: --- Created attachment 138912 --> https://bugs.kde.org/attachment.cgi?id=138912=edit Sample project demonstrating the issue SUMMARY The Position and Zoom effect doesn't seem to work when rendering a video, though it does work in the preview. In this example I use an image clip, but have also observed the issue with video clips. STEPS TO REPRODUCE 1. Import an image clip 2. Create a Color Clip 3. Add both clips to the timeline so that the image is over the color clip 4. Select the image clip in the timeline and apply a Position and Zoom effect 5. Change the fields of the effect to be noticeably different from the default state 6. Render the project to a file OBSERVED RESULT The output file has the image in its default state, scaled to fit the screen EXPECTED RESULT The image should apply the selected effect. It works in the preview view but not for the actual render. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, kernel 5.10.39-1-lts, not using plasma KDE Plasma Version: n/a KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION tested with git master and the arch package, same behaviour applies to both -- You are receiving this mail because: You are watching all bug changes.
[kapman] [Bug 190372] time not paused properly
https://bugs.kde.org/show_bug.cgi?id=190372 Frederik Schwarzer changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #9 from Frederik Schwarzer --- This has been fixed with https://invent.kde.org/games/kapman/commit/9f10c0192116101a77f809313c0b565aa61fe2a3 and https://invent.kde.org/games/kapman/commit/84cff24b138d39cc027e82dae8ee955c629d13e2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437901] Klipper security risks
https://bugs.kde.org/show_bug.cgi?id=437901 medin changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|NOT A BUG |--- --- Comment #6 from medin --- (In reply to David Edmundson from comment #5) > Only through the mechanism keepassxc uses. > Klipper has no other way to determine the source of clipboard data. It's technically possible, on Mate I did it with CopyQ to avoid saving my copied data from specific apps like Writer, Eclipse... The problem with Plasma desktop is that Klipper cannot be disabled because it causes a loss of data when the origin app from which the data is copied is closed. -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 437879] Segfault in Card::sources on 1.3 on Pinephone
https://bugs.kde.org/show_bug.cgi?id=437879 Bhushan Shah changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma-mobile/plasma-dialer/com ||mit/0c10171436a1dac0a4735fa ||1b03409aac670b786 Status|ASSIGNED|RESOLVED --- Comment #5 from Bhushan Shah --- Git commit 0c10171436a1dac0a4735fa1b03409aac670b786 by Bhushan Shah. Committed on 31/05/2021 at 10:24. Pushed by bshah into branch 'master'. Fix crash if used with wrong UCM Wrong/old UCM does not have some proper namings, which means it will not find earpiece/speaker and mic ports and m_voiceCallCard will never be set. While this means audio will not work, at least guard against the crasher. M +5-0src/callaudio.cpp https://invent.kde.org/plasma-mobile/plasma-dialer/commit/0c10171436a1dac0a4735fa1b03409aac670b786 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433134] Cannot highlight task when hovering in Wayland
https://bugs.kde.org/show_bug.cgi?id=433134 --- Comment #8 from Grósz Dániel --- (In reply to Patrick Silva from comment #5) > Since Plasma 5.22 beta, you need to hover over the window preview of the > tooltip. Expect new bug reports about this... :) I for one often use the feature to find the window I'm looking for by moving my mouse along the task bar, so I don't think I'll like this change. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433134] Cannot highlight task when hovering in Wayland
https://bugs.kde.org/show_bug.cgi?id=433134 --- Comment #7 from Patrick Silva --- (In reply to kdbase-kdebug from comment #6) > You may want to add a sentence in the release notes about the new behavior. I do not write the release notes, but I totally agree. :) The new behavior was mentioned in beta announcement, under "General Plasma": "The Task Manager’s 'Highlight Windows' feature now only highlights windows when hovering over that window’s thumbnail in the tooltip, and this behavior has been turned on by default" see https://kde.org/announcements/plasma/5/5.21.90/ -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 437926] New: Non-ASCII characters in certificate names are not printed on a signed document
https://bugs.kde.org/show_bug.cgi?id=437926 Bug ID: 437926 Summary: Non-ASCII characters in certificate names are not printed on a signed document Product: okular Version: 21.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: johan...@selfnet.de Target Milestone: --- SUMMARY Non-ASCII characters in certificate names are removed from the string printed on the document which starts with "Signed by". I think the signing feature text should revert to the friendlyName property instead of just removing those characters from the name property. STEPS TO REPRODUCE 0. Obtain a certificate with a special (= non-ASCII) character 1. Configure PDF backend to access NSS Certificate DB 2. Digitally sign a pdf OBSERVED RESULT Special characters are removed from the rendered text that reads: Signed by: EXPECTED RESULT Either the correct name should be rendered there or the friendlyName specified as part of the certificate. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437925] Crash or hang when either opening or closing a VirtualBox VM
https://bugs.kde.org/show_bug.cgi?id=437925 --- Comment #1 from AK-47 --- Possibly related, I also find that killing XWayland will also crash the entire session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437925] New: Crash or hang when either opening or closing a VirtualBox VM
https://bugs.kde.org/show_bug.cgi?id=437925 Bug ID: 437925 Summary: Crash or hang when either opening or closing a VirtualBox VM Product: kwin Version: 5.21.90 Platform: RedHat RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: chkb...@safe-mail.net Target Milestone: --- SUMMARY When opening or closing a VirtualBox VM, the whole session (presumably thanks to KWin) crashes. This does not happen under X11 session. STEPS TO REPRODUCE 1. Open VirtualBox in Wayland session and attempt to start a Virtual Machine. 2. If there is no crash, close the VM. 3. If there is still no crash, repeat the steps. OBSERVED RESULT The entire session either crashes or locks up. This also occurs when attempting to load a saved VM or attempting to save the VM. The Linux OS itself is stable, and this only occurs in the Wayland session. EXPECTED RESULT The VM should either start or stop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Workstation Rawhide, kernel 5.13.0.0-rc3.25.fc35.x86_64 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 On a side note, I wish the System Information dialog would show the KDE Plasma version. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437901] Klipper security risks
https://bugs.kde.org/show_bug.cgi?id=437901 David Edmundson changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #5 from David Edmundson --- Only through the mechanism keepassxc uses. Klipper has no other way to determine the source of clipboard data. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433134] Cannot highlight task when hovering in Wayland
https://bugs.kde.org/show_bug.cgi?id=433134 --- Comment #6 from kdbase-kde...@yahoo.com --- Thanks. In fact, I again tried the 5.22 beta yesterday, before seeing your note, to see if this worked. It didn't (I thought), until I happened to move the cursor into the tooltip preview, and saw the full window preview. I've been happily logged into Plasma Wayland since then. You may want to add a sentence in the release notes about the new behavior. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 437888] Opens 19+k files and causes 'Too many open files' error
https://bugs.kde.org/show_bug.cgi?id=437888 --- Comment #4 from Yuri --- Created attachment 138911 --> https://bugs.kde.org/attachment.cgi?id=138911=edit baloofilerc Attaching the .config/baloofilerc file. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437901] Klipper security risks
https://bugs.kde.org/show_bug.cgi?id=437901 medin changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from medin --- (In reply to David Edmundson from comment #3) > "save clipboard contents on exit" > > If that doesn't work, please do let me know. That option just clears the whole Klipper data after logging out. What I meant is if there's any way to exclude copied texts within a specific app from being saved or shown in Klipper like how KeePassXC does it ? -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 437923] Okular help crash when opening
https://bugs.kde.org/show_bug.cgi?id=437923 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it --- Comment #1 from Luigi Toscano --- Uhm, I can't reproduce it on Fedora 34 with some updates (Okular 21.04.1, khelpcenter 5.7.6.21041, Frameworks 5.82, Qt 5.15.2) on X11. Maybe a Wayland-specific issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437924] New: application Icon shows audio icon even if application is not capable ot emitting sound
https://bugs.kde.org/show_bug.cgi?id=437924 Bug ID: 437924 Summary: application Icon shows audio icon even if application is not capable ot emitting sound Product: plasmashell Version: 5.21.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: germano.massu...@gmail.com Target Milestone: 1.0 Created attachment 138910 --> https://bugs.kde.org/attachment.cgi?id=138910=edit screenshot I added Dolphin to my applications manager in Plasma panel. When I open Dolphin the icon is replaced by the bar of the application, and this is an expected behaviour but when I change desktop, the Dolphin icon (that will appear again of course) contains the small icon of the audio, even if Dolphin is not capable to emit any sound (see attachment). This happens also with other applications -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 437923] Okular help crash when opening
https://bugs.kde.org/show_bug.cgi?id=437923 Luigi Toscano changed: What|Removed |Added Component|general |general Version|unspecified |5.7.6.21041 Product|okular |khelpcenter Assignee|okular-de...@kde.org|kde-doc-engl...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 437923] Okular help crash when opening
https://bugs.kde.org/show_bug.cgi?id=437923 Luigi Toscano changed: What|Removed |Added Product|khelpcenter |okular Assignee|kde-doc-engl...@kde.org |okular-de...@kde.org Component|general |general Version|5.7.6.21041 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437906] Ditch the Konqi image when hitting the about button
https://bugs.kde.org/show_bug.cgi?id=437906 David Edmundson changed: What|Removed |Added Resolution|--- |NOT A BUG CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #3 from David Edmundson --- >It’s already removed on master. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437901] Klipper security risks
https://bugs.kde.org/show_bug.cgi?id=437901 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from David Edmundson --- "save clipboard contents on exit" If that doesn't work, please do let me know. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 437923] New: Okular help crash when opening
https://bugs.kde.org/show_bug.cgi?id=437923 Bug ID: 437923 Summary: Okular help crash when opening Product: khelpcenter Version: 5.7.6.21041 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: la_is...@mac.com Target Milestone: --- Application: khelpcenter (5.7.6.21041) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.3-arch1-1 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.5 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Selected Tools > Add Signature Drew a rectangle to hold a Signature Got a message reading that there is no Signature and that I can consult Okular help on how to add a signature Clicked on the hyperlink Okular help opens and crashes immediately The crash can be reproduced every time. -- Backtrace: Application: Centre d'aide (khelpcenter), signal: Segmentation fault [KCrash Handler] #4 0x7fc6b16ec024 in _XGetRequest () from /usr/lib/libX11.so.6 #5 0x7fc6b16c5f17 in XChangeWindowAttributes () from /usr/lib/libX11.so.6 #6 0x7fc6b3b5bd82 in KHTMLView::mouseMoveEvent(QMouseEvent*) () from /usr/lib/libKF5KHtml.so.5 #7 0x7fc6b2b360be in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #8 0x7fc6b2be584f in QFrame::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #9 0x7fc6b3b57de0 in KHTMLView::eventFilter(QObject*, QEvent*) () from /usr/lib/libKF5KHtml.so.5 #10 0x7fc6b1ef0d62 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #11 0x7fc6b2af2d51 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x7fc6b2afaac9 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #13 0x7fc6b1ef100a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #14 0x7fc6b2af957b in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib/libQt5Widgets.so.5 #15 0x7fc6b2b4fa84 in ?? () from /usr/lib/libQt5Widgets.so.5 #16 0x7fc6b2b52db5 in ?? () from /usr/lib/libQt5Widgets.so.5 #17 0x7fc6b2af2d62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #18 0x7fc6b1ef100a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #19 0x7fc6b23f7210 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #20 0x7fc6b23cc7e5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #21 0x7fc6af880b71 in ?? () from /usr/lib/libQt5WaylandClient.so.5 #22 0x7fc6afef002c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0x7fc6aff43b59 in ?? () from /usr/lib/libglib-2.0.so.0 #24 0x7fc6afeed781 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0x7fc6b1f49c36 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #26 0x7fc6b1eef97c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #27 0x7fc6b1ef7ee4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #28 0x7fc6b4331ea7 in kdemain () from /usr/lib/libkdeinit5_khelpcenter.so #29 0x7fc6b414bb25 in __libc_start_main () from /usr/lib/libc.so.6 #30 0x561f2481e05e in ?? () [Inferior 1 (process 30255) detached] Possible duplicates by query: bug 182833. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434969] Soft Proofing not working entirely, making the canvas transparent or glitchy. 5.0 pre alpha
https://bugs.kde.org/show_bug.cgi?id=434969 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #18 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/871 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 437922] Multiple konsole tabs for Kate
https://bugs.kde.org/show_bug.cgi?id=437922 Robert Devasia changed: What|Removed |Added Version|unspecified |21.04.1 Component|general |general Assignee|kmymoney-de...@kde.org |kwrite-bugs-n...@kde.org Product|kmymoney|kate -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 210620] No "Control" toolbar button-menu or other obvious way of re-enabling the menubar once hidden
https://bugs.kde.org/show_bug.cgi?id=210620 --- Comment #9 from BryanFRitt --- Ok editing the first file didn't work for me, but editing ~/.config/gwenviewrc got the menu back! Exit all gwenview windows. Edit ~/.config/gwenviewrc by changing 'MenuBar' to 'Enabled', aka 'MenuBar=Enabled'. Save and close file. Then restart gwenview, and the menu will be back. (`ctrl+m` still doesn't work for me) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437920] Plasma dialog shadow lost during fadeout animation on window close
https://bugs.kde.org/show_bug.cgi?id=437920 --- Comment #2 from Kai Uwe Broulik --- X11 -- You are receiving this mail because: You are watching all bug changes.
[peruse] [Bug 437921] crash when loading certain comic books with subfolders.
https://bugs.kde.org/show_bug.cgi?id=437921 wolthera changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/peruse/commit/b6cd4eaf ||4e336866eb26d89f74876e025f9 ||411e8 Status|REPORTED|RESOLVED --- Comment #1 from wolthera --- Git commit b6cd4eaf4e336866eb26d89f74876e025f9411e8 by Wolthera van Hövell tot Westerflier. Committed on 31/05/2021 at 19:56. Pushed by woltherav into branch 'master'. Use asConst for several stringlists. M +3-3src/qtquick/ArchiveBookModel.cpp https://invent.kde.org/graphics/peruse/commit/b6cd4eaf4e336866eb26d89f74876e025f9411e8 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 437922] New: Multiple konsole tabs for Kate
https://bugs.kde.org/show_bug.cgi?id=437922 Bug ID: 437922 Summary: Multiple konsole tabs for Kate Product: kmymoney Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: robertdevasi...@gmail.com Target Milestone: --- SUMMARY Kate's integrated terminal(Konsole) should need the ability to open multiple tabs STEPS TO REPRODUCE 1. Enable Terminal Tool View from Kate --> Settings --> Configure Kate Settings --> Plugins 2. Click Terminal from the bottom 3. OBSERVED RESULT Will open the current tab. Tried Ctrl+Shift+T but it is already set for new Tab in Kate.No options it the menu either. EXPECTED RESULT Need an option either from the menu or by a new shortkey SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 437888] Opens 19+k files and causes 'Too many open files' error
https://bugs.kde.org/show_bug.cgi?id=437888 --- Comment #3 from tagwer...@innerjoin.org --- (In reply to Yuri from comment #2) > The only thing that I did - I installed kde5. It does whatever kde5 does by > default. If you could attach the .config/baloofilerc file, that should say what's happening. I do see that different distributions set up baloo indexing in different ways. > There is no need to keep files open in order to index them. Clear. What I see in Linux is that the "baloo_file" process makes a list of all the files that need indexing and, if content indexing is enabled, feeds batches of 40 files to the indexer process "baloo_file_extractor" to be read and indexed. "baloo_file" does however attempt to work out the Mime Type of the files - and this can require a 'peek' into the file if it is not clear from the the file extension. > It looks like baloo either leaks file descriptors, or keeps them referenced > for no good reason. I'm pretty sure I've have hit the same issue on Linux if there was a general problem. Googling says that "ulimit -n" shows the limit, this gives me 1024 and I have no trouble... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437901] Klipper security risks
https://bugs.kde.org/show_bug.cgi?id=437901 medin changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|NOT A BUG |--- --- Comment #2 from medin --- (In reply to David Edmundson from comment #1) > This is configurable. I opened Klipper config dialog and couldn't find any option to do it, where can I find it ? What I want is to avoid Klipper from saving some sensitive info copied from an application (based on JavaFX) which needs heavy copy/paste actions to work. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 210620] No "Control" toolbar button-menu or other obvious way of re-enabling the menubar once hidden
https://bugs.kde.org/show_bug.cgi?id=210620 --- Comment #8 from Sérgio Basto --- Ctrl+M works for me with with 20.08.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 397953] KIO::highlightInFileManager does not respect default file manager setting when launched via FileManager1 DBus activation
https://bugs.kde.org/show_bug.cgi?id=397953 Patrick Silva changed: What|Removed |Added Version|5.70.0 |5.82.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437692] Dolpin Version > 20.12.3 does not start in Firefox/Opera by clicking "open containing Folder"
https://bugs.kde.org/show_bug.cgi?id=437692 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- Cannot reproduce with Dolphin 21.04.1 on Arch Linux running Plasma 5.22 beta. Both Firefox and Opera open the file manager, despite on my system it is nautilus instead of default Dolphin because bug 397953. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437893] rendering problem on vulkan full-screen applications
https://bugs.kde.org/show_bug.cgi?id=437893 --- Comment #1 from Vlad Zahorodnii --- Do visual artifacts persist if you disable compositing? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437576] Recent Files/Locations page shows wrong description
https://bugs.kde.org/show_bug.cgi?id=437576 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- I can reproduce with Dolphin 21.04.1 on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[peruse] [Bug 437921] New: crash when loading certain comic books with subfolders.
https://bugs.kde.org/show_bug.cgi?id=437921
Bug ID: 437921
Summary: crash when loading certain comic books with
subfolders.
Product: peruse
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ad...@leinir.dk
Reporter: griffinval...@gmail.com
Target Milestone: ---
SUMMARY
This problem seems to happen most often with the Pepper and Carrot Volume 1
ACBF example file, on entries that are inside folders, but otherwise not
unique. I can open the file fine with ark.
Possible Fix
--
When I change the for loops from
for (const QString : entries)
{
to
for(int i =0; i::load (__m=std::memory_order_relaxed, this=0x0) at
/usr/include/c++/9/bits/atomic_base.h:419
#1 QAtomicOps::loadRelaxed (_q_value=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239
--Type for more, q to quit, c to continue without paging--
#2 0x7fffe173dedc in QBasicAtomicInteger::loadRelaxed (this=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107
#3 0x7fffe173db62 in QtPrivate::RefCount::ref (this=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:55
#4 0x7fffe173dc55 in QString::QString (this=0x7fec7dc8, other=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1094
#5 0x7fffe175c97f in operator+ (s1=..., s2=0x7fffe17b6777 "/") at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1534
#6 0x7fffe1749f73 in recursiveEntries (dir=0x579263e0) at
/home/wolthera/Peruse/src/src/qtquick/ArchiveBookModel.cpp:194
#7 0x7fffe174a416 in ArchiveBookModel::setFilename (this=0x578eebb0,
newFilename=...) at
/home/wolthera/Peruse/src/src/qtquick/ArchiveBookModel.cpp:232
#8 0x7fffe176dd1b in BookListModel::contentModelItemsInserted
(this=0x55c5e930, index=..., first=1047, last=1047) at
/home/wolthera/Peruse/src/src/qtquick/BookListModel.cpp:297
#9 0x7fffe177237c in QtPrivate::FunctorCall, QtPrivate::List, void, void
(BookListModel::*)(QModelIndex, int, int)>::call (f=(void
(BookListModel::*)(class BookListModel * const, class QModelIndex, int, int))
0x7fffe176cef2 , o=0x55c5e930, arg=0x7fec8380) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152
#10 0x7fffe1771f2b in QtPrivate::FunctionPointer::call, void> (f=(void (BookListModel::*)(class BookListModel *
const, class QModelIndex, int, int)) 0x7fffe176cef2
,
o=0x55c5e930, arg=0x7fec8380) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185
#11 0x7fffe1771aaa in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x55a7f290, r=0x55c5e930,
a=0x7fec8380, ret=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:418
#12 0x764636fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x763cea92 in QAbstractItemModel::rowsInserted(QModelIndex const&,
int, int, QAbstractItemModel::QPrivateSignal) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x763d7652 in QAbstractItemModel::endInsertRows() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fffe13e7993 in ContentList::fileFound (this=0x55c008d0,
filePath=..., metaData=...) at
/home/wolthera/Peruse/src/src/contentlist/ContentList.cpp:149
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 437906] Ditch the Konqi image when hitting the about button
https://bugs.kde.org/show_bug.cgi?id=437906 --- Comment #2 from Lua --- It's a funny image though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437920] Plasma dialog shadow lost during fadeout animation on window close
https://bugs.kde.org/show_bug.cgi?id=437920 --- Comment #1 from Vlad Zahorodnii --- X11 or Wayland? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 210620] No "Control" toolbar button-menu or other obvious way of re-enabling the menubar once hidden
https://bugs.kde.org/show_bug.cgi?id=210620 BryanFRitt changed: What|Removed |Added CC||bryanfr...@hotmail.com --- Comment #7 from BryanFRitt --- Started to post a new bug, but later found this one. So posting here as a me too, rather than a new bug. SUMMARY There's no way to get the menu bar back once gone. STEPS TO REPRODUCE I think it went like this right click somewhere > hide menu tried right clicking in several spots, tried `ctrl+m`, etc... nothing got the menu back. :( OBSERVED RESULT Menu bar gone, no way to get back. I've even tried `Ctrl+m`, another website suggested(even if this were to work it should be more obvious than this). Tried mv ~/.kde/share/apps/gwenview/gwenviewui.rc ~/.kde/share/apps/gwenview/~gwenviewui.rc~ But the menu is still missing... :( EXPECTED RESULT There be an obvious way to get the menu bar back. (Next best thing: It would be better NOT to have a way to hide the menu bar, than to be able to be able to hide it with no way of getting it back) p.s. Now, How to get the menu back? SOFTWARE/OS VERSIONS Debian 10.x stable Linux/KDE Plasma: (available in About System) KDE Plasma Version: Found in kate... KDE Frameworks Version: "5.54.0" Qt Version: "5.11.3 (built against 5.11.3)" gwenview --version gwenview 18.04.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422072] Plasma hangs when quickly moving the mouse cursor back and forth
https://bugs.kde.org/show_bug.cgi?id=422072 --- Comment #13 from Patrick Silva --- *** Bug 410741 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410741] [Wayland] Plasma froze after I hover over entries of the task manager and icons in systray
https://bugs.kde.org/show_bug.cgi?id=410741 Patrick Silva changed: What|Removed |Added Resolution|WORKSFORME |DUPLICATE --- Comment #11 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 422072 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422072] Plasma hangs when quickly moving the mouse cursor back and forth
https://bugs.kde.org/show_bug.cgi?id=422072 --- Comment #12 from Patrick Silva --- I reported this issue as bug 410741 on August 2019. It happened again on my neon unstable a few days ago. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437920] New: Plasma dialog shadow lost during fadeout animation on window close
https://bugs.kde.org/show_bug.cgi?id=437920 Bug ID: 437920 Summary: Plasma dialog shadow lost during fadeout animation on window close Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: k...@privat.broulik.de Target Milestone: --- Created attachment 138909 --> https://bugs.kde.org/attachment.cgi?id=138909=edit Dialog during fade out transition SUMMARY The dialog shadow vanishes during the window's fade out transition STEPS TO REPRODUCE 1. notify-send foo bar 2. wait for the notification to time out OBSERVED RESULT The popup fades out but immediately loses its shadow EXPECTED RESULT The popup fades out but has its shadow fade out like the rest of the dialog SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master as of 2021-05-23 KDE Frameworks Version: 5.82 Qt Version: 5.15.2 ADDITIONAL INFORMATION Can be more easily observed by reducing animation speed -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435049] [wayland] - the option "open new folders in tabs" does not work
https://bugs.kde.org/show_bug.cgi?id=435049 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- I can reproduce on Wayland session of Plasma 5.22 beta, Arch Linux. Operating System: Arch Linux KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437083] Kwin_wayland crashes in KWin::GLVertexBuffer::reset()
https://bugs.kde.org/show_bug.cgi?id=437083 Thiago Sueto changed: What|Removed |Added Ever confirmed|0 |1 CC||herzensch...@gmail.com Status|REPORTED|CONFIRMED --- Comment #11 from Thiago Sueto --- After demangling my core dump with c++filt it seems to provide the same backtrace Nate posted on comment #10. This seems to be hindering login to the Wayland session with latest KWin from master, causing multiple sequential crashes according to journalctl (I tested with a new user as well). I'm on openSUSE Krypton. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 437553] Konsole: Touchscreen scrolling selects content rather than scrolling.
https://bugs.kde.org/show_bug.cgi?id=437553 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437357] "Open containing folder" feature of notifications should respect "Open new folders in tabs" feature of Dolphin
https://bugs.kde.org/show_bug.cgi?id=437357 --- Comment #5 from Patrick Silva --- I have just noticed that the bug only occurs on Wayland (tested on both Arch and neon unstable). Can you confirm Nate? If so, this bug seems a duplicate of bug 435049, which I also can reproduce on Arch Linux running Plasma 5.22 beta at least. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 437856] org.kde.dolphin: A wrong translation was found: "« Plus tôt en » MMMM, yyyy".
https://bugs.kde.org/show_bug.cgi?id=437856 Jazeix Johnny changed: What|Removed |Added CC||jaz...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Jazeix Johnny --- Hi, thank you for your report! We are actually looking at it. French translation team has found the issue (https://invent.kde.org/system/dolphin/-/blob/master/src/kitemviews/kfileitemmodel.cpp#L2182) and we are planning to discuss with the dolphin people to understand why the single quotes should not be translated to guillemets. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437912] Similarity-Duplicates digiKam closes unexpectedly.
https://bugs.kde.org/show_bug.cgi?id=437912 --- Comment #3 from hann...@hot.ee --- I have completely deleted the file IMG_20210418_162847.jpg. This unexpected shutdown may have been related to the deletion of this file because Update fingerprints was running at the same time. I must have just deleted it and clicked the side file to get into view mode. In general, digiKam responded slowly or not at all to mouse clicks during this period. This digiKam shutdown happened today with different files, even multiple times when Update fingerprints were running at the same time. Hannes -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397999] Sort thumbs by date.. causes issues
https://bugs.kde.org/show_bug.cgi?id=397999 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||7.3.0 --- Comment #4 from Maik Qualmann --- Fixed with bug 437897, we now always have a creation date, if the file date is not valid, we use the current date. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395598] Cannot use CJK input method in input boxes on popup UI elements.
https://bugs.kde.org/show_bug.cgi?id=395598 --- Comment #21 from Alvin Wong --- Please let me know if it doesn't work, or if you find more popups with the same issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395598] Cannot use CJK input method in input boxes on popup UI elements.
https://bugs.kde.org/show_bug.cgi?id=395598 Alvin Wong changed: What|Removed |Added Status|REOPENED|RESOLVED Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/30754f5f4 |hics/krita/commit/8717078e1 |0e2e6711a639a920fe62c8d4a2b |7f9d3269103e6b37f31fb968930 |2646|5fdd Resolution|--- |FIXED --- Comment #20 from Alvin Wong --- Git commit 8717078e17f9d3269103e6b37f31fb9689305fdd by Alvin Wong. Committed on 31/05/2021 at 18:03. Pushed by alvinwong into branch 'master'. Fix input method not working on new tag box M +24 -1libs/resourcewidgets/TagActions.cpp https://invent.kde.org/graphics/krita/commit/8717078e17f9d3269103e6b37f31fb9689305fdd -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437897] Windows timestamp to metadata extraction for TIFFs changes when modifying files
https://bugs.kde.org/show_bug.cgi?id=437897 Maik Qualmann changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/9e7d86b ||09b062ccc25a2ba75e52fd3143d ||282b6b Version Fixed In||7.3.0 Resolution|--- |FIXED --- Comment #9 from Maik Qualmann --- Git commit 9e7d86b09b062ccc25a2ba75e52fd3143d282b6b by Maik Qualmann. Committed on 31/05/2021 at 18:00. Pushed by mqualmann into branch 'master'. always use the file created date if it is valid FIXED-IN: 7.3.0 M +2-1NEWS M +7-13 core/libs/database/item/scanner/itemscanner_file.cpp M +7-13 core/libs/dimg/dimg_fileio.cpp https://invent.kde.org/graphics/digikam/commit/9e7d86b09b062ccc25a2ba75e52fd3143d282b6b -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425287] Firefox always asks to be default browser
https://bugs.kde.org/show_bug.cgi?id=425287 --- Comment #6 from Patrick Silva --- (In reply to David Edmundson from comment #5) > Afaik it's a bug in xdg-utils. > > We saw and fixed something similar, but it's still pending fd.o release are you talking about this commit? https://gitlab.freedesktop.org/xdg/xdg-utils/-/commit/d11b33ec7f24cfb1546f6b459611d440013bdc72 I'm using https://aur.archlinux.org/packages/xdg-utils-git and Firefox 88.0.1 on Arch Linux and the bug reported here persists despite I do not use GTK_USE_PORTAL=1 on my system. Operating System: Arch Linux KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437897] Windows timestamp to metadata extraction for TIFFs changes when modifying files
https://bugs.kde.org/show_bug.cgi?id=437897 --- Comment #8 from Maik Qualmann --- The problem is, if the modifications date is older, we use it because we are looking for the oldest date as the creation date. In the case where there is no metadata, should we always use the file creation date? Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 431505] Kdenlive crashes instantly on Wayland due to EGL format mismatch
https://bugs.kde.org/show_bug.cgi?id=431505 emohr changed: What|Removed |Added Flags|Backport+ |Brainstorm+ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436895] Rotoscoping not working right
https://bugs.kde.org/show_bug.cgi?id=436895 emohr changed: What|Removed |Added Flags|Backport+ |Brainstorm+ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434167] Clip in project bin doesn't work correctly on grouped clips
https://bugs.kde.org/show_bug.cgi?id=434167 emohr changed: What|Removed |Added Flags|Backport+ |Brainstorm+ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437912] Similarity-Duplicates digiKam closes unexpectedly.
https://bugs.kde.org/show_bug.cgi?id=437912 --- Comment #2 from Maik Qualmann --- This was the last image: D:/MEEDIA/My Pictures/2021/2021-04-18/IMG_20210418_162847.jpg Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437912] Similarity-Duplicates digiKam closes unexpectedly.
https://bugs.kde.org/show_bug.cgi?id=437912 Maik Qualmann changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437912] Similarity-Duplicates digiKam closes unexpectedly.
https://bugs.kde.org/show_bug.cgi?id=437912 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The log shows no abnormalities, try to find out whether it is a specific image that is causing digiKam to crash. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437897] Windows timestamp to metadata extraction for TIFFs changes when modifying files
https://bugs.kde.org/show_bug.cgi?id=437897 --- Comment #7 from Maik Qualmann --- Git commit 68cf0879fd29bb7e79ab16a825883698e279b23e by Maik Qualmann. Committed on 31/05/2021 at 17:24. Pushed by mqualmann into branch 'master'. better checking of the date stamps M +17 -6core/libs/database/item/scanner/itemscanner_file.cpp M +12 -6core/libs/dimg/dimg_fileio.cpp https://invent.kde.org/graphics/digikam/commit/68cf0879fd29bb7e79ab16a825883698e279b23e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437901] Klipper security risks
https://bugs.kde.org/show_bug.cgi?id=437901 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from David Edmundson --- This is configurable. There is a mechanism by which sensitive data can be marked as not being something to save in klipper which is used by keepassxc and others. This is done by adding an additional mimetype tag when the selection is saved to the clipboard. Anything else is out of scope. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437919] New: System settings crashes everytime
https://bugs.kde.org/show_bug.cgi?id=437919 Bug ID: 437919 Summary: System settings crashes everytime Product: systemsettings Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: robinwunderbaldin...@gmail.com Target Milestone: --- Application: systemsettings5 (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-14-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: I opened the system settings app, it hangs for a short time and crashes, (showing the main system settings window, but no content). The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbcbcfddcc0 (LWP 21751))] Thread 5 (Thread 0x7fbca9dd0700 (LWP 21776)): #0 0x7fbcc1948819 in __GI___poll (fds=0x7fbc9c003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fbcbf55e136 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbcbf55e25c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbcc1e5a743 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fbcc1e0815b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fbcc1c57e76 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbcc106fc65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fbcc1c61a67 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fbcc01fbfa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7fbcc19534cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fbcabdf6700 (LWP 21772)): #0 __GI___libc_read (nbytes=16, buf=0x7fbcabdf5b20, fd=12) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=12, buf=0x7fbcabdf5b20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fbcbf5a3aa0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbcbf55dc0f in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbcbf55e0e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fbcbf55e25c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fbcc1e5a743 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbcc1e0815b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fbcc1c57e76 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fbcc106fc65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fbcc1c61a67 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fbcc01fbfa3 in start_thread (arg=) at pthread_create.c:486 #12 0x7fbcc19534cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fbcb9f76700 (LWP 21754)): #0 0x7ffca97c79f9 in ?? () #1 0x7ffca97c7bfc in clock_gettime () #2 0x7fbcc1960ff6 in __GI___clock_gettime (clock_id=1, tp=0x7fbcb9f75a70) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7fbcc1e5a061 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fbcc1e58899 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fbcc1e58e95 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbcc1e5a4be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbcbf55d669 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fbcbf55e06b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7fbcbf55e25c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7fbcc1e5a743 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fbcc1e0815b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fbcc1c57e76 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fbcc20b0545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #14 0x7fbcc1c61a67 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fbcc01fbfa3 in start_thread (arg=) at pthread_create.c:486 #16 0x7fbcc19534cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fbcbbfad700 (LWP 21753)): #0 0x7fbcc1948819 in __GI___poll (fds=0x7fbcbbfacc78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1
[kwin] [Bug 437783] Kwin crashes when mouse over time widget
https://bugs.kde.org/show_bug.cgi?id=437783 --- Comment #12 from Patrick Silva --- Sorry, I confused this bug with bug 422072(In reply to Vlad Zahorodnii from comment #10) > (In reply to Patrick Silva from comment #9) > > backtrace was provided. > > > > I can confirm this problem on neon unstable. > > I cannot reproduce it. Did you enable PIM events plugin? Sorry, I think I have confused this bug with bug 422072 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 437918] New: Crash using System Settings
https://bugs.kde.org/show_bug.cgi?id=437918 Bug ID: 437918 Summary: Crash using System Settings Product: ksysguard Version: 5.21.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: goldf...@aol.in CC: plasma-b...@kde.org Target Milestone: --- Application: ksysguard (5.21.4) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.0-17-generic x86_64 Windowing System: Wayland Drkonqi Version: 5.21.4 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: Tried to change System settings - Unusual behavior I noticed: Crash - Custom settings of the application: This happens only with the external monitor connected. Previos version (Kubuntu 20.10) worked fine. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Monitor (ksysguard), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f57f655d864 in __GI_abort () at abort.c:79 #6 0x7f57f4a14c43 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f57e77a9d39 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #8 0x7f57e77b8f9a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #9 0x7f57f4c71b44 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f57f4c750b3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f57f4c758e3 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f57f58a3173 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f57f4c3a22a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f57f4c94195 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f57eae828eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f57eaed5d28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f57eae80023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f57f4c93594 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f57f4c38b8b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f57f4c41024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f57f678f9ed in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_ksysguard.so #22 0x7f57f655f565 in __libc_start_main (main=0x559159874060, argc=1, argv=0x7ffda980e218, init=, fini=, rtld_fini=, stack_end=0x7ffda980e208) at ../csu/libc-start.c:332 #23 0x55915987409e in _start () [Inferior 1 (process 10035) detached] Possible duplicates by query: bug 429344, bug 427384, bug 424911, bug 423951, bug 423222. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 425178] Docker is spewing UdevQt: unhandled device action "move"
https://bugs.kde.org/show_bug.cgi?id=425178 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #2 from Sergey --- I see the same in a regular Qt GUI application without docker. But docker works on the same machine for other tasks. wrt USB I have only USB wireless mouse and whatever built-in into my MSI GL75 9SDK laptop. Last time I saw it, my dmesg was populated with next entries approximately the same time: [234633.368717] docker0: port 1(veth3446d1d) entered disabled state [234633.368939] vethbed7499: renamed from eth0 [234633.395120] docker0: port 1(veth3446d1d) entered disabled state [234633.398863] device veth3446d1d left promiscuous mode [234633.398867] docker0: port 1(veth3446d1d) entered disabled state -- You are receiving this mail because: You are watching all bug changes.
