[phonon-backend-gstreamer] [Bug 377318] MP3 files with a % symbol in file name do not play in preview pane
https://bugs.kde.org/show_bug.cgi?id=377318 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org, ||tdfisc...@kde.org Product|Phonon |phonon-backend-gstreamer Assignee|sit...@kde.org |dvra...@kde.org Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 377189] Crashed on reboot after updating lots of software
https://bugs.kde.org/show_bug.cgi?id=377189 --- Comment #2 from Jeffrey Reagan --- Thank you. --Jeff On Mar 5, 2017 7:16 PM, "Christoph Feck" wrote: > https://bugs.kde.org/show_bug.cgi?id=377189 > > Christoph Feck changed: > >What|Removed |Added > > > Resolution|--- |DOWNSTREAM > Status|UNCONFIRMED |RESOLVED > > --- Comment #1 from Christoph Feck --- > Crash is in DLL library loader. If you see this crash after a reboot, > please > report this bug to the bug tracker of your distribution. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 370968] can't remove position and zoom effect from clip
https://bugs.kde.org/show_bug.cgi?id=370968 Vincent PINON changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |NEEDSINFO --- Comment #2 from Vincent PINON --- Sorry for the long delay, I've just tested your project with Kdenlive 16.12.2 and could remove the effect without problem. Could you try again after an upgrade on your side? Thanks, Vincent -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 363465] kdenlive-git GPU mirror effect has only 1 preset (not configurable). Please make it like CPU Mirror
https://bugs.kde.org/show_bug.cgi?id=363465 Vincent PINON changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Vincent PINON --- Sorry but Movit filter is only X flip. We can't expose parameters that don't exist :( Please report to Movit author. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377366] New: Plasma crashed after being idle for 16 hours
https://bugs.kde.org/show_bug.cgi?id=377366 Bug ID: 377366 Summary: Plasma crashed after being idle for 16 hours Product: plasmashell Version: 5.9.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: acoso...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.3) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.4.0-65-generic x86_64 Distribution: KDE neon User Edition 5.9 -- Information about the crash: - What I was doing when the application crashed: Everything was perfect yesterday, left my office as usual. Logged in, noticed very slow behavior, started closing applications - Unusual behavior I noticed: Very slow behavior, when I tried top with CTRL+ALT+2 logged in typed top, did not notice anything eating-up CPU - Custom settings of the application: Had Crhome with multiple tabs opened, had virtualbox and had atom editor. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2b65f9d8c0 (LWP 2013))] Thread 17 (Thread 0x7f2a725a6700 (LWP 18964)): #0 0x7f2b5c0c4a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2b5c08034e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2b5c08049c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2b611fa75b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2b611a50ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2b60fd4f64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2b63606bf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f2b60fd9b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2b5fe7f6ba in start_thread (arg=0x7f2a725a6700) at pthread_create.c:333 #9 0x7f2b608e682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f2a73fff700 (LWP 3773)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2b60fda9fb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f2aaa7e407f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7f2aaa7e8078 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f2aaa7e326d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f2aaa7e5bf0 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f2b60fd9b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2b5fe7f6ba in start_thread (arg=0x7f2a73fff700) at pthread_create.c:333 #8 0x7f2b608e682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f2a88d4a700 (LWP 3772)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2b60fda9fb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f2aaa7e407f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7f2aaa7e8078 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f2aaa7e326d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f2aaa7e80d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f2aaa7e326d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f2aaa7e5bf0 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f2b60fd9b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f2b5fe7f6ba in start_thread (arg=0x7f2a88d4a700) at pthread_create.c:333 #10 0x7f2b608e682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f2a8954b700 (LWP 3771)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2b60fda9fb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f2aaa7e407f in ThreadWeaver::Weaver::takeFirstAvailabl
[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.
https://bugs.kde.org/show_bug.cgi?id=377006 --- Comment #7 from zephyrus00jp --- To avoid the uncertainty about how mozilla thunderbird is compiled for valgrind testing, I will create a binary (for valgrind testing) on mozilla's tryserver. (You an see that what patches are applied via the web interface.) I figure it would be easier this way after I thought about detailing the manual procedure to compile comm-central thunderbird under linux for valgrind, etc. There are some patches, etc. that have to be applied using MERCURIUM hg command, and other steps. Having a visible binary which has undergone standard testing is much better. Unfortunately, the build is currently busted on the tryserver due to a very recent change in the code that is part of mozilla firefox which thunderbird shares. I hope it will be fixed in a few days. Then I can create a binary on the tryserver which can be used for testing this issue under linux. TIA -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377343] German translation does not one hundred percent translate
https://bugs.kde.org/show_bug.cgi?id=377343 Burkhard Lueck changed: What|Removed |Added CC||lu...@hube-lueck.de --- Comment #1 from Burkhard Lueck --- Version 16.04.3 KDE Frameworks 5.28.0 Qt 5.6.1 Ubuntu 16.04.2 LTS The menu items shown in your screenshots are translated -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 375370] Unable to remove a folder from excludeFolders list
https://bugs.kde.org/show_bug.cgi?id=375370 --- Comment #2 from S. Christian Collins --- This happens on my system as well, with both of my mounted NTFS drives showing up on the exclude list. I am running KDE Neon 5.9.3 64-bit (Plasma Desktop 5.9.3, KDE Frameworks 5.31.0, Qt 5.7.1). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 375370] Unable to remove a folder from excludeFolders list
https://bugs.kde.org/show_bug.cgi?id=375370 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377240] Deleting an image (DEL key) within LightTable resets zoom factor for following image
https://bugs.kde.org/show_bug.cgi?id=377240 --- Comment #2 from Jens --- Wow, that was fast. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 377365] New: krunner crashed when multiplying 2 numbers
https://bugs.kde.org/show_bug.cgi?id=377365 Bug ID: 377365 Summary: krunner crashed when multiplying 2 numbers Product: krunner Version: 5.9.2 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: ricardo.barbe...@gmail.com Target Milestone: --- Application: krunner (5.9.2) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.4.38 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: - What I was doing when the application crashed: I was just trying to multiply 2 numbers (1252*16) and krunner crashed. I guess Dr. Konqi (first time using it!) is going to attach a traceback, hope it's useful :) The crash can be reproduced sometimes. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8661f27c0 (LWP 1989))] Thread 13 (Thread 0x7fb81f738700 (LWP 31767)): #0 0x7fb85cbc136f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb833e045b4 in () at /usr/lib64/libQt5Script.so.5 #2 0x7fb833e045f9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fb85cbbb684 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb860c78efd in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fb825ffb700 (LWP 2285)): #0 0x7fb85cbc136f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb86187fdfb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb83ef7f917 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fb83ef83628 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fb83ef7eb79 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fb83ef83672 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fb83ef7eb79 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fb83ef813ff in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fb86187f069 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fb85cbbb684 in start_thread () at /lib64/libpthread.so.0 #10 0x7fb860c78efd in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fb8267fc700 (LWP 2284)): #0 0x7fb85cbc136f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb86187fdfb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb83ef7f917 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fb83ef83628 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fb83ef7eb79 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fb83ef83672 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fb83ef7eb79 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fb83ef813ff in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fb86187f069 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fb85cbbb684 in start_thread () at /lib64/libpthread.so.0 #10 0x7fb860c78efd in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fb826ffd700 (LWP 2283)): #0 0x7fb85cbc136f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb86187fdfb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb83ef7f917 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fb83ef83628 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fb83ef7eb79 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fb83ef83672 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fb83ef7eb79 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fb83ef813ff in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fb86187f069 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fb85cbbb684 in start_thread () at /lib64/libpthread.so.0 #10 0x7fb860c78efd in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fb8277fe700 (LWP 2282)): #0 0x7fb85cbc136f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb86187fdfb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5
[krita] [Bug 377364] New: Kirta 3.1.2. crashes upon opening new document
https://bugs.kde.org/show_bug.cgi?id=377364 Bug ID: 377364 Summary: Kirta 3.1.2. crashes upon opening new document Product: krita Version: 3.1.2 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: replicajes...@gmail.com Target Milestone: --- This is NOT about brushes, but I can't find Kirta in the list of products to report on. Having an unknown problem, just tried to upgrade from 2.9.1.1 to 3.1.2, but it keeps crashing as soon as i try to start a new document, which I need to. I've tried 64 bit and 32 bit, both do the same. I've tried running it as Admin, tried all sizes of new documents to open, i have Win 8.1, and version 2.9.1.1 worked fine. But now Kirta only crashes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377363] New: Kirta 3.1.2. crashes upon opening new document
https://bugs.kde.org/show_bug.cgi?id=377363 Bug ID: 377363 Summary: Kirta 3.1.2. crashes upon opening new document Product: krita Version: 3.1.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: replicajes...@gmail.com Target Milestone: --- This is NOT about brushes, but I can't find Kirta in the list of products to report on. Having an unknown problem, just tried to upgrade from 2.9.1.1 to 3.1.2, but it keeps crashing as soon as i try to start a new document, which I need to. I've tried 64 bit and 32 bit, both do the same. I've tried running it as Admin, tried all sizes of new documents to open, i have Win 8.1, and version 2.9.1.1 worked fine. But now Kirta only crashes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 372418] Have notifications / notification icons show on the users lock screen
https://bugs.kde.org/show_bug.cgi?id=372418 --- Comment #3 from Martin Klapetek --- Not yet as far as I'm aware, notifications are a whole different league of problems. Media controls are kinda simple in contrast to that. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 370745] Title clips after changing project frames
https://bugs.kde.org/show_bug.cgi?id=370745 David Moore changed: What|Removed |Added CC||davidmoore0...@gmail.com --- Comment #3 from David Moore --- hope you can fix this soon. faced this when editing a promo video for http://glasvezelvergelijken.org/. i think it was fine in previous version, wasn't it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377362] New: KDE crashed when closing Okular
https://bugs.kde.org/show_bug.cgi?id=377362 Bug ID: 377362 Summary: KDE crashed when closing Okular Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: luighi...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.49-16-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I was usign Okular and when I tried to close all the windows of this program, suddenly the KDE plasma crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8fc991c900 (LWP 2187))] Thread 27 (Thread 0x7f4e9700 (LWP 2613)): #0 0x7f8fc303751d in read () at /lib64/libc.so.6 #1 0x7f8fbf743670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8fbf702e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8fbf7032a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8fbf70342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8fc394232b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8fc38effdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f8fc372af1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f8fc372f9e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f8fc2844734 in start_thread () at /lib64/libpthread.so.0 #10 0x7f8fc3043d3d in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f8eb0bdc700 (LWP 2555)): #0 0x7f8fb862e2c4 in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #1 0x7f8fb862eba2 in pa_fdsem_before_poll () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #2 0x7f8fb8646857 in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #3 0x7f8fb8cb0a14 in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0 #4 0x7f8fb8cb0dea in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #5 0x7f8fb8cb0e90 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #6 0x7f8fb8cbf006 in () at /usr/lib64/libpulse.so.0 #7 0x7f8fb8656408 in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #8 0x7f8fc2844734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8fc3043d3d in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f8ef4fdc700 (LWP 2554)): #0 0x7f8fc303b49d in poll () at /lib64/libc.so.6 #1 0x7f8fbf703314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8fbf70342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8fc394232b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8fc38effdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8fc372af1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8fc6a379c8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f8fc372f9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f8fc2844734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8fc3043d3d in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f8eb2ffd700 (LWP 2437)): #0 0x7f8fc28490af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8fc373065b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8f0a5bf42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f8f0a5c2dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f8f0a5bd45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f8f0a5c0a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f8fc372f9e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f8fc2844734 in start_thread () at /lib64/libpthread.so.0 #8 0x7f8fc3043d3d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f8eb37fe700 (LWP 2436)): #0 0x7f8fc28490af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8fc373065b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8f0a5bf42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f8f0a5c2dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f8f0a5bd45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f8f0a5c2e32 in () at /usr/lib64/li
[konsole] [Bug 375540] Seg fault on startup
https://bugs.kde.org/show_bug.cgi?id=375540 Orivej Desh changed: What|Removed |Added CC||ori...@gmx.fr --- Comment #7 from Orivej Desh --- Created attachment 104445 --> https://bugs.kde.org/attachment.cgi?id=104445&action=edit backtrace with some debuginfo I encountered the same bug after upgrading Konsole from the version that used ~/.kde/share/apps/konsole/konsoleui.rc to 16.12.2. I collected the traceback with some debuginfo (attached), noticed container = 0x0, recompiled with the following patch, and the konsole succesfully launched and allowed me to delete conflicting keybindings in the settings. After that I was unable to reproduce the bug, even by deleting ~/.local/share/kxmlgui5/konsole/konsoleui.rc. diff --git a/src/ViewManager.cpp b/src/ViewManager.cpp index c187e64..b656ef2 100644 --- a/src/ViewManager.cpp +++ b/src/ViewManager.cpp @@ -904,6 +904,8 @@ void ViewManager::saveSessions(KConfigGroup& group) // first: sessions in the active container, preserving the order ViewContainer* container = _viewSplitter->activeContainer(); +if (!container) { + return; +} -Q_ASSERT(container); TerminalDisplay* activeview = qobject_cast(container->activeView()); -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367831] chinese word render error
https://bugs.kde.org/show_bug.cgi?id=367831 --- Comment #6 from TOM Harrison --- Same font on gnome has no this kind of error. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377361] New: Moving a file to root-owned NTFS drive crashes dolphin
https://bugs.kde.org/show_bug.cgi?id=377361 Bug ID: 377361 Summary: Moving a file to root-owned NTFS drive crashes dolphin Product: dolphin Version: 16.08.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jingyu9...@hotmail.com Target Milestone: --- Application: dolphin (16.08.2) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.49-16-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: An NTFS drive is mounted on /mnt/E with fstab parameters: users,uid=root,gid=users,fmask=111,dmask=000,locale=zh_CN.UTF-8 therefore the files and directories are world writable. When I move (not copy) a file from desktop or home to /mnt/E, the file is successfully written, but a dialog says (translated from zh_CN) "Access denied for /mnt/E/filename", with buttons "Retry", "Cancel", and "Skip", "Auto Skip" in case of multiple files. If I click "Cancel" for one file, the dialog will disappear and the file is moved. However if I click "Retry", or click "Skip" for multiple files, dolphin will crash and may leave the destination file corrupted. Modifying the fstab parameter "uid=root" to "uid=myusername" can workaround the problem, but only useful for a single user. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd1e90c2900 (LWP 2936))] Thread 5 (Thread 0x7fd13d372700 (LWP 2940)): #0 0x7fd1e897949d in poll () at /lib64/libc.so.6 #1 0x7fd1dd766314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd1dd76642c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd1e2c5432b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd1e2c01fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd1e2a3cf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fd1e2a419e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fd1de2ed734 in start_thread () at /lib64/libpthread.so.0 #8 0x7fd1e8981d3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fd1bf002700 (LWP 2939)): #0 0x7fd1de2f20af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd1bf17693b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fd1bf176969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fd1de2ed734 in start_thread () at /lib64/libpthread.so.0 #4 0x7fd1e8981d3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fd1cbbcd700 (LWP 2938)): #0 0x7fd1e897949d in poll () at /lib64/libc.so.6 #1 0x7fd1dd766314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd1dd76642c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd1e2c5432b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd1e2c01fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd1e2a3cf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fd1e30681d5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7fd1e2a419e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fd1de2ed734 in start_thread () at /lib64/libpthread.so.0 #9 0x7fd1e8981d3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fd1d16c7700 (LWP 2937)): #0 0x7fd1e897949d in poll () at /lib64/libc.so.6 #1 0x7fd1db7203e2 in () at /usr/lib64/libxcb.so.1 #2 0x7fd1db721fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fd1d3c21839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fd1e2a419e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd1de2ed734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd1e8981d3d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fd1e90c2900 (LWP 2936)): [KCrash Handler] #6 0x7fd1e2c35847 in QObjectPrivate::setParent_helper(QObject*) () at /usr/lib64/libQt5Core.so.5 #7 0x7fd1e47af08f in KCompositeJob::removeSubjob(KJob*) () at /usr/lib64/libKF5CoreAddons.so.5 #8 0x7fd1e6a28625 in () at /usr/lib64/libKF5KIOCore.so.5 #9 0x7fd1e6a28df7 in () at /usr/lib64/libKF5KIOCore.so.5 #10 0x7fd1e6a2ae8a in KIO::CopyJob::slotResult(KJob*) () at /usr/lib64/libKF5KIOCore.so.5 #11 0x7fd1e2c2dbb1 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #12 0x7fd1e47afa62 in KJob::result(KJob*, KJob::QPrivateSignal) () at /usr/lib64/libKF5CoreAddons.so.5 #13 0x7fd1e47b078f in KJob::finishJob(bool) () at /usr/lib64/libKF5CoreAddons.so.5 #14 0x7fd1e6a5dadc in KIO::FileCopyJob::slotResult(KJob*) () at /usr/lib64/libKF5KIOCore.so.5 #15 0x7fd1e6a5ee60 in () at /usr/lib64/
[plasmashell] [Bug 367831] chinese word render error
https://bugs.kde.org/show_bug.cgi?id=367831 --- Comment #5 from TOM Harrison --- OK, I found it. Noto Sans CJK and Noto Sans Mono CJK can not use in KDE5. it will generate weird font. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 372418] Have notifications / notification icons show on the users lock screen
https://bugs.kde.org/show_bug.cgi?id=372418 --- Comment #2 from Daniel --- I saw this blog post from Kai: http://blog.broulik.de/2017/03/whats-up-for-5-10/ Notably, "Media Controls on the Lock Screen". Does this mean that notifications will also be on the lockscreen too, if something advanced like media controls is on there? -- You are receiving this mail because: You are watching all bug changes.
[klettres] [Bug 377360] New: Arabic language audio loading error
https://bugs.kde.org/show_bug.cgi?id=377360 Bug ID: 377360 Summary: Arabic language audio loading error Product: klettres Version: 2.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: an...@kde.org Reporter: freeman.aka.ah...@gmail.com Target Milestone: --- Created attachment 10 --> https://bugs.kde.org/attachment.cgi?id=10&action=edit Screenshot 1. Run KLetters 2. Load arabic language 3. Select level 3 or 4 Program will work, but displays error message, please see attachment. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 377359] New: Clicking on File menu item crashes kontact
https://bugs.kde.org/show_bug.cgi?id=377359 Bug ID: 377359 Summary: Clicking on File menu item crashes kontact Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sgr...@redhat.com Target Milestone: --- Application: kontact (5.3.3 (QtWebEngine)) Qt Version: 5.6.2 Frameworks Version: 5.31.0 Operating System: Linux 4.9.13-100.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I just started kontact. I simply clicked on the File menu item and it crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff448260940 (LWP 2840))] Thread 24 (Thread 0x7ff33cb9f700 (LWP 2875)): #0 0x7ff457616bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff45b793959 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7ff45b794020 in base::SequencedWorkerPool::Worker::Run() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7ff45b7941f0 in base::SimpleThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7ff45b790c2d in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7ff4576115ca in start_thread () at /lib64/libpthread.so.0 #6 0x7ff45eea10ed in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7ff33d3a0700 (LWP 2874)): #0 0x7ff457616bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff45b793959 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7ff45b794020 in base::SequencedWorkerPool::Worker::Run() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7ff45b7941f0 in base::SimpleThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7ff45b790c2d in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7ff4576115ca in start_thread () at /lib64/libpthread.so.0 #6 0x7ff45eea10ed in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7ff3ec953700 (LWP 2870)): #0 0x7ff457616bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff44a3661a4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7ff44a3661e9 in () at /lib64/libQt5Script.so.5 #3 0x7ff4576115ca in start_thread () at /lib64/libpthread.so.0 #4 0x7ff45eea10ed in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7ff3ed8ec700 (LWP 2863)): #0 0x7ff457616bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff45b6a37c0 in mojo::system::Waiter::Wait(unsigned long, unsigned int*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7ff45b68f39c in mojo::system::Core::WaitManyInternal(unsigned int const*, unsigned int const*, unsigned int, unsigned long, unsigned int*, mojo::system::HandleSignalsState*) () at /lib64/libQt5WebEngineCore.so.5 #3 0x7ff45b68f89c in mojo::system::Core::WaitMany(mojo::system::UserPointer, mojo::system::UserPointer, unsigned int, unsigned long, mojo::system::UserPointer, mojo::system::UserPointer) () at /lib64/libQt5WebEngineCore.so.5 #4 0x7ff45b68bcf5 in MojoWaitMany () at /lib64/libQt5WebEngineCore.so.5 #5 0x7ff45cd02c47 in mojo::common::MessagePumpMojo::DoInternalWork(mojo::common::MessagePumpMojo::RunState const&, bool) () at /lib64/libQt5WebEngineCore.so.5 #6 0x7ff45cd02e7e in mojo::common::MessagePumpMojo::DoRunLoop(mojo::common::MessagePumpMojo::RunState*, base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5 #7 0x7ff45cd02fb9 in mojo::common::MessagePumpMojo::Run(base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5 #8 0x7ff45b77bca4 in base::RunLoop::Run() () at /lib64/libQt5WebEngineCore.so.5 #9 0x7ff45b766ae5 in base::MessageLoop::Run() () at /lib64/libQt5WebEngineCore.so.5 #10 0x7ff45b7946e6 in base::Thread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #11 0x7ff45b790c2d in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #12 0x7ff4576115ca in start_thread () at /lib64/libpthread.so.0 #13 0x7ff45eea10ed in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7ff3ee0ed700 (LWP 2862)): #0 0x7ff457616bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff45b793959 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7ff45b794020 in base::SequencedWorkerPool::Worker::Run() () at /lib64/libQt5WebEngineCore.
[okular] [Bug 363776] Text selection begins prematurely following change to tool
https://bugs.kde.org/show_bug.cgi?id=363776 --- Comment #8 from Jonathan --- Comment on attachment 104443 --> https://bugs.kde.org/attachment.cgi?id=104443 Alberts patch to fix the problem Sure that is a simple and effective solution to this bug. However it does nothing for two identified inconsistencies: 1. annotation context menus appearing on mouse-press instead of mouse-release; and 2. differing responses in different modes for no good reason to right-click. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 363776] Text selection begins prematurely following change to tool
https://bugs.kde.org/show_bug.cgi?id=363776 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #7 from Albert Astals Cid --- Created attachment 104443 --> https://bugs.kde.org/attachment.cgi?id=104443&action=edit Alberts patch to fix the problem This is a much simpler fix to the problem, i'll commit it in ~24 h if noone disagrees. About the other review you posted, shit it's been sitting there for almost a year. Someone should really have a look at it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377358] New: the animation properties of a layer (show in timeline / onion skin) are lost when merging layers
https://bugs.kde.org/show_bug.cgi?id=377358 Bug ID: 377358 Summary: the animation properties of a layer (show in timeline / onion skin) are lost when merging layers Product: krita Version: 3.1.2 Platform: Other OS: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: gordie.lachance+...@gmail.com Target Milestone: --- Hi ! The "show in timeline" property of a layer, and the "onion skin" one (enabled or disabled) are lost when layers are merged. I guess that the normal behaviour would be that the 'new' layer would have the settings that had the bottom layer before it was merged, no ? Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377151] View mode is transferred to other open documents
https://bugs.kde.org/show_bug.cgi?id=377151 Albert Astals Cid changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #8 from Albert Astals Cid --- Ok, yes, don't know why could not reproduce it the other day -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377292] Improve GPS Correlator UI
https://bugs.kde.org/show_bug.cgi?id=377292 --- Comment #8 from Wolfgang Scheffner --- Simon, I think we got rather close meanwhile. I understand your arguments and what you want to tell me with your drawing. So if you make the switch thing, change the unit for interpolation to sec. and give both values a generous max. value I'm completely fine with that. I think the discussion shows that there are quite a few conceivable scenarios and think also different requirements regarding precision. In the handbook I would tell that to the users and say that in most cases interpolation is the better choice (which is pretty close to what I just sent to Gilles for commit). Thanks so far! Wolfgang -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377151] View mode is transferred to other open documents
https://bugs.kde.org/show_bug.cgi?id=377151 --- Comment #7 from Albert Astals Cid --- Who cares if its set to confirmed or not, what i want is a way to reproduce it so i can fix it, do you prefer me to put it as confirmed and forget about it or to try to reproduce it myself so i can fix it? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377292] Improve GPS Correlator UI
https://bugs.kde.org/show_bug.cgi?id=377292 --- Comment #7 from Simon --- On 07/03/17 23:02, Wolfgang Scheffner wrote: > https://bugs.kde.org/show_bug.cgi?id=377292 > > --- Comment #6 from Wolfgang Scheffner --- > Hi Simon, > > I'd rather start with 2) because that will deliver also the anwer to 1): > I agree that nearly always interpolation is the better, because more precise > option. The only where it is not is when you moved from one GPS point to the > next not straight but in a really bad curve (like helmet camera in a slalom > skiing race. Poor example, I know, too fast for GPS). If the amplitude of that > curve is bigger than the distance between the two points you might get a worse > result than with direct match. I don't think curving is an issue, there a direct match is just as bad as interpolation match. I tried to visualize my thoughts in a crude painting, not sure it adds anything: http://i.imgur.com/GaT6hDg.png. A problem is uneven movement. Say you linger long at point 1, then go fast to point 2 (same applies if you meander around 1 before going straight to 2). In that case direct match gives an accurate position during lingering and only for a short time (going quickly to 2) a wrong one, while interpolation is getting farther off the longer you linger at 1. That is why I consider a shorter limit on the direct match than on the interpolation a plausible scenario. > What you described under 1), interpolation being kind of a backup for direct > match, doesn't make sense to me as long as interpolation is considered the > better option anyway. And it would be everything else but intuitive. It would > really require a description within the GUI. And even with all the space I > have > in the handbook it wouldn't be easy to explain (how it works yes, but what it > is good for ...?). That's what I am aiming at with doing interpolation: KISS. But that's not really digikam philosophy, so I am fine with making it a switch option between the two as you suggest below. I am in favour of making interpolation the default. > So I would still opt for the either - or solution and regarding the limits I > think it would even make sense to have a smaller max. value for interpolation. > The 2000 sec. from direct match, I mean that is more than half of an hour! Who > knows later what happend in this period of time and whether interpolation > still > makes sense? If you really have such a time gap and don't know exactly how you > moved, direct match would be the safer option. And we could enforce that a bit > by limiting interpolation to, say, ten minutes or so (600 sec. of course). I > imagine a pedestrian with this. If we talk about a car for ex. we are away > from > the max. values anyway. I think I misunderstood you. When I talk about max or limits, I was talking about the number entered by the user as max time between picture and track point. I never even considered that there is an upper bound on this number in the code. As explained in the first paragraph, I consider interpolation the long time option. Except for the uneven speed argument I can't think of a reason when interpolation is generally worse than direct matching. I can however imagine a (highly speculatory and probably unlikely) scenario where you only take track points every day (sailing?). In that case you want a limit of 1 day which is ridiculously big for most use cases, but I don't see why it shouldn't be valid. Or never mind I can think of one real scenario I had: In a group lots of people took pics, one person with a phone. On her pics there were therefore geotags, but they were very few. So you have a track with big gaps, meaning big time gaps to interpolate. > > Cheers > Wolfgang > -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 377318] MP3 files with a % symbol in file name do not play in preview pane
https://bugs.kde.org/show_bug.cgi?id=377318 Elvis Angelaccio changed: What|Removed |Added Product|dolphin |Phonon Assignee|dolphin-bugs-n...@kde.org |sit...@kde.org Component|panels: information |general CC||myr...@kde.org, ||romain.per...@gmail.com --- Comment #3 from Elvis Angelaccio --- Anyway Dolphin just uses the widget provided by phonon. Moving to phonon component. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 377357] configurable timer setting to turn off the keyboard's backlight
https://bugs.kde.org/show_bug.cgi?id=377357 ar...@protonmail.com changed: What|Removed |Added CC||ar...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 377357] New: configurable timer setting to turn off the keyboard's backlight
https://bugs.kde.org/show_bug.cgi?id=377357 Bug ID: 377357 Summary: configurable timer setting to turn off the keyboard's backlight Product: Powerdevil Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: ar...@protonmail.com Target Milestone: --- I'm running Mint 18.1 KDE on a 2012 MacBook Pro and would love a setting allowing the keyboard to stay lit for, say 15s of inactivity (no keyboard or mouse/trackpad input) and then turn off. Thanks :D -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377151] View mode is transferred to other open documents
https://bugs.kde.org/show_bug.cgi?id=377151 --- Comment #6 from Bodo Graumann --- No, that is not what I meant and I wrote as much. Please read my complete comment. Maybe my wording in that sentence was not clear: I meant "from the okular window in which the first document is open". It does not matter which document is used. The bug occurs with all of them. Oliver has reproduced the issue, so maybe it can be considered 'confirmed'? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374302] MYSQL : all Images with Geoinfo seem to be at (0°, 0°)
https://bugs.kde.org/show_bug.cgi?id=374302 --- Comment #13 from Maik Qualmann --- Git commit 300aea9d80091ccf4577b3fb140bdafaa8dcd7e1 by Maik Qualmann. Committed on 07/03/2017 at 22:07. Pushed by mqualmann into branch 'master'. remove wrong code to add image position in ImageScanner::copiedFrom() Related: bug 376933 FIXED-IN: 5.5.0 M +2-1NEWS M +0-5libs/database/item/imagescanner.cpp https://commits.kde.org/digikam/300aea9d80091ccf4577b3fb140bdafaa8dcd7e1 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 338669] GHNS dialog does not work, server newstuff.kde.org does not function properly
https://bugs.kde.org/show_bug.cgi?id=338669 Kurt Seebauer changed: What|Removed |Added CC||kurt_seeba...@yahoo.de --- Comment #3 from Kurt Seebauer --- still not working -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376530] Map jumps to 0/0 position when using "Zoom into a group"
https://bugs.kde.org/show_bug.cgi?id=376530 --- Comment #8 from Maik Qualmann --- The Comment 7 is wrong for this bug, sorry. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376933] Geolocation icon missing
https://bugs.kde.org/show_bug.cgi?id=376933 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Wolfgang, You need a complete rescan of the metadata. It is also possible that images in the database have been assigned geodata, but they have none. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376530] Map jumps to 0/0 position when using "Zoom into a group"
https://bugs.kde.org/show_bug.cgi?id=376530 --- Comment #7 from Maik Qualmann --- Git commit 300aea9d80091ccf4577b3fb140bdafaa8dcd7e1 by Maik Qualmann. Committed on 07/03/2017 at 22:07. Pushed by mqualmann into branch 'master'. remove wrong code to add image position in ImageScanner::copiedFrom() Related: bug 376933 FIXED-IN: 5.5.0 M +2-1NEWS M +0-5libs/database/item/imagescanner.cpp https://commits.kde.org/digikam/300aea9d80091ccf4577b3fb140bdafaa8dcd7e1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376933] Geolocation icon missing
https://bugs.kde.org/show_bug.cgi?id=376933 Maik Qualmann changed: What|Removed |Added Version Fixed In||5.5.0 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dig ||ikam/300aea9d80091ccf4577b3 ||fb140bdafaa8dcd7e1 --- Comment #1 from Maik Qualmann --- Git commit 300aea9d80091ccf4577b3fb140bdafaa8dcd7e1 by Maik Qualmann. Committed on 07/03/2017 at 22:07. Pushed by mqualmann into branch 'master'. remove wrong code to add image position in ImageScanner::copiedFrom() Related: bug 376530 FIXED-IN: 5.5.0 M +2-1NEWS M +0-5libs/database/item/imagescanner.cpp https://commits.kde.org/digikam/300aea9d80091ccf4577b3fb140bdafaa8dcd7e1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 331538] Wrong balance calculation
https://bugs.kde.org/show_bug.cgi?id=331538 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net --- Comment #15 from Jack --- Sorry for the delayed response, but I was correct, you seem to misunderstand how liability accounts work in KMyMoney. An account of type liability represents money you owe. A positive amount in the account represents a debt, but it is shown negative on the home page. I assume your intent with the starting balance of the liability account is to show you owe someone that amount. If you switch the sign on the starting balance, it will work as you expect, even if it is not completely obvious at first. If you would play with a credit card or loan account, the names of the columns (such as charge and payment) might make more sense than the simple increase and decrease of a liability account. However, in that case, you can think of it as an increase or decrease of your liability - which is the amount you owe. Your starting balance shows as a decrease, as if you had overpaid a loan. If you have any particular suggestions for improving the manual, I'll be glad to consider them as I really do need to update it for the Frameworks version currently being developed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377151] View mode is transferred to other open documents
https://bugs.kde.org/show_bug.cgi?id=377151 Albert Astals Cid changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from Albert Astals Cid --- "Note that it only occurs if the second document is opened from within the first one. " So you mean that the first document has a link to the second? This seems like an important bit you missed from your "steps to reproduce" list. Can you attach the documents you're using? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377292] Improve GPS Correlator UI
https://bugs.kde.org/show_bug.cgi?id=377292 --- Comment #6 from Wolfgang Scheffner --- Hi Simon, I'd rather start with 2) because that will deliver also the anwer to 1): I agree that nearly always interpolation is the better, because more precise option. The only where it is not is when you moved from one GPS point to the next not straight but in a really bad curve (like helmet camera in a slalom skiing race. Poor example, I know, too fast for GPS). If the amplitude of that curve is bigger than the distance between the two points you might get a worse result than with direct match. What you described under 1), interpolation being kind of a backup for direct match, doesn't make sense to me as long as interpolation is considered the better option anyway. And it would be everything else but intuitive. It would really require a description within the GUI. And even with all the space I have in the handbook it wouldn't be easy to explain (how it works yes, but what it is good for ...?). So I would still opt for the either - or solution and regarding the limits I think it would even make sense to have a smaller max. value for interpolation. The 2000 sec. from direct match, I mean that is more than half of an hour! Who knows later what happend in this period of time and whether interpolation still makes sense? If you really have such a time gap and don't know exactly how you moved, direct match would be the safer option. And we could enforce that a bit by limiting interpolation to, say, ten minutes or so (600 sec. of course). I imagine a pedestrian with this. If we talk about a car for ex. we are away from the max. values anyway. Cheers Wolfgang -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356285] Not enough space for page number
https://bugs.kde.org/show_bug.cgi?id=356285 --- Comment #11 from Albert Astals Cid --- > This is due to a fixed text box size. This is not true. Without any document open: http://i.imgur.com/S4O5Dti.png With a document open: http://i.imgur.com/nrvj8X5.png So stop pretending to know how the code works and start trying to help me reproduce your problem if you want it to be fixed. Which style are you running? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377318] MP3 files with a % symbol in file name do not play in preview pane
https://bugs.kde.org/show_bug.cgi?id=377318 --- Comment #2 from Alberto Gonzalez --- Hello Elvis. I have the same Phonon GStreamer 4.8.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366571] Kdenlive git master w/ movit: video playback corruption after end of CPU transition
https://bugs.kde.org/show_bug.cgi?id=366571 --- Comment #1 from lukefromdc --- As of 3-7-2017, movit noise now appears instead of the expected playback at all times (not just after transitions) unless the project is created using the June 2016 or earlier project file format. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 377274] Option to reset timer
https://bugs.kde.org/show_bug.cgi?id=377274 Albert Astals Cid changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #3 from Albert Astals Cid --- I see, i'll leave it open but since doesn't seem very prioritary for the application main task it may not get implemented soon (or ever). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377292] Improve GPS Correlator UI
https://bugs.kde.org/show_bug.cgi?id=377292 --- Comment #5 from Simon --- Hi Wolfgang, 1) Lets assume the current behaviour is really either only do direct matches or do direct matches and interpolate when a direct match is not possible according to limit. In that case in my opinion it makes sense to have generally a much longer limit on interpolation than on direct matches. I mean that is the point of interpolation: Try to get a more accurate result in case all points are too far away for a direct match. What do I miss? 2) I agree that both at the same time is confusing and I can't see any benefit. And I would even tend to always interpolate and certainly make it the standard behaviour. I struggle to imagine a situation where interpolation is adversary. Cheers, Simon -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377263] Automatically load layout at startup
https://bugs.kde.org/show_bug.cgi?id=377263 Wegwerf changed: What|Removed |Added Resolution|--- |WONTFIX CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |RESOLVED --- Comment #1 from Wegwerf --- This is a well-known issue that we cannot fix, as it is related to Qt. A search here or in the forum reveals a workaround: 1. do *not* maximize the Kdenlive window; "normalize" it temporarily. 2. Resize the Kdenlive window to its maximum, but don't use maximize. 3. Load your layout. 4. Quit Kdenlive. 5. Reload Kdenlive, the layout should now stick and the window be maximized. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377292] Improve GPS Correlator UI
https://bugs.kde.org/show_bug.cgi?id=377292 Wolfgang Scheffner changed: What|Removed |Added CC||wscheffn...@gmail.com --- Comment #4 from Wolfgang Scheffner --- Simon, you wrote via direct mail that you opened this as a wishlist. So I would like to add to that: 1) The Max. time gap is in seconds, the Max. interpol. time gap in minutes which doesn't make much sense to me considering what we discusses earlier. Both should be in second and the max. value you can introduce should also be the same (240 min. = 4 h doesn't make much sense for interpolating a position IMHO. With such a value you even had to take continental drift into account ;-)). 2) Instead of the one checkbox "Interpolate" there should be two toggle boxes/buttons where, if you check one, the other gets unchecked to make clear: either direct match or interpolate, both not possible. From that little bit of testing I could do I'm not sure if this is really implemented in the code (one or the other), at least I had to fill in zeros in one I wanted to disable. Looked a bit as if one of the two options has a higher priority. Unfortunately I have no time right now to test a bit more. Wolfgang -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373427] Plasma locks up in nouveau DRI2GetBuffersWithFormat creating new windows.
https://bugs.kde.org/show_bug.cgi?id=373427 pinheiro changed: What|Removed |Added CC||n...@oxygen-icons.org --- Comment #29 from pinheiro --- can still reproduce with plasmashell 5.8.5 and Xorg-server-1.19.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 Martin Gräßlin changed: What|Removed |Added CC||ed.gres...@greshko.com --- Comment #53 from Martin Gräßlin --- *** Bug 377225 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377075] transition checkboxes do not save checked state
https://bugs.kde.org/show_bug.cgi?id=377075 --- Comment #2 from lukefromdc --- On 3-7, some commit, probably this one: https://cgit.kde.org/kdenlive.git/commit/?id=35af0b4af89a6b92c33217f191dc55fa4d5cbb4d Partially fixed this. On the "dissolve" transition with its single checkbox for "reverse," the checkbox selection is now correctly saved and correctly applied. On the "wipe" transition with two checkboxes however, the top checkbox for "invert" now works, but the bottom one for "revert" still returns to the default settiog. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 377237] Screen configuration changes after reboot
https://bugs.kde.org/show_bug.cgi?id=377237 Martin Gräßlin changed: What|Removed |Added Product|kwin|KScreen Assignee|kwin-bugs-n...@kde.org |se...@kde.org Component|multihead |common -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377225] kwin crash when saving VirtualBox settings
https://bugs.kde.org/show_bug.cgi?id=377225 Martin Gräßlin changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #8 from Martin Gräßlin --- *** This bug has been marked as a duplicate of bug 363224 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377336] Weird behaviour of mouse cursor in games
https://bugs.kde.org/show_bug.cgi?id=377336 --- Comment #1 from Martin Gräßlin --- I'm having problems to understand the problem not knowing the game. Can you please attach screenshots to illustrate? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377206] Sort templates and camera filter ins configuration
https://bugs.kde.org/show_bug.cgi?id=377206 Simon changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/ab3e0bcb03969d545d7666 ||3b4d39a2f2be9fb572 Version Fixed In||5.5.0 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Simon --- Git commit ab3e0bcb03969d545d76663b4d39a2f2be9fb572 by Simon Frei. Committed on 07/03/2017 at 20:26. Pushed by sfrei into branch 'master'. Sort tables in configuration FIXED-IN: 5.5.0 M +2-1NEWS M +1-0utilities/setup/camera/setupcamera.cpp M +3-0utilities/setup/setuptemplate.cpp https://commits.kde.org/digikam/ab3e0bcb03969d545d76663b4d39a2f2be9fb572 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377292] Improve GPS Correlator UI
https://bugs.kde.org/show_bug.cgi?id=377292 Simon changed: What|Removed |Added Version Fixed In||5.5.0 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 371916] execution tree xtree concept
https://bugs.kde.org/show_bug.cgi?id=371916 Philippe Waroquiers changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377329] [Regression] "Del" does not work anymore
https://bugs.kde.org/show_bug.cgi?id=377329 Alex Bikadorov changed: What|Removed |Added CC||alex.bikado...@kdemail.net --- Comment #2 from Alex Bikadorov --- Just set Settings->Configure Krusader->General: "Delete Mode" Everything resolved? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376529] The panel is placed over the desktop icons, when both are located to the right.
https://bugs.kde.org/show_bug.cgi?id=376529 Eike Hein changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/d37b57dae09d1d9 ||d0e2b26101514ad216139c063 --- Comment #4 from Eike Hein --- Git commit d37b57dae09d1d9d0e2b26101514ad216139c063 by Eike Hein. Committed on 07/03/2017 at 20:20. Pushed by hein into branch 'Plasma/5.8'. Do apply margin if in right-to-left mode. M +2-1containments/desktop/package/contents/ui/main.qml https://commits.kde.org/plasma-desktop/d37b57dae09d1d9d0e2b26101514ad216139c063 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377355] Kmail2 does not reset scroll position in message preview/window
https://bugs.kde.org/show_bug.cgi?id=377355 --- Comment #1 from William L. Thomson Jr. --- Seems this is not consistent. After closing and re-opening kmail2 for other reasons. It seems to be resetting scroll. Not sure what I can do or did for it to stop scrolling. I will see if I can replicate. It has happened many times before. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377356] New: Kmail2 unable to deal with Thrashed, T flag in maildir
https://bugs.kde.org/show_bug.cgi?id=377356 Bug ID: 377356 Summary: Kmail2 unable to deal with Thrashed, T flag in maildir Product: kmail2 Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: wlt...@o-sinc.com Target Milestone: --- I believe this problems stems from Dovecot. Which on the server is marking an email Thrashed with the maildir T flag. Kmail seems to fetch/pull in these emails which is fine. But then it grays out the message. Such that it cannot be selected or deleted. If it is in a thread, you can delete the parent, with thread collapsed, and it will delete the Thrashed/T flagged email. Otherwise I have to navigate to the maildir directory containing the email and manually delete the file. Which is pretty annoying. It seems Kmail2 should either not pull in these emails. Immediate delete them, and, or not gray out. So the user can delete the message as normal. Either way Kmail2 is unable to handle them now, and I think falsely fetches them. I do not think Kmail2 is setting the T flag. Pretty sure that was set on the server's maildir. Just ends up the same in the client/kmail2 maildir on my system. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377356] Kmail2 unable to deal with Thrashed, T flag in maildir
https://bugs.kde.org/show_bug.cgi?id=377356 --- Comment #1 from William L. Thomson Jr. --- Forgot version info KMail Version 5.4.2 KDE Frameworks 5.31.0 Qt 5.7.1 (built against 5.7.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377355] New: Kmail2 does not reset scroll position in message preview/window
https://bugs.kde.org/show_bug.cgi?id=377355 Bug ID: 377355 Summary: Kmail2 does not reset scroll position in message preview/window Product: kmail2 Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: wlt...@o-sinc.com Target Milestone: --- When I am reading a long email, below the message list, not opening the email in a new window. If I scroll down. Then I switch to another email in the list. The scroll position does not reset to the top. It seems to end up further down in the next message. I am constantly scrolling to the top of the newly selected message. I do not believe it always did this, but I cannot recall 100%. KMail Version 5.4.2 KDE Frameworks 5.31.0 Qt 5.7.1 (built against 5.7.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366462] Regression: All desktop items cannot be clicked / touched / launched
https://bugs.kde.org/show_bug.cgi?id=366462 --- Comment #7 from Eike Hein --- Qt Quick isn't widgets though, and the entire Qt Quick event handling code is currently in major flux and being rewritten. The code you've quotes is from Task Manager and not related to Folder View. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377206] Sort templates and camera filter ins configuration
https://bugs.kde.org/show_bug.cgi?id=377206 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Simon, fine to commit this patch. But change the initial sort order from template title to A->Z. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377354] New: Do NOT delete 'frames in the same naming scheme' (out of frame range) when exporting
https://bugs.kde.org/show_bug.cgi?id=377354 Bug ID: 377354 Summary: Do NOT delete 'frames in the same naming scheme' (out of frame range) when exporting Product: krita Version: 3.1.2 Platform: unspecified OS: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: gordie.lachance+...@gmail.com Target Milestone: --- Hi, when I export my animation and that some files have the same naming scheme, I got the following message : "Frames with the same naming scheme exist in the destination directory. The are going to be deleted, continue ?" Then the whole sequence is deleted. Only the files from the frame range exported should be deleted. Why ? Let's say I have an animation of 1000 frames but I just changed 20 of them. The 1000 frames are deleted... And I have to render the whole sequence again :/ By the way, files are not moved to the trash bin but are really deleted, so you can't restore them. Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 377353] New: Crash on login after installing "indicator-multiload".
https://bugs.kde.org/show_bug.cgi?id=377353 Bug ID: 377353 Summary: Crash on login after installing "indicator-multiload". Product: kactivitymanagerd Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: jodr...@live.com CC: plasma-b...@kde.org Target Milestone: --- "Segmentation fault (11)", started after i installed: "indicator-multiload". As soon as log out and back in i get this crash, although "indicator-multiload" is running. Also not sure if related but "indicator-multiload" can't open "systemmoitor", i can run it from a terminal, krunner no problem. Backtrace: Application: kactivitymanagerd (kactivitymanagerd), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5b7bd3e8c0 (LWP 10303))] Thread 2 (Thread 0x7f5b700f8700 (LWP 10306)): #0 0x7f5b79d2bb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5b796d2c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f5b796d48d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f5b72cc4d79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f5b7a437b48 in QThreadPrivate::start (arg=0x2665da0) at thread/qthread_unix.cpp:368 #5 0x7f5b78d686ba in start_thread (arg=0x7f5b700f8700) at pthread_create.c:333 #6 0x7f5b79d3782d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f5b7bd3e8c0 (LWP 10303)): [KCrash Handler] #6 std::__atomic_base::compare_exchange_strong (__m2=, __m1=std::memory_order_acquire, __p2=, __p1=@0x7ffd8712d168: 0x0, this=0x20) at /usr/include/c++/5/bits/atomic_base.h:752 #7 std::atomic::compare_exchange_strong (__m=std::memory_order_acquire, __p2=, __p1=@0x7ffd8712d168: 0x0, this=0x20) at /usr/include/c++/5/atomic:475 #8 QAtomicOps::testAndSetAcquire (currentValue=, newValue=, expectedValue=0x0, _q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:290 #9 QBasicAtomicPointer::testAndSetAcquire (currentValue=, newValue=, expectedValue=0x0, this=0x20) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:259 #10 QBasicMutex::fastTryLock (current=, this=0x20) at thread/qmutex.h:89 #11 QMutex::lock (this=this@entry=0x20) at thread/qmutex.cpp:225 #12 0x7f5b7bde69af in QMutexLocker::QMutexLocker (m=0x20, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:137 #13 QDBusConnectionManager::busConnection (this=0x0, type=type@entry=QDBusConnection::SessionBus) at qdbusconnection.cpp:109 #14 0x7f5b7bde7a5a in QDBusConnection::sessionBus () at qdbusconnection.cpp:1177 #15 0x7f5b63cfb8bd in QtCurve::Style::disconnectDBus (this=0x26d75e0) at /workspace/build/qt5/style/qtcurve.cpp:695 #16 0x7f5b63d37726 in QtCurve::runAllCleanups () at /workspace/build/qt5/style/qtcurve_plugin.cpp:86 #17 QtCurve::StylePlugin::~StylePlugin (this=0x26a6e00, __in_chrg=) at /workspace/build/qt5/style/qtcurve_plugin.cpp:167 #18 0x7f5b63d37759 in QtCurve::StylePlugin::~StylePlugin (this=0x26a6e00, __in_chrg=) at /workspace/build/qt5/style/qtcurve_plugin.cpp:170 #19 0x7f5b7a5fa189 in QLibraryPrivate::unload (this=this@entry=0x26a6c30, flag=flag@entry=QLibraryPrivate::UnloadSys) at plugin/qlibrary.cpp:562 #20 0x7f5b7a5f01a2 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate (this=0x26a6140, __in_chrg=) at plugin/qfactoryloader.cpp:86 #21 0x7f5b7a5f02c9 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate (this=0x26a6140, __in_chrg=) at plugin/qfactoryloader.cpp:89 #22 0x7f5b7a63785c in QScopedPointerDeleter::cleanup (pointer=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60 #23 QScopedPointer >::~QScopedPointer (this=0x7f5b7b3a6cc8 <(anonymous namespace)::Q_QGS_loader::innerFunction()::holder+8>, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107 #24 QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:900 #25 0x7f5b7a5ef73a in QFactoryLoader::~QFactoryLoader (this=0x7f5b7b3a6cc0 <(anonymous namespace)::Q_QGS_loader::innerFunction()::holder>, __in_chrg=) at plugin/qfactoryloader.cpp:205 #26 0x7f5b7af131c9 in (anonymous namespace)::Q_QGS_loader::Holder::~Holder (this=, __in_chrg=) at styles/qstylefactory.cpp:72 #27 0x7f5b79c6aff8 in __run_exit_handlers (status=0, listp=0x7f5b79ff45f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #28 0x7f5b79c6b045 in __GI_exit (status=) at exit.c:104 #29 0x7f5b7ba5a27a in KDBusService::KDBusService (this=0x7ffd8712d740, options=..., parent=) at /workspace/build/src/kdbusservice.cpp:120 #30 0x00408dc9 in main (argc=2, argv=0x7ffd8712d888) at /workspace/build/src/service/Application.cpp:404 -- You are rec
[digikam] [Bug 351866] Make focus to input field after adding a face rectangle as an option and not by default
https://bugs.kde.org/show_bug.cgi?id=351866 --- Comment #9 from Wolfgang Scheffner --- (In reply to Yingjie Liu from comment #7) Sorry, I got it wrong. "...in the toolbar beside the "Show Fullscreen" action, " lead me somehow to the Main Toolbar right under the main menu. You were talking about the toolbar of the preview. That's absolutely okay, leave it there! > and it will disappear when user leave people view. ... Well, the preview is used in other views too but since it always have the add-face-tag icon its a must that your new icon will show up there as well (which it probably does anyway). Wolfgang Scheffner -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377352] New: When trying to configure the keyboard shortcut for switching the keyboard layout with wayland, the dialog closes
https://bugs.kde.org/show_bug.cgi?id=377352 Bug ID: 377352 Summary: When trying to configure the keyboard shortcut for switching the keyboard layout with wayland, the dialog closes Product: systemsettings Version: 5.8.4 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_keyboard_layout Assignee: unassigned-b...@kde.org Reporter: rob...@leblancnet.us Target Milestone: --- Using Wayland, I can't set the shortcut for switching the keyboard layouts. I am able to add QWERTY and Dvorak layouts and save them. When I click on "Main shortcuts" to set my custom shortcut, the dialog just closes. There is no autodebug dialog that comes up. Also, selecting the "Advanced" tab and trying to select "Configure keyboard options" causes the crash as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 377351] New: QFileDialog::getSaveFileName() checks for existing files before appending the file name extension
https://bugs.kde.org/show_bug.cgi?id=377351 Bug ID: 377351 Summary: QFileDialog::getSaveFileName() checks for existing files before appending the file name extension Product: frameworks-kio Version: 5.31.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: fschaefer@googlemail.com CC: kdelibs-b...@kde.org Target Milestone: --- When using a QFileDialog::getSaveFileName with automatic file name suffix appending enabled, the overwrite check is done before appending the file name extension, which is wrong. I have verified that QFileDialog calls the native KDE dialog (Qts own dialog also doesn't provide automatic file name suffix appending). Steps to reproduce: 1.) create a file called "aaa" (e.g. in the applications path) 2.) open save dialog, e.g. QString fileName = QFileDialog::getSaveFileName(this, "Save", QCoreApplication::applicationDirPath(), "test files(*.zzz)"); 3.) enable automatic file name extension appending in the dialog 4.) enter file name "aaa" 5.) confirm saving => dialog should return file name "aaa.zzz" (file doesn't exist) => instead the user is asked to confirm overwrite of file "aaa" (which already exists) => if overwriting is confirmed, file name "aaa" is returned instead of "aaa.zzz" (if "aaa" didn't exist and the overwrite check passes, "aaa.zzz" is returned as expected) Used Qt version is 5.7.1. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 377350] New: KDE Chrash directly after Login via rdp
https://bugs.kde.org/show_bug.cgi?id=377350 Bug ID: 377350 Summary: KDE Chrash directly after Login via rdp Product: kdelibs Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kded Assignee: unassigned-b...@kde.org Reporter: rabenh...@gmail.com Target Milestone: --- Application: kded4 (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-4-amd64 x86_64 Distribution: Debian GNU/Linux 8.5 (jessie) -- Information about the crash: - What I was doing when the application crashed: Chrash directly after login via rdp Linux linux01 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) Four AMD Unknown 3900MHz processors, 31140.16 total bogomips, 6851M RAM System library 2.19.0 Qt: 4.8.6 KDE Development Platform: 4.14.2 The crash can be reproduced sometimes. -- Backtrace: Application: KDE Daemon (kded4), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7eff74cb599a in ?? () from /usr/lib/x86_64-linux-gnu/kde4/plugins/kscreen/1/KSC_XRandR11.so #7 0x7eff752ff7b5 in KScreenDaemon::monitorConnectedChange() () from /usr/lib/kde4/kded_kscreen.so #8 0x7eff752ffe5f in KScreenDaemon::KScreenDaemon(QObject*, QList const&) () from /usr/lib/kde4/kded_kscreen.so #9 0x7eff75300968 in ?? () from /usr/lib/kde4/kded_kscreen.so #10 0x7eff91e95e43 in KPluginFactory::create (this=0x19347f0, iface=0x7eff91eedec0 "KDEDModule", parentWidget=0x0, parent=0x17adc10, args=..., keyword=...) at ../../kdecore/util/kpluginfactory.cpp:203 #11 0x7eff7bab1080 in create (args=..., parent=0x17adc10, this=) at ../../kdecore/util/kpluginfactory.h:507 #12 Kded::loadModule (this=this@entry=0x17adc10, s=..., onDemand=onDemand@entry=false) at ../../kded/kded.cpp:409 #13 0x7eff7bab19f9 in Kded::initModules (this=0x17adc10) at ../../kded/kded.cpp:268 #14 0x7eff7bab220e in Kded::recreateDone (this=this@entry=0x17adc10) at ../../kded/kded.cpp:580 #15 0x7eff7bab2293 in Kded::recreate (this=0x17adc10, initial=) at ../../kded/kded.cpp:547 #16 0x7eff7bab49cd in KDEDApplication::newInstance (this=) at ../../kded/kded.cpp:833 #17 0x7eff926fe6ca in KUniqueApplicationAdaptor::newInstance (this=0x18b45e0, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:442 #18 0x7eff926fe7ad in KUniqueApplicationAdaptor::qt_static_metacall (_o=_o@entry=0x18b45e0, _id=_id@entry=0, _a=_a@entry=0x72713560, _c=QMetaObject::InvokeMetaMethod) at ./kuniqueapplication_p.moc:57 #19 0x7eff926fe9b3 in qt_static_metacall (_a=0x72713560, _id=0, _c=QMetaObject::InvokeMetaMethod, _o=0x18b45e0) at ./kuniqueapplication_p.moc:100 #20 KUniqueApplicationAdaptor::qt_metacall (this=0x18b45e0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x72713560) at ./kuniqueapplication_p.moc:101 #21 0x7eff8ec146c6 in QDBusConnectionPrivate::deliverCall (this=this@entry=0x17b8240, object=object@entry=0x18b45e0, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:951 #22 0x7eff8ec15859 in QDBusConnectionPrivate::activateCall (this=this@entry=0x17b8240, object=0x18b45e0, flags=flags@entry=337, msg=...) at qdbusintegrator.cpp:856 #23 0x7eff8ec162f0 in QDBusConnectionPrivate::activateObject (this=0x17b8240, node=..., msg=..., pathStartPos=) at qdbusintegrator.cpp:1427 #24 0x7eff8ec1647b in QDBusActivateObjectEvent::placeMetaCall (this=0x18c3e00) at qdbusintegrator.cpp:1541 #25 0x7eff9191fe11 in QObject::event (this=this@entry=0x72713f70, e=e@entry=0x18c3e00) at kernel/qobject.cpp:1222 #26 0x7eff9190af9c in QCoreApplication::event (this=this@entry=0x72713f70, e=e@entry=0x18c3e00) at kernel/qcoreapplication.cpp:1767 #27 0x7eff90c5c7a3 in QApplication::event (this=0x72713f70, e=0x18c3e00) at kernel/qapplication.cpp:2549 #28 0x7eff90c5748c in QApplicationPrivate::notify_helper (this=this@entry=0x17aeb90, receiver=receiver@entry=0x72713f70, e=e@entry=0x18c3e00) at kernel/qapplication.cpp:4570 #29 0x7eff90c5dfa8 in QApplication::notify (this=this@entry=0x72713f70, receiver=receiver@entry=0x72713f70, e=e@entry=0x18c3e00) at kernel/qapplication.cpp:4356 #30 0x7eff926f71aa in KApplication::notify (this=0x72713f70, receiver=0x72713f70, event=0x18c3e00) at ../../kdeui/kernel/kapplication.cpp:311 #31 0x7eff9190671d in QCoreApplication::notifyInternal (this=0x72713f70, receiver=receiver@entry=0x72713f70, event=event@entry=0x18c3e00) at kernel/qcoreapplication.cpp:955 #32 0x7eff91909fc1 in sendEvent (event=0x18c3e00, receiver=0x72713f70) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #33 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=
[plasmashell] [Bug 377348] Folder view icon hold as selected when cursor pass over them.
https://bugs.kde.org/show_bug.cgi?id=377348 --- Comment #1 from Eike Hein --- I can't reproduce this on 5.9.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366462] Regression: All desktop items cannot be clicked / touched / launched
https://bugs.kde.org/show_bug.cgi?id=366462 --- Comment #6 from sac --- >The problem is that MouseEventListener in frameworks doesn't have touch event >support. Many thanks for the verification & debugging. Is this a bug in QT? In general QT should support this: "By default, QGuiApplication translates the first touch point in a QTouchEvent into a QMouseEvent. This makes it possible to enable touch events on existing widgets that do not normally handle QTouchEvent. " http://doc.qt.io/qt-5/qtouchevent.html "The MouseArea type allows mouse and touch events to be handled in a QML application." http://doc.qt.io/qt-5/qtquick-usecase-userinput.html Is this just related to the following (I guess onContainsMouseChanged will never fire in case of touch)? https://cgit.kde.org/kde-workspace.git/tree/plasma/desktop/applets/tasks/package/contents/ui/Task.qml?id=e9023a81186145ac4b33268a08759ab00df61466 onClicked: { if (isGroupParent) { groupDialog.target = task; groupDialog.visible = true; } else { tasks.activateItem(model.Id, true); } } -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 377349] QFileDialog (using KDEs file dialog): open/save button is enabled even if no file is selected
https://bugs.kde.org/show_bug.cgi?id=377349 --- Comment #1 from Frank Schaefer --- Used Qt version is 5.7.1. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 377349] New: QFileDialog (using KDEs file dialog): open/save button is enabled even if no file is selected
https://bugs.kde.org/show_bug.cgi?id=377349 Bug ID: 377349 Summary: QFileDialog (using KDEs file dialog): open/save button is enabled even if no file is selected Product: frameworks-kio Version: 5.31.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: fschaefer@googlemail.com CC: kdelibs-b...@kde.org Target Milestone: --- Using KDEs native file dialog, the open/save button of QFileDialog::getOpenFileName, getSaveFileName() etc. is enabled even if no file is selected Steps to reproduce: e.g. QFileDialog::getOpenFileName(this, "Open", QCoreApplication::applicationDirPath()); => dialog shows application directory with no file selected, but Open/Save button is enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377348] New: Folder view icon hold as selected when cursor pass over them.
https://bugs.kde.org/show_bug.cgi?id=377348 Bug ID: 377348 Summary: Folder view icon hold as selected when cursor pass over them. Product: plasmashell Version: 5.9.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: vmorenoma...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 104442 --> https://bugs.kde.org/attachment.cgi?id=104442&action=edit Cursor over icons on folder view widget. What happens? When I pass the mouse over icons of Folder view widget, the icons appear as if were selected and they stay as selected without form to "unmarked" them. Expected behavior: When I pass the mouse over icons they should not appear as marked. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377348] Folder view icon hold as selected when cursor pass over them.
https://bugs.kde.org/show_bug.cgi?id=377348 Víctor changed: What|Removed |Added CC||vmorenoma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 377346] Network Manager Import VPN Crashes With Wayland
https://bugs.kde.org/show_bug.cgi?id=377346 --- Comment #2 from Robert LeBlanc --- Sorry, drkoqi said that the bug didn't save. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 377345] Network Manager Import VPN Crashes With Wayland
https://bugs.kde.org/show_bug.cgi?id=377345 --- Comment #3 from Robert LeBlanc --- Sorry, drkoqi said that the bug didn't save. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 377345] Network Manager Import VPN Crashes With Wayland
https://bugs.kde.org/show_bug.cgi?id=377345 --- Comment #2 from Robert LeBlanc --- *** Bug 377347 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 377347] Network Manager Import VPN Crashes With Wayland
https://bugs.kde.org/show_bug.cgi?id=377347 Robert LeBlanc changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Robert LeBlanc --- Sorry, drkoqi said that the bug didn't save. *** This bug has been marked as a duplicate of bug 377345 *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 377346] Network Manager Import VPN Crashes With Wayland
https://bugs.kde.org/show_bug.cgi?id=377346 Robert LeBlanc changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Robert LeBlanc --- *** This bug has been marked as a duplicate of bug 377345 *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 377345] Network Manager Import VPN Crashes With Wayland
https://bugs.kde.org/show_bug.cgi?id=377345 --- Comment #1 from Robert LeBlanc --- *** Bug 377346 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 377345] New: Network Manager Import VPN Crashes With Wayland
https://bugs.kde.org/show_bug.cgi?id=377345 Bug ID: 377345 Summary: Network Manager Import VPN Crashes With Wayland Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rob...@leblancnet.us Target Milestone: --- Application: kde5-nm-connection-editor (5.8.4) Qt Version: 5.7.1 Frameworks Version: 5.28.0 Operating System: Linux 4.9.11-rleblanc201702041 x86_64 Distribution: Debian GNU/Linux 9.0 (stretch) -- Information about the crash: I opened the manage network connections from the network applet. I then selected "Add" and then "Import VPN". I selected my ovpn file and it asked if I wanted to copy the certs over. I said yes, and then got a message saying that the files already exists. The first time my certs were not there so the message didn't show up that time. I then get the crash before the wizard finishes. The first time, my config was there, the second time (I deleted the profile to recreate the bug) it did not show up. The crash can be reproduced every time. -- Backtrace: Application: Connection editor (kde5-nm-connection-editor), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5011d99940 (LWP 5289))] Thread 3 (Thread 0x7f4ffc782700 (LWP 5303)): #0 0x7f50213765bd in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f5013a0c181 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #2 0x7f50156940be in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f5015694b30 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f5015694bf0 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f50156a2bd9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f5013a3b2c8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #7 0x7f501e341424 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f50213839bf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f50100d1700 (LWP 5290)): #0 0x7f502137a54d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f501c20c9f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f501c20cb0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5021c8e06b in QEventDispatcherGlib::processEvents (this=0x7f50080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5021c379ca in QEventLoop::exec (this=this@entry=0x7f50100d0c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f5021a650f3 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f5024d076d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f5021a69da8 in QThreadPrivate::start (arg=0x7f5024d7cd60) at thread/qthread_unix.cpp:368 #8 0x7f501e341424 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f50213839bf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f5011d99940 (LWP 5289)): [KCrash Handler] #6 0x in ?? () #7 0x7f5011b4bcad in QtWaylandClient::QWaylandDisplay::handleKeyboardFocusChanged (this=0x55dd1c4b8120, inputDevice=) at qwaylanddisplay.cpp:418 #8 0x7f5011b42e1e in QtWaylandClient::QWaylandInputDevice::Keyboard::keyboard_leave (this=0x55dd1c4bd750, time=, surface=) at qwaylandinputdevice.cpp:629 #9 0x7f5011053038 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #10 0x7f5011052a9a in ffi_call (cif=cif@entry=0x7ffec2373aa0, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffec2373b70) at ../src/x86/ffi64.c:525 #11 0x7f5011466f2e in wl_closure_invoke (closure=closure@entry=0x55dd1cb35290, flags=flags@entry=1, target=, target@entry=0x55dd1c4be420, opcode=opcode@entry=2, data=) at ../src/connection.c:935 #12 0x7f5011463bc0 in dispatch_event (display=, queue=) at ../src/wayland-client.c:1310 #13 0x7f5011464e14 in dispatch_queue (queue=0x55dd1c4b8368, display=0x55dd1c4b82a0) at ../src/wayland-client.c:1456 #14 wl_display_dispatch_queue_pending (display=0x55dd1c4b82a0, queue=0x55dd1c4b8368) at ../src/wayland-client.c:1698 #15 0x7f5011464e6c in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1761 #16 0x7f5011b4a812 in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55dd1c4b8120) at qwaylanddisplay.cpp:181 #17 0x7f5021c655e9 in QMetaObject::activate (sender=sender@entry=0x55dd1c524290, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3740 #18 0x7f5021c65f07 in QMetaObject::activate (sender=sender@entry=0x55dd1c524290, m=m@entry=0x7f5021e83360 , local_
[kde] [Bug 377347] New: Network Manager Import VPN Crashes With Wayland
https://bugs.kde.org/show_bug.cgi?id=377347 Bug ID: 377347 Summary: Network Manager Import VPN Crashes With Wayland Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rob...@leblancnet.us Target Milestone: --- Application: kde5-nm-connection-editor (5.8.4) Qt Version: 5.7.1 Frameworks Version: 5.28.0 Operating System: Linux 4.9.11-rleblanc201702041 x86_64 Distribution: Debian GNU/Linux 9.0 (stretch) -- Information about the crash: I opened the manage network connections from the network applet. I then selected "Add" and then "Import VPN". I selected my ovpn file and it asked if I wanted to copy the certs over. I said yes, and then got a message saying that the files already exists. The first time my certs were not there so the message didn't show up that time. I then get the crash before the wizard finishes. The first time, my config was there, the second time (I deleted the profile to recreate the bug) it did not show up. The crash can be reproduced every time. -- Backtrace: Application: Connection editor (kde5-nm-connection-editor), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5011d99940 (LWP 5289))] Thread 3 (Thread 0x7f4ffc782700 (LWP 5303)): #0 0x7f50213765bd in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f5013a0c181 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #2 0x7f50156940be in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f5015694b30 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f5015694bf0 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f50156a2bd9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f5013a3b2c8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #7 0x7f501e341424 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f50213839bf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f50100d1700 (LWP 5290)): #0 0x7f502137a54d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f501c20c9f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f501c20cb0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5021c8e06b in QEventDispatcherGlib::processEvents (this=0x7f50080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5021c379ca in QEventLoop::exec (this=this@entry=0x7f50100d0c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f5021a650f3 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f5024d076d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f5021a69da8 in QThreadPrivate::start (arg=0x7f5024d7cd60) at thread/qthread_unix.cpp:368 #8 0x7f501e341424 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f50213839bf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f5011d99940 (LWP 5289)): [KCrash Handler] #6 0x in ?? () #7 0x7f5011b4bcad in QtWaylandClient::QWaylandDisplay::handleKeyboardFocusChanged (this=0x55dd1c4b8120, inputDevice=) at qwaylanddisplay.cpp:418 #8 0x7f5011b42e1e in QtWaylandClient::QWaylandInputDevice::Keyboard::keyboard_leave (this=0x55dd1c4bd750, time=, surface=) at qwaylandinputdevice.cpp:629 #9 0x7f5011053038 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #10 0x7f5011052a9a in ffi_call (cif=cif@entry=0x7ffec2373aa0, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffec2373b70) at ../src/x86/ffi64.c:525 #11 0x7f5011466f2e in wl_closure_invoke (closure=closure@entry=0x55dd1cb35290, flags=flags@entry=1, target=, target@entry=0x55dd1c4be420, opcode=opcode@entry=2, data=) at ../src/connection.c:935 #12 0x7f5011463bc0 in dispatch_event (display=, queue=) at ../src/wayland-client.c:1310 #13 0x7f5011464e14 in dispatch_queue (queue=0x55dd1c4b8368, display=0x55dd1c4b82a0) at ../src/wayland-client.c:1456 #14 wl_display_dispatch_queue_pending (display=0x55dd1c4b82a0, queue=0x55dd1c4b8368) at ../src/wayland-client.c:1698 #15 0x7f5011464e6c in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1761 #16 0x7f5011b4a812 in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55dd1c4b8120) at qwaylanddisplay.cpp:181 #17 0x7f5021c655e9 in QMetaObject::activate (sender=sender@entry=0x55dd1c524290, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3740 #18 0x7f5021c65f07 in QMetaObject::activate (sender=sender@entry=0x55dd1c524290, m=m@entry=0x7f5021e83360 , local_
[kde] [Bug 377346] New: Network Manager Import VPN Crashes With Wayland
https://bugs.kde.org/show_bug.cgi?id=377346 Bug ID: 377346 Summary: Network Manager Import VPN Crashes With Wayland Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rob...@leblancnet.us Target Milestone: --- Application: kde5-nm-connection-editor (5.8.4) Qt Version: 5.7.1 Frameworks Version: 5.28.0 Operating System: Linux 4.9.11-rleblanc201702041 x86_64 Distribution: Debian GNU/Linux 9.0 (stretch) -- Information about the crash: I opened the manage network connections from the network applet. I then selected "Add" and then "Import VPN". I selected my ovpn file and it asked if I wanted to copy the certs over. I said yes, and then got a message saying that the files already exists. The first time my certs were not there so the message didn't show up that time. I then get the crash before the wizard finishes. The first time, my config was there, the second time (I deleted the profile to recreate the bug) it did not show up. The crash can be reproduced every time. -- Backtrace: Application: Connection editor (kde5-nm-connection-editor), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5011d99940 (LWP 5289))] Thread 3 (Thread 0x7f4ffc782700 (LWP 5303)): #0 0x7f50213765bd in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f5013a0c181 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #2 0x7f50156940be in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f5015694b30 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f5015694bf0 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f50156a2bd9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f5013a3b2c8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #7 0x7f501e341424 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f50213839bf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f50100d1700 (LWP 5290)): #0 0x7f502137a54d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f501c20c9f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f501c20cb0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5021c8e06b in QEventDispatcherGlib::processEvents (this=0x7f50080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5021c379ca in QEventLoop::exec (this=this@entry=0x7f50100d0c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f5021a650f3 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f5024d076d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f5021a69da8 in QThreadPrivate::start (arg=0x7f5024d7cd60) at thread/qthread_unix.cpp:368 #8 0x7f501e341424 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f50213839bf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f5011d99940 (LWP 5289)): [KCrash Handler] #6 0x in ?? () #7 0x7f5011b4bcad in QtWaylandClient::QWaylandDisplay::handleKeyboardFocusChanged (this=0x55dd1c4b8120, inputDevice=) at qwaylanddisplay.cpp:418 #8 0x7f5011b42e1e in QtWaylandClient::QWaylandInputDevice::Keyboard::keyboard_leave (this=0x55dd1c4bd750, time=, surface=) at qwaylandinputdevice.cpp:629 #9 0x7f5011053038 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #10 0x7f5011052a9a in ffi_call (cif=cif@entry=0x7ffec2373aa0, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffec2373b70) at ../src/x86/ffi64.c:525 #11 0x7f5011466f2e in wl_closure_invoke (closure=closure@entry=0x55dd1cb35290, flags=flags@entry=1, target=, target@entry=0x55dd1c4be420, opcode=opcode@entry=2, data=) at ../src/connection.c:935 #12 0x7f5011463bc0 in dispatch_event (display=, queue=) at ../src/wayland-client.c:1310 #13 0x7f5011464e14 in dispatch_queue (queue=0x55dd1c4b8368, display=0x55dd1c4b82a0) at ../src/wayland-client.c:1456 #14 wl_display_dispatch_queue_pending (display=0x55dd1c4b82a0, queue=0x55dd1c4b8368) at ../src/wayland-client.c:1698 #15 0x7f5011464e6c in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1761 #16 0x7f5011b4a812 in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55dd1c4b8120) at qwaylanddisplay.cpp:181 #17 0x7f5021c655e9 in QMetaObject::activate (sender=sender@entry=0x55dd1c524290, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3740 #18 0x7f5021c65f07 in QMetaObject::activate (sender=sender@entry=0x55dd1c524290, m=m@entry=0x7f5021e83360 , local_
[digikam] [Bug 377240] Deleting an image (DEL key) within LightTable resets zoom factor for following image
https://bugs.kde.org/show_bug.cgi?id=377240 Maik Qualmann changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/79ec5ffd45ea8b96f9b87f ||e7fe6e810891c050b9 Version Fixed In||5.5.0 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Maik Qualmann --- Git commit 79ec5ffd45ea8b96f9b87fe7fe6e810891c050b9 by Maik Qualmann. Committed on 07/03/2017 at 18:39. Pushed by mqualmann into branch 'master'. fix reset zoom factor to fit the window FIXED-IN: 5.5.0 M +2-1NEWS M +1-1libs/widgets/graphicsview/previewlayout.cpp https://commits.kde.org/digikam/79ec5ffd45ea8b96f9b87fe7fe6e810891c050b9 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377344] Some emails are duplicated
https://bugs.kde.org/show_bug.cgi?id=377344 gugs...@free.fr changed: What|Removed |Added Platform|Other |Debian testing -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377344] New: Some emails are duplicated
https://bugs.kde.org/show_bug.cgi?id=377344 Bug ID: 377344 Summary: Some emails are duplicated Product: kmail2 Version: 5.2.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: gugs...@free.fr Target Milestone: --- Created attachment 104441 --> https://bugs.kde.org/attachment.cgi?id=104441&action=edit View of a thread with duplicated emails Some of the emails I receive are duplicated in Kmail. See screenshot attached for some example. Not all the emails received are duplicated; it happens frequently, but not always. I could not find any pattern for the duplicated emails; However, I am the impression that it is related with emails coming from mailing-lists. If I use the "Delete duplicated emails", one of the duplicated email is deleted. I am using Kmail 5.2.3 from debian testing. I retrieve my emails with pop3. Using Kmail's view source option, I compared the two copies of a duplicate email (using ediff in a text editor). They were completely identical . I also had a look in the folder containing the emails (maildir). "Greping" with a string that appears in a duplicate email, I had only one match. This would means that the email is not duplicated in the maildir folder, but only in Kmail's display (also in akonadi db?). I run a akonadictl fsck and restarted Kmail, but it did not change anything. Feel free to contact me for any additional information I could provide. Thank you. Best regards -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376613] Flatten doesn't affect file layers
https://bugs.kde.org/show_bug.cgi?id=376613 --- Comment #6 from Nathan Lovato --- Ah yes, sorry for the lack of details. Sounds great :) (In reply to Dmitry Kazakov from comment #5) > Created attachment 104435 [details] > attachment-30403-0.html > > I just checked how PS works: > > 1) If there is a group layer with children, then Ctrl+E shortcut is > automatically **renamed** into "Merge group" and the action doesn't > merge down, but merges the group > 2) If there is a layer with masks, then Ctrl+E doesn't bake it, but > works as usual, merges the layer down. > > So I feel that Ctrl+E with should still flatten, but groups only. But > for other types of layers, Ctrl+E should work as usual. And flatten > would convert the layers into usual paint layers if applicable. What do > you think about such idea? > > On 07.03.2017 16:27, Nathan Lovato wrote: > > https://bugs.kde.org/show_bug.cgi?id=376613 > > > > --- Comment #3 from Nathan Lovato --- > > (In reply to Dmitry Kazakov from comment #2) > >> Could you answer one question? Do you also want Ctrl+E (Merge Down) > >> shortcut to do flatten layer operation when possible? > >> > >> Basically, it would mean that you will have to press Ctrl+E multiple > >> times before merging down a layer with some masks/sublayers: > >> > >> Step 1) Ctrl+E -> Flatten Layer > >> Step 2) Ctrl+E -> Merge Down > > Would it be possible to merge the steps? I.e. Ctrl E -> merge and if > > necessary, > > auto flatten. Otherwise, if the merge operation can do 2 different things > > (flatten or merge) depending on where you use it, plus there's still the > > flatten option, you're going to lose some people. I don't know about Gimp, > > but > > at least Affinity and PS flatten things for you when you use the merge > > function. > > -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377343] New: German translation does not one hundred percent translate
https://bugs.kde.org/show_bug.cgi?id=377343 Bug ID: 377343 Summary: German translation does not one hundred percent translate Product: kdenlive Version: 16.12.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Translation Assignee: vpi...@kde.org Reporter: leelewislor...@yahoo.de Target Milestone: --- Created attachment 104440 --> https://bugs.kde.org/attachment.cgi?id=104440&action=edit 1.German 2.Englisch German is not German -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368535] Messageviewer: Line pitch too small on high dpi settings
https://bugs.kde.org/show_bug.cgi?id=368535 Tom Mittelstädt changed: What|Removed |Added Version|5.1.3 |5.2.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366204] Setting Fancy headers in View is not kept in kmail 16.04
https://bugs.kde.org/show_bug.cgi?id=366204 Freek de Kruijf changed: What|Removed |Added Resolution|INVALID |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #7 from Freek de Kruijf --- Using kmail2 5.4.2 from packet kmail version 16.12.2-1.1 and having installed kdepim-addons packet version 16.12.2-1.1, I still need to set Fancy headers each time I start kmail/kontact or to set the workaround. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377294] Application Launcher pops out very slowly
https://bugs.kde.org/show_bug.cgi?id=377294 --- Comment #5 from Martin Gräßlin --- The support info is the one to trust. It always reports the correct information. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 377342] New: "Whole words" search works in a wrong way
https://bugs.kde.org/show_bug.cgi?id=377342 Bug ID: 377342 Summary: "Whole words" search works in a wrong way Product: kate Version: 16.08 Platform: Other OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: kwrite-bugs-n...@kde.org Reporter: por...@narod.ru Target Milestone: --- When I do "Whole words" search for $Pay variable in a Perl file, it finds nothing (even though the Perl file contains such variable). Workaround: Use plain text or regex search. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 370028] Reduce the number of compiler warnings on MIPS platforms
https://bugs.kde.org/show_bug.cgi?id=370028 --- Comment #25 from Aleksandar Rikalo --- (In reply to Julian Seward from comment #23) > What's the status of this now? Can it be closed? No, it shouldn't. This is just the beginning. I'll prepare next few patches soon. Also, there are patches 2 and 3 which are still uncommitted. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 377341] New: Raise help window to foreground on F1 key
https://bugs.kde.org/show_bug.cgi?id=377341 Bug ID: 377341 Summary: Raise help window to foreground on F1 key Product: khelpcenter Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: por...@narod.ru Target Milestone: --- When I click "Kate Handbook" in Kate help menu or press F1 and the window with help is already opened but in background, the help window is not raised. The help window should be raised to foreground when one clicks help item. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377340] Select folder on middle click
https://bugs.kde.org/show_bug.cgi?id=377340 kishor...@gmail.com changed: What|Removed |Added Component|view-engine: general|general -- You are receiving this mail because: You are watching all bug changes.