[digikam] [Bug 397411] Not being able to move files in a removable media collection which is not mounted
https://bugs.kde.org/show_bug.cgi?id=397411 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Status|UNCONFIRMED |RESOLVED Version Fixed In||6.0.0 Resolution|--- |FIXED --- Comment #1 from Maik Qualmann --- The problem is fixed in the developer version of digiKam-6.0.0. The files were first moved to the DB, but because they could not be physically moved, they were gone. In digiKam-6.0.0 they are only moved in the DB if it was physically successful. Maik -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 397412] New: Crash when closing Dragon Player
https://bugs.kde.org/show_bug.cgi?id=397412 Bug ID: 397412 Summary: Crash when closing Dragon Player Product: dragonplayer Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: sit...@kde.org Reporter: pawel6...@gmail.com CC: myr...@kde.org Target Milestone: --- Application: dragon (17.08.3) Qt Version: 5.10.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.0-1-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: I have closed the Dragon Player aplication with active video. The crash can be reproduced sometimes. -- Backtrace: Application: Dragon Player (dragon), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f40aba11840 (LWP 16456))] Thread 3 (Thread 0x7f407ca66700 (LWP 16461)): #0 0x7f40b3704e6c in futex_wait_cancelable (private=, expected=0, futex_word=0x55a2db748250) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f40b3704e6c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55a2db748200, cond=0x55a2db748228) at pthread_cond_wait.c:502 #2 0x7f40b3704e6c in __pthread_cond_wait (cond=0x55a2db748228, mutex=0x55a2db748200) at pthread_cond_wait.c:655 #3 0x7f407d72ed6b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f407d72ea97 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f40b36fef2a in start_thread (arg=0x7f407ca66700) at pthread_create.c:463 #6 0x7f40b5feeedf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f40a1388700 (LWP 16458)): #0 0x7f40b5fe4739 in __GI___poll (fds=0x7f409c01c700, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f40b1ac2439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f40b1ac254c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f40b66bc1bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f40b665fb6a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f40b64757ea in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f40b6adfdf5 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f40b647ab4f in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f40b36fef2a in start_thread (arg=0x7f40a1388700) at pthread_create.c:463 #9 0x7f40b5feeedf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f40aba11840 (LWP 16456)): [KCrash Handler] #6 0x7f40b5f2cf3b in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f40b5f2e2f1 in __GI_abort () at abort.c:79 #8 0x7f40b06e48a9 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #9 0x7f40b06e52af in pa_fdsem_after_poll () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #10 0x7f40b06fcd0d in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #11 0x7f40b2e5bf30 in () at /usr/lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0 #12 0x7f40b1ac2287 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f40b1ac24c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f40b1ac254c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f40b66bc19f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f40ab3da2c1 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #17 0x7f40b665fb6a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f40b6668ed4 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x55a2d9a066be in () #20 0x7f40b5f19b17 in __libc_start_main (main=0x55a2d9a05ce0, argc=2, argv=0x7ffe7b47aea8, init=, fini=, rtld_fini=, stack_end=0x7ffe7b47ae98) at ../csu/libc-start.c:310 #21 0x55a2d9a0682a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397411] New: Not being able to move files in a removable media collection which is not mounted
https://bugs.kde.org/show_bug.cgi?id=397411 Bug ID: 397411 Summary: Not being able to move files in a removable media collection which is not mounted Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Albums-Engine Assignee: digikam-bugs-n...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hi there, I was just wondering if it could be possible to have an error message when we try to move some files in a collection stored on a network share which is not mounted? I have two collections: one locally stored and the other one on a network share. Yesterday, after editing my photos in my locally stored collection, I've moved them in the network share collection. Digikam told me that the folder where I wanted to put my photos didn't exists anymore. This is true, the network share wasn't mounted! But my problem was that the files I moved from my local storage were not displayed anymore in digikam: where were my pictures!? I get them back after closing and restarting digikam, but it has been very stressful. Do you think we could have an error message when we try to move files in an album stored in a network share which has not been mounted? Regards -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 --- Comment #47 from Viktor Maksimov --- Problem actual for version kmail 5.2.3 (Debian buster) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397194] Face tags are not well rendered when coming from Portrait DNG files
https://bugs.kde.org/show_bug.cgi?id=397194 --- Comment #5 from Mat --- Hello Maik, Even after updating the image preview mode, face tags are not well rendered. Kind regards -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 Viktor Maksimov changed: What|Removed |Added CC||va...@sincore.ru --- Comment #46 from Viktor Maksimov --- Problem actual for version kmail 5.2.3 (Debian buster) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397229] Facetags are not well displayed in the facetag list for one person
https://bugs.kde.org/show_bug.cgi?id=397229 --- Comment #4 from Mat --- hello Maik, sorry to answer so late. Yes, face tags have been defined manually. And for all the files I identified there was a problem, they have not been rotated: the orientation is stored in the picture, and I didn't change it. Regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]
https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #8 from Maik Qualmann --- Yes, Gilles. But I have another idea. If writing is only activated to sidecar, the modification date of the sidecar file will be written to the DB instead of the image. That would save us any changes to the DB. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374240] Krita crashes when creating a filter layer
https://bugs.kde.org/show_bug.cgi?id=374240 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 from Raghavendra kamath --- Thanks for checking, I think we can close this bug :) If you encounter anything in future please report a bug here, until then enjoy Krita. P.S. thanks to developers for fixing bugs :D -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397406] Digikam shouldn't use parentheses when renaming files
https://bugs.kde.org/show_bug.cgi?id=397406 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||metzping...@gmail.com Version Fixed In||6.0.0 --- Comment #1 from Maik Qualmann --- This behavior is already corrected in the developer version of digiKam-6.0.0. Now _1 is used again as a counter, thereby also the counter is increased if the file exists several times. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397405] Large empty space in Digikams main icon view since ~20180707 appimage
https://bugs.kde.org/show_bug.cgi?id=397405 Maik Qualmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 396961 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396961] Empty space on interface on thumbnail view
https://bugs.kde.org/show_bug.cgi?id=396961 Maik Qualmann changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #3 from Maik Qualmann --- *** Bug 397405 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 397410] New: Plasma shell crashes when right click on an item from Application menu
https://bugs.kde.org/show_bug.cgi?id=397410 Bug ID: 397410 Summary: Plasma shell crashes when right click on an item from Application menu Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: p.ha...@seznam.cz Target Milestone: --- Application: plasmashell (5.13.4) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.0-30-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: select item from application menu and right click on it (KDE neon 5.13.4). Crashes everytime. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa58469d940 (LWP 1906))] Thread 16 (Thread 0x7fa49b7fe700 (LWP 2746)): #0 0x7fa57d84074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa577c5038c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa577c50712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4cd3109d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fa577c76bb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa57cde36ba in start_thread (arg=0x7fa49b7fe700) at pthread_create.c:333 #6 0x7fa57d84c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7fa49bfff700 (LWP 2745)): #0 0x7fa57d84074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa577c5038c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa577c5049c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa577c504d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa577c76bb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa57cde36ba in start_thread (arg=0x7fa49bfff700) at pthread_create.c:333 #6 0x7fa57d84c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7fa4a57fa700 (LWP 2742)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa57df475cb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fa4cd80978f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7fa4cd80d868 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7fa4cd8089ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fa4cd80d8c2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fa4cd8089ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fa4cd80d8c2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fa4cd8089ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fa4cd80d8c2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fa4cd8089ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fa4cd80b3e0 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7fa57df46727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fa57cde36ba in start_thread (arg=0x7fa4a57fa700) at pthread_create.c:333 #14 0x7fa57d84c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7fa4a5ffb700 (LWP 2741)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa57df475cb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fa4cd80978f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7fa4cd80d868 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7fa4cd8089ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fa4cd80d8c2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fa4cd8089ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_
[digikam] [Bug 383563] Many tags disappeared from mariadb database
https://bugs.kde.org/show_bug.cgi?id=383563 --- Comment #5 from caulier.gil...@gmail.com --- Note : AppImage do not install anything on your system, and don't need to install extra package, as all in bundle in single executable -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383563] Many tags disappeared from mariadb database
https://bugs.kde.org/show_bug.cgi?id=383563 --- Comment #4 from caulier.gil...@gmail.com --- AppImage has only X11 support not Wayland. Wayland is not yet enough stable, and slow. The git repository is switch to maintenance stage but it's back now, as i can use it here... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]
https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #7 from caulier.gil...@gmail.com --- Maik, Your last Q is for me ??? Gilles -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397409] New: Buggy please parse!
https://bugs.kde.org/show_bug.cgi?id=397409 Bug ID: 397409 Summary: Buggy please parse! Product: Discover Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: perell.landscap...@gmail.com Target Milestone: --- Buggy please parse discover immediately, if you have crSHES WHERE it stays stuck and will not close after a large update -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 386391] Kate: code highlighting java: Binary Literals not supported
https://bugs.kde.org/show_bug.cgi?id=386391 Nibaldo changed: What|Removed |Added Latest Commit||https://commits.kde.org/syn ||tax-highlighting/48c8c7acd4 ||768342ba79c5b1feeda06f0f803 ||281 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Nibaldo --- Git commit 48c8c7acd4768342ba79c5b1feeda06f0f803281 by Nibaldo González. Committed on 13/08/2018 at 02:39. Pushed by ngonzalez into branch 'master'. Java: add binaries & hex-float, and support underscores in numbers Summary: Some improvements in the highlighting of literal numbers: * Add binaries: `0b1010` [1][3]. * Allow underscores in numbers (Float, Int, Hex, Octal & Binary) [2][3][4]. NOTE: The exact format of the numbers supported can be found in ref. [3] & [4]. * Add hexadecimal floating point: `0xA21.F18p+123` [4]. * Add missing suffixes in numbers: "L" in Hex & Octal, and "D" in Float [3][4]. **References:** * [1] Java (8) Documentation. Binary Literals: https://docs.oracle.com/javase/8/docs/technotes/guides/language/binary-literals.html * [2] Java (8) Documentation. Underscores in Numeric Literals: https://docs.oracle.com/javase/8/docs/technotes/guides/language/underscores-literals.html * [3] Java Language Specification. Chapter 3, Lexical Structure. [3.10.1] Integer Literals: https://docs.oracle.com/javase/specs/jls/se10/html/jls-3.html#jls-3.10.1 * [4] Java Language Specification. Chapter 3, Lexical Structure. [3.10.2] Floating-Point Literals: https://docs.oracle.com/javase/specs/jls/se10/html/jls-3.html#jls-3.10.2 Reviewers: dhaumann, cullmann, vkrause, #kate Reviewed By: cullmann, #kate Subscribers: ngraham, kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D14702 M +9-0autotests/folding/highlight.java.fold M +9-0autotests/html/highlight.java.html M +9-0autotests/input/highlight.java M +9-0autotests/reference/highlight.java.ref M +14 -10 data/syntax/java.xml https://commits.kde.org/syntax-highlighting/48c8c7acd4768342ba79c5b1feeda06f0f803281 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 394969] Baloo crashes on indexing new files
https://bugs.kde.org/show_bug.cgi?id=394969 --- Comment #1 from hotmusic...@mail.bg --- Hello! Are you devs on a long vacantion?!? :/ Application: baloo_file (5.45.0) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.13-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f945d4fa100 (LWP 12066))] Thread 2 (Thread 0x7f9452c11700 (LWP 12073)): #0 0x7f945af0508b in poll () from /lib64/libc.so.6 #1 0x7f94575ee109 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f94575ee21c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f945bb7ec0b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f945bb2709a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f945b9564da in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f945cd9b985 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f945b95b0ce in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f9459f66559 in start_thread () from /lib64/libpthread.so.0 #9 0x7f945af0f82f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f945d4fa100 (LWP 12066)): [KCrash Handler] #6 0x7f945aeb9533 in __memmove_sse2_unaligned_erms () from /lib64/libc.so.6 #7 0x7f945c4f4a93 in ?? () from /usr/lib64/libKF5BalooEngine.so.5 #8 0x7f945c4e5f64 in Baloo::PostingDB::get(QByteArray const&) () from /usr/lib64/libKF5BalooEngine.so.5 #9 0x7f945c4f2180 in Baloo::WriteTransaction::commit() () from /usr/lib64/libKF5BalooEngine.so.5 #10 0x7f945c4eb4c2 in Baloo::Transaction::commit() () from /usr/lib64/libKF5BalooEngine.so.5 #11 0x563275fed408 in ?? () #12 0x7f945bb5614c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #13 0x563275ff5b95 in ?? () #14 0x563275feb42e in ?? () #15 0x7f945bb5614c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #16 0x7f945bb62437 in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib64/libQt5Core.so.5 #17 0x7f945bb62768 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib64/libQt5Core.so.5 #18 0x7f945bb569eb in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #19 0x7f945bb28a71 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #20 0x7f945bb7e19e in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5 #21 0x7f945bb7e8e9 in ?? () from /usr/lib64/libQt5Core.so.5 #22 0x7f94575edf57 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #23 0x7f94575ee190 in ?? () from /usr/lib64/libglib-2.0.so.0 #24 0x7f94575ee21c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #25 0x7f945bb7ebef in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #26 0x7f945bb2709a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #27 0x7f945bb2f9e4 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #28 0x563275fd721c in ?? () #29 0x7f945ae37f4a in __libc_start_main () from /lib64/libc.so.6 #30 0x563275fd748a in _start () Report to https://bugs.kde.org/ -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 315468] Close button for tabs
https://bugs.kde.org/show_bug.cgi?id=315468 Simon Depiets changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 315468] Close button for tabs
https://bugs.kde.org/show_bug.cgi?id=315468 Simon Depiets changed: What|Removed |Added Assignee|sha...@ukr.net |sdepi...@gmail.com CC||sdepi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 193899] Lokalize crashes with project overview opened and externaly updating translation files
https://bugs.kde.org/show_bug.cgi?id=193899 Simon Depiets changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |NEEDSINFO CC||sdepi...@gmail.com --- Comment #2 from Simon Depiets --- I've never encountered this issue, is there a way to reproduce it ? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 193899] Lokalize crashes with project overview opened and externaly updating translation files
https://bugs.kde.org/show_bug.cgi?id=193899 Simon Depiets changed: What|Removed |Added Assignee|kdelibs-b...@kde.org|sdepi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 397389] Falkon crashes when launched
https://bugs.kde.org/show_bug.cgi?id=397389 --- Comment #6 from tr...@yandex.com --- Try this workaround: QT_XCB_FORCE_SOFTWARE_OPENGL = 1 falkon https://bbs.archlinux.org/viewtopic.php?id=238108 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397397] New: No access to the client that changed desktop in KWin::Client.desktopChanged() signal
https://bugs.kde.org/show_bug.cgi?id=397397 Bug ID: 397397 Summary: No access to the client that changed desktop in KWin::Client.desktopChanged() signal Product: kwin Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: lingtj...@hotmail.com Target Milestone: --- I'm trying to let my script hook into the default KWin methods to change client desktops but I can't seem to get access to the client that is changing its desktop. The API describes for the KWin::Client object the desktopChanged() signal without arguments whereas I would expect it to be similar to any of the other signals such as clientStartUserMovedResized(KWin::Client *) which gives the user access to the client that changed by its argument. I tried to get access to the client that switches desktop using the active client (workspace.activeClient) but this return null in this method. I'm not sure if this is intended behavior or if it's a bug, but either way I would like to get access to the client which had its desktop property changed. How do I do this? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395954] Broken KDE activities integration
https://bugs.kde.org/show_bug.cgi?id=395954 Christoph Cullmann changed: What|Removed |Added Latest Commit||https://commits.kde.org/kat ||e/cdb3da47ccda1c0600bbeb6c6 ||a73180b9a3b9754 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #4 from Christoph Cullmann --- Git commit cdb3da47ccda1c0600bbeb6c6a73180b9a3b9754 by Christoph Cullmann, on behalf of Simone Scalabrino. Committed on 12/08/2018 at 11:42. Pushed by cullmann into branch 'master'. Support activities when opening files Differential Revision: https://phabricator.kde.org/D13826 M +15 -0kate/kateapp.cpp M +7-0kate/kateapp.h M +4-0kate/kateappadaptor.cpp M +7-0kate/kateappadaptor.h M +37 -1kate/main.cpp https://commits.kde.org/kate/cdb3da47ccda1c0600bbeb6c6a73180b9a3b9754 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397397] No access to the client that changed desktop in KWin::Client.desktopChanged() signal
https://bugs.kde.org/show_bug.cgi?id=397397 Martin Flöser changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- You connect to the client's signal desktopChanged. This means you already have the client. Otherwise you could not even connect to the signal. It's your task to capture it appropriately in the lambda. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 389636] YAML syntax highlighting for nested flow collections fails
https://bugs.kde.org/show_bug.cgi?id=389636 Nibaldo changed: What|Removed |Added Latest Commit||https://commits.kde.org/syn ||tax-highlighting/bd9dbac79a ||a4402a3f768140993a53b12eab7 ||4e2 CC||nibg...@gmail.com Version Fixed In||5.50.0 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Nibaldo --- Hi, thanks for reporting this bug. It has been solved in: https://phabricator.kde.org/D14760 That corresponds to the commit: https://commits.kde.org/syntax-highlighting/bd9dbac79aa4402a3f768140993a53b12eab74e2 The fix will be included in KDE Frameworks 5.50, available in September 2018. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 397404] New: kformattest fails with installed kcoreaddons language package
https://bugs.kde.org/show_bug.cgi?id=397404
Bug ID: 397404
Summary: kformattest fails with installed kcoreaddons language
package
Product: frameworks-kcoreaddons
Version: 5.49.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mp...@kde.org
Reporter: ralf.habac...@freenet.de
CC: kdelibs-b...@kde.org
Target Milestone: ---
On a system without installed kcoreaddonsl language package kformattest does
not return any error:
~/src/kf5/kcoreaddons-build> bin/kformattest
* Start testing of KFormatTest *
Config: Using QtTest library 5.11.1, Qt 5.11.1 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 4.8.5)
PASS : KFormatTest::initTestCase()
PASS : KFormatTest::formatByteSize()
PASS : KFormatTest::formatDuration()
PASS : KFormatTest::formatDecimalDuration()
PASS : KFormatTest::formatSpelloutDuration()
PASS : KFormatTest::formatRelativeDate()
PASS : KFormatTest::formatValue()
PASS : KFormatTest::cleanupTestCase()
Totals: 8 passed, 0 failed, 0 skipped, 0 blacklisted, 2ms
* Finished testing of KFormatTest *
With installed kcoreaddons language package it returns on a system using
'de_DE' locale
~/src/kf5/kcoreaddons-build> bin/kformattest
* Start testing of KFormatTest *
Config: Using QtTest library 5.11.1, Qt 5.11.1 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 4.8.5)
PASS : KFormatTest::initTestCase()
PASS : KFormatTest::formatByteSize()
FAIL! : KFormatTest::formatDuration() Compared values are not the same
Actual (format.formatDuration(singleSecond, options)): "0 h 00 m 04 s"
Expected (QStringLiteral("0h00m04s")) : "0h00m04s"
Loc: [/home/ralf/src/kf5/kcoreaddons/autotests/kformattest.cpp(226)]
FAIL! : KFormatTest::formatDecimalDuration() Compared values are not the same
Actual (format.formatDecimalDuration(10)) : "10 Millisekunde(n)"
Expected (QStringLiteral("10 millisecond(s)")): "10 millisecond(s)"
Loc: [/home/ralf/src/kf5/kcoreaddons/autotests/kformattest.cpp(302)]
FAIL! : KFormatTest::formatSpelloutDuration() Compared values are not the same
Actual (format.formatSpelloutDuration(1000)): "1 Sekunde(n)"
Expected (QStringLiteral("1 second(s)")) : "1 second(s)"
Loc: [/home/ralf/src/kf5/kcoreaddons/autotests/kformattest.cpp(318)]
FAIL! : KFormatTest::formatRelativeDate() Compared values are not the same
Actual (format.formatRelativeDate(testDate, QLocale::LongFormat)): "Heute"
Expected (QStringLiteral("Today")) : "Today"
Loc: [/home/ralf/src/kf5/kcoreaddons/autotests/kformattest.cpp(341)]
PASS : KFormatTest::formatValue()
PASS : KFormatTest::cleanupTestCase()
Totals: 4 passed, 4 failed, 0 skipped, 0 blacklisted, 1ms
* Finished testing of KFormatTest *
and with 'C' locale
~/src/kf5/kcoreaddons-build> LC_ALL=C bin/kformattest
* Start testing of KFormatTest *
Config: Using QtTest library 5.11.1, Qt 5.11.1 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 4.8.5)
PASS : KFormatTest::initTestCase()
PASS : KFormatTest::formatByteSize()
PASS : KFormatTest::formatDuration()
FAIL! : KFormatTest::formatDecimalDuration() Compared values are not the same
Actual (format.formatDecimalDuration(10)) : "10 milliseconds"
Expected (QStringLiteral("10 millisecond(s)")): "10 millisecond(s)"
Loc: [/home/ralf/src/kf5/kcoreaddons/autotests/kformattest.cpp(302)]
FAIL! : KFormatTest::formatSpelloutDuration() Compared values are not the same
Actual (format.formatSpelloutDuration(1000)): "1 second"
Expected (QStringLiteral("1 second(s)")) : "1 second(s)"
Loc: [/home/ralf/src/kf5/kcoreaddons/autotests/kformattest.cpp(318)]
PASS : KFormatTest::formatRelativeDate()
PASS : KFormatTest::formatValue()
PASS : KFormatTest::cleanupTestCase()
Totals: 6 passed, 2 failed, 0 skipped, 0 blacklisted, 1ms
* Finished testing of KFormatTest *
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 225481] Adjust the color temperature of your screen
https://bugs.kde.org/show_bug.cgi?id=225481 Kai-Uwe Behrmann changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Kai-Uwe Behrmann --- Good to bring this physiological color issue on the table. After more reading on the subject, personally I support the idea since some months. It is good to have. My efforts went into integration of ICC style color management inside the Oyranos project. Here the page for the Oyranos Night Manager for the interested: https://github.com/oyranos-cms/oyranos/projects/2 This implementation will work with old X11, as there are API's easily available. There is a different KWin-Wayland effort, which works only for the white point side without ICC calibration integration or general GPU color transforms. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397160] Task manager don’t take Fitt’s law into account
https://bugs.kde.org/show_bug.cgi?id=397160 --- Comment #4 from ariasuni --- I have the exact same problem for both. There is exactly one pixel between screen edge and the icon with my setup. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 347225] Crash upon closing System Settings
https://bugs.kde.org/show_bug.cgi?id=347225 Ben Creasy changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||b...@bencreasy.com --- Comment #2 from Ben Creasy --- Is this still happening with later versions? Closing in the meantime. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 366586] YAML highlight fails
https://bugs.kde.org/show_bug.cgi?id=366586 Nibaldo changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.50.0 CC||nibg...@gmail.com Latest Commit||https://commits.kde.org/syn ||tax-highlighting/bd9dbac79a ||a4402a3f768140993a53b12eab7 ||4e2 --- Comment #1 from Nibaldo --- Hi, thanks for reporting this bug! It has been solved in: https://phabricator.kde.org/D14760 That corresponds to the commit: https://commits.kde.org/syntax-highlighting/bd9dbac79aa4402a3f768140993a53b12eab74e2 The fix will be included in KDE Frameworks 5.50, available in September 2018. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 336715] Read-only fields on the General tab should be selectable so their information can be copied
https://bugs.kde.org/show_bug.cgi?id=336715 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from Karl Ove Hufthammer --- This seems to be fixed. By this patch (for bug #105692), I believe: https://phabricator.kde.org/D13554 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 397398] Misleading ‘Created’ date in file properties
https://bugs.kde.org/show_bug.cgi?id=397398 --- Comment #1 from Karl Ove Hufthammer --- I believe the *real* creation time (if available) can be found using QFileInfo::birthTime() available in Qt 5.10+ https://doc.qt.io/qt-5/qfileinfo.html#birthTime -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396271] Unable to open files directly from mtp device (video inside)
https://bugs.kde.org/show_bug.cgi?id=396271 Zayed Al-Saidi changed: What|Removed |Added CC||zayed.alsa...@gmail.com --- Comment #1 from Zayed Al-Saidi --- MTP protocol is not working at all in Dolphin!! As workaround, please use different file manager. I am using nautilus to get the work done. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397001] The "maximise" button is missing in decoration of the geolocation editor window [patch]
https://bugs.kde.org/show_bug.cgi?id=397001 Maik Qualmann changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/62499189cbe39308bff231 ||5a98cfd21f3a7397f5 Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #5 from Maik Qualmann --- Git commit 62499189cbe39308bff2315a98cfd21f3a7397f5 by Maik Qualmann. Committed on 12/08/2018 at 10:43. Pushed by mqualmann into branch 'master'. replace Qt::Dialog window flag with Qt::Window to enable min/max button under GNOME currently tested for problems under GNOME3, KF5 and Window7/10 BUGS: 397001 FIXED-IN: 6.0.0 https://commits.kde.org/digikam/62499189cbe39308bff2315a98cfd21f3a7397f5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383563] Many tags disappeared from mariadb database
https://bugs.kde.org/show_bug.cgi?id=383563 --- Comment #3 from maderios --- I never install any appimage because they crash my graphic system based on last Enlightenment/wayland. Normally, I can easily compile DK git/Arch Aur but today, I can't update. DK git site seems down, I get : 'fatal: Unable to look up anongit.kde.org (port 9418) (Temporary failure in name resolution' -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365786] Mouse button used for gestures cannot be used in normal way
https://bugs.kde.org/show_bug.cgi?id=365786 obno...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||obno...@gmail.com --- Comment #4 from obno...@gmail.com --- Same here. Any news? openSUSE Tumbleweed Plasma 5.13.4 Frameworks 5.48.0 Qt 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 397403] New: Lagging square around mouse pointer
https://bugs.kde.org/show_bug.cgi?id=397403 Bug ID: 397403 Summary: Lagging square around mouse pointer Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ser...@iskynet.es Target Milestone: --- This bug happen in KDE NEON Bionic. https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1684240 This bug have more one year and now in bionic. When will it fix? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]
https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #5 from Kristian Karl --- If you don't mind. I can try to have a go at suggesting a new patch, where the modification timestamp of the sidecar file is stored in the database (as Maik suggested) and used. I guess it will take me a week to do that. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 364093] No warning if file could not be saved
https://bugs.kde.org/show_bug.cgi?id=364093 Simon Depiets changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/lok ||alize/fcd47259b449aa03b2e61 ||e934d79b2bef7da7788 Status|ASSIGNED|RESOLVED --- Comment #2 from Simon Depiets --- Git commit fcd47259b449aa03b2e61e934d79b2bef7da7788 by Simon Depiets. Committed on 13/08/2018 at 01:08. Pushed by sdepiets into branch 'master'. Save as saves the file to a new path even if there was no changes Summary: Currently the file is not "saved as" if it hasn't been modified, which can lead to some confusion. With this revision the file will be saved as long as the new path is different from the old one. Reviewers: #localization, aacid, ltoscano, shaforostoff, mlaurent Reviewed By: #localization, aacid Tags: #localization Differential Revision: https://phabricator.kde.org/D14699 M +0-1src/catalog/catalog.cpp M +7-7src/editortab.cpp M +1-1src/editortab.h https://commits.kde.org/lokalize/fcd47259b449aa03b2e61e934d79b2bef7da7788 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382390] plasma-shell crash when search for app in installed app list
https://bugs.kde.org/show_bug.cgi?id=382390 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 397389] Falkon crashes when launched
https://bugs.kde.org/show_bug.cgi?id=397389 --- Comment #5 from thflo...@gmail.com --- Thanks, indeed package qml-module-qtwebengine was not installed. But falkon still crashes: Error message: $ LANG=C falkon -e QObject::connect: invalid null parameter Received signal 11 SEGV_MAPERR 0008 #0 0x7f510ce7e76e #1 0x7f510ce7e880 #2 0x7f510ce7eeb7 #3 0x7f51088f4fc0 #4 0x7f50e73e5dbc #5 0x7f50e73e5fb7 #6 0x7f50e7472f2f #7 0x7f50e6a6fef6 #8 0x7f50e6a701af #9 0x7f50e6a70d40 nouveau_pushbuf_kick #10 0x7f50e7473556 #11 0x7f50e704e451 #12 0x7f510d7a2254 #13 0x7f510d7a1efa #14 0x7f510d9b4cb5 #15 0x7f510d931214 #16 0x7f510d95a5f1 #17 0x7f510f4c86f6 #18 0x7f510f4d954b #19 0x7f510f4dd02b #20 0x7f510f4e1d83 #21 0x7f510f4e1e3a #22 0x7f510f4ccbb6 #23 0x7f510ce7f218 #24 0x7f510ce9f91a #25 0x7f510cea03bf #26 0x7f510cea0558 #27 0x7f510cea2b21 #28 0x7f510cec21fb #29 0x7f510cee34f4 #30 0x7f510cedef41 #31 0x7f51088a5f2a start_thread #32 0x7f51089b6edf clone r8: 7f50cc099fc0 r9: 7f50cc000200 r10: r11: 0206 r12: 7f50cc099de0 r13: 5617e5c476f0 r14: 0001 r15: 002d di: 7f50cc099fd0 si: bp: 7f50cc099de0 bx: 7f50cc099de0 dx: ax: 7f50cc099de0 cx: sp: 7f509fffdd10 ip: 7f50e73e5dbc efl: 00010202 cgf: 002b0033 erf: 0006 trp: 000e msk: cr2: 0008 [end of stack trace] Calling _exit(1). Core file will not be generated. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 397369] [Neon Bionic] Chat window does not show messages - version 4:17.12.3-0ubuntu1
https://bugs.kde.org/show_bug.cgi?id=397369 malek@gmail.com changed: What|Removed |Added CC||malek@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378275] Kate doesn't do smooth pixel-by-pixel scrolling
https://bugs.kde.org/show_bug.cgi?id=378275 Nate Graham changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397001] The "maximise" button is missing in decoration of the geolocation editor window [patch]
https://bugs.kde.org/show_bug.cgi?id=397001 --- Comment #6 from Maik Qualmann --- Git commit 62499189cbe39308bff2315a98cfd21f3a7397f5 by Maik Qualmann. Committed on 12/08/2018 at 10:43. Pushed by mqualmann into branch 'master'. replace Qt::Dialog window flag with Qt::Window to enable min/max button under GNOME currently tested for problems under GNOME3, KF5 and Window7/10 FIXED-IN: 6.0.0 M +2-2NEWS M +4-0core/utilities/advancedrename/advancedrenamedialog.cpp M +4-0core/utilities/geolocation/editor/dialog/geolocationedit.cpp M +4-0core/utilities/maintenance/maintenancedlg.cpp M +3-0core/utilities/mediaserver/dmediaserverdlg.cpp M +3-0core/utilities/metadataedit/dialog/metadataedit.cpp M +3-0core/utilities/setup/setup.cpp https://commits.kde.org/digikam/62499189cbe39308bff2315a98cfd21f3a7397f5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397396] F11 as full-screen shortcut
https://bugs.kde.org/show_bug.cgi?id=397396 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt --- Okay, I looked into this, and this isn't going to change by default: the KDE default is ctrl-shift-f, and I don't want to move away from that without very good reasons.. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375951] locally integrated menus
https://bugs.kde.org/show_bug.cgi?id=375951 Kai Krakow changed: What|Removed |Added CC||k...@kaishome.de -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 397389] Falkon crashes when launched
https://bugs.kde.org/show_bug.cgi?id=397389 thflo...@gmail.com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|UPSTREAM|--- -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397406] New: Digikam shouldn't use parentheses when renaming files
https://bugs.kde.org/show_bug.cgi?id=397406 Bug ID: 397406 Summary: Digikam shouldn't use parentheses when renaming files Product: digikam Version: 5.9.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import-Rename Assignee: digikam-bugs-n...@kde.org Reporter: fireph...@gmail.com Target Milestone: --- When duplicate file names are downloaded and automatically renamed with no prompt they have ' (1)' added to the file name. This string is not searchable with the normal search tools provided by the desktop. These file names can't be found with Dolphin or kfind. In my case it was due to actual identical duplicate files in every sense so the find duplicates tool only helps in locating them but not easily deleting the nearly 700 photos within a range of 160 directories and the thousands of other photos and videos where they were all downloaded to. I know this is because of changed behavior where the prompt for duplicate was taken away, but the biggest issue is the hours I spent finding a reliable way to find all the images and rename them or move them because they used parentheses. If the files were just renamed without using special characters and the space then searching for them would me much simpler with your typical desktop tools without having to resort to regex or piped commands which is how I was able to find all these files in 8 months worth of folders. I know it is trivial for some to do some regex and pipe some commands to find or do anything but for most it is not and the complexity or limitations involved with the tools provided by the desktop can leave a person frustrated due to some relatively minor choices in file names. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397402] New: Invisible guides
https://bugs.kde.org/show_bug.cgi?id=397402 Bug ID: 397402 Summary: Invisible guides Product: krita Version: 4.1.1 Platform: Other OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: jo.y.v...@gmail.com Target Milestone: --- Guides become invisible after dragging from the ruler to the canvas -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397405] New: Large empty space in Digikams main icon view since ~20180707 appimage
https://bugs.kde.org/show_bug.cgi?id=397405 Bug ID: 397405 Summary: Large empty space in Digikams main icon view since ~20180707 appimage Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Albums-IconView Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Created attachment 114417 --> https://bugs.kde.org/attachment.cgi?id=114417&action=edit Digikams icon view with wasted space Since the appimage of 20180707 (approx) there is a large empty space in the Digikam main view area. Right clicking on it provides a checkbox labeled "Digikam thumbnail dock" but this doesn't make sense in icon view. Also, if I enable it in icon view and then enter preview mode (where it does make sense as an option) and then exit again, it is gone, so the state does not seem to be saved either. Please remove it for icon view or at least let Digikam's main icon view use the space like previously. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397397] No access to the client that changed desktop in KWin::Client.desktopChanged() signal
https://bugs.kde.org/show_bug.cgi?id=397397
--- Comment #2 from LinG ---
Yes, I understand that at the moment when I'm connecting to the signal I have
access to the client, but I don't understand how I get access to the client
inside the callback method that I provide for when the signal gets triggered.
My current understanding is:
```
client.desktopChanged.connect(function () {
// how do I get the client inside this callback?
})
```
Here I provide a method (callback/lambda) that gets triggered whenever the
desktop of this client changes.
The gap in my knowledge is then, how I would get access to the client inside
this callback?
You refer to capturing the client in this lambda, could you please give a small
example of how I would go about doing this?
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 397400] New: Masking reference pictures
https://bugs.kde.org/show_bug.cgi?id=397400 Bug ID: 397400 Summary: Masking reference pictures Product: krita Version: 4.1.1 Platform: Other OS: OS X Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: jo.y.v...@gmail.com Target Milestone: --- I'm Very happy with Krita 4.1.1. Runs smoothly with low resource consumption as it should. Finally I can drop version 3.1.1. My very first impression about the reference tool was: where is the masking tool? Or... A way to cut the picture temporally to a smaller size. Example. I load a human figure as reference, but need just a detail of the whole, let's say the head. So I adjust the boundaries of the reference image to show just the head, meanwhile the reference picture beneth rests unmodified and in the same scale ratio. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 397389] Falkon crashes when launched
https://bugs.kde.org/show_bug.cgi?id=397389 tr...@yandex.com changed: What|Removed |Added CC||tr...@yandex.com --- Comment #4 from tr...@yandex.com --- (In reply to thflorek) Did you try this? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903785 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378275] Kate doesn't do smooth pixel-by-pixel scrolling
https://bugs.kde.org/show_bug.cgi?id=378275 Nate Graham changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #9 from Nate Graham --- Unmarking as a duplicate of Bug 256561 because there's a patch that fixes that, but not this. This will have to be fixed separately. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 256561] Katepart scrolls per paragraph rather than respecting the input device's scroll preference (i.e. n lines for a mouse wheel, pixel-by-pixel for touchpad)
https://bugs.kde.org/show_bug.cgi?id=256561 --- Comment #33 from Dominik Haumann --- New proposed patch: https://phabricator.kde.org/D14758 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 396954] When someone calls, it appears in uncountable desktop-popup widgets
https://bugs.kde.org/show_bug.cgi?id=396954 --- Comment #3 from pi...@gmx.de --- Okay, I did killall kdeconnectd ; /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd and then I called my cellphone. I didn't answer the call but as soon as my cellphone begins to ring, dozens of popups appear on my desktop. Here is my output: kdeconnect.core: KdeConnect daemon starting kdeconnect.core: onStart kdeconnect.core: KdeConnect daemon started kdeconnect.core: Broadcasting identity packet kdeconnect.core: Sending onNetworkChange to 1 LinkProviders kdeconnect.core: Broadcasting identity packet kdeconnect.core: Sending onNetworkChange to 1 LinkProviders kdeconnect.core: Broadcasting identity packet kdeconnect.core: Starting client ssl (but I'm the server TCP socket) kdeconnect.core: TCP connection done (i'm the existing device) kdeconnect.core: Starting server ssl (I'm the client TCP socket) kdeconnect.core: Socket succesfully stablished an SSL connection kdeconnect.core: It is a known device "Sony Xperia XZ1" kdeconnect.plugin.sftp: add to dolphin kdeconnect.plugin.sftp: Created device: "Sony Xperia XZ1" Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeconnect.plugin.mpris: MPRIS service "org.mpris.MediaPlayer2.amarok" just came online kdeconnect.plugin.mpris: Mpris addPlayer "org.mpris.MediaPlayer2.amarok" -> "Amarok" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.plugin.telephony: Creating notification with type: "callReceived" kdeconnect.core: TCP connection done (i'm the existing device) kdeconnect.core: Starting server ssl (I'm the client TCP socket) kdeconnect.core: Socket succesfully stablished an SSL connection kdeconnect.core: It is a known device "Sony Xperia XZ1" This is not very helpful, is it? Do I need debug-libs? Thanks Andreas -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 397399] New: Firefox plasma-browser-integration crashes with apparmor profiles enforced
https://bugs.kde.org/show_bug.cgi?id=397399 Bug ID: 397399 Summary: Firefox plasma-browser-integration crashes with apparmor profiles enforced Product: plasma-browser-integration Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: markota...@gmail.com Target Milestone: --- Ubuntu 18.04.1, up to date. Latest firefox, plasma-browser-integration, apparmor with FF profile enabled. I get this crash after starting FF: ..that browser-integration was denied x (execute) right. Quite obviously from the POV of apparmor. I think browser-integration needs to provide its own profile to apparmor that will override this, or cooperate with Firefox that provide theirs for ubuntu. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 397041] Shortcut to Re-open recently closed tab
https://bugs.kde.org/show_bug.cgi?id=397041 Alex Bikadorov changed: What|Removed |Added Severity|normal |wishlist Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||alex.bikado...@kdemail.net --- Comment #1 from Alex Bikadorov --- Yes, would be good to have that. With full view state, navigation history and, unlike Dolphin, tab position. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 397154] Cannot build kcoreadons 5.49rc1
https://bugs.kde.org/show_bug.cgi?id=397154 --- Comment #11 from Pawel --- And more... I cannot build kcoreaddons with any patch starts from this commit: https://cgit.kde.org/kcoreaddons.git/commit/?id=cfd7b30ef6c22d71c5931a920ffbabb818327988 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 397398] Misleading ‘Created’ date in file properties
https://bugs.kde.org/show_bug.cgi?id=397398 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- Technically, that file was "Created" on that given date. However, I can see your point. From what I can tell there's UDS_CREATION_TIME in UDSEntry which might be set to birth time depending on platform/fs. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 367902] Systemsettings crash under wayland session
https://bugs.kde.org/show_bug.cgi?id=367902 Ben Creasy changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||b...@bencreasy.com --- Comment #2 from Ben Creasy --- Is this still happening? Please comment and reopen if so. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 397389] Falkon crashes when launched
https://bugs.kde.org/show_bug.cgi?id=397389 --- Comment #3 from thflo...@gmail.com --- (In reply to David Rosca from comment #2) > QtWebEngine doesn't work with nouveau Thank you for the quick reply. For me the question remains, why did falkon launch without problems some days/weeks before? Videocard unchanged, only software updates e.g. qt5 transition -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397401] New: Lock default resources
https://bugs.kde.org/show_bug.cgi?id=397401 Bug ID: 397401 Summary: Lock default resources Product: krita Version: 4.1.1 Platform: Other OS: OS X Status: UNCONFIRMED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: jo.y.v...@gmail.com Target Milestone: --- I wondered why I could (by mistake) delete Krita's default resources like brushes and brush settings.. Please lock default resources -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]
https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #4 from Kristian Karl --- I'm using my patch as a work-around for now. Sync'd metadata is a bit more important to me, than the significant drawback of increased backup times. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 397398] New: Misleading ‘Created’ date in file properties
https://bugs.kde.org/show_bug.cgi?id=397398 Bug ID: 397398 Summary: Misleading ‘Created’ date in file properties Product: frameworks-kio Version: 5.48.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Properties dialog Assignee: fa...@kde.org Reporter: k...@huftis.org CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 114415 --> https://bugs.kde.org/attachment.cgi?id=114415&action=edit Screenshot showing properties window launched from Krusader The KIO ‘Properties’ window for a file shows three dates: Created: Modified: Accessed: However, the ‘Created’ date seems to be the ‘ctime’, which is *not* the creation time for the file. I have a bunch of files with apparently have been ‘modified’ *before* their ‘Created’ date, which is chronologically impossible. (See screenshot.) Note 1: What is shown in the ‘Properties’ window seems to depend on how it’s accessed. Accessing it via Dolphin doesn’t show the ‘Created’ field, but accessing it via Krusader does. (In both cases the window comes from KIO, not the host application.) Note 2: Unix/Linux filesystems doesn’t store the creation time in a *standard* field: https://unix.stackexchange.com/questions/7562/what-file-systems-on-linux-store-the-creation-time Note 3: Explanation of ctime, atime and mtime https://www.unixtutorial.org/2008/04/atime-ctime-mtime-in-unix-filesystems/ -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 397407] New: Search URLs are wrong
https://bugs.kde.org/show_bug.cgi?id=397407 Bug ID: 397407 Summary: Search URLs are wrong Product: choqok Version: 1.6 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Friendica Assignee: scarp...@kde.org Reporter: theodorstormgr...@gmail.com CC: mehrdad.mom...@gmail.com Target Milestone: --- When tring to search for posts of a user it get 404 page not found. The instance I use is libranet. I'm not 100% sure but at least the rss feed for the posts of a user was /feed/ -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 397408] New: Deleting calendar event in DAV groupware resource fails
https://bugs.kde.org/show_bug.cgi?id=397408 Bug ID: 397408 Summary: Deleting calendar event in DAV groupware resource fails Product: korganizer Version: 5.8.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: groupware Assignee: kdepim-b...@kde.org Reporter: miros...@vujicic.com Target Milestone: --- I can create and edit events in CalDav resources, but deleting fails. If I try and delete an event I created, the event disappears from the local calendar view, but when I try to update the calendar folder I get "Before syncing it is necessary to have the resource online. Do you want to make it online?", and I click "Go Online". If I try to update the calendar again the same happens again - which means the upstream resource was not updated. When I look in akonadiconsole, in Agents tab, next to the resource there is a Status Message: "There was a problem with the request. The item has not been deleted from the server. The file or folder does not exist. (0)." Once this happens, the only thing I can do (what I found so far) is delete the agent and re-create it. I got the line from the calendar log: Code: Select all 2404:130:0:1000:4186:4465:8a69:1b4c - [23/Apr/2018:06:27:11 +1200] "DELETE /caldav.php//1518548964.R513.ics/ HTTP/1.1" 404 407 "-" "Mozilla/5.0 (X11; Linux x86_64) KHTML/5.38.0 (like Gecko) Konqueror/5 KIO/5.38" I was told that trailing slash after 1518548964.R513.ics is probably the culprit. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 256561] Katepart scrolls per paragraph rather than respecting the input device's scroll preference (i.e. n lines for a mouse wheel, pixel-by-pixel for touchpad)
https://bugs.kde.org/show_bug.cgi?id=256561 Dominik Haumann changed: What|Removed |Added CC||m...@svenbrauch.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 366586] YAML highlight fails
https://bugs.kde.org/show_bug.cgi?id=366586
--- Comment #2 from Nibaldo ---
Git commit bd9dbac79aa4402a3f768140993a53b12eab74e2 by Nibaldo González.
Committed on 12/08/2018 at 11:08.
Pushed by ngonzalez into branch 'master'.
YAML: fix keys, add numbers and other improvements
Summary:
Fix some reported bugs and update the syntax for YAML 1.2:
* Fixes the end of a Key:
Related: bug 389636
Any line of text before `:` is highlighted as Key, which is very general and
gives rise to errors. As mentioned in the bug, in a line like the following,
everything is considered as a Key, until the last `:`
{F6188499}
To fix this, it's necessary to add a space/end-line to the end of a Key
`KEY:(?=\s|$)`.
The YAML documentation mentions: *Mappings use a colon and space (“: ”) to mark
each key: value pair* [1].
* Fix delimiter characters in a Key:
On the next line, it is highlighted as a Key: `{b:`
{F6188501}
Within hashes and lists, the characters `{`, `[` and `,` should not be
highlighted as Keys, since these are delimiting characters that mark the
start/end of an element.
* Allow inline attributes in lists: `[key1: value, key2: value, ...]`
Previously, when writing a key, the entire line was highlighted as a value, now
the value ends with "," or "]" (in the example, `3, 2, !!ddfgdf` is Key and
`sdsd 1, takeoff]}` is value).
{F6188504}
* Highlight values in Key with multiple lines. That is, when ":" is the first
character of a line.
* Highlight references, aliases, strings, etc. in hashes. Before, the hashes
only support content of the type `key: value`. This improves highlighting in
keys with many lines.
{F6188507}
* Add mapping-key operator: `?`. In the current highlight, references, aliases,
sequences and dash after "?" are not highlighted, that is corrected. This also
applies to lists and hashes.
{F6188508}
* Add escapes [2]. Also, allow escapes in keys quoted. Ex: `"key\"a": value` or
'key''a': value`.
* Add Integers [4] & Floats [5] [3] (the documentation shows the exact regular
expressions).
* Add booleans [7] & improves the detection of null (add missing null keywords)
[6]. These are highlighted with "dsChar".
NOTE: Booleans, null, integers & floats require specific delimiters to avoid
incorrect highlighting (for example, not highlight numbers present in sentences
or dates). For that reason I use several RegExpr instead of keywords or other
rules.
{F6188509}
Although there are still things to be corrected! Lines with literal/folded
style (after "|" or ">") are not highlighted correctly.
Ex:
```
key1:
- key2: |
Literal characters " ' { }
Literal...
- key 3: value
```
To do that you have to capture the exact indentation of the Key. I tried to do
it with dynamic rules, but it does not capture the spaces at the start of a
line! I will try to fix this in a future diff. I added a comment mentioning
this.
**References:**
* [1] YAML Specs, Collections: http://yaml.org/spec/1.2/spec.html#id2759963
* [2] YAML Specs, Escaped Characters:
http://yaml.org/spec/1.2/spec.html#id2776092
* [3] YAML Specs, Integer & Float: http://yaml.org/spec/1.2/spec.html#id2803828
* [4] Integer Language-Independent Type for YAML™ Version 1.1:
http://yaml.org/type/int.html
* [5] Floating-Point Language-Independent Type for YAML™ Version 1.1:
http://yaml.org/type/float.html
* [6] Null Language-Independent Type for YAML™ Version 1.1:
http://yaml.org/type/null.html
* [7] Boolean Language-Independent Type for YAML™ Version 1.1:
http://yaml.org/type/bool.html
Reviewers: dhaumann, cullmann, #framework_syntax_highlighting
Reviewed By: cullmann, #framework_syntax_highlighting
Subscribers: kwrite-devel, kde-frameworks-devel
Tags: #kate, #frameworks
Differential Revision: https://phabricator.kde.org/D14760
A +78 -0autotests/folding/test.yaml.fold
A +85 -0autotests/html/test.yaml.html
A +78 -0autotests/input/test.yaml
A +78 -0autotests/reference/test.yaml.ref
M +166 -39 data/syntax/yaml.xml
https://commits.kde.org/syntax-highlighting/bd9dbac79aa4402a3f768140993a53b12eab74e2
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 389636] YAML syntax highlighting for nested flow collections fails
https://bugs.kde.org/show_bug.cgi?id=389636
--- Comment #2 from Nibaldo ---
Git commit bd9dbac79aa4402a3f768140993a53b12eab74e2 by Nibaldo González.
Committed on 12/08/2018 at 11:08.
Pushed by ngonzalez into branch 'master'.
YAML: fix keys, add numbers and other improvements
Summary:
Fix some reported bugs and update the syntax for YAML 1.2:
* Fixes the end of a Key:
Related: bug 366586
Any line of text before `:` is highlighted as Key, which is very general and
gives rise to errors. As mentioned in the bug, in a line like the following,
everything is considered as a Key, until the last `:`
{F6188499}
To fix this, it's necessary to add a space/end-line to the end of a Key
`KEY:(?=\s|$)`.
The YAML documentation mentions: *Mappings use a colon and space (“: ”) to mark
each key: value pair* [1].
* Fix delimiter characters in a Key:
On the next line, it is highlighted as a Key: `{b:`
{F6188501}
Within hashes and lists, the characters `{`, `[` and `,` should not be
highlighted as Keys, since these are delimiting characters that mark the
start/end of an element.
* Allow inline attributes in lists: `[key1: value, key2: value, ...]`
Previously, when writing a key, the entire line was highlighted as a value, now
the value ends with "," or "]" (in the example, `3, 2, !!ddfgdf` is Key and
`sdsd 1, takeoff]}` is value).
{F6188504}
* Highlight values in Key with multiple lines. That is, when ":" is the first
character of a line.
* Highlight references, aliases, strings, etc. in hashes. Before, the hashes
only support content of the type `key: value`. This improves highlighting in
keys with many lines.
{F6188507}
* Add mapping-key operator: `?`. In the current highlight, references, aliases,
sequences and dash after "?" are not highlighted, that is corrected. This also
applies to lists and hashes.
{F6188508}
* Add escapes [2]. Also, allow escapes in keys quoted. Ex: `"key\"a": value` or
'key''a': value`.
* Add Integers [4] & Floats [5] [3] (the documentation shows the exact regular
expressions).
* Add booleans [7] & improves the detection of null (add missing null keywords)
[6]. These are highlighted with "dsChar".
NOTE: Booleans, null, integers & floats require specific delimiters to avoid
incorrect highlighting (for example, not highlight numbers present in sentences
or dates). For that reason I use several RegExpr instead of keywords or other
rules.
{F6188509}
Although there are still things to be corrected! Lines with literal/folded
style (after "|" or ">") are not highlighted correctly.
Ex:
```
key1:
- key2: |
Literal characters " ' { }
Literal...
- key 3: value
```
To do that you have to capture the exact indentation of the Key. I tried to do
it with dynamic rules, but it does not capture the spaces at the start of a
line! I will try to fix this in a future diff. I added a comment mentioning
this.
**References:**
* [1] YAML Specs, Collections: http://yaml.org/spec/1.2/spec.html#id2759963
* [2] YAML Specs, Escaped Characters:
http://yaml.org/spec/1.2/spec.html#id2776092
* [3] YAML Specs, Integer & Float: http://yaml.org/spec/1.2/spec.html#id2803828
* [4] Integer Language-Independent Type for YAML™ Version 1.1:
http://yaml.org/type/int.html
* [5] Floating-Point Language-Independent Type for YAML™ Version 1.1:
http://yaml.org/type/float.html
* [6] Null Language-Independent Type for YAML™ Version 1.1:
http://yaml.org/type/null.html
* [7] Boolean Language-Independent Type for YAML™ Version 1.1:
http://yaml.org/type/bool.html
Reviewers: dhaumann, cullmann, #framework_syntax_highlighting
Reviewed By: cullmann, #framework_syntax_highlighting
Subscribers: kwrite-devel, kde-frameworks-devel
Tags: #kate, #frameworks
Differential Revision: https://phabricator.kde.org/D14760
A +78 -0autotests/folding/test.yaml.fold
A +85 -0autotests/html/test.yaml.html
A +78 -0autotests/input/test.yaml
A +78 -0autotests/reference/test.yaml.ref
M +166 -39 data/syntax/yaml.xml
https://commits.kde.org/syntax-highlighting/bd9dbac79aa4402a3f768140993a53b12eab74e2
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-browser-integration] [Bug 397399] Firefox plasma-browser-integration crashes with apparmor profiles enforced
https://bugs.kde.org/show_bug.cgi?id=397399 --- Comment #1 from Mark --- Created attachment 114416 --> https://bugs.kde.org/attachment.cgi?id=114416&action=edit apparmour message after starting FF, browser-integration crash -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 397381] Grammar/spelling error in Configure Konsole, TabBar
https://bugs.kde.org/show_bug.cgi?id=397381 Egmont Koblinger changed: What|Removed |Added CC||egm...@gmail.com --- Comment #2 from Egmont Koblinger --- Indeed "effect" would be the correct word here. I'd take a step backwards though and question this entire string. I have Qt 5.9. Why does it say "will have ...", in future tense? Why would I care that they used to have different meanings, especially if the UI doesn't state what those meanings were? Are the next two labels correct now anyway? Or do they correspond to the old behavior? And what's the new behavior, then? This message makes me totally uncertain. Or is the label correct for both Qt versions, just some little detail changed in the implementation (not _a_ffecting the semantics of the option)? Why would I care about my Qt version? Why not just tell me what these options do now, and nothing more? (If technically required, then decide based on a compile-time or run-time check on Qt version). This thing just looks way too technical, very user unfriendly to me. Maybe it's just me, more of a GNOME guy than a KDE one, usually following/preferring their UI choices. Please don't let my rant and overall dislike of this UI block you from quickly applying the one-letter fix first! :) -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 393081] PO-Revision-Date timezone offset doesn't account for DST
https://bugs.kde.org/show_bug.cgi?id=393081 Simon Depiets changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://commits.kde.org/lok ||alize/e7fdea7a5c8783ac2eadd ||244c09ee0534653efb6 --- Comment #3 from Simon Depiets --- Git commit e7fdea7a5c8783ac2eadd244c09ee0534653efb6 by Simon Depiets. Committed on 13/08/2018 at 01:01. Pushed by sdepiets into branch 'master'. Take into account summer time for the date offset in PO-Revision-Date Summary: Using the offsetFromUtc is more straightforward and accurate Reviewers: #localization, aacid, mlaurent, ltoscano, shaforostoff Reviewed By: #localization, aacid Tags: #localization Differential Revision: https://phabricator.kde.org/D14721 M +5-4src/catalog/gettextheader.cpp https://commits.kde.org/lokalize/e7fdea7a5c8783ac2eadd244c09ee0534653efb6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 359517] Can't extend onto second screen in VMWare
https://bugs.kde.org/show_bug.cgi?id=359517 Ben Creasy changed: What|Removed |Added CC||b...@bencreasy.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 397154] Cannot build kcoreadons 5.49rc1
https://bugs.kde.org/show_bug.cgi?id=397154 --- Comment #10 from Pawel --- Maybe some historic (and not only) informations will be helpful. I built kcoreaddons 5.48rc myself on python-pyqt5 ver. 5.11.2; after that, python-pyqt5 was rebuild against of python 3.7. So in Arch we have python 3.7 and python-pyqt5 5.11.2 rebuild on it now. Today I try to build kcoreaddons 5.48 against of python-pyqt5 5.11.2 (and python 3.7 and of course with PythonModuleGeneration optional dependency) and I can build it without any errors. I use ECM 5.49 (becouse of my fault). I cannot build kcoreaddons 5.49 against of those same packages (version of them) of python, python-pyqt5 and sip/python-sip, so maybe it's related to one commit in kcoreaddons between 5.48 and 5.49. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 176737] Inconsistent file extensions (jpg and jpeg, tif and tiff ...)
https://bugs.kde.org/show_bug.cgi?id=176737 David Faure changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from David Faure --- Nowadays (Qt5/KF5), the default extension for a mimetype comes from shared-mime-info (from freedesktop), not from kimgio (which doesn't really exist anymore). In shared-mime-info the default for JPEG is *.jpeg and the default for TIFF is *.tif OK, I have now fixed it in shared-mime-info (commit 2d7bea2), the default extension for JPEG is now *.jpg. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 256561] Katepart scrolls per paragraph rather than respecting the input device's scroll preference (i.e. n lines for a mouse wheel, pixel-by-pixel for touchpad)
https://bugs.kde.org/show_bug.cgi?id=256561 Nate Graham changed: What|Removed |Added Latest Commit|http://commits.kde.org/ktex | |teditor/5a1d633587bf961f40d | |5b1da02ca5ebe55a25f3b | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]
https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #6 from Maik Qualmann --- Gilles, how do you see that? Add additional modification date of the sidecar file in the DB? Or adjust the file modification date of the image file? I do not see another solution. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397082] The new media player icons rely on the icon theme instead of the desktop theme
https://bugs.kde.org/show_bug.cgi?id=397082 --- Comment #15 from Filip --- Im not a developer, but from what Ive read, yes, this was done on purpose. It seems the idea was to add new functionality and this was the side effect. I probably would have made the same decision in regards to implementing it, but I do however fully agree with you that this was handled rather poorly, seeing as how there should have been a PSA in advance that themes will be broken and will need to be updated. Surprisingly not even the 5.13 release notes give any warning. It does happen at times that all things non-Breeze get a bit overlooked, but usually it's nothing major and hopefully this and what happened with the network applet recently are a one off. But the point now is to fix it. Im a Manjaro user myself so I can tell you that Arc's package did not have the right media.svg icon for me. I had to get it from Github. Not sure about Breath, but im pretty certain that if a theme has received the update, you should be able to get the icons right. I mentioned the cache; varlesh says to do this: rm -rf ~/.cache/plasm* ~/.cache/ico* And you can always test things with an entirely new user as well. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374240] Krita crashes when creating a filter layer
https://bugs.kde.org/show_bug.cgi?id=374240 --- Comment #9 from Pablo --- Hi Raghavendra, I have just checked with version 4.1.0 and it works correctly, I have tried adding 2 new filter layers and they worked as expected. =) Do you want me to try anything else? And, of course, thanks a lot for the bug fixing ;) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 397154] Cannot build kcoreadons 5.49rc1
https://bugs.kde.org/show_bug.cgi?id=397154 --- Comment #9 from Michael Pyne --- Thanks for confirming the relation to pyqt5. The Python module generation feature has never worked on my system so I can't reproduce this myself. As things stand I'm still not sure if this is a bug in sip (though your version of sip should be sufficient for C++ class enum), a bug in kcoreaddons, or some other part of the toolchain (e.g. extra-cmake-module's FindPythonModuleGeneration module). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397395] Holes in the panel after changing the resolution
https://bugs.kde.org/show_bug.cgi?id=397395 --- Comment #2 from Dimitry Perov --- KDE Plasma: 5.12.6 KDE Frameworks: 5.47.0 Qt: 5.9.6 Kernel: 4.17.9-100.fc27.x86_64 Dual monitor: DVI: 1920×1080 (main) HDMI: 1680×1050 (TV) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 338333] Account problem
https://bugs.kde.org/show_bug.cgi?id=338333 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||6.0.0 --- Comment #3 from caulier.gil...@gmail.com --- Git commit 1d4a95bc3d36060a025b8950aaaca467253532bc by Gilles Caulier. Committed on 28/07/2014 at 05:57. Pushed by cgilles into branch 'master'. use SSL based url for flickr web service communication FIXED-IN: 4.2.0 M +4-4flickrexport/flickrtalker.cpp M +1-1flickrexport/flickrtalker.h http://commits.kde.org/kipi-plugins/1d4a95bc3d36060a025b8950aaaca467253532bc -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383987] Flickr tool no longer authenticates to Flickr
https://bugs.kde.org/show_bug.cgi?id=383987 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||6.0.0 --- Comment #3 from caulier.gil...@gmail.com --- Git commit 2dd941615dfc35684152e69be6437475633abe71 by Maik Qualmann. Committed on 20/08/2017 at 15:19. Pushed by mqualmann into branch 'master'. first step to porting Flickr service to OAuth removing no longer existing Zooomr service disable currently 23 service FIXED-IN: 5.7.0 M +2-1NEWS M +3-3common/libkipiplugins/CMakeLists.txt M +128 -610 flickr/flickrtalker.cpp M +14 -18 flickr/flickrtalker.h M +2-1flickr/flickrwidget.cpp M +39 -76 flickr/flickrwindow.cpp M +1-2flickr/flickrwindow.h M +4-43 flickr/plugin_flickr.cpp M +0-4flickr/plugin_flickr.h https://commits.kde.org/kipi-plugins/2dd941615dfc35684152e69be6437475633abe71 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397396] F11 as full-screen shortcut
https://bugs.kde.org/show_bug.cgi?id=397396 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- It is really easy to do that, but I'm kinda wary of changing default shortcuts at this point. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 397154] Cannot build kcoreadons 5.49rc1
https://bugs.kde.org/show_bug.cgi?id=397154 --- Comment #8 from Pawel --- For sure bug is related to python-pyqt5 (see: https://www.archlinux.org/packages/extra/x86_64/python-pyqt5/) and with PythonModuleGeneration optional dependency of kcoreaddons. I cannot build kcoreaddons (now 5.49) with this optional dependency and it builds without it well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397395] Holes in the panel after changing the resolution
https://bugs.kde.org/show_bug.cgi?id=397395 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from David Edmundson --- Please include frameworks version. You can find it in kinfocenter. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397082] The new media player icons rely on the icon theme instead of the desktop theme
https://bugs.kde.org/show_bug.cgi?id=397082 --- Comment #14 from rplanchu...@gmail.com --- Michał Dybczak, I agree with you. I opened https://bugs.kde.org/show_bug.cgi?id=395485 and I don't understand why a older bug is "duplicated" with a younger bud. And the bug is not resolved at all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397396] New: F11 as full-screen shortcut
https://bugs.kde.org/show_bug.cgi?id=397396 Bug ID: 397396 Summary: F11 as full-screen shortcut Product: krita Version: unspecified Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: ene...@gmail.com Target Milestone: --- Current shortcut is ctrl+shift+F. F11 is bit more common except libre office: - gimp - inskcape - digicam - rawtherapee - firefox This would allow to free ctrl+shift+F and use it for something like "filters", as F11 seems not to be assigned to anything (correct me if I'm wrong). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397395] New: Holes in the panel after changing the resolution
https://bugs.kde.org/show_bug.cgi?id=397395 Bug ID: 397395 Summary: Holes in the panel after changing the resolution Product: plasmashell Version: 5.12.6 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: battlepeas...@gmail.com Target Milestone: 1.0 Created attachment 114414 --> https://bugs.kde.org/attachment.cgi?id=114414&action=edit Right side of the taskbar After changing the resolution to smaller and returning the previous one, in the taskbar there are holes: on the bottom along the entire length, small on the right. On the screenshot you can see the blue color of the desktop. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 279115] Standard Mailing list doesn't thread properly
https://bugs.kde.org/show_bug.cgi?id=279115 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397358] Different type of Configure button
https://bugs.kde.org/show_bug.cgi?id=397358 --- Comment #4 from isalliswell --- That was quick! Thank you all for your time. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 279115] Standard Mailing list doesn't thread properly
https://bugs.kde.org/show_bug.cgi?id=279115 --- Comment #11 from Jan --- I figured out why this is happening: KMail only considers prefixed E-Mails for subject based threading. If it doesn't start with a "Re:" for example, it's not a thread. Bugzilla doesn't do that. So in the absence of that, it only uses In-Reply-To/Reference headers. And that doesn't work if the thread starter is missing, which imho is the wrong way to handle that. And even if it is prefixed, it will not consider messages with a time difference of 120 seconds. So if you managed to have a github conversation that is faster than that, it's not a thread either. This one in particular I really don't understand. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397373] Links no longer work after saving annotated PDF
https://bugs.kde.org/show_bug.cgi?id=397373 --- Comment #5 from Pastafarianist --- Original reporter here. I must say that your response time is very impressive, usually with open-source projects I have to wait for weeks or months for a fix. Great job! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382390] plasma-shell crash when search for app in installed app list
https://bugs.kde.org/show_bug.cgi?id=382390 André Verwijs changed: What|Removed |Added Keywords|drkonqi | Assignee|k...@davidedmundson.co.uk|h...@kde.org Component|general |Application Menu (Kicker) --- Comment #2 from André Verwijs --- Getting the same with Debian Linux - Plasma version 5.13.2 - KDE Frameworks 5.47.0 - QT 5.10.1 - Kernel version 4.17.0-1-amd64 when opening app menu and type random text, plasma restarts (screen tuns black for 4 second and returns again) but also sometimes crashes (not returning) added Backtrace as attachment.. "plasmashell-20180812-075135.kcrash.txt" .. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382390] plasma-shell crash when search for app in installed app list
https://bugs.kde.org/show_bug.cgi?id=382390 André Verwijs changed: What|Removed |Added CC||dutchgig...@gmail.com --- Comment #1 from André Verwijs --- Created attachment 114413 --> https://bugs.kde.org/attachment.cgi?id=114413&action=edit backtrace: plasmashell-20180812-075135.kcrash -- You are receiving this mail because: You are watching all bug changes.
