[kwin] [Bug 418978] New: KWin crashed on returning from sleep
https://bugs.kde.org/show_bug.cgi?id=418978 Bug ID: 418978 Summary: KWin crashed on returning from sleep Product: kwin Version: 5.17.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: szots...@gmail.com Target Milestone: --- Application: kwin_x11 (5.17.5) Qt Version: 5.14.0 Frameworks Version: 5.65.0 Operating System: Linux 5.3.12-2-default x86_64 Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: I turned my PC on again after returning from sleep and I saw that KWin crashed. Unfortunately, I could not load more debuginfo packages since when I installed them after the crash they were newer versions and GDB could not load them. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f03922c7880 (LWP 1729))] Thread 5 (Thread 0x7f038e320700 (LWP 10835)): #0 0x7f03974d6cd6 in __GI_ppoll (fds=0x7f0384005cc8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f0395f48cf9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f0395f4a253 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f0395ef4d5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f0395d2063e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f0395d21708 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f039532bf2a in start_thread (arg=) at pthread_create.c:479 #7 0x7f03974e14af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f037700 (LWP 2089)): #0 0x7f03953326a5 in futex_wait_cancelable (private=0, expected=0, futex_word=0x7f0395926fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f03953326a5 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f0395926f68, cond=0x7f0395926f90) at pthread_cond_wait.c:508 #2 0x7f03953326a5 in __pthread_cond_wait (cond=0x7f0395926f90, mutex=0x7f0395926f68) at pthread_cond_wait.c:638 #3 0x7f039582c1ea in () at /usr/lib64/libQt5Script.so.5 #4 0x7f039582c20b in () at /usr/lib64/libQt5Script.so.5 #5 0x7f039532bf2a in start_thread (arg=) at pthread_create.c:479 #6 0x7f03974e14af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f038d85b700 (LWP 1797)): #0 0x7f03974d6cd6 in __GI_ppoll (fds=0x7f0378000d38, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f0395f48cf9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f0395f4a253 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f0395ef4d5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f0395d2063e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f0394a46a65 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f0395d21708 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f039532bf2a in start_thread (arg=) at pthread_create.c:479 #8 0x7f03974e14af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f038f5d7700 (LWP 1752)): #0 0x7f03974d6cd6 in __GI_ppoll (fds=0x7f038000ebc8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f0395f48cf9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f0395f4a253 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f0395ef4d5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f0395d2063e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f03944a5507 in () at /usr/lib64/libQt5DBus.so.5 #6 0x7f0395d21708 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f039532bf2a in start_thread (arg=) at pthread_create.c:479 #8 0x7f03974e14af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f03922c7880 (LWP 1729)): [KCrash Handler] #6 0x7f0395975f26 in () at /usr/lib64/libkwin4_effect_builtins.so.1 #7 0x7f03972ac903 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib64/libkwin.so.5 #8 0x7f03959f6c45 in () at /usr/lib64/libkwin4_effect_builtins.so.1 #9 0x7f03972ac903 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib64/libkwin.so.5 #10 0x7f039722f47b in KWin::Scene::finalPaintWindow(KWin::EffectWindowImpl*, int, QRegion, KWin::WindowPaintData&) () at
[kwin] [Bug 418977] New: After rotation mouse cursor is visible on touch device
https://bugs.kde.org/show_bug.cgi?id=418977 Bug ID: 418977 Summary: After rotation mouse cursor is visible on touch device Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bhus...@gmail.com Target Milestone: --- SUMMARY On mobile devices cursor should not be visible at all, but it appears after rotating device once using orientation sensor. STEPS TO REPRODUCE 1. Have a Mobile/Tablet device without any cursor 2. Rotate it OBSERVED RESULT Cursor is visible EXPECTED RESULT Cursor should not be visible since no mouse is attached. KDE Plasma Version: git master KDE Frameworks Version: git master Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 Bernard Gray changed: What|Removed |Added CC||bernard.g...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418976] No pen pressure when I draw on Krita. It works on other drawing softwares, but on Krita it doesn't work
https://bugs.kde.org/show_bug.cgi?id=418976 megaman...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from megaman...@gmail.com --- Actually nvm. figured out the fix -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418976] New: No pen pressure when I draw on Krita. It works on other drawing softwares, but on Krita it doesn't work
https://bugs.kde.org/show_bug.cgi?id=418976 Bug ID: 418976 Summary: No pen pressure when I draw on Krita. It works on other drawing softwares, but on Krita it doesn't work Product: krita Version: 4.2.9-beta1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: megaman...@gmail.com Target Milestone: --- SUMMARY No pen pressure when I draw on Krita. It works on other drawing softwares, but on Krita, it doesn't work STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408072] The pen pressure isnt working in this latest update, the older version before the alpha and beta had the same issue with pen pressure
https://bugs.kde.org/show_bug.cgi?id=408072 megaman...@gmail.com changed: What|Removed |Added CC||megaman...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410206] just downloaded this software. When toggling the pen pressure in configuration it doesn't work on canvas. the tablet tester shows the pen pressure working. CONFUSED
https://bugs.kde.org/show_bug.cgi?id=410206 megaman...@gmail.com changed: What|Removed |Added CC||megaman...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401800] Even so I enabled pen pressure, pen pressure is not working
https://bugs.kde.org/show_bug.cgi?id=401800 megaman...@gmail.com changed: What|Removed |Added CC||megaman...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418791] Middle click not registering on first button of Wacom Pen
https://bugs.kde.org/show_bug.cgi?id=418791 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418438] Crash when clicking "Settings->Configure Kate" in Windows 10
https://bugs.kde.org/show_bug.cgi?id=418438 --- 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.
[krita] [Bug 417343] font on user interface way too small to read
https://bugs.kde.org/show_bug.cgi?id=417343 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 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.
[khangman] [Bug 344834] installs khangman-harmattan icons even when not building harmattan version
https://bugs.kde.org/show_bug.cgi?id=344834 --- 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.
[krita] [Bug 417711] Cannot use the mouse after using the drawing tablet if I don't unfocus and focus the window again
https://bugs.kde.org/show_bug.cgi?id=417711 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 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.
[krita] [Bug 417667] Bad allocation crash
https://bugs.kde.org/show_bug.cgi?id=417667 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.
[kdenlive] [Bug 418121] If i copy a video with altered speed, it appears just one frame when i paste
https://bugs.kde.org/show_bug.cgi?id=418121 --- Comment #9 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.
[plasmashell] [Bug 415828] Memory leak
https://bugs.kde.org/show_bug.cgi?id=415828 --- 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 418139] kdenlive PID: 3.676 Señal: Segmentation fault (11)
https://bugs.kde.org/show_bug.cgi?id=418139 --- 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.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #23 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.
[kate] [Bug 418918] Comments by shortcut do not follow the indentation rule
https://bugs.kde.org/show_bug.cgi?id=418918 kogiokkaf...@gmail.com changed: What|Removed |Added CC||kogiokkaf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 418975] New: .wav files don't play when set as notification sound in gui, but work in notification sound preview
https://bugs.kde.org/show_bug.cgi?id=418975 Bug ID: 418975 Summary: .wav files don't play when set as notification sound in gui, but work in notification sound preview Product: frameworks-knotifications Version: 5.68.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: i...@kintsugi-computers.org CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 126862 --> https://bugs.kde.org/attachment.cgi?id=126862=edit Included a test .wav file I used to verify the issue. (.wav re-encode of one of the default system sounds) SUMMARY .wav files don't play back when assigned to a notification event. They play in the preview area fine but do nothing when an event is actually triggered. .ogg files work perfectly in both scenarios. STEPS TO REPRODUCE 1. Assign a short .wav file to a notification event using the notifications menu in the settings gui. 2. Note that .wav file plays back correctly when pressing the play preview button. 3. Trigger event with relevant notification. Nothing happens. 4. Re-encode file to .ogg. Assign .ogg file instead of .wav 5. Event sound now works. OBSERVED RESULT Nothing happens when a .wav file is assigned to a notification event and triggered. EXPECTED RESULT The .wav file should play when the event is triggered. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 4.15.0-91-generic / KDE Neon KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Also tested on a different system with the current blank KDE Neon install as of ~March 10. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 398069] Can't assign shortcut to activities
https://bugs.kde.org/show_bug.cgi?id=398069 --- Comment #8 from Gauthier --- This issue still persists but a workaround was provided in the other bug report related to this issue: https://bugs.kde.org/show_bug.cgi?id=416496#c2 linking to the solution described here: https://forum.kde.org/viewtopic.php?f=289=137658#p379827 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 398069] Can't assign shortcut to activities
https://bugs.kde.org/show_bug.cgi?id=398069 Gauthier changed: What|Removed |Added CC||lucassschwa...@gmail.com --- Comment #7 from Gauthier --- *** Bug 416496 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 416496] Unable to switch activity with shortcut
https://bugs.kde.org/show_bug.cgi?id=416496 Gauthier changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||achat1...@free.fr --- Comment #3 from Gauthier --- *** This bug has been marked as a duplicate of bug 398069 *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 418940] latte dock is resetting my settings for systray icons
https://bugs.kde.org/show_bug.cgi?id=418940 --- Comment #4 from andresdor...@gmail.com --- (In reply to Michail Vourlakos from comment #3) > (In reply to andresdortiz from comment #2) > > (In reply to Michail Vourlakos from comment #1) > > > it can happen if you have a broken latte layout... > > > > > > Are using Multiple Layouts mode of Single Layout? > > > > multiple > > I can fix it for you if you want but you need to send through google drive > or dropbox the specific latte layout file that contains the systray. okay here is a zip https://drive.google.com/file/d/17t2RYtAcqzphFuG767QzOHJEcGZDggX0/view?usp=sharing of my latte config for the top bar I believe I am using dock and topbar.layout for the systray -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 396291] Activities
https://bugs.kde.org/show_bug.cgi?id=396291 Gauthier changed: What|Removed |Added CC||achat1...@free.fr --- Comment #3 from Gauthier --- Is there still a plan to improve firefox integration and behaviours with activities. When restarting the computer (e.g. because of updates) with several activities and several firefox windows, those windows are restored more or less randomly to the different activities (for some reason some firefox windows almost always restore in the right activity but others are just restored randomly). This issue makes rebooting a bit of a pain. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 418739] tablet mode value is wrong in kded
https://bugs.kde.org/show_bug.cgi?id=418739 Roman Gilg changed: What|Removed |Added Latest Commit||https://commits.kde.org/lib ||kscreen/6ba447e9e59da852a51 ||4101d8f2fa467c972ff8f Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Roman Gilg --- Git commit 6ba447e9e59da852a514101d8f2fa467c972ff8f by Roman Gilg. Committed on 18/03/2020 at 01:44. Pushed by romangilg into branch 'master'. fix: transfer tablet mode properties Summary: I forgot to copy over the tablet-mode-available and -engaged data from one config to the next one. Because of that the data was not available to the daemon. Also serialize the tablet mode properties in the Serializer. The Serializer is not used on Wayland afaik but if at one point for example the RandR backend gains auto rotation support we need to have it in the Serializer. Test Plan: Manually with hard-coded tablet mode availability in KWin. Reviewers: #plasma, bshah Reviewed By: #plasma, bshah Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28106 M +2-0src/config.cpp M +10 -0src/configserializer.cpp https://commits.kde.org/libkscreen/6ba447e9e59da852a514101d8f2fa467c972ff8f -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418974] Corruption of project by broken association between video and audio clips
https://bugs.kde.org/show_bug.cgi?id=418974 --- Comment #1 from alridd...@googlemail.com --- By binary search, I have tracked the bug down to the following commit: 1ffc0b611ee6425bcac35aa732b702fa93b34c9c "Ensure audio track is inserted at correct position when no previous audio exists" -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 417805] ark crashed on closing child window
https://bugs.kde.org/show_bug.cgi?id=417805 --- Comment #4 from J Wiggins --- I installed debugging for dragonplayer as requested and crashed ark again, and sent the new report. I'm glad to help if I can. Let me know what to do. I'm only a user since 2002 on Suse so I don't know very much. Thanks for your time. This bug isn't hurting my work just slowing it a little. I like Linux and only want to help. Thanks, J On 3/14/20 4:32 AM, Elvis Angelaccio wrote: > https://bugs.kde.org/show_bug.cgi?id=417805 > > Elvis Angelaccio changed: > >What|Removed |Added > > CC||elvis.angelac...@kde.org > > --- Comment #3 from Elvis Angelaccio --- > (In reply to J Wiggins from comment #2) >> Created attachment 126644 [details] >> New crash information added by DrKonqi >> >> ark (18.12.3) using Qt 5.9.7 >> >> - What I was doing when the application crashed: Opened Windows power point >> to access media (wma), was closing 3 played windows, on closing 2nd Arc >> crashed. >> >> -- Backtrace (Reduced): >> #6 0x7f1a34017970 in () >> #7 0x7f1a268bd6e5 in () at /usr/lib64/qt5/plugins/dragonpart.so >> #8 0x7f1a268be904 in () at /usr/lib64/qt5/plugins/dragonpart.so >> #9 0x7f1a268c075b in () at /usr/lib64/qt5/plugins/dragonpart.so >> #10 0x7f1a3033c930 in () at /usr/lib64/qt5/plugins/arkpart.so > Still no debug symbols, please install them. > -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418974] New: Corruption of project by broken association between video and audio clips
https://bugs.kde.org/show_bug.cgi?id=418974 Bug ID: 418974 Summary: Corruption of project by broken association between video and audio clips Product: kdenlive Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: alridd...@googlemail.com Target Milestone: --- Created attachment 126861 --> https://bugs.kde.org/attachment.cgi?id=126861=edit Screenshot showing corrupted project loaded into latest nightly at time of filing SUMMARY When a project is loaded, the association between video and audio clips with the same origin is broken and corrupted. Saving the project makes this corruption permanent. This bug is present in kdenlive-20.07.70-f1def35-x86_64.appimage but not present in kdenlive-19.12.3-x86_64.appimage. DETAILS In the new timeline, video and audio clips have separate tracks, and when a clip is added from a source which has both audio and video, two associated clips are created on the timeline, one audio, one video. The two associated clips are grouped so that they automatically move together, and selecting and editing one also edits the other. When a project is loaded into the latest nightly build (kdenlive-20.07.70-f1def35-x86_64.appimage) the clip groupings don't work, and in some cases clips appear to be grouped with the wrong counterpart clip. STEPS TO REPRODUCE 1. Load an existing project into kdenlive. 2. Select a video clip on the timeline. 3. OBSERVED RESULT The corresponding audio clip is not selected as well, or another nearby audio clip is selected in addition to the video clip. EXPECTED RESULT The corresponding audio clip should also be selected. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The attached screenshot shows a short project created recently, loaded into kdenlive-20.07.70-f1def35-x86_64.appimage. The dark outline on all the clips on the timeline indicates they are not grouped (as they should be), and the single selected video clip is dis-associated from its corresponding audio. This project works correctly when loaded into kdenlive-19.12.3-x86_64.appimage -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 418919] Okular crashes on pdf
https://bugs.kde.org/show_bug.cgi?id=418919 --- Comment #2 from Jose Lello --- Thanks Albert. It is not clear for me if you advise to update the application to a version newer than the one available at my distribution official repository. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384444] Wish: support "remote metadata services" (eg. AI based image tagging like Clarifai.com)
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #6 from Minh Nghia Duong --- Hello Jens, I am not familiar with the Clarifai platform. Could you help me clarify some points, please? Firstly, As in your description, when you import an image to Clarifai, it will return an output with the image tags embedded in metadata of the image itself or just an encoded JSON of tags? And if it's true, is the representation of face tags in metadata is universal to other platforms? And you want a tool to export images to Clarifai or a tool to read the output of clarifai to the images? Nghia. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418506] kdenlive crashes on exit
https://bugs.kde.org/show_bug.cgi?id=418506 andreas.sturmlech...@gmail.com changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED Version Fixed In||20.03.80 Latest Commit|Thank you for reporting: I |78f8880a3d9c1e37548b5146d9f |think it's fixed with this |61f05ab7032ea |commit on master: | |https://invent.kde.org/kde/ | |kdenlive/-/commit/a6bff2f99 | |e3cf3d7adb0ef2aa61f35c74635 | |7e16| --- Comment #10 from andreas.sturmlech...@gmail.com --- Fixed after cherry-picking git commit 78f8880a3d9c1e37548b5146d9f61f05ab7032ea for 19.12.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418973] New: Plasmashell process crashes when clicking on Configure Desktop... option
https://bugs.kde.org/show_bug.cgi?id=418973 Bug ID: 418973 Summary: Plasmashell process crashes when clicking on Configure Desktop... option Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ryu.ketsu...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.80) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.5.7-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I only wanted to change the wallpaper, so I right clicked on the desktop and clicked on Configure Desktop... After that, Plasmashell crashed. I launched plasmashell again several times through Krunner and the result is always the same. Crashing after clicking on Configure Desktop The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1732af2c80 (LWP 10012))] Thread 10 (Thread 0x7f170cffe700 (LWP 11364)): #0 0x7f1733574f99 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f1733576565 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f17335777c3 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #3 0x7f173357822b in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f173357841f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f1734f8dc6b in QEventDispatcherGlib::processEvents (this=0x7f16fc00b3c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f1734f35bfb in QEventLoop::exec (this=this@entry=0x7f170cffdd80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #7 0x7f1734d6062e in QThread::exec (this=this@entry=0x55d757234970) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #8 0x7f17366f76e5 in QQmlThreadPrivate::run (this=0x55d757234970) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/src/qml/qml/ftw/qqmlthread.cpp:155 #9 0x7f1734d616f8 in QThreadPrivate::start (arg=0x55d757234970) at thread/qthread_unix.cpp:342 #10 0x7f1734260efa in start_thread () from /lib64/libpthread.so.0 #11 0x7f17372443bf in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f170700 (LWP 10020)): #0 0x7f1737239acf in poll () from /lib64/libc.so.6 #1 0x7f17335782fe in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f173357841f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1734f8dc6b in QEventDispatcherGlib::processEvents (this=0x7f1704000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f1734f35bfb in QEventLoop::exec (this=this@entry=0x7f170fffed60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f1734d6062e in QThread::exec (this=this@entry=0x55d75559c6c0) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f17369af0e6 in QQuickPixmapReader::run (this=0x55d75559c6c0) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/src/quick/util/qquickpixmapcache.cpp:987 #7 0x7f1734d616f8 in QThreadPrivate::start (arg=0x55d75559c6c0) at thread/qthread_unix.cpp:342 #8 0x7f1734260efa in start_thread () from /lib64/libpthread.so.0 #9 0x7f17372443bf in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f1722280700 (LWP 10019)): #0 0x7f1734267795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f17237c1a5b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f17237c18d7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f1734260efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f17372443bf in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f1722a81700 (LWP 10018)): #0 0x7f1734267795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f17237c1a5b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f17237c18d7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f1734260efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f17372443bf in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f1723282700 (LWP 10017)): #0 0x7f1734267795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f17237c1a5b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f17237c18d7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f1734260efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f17372443bf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f1728add700 (LWP 10016)): #0 0x7f1734267795 in pthread_cond_wait@@GLIBC_2.3.2 () from
[kdeconnect] [Bug 394646] kdeconnect 1.8.2 on android and 1.3.0 on debian do not see each other
https://bugs.kde.org/show_bug.cgi?id=394646 Nicolas Fella changed: What|Removed |Added Resolution|--- |DUPLICATE CC||nicolas.fe...@gmx.de Status|REPORTED|RESOLVED --- Comment #4 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 389010 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389010] devices cannot see eachother
https://bugs.kde.org/show_bug.cgi?id=389010 Nicolas Fella changed: What|Removed |Added CC||eric.vale...@free.fr --- Comment #6 from Nicolas Fella --- *** Bug 394646 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418972] New: Remember Activities when kwin is restarted
https://bugs.kde.org/show_bug.cgi?id=418972 Bug ID: 418972 Summary: Remember Activities when kwin is restarted Product: kwin Version: 5.17.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: a...@laxu.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open some windows on one or more activities. 2. run kwin --replace (or have a kwin crash) OBSERVED RESULT All windows are assigned to "all activities". EXPECTED RESULT The association to activities should be restored. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.62.0 (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 17.08 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401861] Menu search doesn't return any results if cursor happens to be positioned below the tab bar
https://bugs.kde.org/show_bug.cgi?id=401861 Luca Weiss changed: What|Removed |Added CC||l...@z3ntu.xyz -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418542] Program crashes when zooming out
https://bugs.kde.org/show_bug.cgi?id=418542 Jean-Baptiste Mardelle changed: What|Removed |Added CC||j...@kdenlive.org --- Comment #7 from Jean-Baptiste Mardelle --- I cannot reproduce the crash. emohr, you describe a crash with alt+left/right, which triggers seek to next snap point, while original report is about zooming, so it seems like different issues. I cannot reproduce any of these with current git. Can you confirm on latest daily AppImage : https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418960] Layered Images in VMWare
https://bugs.kde.org/show_bug.cgi?id=418960 --- Comment #6 from Vladimir --- Created attachment 126860 --> https://bugs.kde.org/attachment.cgi?id=126860=edit screenfetch_info -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418960] Layered Images in VMWare
https://bugs.kde.org/show_bug.cgi?id=418960 --- Comment #5 from Vladimir --- Created attachment 126859 --> https://bugs.kde.org/attachment.cgi?id=126859=edit bug-1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418960] Layered Images in VMWare
https://bugs.kde.org/show_bug.cgi?id=418960 Vladimir changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Vladimir --- . -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418960] Layered Images in VMWare
https://bugs.kde.org/show_bug.cgi?id=418960 --- Comment #3 from Vladimir --- Created attachment 126858 --> https://bugs.kde.org/attachment.cgi?id=126858=edit layered Images -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 407524] No way to provide keyboard focus to the global drawer
https://bugs.kde.org/show_bug.cgi?id=407524 Vladimir changed: What|Removed |Added OS|Linux |other Version|5.67.0 |5.62.0 Platform|Kubuntu Packages|unspecified -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 407524] No way to provide keyboard focus to the global drawer
https://bugs.kde.org/show_bug.cgi?id=407524 Vladimir changed: What|Removed |Added Platform|Other |Kubuntu Packages Version|5.62.0 |5.67.0 CC||tut30tut...@yandex.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418960] Layered Images in VMWare
https://bugs.kde.org/show_bug.cgi?id=418960 --- Comment #2 from Vladimir --- (In reply to Nicolas Fella from comment #1) > Please report bugs in English, or most of us won't understand it. OK. Interface images are layered on top of each other in the VMWare virtual machine. 1. Manifested by prolonged movement of the cursor with the mouse over objects or a list. 2. It appears during prolonged scrolling of lists, for example, a list of programs for installation. The error occurs regardless of whether VMTools is installed or not. P.S. I can`t edit my first comment. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418960] Layered Images in VMWare
https://bugs.kde.org/show_bug.cgi?id=418960 Vladimir changed: What|Removed |Added Summary|Наслаивается изображение в |Layered Images in VMWare |VMWare | -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418971] New: "Featured" page is almost empty and "Application addons" section is missing in side bar after a flatpak update to be installed while its description page is open
https://bugs.kde.org/show_bug.cgi?id=418971 Bug ID: 418971 Summary: "Featured" page is almost empty and "Application addons" section is missing in side bar after a flatpak update to be installed while its description page is open Product: Discover Version: 5.18.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: bugsefor...@gmx.com CC: aleix...@kde.org Target Milestone: --- Created attachment 126857 --> https://bugs.kde.org/attachment.cgi?id=126857=edit screenshot STEPS TO REPRODUCE 1. open Discover when a flatpak update is available 2. click on the flatpak update listed in "Update" page and click on "More information" button to open its description page 3. click on "Update all" button 4. when updated process is completed, click on Home icon beside the search field OBSERVED RESULT "Featured" page is almost empty (Krita is the only app listed, without its own icon) and "Application addons" section is missing in the side bar. See the attached screenshot. EXPECTED RESULT "Featured" page should list all apps and "Application addons" section should be present in the side bar. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 418970] New: umbrello does not import sequences of C++ comments
https://bugs.kde.org/show_bug.cgi?id=418970 Bug ID: 418970 Summary: umbrello does not import sequences of C++ comments Product: umbrello Version: 2.30.3 (KDE releases 19.12.3) Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- Created attachment 126856 --> https://bugs.kde.org/attachment.cgi?id=126856=edit test header file SUMMARY doxygen describes at http://www.doxygen.nl/manual/docblocks.html a way to document c++ code by using a block of at least two C++ comment lines, where each line starts with an additional slash or an exclamation mark. Here are examples of the two cases: /// /// ... text ... /// or //! //!... text ... //! The documentation from c++ projects, which are using such documentation could not be imported completly into umbrello, because in the recent umbrello imports only the last line. STEPS TO REPRODUCE 1. start umbrello 2. save appended test case to a local file 3. import saved file into umbrello 4. Inspect the documentation of the imported file OBSERVED RESULT The documentation from class comments_class_test1c, comments_class_test1d and comments_class_test1e are incomplete. EXPECTED RESULT The documentation of the mentioned classes should be imported completly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE_Leap_15.1 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418939] Crash when search faces
https://bugs.kde.org/show_bug.cgi?id=418939 --- Comment #9 from caulier.gil...@gmail.com --- Note 7.0.0-bet3 appimage is available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 Alex changed: What|Removed |Added CC||mail.alex.voro...@gmail.com --- Comment #8 from Alex --- The same issue for me. Appears after last update my Manjaro KDE to 5.18.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418939] Crash when search faces
https://bugs.kde.org/show_bug.cgi?id=418939 --- Comment #8 from Maik Qualmann --- You can pass the -debug option to the AppImage to run it in the GDB. I think the crash is related to the large amount of debug output from digiKam. We already know the crash under Ubuntu / Gnome. It probably crashes in the Gnome Shell. Please test the digiKam-7.0.0-Beta3, there the debug output is reduced. Maik -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 385314] Exit Full Screen button needs text, like Kate's button has
https://bugs.kde.org/show_bug.cgi?id=385314
Nate Graham changed:
What|Removed |Added
Version Fixed In||20.04.0
Resolution|--- |FIXED
Status|ASSIGNED|RESOLVED
Latest Commit||https://commits.kde.org/gwe
||nview/435d2ad1b250b81fed19e
||f9b796c97d240ad4875
--- Comment #6 from Nate Graham ---
Git commit 435d2ad1b250b81fed19ef9b796c97d240ad4875 by Nate Graham.
Committed on 17/03/2020 at 19:00.
Pushed by ngraham into branch 'release/20.04'.
Give Exit Full Screen and Configure buttons text and adjust wording
Summary:
Unlike Kate, Gwenview's {nav Exit Full Screen} button is icons-only, impeding
discoverability. This patch shows its action's text, and adjusts that text to
be more
consistent with the typical wording.
In the process, the button below it is also given visible text to avoid making
it look
odd in its layout.
To accomplish this technically, the `FullScreenToolBar` class's `addAction()`
function
is given a new optional parameter for specifying if and where the button's text
should
appear, which is then used to give the aforementioned buttons visible text
according to
the user's toolbutton text display preferences. The actions are also no longer
marked
with the Low Priority status, which forces them to be always icons-only and was
previously redundant since icons-only status was forced in a different way.
Fixed now.
FIXED-IN: 20.04.0
Test Plan: {F8176526}
Reviewers: #gwenview, #vdg, broulik
Reviewed By: broulik
Tags: #gwenview
Differential Revision: https://phabricator.kde.org/D28052
M +5-5app/fullscreencontent.cpp
M +1-2app/mainwindow.cpp
https://commits.kde.org/gwenview/435d2ad1b250b81fed19ef9b796c97d240ad4875
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 417823] Unknown fate of multiple files shared from device to desktop
https://bugs.kde.org/show_bug.cgi?id=417823 Nate Graham changed: What|Removed |Added Summary|Unknown fate of things |Unknown fate of multiple |"shared" from device to |files shared from device to |desktop |desktop --- Comment #5 from Nate Graham --- Turns out that I was using an old version of the host software, and after building everything from source and rebooting for good measure, I can see an "Open" button for the notification for single files. However when I've transferred multiple files, the notification doesn't show an "open containing folder" button like it should. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 416807] Flood of notifications when transferring large number of files
https://bugs.kde.org/show_bug.cgi?id=416807 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Nate Graham --- You're right, I was using an old version. I can see that it works properly with the latest code from git master. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418969] New: Plasmashell crashes when searching with a number
https://bugs.kde.org/show_bug.cgi?id=418969 Bug ID: 418969 Summary: Plasmashell crashes when searching with a number Product: plasmashell Version: master Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: t...@tutanota.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.2) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.7-arch1-1 x86_64 Windowing system: X11 Distribution: EndeavourOS -- Information about the crash: - What I was doing when the application crashed: I was search an application by a number, I typed "1" and then it crashed The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1150c43840 (LWP 1090))] Thread 23 (Thread 0x7f10e8bb4700 (LWP 3127)): #0 0x7f1154716cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f11552d6cb4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f11552d6d92 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1130f6b289 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f1130f6ed1b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f1130f6a47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f1130f6ed71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f1130f6a47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f1130f6ce5c in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f11552d0fc6 in () at /usr/lib/libQt5Core.so.5 #10 0x7f115471046f in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f1154f573d3 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f10e93b5700 (LWP 3126)): #0 0x7f1154716cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f11552d6cb4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f11552d6d92 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1130f6b289 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f1130f6ed1b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f1130f6a47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f1130f6ed71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f1130f6a47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f1130f6ce5c in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f11552d0fc6 in () at /usr/lib/libQt5Core.so.5 #10 0x7f115471046f in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f1154f573d3 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f10e9bb6700 (LWP 3125)): #0 0x7f1154716cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f11552d6cb4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f11552d6d92 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1130f6b289 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f1130f6ed1b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f1130f6a47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f1130f6ed71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f1130f6a47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f1130f6ed71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f1130f6a47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f1130f6ce5c in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f11552d0fc6 in () at /usr/lib/libQt5Core.so.5 #12 0x7f115471046f in start_thread () at /usr/lib/libpthread.so.0 #13 0x7f1154f573d3 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f10ea3b7700 (LWP 3124)): #0 0x7f1154716cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f11552d6cb4 in
[kdevelop] [Bug 418955] kdevelop crashes opening an existing cmake c++ project if gcc-c++ is not installed
https://bugs.kde.org/show_bug.cgi?id=418955 --- Comment #1 from Milian Wolff --- crash within LLVM/clang, maybe it's depending on g++ for the libstdc++? though quite odd that it's crashing... anyhow, not really something we can easily fix in kdevleop I guess? I'll see if I find the time to inspect this by uninstall g++ - maybe there's something we can do to workaround it... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418939] Crash when search faces
https://bugs.kde.org/show_bug.cgi?id=418939 --- Comment #7 from Clon --- Crash also with AppImage https://www.pastefs.com/pid/201482 I don't know how to get debug info from crash because crash of digikam also crash system and it shutsdown. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381674] wl_keyboard::keymap fd is shared and can be modified from any client
https://bugs.kde.org/show_bug.cgi?id=381674 David Edmundson changed: What|Removed |Added Ever confirmed|0 |1 CC||k...@davidedmundson.co.uk Status|REPORTED|ASSIGNED --- Comment #2 from David Edmundson --- Sorry for the delay, thanks for the investigation. https://phabricator.kde.org/D28105 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405111] qwerty instead of azerty
https://bugs.kde.org/show_bug.cgi?id=405111 --- Comment #6 from Philippe ROUBACH --- I experimented some progress with French language. a ... z good but type "&" then "1" is written. kdeconnect 1.4 kde app 19.12.3 plasma 5.18.3 kde frameworks 5.68.0 qt 5.14.1 Samsung S7, android 8.0, kdeconnect 1.13.7 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 418968] New: Network speed in bits per second
https://bugs.kde.org/show_bug.cgi?id=418968 Bug ID: 418968 Summary: Network speed in bits per second Product: ksysguard Version: 5.18.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: paclarushtao...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- We could have the ability to set bits per second as the unit in the network monitoring. STEPS TO REPRODUCE 1. Open Ksysguard 2. Go to "system load" tab or load/create a worksheet with a network monitor. OBSERVED RESULT The network speed is listed in Bytes per second, with no visible option to set it in bits per second. EXPECTED RESULT An option somewhere to set that monitor in bits per second. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418917] System Settings -> Application Style crash
https://bugs.kde.org/show_bug.cgi?id=418917 Alberto Castillo G. changed: What|Removed |Added Platform|unspecified |Archlinux Packages Resolution|WAITINGFORINFO |NOT A BUG --- Comment #2 from Alberto Castillo G. --- As Kai mentioned, running from terminal showed incompatible versions. Rebuilt qt5-styleplugins and now it's working fine. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 418967] New: rarely, randomly mailfilter agent switch to "not ready" mode thus mail are not sent
https://bugs.kde.org/show_bug.cgi?id=418967 Bug ID: 418967 Summary: rarely, randomly mailfilter agent switch to "not ready" mode thus mail are not sent Product: Akonadi Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Mail Filter Agent Assignee: kdepim-b...@kde.org Reporter: philippe.roub...@free.fr Target Milestone: --- SUMMARY rarely, randomly mailfilter agent switch to "not ready" mode thus mail are not sent OBSERVED RESULT you can no more send any mail. They all stay in the outbox. with akonadiconsole you can check that mailfilter agent is not ready. "ready" is not displayed, no state is displayed. restart mailfilter agent then you can again send mail. EXPECTED RESULT you can send any mail. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION openSuse Argon LEAP 15.1 kde app 19.12.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417488] Broken fonts and fuzzy theme previews in multiple system settings
https://bugs.kde.org/show_bug.cgi?id=417488 --- Comment #24 from Mike Simms --- Created attachment 126855 --> https://bugs.kde.org/attachment.cgi?id=126855=edit kdeglobals from affected machine KDE Globals as requested -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418966] kcm_notifications has too much margin in French
https://bugs.kde.org/show_bug.cgi?id=418966 --- Comment #3 from ariasuni --- Created attachment 126854 --> https://bugs.kde.org/attachment.cgi?id=126854=edit kcm layout jumping around Also note that: - When playing with translations (tried to shorten some long ones), the window layout appeared like in 2nd screenshot, before changing back to the one seen in the first screenshot after 1 second or 2 (see gif attachment). - With the broken layout of the French translation, going to the “Choose Custom Position…” or “Applications Settings” screen then going back makes the scrollbar disappear for good, even though I can still scroll So this may be an issue with Kirigami. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418951] The composer breaks down after you unlock the pc
https://bugs.kde.org/show_bug.cgi?id=418951 --- Comment #8 from Vlad Zahorodnii --- Could you please check whether this bug still occurs when "Allow applications to block compositing" in the compositor settings is unchecked? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418966] kcm_notifications has too much margin in French
https://bugs.kde.org/show_bug.cgi?id=418966 --- Comment #1 from ariasuni --- Created attachment 126852 --> https://bugs.kde.org/attachment.cgi?id=126852=edit Widened kcm in French -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418966] kcm_notifications has too much margin in French
https://bugs.kde.org/show_bug.cgi?id=418966 --- Comment #2 from ariasuni --- Created attachment 126853 --> https://bugs.kde.org/attachment.cgi?id=126853=edit kcm in English -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418966] New: kcm_notifications has too much margin in French
https://bugs.kde.org/show_bug.cgi?id=418966 Bug ID: 418966 Summary: kcm_notifications has too much margin in French Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: pe...@hack-libre.org CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 126851 --> https://bugs.kde.org/attachment.cgi?id=126851=edit Screen with default size in French SUMMARY kcm_notifications layout has too much margin in French and looks broken. STEPS TO REPRODUCE Run `env LANG=fr_FR.UTF-8 kcmshell5 kcm_notifications` OBSERVED RESULT EXPECTED RESULT kcm_notifications displays approximately the same in French than in other languages. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418949] plymouth-theme-breeze should have a background/wallpaper option
https://bugs.kde.org/show_bug.cgi?id=418949 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 416807] Flood of notifications when transferring large number of files
https://bugs.kde.org/show_bug.cgi?id=416807 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- We're using a composite job since quite a while for this now, so unless you're running an old version I don't understand why this is happening See https://cgit.kde.org/kdeconnect-kde.git/commit/?id=283d0140597d338210cff62a83c7d72a2e5e368d -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 349564] Add support of face tags group
https://bugs.kde.org/show_bug.cgi?id=349564 Kartik changed: What|Removed |Added CC||kartikx2...@gmail.com --- Comment #2 from Kartik --- Hello Martin, DigiKam 7.0.0 has been released, can you please confirm whether the bug still exists? Can you also please clarify what exactly you mean by tagging a face twice? Does the unconfirmed result after a scan report the same face tag (of the same image) twice under different tags? Thanks Kartik -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417823] Unknown fate of things "shared" from device to desktop
https://bugs.kde.org/show_bug.cgi?id=417823 --- Comment #4 from Nicolas Fella --- The notification not having an open button should be fixed with https://cgit.kde.org/kdeconnect-kde.git/commit/?id=5da0ae7903d69c04dcfb444008494052ff3c -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414913] Connect Deamon closed unexpectedly in Slideshow remote menu
https://bugs.kde.org/show_bug.cgi?id=414913 Nicolas Fella changed: What|Removed |Added Resolution|--- |FIXED CC||nicolas.fe...@gmx.de Status|REPORTED|RESOLVED --- Comment #6 from Nicolas Fella --- This appears to be caused by a QML error in the laser pointer UI. Most likely this is caused by the runtime dependency qml-module-qtquick-particles2 not being installed. I've added indication that this is needed in the build system, but ultimately it's a packaging thing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418951] The composer breaks down after you unlock the pc
https://bugs.kde.org/show_bug.cgi?id=418951 --- Comment #6 from s1r51ck...@gmail.com --- Created attachment 126849 --> https://bugs.kde.org/attachment.cgi?id=126849=edit kwinrc_2 I enclose again kwinrc (kwinrc_2) and qdbus -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418951] The composer breaks down after you unlock the pc
https://bugs.kde.org/show_bug.cgi?id=418951 --- Comment #7 from s1r51ck...@gmail.com --- Created attachment 126850 --> https://bugs.kde.org/attachment.cgi?id=126850=edit Qdbus_log -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417340] QtQuick Particles not marked as runtime dependency
https://bugs.kde.org/show_bug.cgi?id=417340 Nicolas Fella changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||kdeconnect-kde/commit/48304 ||7f590b7fd5c9d6f270aaa0c6778 ||a3666c9d Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Nicolas Fella --- Git commit 483047f590b7fd5c9d6f270aaa0c6778a3666c9d by Nicolas Fella. Committed on 17/03/2020 at 16:13. Pushed by nicolasfella into branch 'release/20.04'. Mark QtQuick.Particles as runtime dependency M +1-0CMakeLists.txt https://invent.kde.org/kde/kdeconnect-kde/commit/483047f590b7fd5c9d6f270aaa0c6778a3666c9d -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||https://phabricator.kde.org ||/R241:213ed50634c02d8ec4aa9 ||1f0c307cfdd6f78170d Resolution|--- |FIXED Latest Commit||5.68 -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 407975] Ensure correct permissions when trying to create a share of a folder in the user's homedir
https://bugs.kde.org/show_bug.cgi?id=407975 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org --- Comment #1 from Harald Sitter --- This is a bit more involved than what is described: To traverse any directory the user (that is the user logged into the samba share) needs to have +x on all parenting directories of the folder they are trying to navigate. That isn't specific to home, nor is it specifically about the home directory. Namely whenever a share is created we should actually walk up the dir tree and +x on all directories. And that +x is also a bit tricky because either you set all +x or you figure out which +x needs setting (in POSIX ACL or mode, as available and applicable). I am not sure what the security implications of +x exactly are, but forcing +x on everything seems a bit questionable. Windows fundamentally has the same problem btw, and they've made a share wizard to deal with this. Because in the end this is just one example of the eternal conflict ShareACL != FileSystemACL. I.e. just because you give a user access on a share level doesn't mean they have access on a file system level. So with their wizard you just say userX should have RW access and userY should have R access. The wizard then bends both types of ACLs into place all the way up the directory tree so they meet the expected outcome. I feel like that may be where we should go too. Advanced users on the other hand could totally avoid the wizard and instead fiddle with the ACLs and have constructs like fullcontrol for everyone on a share level but then restrict effective access via the file system (that is actually how windows wizard shares work I think; they share the top most directory and then adjust NTFS permissions below that). -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 418965] New: Translation memory creation not working (English->Slovak)
https://bugs.kde.org/show_bug.cgi?id=418965 Bug ID: 418965 Summary: Translation memory creation not working (English->Slovak) Product: lokalize Version: 19.12 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: translation memory Assignee: sdepi...@gmail.com Reporter: prescot...@gmail.com CC: sha...@ukr.net Target Milestone: --- For slovak language there is default source language set to "en_US" and target language to "sk_SK". With these settings i get no pairs to translation memory. Solution is to remove existing TM and create new with: Source language: "en_US" Target language: "sk" Conclusion: I think this situation can be fixed, with replacing target language by default from "sk_SK" to "sk" -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 417108] Command line operation fails
https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #12 from David Jarvie --- I suspect that the QObject::disconnect errors probably come from inside QCommandLineParser rather than KAlarm itself, although I can't be sure. Certainly, there isn't any obvious place in KAlarm where a set of four such errors could be generated together. I've looked at your recordings, and tried running the same scripts (also on a Neon system), but I have been unable to reproduce the errors which you have seen. The command "kalarm -v" doesn't produce the error for me either. So there must be some difference between our systems which is causing the different results - one possibility is because I'm running a slightly older version of Qt. Unfortunately, until I'm able to update my Neon system (which will mess up my current development setup), it's difficult to know how I can investigate this further, and given that you are not a developer, I can't think of how you could help either. I'll look at this again once I do update my system. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415425] kde connect slideshow remote crashed
https://bugs.kde.org/show_bug.cgi?id=415425 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #5 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 414913 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 418076] KDE Connect Slideshow Remote Pointer bug
https://bugs.kde.org/show_bug.cgi?id=418076 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 414913 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414913] Connect Deamon closed unexpectedly in Slideshow remote menu
https://bugs.kde.org/show_bug.cgi?id=414913 Nicolas Fella changed: What|Removed |Added CC||philipp.jacob.neumann@gmail ||.com --- Comment #5 from Nicolas Fella --- *** Bug 415425 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414913] Connect Deamon closed unexpectedly in Slideshow remote menu
https://bugs.kde.org/show_bug.cgi?id=414913 Nicolas Fella changed: What|Removed |Added CC||albertodurmie...@yahoo.com --- Comment #4 from Nicolas Fella --- *** Bug 418076 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418939] Crash when search faces
https://bugs.kde.org/show_bug.cgi?id=418939 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #6 from caulier.gil...@gmail.com --- No, all is fine from you side. Thread 1 "digikam" hit Catchpoint 1 (exception thrown), 0x73988d1d in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) bt #0 0x73988d1d in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x7fffef7c4411 in Exiv2::ExifKey::Impl::decomposeKey(std::__cxx11::basic_string, std::allocator > const&) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #2 0x7fffef7c44cc in Exiv2::ExifKey::ExifKey(std::__cxx11::basic_string, std::allocator > const&) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #3 0x766eff28 in Digikam::MetaEngine::getExifTagString(char const*, bool) const () from /usr/lib/digikam/libdigikamcore.so.5.6.0 #4 0x76715576 in Digikam::DMetadata::getExifTagStringFromTagsList(QStringList const&) const () from /usr/lib/digikam/libdigikamcore.so.5.6.0 #5 0x767163ae in Digikam::DMetadata::getPhotographInformation() const () from /usr/lib/digikam/libdigikamcore.so.5.6.0 #6 0x768d2c2c in Digikam::ImagePropertiesSideBar::setImagePropertiesInformation(QUrl const&) () from /usr/lib/digikam/libdigikamcore.so.5.6.0 #7 0x775d7514 in ?? () from /usr/lib/digikam/libdigikamgui.so.5.6.0 #8 0x775d4ef5 in ?? () from /usr/lib/digikam/libdigikamgui.so.5.6.0 #9 0x775d4fc6 in ?? () from /usr/lib/digikam/libdigikamgui.so.5.6.0 #10 0x7759abd7 in ?? () from /usr/lib/digikam/libdigikamgui.so.5.6.0 #11 0x775b0e11 in ?? () from /usr/lib/digikam/libdigikamgui.so.5.6.0 #12 0x7430c555 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ---Type to continue, or q to quit---Quit (gdb) In fact it's Exiv2 from your system which crash when library analyze image metadata contents. You use certainly an older Exiv2 version. This component is sensible in digiKam and used everywhere to population the database. As Maik said, we recommend to try with digiKam official AppImage linux bundle which use the last Exiv2 version inside. Just donwload the AppImage digiKam file, make it executable and run it as well. https://www.digikam.org/download/ Thanks in advance... Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418939] Crash when search faces
https://bugs.kde.org/show_bug.cgi?id=418939 caulier.gil...@gmail.com changed: What|Removed |Added Component|Faces-Recognition |Metadata-Engine -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 418521] Translation bug: Turkish
https://bugs.kde.org/show_bug.cgi?id=418521 Nicolas Fella changed: What|Removed |Added Assignee|albertv...@gmail.com|gor...@gelecek.com.tr Component|android-application |tr CC||nicolas.fe...@gmx.de Product|kdeconnect |i18n --- Comment #1 from Nicolas Fella --- Reassigning to the translation team -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 418761] Muting notifications
https://bugs.kde.org/show_bug.cgi?id=418761 Nicolas Fella changed: What|Removed |Added Status|REPORTED|RESOLVED CC||nicolas.fe...@gmx.de Resolution|--- |DUPLICATE --- Comment #1 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 404043 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 404043] feature request: silence notifications from mobile phone for fixed time
https://bugs.kde.org/show_bug.cgi?id=404043 Nicolas Fella changed: What|Removed |Added CC||steven...@gmail.com --- Comment #1 from Nicolas Fella --- *** Bug 418761 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418791] Middle click not registering on first button of Wacom Pen
https://bugs.kde.org/show_bug.cgi?id=418791 --- Comment #2 from Sonia --- Hi, the middle button just never worked in the end. I reassigned ctrl left click and it worked...so its working now. Thank you for getting back to me! On Tue, Mar 17, 2020 at 4:53 AM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=418791 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC||b...@valdyas.org > > --- Comment #1 from Boudewijn Rempt --- > If it used to work and now suddenly doesn't work without having updated > Krita > it must be something else... > > Did you update Krita, the Wacom driver or did you get a Windows update? > > Could you try to reset Krita's settings and the Wacom driver settings and > try > again? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 418954] remote keyboard doesn't work properly when host PC uses Russian keyboard layout
https://bugs.kde.org/show_bug.cgi?id=418954 Nicolas Fella changed: What|Removed |Added Resolution|--- |DUPLICATE CC||nicolas.fe...@gmx.de Status|REPORTED|RESOLVED --- Comment #1 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 405111 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405111] qwerty instead of azerty
https://bugs.kde.org/show_bug.cgi?id=405111 Nicolas Fella changed: What|Removed |Added CC||l...@royal.net --- Comment #5 from Nicolas Fella --- *** Bug 418954 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405111] qwerty instead of azerty
https://bugs.kde.org/show_bug.cgi?id=405111 --- Comment #4 from Nicolas Fella --- That's odd since there was no relevant code change and I can still reproduce. This appears to be a generic problem with non-english layouts on the PC. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418939] Crash when search faces
https://bugs.kde.org/show_bug.cgi?id=418939 --- Comment #5 from Clon --- When run with GDB, it even doesnt start. I suspect that I am doing something wrong. https://hastebin.com/wapajimufe.coffeescript -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 412779] Test for and try to fix a lack of FUSE availability
https://bugs.kde.org/show_bug.cgi?id=412779 Ivan Čukić changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-vault/1e2988d7d3ca68f9f ||f00e576c634aff4fe5b8b32 Resolution|--- |FIXED --- Comment #3 from Ivan Čukić --- Git commit 1e2988d7d3ca68f9ff00e576c634aff4fe5b8b32 by Ivan Čukić. Committed on 17/03/2020 at 14:35. Pushed by ivan into branch 'master'. Show command output on unknown failure Summary: If the error is unknown (all errors in encfs), show the 'details...' button which shows the command line output to the user when activated. Reviewers: #plasma, davidedmundson, ngraham, mart Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28099 M +2-0.gitignore M +2-1kded/engine/backends/cryfs/cryfsbackend.cpp M +13 -1kded/engine/commandresult.cpp M +9-4kded/engine/commandresult.h M +2-1kded/engine/fusebackend_p.cpp M +35 -4kded/ui/mountdialog.cpp M +5-0kded/ui/mountdialog.h https://commits.kde.org/plasma-vault/1e2988d7d3ca68f9ff00e576c634aff4fe5b8b32 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395449] Show used tool and/or brush in undo history entries
https://bugs.kde.org/show_bug.cgi?id=395449 Igor changed: What|Removed |Added CC||igortechnicalm...@gmail.com --- Comment #1 from Igor --- Vote for the feature. And link to discussion https://krita-artists.org/t/exact-name-of-brush-presets-in-the-undo-history/4350/4 -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 418490] Kexi form navigation bar not visible on new Manjaro installation
https://bugs.kde.org/show_bug.cgi?id=418490 --- Comment #9 from Jarosław Staniek --- Ian, Glad the Discover works for you. It can be used instead of the command line. For people who want the command line, I also fixed the instructions from the https://community.kde.org/Kexi/Snapshots#Linux page. The flatpak command in question should be now: flatpak remote-add --if-not-exists kde https://distribute.kde.org/kdeapps.flatpakrepo Regarding the connections list, it is your personal data residing in your $HOME directory so it was found and used at KEXI startup just fine. Such information is never uninstalled when you upgrade or uninstall KEXI. Fairy standard behavior of apps. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414755] Status logging on mobile
https://bugs.kde.org/show_bug.cgi?id=414755 --- Comment #2 from Kodiak --- Hi Nicholas Fella, Having any ability to see status would be helpful to me in the following circumstances: - Debugging issues from mobile device - Observe status of long transfers or any other long-running operations Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414755] Status logging on mobile
https://bugs.kde.org/show_bug.cgi?id=414755 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- How would it be useful? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418964] New: The Microsoft Store version is missing ".log" file association.
https://bugs.kde.org/show_bug.cgi?id=418964 Bug ID: 418964 Summary: The Microsoft Store version is missing ".log" file association. Product: kate Version: 19.12.2 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: kovacs.artur.barna...@gmail.com Target Milestone: --- SUMMARY Kate downloaded from the Microsoft Store does not register itself to support the ".log" fileformat. This prevents the user from associating this format with Kate without empolying a hacky workaround like manually adding the format to the registry. (See https://superuser.com/questions/1071323/cannot-set-a-windows-10-store-app-as-default-program-to-open-a-file) STEPS TO REPRODUCE 1. Install Kate from the Microsoft Store 2. Try to open a ".log" file with Kate. OBSERVED RESULT Cannot do it without hacking. EXPECTED RESULT The format is either automatically associated with Kate upon installing or the "Open with / Choose another app" window offers to use Kate. SOFTWARE/OS VERSIONS Windows: 10 KDE Frameworks Version: 5.67.0 Qt Version: Qt 5.14.0 (built against 5.14.0) -- You are receiving this mail because: You are watching all bug changes.
