[akregator] [Bug 374108] New: Akregator - clicking some links in articles has no effect
https://bugs.kde.org/show_bug.cgi?id=374108 Bug ID: 374108 Summary: Akregator - clicking some links in articles has no effect Product: akregator Version: 5.3.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: naughtyp...@openmailbox.org Target Milestone: --- Clicking (left or middle) on some article links, whether in "feed summary" or "load full page" article viewer mode, has no effect -- does not open internally or externally (i.e. firefox). Right-clicking the SAME LINK and selecting an option to open in tab/external browser/etc. DOES work, however. Other links in the same article work normally. I.e. in "feed summary" viewing mode, the "Complete Story" link seems to always work, although I don't believe that link to be part of the article proper and is generated by Akregator. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 374107] New: Left sidebar handle is sometimes unusually wide
https://bugs.kde.org/show_bug.cgi?id=374107 Bug ID: 374107 Summary: Left sidebar handle is sometimes unusually wide Product: kontact Version: 5.2.3 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andr...@ubuntu.si Target Milestone: --- Created attachment 102973 --> https://bugs.kde.org/attachment.cgi?id=102973&action=edit Kontact stuck sidebar Sometimes when Kontact is started the left sidebar part (the one that allows you to resize the sidebar) becomes unusually wide (almost 40px, see screenshot). The sidebar can still be shown/hidden. The problem always resolves itself, restarting the program manually doesn't seem to do anything. Best Regards, Andrej -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371858] Occasional wrong desktop at startup
https://bugs.kde.org/show_bug.cgi?id=371858 --- Comment #15 from it...@inwind.it --- I haven't encountered the issue in a few days, even though there haven't been any updates to either Plasma (still on 5.8.4) or Qt (5.6.2). Unfortunately I can't confirm when exactly it got solved (it could've been about a week ago), so I can't tell which software updates contained the fix. Possibly related software that was updated recently: - KDE Frameworks (5.27 -> 5.28 2016-12-04 -> 5.29 on 2016-12-13) - KDE Applications (16.08.3 -> 16.11.90 on 2016-12-17) - KDE 4 Workspace (4.11.22 -> distro patch on 2016-12-10) - SDDM (0.14 -> distro patch on 2016-12-10, but doesn't seem to be related) If there's nothing else I can help with you may close the bug. Thanks for your work -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 --- Comment #17 from Philippe ROUBACH --- see my upstream report http://dev.exiv2.org/issues/1267 in particular comment #1 and http://dev.exiv2.org/issues/1068 interesting data about our problem -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 374106] New: KDevelop5 crush on open progect-name.kdev4 projects
https://bugs.kde.org/show_bug.cgi?id=374106 Bug ID: 374106 Summary: KDevelop5 crush on open progect-name.kdev4 projects Product: kdevelop Version: 5.0.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: anisim...@ada-ru.org Target Milestone: --- Application: kdevelop (5.0.1) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: I was just trying to open the project file with such content [Project] CreatedFrom=Makefile Manager=KDevCustomMakeManager Name=infosys The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f279002e900 (LWP 7827))] Thread 17 (Thread 0x7f276c8d1700 (LWP 7830)): #0 0x7f278cdcb49d in poll () from /lib64/libc.so.6 #1 0x7f2785c33314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2785c3342c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f278d6d732b in QEventDispatcherGlib::processEvents (this=0x7f2768c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f278d684fdb in QEventLoop::exec (this=this@entry=0x7f276c8d0ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f278d4bff1a in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7f278f1f21d5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f278d4c49e9 in QThreadPrivate::start (arg=0x7f278f45ace0) at thread/qthread_unix.cpp:341 #8 0x7f27868ab734 in start_thread () from /lib64/libpthread.so.0 #9 0x7f278cdd3d3d in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f27563be700 (LWP 7831)): #0 0x7f27868b00af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f275d720533 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f275d71fd57 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f27868ab734 in start_thread () from /lib64/libpthread.so.0 #4 0x7f278cdd3d3d in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f2755587700 (LWP 7832)): #0 0x7f27868b0458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f278d4c55a8 in QWaitConditionPrivate::wait_relative (time=1000, this=0xbf5990) at thread/qwaitcondition_unix.cpp:126 #2 QWaitConditionPrivate::wait (time=1000, this=0xbf5990) at thread/qwaitcondition_unix.cpp:134 #3 QWaitCondition::wait (this=this@entry=0xbb8868, mutex=mutex@entry=0xbb8870, time=time@entry=1000) at thread/qwaitcondition_unix.cpp:208 #4 0x7f278af1acc3 in KDevelop::DUChainPrivate::CleanupThread::run (this=0xbb8850) at /usr/src/debug/kdevplatform-5.0.1/language/duchain/duchain.cpp:282 #5 0x7f278d4c49e9 in QThreadPrivate::start (arg=0xbb8850) at thread/qthread_unix.cpp:341 #6 0x7f27868ab734 in start_thread () from /lib64/libpthread.so.0 #7 0x7f278cdd3d3d in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f274a9de700 (LWP 7860)): #0 QTimerInfoList::updateCurrentTime (this=this@entry=0x7f27440012e0) at kernel/qtimerinfo_unix.cpp:85 #1 0x7f278d6d5f05 in QTimerInfoList::timerWait (this=0x7f27440012e0, tm=...) at kernel/qtimerinfo_unix.cpp:381 #2 0x7f278d6d70fe in timerSourcePrepareHelper (timeout=0x7f274a9ddaf4, src=) at kernel/qeventdispatcher_glib.cpp:126 #3 timerSourcePrepare (source=, timeout=0x7f274a9ddaf4) at kernel/qeventdispatcher_glib.cpp:159 #4 0x7f2785c3295d in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #5 0x7f2785c33230 in ?? () from /usr/lib64/libglib-2.0.so.0 #6 0x7f2785c3342c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #7 0x7f278d6d732b in QEventDispatcherGlib::processEvents (this=0x7f2744002e00, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #8 0x7f278d684fdb in QEventLoop::exec (this=this@entry=0x7f274a9ddcb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #9 0x7f278d4bff1a in QThread::exec (this=) at thread/qthread.cpp:500 #10 0x7f27827f59b8 in ?? () from /usr/lib64/libQt5Qml.so.5 #11 0x7f278d4c49e9 in QThreadPrivate::start (arg=0x125eb20) at thread/qthread_unix.cpp:341 #12 0x7f27868ab734 in start_thread () from /lib64/libpthread.so.0 #13 0x7f278cdd3d3d in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f274b1df700 (LWP 7931)): #0 0x7f278cdcb49d in poll () from /lib64/libc.so.6 #1 0x7f2785c33314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2785c3342c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f278d6d732b in QEventDispatcherGlib::processEvents (this=0x7f273c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f278d68
[kwin] [Bug 374105] New: Kwin crashes while starting wayland session
https://bugs.kde.org/show_bug.cgi?id=374105 Bug ID: 374105 Summary: Kwin crashes while starting wayland session Product: kwin Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 102972 --> https://bugs.kde.org/attachment.cgi?id=102972&action=edit Logs during the kwin crash (containing stack trace) When I choose the plasma-wayland session in sddm and log in, the session crashes and I am brought back to the sddm screen. Output of journalctl -f shows that kwon_wayland crashes. I have attached the logs as a text file. This is in a virtualbox VM with 3D acceleration disabled. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374105] Kwin crashes while starting wayland session
https://bugs.kde.org/show_bug.cgi?id=374105 kishor...@gmail.com changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374008] Any selection tool will not allow a selected item to be transformed, and instead select a portion off of the canvas.
https://bugs.kde.org/show_bug.cgi?id=374008 --- Comment #4 from Elara Methone --- Created attachment 102967 --> https://bugs.kde.org/attachment.cgi?id=102967&action=edit 2.PNG --- Comment #5 from Elara Methone --- Created attachment 102968 --> https://bugs.kde.org/attachment.cgi?id=102968&action=edit 3.PNG --- Comment #6 from Elara Methone --- Created attachment 102969 --> https://bugs.kde.org/attachment.cgi?id=102969&action=edit 4.PNG --- Comment #7 from Elara Methone --- Created attachment 102970 --> https://bugs.kde.org/attachment.cgi?id=102970&action=edit 5.PNG --- Comment #8 from Elara Methone --- Created attachment 102971 --> https://bugs.kde.org/attachment.cgi?id=102971&action=edit 6.PNG -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374008] Any selection tool will not allow a selected item to be transformed, and instead select a portion off of the canvas.
https://bugs.kde.org/show_bug.cgi?id=374008 --- Comment #3 from Elara Methone --- Alright, I have collected a series of pictures that describe the situation that happened twice now. In picture 1, everything is going as normal. I can select certain portions of the picture and transform them. Picture 2: you can see I have selected a small portion of the picture. This is on a new layer, zoomed in more. Picture 3: there appears to be a random line in the top left corner of the selection box that I did not include. I erased it later. Picture 4: while it's not visible, I only used the free select tool around the head, yet the transform tool selected the entire layer. Picture 5: I used the free select tool around my writing only, and for some reason it worked in selecting only what I chose. Picture 6: everything snapped back to normal, and I could select certain portions again. I saved and reopened the program. There doesn't seem to be a set time when this happens, it just happens at random. I hope these screenshots were able to help. On Fri, Dec 23, 2016 at 2:56 PM, Elara Methone wrote: > Yes, I will try to take screenshots and recreate this issue. I apologize > for any inconvenience. > > On Thu, Dec 22, 2016 at 3:35 AM, Boudewijn Rempt > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=374008 >> >> Boudewijn Rempt changed: >> >>What|Removed |Added >> >> >> CC||b...@valdyas.org >> Resolution|--- |WAITINGFORINFO >>Platform|unspecified |MS Windows >> Status|UNCONFIRMED |NEEDSINFO >> >> --- Comment #1 from Boudewijn Rempt --- >> Hi Elara, >> >> Could you add a screenshot or video? I've just tried to reproduce this >> issue: >> >> * created a new image >> * added some lines >> * selected an ellipse >> * select the transform tool >> >> And found the transform tool, as expected working on only the selection, >> and >> the cut tool cutting only the ellipse. >> >> So I'm wondering whether I misunderstood you, or whether you're doing >> something >> really different... >> >> -- >> You are receiving this mail because: >> You reported the bug. > > > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374104] New: Low resolution icons in task-switcher in kde
https://bugs.kde.org/show_bug.cgi?id=374104 Bug ID: 374104 Summary: Low resolution icons in task-switcher in kde Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-tabbox Assignee: kwin-bugs-n...@kde.org Reporter: abhigeni...@gmail.com Target Milestone: --- I am using kde neon 5.8.4 user edition. When I press switch windows ALT+TAB, the icons that appear are distorted most of times. I have described the issue in detail here: http://askubuntu.com/questions/864056/low-resolution-icons-in-task-switcher-in-kde -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 373486] okular crashes every time gnome desktop switches between multiple screens
https://bugs.kde.org/show_bug.cgi?id=373486 --- Comment #5 from Naitree Zhu --- Sorry, here is the rpm info about libkscreen: Name: libkscreen Epoch : 1 Version : 1.0.5 Release : 9.fc25 Architecture: x86_64 Install Date: Sunday, December 04, 2016 AM08:21:18 CST Group : Unspecified Size: 267636 License : GPLv2+ Signature : RSA/SHA256, Tuesday, April 26, 2016 AM10:37:21 CST, Key ID 4089d8f2fdb19c98 Source RPM : libkscreen-1.0.5-9.fc25.src.rpm Build Date : Thursday, April 21, 2016 AM07:02:32 CST Build Host : buildvm-10-nfs.phx2.fedoraproject.org Relocations : (not relocatable) Packager: Fedora Project Vendor : Fedora Project URL : https://quickgit.kde.org/?p=libkscreen.git Summary : Display configuration library Description : LibKScreen is a library that provides access to current configuration of connected displays and ways to change the configuration. On Fri, Dec 23, 2016 at 7:57 PM, Albert Astals Cid wrote: > https://bugs.kde.org/show_bug.cgi?id=373486 > > --- Comment #4 from Albert Astals Cid --- > Can you please give me the rpm package version of libkscreen > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365327] Support macOS Sierra (10.12)
https://bugs.kde.org/show_bug.cgi?id=365327 Mark Abraham changed: What|Removed |Added CC||mark.j.abra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 373850] Highlighting ranges often wrong for constructors/__call__()/indexing.
https://bugs.kde.org/show_bug.cgi?id=373850 Francis Herne changed: What|Removed |Added Priority|HI |NOR -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 373850] Highlighting ranges often wrong for constructors/__call__()/indexing.
https://bugs.kde.org/show_bug.cgi?id=373850 --- Comment #2 from Francis Herne --- The very frequent errors were my fault; I introduced a bug in https://cgit.kde.org/kdev-python.git/commit/?id=94ab1ee Fixed that in https://commits.kde.org/kdev-python/9ba8942 There are remaining glitches if: - The bracket doesn't immediately follow what's being called: `foo (arg)` <- the space is highlighted. Uncommon. - The expression being called/subscripted has an incorrect range: ``` class A: def __call__(self): return 10 aaa = [A()] bbb = aaa[000]() # The middle '0' is highlighted. ``` I think these have always existed, but the second type is more common after 9ba8942 because we show uses after many more subscript expressions, which are most commonly broken. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 365034] The Filechoosing-dialoug cannot handly folders to compare anymore
https://bugs.kde.org/show_bug.cgi?id=365034 Kevin Kofler changed: What|Removed |Added CC||pjsingh5...@gmail.com --- Comment #1 from Kevin Kofler --- *** Bug 374102 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 374102] Unable to open directories for comparison
https://bugs.kde.org/show_bug.cgi?id=374102 Kevin Kofler changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Kevin Kofler --- *** This bug has been marked as a duplicate of bug 365034 *** -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 374103] New: Amarok does not open
https://bugs.kde.org/show_bug.cgi?id=374103 Bug ID: 374103 Summary: Amarok does not open Product: amarok Version: 2.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: greenisagoodco...@gmail.com Target Milestone: 2.9 Application: amarok (2.8.0) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Trying to open amarok upon startup. This was after I was trying to create a new playlist, "do you groove"?, and add earth wind and fire song to it, "Yearnin' Learning'". Now it won't open at all, so sad. Running Arch with KDE, all current, minimum package install, lenovo x220. The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Bus error Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb1849125c0 (LWP 10825))] Thread 12 (Thread 0x7fb12f7fe700 (LWP 10837)): #0 0x7fb18007910f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb181bcd5c6 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQtCore.so.4 #2 0x7fb17d247df0 in () at /usr/lib/libthreadweaver.so.4 #3 0x7fb17d24a653 in () at /usr/lib/libthreadweaver.so.4 #4 0x7fb17d24914d in ThreadWeaver::Thread::run() () at /usr/lib/libthreadweaver.so.4 #5 0x7fb181bcd05a in () at /usr/lib/libQtCore.so.4 #6 0x7fb180073454 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb1815037df in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fb12700 (LWP 10836)): #0 0x7fb18007910f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb181bcd5c6 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQtCore.so.4 #2 0x7fb17d247df0 in () at /usr/lib/libthreadweaver.so.4 #3 0x7fb17d24a653 in () at /usr/lib/libthreadweaver.so.4 #4 0x7fb17d24914d in ThreadWeaver::Thread::run() () at /usr/lib/libthreadweaver.so.4 #5 0x7fb181bcd05a in () at /usr/lib/libQtCore.so.4 #6 0x7fb180073454 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb1815037df in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fb13cad9700 (LWP 10835)): #0 0x7fb18007910f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb181bcd5c6 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQtCore.so.4 #2 0x7fb17d247df0 in () at /usr/lib/libthreadweaver.so.4 #3 0x7fb17d24a653 in () at /usr/lib/libthreadweaver.so.4 #4 0x7fb17d24914d in ThreadWeaver::Thread::run() () at /usr/lib/libthreadweaver.so.4 #5 0x7fb181bcd05a in () at /usr/lib/libQtCore.so.4 #6 0x7fb180073454 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb1815037df in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fb13d2da700 (LWP 10834)): #0 0x7fb18007910f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb181bcd5c6 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQtCore.so.4 #2 0x7fb17d247df0 in () at /usr/lib/libthreadweaver.so.4 #3 0x7fb17d24a653 in () at /usr/lib/libthreadweaver.so.4 #4 0x7fb17d24914d in ThreadWeaver::Thread::run() () at /usr/lib/libthreadweaver.so.4 #5 0x7fb181bcd05a in () at /usr/lib/libQtCore.so.4 #6 0x7fb180073454 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb1815037df in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fb13dadb700 (LWP 10833)): #0 0x7fb18007910f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb181bcd5c6 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQtCore.so.4 #2 0x7fb17d247df0 in () at /usr/lib/libthreadweaver.so.4 #3 0x7fb17d24a653 in () at /usr/lib/libthreadweaver.so.4 #4 0x7fb17d24914d in ThreadWeaver::Thread::run() () at /usr/lib/libthreadweaver.so.4 #5 0x7fb181bcd05a in () at /usr/lib/libQtCore.so.4 #6 0x7fb180073454 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb1815037df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fb13e2dc700 (LWP 10832)): #0 0x7fb18007910f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb181bcd5c6 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQtCore.so.4 #2 0x7fb17d247df0 in () at /usr/lib/libthreadweaver.so.4 #3 0x7fb17d24a653 in () at /usr/lib/libthreadweaver.so.4 #4 0x7fb17d24914d in ThreadWeaver::Thread::run() () at /usr/lib/libthreadweaver.so.4 #5 0x7fb181bcd05a in () at /usr/lib/libQtCore.so.4 #6 0x7fb180073454 in start_thread () at /usr/lib/libpthread.so.0 #
[digikam] [Bug 366391] rotating an image seems to forget to reset the orientation flag
https://bugs.kde.org/show_bug.cgi?id=366391 --- Comment #11 from Nico Kruber --- with the 5.4.0 package from 22/12/2016: * using auto-rotate does not touch the jpg file at all but only seems to set the orientation flag in digikam's DB and thus the file is shown in the wrong orientation in digikam itself. (this is some other bug, I guess) * using rotate left/right the file's content is rotated but the exif data in the jpg is not changed (only in the sidecar file). It is shown correctly in Digikam but is wrong in programs only using the exif data from the jpg. Please let me sum up my desired change: the content of the file needs to be consistent with the exif data in the file, so if the content is changed, e.g. by allowing rotation, there is no point in not changing the metadata along with it, despite the setting of where to save metadata. -- You are receiving this mail because: You are watching all bug changes.
[kdm] [Bug 342299] Keyboard Layout not persistent
https://bugs.kde.org/show_bug.cgi?id=342299 Christoph Feck changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 374102] Unable to open directories for comparison
https://bugs.kde.org/show_bug.cgi?id=374102 pjsingh5...@gmail.com changed: What|Removed |Added CC||pjsingh5...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 374102] New: Unable to open directories for comparison
https://bugs.kde.org/show_bug.cgi?id=374102 Bug ID: 374102 Summary: Unable to open directories for comparison Product: kompare Version: 4.1.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kompare-de...@kde.org Reporter: pjsingh5...@gmail.com Target Milestone: --- In the "Open File" dialog, you are not able to select a directory for comparison. You should be able to select a file OR directory. NOT WORKING (FOR DIRECTORIES)... When you select a directory in the "Open File" dialog, and click the Open button, the "Open File" dialog does not close, and the directory path is not entered in the "Source" or "Destination" text fields of Kompare's "Compare Files or Folders" dialog. Instead, the selected directory opens in the "Open File" dialog. WORKING (FOR FILES)... When you select a file in the "Open File" dialog, and click the Open button, the "Open File" dialog closes, and the file path is populated in the "Source" or "Destination" text fields of Kompare's "Compare Files or Folders" dialog. EXPECTED BEHAVIOR (FOR FILES & DIRECTORIES)... When you select a file or directory in the "Open File" dialog, and click the Open button, the "Open File" dialog closes, and the file path or directory path is populated in the "Source" or "Destination" text fields of Kompare's "Compare Files or Folders" dialog. $ uname -a Linux PS001 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release --all No LSB modules are available. Distributor ID: neon Description:KDE neon User Edition 5.8 Release:16.04 Codename: xenial -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374014] Plasmashell renders fonts in QT5-Apps pixelated
https://bugs.kde.org/show_bug.cgi?id=374014 --- Comment #8 from hotschi --- ~/.config/kdeglobals for broken font-rendering: [$Version] update_info=fonts_global.upd:Fonts_Global [Appmenu Style] Style=InApplication [ColorEffects:Disabled] Color=56,56,56 ColorAmount=0 ColorEffect=0 ContrastAmount=0.65 ContrastEffect=1 IntensityAmount=0.1 IntensityEffect=2 [ColorEffects:Inactive] ChangeSelectionColor=true Color=112,111,110 ColorAmount=0.025 ColorEffect=2 ContrastAmount=0.1 ContrastEffect=2 Enable=false IntensityAmount=0 IntensityEffect=0 [Colors:Button] BackgroundAlternate=77,77,77 BackgroundNormal=49,54,59 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=61,174,233 ForegroundInactive=189,195,199 ForegroundLink=41,128,185 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=239,240,241 ForegroundPositive=39,174,96 ForegroundVisited=127,140,141 [Colors:Complementary] BackgroundAlternate=59,64,69 BackgroundNormal=49,54,59 DecorationFocus=30,146,255 DecorationHover=61,174,230 ForegroundActive=246,116,0 ForegroundInactive=175,176,179 ForegroundLink=61,174,230 ForegroundNegative=237,21,21 ForegroundNeutral=201,206,59 ForegroundNormal=239,240,241 ForegroundPositive=17,209,22 ForegroundVisited=61,174,230 [Colors:Selection] BackgroundAlternate=29,153,243 BackgroundNormal=61,174,233 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=252,252,252 ForegroundInactive=239,240,241 ForegroundLink=253,188,75 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=239,240,241 ForegroundPositive=39,174,96 ForegroundVisited=189,195,199 [Colors:Tooltip] BackgroundAlternate=77,77,77 BackgroundNormal=49,54,59 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=61,174,233 ForegroundInactive=189,195,199 ForegroundLink=41,128,185 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=239,240,241 ForegroundPositive=39,174,96 ForegroundVisited=127,140,141 [Colors:View] BackgroundAlternate=49,54,59 BackgroundNormal=35,38,41 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=61,174,233 ForegroundInactive=189,195,199 ForegroundLink=41,128,185 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=239,240,241 ForegroundPositive=39,174,96 ForegroundVisited=127,140,141 [Colors:Window] BackgroundAlternate=77,77,77 BackgroundNormal=49,54,59 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=61,174,233 ForegroundInactive=189,195,199 ForegroundLink=41,128,185 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=239,240,241 ForegroundPositive=39,174,96 ForegroundVisited=127,140,141 [DirSelect Dialog] DirSelectDialog Size=640,480 History Items[$e]=file:///media/Daten/Musik,file:///media/Daten/OwnCloud,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung19,file:$HOME,file:$HOME/Sortieren,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung17,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung16,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung15,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung14,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung13,file:///media/Daten/Downloads/Torrents,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung 12.1,file:///media/Daten/OwnCloud/FH/1. Semester/IP1/Uebungen/Uebung09/Damenproblem [General] BrowserApplication=firefox.desktop ColorScheme=Breeze Dark Name=Breeze Dark dbfile=/home/hansi/.mozilla/firefox/jkeq00f7.default/places.sqlite fixed=Hack,12,-1,5,50,0,0,0,0,0 font=Noto Sans,14,-1,5,50,0,0,0,0,0 menuFont=Noto Sans,14,-1,5,50,0,0,0,0,0 shadeSortColumn=true smallestReadableFont=Noto Sans,10,-1,5,50,0,0,0,0,0 toolBarFont=Noto Sans,12,-1,5,50,0,0,0,0,0 widgetStyle=Breeze [Icons] Theme=breeze-dark [KDE] ColorScheme=Breeze DoubleClickInterval=400 LookAndFeelPackage=org.kde.breezedark.desktop ShowDeleteCommand=false ShowIconsInMenuItems=true ShowIconsOnPushButtons=true SingleClick=false StartDragDist=1 StartDragTime=500 WheelScrollLines=5 contrast=4 widgetStyle=Breeze [KFileDialog Settings] Automatically select filename extension=false Breadcrumb Navigation=true Decoration position=0 LocationCombo Completionmode=5 PathCombo Completionmode=5 Previews=false Show Bookmarks=false Show Full Path=false Show Preview=false Show Speedbar=true Show hidden files=false Sort by=Name Sort directories first=true Sort reversed=false Speedbar Width=252 View Style=Simple listViewIconSize=0 [KScreen] ScaleFactor=1.4 ScreenScaleFactors=eDP1=1.4;DP1=1.4;DP2=1.4;HDMI1=1.4;HDMI2=1.4;VIRTUAL1=1.4; [KShortcutsDialog Settings] Dialog Size=631,480 [PreviewSettings] MaximumRemoteSize=0 [Toolbar style] ToolButtonStyle=TextBesideIcon ToolButtonStyleOtherToolbars=TextBesideIcon [Translations] LANGUAGE=de:en_US [WM] activeBackground=49,54,59 activeBlend=255,255,255 activeFont=Noto Sans,14,-1,5,50,0,0,0,0,0 activeForeground=239,240,241 inactiveBackground=49,54,59 inactiveBlend=75,71,67 inactiveForeground=12
[plasmashell] [Bug 374014] Plasmashell renders fonts in QT5-Apps pixelated
https://bugs.kde.org/show_bug.cgi?id=374014 --- Comment #7 from hotschi --- ~/.config/kdeglobals [$Version] update_info=fonts_global.upd:Fonts_Global [Appmenu Style] Style=InApplication [ColorEffects:Disabled] Color=56,56,56 ColorAmount=0 ColorEffect=0 ContrastAmount=0.65 ContrastEffect=1 IntensityAmount=0.1 IntensityEffect=2 [ColorEffects:Inactive] ChangeSelectionColor=true Color=112,111,110 ColorAmount=0.025 ColorEffect=2 ContrastAmount=0.1 ContrastEffect=2 Enable=false IntensityAmount=0 IntensityEffect=0 [Colors:Button] BackgroundAlternate=77,77,77 BackgroundNormal=49,54,59 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=61,174,233 ForegroundInactive=189,195,199 ForegroundLink=41,128,185 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=239,240,241 ForegroundPositive=39,174,96 ForegroundVisited=127,140,141 [Colors:Complementary] BackgroundAlternate=59,64,69 BackgroundNormal=49,54,59 DecorationFocus=30,146,255 DecorationHover=61,174,230 ForegroundActive=246,116,0 ForegroundInactive=175,176,179 ForegroundLink=61,174,230 ForegroundNegative=237,21,21 ForegroundNeutral=201,206,59 ForegroundNormal=239,240,241 ForegroundPositive=17,209,22 ForegroundVisited=61,174,230 [Colors:Selection] BackgroundAlternate=29,153,243 BackgroundNormal=61,174,233 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=252,252,252 ForegroundInactive=239,240,241 ForegroundLink=253,188,75 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=239,240,241 ForegroundPositive=39,174,96 ForegroundVisited=189,195,199 [Colors:Tooltip] BackgroundAlternate=77,77,77 BackgroundNormal=49,54,59 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=61,174,233 ForegroundInactive=189,195,199 ForegroundLink=41,128,185 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=239,240,241 ForegroundPositive=39,174,96 ForegroundVisited=127,140,141 [Colors:View] BackgroundAlternate=49,54,59 BackgroundNormal=35,38,41 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=61,174,233 ForegroundInactive=189,195,199 ForegroundLink=41,128,185 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=239,240,241 ForegroundPositive=39,174,96 ForegroundVisited=127,140,141 [Colors:Window] BackgroundAlternate=77,77,77 BackgroundNormal=49,54,59 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=61,174,233 ForegroundInactive=189,195,199 ForegroundLink=41,128,185 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=239,240,241 ForegroundPositive=39,174,96 ForegroundVisited=127,140,141 [DirSelect Dialog] DirSelectDialog Size=640,480 History Items[$e]=file:///media/Daten/Musik,file:///media/Daten/OwnCloud,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung19,file:$HOME,file:$HOME/Sortieren,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung17,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung16,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung15,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung14,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung13,file:///media/Daten/Downloads/Torrents,file:///media/Daten/OwnCloud/FH/2. Semester/IP2/Uebung 12.1,file:///media/Daten/OwnCloud/FH/1. Semester/IP1/Uebungen/Uebung09/Damenproblem [General] BrowserApplication=firefox.desktop ColorScheme=Breeze Dark Name=Breeze Dark dbfile=/home/hansi/.mozilla/firefox/jkeq00f7.default/places.sqlite fixed=Hack,12,-1,5,50,0,0,0,0,0 font=Noto Sans,14,-1,5,50,0,0,0,0,0 menuFont=Noto Sans,14,-1,5,50,0,0,0,0,0 shadeSortColumn=true smallestReadableFont=Noto Sans,10,-1,5,50,0,0,0,0,0 toolBarFont=Noto Sans,12,-1,5,50,0,0,0,0,0 widgetStyle=Breeze [Icons] Theme=breeze-dark [KDE] ColorScheme=Breeze DoubleClickInterval=400 LookAndFeelPackage=org.kde.breezedark.desktop ShowDeleteCommand=false ShowIconsInMenuItems=true ShowIconsOnPushButtons=true SingleClick=false StartDragDist=1 StartDragTime=500 WheelScrollLines=5 contrast=4 widgetStyle=Breeze [KFileDialog Settings] Automatically select filename extension=false Breadcrumb Navigation=true Decoration position=0 LocationCombo Completionmode=5 PathCombo Completionmode=5 Previews=false Show Bookmarks=false Show Full Path=false Show Preview=false Show Speedbar=true Show hidden files=false Sort by=Name Sort directories first=true Sort reversed=false Speedbar Width=252 View Style=Simple listViewIconSize=0 [KScreen] ScaleFactor=1 ScreenScaleFactors=eDP1=1;DP1=1;DP2=1;HDMI1=1;HDMI2=1;VIRTUAL1=1; [KShortcutsDialog Settings] Dialog Size=631,480 [PreviewSettings] MaximumRemoteSize=0 [Toolbar style] ToolButtonStyle=TextBesideIcon ToolButtonStyleOtherToolbars=TextBesideIcon [Translations] LANGUAGE=de:en_US [WM] activeBackground=49,54,59 activeBlend=255,255,255 activeFont=Noto Sans,14,-1,5,50,0,0,0,0,0 activeForeground=239,240,241 inactiveBackground=49,54,59 inactiveBlend=75,71,67 inactiveForeground=127,140,141 -- You are receiving this mai
[digikam] [Bug 320666] Add search of similar images outside digiKam collections [patch]
https://bugs.kde.org/show_bug.cgi?id=320666 --- Comment #13 from caulier.gil...@gmail.com --- Great. it will be perfect. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 --- Comment #16 from Philippe ROUBACH --- you have not the right to manage the album only to download the video. i assume google photo grant my privacy and take away all about privacy. so you don't gate the original video. i can't upload it to bugs.kde.org because this video have a size of 22 MB i will try to cut it and upload it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374095] QOffscreenSurface created off the main/gui thread
https://bugs.kde.org/show_bug.cgi?id=374095 Jean-Baptiste Mardelle changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Jean-Baptiste Mardelle --- Thanks for your report. In fact the same warning displays on the windows version and I also think we should take care of this -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 --- Comment #15 from Maik Qualmann --- In this video after the download are no GPS data. See exiftool output from Gilles Comment 12. https://goo.gl/photos/4732E3QexiVnHbSt8 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 365133] Consistency check failure: currency of a category has no price set for 1900-01-01
https://bugs.kde.org/show_bug.cgi?id=365133 m...@azu.ca changed: What|Removed |Added CC||m...@azu.ca --- Comment #1 from m...@azu.ca --- I have a fix for this bug but I am concerned about potential side-effects. My fix is to exclude accounts of type IncomeExpense from the consistency check for missing prices on the opening date (mymoneyfile.cpp:2337). Is there any reason that a IncomeExpense category in a foreign (non-base) currency would require a price on the 'fake' account opening date of 1900-01-01? If not, I'll submit a review request. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 331891] Broken references-chain (email header) leads to new Thread
https://bugs.kde.org/show_bug.cgi?id=331891 Matt Whitlock changed: What|Removed |Added CC||k...@mattwhitlock.name --- Comment #3 from Matt Whitlock --- Still reproducible in KMail 5.4.0 too. Quite annoying, as this breaks the most common threading scenario: Bob emails me, I reply back, Bob replies to my reply. Bob's reply is not threaded under Bob's original message, as the intervening message (my reply) is in my Sent box, not in my Inbox. Threading should consider *all* of the message IDs given in the "References" header if a message identified by the "In-Reply-To" header is not found. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 --- Comment #14 from Philippe ROUBACH --- there is gps data roubach@linux-9vc6:~/Documents/photo/Images/mes_depots/urbanisme_architecture/Musée_FLV> exiftool -a -u -g1 20161223T153428.mp4 ExifTool ExifTool Version Number : 10.20 System File Name : 20161223T153428.mp4 Directory : . File Size : 23 MB File Modification Date/Time : 2016:12:23 15:34:28+01:00 File Access Date/Time : 2016:12:23 15:54:39+01:00 File Inode Change Date/Time : 2016:12:23 15:54:39+01:00 File Permissions: rwx-- File File Type : MP4 File Type Extension : mp4 MIME Type : video/mp4 QuickTime Major Brand : MP4 v2 [ISO 14496-14] Minor Version : 0.0.0 Compatible Brands : isom, mp42 Movie Header Version: 0 Create Date : 2016:12:10 12:00:02 Modify Date : 2016:12:10 12:00:02 Time Scale : 1000 Duration: 11.12 s Preferred Rate : 1 Preferred Volume: 100.00% Matrix Structure: 1 0 0 0 1 0 0 0 1 Preview Time: 0 s Preview Duration: 0 s Poster Time : 0 s Selection Time : 0 s Selection Duration : 0 s Current Time: 0 s Next Track ID : 3 GPS Coordinates : 48 deg 52' 35.76" N, 2 deg 15' 52.20" E Handler Type: Metadata Tags Com Android Version : 6.0.1 Free: (Binary data 399751 bytes, use -b option to extract) Movie Data Size : 23630064 Movie Data Offset : 405185 Movie Data : (Binary data 23630064 bytes, use -b option to extract) Track1 Track Header Version: 0 Track Create Date : 2016:12:10 12:00:02 Track Modify Date : 2016:12:10 12:00:02 Track ID: 1 Track Duration : 11.03 s Track Layer : 0 Track Volume: 0.00% Matrix Structure: 1 0 0 0 1 0 0 0 1 Image Width : 1920 Image Height: 1080 Media Header Version: 0 Media Create Date : 2016:12:10 12:00:02 Media Modify Date : 2016:12:10 12:00:02 Media Time Scale: 9 Media Duration : 11.03 s Handler Type: Video Track Handler Description : VideoHandle Graphics Mode : srcCopy Op Color: 0 0 0 Compressor ID : avc1 Source Image Width : 1920 Source Image Height : 1080 X Resolution: 72 Y Resolution: 72 Bit Depth : 24 Unknown avcC: (Binary data 34 bytes, use -b option to extract) Pixel Aspect Ratio : 65536:65536 Video Frame Rate: 30.021 Sync Sample Table : (Binary data 52 bytes, use -b option to extract) Sample Sizes: (Binary data 1336 bytes, use -b option to extract) Sample To Chunk : (Binary data 44 bytes, use -b option to extract) Chunk Offset: (Binary data 52 bytes, use -b option to extract) Track2 Track Header Version: 0 Track Create Date : 2016:12:10 12:00:02 Track Modify Date : 2016:12:10 12:00:02 Track ID: 2 Track Duration : 11.12 s Track Layer : 0 Track Volume: 100.00% Matrix Structure: 1 0 0 0 1 0 0 0 1 Media Header Version: 0 Media Create Date : 2016:12:10 12:00:02 Media Modify Date : 2016:12:10 12:00:02 Media Time Scale: 48000 Media Duration : 11.11 s Handler Type: Audio Track Handler Description : SoundHandle Balance : 0 Audio Format: mp4a Audio Channels : 1 Audio Bits Per Sample : 16 Audio Sample Rate : 48000 Unknown esds: (Binary data 31 bytes, use -b option to extract) Time To Sample Table: (Binary data 24 bytes, use -b option to extract) Sample Sizes: (Binary data 2096 bytes, use -b option to extract) Sample To Chunk : (Binary data 44 bytes, use -b option to extract) Chunk Offset: (Binary data 56 bytes, use -b option to extract) Composite Avg Bitrate : 17 Mbps GPS Latitude: 48 deg 52' 35.76" N GPS Longitud
[krunner] [Bug 211409] Support Keyboard shortcuts for each runner
https://bugs.kde.org/show_bug.cgi?id=211409 k...@web.de changed: What|Removed |Added CC||k...@web.de --- Comment #6 from k...@web.de --- I have a solution for this using dbus. To start the shell runner, you can run this command in a terminal: qdbus-qt5 org.kde.krunner /App displaySingleRunner shell The name of this runner is "shell". The names of the other runners are found with grep 'X-KDE-PluginInfo-Name=' /usr/share/kservices5/plasma-runner-* You can create keyboard shortcuts to a dbus call directly in Systemsettings > Shorcuts > Own shortcuts Right click in list > New > Global shortcut > D-Bus-call Then fill the form with org.kde.krunner /App displaySingleRunner shell Replace shell with whatever the name of the runners is, for example bookmarks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364386] The freehand tool doesn't work when I am trying to finger paint on the touch screen
https://bugs.kde.org/show_bug.cgi?id=364386 --- Comment #7 from Sofia Aparicio --- When my computer is in tablet mode, the brush tool in freehand doesn't work. It does not draw at all. When it is in regular laptop mode, the brush tool only works while using the mousepad. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364386] The freehand tool doesn't work when I am trying to finger paint on the touch screen
https://bugs.kde.org/show_bug.cgi?id=364386 Sofia Aparicio changed: What|Removed |Added CC||saparici...@knights.ucf.edu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 374101] New: Alt + up not comfortable usable
https://bugs.kde.org/show_bug.cgi?id=374101 Bug ID: 374101 Summary: Alt + up not comfortable usable Product: dolphin Version: 16.08.2 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: hb_...@brueningserver.de Target Milestone: --- Alt + Up would be much more comfortable if the folder where we are coming from is the selected one. The use case is very fast navigating through the folder structure just by keyboard: Press Enter to enter a folder. Do something. Press Alt + Up, Down, Enter to enter the next folder. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 320666] Add search of similar images outside digiKam collections [patch]
https://bugs.kde.org/show_bug.cgi?id=320666 --- Comment #12 from Mario Frank --- (In reply to caulier.gilles from comment #10) > I discovered a serious problem to Slideshow and Presentation with some video > file to handle. So postponed is the best way. > > The doc is not a problem. > > For i18n, if patch over GUI is applied quickly and not touched later, it's > acceptable. Patching code not relevant of i18n is not a problem of course. > > Gilles Hey, after making some more tests, I patched the master branch. There is only one change which has to be localised, i.e. the sort role "By Similarity". I will make more tests in the next days and see if I can generate automated tests for the test suite. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329854] digiKam doesn't rotate video thumbnail
https://bugs.kde.org/show_bug.cgi?id=329854 --- Comment #18 from Maik Qualmann --- Git commit 7ce05cef9ce1260aa75cdfa909be57e7aaa49fc5 by Maik Qualmann. Committed on 23/12/2016 at 21:14. Pushed by mqualmann into branch 'master'. add manual rotating the video output with the right mouse button M +39 -6app/views/mediaplayerview.cpp M +1-0app/views/mediaplayerview.h https://commits.kde.org/digikam/7ce05cef9ce1260aa75cdfa909be57e7aaa49fc5 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371353] Undo broken when moving more then one clip
https://bugs.kde.org/show_bug.cgi?id=371353 --- Comment #1 from Johannes Wuensch --- I tested with the AppImage of 16.12 again. Bug is still there, nothing changed... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 302923] Sort Icon-view items found by Fuzzy Searches [patch]
https://bugs.kde.org/show_bug.cgi?id=302923 Mario Frank changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/e12dd0980f4371f1a7511a ||817fc7e17d7dccd2e6 Resolution|--- |FIXED Version Fixed In||5.4.0 Status|UNCONFIRMED |RESOLVED --- Comment #11 from Mario Frank --- Git commit e12dd0980f4371f1a7511a817fc7e17d7dccd2e6 by Mario Frank. Committed on 23/12/2016 at 20:45. Pushed by mfrank into branch 'master'. This patch aims to improve the usability of fuzzy/duplicates/sketch search. A sorting option (by similarity) is introduced which can be helpful in fuzzy/sketch search where similar images are searched for a given one. Sorting the resulting images by similarity to the given image is an obviously helpful feature. It is now possible to drop local files that are images and not present in the Digikam database into the fuzzy search image label and trigger a fuzzy search for this image. Details: Sort by similarity: For sorting by similarity, a new option Sort by similarity with default order descending was introduced. This option is only active if the fuzzy search sidebar is active, i.e. fuzzy/duplicates/sketch search. To compare two pictures, it is necessary to get their similarity to the original picture. Since this information was only printed to console but not saved in the image info, SAlbum query or the properties, I do that myself. For every similar picture, a property similarityTo_X with X being the id of the original image and the similarity are stored as image property. When the image with id X is deleted, the property is removed to keep the DB small. Also, the property is removed from images if the fuzzy/duplicates search is done for image X such that old similarity values are removed. Though the similarity of image X to image Y is symmetric, I do not want to store both. This would bloat the DB. Only the detected similarities are explicitly stored. Drag and drop images not yet present in DB for fuzzy searches: I allow dragging objects over the image label iff the mime type of the event data is a URL list. In this case, it is no DIMG. If the first URL (there is only one in the list) is a local file and can be loaded as QImage, dropping is allowed. The function loadImage in HaarIface is used since it was already present and has optimisations for specific image formats. In order to not import the image but to be able to find similar pictures, and sort by the similarity, a temporary image id is needed. I use -1 for this case since this image id cannot be present in DB. Also, everytime a new external image is dropped for fuzzy search, the similarities for the previous dropped image are removed from database to keep the entries up to date. Moreover, I save the image url of the dropped image in the fuzzy search view. This way, refreshing the similar images due to modification of thresholds does work, too. Made small tests with valgrind - did not find memory leaks, yet. Made functionality tests for fuzzy drop. Trying to drag local files that are no images (e.g. pdf, odt, plain text) is not successful as wished. Made functionality tests for similarity search. Did not find defects. More tests will be applied in the next days. Related: bug 320666 FIXED-IN: 5.4.0 M +3-1NEWS M +7-0app/main/digikamapp.cpp M +46 -0app/utils/searchmodificationhelper.cpp M +29 -0app/utils/searchmodificationhelper.h M +27 -0app/views/digikamview.cpp M +4-0app/views/digikamview.h M +9-0app/views/leftsidebarwidgets.cpp M +8-0app/views/leftsidebarwidgets.h M +6-0libs/album/albummanager.cpp M +6-0libs/database/coredb/coredb.cpp M +1-0libs/database/coredb/coredb.h M +28 -1libs/database/haar/haariface.cpp M +14 -2libs/database/haar/haariface.h M +25 -0libs/database/item/imageextendedproperties.cpp M +7-0libs/database/item/imageextendedproperties.h M +5-0libs/database/item/imageinfo.cpp M +2-0libs/database/item/imageinfo.h M +13 -0libs/database/item/imagelister.cpp M +6-0libs/models/imagefiltermodel.cpp M +1-0libs/models/imagefiltermodel.h M +26 -1libs/models/imagesortsettings.cpp M +4-1libs/models/imagesortsettings.h M +2-0libs/settings/applicationsettings.cpp M +3-0libs/settings/applicationsettings.h M +9-0libs/settings/applicationsettings_miscs.cpp M +4-0libs/settings/applicationsettings_p.cpp M +2-0libs/settings/applicationsettings_p.h M +11 -0utilities/fuzzysearch/findduplicatesview.cpp M +73 -0utilities/fuzzysearch/fuzzysearchview.cpp M +3
[digikam] [Bug 320666] Add search of similar images outside digiKam collections [patch]
https://bugs.kde.org/show_bug.cgi?id=320666 Mario Frank changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/e12dd0980f4371f1a7511a ||817fc7e17d7dccd2e6 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.4.0 --- Comment #11 from Mario Frank --- Git commit e12dd0980f4371f1a7511a817fc7e17d7dccd2e6 by Mario Frank. Committed on 23/12/2016 at 20:45. Pushed by mfrank into branch 'master'. This patch aims to improve the usability of fuzzy/duplicates/sketch search. A sorting option (by similarity) is introduced which can be helpful in fuzzy/sketch search where similar images are searched for a given one. Sorting the resulting images by similarity to the given image is an obviously helpful feature. It is now possible to drop local files that are images and not present in the Digikam database into the fuzzy search image label and trigger a fuzzy search for this image. Details: Sort by similarity: For sorting by similarity, a new option Sort by similarity with default order descending was introduced. This option is only active if the fuzzy search sidebar is active, i.e. fuzzy/duplicates/sketch search. To compare two pictures, it is necessary to get their similarity to the original picture. Since this information was only printed to console but not saved in the image info, SAlbum query or the properties, I do that myself. For every similar picture, a property similarityTo_X with X being the id of the original image and the similarity are stored as image property. When the image with id X is deleted, the property is removed to keep the DB small. Also, the property is removed from images if the fuzzy/duplicates search is done for image X such that old similarity values are removed. Though the similarity of image X to image Y is symmetric, I do not want to store both. This would bloat the DB. Only the detected similarities are explicitly stored. Drag and drop images not yet present in DB for fuzzy searches: I allow dragging objects over the image label iff the mime type of the event data is a URL list. In this case, it is no DIMG. If the first URL (there is only one in the list) is a local file and can be loaded as QImage, dropping is allowed. The function loadImage in HaarIface is used since it was already present and has optimisations for specific image formats. In order to not import the image but to be able to find similar pictures, and sort by the similarity, a temporary image id is needed. I use -1 for this case since this image id cannot be present in DB. Also, everytime a new external image is dropped for fuzzy search, the similarities for the previous dropped image are removed from database to keep the entries up to date. Moreover, I save the image url of the dropped image in the fuzzy search view. This way, refreshing the similar images due to modification of thresholds does work, too. Made small tests with valgrind - did not find memory leaks, yet. Made functionality tests for fuzzy drop. Trying to drag local files that are no images (e.g. pdf, odt, plain text) is not successful as wished. Made functionality tests for similarity search. Did not find defects. More tests will be applied in the next days. Related: bug 302923 FIXED-IN: 5.4.0 M +3-1NEWS M +7-0app/main/digikamapp.cpp M +46 -0app/utils/searchmodificationhelper.cpp M +29 -0app/utils/searchmodificationhelper.h M +27 -0app/views/digikamview.cpp M +4-0app/views/digikamview.h M +9-0app/views/leftsidebarwidgets.cpp M +8-0app/views/leftsidebarwidgets.h M +6-0libs/album/albummanager.cpp M +6-0libs/database/coredb/coredb.cpp M +1-0libs/database/coredb/coredb.h M +28 -1libs/database/haar/haariface.cpp M +14 -2libs/database/haar/haariface.h M +25 -0libs/database/item/imageextendedproperties.cpp M +7-0libs/database/item/imageextendedproperties.h M +5-0libs/database/item/imageinfo.cpp M +2-0libs/database/item/imageinfo.h M +13 -0libs/database/item/imagelister.cpp M +6-0libs/models/imagefiltermodel.cpp M +1-0libs/models/imagefiltermodel.h M +26 -1libs/models/imagesortsettings.cpp M +4-1libs/models/imagesortsettings.h M +2-0libs/settings/applicationsettings.cpp M +3-0libs/settings/applicationsettings.h M +9-0libs/settings/applicationsettings_miscs.cpp M +4-0libs/settings/applicationsettings_p.cpp M +2-0libs/settings/applicationsettings_p.h M +11 -0utilities/fuzzysearch/findduplicatesview.cpp M +73 -0utilities/fuzzysearch/fuzzysearchview.cpp M +3
[kdialog] [Bug 363185] file selection dialog very slow when samba shares are not present
https://bugs.kde.org/show_bug.cgi?id=363185 Romain Bazile changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=320560 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar
https://bugs.kde.org/show_bug.cgi?id=373824 Cochise César changed: What|Removed |Added CC||cochisece...@gmail.com --- Comment #7 from Cochise César --- Ths sidebar itself is a feature, I think is important. And inside the sidebar we can have extensions/plugins/watheraver, and it is up to community making tis extensions. Can you point where are the sidebar code right now? I wanto to see if it is hard to port to kf5. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 374082] Columns not wide enough - Date and Balance
https://bugs.kde.org/show_bug.cgi?id=374082 --- Comment #2 from Jack --- This bug should be closed as a duplicate of 342196. It does not help to have one problem discussed in two different places. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 363185] file selection dialog very slow when samba shares are not present
https://bugs.kde.org/show_bug.cgi?id=363185 Romain Bazile changed: What|Removed |Added CC||grom...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 363185] file selection dialog very slow when samba shares are not present
https://bugs.kde.org/show_bug.cgi?id=363185 Romain Bazile changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=323650 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #13 from Maik Qualmann --- I think there is no GPS data in this video. When I upload it to my Google Photo user account, Google does not show me a GPS position. I think the GPS data comes from the recorded user motion profile and Google links this data. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 363185] file selection dialog very slow when samba shares are not present
https://bugs.kde.org/show_bug.cgi?id=363185 Romain Bazile changed: What|Removed |Added Severity|crash |major -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 363185] file selection dialog very slow when samba shares are not present
https://bugs.kde.org/show_bug.cgi?id=363185
Romain Bazile changed:
What|Removed |Added
Product|kfile |kdialog
Component|general |general
Version|unspecified |1.0
--- Comment #3 from Romain Bazile ---
I changed the concerned module. The problem can be reproduced by calling
'kdialog --getopenfilename'.
Also, I ran an strace on the call.
A lot of calls are made and are all the same.
More specifically this sequence is repeated continuously:
ioctl(10, FIONREAD, [32]) = 0 <0.21>
read(10, "\2\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0logkdialog2\0\0\0\0\0", 32) = 32
<0.23>
recvmsg(6, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily
unavailable) <0.23>
poll([{fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN},
{fd=8, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11, events=POLLIN}, {fd=13,
events=POLLPRI}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=17,
events=POLLIN}, {fd=18, events=POLLIN}], 11, 0) = 1 ([{fd=10, revents=POLLIN}])
<0.28>
recvmsg(6, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily
unavailable) <0.22>
If the calls are counted I get this results:
% time seconds usecs/call callserrors syscall
-- --- --- - -
30.910.17 0 1213 821 recvmsg
27.270.15 8 2 wait4
20.000.11 0 2099 206 stat
10.910.06 0 652 fstat
10.910.06 0 2806 1650 access
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 374100] New: Kwin random crashes
https://bugs.kde.org/show_bug.cgi?id=374100 Bug ID: 374100 Summary: Kwin random crashes Product: kwin Version: 5.8.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: trade...@hotmail.com Target Milestone: --- Application: kwin_x11 (5.8.4) Qt Version: 5.6.1 Frameworks Version: 5.28.0 Operating System: Linux 4.4.0-57-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I just oppened Firefox, but sometimes it also happens with some random other Kubuntu applications and at system inicialization. - Unusual behavior I noticed: When launching Firefox and sometimes with some random other Kubuntu applications, their windows closes for a brief moment but then get back up. But when it happens at system start, all the windows lose their borders, and keep stacking up, positioned at the left top corner of the screen, and no crash report of kwin-x11 appears before a few minutes. I would like to also add that the debugging package kwin-dbg, right now, is worthless for this report, as its current version only applies to an older version of kwin/kwin-x11. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f32bc6b7940 (LWP 1698))] Thread 7 (Thread 0x7f3296ffe700 (LWP 2206)): #0 0x7f32bc1a99e3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f32ba017a1f in qt_safe_select (nfds=14, fdread=fdread@entry=0x7f3284000a78, fdwrite=fdwrite@entry=0x7f3284000d08, fdexcept=fdexcept@entry=0x7f3284000f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7f32ba01945e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f3284000f98, writefds=0x7f3284000d08, readfds=0x7f3284000a78, nfds=, this=0x7f32840008c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f32840008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7f32ba019972 in QEventDispatcherUNIX::processEvents (this=0x7f32840008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7f32b9fc4e4a in QEventLoop::exec (this=this@entry=0x7f3296ffdc60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f32b9ded9e4 in QThread::exec (this=this@entry=0x2da3900) at thread/qthread.cpp:500 #7 0x7f32b4fe46b5 in QQmlThreadPrivate::run (this=0x2da3900) at qml/ftw/qqmlthread.cpp:141 #8 0x7f32b9df2808 in QThreadPrivate::start (arg=0x2da3900) at thread/qthread_unix.cpp:341 #9 0x7f32b5e816ba in start_thread (arg=0x7f3296ffe700) at pthread_create.c:333 #10 0x7f32bc1b382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f328a7c6700 (LWP 2058)): #0 0x7f32bc1a99e3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f32ba017a1f in qt_safe_select (nfds=11, fdread=fdread@entry=0x7f320a58, fdwrite=fdwrite@entry=0x7f320ce8, fdexcept=fdexcept@entry=0x7f320f78, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7f32ba01945e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f320f78, writefds=0x7f320ce8, readfds=0x7f320a58, nfds=, this=0x7f3200086450) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f3208c0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7f32ba019972 in QEventDispatcherUNIX::processEvents (this=0x7f3200086450, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7f32b9fc4e4a in QEventLoop::exec (this=this@entry=0x7f328a7c5c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f32b9ded9e4 in QThread::exec (this=this@entry=0x3f36540) at thread/qthread.cpp:500 #7 0x7f32b4fe46b5 in QQmlThreadPrivate::run (this=0x3f36540) at qml/ftw/qqmlthread.cpp:141 #8 0x7f32b9df2808 in QThreadPrivate::start (arg=0x3f36540) at thread/qthread_unix.cpp:341 #9 0x7f32b5e816ba in start_thread (arg=0x7f328a7c6700) at pthread_create.c:333 #10 0x7f32bc1b382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f32967fd700 (LWP 1772)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f32b918b574 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f32b918b5b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f32b5e816ba in start_thread (arg=0x7f32967fd700) at pthread_create.c:333 #4 0x7f32bc1b382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4
[kdev-python] [Bug 373850] Highlighting ranges often wrong for constructors/__call__()/indexing.
https://bugs.kde.org/show_bug.cgi?id=373850 Sven Brauch changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Sven Brauch --- This is a quite frequent issue, and should definitely be fixed before 5.1 final. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 373850] Highlighting ranges often wrong for constructors/__call__()/indexing.
https://bugs.kde.org/show_bug.cgi?id=373850 Sven Brauch changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 373768] Cannot start Kbibtex, crashes when launched
https://bugs.kde.org/show_bug.cgi?id=373768 Thomas Fischer changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 373768] Cannot start Kbibtex, crashes when launched
https://bugs.kde.org/show_bug.cgi?id=373768 --- Comment #2 from Thomas Fischer --- Created attachment 102964 --> https://bugs.kde.org/attachment.cgi?id=102964&action=edit Possible fix for crash Please apply this patch to KBibTeX 0.6.0.95 to see if it fixes your problem. The patch is based on the most recent Git version of branch kbibtex/0.6. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374008] Any selection tool will not allow a selected item to be transformed, and instead select a portion off of the canvas.
https://bugs.kde.org/show_bug.cgi?id=374008 --- Comment #2 from Elara Methone --- Yes, I will try to take screenshots and recreate this issue. I apologize for any inconvenience. On Thu, Dec 22, 2016 at 3:35 AM, Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=374008 > > Boudewijn Rempt changed: > >What|Removed |Added > > > CC||b...@valdyas.org > Resolution|--- |WAITINGFORINFO >Platform|unspecified |MS Windows > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #1 from Boudewijn Rempt --- > Hi Elara, > > Could you add a screenshot or video? I've just tried to reproduce this > issue: > > * created a new image > * added some lines > * selected an ellipse > * select the transform tool > > And found the transform tool, as expected working on only the selection, > and > the cut tool cutting only the ellipse. > > So I'm wondering whether I misunderstood you, or whether you're doing > something > really different... > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 373802] flatpak-kde-applications fails to compile: missing /app/files/share/applications/org.kde.marble.maps.desktop
https://bugs.kde.org/show_bug.cgi?id=373802 Dennis Nienhüser changed: What|Removed |Added CC||aleix...@gmail.com, ||nienhue...@kde.org --- Comment #2 from Dennis Nienhüser --- Aleix, can you comment on https://github.com/KDE/flatpak-kde-applications/blob/master/org.kde.marble.json and what it expects? I wonder if "id": "org.kde.marble.maps" should rather be "id": "org.kde.marble" which corresponds to the Desktop application, while org.kde.marble.maps is the mobile variant which is not installed by default. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374099] New: Add more information to file transfers notification without having to expand the more details button
https://bugs.kde.org/show_bug.cgi?id=374099 Bug ID: 374099 Summary: Add more information to file transfers notification without having to expand the more details button Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: arco...@gmail.com CC: mklape...@kde.org Target Milestone: 1.0 It would be nice to have a bit more information about file transfers in the notification box. Having all details tucked away under the "more details" just requires an unnecessary extra click to access basic information. I Krita'd an example here: http://i.imgur.com/PsAJXR9.png I know Plasma5 is all about whitespace but I do think function over form should take priority in some cases like this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 240862] KDE System Settings - Backup & Restore
https://bugs.kde.org/show_bug.cgi?id=240862 spechtra changed: What|Removed |Added CC||adilas...@ymail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373879] desktop background not consistently remembered
https://bugs.kde.org/show_bug.cgi?id=373879 Dimitrios T Tanis changed: What|Removed |Added CC||dimitrios.ta...@kdemail.net --- Comment #1 from Dimitrios T Tanis --- Same problem with 5.8.3 here. -- You are receiving this mail because: You are watching all bug changes.
[rekonq] [Bug 292772] restore last opened tabs merges multiple windows into one on restore
https://bugs.kde.org/show_bug.cgi?id=292772 spechtra changed: What|Removed |Added CC||adilas...@ymail.com -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 374097] Kdevelop 5 crashes when editing python file
https://bugs.kde.org/show_bug.cgi?id=374097 --- Comment #1 from Sven Brauch --- Thanks for the precise report. I can't reproduce it though ... no crash here. I just notice it's very laggy with code style checking enabled (really need to fix that). Can you reproduce the issue you describe every time? Can you still reproduce it after closing kdevelop and removing ~/.cache/kdevduchain? -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 374098] New: Replace the Maxima entry code with its LaTeX representation
https://bugs.kde.org/show_bug.cgi?id=374098 Bug ID: 374098 Summary: Replace the Maxima entry code with its LaTeX representation Product: cantor Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: maxima-backend Assignee: fil...@kde.org Reporter: elv1...@gmail.com CC: alexanderrie...@gmail.com Target Milestone: --- Hello, When not being edited, could the entry line be replaced by its LaTeX representation. Maxima has built in support for that. All you have to do is to add "'" in front of the line and evaluate that. When selected or clicked, it should go back to the string representation. This would make the output much more readable. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 374097] New: Kdevelop 5 crashes when editing python file
https://bugs.kde.org/show_bug.cgi?id=374097 Bug ID: 374097 Summary: Kdevelop 5 crashes when editing python file Product: kdev-python Version: 5.0.3 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Language support Assignee: m...@svenbrauch.de Reporter: jonathan.ver...@gmail.com Target Milestone: --- Created attachment 102962 --> https://bugs.kde.org/attachment.cgi?id=102962&action=edit The file leading to the crash. When editing the attached file and entering `c` into the `cls.add_bundle` call on line `63` kdevelop immediately crashes on me. Sometimes, it prints the following lines on the console: > doing pep8 checking > invalid pep8 error line: "" In general, editing this file leads to frequent crashes. Unfortunately, I am not sure how to get a backtrace with the appimage, but if someone helps me, I can provide it. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 374096] New: Cantor LaTeX output doesn't follow the color palette
https://bugs.kde.org/show_bug.cgi?id=374096 Bug ID: 374096 Summary: Cantor LaTeX output doesn't follow the color palette Product: cantor Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: maxima-backend Assignee: fil...@kde.org Reporter: elv1...@gmail.com CC: alexanderrie...@gmail.com Target Milestone: --- [maxima backend] Hello, The background is always white and text color always black. This doesn't look good at all when using dark themes. A minor bug for some, but an accessibility bug for others. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 374075] File does not appear in Dolphin after creation
https://bugs.kde.org/show_bug.cgi?id=374075 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Elvis Angelaccio --- Thanks for the bug report. After some investigation, turns out that you can reproduce it only if you start Dolphin from the Plasma menu or from a Konsole _not_ in the home folder. Otherwise if Konsole's cd is another folder, everything works as expected (indeed I could not reproduce with my local Dolphin build run from the build directory...). Btw the problem is that the dir lister does not emit completed() and thus DolphinView::updateViewState() is not called. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 320666] Add search of similar images outside digiKam collections [patch]
https://bugs.kde.org/show_bug.cgi?id=320666 --- Comment #10 from caulier.gil...@gmail.com --- I discovered a serious problem to Slideshow and Presentation with some video file to handle. So postponed is the best way. The doc is not a problem. For i18n, if patch over GUI is applied quickly and not touched later, it's acceptable. Patching code not relevant of i18n is not a problem of course. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 320666] Add search of similar images outside digiKam collections [patch]
https://bugs.kde.org/show_bug.cgi?id=320666 --- Comment #9 from Mario Frank --- (In reply to caulier.gilles from comment #8) > Mario, > > I postponed digiKam 5.4.0 to 1 January. This will let's time to you to patch > git/master and test to stabilize implementation for production while > holidays. > > Please don't waste time. > > Gilles Hey, postponing the deadline was not what I aimed at but since I am in Holidays now, there will be enough time to test. I will patch the master branch after doing some standard tests with valgrind and some more functionality tests. The similarity sort patch introduces some i18n-related topics. How are the maintainers informed about necessary changes for localisation and/or documentation? Cheers, Mario -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 373276] commit "Do not ask for root permissions when it's unnecessary" makes it difficult to add a new user
https://bugs.kde.org/show_bug.cgi?id=373276 pjsingh5...@gmail.com changed: What|Removed |Added CC||pjsingh5...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 291835] KIO very slow when copying from network through smb
https://bugs.kde.org/show_bug.cgi?id=291835 --- Comment #45 from oli...@openbrackets.net --- I think we can safely assume that the SMB protocol is not just "a socket". Obviously no-one wants to re-implement an SMB protocol client, that would be a huge task. So it's really a question of whether libsmbclient (or similar lib) can support "just being fed data from an FD". From all I have seen, that is not the case. libsmbclient expects discrete calls to smbc_read|write: /**@ingroup file * Read from a file using an opened file handle. * * @param fdOpen file handle from smbc_open() or smbc_creat() * * @param buf Pointer to buffer to receive read data * * @param bufsize Size of buf in bytes * * @return Number of bytes read; * 0 upon EOF; * < 0 on error, with errno set: * - EISDIR fd refers to a directory * - EBADF fd is not a valid file descriptor or *is not open for reading. * - EINVAL fd is attached to an object which is *unsuitable for reading, or no buffer passed or *smbc_init not called. * * @see smbc_open(), smbc_write() * */ ssize_t smbc_read(int fd, void *buf, size_t bufsize); -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374095] New: QOffscreenSurface created off the main/gui thread
https://bugs.kde.org/show_bug.cgi?id=374095 Bug ID: 374095 Summary: QOffscreenSurface created off the main/gui thread Product: kdenlive Version: 16.12.0 Platform: Compiled Sources OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: rjvber...@gmail.com Target Milestone: --- Since v 16.8.x I'm seeing startup warnings/errors on the calling terminal, under OS X: ``` Attempting to create QWindow-based QOffscreenSurface outside the gui thread. Expect failures. 2016-12-23 19:13:17.058 kdenlive[1807:e103] invalid drawable Attempting to create QWindow-based QOffscreenSurface outside the gui thread. Expect failures. 2016-12-23 19:13:17.071 kdenlive[1807:e103] invalid drawable 2016-12-23 19:13:43.139 kdenlive[1807:e103] invalid drawable 2016-12-23 19:13:43.281 kdenlive[1807:e103] invalid drawable ``` The "invalid drawable" messages also appear in the System.log indicating that they were made with `NSLog()`, presumably by Qt. I haven't investigated this yet because I didn't notice any feature loss or issues, but it's probably worth raising the issue. Doing OpenGL graphics off the main thread used to be a sure recipe for Mac KPs, and Qt still doesn't work properly when the event loop isn't handled on the main thread. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 353245] Support of OMEMO in Kopete
https://bugs.kde.org/show_bug.cgi?id=353245 Maximilian Böhm changed: What|Removed |Added CC||m...@elbmurf.de -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 291835] KIO very slow when copying from network through smb
https://bugs.kde.org/show_bug.cgi?id=291835 --- Comment #44 from Mark --- (In reply to oli...@openbrackets.net from comment #43) > @Mark > > one more thought... > > if 1. above is OK, ie smbclient / smbc_read|write can support and FD > streaming approach, then, eventhough we are getting rid of the problem of > determining buffer size, is that going to solve the throughput issue? > > I don't understand the problem in great detail yet, but it seems to me that > because of the way the SMB protocol works, the way the libsmbclient API > needs to be called and fed data, is quite critical, ref > https://bugs.kde.org/show_bug.cgi?id=291835#c26 where wireshark forensics > show that smbclient/cifs use clever strategy of pre-fetching "one block > ahead" to get max throughput... > > How can sendfile / splice ever understand these semantics? > > Would we be getting rid of the "deciding what size buffer to use" problem, > while failing to address the actual problem of achieving highly optimised > throughput...? For all your questions: i don't know :) But i do know that sendfile/splice works marvelously on sockets. If i do an iperf benchmark between my computer and my locak server i get around 990mbit/sec. That is very fast for a 1gbit connection. It's hitting the maximum throughput, anything more is close to impossible due to TCP overhead. Now if i use sendfile/splice to copy a file over the same network i get between 900 and 950 mbit/sec. Close enough for me :) And that is with just those file descriptors and letting sendfile/splice handle whatever they want to handle. I don't know how it internally does smart stuff, but i do know it's blazingly fast. If all of this works with samba around id.. We will just have to try it out i guess. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 --- Comment #12 from caulier.gil...@gmail.com --- with Exiftool, no GPS metadata can be extracted : gilles@localhost Videos]$ exiftool -a -u -g1 20161223T153428.mp4 ExifTool ExifTool Version Number : 10.15 System File Name : 20161223T153428.mp4 Directory : . File Size : 13 MB File Modification Date/Time : 2016:12:23 18:54:26+01:00 File Access Date/Time : 2016:12:23 18:54:26+01:00 File Inode Change Date/Time : 2016:12:23 18:54:26+01:00 File Permissions: rw-rw-r-- File File Type : MP4 File Type Extension : mp4 MIME Type : video/mp4 QuickTime Major Brand : MP4 v2 [ISO 14496-14] Minor Version : 0.0.0 Compatible Brands : isom, mp42 Movie Header Version: 0 Create Date : 2016:12:23 17:46:11 Modify Date : 2016:12:23 17:46:11 Time Scale : 600 Duration: 11.17 s Preferred Rate : 1 Preferred Volume: 100.00% Matrix Structure: 1 0 0 0 1 0 0 0 1 Preview Time: 0 s Preview Duration: 0 s Poster Time : 0 s Selection Time : 0 s Selection Duration : 0 s Current Time: 0 s Next Track ID : 3 Initial Object Descriptor : (Binary data 13 bytes, use -b option to extract) Movie Data Size : 13137831 Movie Data Offset : 4890 Movie Data : (Binary data 13137831 bytes, use -b option to extract) Track1 Track Header Version: 0 Track Create Date : :00:00 00:00:00 Track Modify Date : 2016:12:23 17:46:11 Track ID: 1 Track Duration : 11.03 s Track Layer : 0 Track Volume: 0.00% Matrix Structure: 1 0 0 0 1 0 0 0 1 Image Width : 1920 Image Height: 1080 Unknown edts: (Binary data 28 bytes, use -b option to extract) Media Header Version: 0 Media Create Date : :00:00 00:00:00 Media Modify Date : 2016:12:23 17:46:11 Media Time Scale: 30 Media Duration : 11.03 s Media Language Code : und Handler Type: Video Track Handler Description : VideoHandler Graphics Mode : srcCopy Op Color: 0 0 0 Compressor ID : avc1 Source Image Width : 1920 Source Image Height : 1080 X Resolution: 72 Y Resolution: 72 Bit Depth : 24 Unknown avcC: (Binary data 45 bytes, use -b option to extract) Buffer Size : 124798 Max Bitrate : 10111712 Average Bitrate : 9380128 Video Frame Rate: 30 Sync Sample Table : (Binary data 32 bytes, use -b option to extract) Sample To Chunk : (Binary data 212 bytes, use -b option to extract) Sample Sizes: (Binary data 1336 bytes, use -b option to extract) Chunk Offset: (Binary data 100 bytes, use -b option to extract) Track2 Track Header Version: 0 Track Create Date : 2016:12:23 17:46:11 Track Modify Date : 2016:12:23 17:46:11 Track ID: 2 Track Duration : 11.17 s Track Layer : 0 Track Volume: 100.00% Matrix Structure: 1 0 0 0 1 0 0 0 1 Media Header Version: 0 Media Create Date : 2016:12:23 17:46:11 Media Modify Date : 2016:12:23 17:46:11 Media Time Scale: 44100 Media Duration : 11.17 s Media Language Code : eng Handler Type: Audio Track Handler Description : IsoMedia File Produced by Google, 5-11-2011 Balance : 0 Audio Format: mp4a Audio Channels : 1 Audio Bits Per Sample : 16 Audio Sample Rate : 44100 Unknown esds: (Binary data 45 bytes, use -b option to extract) Time To Sample Table: (Binary data 16 bytes, use -b option to extract) Sample To Chunk : (Binary data 44 bytes, use -b option to extract) Sample Sizes: (Binary data 1936 bytes, use -b option to extract) Chunk Offset: (Binary data 100 bytes, use -b option to extract) Composite Avg Bitrate :
[plasmashell] [Bug 374094] New: plasmoids cover icons
https://bugs.kde.org/show_bug.cgi?id=374094 Bug ID: 374094 Summary: plasmoids cover icons Product: plasmashell Version: 5.8.2 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: hb_...@brueningserver.de CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 102961 --> https://bugs.kde.org/attachment.cgi?id=102961&action=edit impossible to use folder plasmoid at that position This makes it hard to use plasmoids in combination with folderview as background plasmoid. If using the features "create new file", "create new folder" or "sort icons" it may happen that icons appear under a plasmoid and thus are invisible. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #11 from caulier.gil...@gmail.com --- As i said, something is wrong in Exiv2 0.26. It report nothing in Exif. [gilles@localhost Videos]$ exiv2 -pr 20161223T153428.mp4 exiv2: Unrecognized print mode `r' Usage: exiv2 [ options ] [ action ] file ... Manipulate the Exif metadata of images. [gilles@localhost Videos]$ exiv2 -pa 20161223T153428.mp4 Xmp.video.FileSize XmpText 7 12.5339 Xmp.video.FileName XmpText19 20161223T153428.mp4 Xmp.video.MimeType XmpText15 video/quicktime Xmp.video.MajorBrand XmpText21 MP4 v2 [ISO 14496-14] Xmp.video.MinorVersion XmpText 1 0 Xmp.video.CompatibleBrands XmpSeq 2 MP4 Base Media v1 [IS0 14496-12:2003], MP4 v2 [ISO 14496-14] Xmp.video.MovieHeaderVersion XmpText 1 0 Xmp.video.DateUTCXmpText10 3565359971 Xmp.video.ModificationDate XmpText10 3565359971 Xmp.video.TimeScale XmpText 3 600 Xmp.video.Duration XmpText 5 11168 Xmp.video.PreferredRate XmpText 1 1 Xmp.video.PreferredVolumeXmpText 3 100 Xmp.video.PreviewTimeXmpText 1 0 Xmp.video.PreviewDurationXmpText 1 0 Xmp.video.PosterTime XmpText 1 0 Xmp.video.SelectionTime XmpText 1 0 Xmp.video.SelectionDuration XmpText 1 0 Xmp.video.CurrentTimeXmpText 1 0 Xmp.video.NextTrackIDXmpText 1 3 Xmp.video.TrackHeaderVersion XmpText 1 0 Xmp.video.TrackCreateDateXmpText 1 0 Xmp.video.TrackModifyDateXmpText10 3565359971 Xmp.video.TrackIDXmpText 1 1 Xmp.video.TrackDuration XmpText 2 11 Xmp.video.TrackLayer XmpText 1 0 Xmp.video.TrackVolumeXmpText 3 100 Xmp.video.Width XmpText 4 1920 Xmp.video.Height XmpText 4 1080 Xmp.video.MediaHeaderVersion XmpText 1 0 Xmp.video.MediaCreateDateXmpText 1 0 Xmp.video.MediaModifyDateXmpText10 3565359971 Xmp.video.MediaTimeScale XmpText 2 30 Xmp.video.MediaDuration XmpText 2 11 Xmp.video.MediaLangCode XmpText 5 21956 Xmp.video.HandlerTypeXmpText11 Video Track Xmp.video.GraphicsMode XmpText 7 srcCopy Xmp.video.OpColorXmpText 1 0 Xmp.video.URLXmpText 0 Xmp.video.Codec XmpText39 MP4 Base w/ AVC ext [ISO 14496-12:2005] Xmp.video.SourceImageWidth XmpText 4 1920 Xmp.video.SourceImageHeight XmpText 4 1080 Xmp.video.XResolutionXmpText 2 72 Xmp.video.YResolutionXmpText 2 72 Xmp.video.Compressor XmpText 0 Xmp.video.BitDepth XmpText 2 24 Xmp.video.FrameRate XmpText 3 600 Xmp.audio.TrackHeaderVersion XmpText 1 0 Xmp.audio.TrackCreateDateXmpText10 3565359971 Xmp.audio.TrackModifyDateXmpText10 3565359971 Xmp.audio.TrackIDXmpText 1 2 Xmp.audio.TrackDuration XmpText 2 11 Xmp.audio.TrackLayer XmpText 1 0 Xmp.audio.MediaHeaderVersion XmpText 1 0 Xmp.audio.MediaCreateDateXmpText10 3565359971 Xmp.audio.MediaModifyDateXmpText10 3565359971 Xmp.audio.MediaTimeScale XmpText 5 44100 Xmp.audio.MediaDuration XmpText 2 11 Xmp.audio.MediaLangCode XmpText 4 5575 Xmp.audio.HandlerTypeXmpText11 Audio Track Xmp.audio.BalanceXmpText 1 0 Xmp.audio.URLXmpText 0 Xmp.audio.Compressor XmpText 4 mp4a Xmp.audio.ChannelTypeXmpText 1 1 Xmp.audio.BitsPerSample X
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 --- Comment #10 from Philippe ROUBACH --- the link to get the movie https://goo.gl/photos/4732E3QexiVnHbSt8 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 Philippe ROUBACH changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|UPSTREAM|--- --- Comment #9 from Philippe ROUBACH --- from google photo site i imported the video. i check that google photo displaysa map with a pointer about this movie. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #8 from caulier.gil...@gmail.com --- It's abnormal. MP4 must be supported by Exiv2 0.26-svn. Please report this problem to Exiv2 bugzilla. Share MP4 file for investigations. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 Philippe ROUBACH changed: What|Removed |Added Version|5.2.0 |5.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 Philippe ROUBACH changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED |--- --- Comment #7 from Philippe ROUBACH --- it is not fixed mp4 video nothing in exif media data viewer -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 374093] New: System settings always crash after every use independent of view mode
https://bugs.kde.org/show_bug.cgi?id=374093 Bug ID: 374093 Summary: System settings always crash after every use independent of view mode Product: systemsettings Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m...@freenet.de Target Milestone: --- Fresh install from Kubuntu (16) DVD, local settings Germany/german, always updated packages incl kernels. Since the beginning systemsettings crash on close, this is a typical backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6664b398c0 (LWP 6955))] Thread 3 (Thread 0x7f66297f8700 (LWP 7054)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f665e1edd4a in g_cond_wait_until () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f665e17d999 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f665e17dfbb in g_async_queue_timeout_pop () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f665e1d061a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f665e1cfbc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f665e6ca6ba in start_thread (arg=0x7f66297f8700) at pthread_create.c:333 #7 0x7f666126482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f66531fa700 (LWP 6956)): #0 0x7f6661258b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f665ef40c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f665ef428d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f665554c629 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f666194e7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f665e6ca6ba in start_thread (arg=0x7f66531fa700) at pthread_create.c:333 #6 0x7f666126482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f6664b398c0 (LWP 6955)): [KCrash Handler] #6 0x7f6661b376e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6661b620cb in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6644ce41b3 in KParts::PartManager::~PartManager() () from /usr/lib/x86_64-linux-gnu/libKF5Parts.so.5 #9 0x7f6644ce4369 in KParts::PartManager::~PartManager() () from /usr/lib/x86_64-linux-gnu/libKF5Parts.so.5 #10 0x7f6661b5c28b in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f6661b65b00 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f664542731b in KHTMLPart::~KHTMLPart() () from /usr/lib/x86_64-linux-gnu/libKF5KHtml.so.5 #13 0x7f6645427439 in KHTMLPart::~KHTMLPart() () from /usr/lib/x86_64-linux-gnu/libKF5KHtml.so.5 #14 0x7f6661b5ec20 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f666300205c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f6663007516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f6661b2f38b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f6661b31786 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f6661b853c3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f665e1a91a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f665e1a9400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f665e1a94ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f6661b857cf in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f6661b2cb4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f6661b34bec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x0040f7a1 in main () -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374092] New: option to disable/enable window borders from taskbar
https://bugs.kde.org/show_bug.cgi?id=374092 Bug ID: 374092 Summary: option to disable/enable window borders from taskbar Product: plasmashell Version: 5.8.2 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: hb_...@brueningserver.de CC: plasma-b...@kde.org Target Milestone: 1.0 When window borders are hidden by clicking on the title bar of a window, a message box appears that this situation can only be changed by pressing Alt+F3. However, users might forget this combination or VirtualBox might eat up Alt+F3. It would be helpful if window borders could be enabled from the task bar, too. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 374082] Columns not wide enough - Date and Balance
https://bugs.kde.org/show_bug.cgi?id=374082 --- Comment #1 from allan --- Are you able to stretch the window horizontally, and does that help? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374091] Theme application menu icons combine theme with icon theme.
https://bugs.kde.org/show_bug.cgi?id=374091 Geoff King changed: What|Removed |Added CC||gski...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342196] Register page, the colum of Date and Balance are not wide enough, only shown 3 digits + 2 decimal
https://bugs.kde.org/show_bug.cgi?id=342196 --- Comment #12 from allan --- (In reply to Lenka Filova from comment #9) > Hello, > > I have the same problem as Dino. Nevertheless, on this page I could not find > any solution to it. > > Is there a way how to solve it? I use Windows 10 and the latest version of > Kmymoney 4.8.0. > > Thank you! Would you, too, also say if my comments to Dino help you in any way. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342196] Register page, the colum of Date and Balance are not wide enough, only shown 3 digits + 2 decimal
https://bugs.kde.org/show_bug.cgi?id=342196 --- Comment #11 from allan --- Also, would you say if stretching the window width helps, or not. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374091] New: Theme application menu icons combine theme with icon theme.
https://bugs.kde.org/show_bug.cgi?id=374091 Bug ID: 374091 Summary: Theme application menu icons combine theme with icon theme. Product: digikam Version: 5.4.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: gski...@gmail.com Target Milestone: --- I switched to the "ShadeOfGray" theme. When using this theme some menu icons were too light and could not be seen as is, so I found the configure>miscellaneous entry for Icon Theme and changed that to "Breeze Dark". Nice! All is good now. However, maybe you could make it a little easier by including both the Theme and the Icon Theme in the same menu or same configuration page? Or provide a popup hint reminder to also change Icon Theme when changing the theme? Or even change them together with a Theme entry of "Shade of Gray using Breeze Dark (restart required)" A minor issue, but though I would point it out since it took me a while to figure this out again. It does look good now. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342196] Register page, the colum of Date and Balance are not wide enough, only shown 3 digits + 2 decimal
https://bugs.kde.org/show_bug.cgi?id=342196 --- Comment #10 from allan --- (In reply to Dino from comment #8) > Created attachment 91932 [details] > MyMoney05.jpg > > 1) should be system fonts, never changed fonts type (see attached image) > > 2) Yes, I use the transaction form. > > > > > > Il 07/04/2015 14:44, Cristian Oneț ha scritto: > > https://bugs.kde.org/show_bug.cgi?id=342196 > > > > --- Comment #6 from Cristian Oneț --- > > The column width can't be modified because it's managed by the application, > > in > > the case of the attached screenshots the automatic calculation have failed. > > To > > pinpoint the problem I have to ask a few more questions: > > > > 1. Do you use system fonts or custom fonts? > > > > https://docs.kde.org/stable/en/extragear-office/kmymoney/details.settings.fonts.html > >MyMoney05.jpg > > 2. Do you use the transaction form? > > > > https://docs.kde.org/stable/en/extragear-office/kmymoney/details.settings.register.html > > This screen-shot, MyMoney05.jpg, shows that you are not using system fonts as the appropriate check-box (top left) is unchecked. Please say if changing that helps, or otherwise. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368811] Screen freezed when trying to get desktop grid from desktop corner (3d effect)
https://bugs.kde.org/show_bug.cgi?id=368811 unsuspicious.fakename+kdeb...@gmail.com changed: What|Removed |Added CC||unsuspicious.fakename+kdebu ||g...@gmail.com --- Comment #12 from unsuspicious.fakename+kdeb...@gmail.com --- Same problem here, don't have any "weird windows" as far as I can tell. Did you use some sort of debugging trick to find out which window is the cause or just trial and error? -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 291835] KIO very slow when copying from network through smb
https://bugs.kde.org/show_bug.cgi?id=291835 --- Comment #43 from oli...@openbrackets.net --- @Mark one more thought... if 1. above is OK, ie smbclient / smbc_read|write can support and FD streaming approach, then, eventhough we are getting rid of the problem of determining buffer size, is that going to solve the throughput issue? I don't understand the problem in great detail yet, but it seems to me that because of the way the SMB protocol works, the way the libsmbclient API needs to be called and fed data, is quite critical, ref https://bugs.kde.org/show_bug.cgi?id=291835#c26 where wireshark forensics show that smbclient/cifs use clever strategy of pre-fetching "one block ahead" to get max throughput... How can sendfile / splice ever understand these semantics? Would we be getting rid of the "deciding what size buffer to use" problem, while failing to address the actual problem of achieving highly optimised throughput...? -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 291835] KIO very slow when copying from network through smb
https://bugs.kde.org/show_bug.cgi?id=291835 --- Comment #42 from oli...@openbrackets.net --- @Mark That sounds very neat, some questions: 1. gvfs-smb backend uses libsmbclient, so does the cmd line smbget. I assume kioslave-smb is the same? Is the libsmbclient API, which we don't control, compatible with a sendfile / splice "streaming" approach? 2. given the apparent lack of devs on this long-standing issue, is this rather ambitious approach, while potentially being the "more correct/elegant way", likely to result in more paralysis... ie what can we commit/release today? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374090] New: Multiple Desktops change position for no apparent reason sometimes
https://bugs.kde.org/show_bug.cgi?id=374090 Bug ID: 374090 Summary: Multiple Desktops change position for no apparent reason sometimes Product: kwin Version: 5.8.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: unsuspicious.fakename+kdeb...@gmail.com Target Milestone: --- Reproduce: - Cover at least 9 (better 12) Desktops in windows (optionally: hide task bar, tile / arrange windows so they cover 100% of all desktops which - in theory - should probably make it impossible to drag desktops accidentally ) - Work on something very complicated that requires interaction with many different windows for some hours - Use desktop grid repeatedly to locate the desktop you need (when it isn't directly adjacent) - Try not to drag ANYTHING ANYWHERE Expected result: Work efficiently. Bug / actual result: Multiple Desktop-swaps / drags happen very fast - possibly during zoom-out animation or very shortly after; not quite visibly animated but obvious enough to recognize some sort of "transition" in the order (as opposed to an instantaneous change of sequence). Desktop grid turns into a sliding puzzle, where you have to minimize windows on at least one Desktop so you can grab it and then figure out the right order of slides/swaps to restore the arrangement you had set up. Slow descent into insanity over the course of several months. Subsequent exposure to sliding puzzles in other situations might lead to irrationally violent behavior. Tried to figure out what makes this happen for months and failed. For the most time, I had all desktops almost covered in neatly tiled windows when it happened, so there should have been no space left to grab + drag a desktop. I don't remember ever having accidentally dragged a window. Unless I missed something, there shouldn't be any Desktop-drag-space left on my Desktops. "Tested" all occurring elements I could think of for potential "desktop-draggability" (except for tool-tips) and found none. ( If I oversaw a way to turn off Desktop dragging altogether, someone please point me to it. I have never on purpose dragged a desktop, so in my case that would be a great workaround. ) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329854] digiKam doesn't rotate video thumbnail
https://bugs.kde.org/show_bug.cgi?id=329854 caulier.gil...@gmail.com changed: What|Removed |Added Platform|openSUSE RPMs |Appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329854] digiKam doesn't rotate video thumbnail
https://bugs.kde.org/show_bug.cgi?id=329854 caulier.gil...@gmail.com changed: What|Removed |Added Version|4.2.0 |5.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 --- Comment #6 from caulier.gil...@gmail.com --- Or in your comment #4 you want mean "now fixed" instead "not fixed" ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369629] digikam does not use GPS data from video files
https://bugs.kde.org/show_bug.cgi?id=369629 --- Comment #5 from caulier.gil...@gmail.com --- Which kind of video file you use. 5.4.0 bundle use Exiv2 026-svn with video metadata support that must do the stuff. Do you see any GPS info in Exif metadata viewer ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374089] New: many problems with control bar on left side
https://bugs.kde.org/show_bug.cgi?id=374089 Bug ID: 374089 Summary: many problems with control bar on left side Product: plasmashell Version: 5.8.2 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: hb_...@brueningserver.de Target Milestone: 1.0 Created attachment 102960 --> https://bugs.kde.org/attachment.cgi?id=102960&action=edit video containing demonstration for all bugs Many problems with control bar on left side and activity bar in it. See in my attached screencast. 1. See at 0:11 that when clicking on the configure button, the desktop shifts to the right. If configure menu is closed at 0:13 it shifts back. This is confusing to the user because what you see is not what you get. 2. From 0:15 to 0:22 I am moving around the resize arrows. It is not obvious to the user why nothing happens. 3. At 0:23 I made the control bar vertically smaller. But the activity bar is also resized horizontally in a strange way. 4. You see that there is empty space below the activity bar. At 0:29 you can see that there is really no other plasmoid claiming this space. You saw before that this space cannot be eliminated by resizing the control bar. 5. If the control bar is always visible, then it is not possible for icons or plasmoids (see at 0:45) to be placed above or below the control bar. So there is much lost space. 6. When moving a plasmoid, the control bar catches it without releasing the mouse button. At 0:49 I definitelly did not realease the mouse button. 7. When a plasmoid is moved into a control bar, it cannot moved back by the same way. But as a user I would expect so. At 0:52 I am trying this twice. 8: At 0:58 I want to open the the configure menu of the control bar. But for some reason the calender opens as if I had clicked on the clock. 9. At 1:06 I am trying to remove the clock plasmoid. But I am not fast enough with the mouse motion and, the remove button disappears. This is a wrong behaviour. 10. See what happens at 1:31. I would expect the clock to be resized. 11. At 1:40 I am starting to move the clock plasmoid. In that instant, the control bar resizes. This is strange behaviour because what you see is not what you get when releasing the mouse button. All these bugs are reproducible for me as you can see in the video. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374088] In recent archlinux version (16.12.0-1) Folder Properties Are NOT Retained
https://bugs.kde.org/show_bug.cgi?id=374088 kdepim...@graumannschaft.org changed: What|Removed |Added CC||kdepim...@graumannschaft.or ||g -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374088] New: In recent archlinux version (16.12.0-1) Folder Properties Are NOT Retained
https://bugs.kde.org/show_bug.cgi?id=374088 Bug ID: 374088 Summary: In recent archlinux version (16.12.0-1) Folder Properties Are NOT Retained Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: kdepim...@graumannschaft.org Target Milestone: --- When setting folder specific retrieval intervals, keep replies in a folder etc. via right-click --> Folder properties, the set properties are NOT retained and display identical to before trying to set them when revisiting the properties dialog. See https://mail.kde.org/pipermail/kdepim-users/2016-December/000502.html for validation. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374087] New: Create Calendar creates corrupt looking image when using High setting when sending to other than printer
https://bugs.kde.org/show_bug.cgi?id=374087 Bug ID: 374087 Summary: Create Calendar creates corrupt looking image when using High setting when sending to other than printer Product: digikam Version: 5.4.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Calendar Assignee: digikam-de...@kde.org Reporter: gski...@gmail.com Target Milestone: --- Created attachment 102959 --> https://bugs.kde.org/attachment.cgi?id=102959&action=edit picture copied from adobe pdf and coverted to png so you can see the horizontal banding. I did not provide a full calendar export becuase the PDF is very large (~20MB) I tried the create calendar option (never used it before). I had an issue when exporting to adobe PDF (using Adobe's Printer in Windows)and exporting to OneNote as another test. However I was able to print to a normal printer without issues. The problem was when using the default resolution setting of "high" it results in images that have horizontal lines over them. If I use the "low" setting it is okay and I do not see the lines. I ran 2 tests outputting to Adobe PDF and to OneNote2013 and got similar (but not exact results). I also printed to a normal printer and it was okay. This is on Windows 7, 64bit version of digikam, test version of 5.4.0 (12/23/2016) Example provided. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 374074] Lock Screen: "Show Password" - lockscreen vulnerable to social engineering
https://bugs.kde.org/show_bug.cgi?id=374074 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374086] New: random crash after deleting a message
https://bugs.kde.org/show_bug.cgi?id=374086
Bug ID: 374086
Summary: random crash after deleting a message
Product: Akonadi
Version: GIT (master)
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: server
Assignee: kdepim-b...@kde.org
Reporter: cgiboude...@gmx.com
Target Milestone: ---
Just got this with master after deleting a message in KMail :
17:32:07 - kmail2(2020) - : ASSERT: "m_collections.contains(collectionId)" in
file /kde/src/5/akonadiserver/src/core/models/entitytreemodel_p.cpp, line 1253
bt
#7 0x7f9824093665 in
Akonadi::EntityTreeModelPrivate::monitoredItemLinked(Akonadi::Item const&,
Akonadi::Collection const&) (this=0x1874810, item=..., collection=...) at
/kde/src/5/akonadiserver/src/core/models/entitytreemodel_p.cpp:1253
#8 0x7f982408914f in
Akonadi::EntityTreeModel::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**) (_o=0x1760c20, _c=QMetaObject::InvokeMetaMethod, _id=28,
_a=0x7ffcc63da6d0) at
/kde/build/5/akonadiserver/src/core/moc_entitytreemodel.cpp:234
#9 0x7f982b585681 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f9823fd005f in Akonadi::Monitor::itemLinked(Akonadi::Item const&,
Akonadi::Collection const&) (this=0x1802770, _t1=..., _t2=...) at
/kde/build/5/akonadiserver/src/core/moc_monitor.cpp:960
#11 0x7f9823fdd7b1 in
Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification
const&, QVector const&, Akonadi::Collection const&,
Akonadi::Collection const&) (this=0x17b60e0, msg_=...,
items=QVector = {...}, collection=..., collectionDest=...) at
/kde/src/5/akonadiserver/src/core/monitor_p.cpp:1054
#12 0x7f9823fd9cbb in
Akonadi::MonitorPrivate::emitNotification(Akonadi::Protocol::ChangeNotification
const&) (this=0x17b60e0, msg=...) at
/kde/src/5/akonadiserver/src/core/monitor_p.cpp:507
#13 0x7f9823f8458a in
Akonadi::ChangeRecorderPrivate::emitNotification(Akonadi::Protocol::ChangeNotification
const&) (this=0x17b60e0, msg=...) at
/kde/src/5/akonadiserver/src/core/changerecorder_p.cpp:367
#14 0x7f9823fdc49b in Akonadi::MonitorPrivate::flushPipeline()
(this=0x17b60e0) at /kde/src/5/akonadiserver/src/core/monitor_p.cpp:873
#15 0x7f9823fdc4fa in Akonadi::MonitorPrivate::dataAvailable()
(this=0x17b60e0) at /kde/src/5/akonadiserver/src/core/monitor_p.cpp:882
#16 0x7f9823fce24a in Akonadi::Monitor::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=0x1802770,
_c=QMetaObject::InvokeMetaMethod, _id=43, _a=0x7ffcc63db440) at
/kde/build/5/akonadiserver/src/core/moc_monitor.cpp:338
#17 0x7f982b585681 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#18 0x7f9823faac77 in Akonadi::EntityCacheBase::dataAvailable()
(this=0x185d270) at
/kde/build/5/akonadiserver/src/core/moc_entitycache_p.cpp:146
#19 0x7f9823f7d0c8 in Akonadi::EntityListCache::processResult(KJob*)
(this=0x185d270, job=0x251a6c0) at
/kde/src/5/akonadiserver/src/core/entitycache_p.h:499
#20 0x7f9823faaa55 in
Akonadi::EntityCacheBase::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**) (_o=0x185d270, _c=QMetaObject::InvokeMetaMethod, _id=1,
_a=0x7ffcc63db760) at
/kde/build/5/akonadiserver/src/core/moc_entitycache_p.cpp:80
--
You are receiving this mail because:
You are watching all bug changes.
