[plasmashell] [Bug 382340] Notifications are often as 1px vertical line
https://bugs.kde.org/show_bug.cgi?id=382340 Petr Nehez changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #28 from Petr Nehez --- I can confirm this issue is not happening anymore in 5.38. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383166] Plasma hangs on waking up from suspend when USB-C is plugged in
https://bugs.kde.org/show_bug.cgi?id=383166 --- Comment #4 from Dan Duris --- This seems to be resolved with the latest kernel, where the slowdown is just few seconds (e.g. 2-3) instead of 15-20 seconds. Linux 4.13.0-997-generic #201709072202 SMP Fri Sep 8 02:04:38 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 295929] editing variables in debugger
https://bugs.kde.org/show_bug.cgi?id=295929 Kevin Funk changed: What|Removed |Added CC||petross...@gmail.com --- Comment #3 from Kevin Funk --- *** Bug 377291 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377291] KDevelop doesn't allow me to modify a variable's value, when stepping though the code in Debug
https://bugs.kde.org/show_bug.cgi?id=377291 Kevin Funk changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Kevin Funk --- Marking as duplicate. Thanks, Jaka! *** This bug has been marked as a duplicate of bug 295929 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384870] Overlay over canvas while setup Filter layer or mask
https://bugs.kde.org/show_bug.cgi?id=384870 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Krita doesn't do that, it's the window manager which does that. Whether or not that is configurable depends on which window manager you're using. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369474] OCIO - Krita could not initialize OpenGL canvas
https://bugs.kde.org/show_bug.cgi?id=369474 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version|unspecified |3.0.1 Resolution|--- |FIXED --- Comment #4 from Boudewijn Rempt --- Oh yes, should've been fixed for ages. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 384704] Scrolling with mouse roll not working
https://bugs.kde.org/show_bug.cgi?id=384704 Julian Wolff changed: What|Removed |Added CC||wo...@julianwolff.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384863] Global menu not exported for different user
https://bugs.kde.org/show_bug.cgi?id=384863 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |WONTFIX --- Comment #3 from David Edmundson --- You can chmod your session DBus socket, and then export the env vars... Or find a way to proxy it (like your link) but generally speaking this isn't something we want to do on the plasma level. That's up to you when you start the other app. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 384404] Kate and KWrite both crash when editing a Javascript or CSS file
https://bugs.kde.org/show_bug.cgi?id=384404 Kevin Funk changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #5 from Kevin Funk --- Just ran into this as well -> marking as confirmed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357100] The destUrl of 'Show original directory' of a link is wrong in DesktopView showing desktop folder
https://bugs.kde.org/show_bug.cgi?id=357100 --- Comment #5 from Eike Hein --- There was no Folder View rewrite in 5.10. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369658] Different windows from same app show icon defined in .desktop file instead of app-specified icon
https://bugs.kde.org/show_bug.cgi?id=369658 Eike Hein changed: What|Removed |Added CC||p...@ralfj.de --- Comment #43 from Eike Hein --- *** Bug 382142 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382142] Panel icon wrong: Does not match window icon
https://bugs.kde.org/show_bug.cgi?id=382142 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #11 from Eike Hein --- *** This bug has been marked as a duplicate of bug 369658 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 384404] Kate and KWrite both crash when editing a Javascript or CSS file
https://bugs.kde.org/show_bug.cgi?id=384404 --- Comment #6 from Christoph Cullmann --- :( -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 384404] Kate and KWrite both crash when editing a Javascript or CSS file
https://bugs.kde.org/show_bug.cgi?id=384404 --- Comment #7 from Christoph Cullmann --- Thanks for providing the infos in the upstream bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377392] Select Folder on Going up (Feature Request)
https://bugs.kde.org/show_bug.cgi?id=377392 --- Comment #8 from Tsu Jan --- > are you willing to let me take over the patch? Oh, that would be very kind of you! Yes, please! I haven't touched the patch for a long time; it may need to be updated. As far as I remember, at that time, some changes in Dolphin made the job very easy; just a few changes was enough for this functionality to be implemented. Thanks for your attention! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384861] Auto-hide panel should raise when global menu is triggered via Alt-key
https://bugs.kde.org/show_bug.cgi?id=384861 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Two reasons: 1) Because the QMenus don't have a transient parent (and thus panel has no children). 2) My "hack" / "awesome fix" never causes activation only prevents closing. I'll fix this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373676] Bent lines showing up on OSX.
https://bugs.kde.org/show_bug.cgi?id=373676 --- Comment #7 from Boudewijn Rempt --- Git commit f386cdb7686c50ddc0a0842d2921aa3eff87b98e by Boudewijn Rempt. Committed on 20/09/2017 at 09:19. Pushed by rempt into branch 'krita/3.3'. Improve stylus precision on OSX Patch by Bernhard Liebl Differential Revision: https://phabricator.kde.org/D7880 M +8-0libs/ui/CMakeLists.txt M +9-1libs/ui/KisApplication.cpp A +22 -0libs/ui/osx.h [License: LGPL (v2+)] A +32 -0libs/ui/osx.mm https://commits.kde.org/krita/f386cdb7686c50ddc0a0842d2921aa3eff87b98e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 353062] Freeze/failure to start when "show tray icon" is enabled
https://bugs.kde.org/show_bug.cgi?id=353062 Jean-Michaël Celerier changed: What|Removed |Added CC||jeanmichael.celerier@gmail. ||com --- Comment #8 from Jean-Michaël Celerier --- Getting the same bug for months when using QT_QPA_PLATFORMTHEME=kde or QT_QPA_PLATFORMTHEME=plasma Other themes such as QT_QPA_PLATFORMTHEME=plasma do work, but I'd really like to have the "plasma" platform theme (while keeping i3 as a window manager). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 381223] Custom Profile handling bugs
https://bugs.kde.org/show_bug.cgi?id=381223 --- Comment #14 from Jean-Baptiste Mardelle --- Can you please attach or mail me a small video sample or a video clip that triggers this issue ? You should be able to extract a small 5 seconds sample from your video with that command: ffmpeg -i myclip.mp4 -c copy -t 5 output.mp4 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384872] New: Password input field not focused
https://bugs.kde.org/show_bug.cgi?id=384872 Bug ID: 384872 Summary: Password input field not focused Product: kscreenlocker Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: christian.ohrfa...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- Distro: KDE Neon Developer Edition Git-Unstable from 19th August 2017. Plasma: 5.10.9 KDE Frameworks: 5.39.0 Related bugs: 312427 and 316084 Number of users on the system: 1 At the user login (after starting the system) and at the lockscreen (if these two use cases are handled differen internally), the password field of the user is not focused and therefore, needs to be focussed manually (by clicking into the field). This circumstance is unfortunate, because it minimizes flow of user interaction. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373676] Bent lines showing up on OSX.
https://bugs.kde.org/show_bug.cgi?id=373676 --- Comment #8 from Boudewijn Rempt --- Git commit d4bca56cde88f9be851d151aec8091a7a252ad46 by Boudewijn Rempt. Committed on 20/09/2017 at 09:24. Pushed by rempt into branch 'master'. Improve stylus precision on OSX Patch by Bernhard Liebl Differential Revision: https://phabricator.kde.org/D7880 M +8-0libs/ui/CMakeLists.txt M +9-1libs/ui/KisApplication.cpp A +22 -0libs/ui/osx.h [License: LGPL (v2+)] A +32 -0libs/ui/osx.mm https://commits.kde.org/krita/d4bca56cde88f9be851d151aec8091a7a252ad46 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384873] New: Alt/F10 opens appmenu in titlebar
https://bugs.kde.org/show_bug.cgi?id=384873 Bug ID: 384873 Summary: Alt/F10 opens appmenu in titlebar Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 107910 --> https://bugs.kde.org/attachment.cgi?id=107910&action=edit Appmenu in titlebar Alt/F10 tends to open the appmenu. Can we realize this behavior also, when the appmenu is in the titlebar? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 384874] New: DNS server in connection settings does not matter
https://bugs.kde.org/show_bug.cgi?id=384874 Bug ID: 384874 Summary: DNS server in connection settings does not matter Product: plasma-nm Version: 5.8.7 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: romeo.ber...@gmail.com Target Milestone: --- I've run linux mint 18.2 KDE. At begin network worked good but after 30 minutes domain name servers stopped to resolving. I've run mc and saw that /etc/resolv.conf was disabled (before file name was red symbol "!"). I've deleted this file, opened network manager, edited LAN connection and added new DNS IP, saved connection. Then I've executed sudo service network-manager restart but problem was not resolved. Then I've rebooted CPU but problem was not resolved. And after creating new file (because network manager did not create it automatically) /etc/resolv.conf problem was resolved. This problem have being repeated 2 times since installation Linux Mint during 2 weeks -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 384857] Allow zooming out
https://bugs.kde.org/show_bug.cgi?id=384857 Alberto Salvia Novella changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #2 from Alberto Salvia Novella --- Yes, but it's simpler to use the image viewer for that. The zooming would only apply to the current image, not all in the folder. And simply put it feels more natural that way, been able to zoom the image the way you want. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 347323] Add support for changing cursor shape with extended DECSCUSR escape sequences
https://bugs.kde.org/show_bug.cgi?id=347323 James Baxter changed: What|Removed |Added CC||james.bax...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369014] On Apple systems with an AMD CPU, saving to single-layer images hangs Krita
https://bugs.kde.org/show_bug.cgi?id=369014 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/d81bbd498b8cb0c6829a897a |ta/4ee5048486b9e24e79ffc4e4 |31204ec8b4486694|e9f784ea001568a9 --- Comment #43 from Boudewijn Rempt --- Git commit 4ee5048486b9e24e79ffc4e4e9f784ea001568a9 by Boudewijn Rempt. Committed on 20/09/2017 at 09:40. Pushed by rempt into branch 'master'. Disable opengl on OSX if the GPU is AMD For some reason, with Sierra and an AMD gpu Krita hangs when saving images that have no layers (i.e., something keeps the projection locked). This is properly fixed in master with the saving of images in the background. M +3-1libs/ui/opengl/kis_opengl.cpp https://commits.kde.org/krita/4ee5048486b9e24e79ffc4e4e9f784ea001568a9 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369014] On Apple systems with an AMD CPU, saving to single-layer images hangs Krita
https://bugs.kde.org/show_bug.cgi?id=369014 Boudewijn Rempt changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kri ||ta/d81bbd498b8cb0c6829a897a ||31204ec8b4486694 Resolution|--- |FIXED --- Comment #42 from Boudewijn Rempt --- Git commit d81bbd498b8cb0c6829a897a31204ec8b4486694 by Boudewijn Rempt. Committed on 20/09/2017 at 09:38. Pushed by rempt into branch 'krita/3.3'. Disable opengl on OSX if the GPU is AMD For some reason, with Sierra and an AMD gpu Krita hangs when saving images that have no layers (i.e., something keeps the projection locked). This is properly fixed in master with the saving of images in the background. M +3-1libs/ui/opengl/kis_opengl.cpp https://commits.kde.org/krita/d81bbd498b8cb0c6829a897a31204ec8b4486694 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 384874] DNS server in connection settings does not matter
https://bugs.kde.org/show_bug.cgi?id=384874 Jan Grulich changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||jgrul...@redhat.com Resolution|--- |WONTFIX --- Comment #1 from Jan Grulich --- Doesn't sound like an issue in plasma-nm. Report this please to NetworkManager bugzilla. https://bugzilla.gnome.org/page.cgi?id=browse.html&product=NetworkManager -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382340] Notifications are often as 1px vertical line
https://bugs.kde.org/show_bug.cgi?id=382340 --- Comment #29 from Mykola Krachkovsky --- I can confirm too. Notifications in 5.38 are fine. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384875] New: Plasma Crashed
https://bugs.kde.org/show_bug.cgi?id=384875 Bug ID: 384875 Summary: Plasma Crashed Product: plasmashell Version: 5.10.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kedar.a...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.10.0-35-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: I was using Skype, Google Chrome, Kmail, Firefox. My video in Skype froze while having a conversation. So I disconnected the call and exited skype by right clicking on the icon in the try. And I got a message Plasma crashed. I have the updated Skype client. My KDE Neon is a fairly new fresh install on a Dell Optiplex Desktop. All updates and patches are regularly taken as and when they arrive. Regards -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef4cca88c0 (LWP 1353))] Thread 18 (Thread 0x7fee490a9700 (LWP 7311)): #0 0x7fef474f324d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fef3bfd2f61 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #2 0x7fef3cd6aa2e in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fef3cd6b4a0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fef3cd6b560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fef3cd797a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fef3c001078 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #7 0x7fef46a9c6ba in start_thread (arg=0x7fee490a9700) at pthread_create.c:333 #8 0x7fef475033dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7fae337ff700 (LWP 6252)): #0 0x7fef474f770d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fef42e9438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fef42e9449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fef47e1f94b in QEventDispatcherGlib::processEvents (this=0x7fae280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fef47dc87ca in QEventLoop::exec (this=this@entry=0x7fae337fece0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fef47bf1cd4 in QThread::exec (this=this@entry=0x200ab60) at thread/qthread.cpp:515 #6 0x7fef4a2c00c5 in QQmlThreadPrivate::run (this=0x200ab60) at qml/ftw/qqmlthread.cpp:147 #7 0x7fef47bf6989 in QThreadPrivate::start (arg=0x200ab60) at thread/qthread_unix.cpp:368 #8 0x7fef46a9c6ba in start_thread (arg=0x7fae337ff700) at pthread_create.c:333 #9 0x7fef475033dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7fee49ffb700 (LWP 3947)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef47bf78eb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x8124c50) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x742d650, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fee6e4ea6df in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7fee6e4ee768 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fee6e4e98cd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fee6e4ee7c2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fee6e4e98cd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fee6e4ec2e0 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fef47bf6989 in QThreadPrivate::start (arg=0x7fee44002f90) at thread/qthread_unix.cpp:368 #10 0x7fef46a9c6ba in start_thread (arg=0x7fee49ffb700) at pthread_create.c:333 #11 0x7fef475033dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7fee4a7fc700 (LWP 3946)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef47bf78eb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x8124c50) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x74
[kwin] [Bug 376245] Mouse cursor changes size when pointer on Kwin window title bar
https://bugs.kde.org/show_bug.cgi?id=376245 --- Comment #14 from Eric Donkersloot --- I tried both workarounds listed in this bug report: 1. Setting the cursor size to a fixed value (36) 2. Create ~/.icons/default/index.theme and set the cursor theme like in KDE But they both have no effect. I've posted the output of "qdbus org.kde.KWin /KWin supportInformation" again here: https://paste.kde.org/pjoxuk9ej/w7hv2v -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 321209] [wish] Thumbnail view in 'compact mode'
https://bugs.kde.org/show_bug.cgi?id=321209 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #4 from Christoph Feck --- This is present in many KDE applications (at least Dolphin, Gwenview, and Digikam). They use a grid instead of a flow layout. But this is especially bad with Gwenview because the grid is not square, causing a bigger empty space with portrait images. Digikam uses a square grid. Nate, an image of the expected result is in comment #0. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384876] New: project import inefficiency
https://bugs.kde.org/show_bug.cgi?id=384876 Bug ID: 384876 Summary: project import inefficiency Product: kdevelop Version: unspecified Platform: Compiled Sources OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: rjvber...@gmail.com Target Milestone: --- These are observations by Sven Brauch taken from a phabricator review. Not taking credit, nor taking the challenge to address the reported issue just yet. I may in due time if no one more qualified beats me to it. The observations probably pertain to the cmake project plugin, in "CMake Server" mode (which is roughly 4x slower than the json-based importer in my own benchmarks). >> It indeed takes ages to import the project, and I couldn't figure out why ... it is certainly not CPU load. I looked in perf, the CPU time spent in importing the project is quite low. In fact, the code model generation (which seems to be the last step in the import AFAIU) finishes relatively quickly here (after something like 5 seconds), but then it still takes like 30 seconds for the import to finish. I don't know where that time is spent. This is a bug, something is waiting too long for something else. Let's find the bug instead of introducing checkboxes to work around it. Here's the two things that are broken and need fixing: 1. FileManagerListJob has a queue of directories to list. It processes those sequentially, and after listing each, it goes through the event loop (async slot invocation) to list the next. This takes aages for lots of directories to list, which are mostly spent waiting and not in actual CPU time. When doing this synchronously as a test, it takes maybe half a second instead of 30 seconds. 2. The reason this is noticeable now is that for some reason, it lists all the build dirs. This is probably a bug in the new cmake importer, they should not be listed. Fixing the second point would solve the problem, but fixing the first one somehow (just making it sync isn't a solution, but there is certainly a better way) would also be very nice since it will further speed up the import. The first point is IMO the much worse bug, since that is what will cause large project imports (think clang) be very slow in either case. For completely no reason whatsoever. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384784] kmail crash when selecting enable system tray icon
https://bugs.kde.org/show_bug.cgi?id=384784 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- No problem in last version. Could you verify in last version please ? Thanks -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384656] progress bar resizes itself when hovering links
https://bugs.kde.org/show_bug.cgi?id=384656 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- Fixed in master -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384797] UI Freezes 100% CPU usage of 1 core while clicking on clip with spacer tool in large project
https://bugs.kde.org/show_bug.cgi?id=384797 carion.nico...@gmail.com changed: What|Removed |Added CC||carion.nico...@gmail.com --- Comment #1 from carion.nico...@gmail.com --- This won't fix in the current version of Kdenlive, but will probably be better in the next, because of significant rewrites of that part of the code. Please stay tuned and give it a new try when the new version (probably 17.12) is out. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384797] UI Freezes 100% CPU usage of 1 core while clicking on clip with spacer tool in large project
https://bugs.kde.org/show_bug.cgi?id=384797 alcinos changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX CC||french.ebook.lo...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384877] New: (ARM64) Added translation for instruction LDRSW (literal)
https://bugs.kde.org/show_bug.cgi?id=384877 Bug ID: 384877 Summary: (ARM64) Added translation for instruction LDRSW (literal) Product: valgrind Version: unspecified Platform: unspecified OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: rosko...@sit.fhg.de Target Milestone: --- Created attachment 107911 --> https://bugs.kde.org/attachment.cgi?id=107911&action=edit The patch for the file priv/guest_arm64_toIR.c Hi, the instruction LDRSW (literal) was not handled by vex. I implemented this instruction to the best of my knowledge. Maybe you can apply the patch to your repository. Or modify the code as you wish. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384878] New: Crash due touchdocker when opening a new document.
https://bugs.kde.org/show_bug.cgi?id=384878 Bug ID: 384878 Summary: Crash due touchdocker when opening a new document. Product: krita Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- Application: krita (4.0.0-pre-alpha (git 16113f5)) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.10.0-33-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: 1. Open file, this will succeed 2. doodle, save close file. this will succeed. 3. Make a new document, this will crash. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f87225c7900 (LWP 32544))] Thread 6 (Thread 0x7f8706126700 (LWP 5080)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f8736cfa826 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f8736cf5e9a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f8736cf9989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8730cc06ba in start_thread (arg=0x7f8706126700) at pthread_create.c:333 #5 0x7f87363f03dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f86d9ed9700 (LWP 32555)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f8736cfa8eb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f8737a56d8a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #3 0x7f8736cf9989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8730cc06ba in start_thread (arg=0x7f86d9ed9700) at pthread_create.c:333 #5 0x7f87363f03dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f86ebe15700 (LWP 32554)): #0 0x7f87363e470d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f872f6c638c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f872f6c649c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8736f2294b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8736ecb7ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8736cf4cd4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8714f0b0c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f8736cf9989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8730cc06ba in start_thread (arg=0x7f86ebe15700) at pthread_create.c:333 #9 0x7f87363f03dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f86eb614700 (LWP 32552)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f8736cfa8eb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f8736cf3a16 in QSemaphore::tryAcquire(int, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f87342c75d3 in KisTileDataSwapper::waitForWork (this=) at /home/wolthera/krita/src/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #4 0x7f87342c77ca in KisTileDataSwapper::run (this=0x7f8734799b80 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>) at /home/wolthera/krita/src/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #5 0x7f8736cf9989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8730cc06ba in start_thread (arg=0x7f86eb614700) at pthread_create.c:333 #7 0x7f87363f03dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f8714c32700 (LWP 32546)): #0 0x7f87363e024d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f872f7096f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f872f6c5e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f872f6c6330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f872f6c649c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8736f2294b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8736ecb7ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8736cf4cd4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Co
[calligraplan] [Bug 384879] New: file crashes plan every time 20170920
https://bugs.kde.org/show_bug.cgi?id=384879 Bug ID: 384879 Summary: file crashes plan every time 20170920 Product: calligraplan Version: 2.9.11 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dand...@get2net.dk Reporter: wch-t...@house-grp.net Target Milestone: --- Application: calligraplan (2.9.11) KDE Platform Version: 4.14.25 Qt Version: 4.8.6 Operating System: Linux 4.4.87-18.29-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: I was using plan to help me prioritize some tasks. Just a pretty simple todo list. I was editing the list and adding tasks and rearranging the tasks and learning about plan. In particular, I was testing printing and flaging features. After a time, I noticed the work had become corrupted. By that I mean that the order of the tasks in the edit mode was different from the order of the tasks as displayed in the graphics mode. I thought closing and opening the program might clear that up. No. Now that file crashes the program every time an attempt to open it is made. I will send the file with this report if that is possible, otherwise, if you are interested in it, you may request it. The crash can be reproduced every time. -- Backtrace: Application: Plan (calligraplan), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7fe4fe45f8d7 in raise () from /lib64/libc.so.6 #7 0x7fe4fe460caa in abort () from /lib64/libc.so.6 #8 0x7fe4fe49d1b4 in __libc_message () from /lib64/libc.so.6 #9 0x7fe4fe4a2706 in malloc_printerr () from /lib64/libc.so.6 #10 0x7fe4fe4a3453 in _int_free () from /lib64/libc.so.6 #11 0x7fe4fcb8bd68 in QString::free (d=0x3450034) at tools/qstring.cpp:1235 #12 0x7fe4e99a9b79 in QString::~QString (this=0x7ffd0bf10040, __in_chrg=) at /usr/include/QtCore/qstring.h:880 #13 KPlato::Report::findReportData (lst=..., type=...) at /usr/src/debug/calligra-2.9.11/plan/libs/ui/reports/reportdata.cpp:85 #14 0x7fe4e99a2c75 in KPlato::ReportDesigner::setReportData (this=0x33ac9a0, tag=...) at /usr/src/debug/calligra-2.9.11/plan/libs/ui/reports/reportview.cpp:1254 #15 0x7fe4fcc590ea in QMetaObject::activate (sender=sender@entry=0x33b8af0, m=m@entry=0x7fe4e9c9a4e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd0bf101c0) at kernel/qobject.cpp:3576 #16 0x7fe4e9998792 in KPlato::ReportSourceEditor::selectFromChanged (this=this@entry=0x33b8af0, _t1=...) at /usr/src/debug/calligra-2.9.11/build/plan/libs/ui/moc_reportsourceeditor.cpp:105 #17 0x7fe4e99ae60f in KPlato::ReportSourceEditor::slotCurrentIndexChanged (this=0x33b8af0) at /usr/src/debug/calligra-2.9.11/plan/libs/ui/reports/reportsourceeditor.cpp:49 #18 0x7fe4e9998736 in KPlato::ReportSourceEditor::qt_static_metacall (_o=, _c=, _id=, _a=) at /usr/src/debug/calligra-2.9.11/build/plan/libs/ui/moc_reportsourceeditor.cpp:54 #19 0x7fe4fcc590ea in QMetaObject::activate (sender=sender@entry=0x33bae80, m=m@entry=0x7fe4fe0fdd80 , local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7ffd0bf10340) at kernel/qobject.cpp:3576 #20 0x7fe4fda144b1 in QComboBox::currentIndexChanged (this=this@entry=0x33bae80, _t1=1) at .moc/release-shared/moc_qcombobox.cpp:315 #21 0x7fe4fda14511 in QComboBoxPrivate::_q_emitCurrentIndexChanged (this=this@entry=0x33baeb0, index=...) at widgets/qcombobox.cpp:1278 #22 0x7fe4fda147bc in QComboBoxPrivate::setCurrentIndex (this=this@entry=0x33baeb0, mi=...) at widgets/qcombobox.cpp:2049 #23 0x7fe4fda14a0f in QComboBox::setCurrentIndex (this=, index=index@entry=1) at widgets/qcombobox.cpp:2025 #24 0x7fe4e99aeb0f in KPlato::ReportSourceEditor::setSourceData (this=0x33b8af0, element=...) at /usr/src/debug/calligra-2.9.11/plan/libs/ui/reports/reportsourceeditor.cpp:74 #25 0x7fe4e99a2def in KPlato::ReportDesigner::setData (this=this@entry=0x33ac9a0) at /usr/src/debug/calligra-2.9.11/plan/libs/ui/reports/reportview.cpp:1129 #26 0x7fe4e99a3020 in KPlato::ReportDesigner::setData (this=this@entry=0x33ac9a0, doc=...) at /usr/src/debug/calligra-2.9.11/plan/libs/ui/reports/reportview.cpp:1115 #27 0x7fe4e99a34f0 in KPlato::ReportDesigner::loadContext (this=0x33ac9a0, context=...) at /usr/src/debug/calligra-2.9.11/plan/libs/ui/reports/reportview.cpp:1347 #28 0x7fe4e999a594 in KPlato::ReportView::loadContext (this=this@entry=0x334fdd0, context=...) at /usr/src/debug/calligra-2.9.11/plan/libs/ui/reports/reportview.cpp:240 #29 0x7fe4e9d23e8a in KPlato::View::createViews (this=this@entry=0x1b149f0) at /usr/src/debug/calligra-2.9.11/plan/kptview.cpp:539 #30 0x7fe4e9d246ae in KPlato::View::initiateViews (this=0x1b149f0) at /usr/src/debug/calligra-2.9.11/plan/kptview.cpp:444 #31 0
[gwenview] [Bug 348746] Background color in fullscreen mode should use System Settings > Colors > Tooltip Background color
https://bugs.kde.org/show_bug.cgi?id=348746 Christoph Feck changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Christoph Feck --- There is a slider to change the background brightness in the settings dialog. Using the tooltip color whould be distracting for those (incl. me) who have classic yellow as the tooltip color. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 348746] Background color in fullscreen mode should use System Settings > Colors > Tooltip Background color
https://bugs.kde.org/show_bug.cgi?id=348746 Christoph Feck changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from Christoph Feck --- Ah sorry, this ticket is about the slideshow. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384797] UI Freezes 100% CPU usage of 1 core while clicking on clip with spacer tool in large project
https://bugs.kde.org/show_bug.cgi?id=384797 --- Comment #2 from b...@stefantriller.de --- Thank you for this information. Is there any preview version of 17.12. that I could use to move my clips around? And more important: if such a preview version exists, is it compatible project-wise with the 17.08.1, so afterwards I can open it again with the older version and continue editing there? Because its really annoying to wait for minutes until something happens. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 356998] After cropping a .jpg image and cancelling/denying the crop operation, the preview icon shows the cropped version in the directory browser
https://bugs.kde.org/show_bug.cgi?id=356998 Christoph Feck changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #4 from Christoph Feck --- I can still reproduce using the provided steps. The browse mode shows the cropped version after undoing the crop. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 359269] When I open a picture showing me a yucky dialog (see URL)
https://bugs.kde.org/show_bug.cgi?id=359269 Christoph Feck changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 362295 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 362295] No such object path '/modules/kdeconnect/devices/_d05cbcbd_dea5_4135_949c_6430342eec97_/sftp'
https://bugs.kde.org/show_bug.cgi?id=362295 Christoph Feck changed: What|Removed |Added CC||yerayli...@gmail.com --- Comment #9 from Christoph Feck --- *** Bug 359269 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 360590] The background in fullscreen mode is not black, even is it is set to black in the settings.
https://bugs.kde.org/show_bug.cgi?id=360590 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 348746 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 348746] Background color in fullscreen mode should use System Settings > Colors > Tooltip Background color
https://bugs.kde.org/show_bug.cgi?id=348746 Christoph Feck changed: What|Removed |Added CC||tho@gmx.net --- Comment #5 from Christoph Feck --- *** Bug 360590 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 362158] Plugins missing after upgrade from 14.04 LTS to 16.04 LTS
https://bugs.kde.org/show_bug.cgi?id=362158 --- Comment #2 from Christoph Feck --- See also https://bugs.launchpad.net/ubuntu/+source/gwenview/+bug/1594156 This is fixed in Kubuntu 17.04 version. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 362249] Blue/Red inversion
https://bugs.kde.org/show_bug.cgi?id=362249 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |DOWNSTREAM Status|NEEDSINFO |RESOLVED --- Comment #3 from Christoph Feck --- RGB vs. BGR is a driver issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384797] UI Freezes 100% CPU usage of 1 core while clicking on clip with spacer tool in large project
https://bugs.kde.org/show_bug.cgi?id=384797 --- Comment #3 from alcinos --- Currently, the best way to have a preview of the next version is to build it yourself from git (branch "refactoring_timeline"). We are working to provide some appImage builds but that's not available yet. Be aware that this is still under heavy development, and important features might still be missing. Also note that the projects won't be backwards compatible. If you save in 17.12, you won't be able to open in 17.08. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377746] crash at startup
https://bugs.kde.org/show_bug.cgi?id=377746 --- Comment #4 from MB --- Hi! digikam-5.7.0-01-x86-64.appimage build on 30-Aug-2017 works on CentOS 7.4-1708! Thanks. Best regards -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 384880] New: Dirwatcher inefficiency when using QFileSystemWatcher
https://bugs.kde.org/show_bug.cgi?id=384880 Bug ID: 384880 Summary: Dirwatcher inefficiency when using QFileSystemWatcher Product: kdevplatform Version: unspecified Platform: Compiled Sources OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: filemanager Assignee: kdevelop-bugs-n...@kde.org Reporter: rjvber...@gmail.com Target Milestone: --- Creating dirwatcher is largely negligible in terms of cost on Linux when inotify is (can be used). For instance, when importing a pre-existing project for the GCC 7.2.0 source tree on Linux (1.6Ghz N3150 CPU, ZFS on an SSHD), with dirwatcher creation deferred to after the initial project load and full-project parsing off: kdevplatform.shell: Starting project import timer kdevplatform.shell: All projects imported in 17.948 seconds kdevplatform.filemanager: Project dir monitoring is enabled for project "gcc-7.2.0-MP" kdevplatform.shell: creating dir watchers and/or starting parse jobs took an additional 1.189 seconds kdevplatform.filemanager: Deleting dir watcher took 0.024 seconds for project "gcc-7.2.0-MP" 31.069 user_cpu 5.016 kernel_cpu 0:34.10 total_time 105.7%CPU When forcing the use of QFileSystemWatcher (using KDIRWATCH_METHOD=QFSWatch), those figures become kdevplatform.shell: Starting project import timer kdevplatform.shell: All projects imported in 17.701 seconds kdevplatform.filemanager: Project dir monitoring is enabled for project "gcc-7.2.0-MP" kdevplatform.shell: creating dir watchers and/or starting parse jobs took an additional 179.013 seconds kdevplatform.filemanager: Deleting dir watcher took 256.16 seconds for project "gcc-7.2.0-MP" 470.119 user_cpu 19.310 kernel_cpu 7:39.48 total_time 106.5%CPU (On Mac OS X with a 2.7Ghz i7 and HFS on a regular 7200RPM HDD, creation:destruction take roughly 85:176 seconds) These long wait times are spent entirely in KDirWatch method, blocking the thread's event loop (and the UI in this case) and running at 100%CPU (on Mac and Linux alike). Deferring dirwatcher creation means the host OS has had opportunity to cache the directory structure, and indeed profiling the operation on OS X shows that the time is mostly spent in memory allocation and string comparison. I think the extent of the overhead is due to an inefficiency in the way dirwatching is implemented. A project nothing but a directory which will usually contain other directories. Rather than doing actual dirwatching (watching the project directory for changes), KDevelop installs watchers on each and every item in the project tree. Notifications are only used for keeping the tree in the project toolview uptodate. The KDirWatch::created signal can lead to emitting a fileAdded signal, but that KDirWatch signal (quote) " is not emitted when creating a file is created in a watched directory". IOW and IIUC that signal is thus only emitted when a watch was added for a non-existent file, which KDevelop doesn't do. All this to say that I think it should be possible to rewrite this implementation to watch only project directories for change, and invoke `eventuallyReadFolder()` when a change is detected. This is an automated version of how I have always worked with KDevelop on Mac (where dirwatching doesn't work), and I don't have the impression that I'm missing any features because of it. Adding only project directories to the project dirwatcher will 1) speed up its creation on all platforms and 2) will help avoid file descriptor depletion on BSD variants (the kqueue-based QFSW backend uses 2 filedescriptors per watched item, if memory serves me well, and depletion is not just a theoretical possibility as I've observed with Qt4/KDevelop4 on Mac - OS X is a BSD variant too). And finally 3) it should be possible to make the non-recursive KDirWatch::addDir() call in eventuallyReadFolder or even in the FileManagerListJob instance it creates. That could improve efficiency even more by reducing the number of directory traversals. NB: change detection in open documents does not depend on project dirwatching so will not be affected by the proposed change. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 374581] browse missing icons on hover the image
https://bugs.kde.org/show_bug.cgi?id=374581 --- Comment #5 from Christoph Feck --- Does it work when you run Gwenview from a shell using: XDG_CURRENT_DESKTOP=KDE gwenview -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 381535] Left panel is not indented properly
https://bugs.kde.org/show_bug.cgi?id=381535 Christoph Feck changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #2 from Christoph Feck --- Nate, there is no margin. What you might see is the window border? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362035] Incorrect layout of Hard Disk Usage widget in a vertical panel after logout
https://bugs.kde.org/show_bug.cgi?id=362035 --- Comment #11 from H Rantala --- Still happening. I don't know if this helps, but for some reason every time I logged in plasmashell crashed and was restarted and after that the layout of Hard Disk Usage was ok. I recreated all plasma related config files and now plasma does not crash, but layout is incorrect again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384870] Overlay over canvas while setup Filter layer or mask
https://bugs.kde.org/show_bug.cgi?id=384870 --- Comment #2 from Andras --- Thanks for the prompt response! I won't assume there is option to ask for advice here seems it's an invalid report although I was guided on Krita's IRC to report a bug here about this. system related info: nvidia 375.82 / kde plasma 5.8.6 / Qt 5.7.1 / kernel 4.9.0-3-amd64 It's ok if it will be deleted anyway. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384797] UI Freezes 100% CPU usage of 1 core while clicking on clip with spacer tool in large project
https://bugs.kde.org/show_bug.cgi?id=384797 --- Comment #4 from b...@stefantriller.de --- Thank you for the clarification, although this means that I have to wait some time to get the spaces for the clips I want to insert at the beginning of my large project because the movie should be finished before December. Anyway, I will give it a try with the new version to see if it improves the situation and if not I will create a new bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384004] Add ability to navigate widgets by dragging if all widgets don't fit into panel
https://bugs.kde.org/show_bug.cgi?id=384004 Christoph Feck changed: What|Removed |Added Severity|normal |wishlist --- Comment #1 from Christoph Feck --- For those use cases (narrow screen), a two-line panel would be better. You would probably constantly scroll forth and back to see all widgets. Since stacked panels are not supported, right now you have a to use a top and a bottom panel. This is also the solution many other desktops use. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384870] Overlay over canvas while setup Filter layer or mask
https://bugs.kde.org/show_bug.cgi?id=384870 --- Comment #3 from Boudewijn Rempt --- With kwin, the option is here: right-click on the titlebar choose More Actions/Window Manager Settings Go to the Desktop Effects page Search for "Dialog Parent" and uncheck it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384757] Enable slim Kickoff variant
https://bugs.kde.org/show_bug.cgi?id=384757 --- Comment #2 from Matthias --- Yes, correct. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384870] Overlay over canvas while setup Filter layer or mask
https://bugs.kde.org/show_bug.cgi?id=384870 --- Comment #4 from Andras --- I'm amazed, thank you so much, it works! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384135] [Panel] Doesn't remember widget placement if you adjusted manually
https://bugs.kde.org/show_bug.cgi?id=384135 --- Comment #7 from Christoph Feck --- Well, you need to add a spacer. But since this is reported quite often, I keep this open to investigate if there is a better way to make this understandable in the UI, for example, by already flushing the layout during configuration. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 383018] Discover crash.
https://bugs.kde.org/show_bug.cgi?id=383018 Aleix Pol changed: What|Removed |Added CC||s.scalabri...@gmail.com --- Comment #1 from Aleix Pol --- *** Bug 384848 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384848] Discover crashes when I search for something
https://bugs.kde.org/show_bug.cgi?id=384848 Aleix Pol changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 383018 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384725] Crashes on opening app's page
https://bugs.kde.org/show_bug.cgi?id=384725 Aleix Pol changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 383018 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 383018] Discover crash.
https://bugs.kde.org/show_bug.cgi?id=383018 Aleix Pol changed: What|Removed |Added CC||masyanov...@gmail.com --- Comment #2 from Aleix Pol --- *** Bug 384725 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland
https://bugs.kde.org/show_bug.cgi?id=379174 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 384880] Dirwatcher inefficiency when using QFileSystemWatcher
https://bugs.kde.org/show_bug.cgi?id=384880 --- Comment #1 from Milian Wolff --- Thanks for creating this report so we can track this properly. Some notes: a) - kdev should only watch directories, CMakeLists.txt files and open files for changes - the CMakeLists.txt used to be required, now that we use the cmake server it may not be required anymore, we'll have to check that again. - so if you say all files are watched then this needs to be fixed - it shouldn't be the case b) - if using QFSWatch shows hotspots in memory allocation and string comparison, then those should be fixed in QFileSystemWatcher upstream. Writing a separate benchmark (standalone from kdevelop) for that purpose would help a lot. I imagine KDirWatch would contain a benchmark, if not, then one should be added that resembles the workload you are seeing. Similarly, such a benchmark would be helpful upstream in Qt itself So I think a) is the actual bug you have uncovered and that needs to be fixed. b) can then also be done on top of that, to improve the situation even further -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384165] Plasma5 Crash after Updating System with Update Plugin
https://bugs.kde.org/show_bug.cgi?id=384165 Christoph Feck changed: What|Removed |Added CC||ffds...@gmail.com --- Comment #1 from Christoph Feck --- *** Bug 384611 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384611] Plasma Crashed after update vlc libs
https://bugs.kde.org/show_bug.cgi?id=384611 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 384165 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384498] Plasma crashes during normal updates installation
https://bugs.kde.org/show_bug.cgi?id=384498 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 384165 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384165] Plasma5 Crash after Updating System with Update Plugin
https://bugs.kde.org/show_bug.cgi?id=384165 Christoph Feck changed: What|Removed |Added CC||jes...@goll-rossau.dk --- Comment #2 from Christoph Feck --- *** Bug 384498 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384204] can't submit a crash report
https://bugs.kde.org/show_bug.cgi?id=384204 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Christoph Feck --- There is not enough information to address this issue. The attachment only talks about 'kdenlive' video editor, which is unrelated to Plasma. Please ask in a forum of your distribution for help with crash reporting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384214] Plasma shell crash when dragging panel to other screen
https://bugs.kde.org/show_bug.cgi?id=384214 Christoph Feck changed: What|Removed |Added CC||michal.dybc...@gmail.com --- Comment #4 from Christoph Feck --- *** Bug 384030 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384030] Plasmashell freezes and crashes when panel is moved on left or right side of screen
https://bugs.kde.org/show_bug.cgi?id=384030 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 384214 *** -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 384881] New: Crash on logout button click from application launcher menu
https://bugs.kde.org/show_bug.cgi?id=384881 Bug ID: 384881 Summary: Crash on logout button click from application launcher menu Product: ksmserver Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: jsbm...@gmail.com Target Milestone: --- Created attachment 107912 --> https://bugs.kde.org/attachment.cgi?id=107912&action=edit Crash info. When go to application launcher and then clicked "Logout", ksm server has crashed. Before this I have changed Intel video to Nvidia. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384882] New: Rendering broken after fbconfig visual matching change in XServer
https://bugs.kde.org/show_bug.cgi?id=384882 Bug ID: 384882 Summary: Rendering broken after fbconfig visual matching change in XServer Product: kwin Version: 5.10.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: glx Assignee: kwin-bugs-n...@kde.org Reporter: commendsar...@gmail.com Target Milestone: --- Created attachment 107913 --> https://bugs.kde.org/attachment.cgi?id=107913&action=edit good Hi all, After Xserver git commit 4486d199bd3bcb5b2b8ad9bc54eb11604d9bd653, the fbconfig visual matching system has changed. This results in incorrect rendering when KWin compositing is enabled. The Xorg developer has reproduced the issue but believes this is a Kwin application bug. Here is the original xorg bug report: https://bugs.freedesktop.org/show_bug.cgi?id=102806 I am using Mesa on Radeonsi, and both the OpenGL3.1 and 2.0 backends have the same corruption, while the Xrender option is still incorrect, but the incorrect color is a bit less notable. Please see the attachments for the good and bad behavior. I can provide any more information, and test any patches. Thanks, Sarnex -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384882] Rendering broken after fbconfig visual matching change in XServer
https://bugs.kde.org/show_bug.cgi?id=384882 --- Comment #1 from Nick Sarnie --- Created attachment 107914 --> https://bugs.kde.org/attachment.cgi?id=107914&action=edit bad -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384882] Rendering broken after fbconfig visual matching change in XServer
https://bugs.kde.org/show_bug.cgi?id=384882 Nick Sarnie changed: What|Removed |Added CC||commendsar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 384798] KFind launcher for the toolbar
https://bugs.kde.org/show_bug.cgi?id=384798 --- Comment #2 from Matthias --- I am aware about this. Toolbar is somewhere else. I like it in the toolbar. Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383776] Add LatteDock to Look and Feel
https://bugs.kde.org/show_bug.cgi?id=383776 Matthias changed: What|Removed |Added Resolution|INVALID |UNMAINTAINED --- Comment #2 from Matthias --- https://en.wikipedia.org/wiki/Open-source_software_development -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 377895] "Close Description" button has UI/UX issues; should just be a regular back button
https://bugs.kde.org/show_bug.cgi?id=377895 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dis ||cover/d6318b0d0df488cb40196 ||4e7607d4dc0ea85a21d Status|UNCONFIRMED |RESOLVED --- Comment #5 from Aleix Pol --- Git commit d6318b0d0df488cb401964e7607d4dc0ea85a21d by Aleix Pol. Committed on 20/09/2017 at 14:03. Pushed by apol into branch 'master'. Add a header into the ApplicationPage Removes the clashing with the controls when it's compact. Solves some issues with the current close control M +150 -180 discover/qml/ApplicationPage.qml https://commits.kde.org/discover/d6318b0d0df488cb401964e7607d4dc0ea85a21d -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384135] [Panel] Doesn't remember widget placement if you adjusted manually
https://bugs.kde.org/show_bug.cgi?id=384135 --- Comment #8 from Matthew Trescott --- Why not simply record which side of the panel a widget is anchored to, except for task managers which expand to fill all available space? Then spacers wouldn't be needed. I suppose this idea might break add-on widgets though. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 384880] Dirwatcher inefficiency when using QFileSystemWatcher
https://bugs.kde.org/show_bug.cgi?id=384880 --- Comment #2 from RJVB --- If CMakeLists.txt files are to be monitored that should be an additional action taken by the CMake project manager, not by a generic file manager. And that was once necessary it should not be removed until support for older cmake versions is officially and completely removed. (Which in turn shouldn't happen until cmake server mode works as reliably and efficiently as the json-based mode, IMHO). The venom is in this call: d->m_watchers[project]->addDir(project->path().toLocalFile(), KDirWatch::WatchSubDirs | KDirWatch:: WatchFiles ); Removing the KDirWatch::WatchFiles should already be an improvement, but I'd hope that doing the addDir() only for folders that are actually being loaded might at the same time avoid putting a monitor on excluded folders. Assuming that's OK of course. > b) Maybe. I've queried the Qt ML for feedback on this, and for the existence of a dedicated benchmark but I'm going to go with the null hypothesis that the QFSW API isn't new and has had ample opportunity for fine-tuning by Qt experts. We're just using it in a very intensive way here. I think that the GCC source tree contains almost 8000 files in I don't know how many directories. It doesn't strike me as odd that memory allocation and string comparisons show up as hotspots when creating or deleting that many QFSW entries involve that kind of operation. I'm a bit surprised that "only" 8000 or so allocations and string comparisons can be that expensive in terms of processing time but not incredulous. It's really not something I want to dig into at the moment. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 384880] Dirwatcher inefficiency when using QFileSystemWatcher
https://bugs.kde.org/show_bug.cgi?id=384880 --- Comment #3 from RJVB --- Created attachment 107915 --> https://bugs.kde.org/attachment.cgi?id=107915&action=edit profiling overview on Mac, dirwatcher creation -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 384859] Drag and drop a file doesn't work in Windows
https://bugs.kde.org/show_bug.cgi?id=384859 Asko Eronen changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Asko Eronen --- Typical. After several years of waiting someone to fix this, and one failed attempt to debug the issue from source by my self, I finally managed to make a bug report just to see, that after 24 hours from it, it's no longer an issue. Excuse me for making this useless bug report. I'm sure I tried the same Kate build yesterday and the drag 'n drop didn't work. Now that I tried it again, it works... This bug report can be closed now. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 384880] Dirwatcher inefficiency when using QFileSystemWatcher
https://bugs.kde.org/show_bug.cgi?id=384880 --- Comment #4 from RJVB --- Created attachment 107916 --> https://bugs.kde.org/attachment.cgi?id=107916&action=edit profiling overview on Mac, dirwatcher destruction -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 384883] New: Issues to Export / Import Calendars
https://bugs.kde.org/show_bug.cgi?id=384883 Bug ID: 384883 Summary: Issues to Export / Import Calendars Product: kalarm Version: 2.11.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Akonadi Assignee: djar...@kde.org Reporter: rfernan...@cbm.sc.gov.br Target Milestone: --- 732/5000 Hello I would like to report that it is not possible to export / import calendars in KAlarm, version 2.11.4-5ak. When you try to export an alarm and calendars the following message appears: Failed to save new calendar to: / home / Desktop / alarm.ics Another attempt I made was to go to the KAlarm folder (/home/.local/share/kalarm) and copy the files "expired.ics" and "displaying.ics". Then I imported these files into KAlarm that is installed on another computer. However, after importing these files no calendar appears in the program! I really need your help because I use the program a long time and I have dozens of alarms saved there that need to be imported to another machine! Thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 384883] Issues to Export / Import Calendars
https://bugs.kde.org/show_bug.cgi?id=384883 Rafael Fernandes changed: What|Removed |Added Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 384874] DNS server in connection settings does not matter
https://bugs.kde.org/show_bug.cgi?id=384874 Roman changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WONTFIX |--- --- Comment #2 from Roman --- Hey, you don't full me. I use KDE why do you send me to Gnome? No no. Resolve bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384884] New: Crash on screen resize
https://bugs.kde.org/show_bug.cgi?id=384884 Bug ID: 384884 Summary: Crash on screen resize Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@davidedmundson.co.uk Target Milestone: --- >From the trace I'd say I'm running glDeleteProgram() without a context? I'm not fully sure why it's not reliably reproducible. I've spent a big chunk of the day switching screen scales (and so geometry) constantly, and hit this twice. Do we sometimes "leak" the doneCurrentContext() and it depends on what it happened to have rendered last? I made the obvious patch, and not seen this since. #6 0x7fffee16c298 in __run_exit_handlers () at /usr/lib/libc.so.6 #7 0x7fffee16c2ea in () at /usr/lib/libc.so.6 #8 0x7fffee220695 in () at /usr/lib/libc.so.6 #9 0x7fffee2207d4 in () at /usr/lib/libc.so.6 #10 0x7fffeee175fc in () at /usr/lib/libepoxy.so.0 #11 0x7fffeedfa69d in () at /usr/lib/libepoxy.so.0 #12 0x70b22636 in KWin::GLShader::~GLShader() (this=0x1e786f0, __in_chrg=) at /home/david/projects/kde5/src/kde/workspace/kwin/libkwineffects/kwinglutils.cpp:172 #13 0x7796b5f7 in QScopedPointerDeleter::cleanup(KWin::GLShader*) (pointer=0x1e786f0) at /opt/qt5/include/QtCore/qscopedpointer.h:60 #14 0x7796b2cd in QScopedPointer >::~QScopedPointer() (this=0x1ee47a8, __in_chrg=) at /opt/qt5/include/QtCore/qscopedpointer.h:107 #15 0x77968a91 in KWin::LanczosFilter::~LanczosFilter() (this=0x1ee4780, __in_chrg=) at /home/david/projects/kde5/src/kde/workspace/kwin/lanczosfilter.cpp:55 #16 0x77968ace in KWin::LanczosFilter::~LanczosFilter() (this=0x1ee4780, __in_chrg=) at /home/david/projects/kde5/src/kde/workspace/kwin/lanczosfilter.cpp:59 #17 0x77950c6e in KWin::SceneOpenGL2::resetLanczosFilter() (this=0xaabf40) at /home/david/projects/kde5/src/kde/workspace/kwin/scene_opengl.cpp:1194 #18 0x77a6f77f in KWin::SceneOpenGL2::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0xaabf40, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffcbf8) at kwin_autogen/EWIEGA46WW/moc_scene_opengl.cpp:178 #19 0x7fffef531a22 in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x7ca700, signalOffset=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at /home/david/projects/qt5/qtbase/src/corelib/kernel/qobject.cpp:3766 #20 0x7fffef531d0b in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=0x7ca700, m= to continue, or q to quit--- >, local_signal_index=1, argv=0x0) at >/home/david/projects/qt5/qtbase/src/corelib/kernel/qobject.cpp:3628 > > #21 0x77a70bbb in KWin::Screens::changed() (this=0x7ca700) at kwin_autogen/EWIEGA46WW/moc_screens.cpp:262 #22 0x7fffde44e19a in KWin::DrmBackend::configurationChangeRequested(KWayland::Server::OutputConfigurationInterface*) (this=0x6a9910, config=0x1edd2f0) at /home/david/projects/kde5/src/kde/workspace/kwin/plugins/platforms/drm/drm_backend.cpp:537 #23 0x77a046fa in KWin::WaylandServeroperator()(KWayland::Server::OutputConfigurationInterface *) const (__closure=0x6a9560, config=0x1edd2f0) at /home/david/projects/kde5/src/kde/workspace/kwin/wayland_server.cpp:298 #24 0x77a0971f in QtPrivate::FunctorCall, QtPrivate::List, void, KWin::WaylandServer::init(const QByteArray&, KWin::WaylandServer::InitalizationFlags):: >::call(KWin::WaylandServer:: &, void **) (f=..., arg=0x7fffcee0) at /opt/qt5/include/QtCore/qobjectdefs_impl.h:130 #25 0x77a092fe in QtPrivate::Functor, 1>::call, void>(KWin::WaylandServer:: &, void *, void **) (f=..., arg=0x7fffcee0) at /opt/qt5/include/QtCore/qobjectdefs_impl.h:240 #26 0x77a0829a in QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1, this_=0x6a9550, r=0x69f0f0, a=0x7fffcee0, ret=0x0) at /opt/qt5/include/QtCore/qobject_impl.h:168 #27 0x7fffef531879 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=, r=0x69f0f0, this=0x6a9550) at ../../include/QtCore/../../../../qt5/qtbase/src/corelib/kernel/qobject_impl.h:101 #28 0x7fffef531879 in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x6a93f0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffcee0) at /home/david/projects/qt5/qtb
[digikam] [Bug 377746] crash at startup
https://bugs.kde.org/show_bug.cgi?id=377746 --- Comment #5 from caulier.gil...@gmail.com --- Philippe, Can you reproduce the crash with official AppImage bundle released with 5.7.0 ? Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384873] Alt/F10 opens appmenu in titlebar
https://bugs.kde.org/show_bug.cgi?id=384873 Martin Flöser changed: What|Removed |Added Severity|normal |wishlist CC||k...@privat.broulik.de Component|general |appmenu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384882] Rendering broken after fbconfig visual matching change in XServer
https://bugs.kde.org/show_bug.cgi?id=384882 --- Comment #2 from Martin Flöser --- could you please try to use the OpenGL/ES compositor? Run: KWIN_COMPOSE=O2ES kwin_x11 --replace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384878] Crash due touchdocker when opening a new document.
https://bugs.kde.org/show_bug.cgi?id=384878 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||b...@valdyas.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384884] Crash on screen resize
https://bugs.kde.org/show_bug.cgi?id=384884 Martin Flöser changed: What|Removed |Added Component|general |compositing Flags||Wayland+ --- Comment #1 from Martin Flöser --- Why are you not seeing it always: the LanczosFilter is lazy loaded, so you need to trigger it. This happens for example in Present Windows. Yes, I consider it possible that we leak the doneCurrentContext in the case that a screen gets deleted. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384884] Crash on screen resize
https://bugs.kde.org/show_bug.cgi?id=384884 Martin Flöser changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 384880] Dirwatcher inefficiency when using QFileSystemWatcher
https://bugs.kde.org/show_bug.cgi?id=384880 --- Comment #5 from Milian Wolff --- a) if my memory serves me right (I've written this a long time ago), I think the WatchFiles there may have been required to get notified about file deletion events. Anyhow, I agree that this needs to be improved somehow. Maybe this isn't needed anymore, maybe it was never required in the first place. Writing better tests for this would be the first way to fix this. b) You said: "I'm going to go with the null hypothesis that the QFSW API isn't new and has had ample opportunity for fine-tuning by Qt experts. We're just using it in a very intensive way here." >From my long time experience working with Qt, this shouldn't be your null hypothesis. I've found and fixed quite a few glaring performance issues in Qt over the years, and most simply arose when you pushed a bit more load at the public API in ways that apparently noone did so far. Maybe we do that here due to the misconfiguration in a). Nevertheless ruling out performance optimizations upstream is a very bad idea at this stage. Just looking at the profile reports, QStringList pops up - a very bad idea if that's getting queries in O(N) all the time. Using a QSet or sorted vector could already dramatically improve the runtime performance. -- You are receiving this mail because: You are watching all bug changes.
