[krita] [Bug 411510] No Label Selection doesn't filter out colored layers label
https://bugs.kde.org/show_bug.cgi?id=411510 Boudewijn Rempt changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412178] New: crash after reconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=412178 Bug ID: 412178 Summary: crash after reconnecting external monitor Product: kwin Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: t...@tim-richardson.net Target Milestone: --- Application: kwin_x11 (5.16.5) Qt Version: 5.12.3 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: - Unusual behavior I noticed: Laptop resumed from suspend, but one of the external monitors did not wake up. I disconnected it from the thunderbolt port and reconnected it; Kwin crashed (hence this report) but the external monitor did work. The crash does not seem to be reproducible. -- 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 0x7f1de9266d00 (LWP 3019))] Thread 6 (Thread 0x7f1db0b9c700 (LWP 3377)): #0 0x7f1de1b499f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f1de5103fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1de1b499f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f1de5103f68, cond=0x7f1de5103f90) at pthread_cond_wait.c:502 #2 0x7f1de1b499f3 in __pthread_cond_wait (cond=0x7f1de5103f90, mutex=0x7f1de5103f68) at pthread_cond_wait.c:655 #3 0x7f1de4e0d844 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f1de4e0d889 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f1de1b436db in start_thread (arg=0x7f1db0b9c700) at pthread_create.c:463 #6 0x7f1de8bdf88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f1db1b9e700 (LWP 3343)): #0 0x7f1de1b499f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55df5ae3d328) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1de1b499f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55df5ae3d2d8, cond=0x55df5ae3d300) at pthread_cond_wait.c:502 #2 0x7f1de1b499f3 in __pthread_cond_wait (cond=0x55df5ae3d300, mutex=0x55df5ae3d2d8) at pthread_cond_wait.c:655 #3 0x7f1db269b91b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f1db269b527 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f1de1b436db in start_thread (arg=0x7f1db1b9e700) at pthread_create.c:463 #6 0x7f1de8bdf88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f1dc6579700 (LWP 3330)): #0 0x7f1de8bd2cf6 in __GI_ppoll (fds=fds@entry=0x7f1db4000d28, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f1de6126ab1 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 0x7f1de6126ab1 in qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f1db4000d28) at kernel/qcore_unix.cpp:132 #3 0x7f1de6126ab1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x7f1db4000d28, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #4 0x7f1de61281be in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f1de60cc03a in QEventLoop::exec(QFlags) (this=this@entry=0x7f1dc6578d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f1de5ef34ca in QThread::exec() (this=) at thread/qthread.cpp:531 #7 0x7f1de053a115 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f1de5ef4c72 in QThreadPrivate::start(void*) (arg=0x55df5ae1c190) at thread/qthread_unix.cpp:361 #9 0x7f1de1b436db in start_thread (arg=0x7f1dc6579700) at pthread_create.c:463 #10 0x7f1de8bdf88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f1dcdb12700 (LWP 3100)): #0 0x7f1de8bd2cf6 in __GI_ppoll (fds=fds@entry=0x7f1dc0010e88, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f1de6126ab1 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 0x7f1de6126ab1 in qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f1dc0010e88) at kernel/qcore_unix.cpp:132 #3 0x7f1de6126ab1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x7f1dc0010e88, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #4 0x7f1de61281be in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f1de60cc03a in QEventLoop::exec(QFlags) (this=this@entry=0x7f1dcdb11cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7
[krita] [Bug 411510] No Label Selection doesn't filter out colored layers label
https://bugs.kde.org/show_bug.cgi?id=411510 --- Comment #3 from reptilli...@live.com --- I tested that it does work properly in latest build. Please close this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407050] G'Mic filters don't work if they need multiple layers
https://bugs.kde.org/show_bug.cgi?id=407050 reptilli...@live.com changed: What|Removed |Added CC||reptilli...@live.com --- Comment #1 from reptilli...@live.com --- In my experience, they do work, otherwise I wouldn't code in G'MIC at all. Stylize filter for some reason can't work at all in Krita. That's a bug reported by the maintainer of Krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407050] G'Mic filters don't work if they need multiple layers
https://bugs.kde.org/show_bug.cgi?id=407050 --- Comment #2 from reptilli...@live.com --- More commentary, I use nightly and Windows 10 myself. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412176] Unable to arrange devices in sidebar
https://bugs.kde.org/show_bug.cgi?id=412176 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Nate Graham --- Works for me with Dolphin 19.08. Looks like it got fixed since 18.12, which is the version you're using. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409821] Color Selector disappears / invalid color if attempting to type in colors in 32bit float depth mode
https://bugs.kde.org/show_bug.cgi?id=409821 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 --- Comment #8 from Kishore Gopalakrishnan --- I ca nreproduce this bug if I use the Arch package (5.16.90), or if I build from the tar at `https://download.kde.org/unstable/plasma/`. However, I can't reproduce it if I build from the git repo (checked with 5.17 branch, 5.16 branch, 5.16.90 tag). Perhaps there is some issue with the tars? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412177] New: Plasmashell crash when KDE connect causes a large number of notifications
https://bugs.kde.org/show_bug.cgi?id=412177 Bug ID: 412177 Summary: Plasmashell crash when KDE connect causes a large number of notifications Product: plasmashell Version: 5.16.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: benk...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.90) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-arch1-1-ARCH x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: I was browsing the web, and KDE Connect connected to my phone and opened up notifications for all the notifications on my phone. There were a large number. Immediately after this, plasmashell crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f59c2e05c80 (LWP 51416))] Thread 17 (Thread 0x7f5991cd6700 (LWP 51455)): [KCrash Handler] #6 0x7f59c7506e94 in wl_proxy_marshal_constructor () at /usr/lib/libwayland-client.so.0 #7 0x7f59c299e4d0 in QtWaylandClient::QWaylandWindow::handleUpdate() () at /usr/lib/libQt5WaylandClient.so.5 #8 0x7f59c01e0b31 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #9 0x7f59c7fdea72 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #10 0x7f59c96c10ee in () at /usr/lib/libQt5Quick.so.5 #11 0x7f59c96c4fc8 in () at /usr/lib/libQt5Quick.so.5 #12 0x7f59c7a375b0 in () at /usr/lib/libQt5Core.so.5 #13 0x7f59c6f2f57f in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f59c76c40e3 in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f59723c1700 (LWP 51453)): #0 0x7f59c6f35415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f59c7a3d660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f59c7a3d752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f59c96c4dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f59c96c505e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f59c7a375b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f59c6f2f57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f59c76c40e3 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f5972ef6700 (LWP 51452)): #0 0x7f59c6f35415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f59c7a3d660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f59c7a3d752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f59c96c4dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f59c96c505e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f59c7a375b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f59c6f2f57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f59c76c40e3 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f59737c6700 (LWP 51451)): #0 0x7f59c6f35415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f59c7a3d660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f59c7a3d752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f59c96c4dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f59c96c505e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f59c7a375b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f59c6f2f57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f59c76c40e3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f5973fff700 (LWP 51450)): #0 0x7f59c6f35415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f59c7a3d660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f59c7a3d752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f59c96c4dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f59c96c505e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f59c7a375b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f59c6f2f57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f59c76c40e3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f5990923700 (LWP 51449)): #0 0x7f59c6f35415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f59c7a3d660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f59c7a3d752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f59c96c4dad
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412176] Unable to arrange devices in sidebar
https://bugs.kde.org/show_bug.cgi?id=412176 --- Comment #1 from Rajinder Yadav --- Created attachment 122795 --> https://bugs.kde.org/attachment.cgi?id=122795&action=edit devices oin sidebar -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412176] New: Unable to arrange devices in sidebar
https://bugs.kde.org/show_bug.cgi?id=412176 Bug ID: 412176 Summary: Unable to arrange devices in sidebar Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: devguy...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Not able to move the devices to rearrange their order STEPS TO REPRODUCE 1. Click and drag device up or down. 2. Unclick after moving device. OBSERVED RESULT Device is not rearranged. EXPECTED RESULT should be able to drag and move device. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412175] New: brush sizes on krita are changing without me changing them
https://bugs.kde.org/show_bug.cgi?id=412175 Bug ID: 412175 Summary: brush sizes on krita are changing without me changing them Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: ldoug...@gmail.com Target Milestone: --- SUMMARY I don't know why but as Im drawing on krita, all of my brushes will change sizes, like my brush will be on it's default size but as i start drawing at first the brush won't even draw until i pick up my bamboo pen and put it back on the tablet. Once i start drawing again, my brush will suddenly change to a very small size and then in one stroke, it'll grow very big. is this some sort of bug STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412174] Plasma crash upon initial loading (after log-in) on Wayland
https://bugs.kde.org/show_bug.cgi?id=412174 --- Comment #2 from Chris --- Created attachment 122794 --> https://bugs.kde.org/attachment.cgi?id=122794&action=edit photo of current desktop state. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412174] Plasma crash upon initial loading (after log-in) on Wayland
https://bugs.kde.org/show_bug.cgi?id=412174 --- Comment #1 from Chris --- I would like to go ahead and note (since this is the report that I had just made), that Plasma has just crashed and hasn't loaded back in yet. I clicked the option to open this page after hitting "finish" in the bug reporter, and it crashed after firefox started loading. I am still in firefox though, but the entire system is just BLACK, besides this -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412174] New: Plasma crash upon initial loading (after log-in) on Wayland
https://bugs.kde.org/show_bug.cgi?id=412174 Bug ID: 412174 Summary: Plasma crash upon initial loading (after log-in) on Wayland Product: plasmashell Version: 5.16.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: christopherbwilliams1...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.12.3 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Had just logged in, after switching to "Plasma on Wayland". Using the open-source video drivers. Does not do this when on X -- 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 0x7f80f3c2f880 (LWP 1393))] Thread 9 (Thread 0x7f808700 (LWP 1532)): [KCrash Handler] #6 0x7f80cac670b3 in () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 #7 0x7f80cac677dd in () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 #8 0x7f80cf256196 in () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #9 0x7f80cf3fbe6b in () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #10 0x7f80cef7982a in () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #11 0x7f80d5b4b24b in () at /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 #12 0x7f80d5b38829 in eglSwapBuffers () at /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 #13 0x7f80d6187b7c in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #14 0x7f80edf2cdbf in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7f80f1a9aed9 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f80f1a9eae8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x7f80ed74bc72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f80ea2616db in start_thread (arg=0x7f808700) at pthread_create.c:463 #19 0x7f80ed04b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f809da53700 (LWP 1472)): #0 0x7f80ed981b52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f80e6ea5fe1 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f80e6ea6570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f80e6ea66dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f80ed981dcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f80ed92303a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f80ed74a4ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f80ed74bc72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f80ea2616db in start_thread (arg=0x7f809da53700) at pthread_create.c:463 #9 0x7f80ed04b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f809e663700 (LWP 1471)): #0 0x7fffbf9f666f in () #1 0x7f80ed05aea6 in __GI___clock_gettime (clock_id=1, tp=0x7f809e662ac0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f80ed9816b1 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f80ed97fee9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f80ed982535 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f80e6ea5fe1 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f80e6ea6570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f80e6ea66dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f80ed981dcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f80ed92303a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f80ed74a4ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f809ed2e197 in KCupsConnection::run() () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #12 0x7f80ed74bc72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f80ea2616db in start_thread (arg=0x7f809e663700) at pthread_create.c:463 #14 0x7f80ed04b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f80b1a7f700 (LWP 1468)): #0 0x7f80ea26b10d in __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7f80ea264023 in __GI___pthread_mutex_lock (mutex=0x55bcb25138e8) at ../nptl/pthread_mutex_l
[skrooge] [Bug 412164] I have been trying to upgrade from 2.15.0 with no success,
https://bugs.kde.org/show_bug.cgi?id=412164 --- Comment #3 from Dave --- (In reply to Dave from comment #2) > Created attachment 122789 [details] > attachment-16847-0.html > > I believe l do. > On Saturday, September 21, 2019, 02:39:53 p.m. EDT, Stephane MANKOWSKI > wrote: > > https://bugs.kde.org/show_bug.cgi?id=412164 > > --- Comment #1 from Stephane MANKOWSKI --- > Do you have free space on your device? yes though l don't know how much : about 8 gb -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412173] New: crash after system upgrade opening new tab in blank Konsole window
https://bugs.kde.org/show_bug.cgi?id=412173 Bug ID: 412173 Summary: crash after system upgrade opening new tab in blank Konsole window Product: konsole Version: 19.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: skierp...@gmail.com Target Milestone: --- Application: konsole (19.08.0) Qt Version: 5.12.4 Frameworks Version: 5.61.0 Operating System: Linux 5.3.0-1.fc31.x86_64 x86_64 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: When I ran `sudo dnf system-upgrade reboot` to upgrade to Fedora 31 beta, I had a Konsole window with three white on black tabs open. When the upgrade completed and KDE restarted (nice and smooth, well done!), Konsole reappeared but with a blank white window containing no tabs. I was able to create a new Konsole window but when I created a new tab in the blank window (I think with File > New Tab), crash! - Unusual behavior I noticed: As above, I've never seen a Konsole window with no shell or tab in it. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f562b96a840 (LWP 239947))] Thread 4 (Thread 0x7f561690c700 (LWP 239978)): #0 0x7f562e8f1d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5616df705b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7f5616df6c6b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7f562e8eb4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f56312e6643 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f561cef2700 (LWP 239958)): #0 0x7f562e06c9e8 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7f562e0201f1 in g_main_context_check () from /lib64/libglib-2.0.so.0 #2 0x7f562e020742 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f562e0208d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f562fb79bd3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f562fb239db in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f562f97c625 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f562f06bf4a in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #8 0x7f562f97d776 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f562e8eb4e2 in start_thread () from /lib64/libpthread.so.0 #10 0x7f56312e6643 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f561e679700 (LWP 239956)): #0 0x7f56312dba1f in poll () from /lib64/libc.so.6 #1 0x7f562e91638a in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f562e917fea in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f561e843be8 in QXcbEventQueue::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f562f97d776 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f562e8eb4e2 in start_thread () from /lib64/libpthread.so.0 #6 0x7f56312e6643 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f562b96a840 (LWP 239947)): [KCrash Handler] #6 0x7f5631188814 in Konsole::ViewSplitter::getToplevelSplitter() () from /lib64/libkonsoleprivate.so.19 #7 0x7f563117f0eb in Konsole::ViewManager::switchToTerminalDisplay(Konsole::TerminalDisplay*) () from /lib64/libkonsoleprivate.so.19 #8 0x7f56311841aa in Konsole::ViewManager::focusAnotherTerminal(Konsole::ViewSplitter*) () from /lib64/libkonsoleprivate.so.19 #9 0x7f563118439b in Konsole::ViewManager::sessionFinished() () from /lib64/libkonsoleprivate.so.19 #10 0x7f562fb4eea0 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #11 0x7f56311491e7 in Konsole::Session::done(int, QProcess::ExitStatus) () from /lib64/libkonsoleprivate.so.19 #12 0x7f562fb4eea0 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #13 0x7f562faaf7e3 in QProcess::finished(int, QProcess::ExitStatus) () from /lib64/libQt5Core.so.5 #14 0x7f562fab5a53 in QProcessPrivate::_q_processDied() () from /lib64/libQt5Core.so.5 #15 0x7f562fab5c32 in QProcess::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5Core.so.5 #16 0x7f562fb4ed5b in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #17 0x7f562fb5afac in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5 #18 0x7f562fb5b311 in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f5630486af6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib6
[drkonqi] [Bug 412172] New: garbled display of multiple toolbars in DrKonqi
https://bugs.kde.org/show_bug.cgi?id=412172 Bug ID: 412172 Summary: garbled display of multiple toolbars in DrKonqi Product: drkonqi Version: 5.16.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: skierp...@gmail.com Target Milestone: --- Created attachment 122793 --> https://bugs.kde.org/attachment.cgi?id=122793&action=edit garbled DrKonqi display SUMMARY Most recently I started reporting a bug, then went into standby while on the log in to bugs.kde.org step. When I resumed, I entered my username and password for bugs.kde.org, and the next screen displayed multiple toolbars. This has happened before back in April on other steps, I think when I pressing the back button; I took screenshots at the time but I can't find any bug report. STEPS TO REPRODUCE As above. I haven't tried reproducing b OBSERVED RESULT See screenshot. EXPECTED RESULT Correct display. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.4 using XCB ADDITIONAL INFORMATION You can't resize the DrKonqi window with the mouse, but if you Maximize the window the display is fine and remains OK if you Restore to the original size. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412080] add 2px border to CSD gtk windows when shadows are not supported from window manager
https://bugs.kde.org/show_bug.cgi?id=412080
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Version Fixed In||5.17.0
Latest Commit||https://commits.kde.org/bre
||eze-gtk/5ded281f8e5f99dd65b
||94e5ad759cbfc3da5cb00
Resolution|--- |FIXED
--- Comment #6 from Nate Graham ---
Git commit 5ded281f8e5f99dd65b94e5ad759cbfc3da5cb00 by Nate Graham, on behalf
of Carson Black.
Committed on 21/09/2019 at 22:02.
Pushed by ngraham into branch 'Plasma/5.17'.
[GTK3] CSD windows show handles on .solid-csd
Summary:
CSD windows will now show 5px handles on windows with .solid-csd (CSD windows
in window managers that do not support GTK frame extents)
FIXED-IN: 5.17.0
Test Plan:
Handle before (KWin):
{F7396999}
Handle after (KWin):
{F7397796}
Reviewers: #breeze, ngraham, ndavis
Reviewed By: #breeze, ngraham, ndavis
Subscribers: ngraham, ndavis, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D24126
M +8-2src/gtk3/widgets/_window_decorations.scss
https://commits.kde.org/breeze-gtk/5ded281f8e5f99dd65b94e5ad759cbfc3da5cb00
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 412163] Checking for freespace BEFORE copy instead of during or once MERGE has been clicked.
https://bugs.kde.org/show_bug.cgi?id=412163 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 141564 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 141564] Check that destination is writable before preparing move/copy job
https://bugs.kde.org/show_bug.cgi?id=141564 Nate Graham changed: What|Removed |Added Version Fixed In||5.63 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 141564] Check that destination is writable before preparing move/copy job
https://bugs.kde.org/show_bug.cgi?id=141564 Nate Graham changed: What|Removed |Added CC||dieseltr...@gmail.com --- Comment #6 from Nate Graham --- *** Bug 412163 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 412171] New: color of hovering effect changes after I leave full screen mode
https://bugs.kde.org/show_bug.cgi?id=412171 Bug ID: 412171 Summary: color of hovering effect changes after I leave full screen mode Product: gwenview Version: 19.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 122792 --> https://bugs.kde.org/attachment.cgi?id=122792&action=edit screen recording SUMMARY Watch the attached screen recording please. The menu bar and its entries and the entries of the context menu have different color on mouseover after I leave full screen mode. STEPS TO REPRODUCE 1. open any file with gwenview 2. enter and leave full screen mode 3. hover over the menu bar and its entries, open the context menu and hover over its entries EXPECTED RESULT color of hovering effect never changes after full screen mode SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 299248] External tools plugin is missing
https://bugs.kde.org/show_bug.cgi?id=299248 --- Comment #6 from Dominik Haumann --- Blog with details: https://kate-editor.org/post/2019/2019-09-21-external-tools-plugin/ -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 153963] external tools need a capture window for output
https://bugs.kde.org/show_bug.cgi?id=153963 --- Comment #4 from Dominik Haumann --- It's back, see here: https://kate-editor.org/post/2019/2019-09-21-external-tools-plugin/ And it has a capture window for output. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 181528] Menu items in Tools -> External Tools are untranslatable
https://bugs.kde.org/show_bug.cgi?id=181528 --- Comment #7 from Dominik Haumann --- PS: It's back. We have to check translation issues, though. https://kate-editor.org/post/2019/2019-09-21-external-tools-plugin/ -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 117946] Defining external tools overreacts on wrong user input
https://bugs.kde.org/show_bug.cgi?id=117946 --- Comment #5 from Dominik Haumann --- https://kate-editor.org/post/2019/2019-09-21-external-tools-plugin/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399988] Dolphin crash when moving/renaming file (local ext4 to mounted NAS folder fat32)
https://bugs.kde.org/show_bug.cgi?id=399988 theotyf...@gmail.com changed: What|Removed |Added CC||theotyf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399988] Dolphin crash when moving/renaming file (local ext4 to mounted NAS folder fat32)
https://bugs.kde.org/show_bug.cgi?id=399988 --- Comment #2 from theotyf...@gmail.com --- Created attachment 122791 --> https://bugs.kde.org/attachment.cgi?id=122791&action=edit New crash information added by DrKonqi dolphin (17.12.3) using Qt 5.9.5 - What I was doing when the application crashed: renamed the targed file while copying across different filesystens. -- Backtrace (Reduced): #6 0x7ff1e3316af4 in KJob::isAutoDelete() const () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #7 0x7ff1e3316b41 in KJob::finishJob(bool) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #8 0x7ff1e5cfffa9 in KIO::FileCopyJob::slotResult(KJob*) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 [...] #10 0x7ff1e331603c in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #11 0x7ff1e3316b71 in KJob::finishJob(bool) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 412169] baloo_file crashes on each system boot
https://bugs.kde.org/show_bug.cgi?id=412169 Stefan Brüns changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 406295] Status of checkboxes related to firmware sources is not updated immediately after checking/uncheking
https://bugs.kde.org/show_bug.cgi?id=406295 Patrick Silva changed: What|Removed |Added Version|5.16.4 |5.16.90 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405609] System settings crashed when I opened "Application style"
https://bugs.kde.org/show_bug.cgi?id=405609 --- Comment #8 from Patrick Silva --- Sometimes I can reproduce this crash on Plasma 5.17 beta (on Wayland session), but the backtrace looks different. Operating System: Arch Linux KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 Kernel Version: 5.3.0-arch1-1-ARCH open system settings > desktop behavior > desktop effects click on "All settings" on top left corner open "Application style" if system settings did not crash, close it and repeat the steps above. At some point probably it will crash. Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3847625800 (LWP 8230))] Thread 5 (Thread 0x7f38277bf700 (LWP 8257)): #0 0x7f384c2fd686 in __libc_disable_asynccancel () at /usr/lib/libc.so.6 #1 0x7f384c2e567b in poll () at /usr/lib/libc.so.6 #2 0x7f3848690130 in g_main_context_poll (priority=, n_fds=1, fds=0x7f381c00a080, timeout=, context=0x7f381c002540) at ../glib/glib/gmain.c:4216 #3 0x7f3848690130 in g_main_context_iterate (context=context@entry=0x7f381c002540, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3912 #4 0x7f3848690201 in g_main_context_iteration (context=0x7f381c002540, may_block=may_block@entry=1) at ../glib/glib/gmain.c:3978 #5 0x7f384c889a1c in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f381c005070, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f384c8304ec in QEventLoop::exec(QFlags) (this=this@entry=0x7f38277bed80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f384c662385 in QThread::exec() (this=this@entry=0x55613cfb9d10) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f384b96d849 in QQmlThreadPrivate::run() (this=0x55613cfb9d10) at /tmp/makepkg/qt5-declarative-debug/src/qtdeclarative-everywhere-src-5.13.1/src/qml/qml/ftw/qqmlthread.cpp:152 #9 0x7f384c6635b0 in QThreadPrivate::start(void*) (arg=0x55613cfb9d10) at thread/qthread_unix.cpp:360 #10 0x7f384aec457f in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f384c2f00e3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f38369dc700 (LWP 8234)): #0 0x7f384c2e118c in read () at /usr/lib/libc.so.6 #1 0x7f38486409f0 in read (__nbytes=16, __buf=0x7f38369dbb60, __fd=, __fd=, __buf=, __nbytes=) at /usr/include/bits/unistd.h:44 #2 0x7f38486409f0 in g_wakeup_acknowledge (wakeup=0x7f3840003db0) at ../glib/glib/gwakeup.c:210 #3 0x7f384868e9f1 in g_main_context_check (context=context@entry=0x7f383bf0, max_priority=2147483647, fds=fds@entry=0x7f3830004e30, n_fds=n_fds@entry=1) at ../glib/glib/gmain.c:3695 #4 0x7f38486900d8 in g_main_context_iterate (context=context@entry=0x7f383bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3914 #5 0x7f3848690201 in g_main_context_iteration (context=0x7f383bf0, may_block=may_block@entry=1) at ../glib/glib/gmain.c:3978 #6 0x7f384c889a1c in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f383b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f384c8304ec in QEventLoop::exec(QFlags) (this=this@entry=0x7f38369dbd80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #8 0x7f384c662385 in QThread::exec() (this=this@entry=0x55613738a1b0) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #9 0x7f384b96d849 in QQmlThreadPrivate::run() (this=0x55613738a1b0) at /tmp/makepkg/qt5-declarative-debug/src/qtdeclarative-everywhere-src-5.13.1/src/qml/qml/ftw/qqmlthread.cpp:152 #10 0x7f384c6635b0 in QThreadPrivate::start(void*) (arg=0x55613738a1b0) at thread/qthread_unix.cpp:360 #11 0x7f384aec457f in start_thread () at /usr/lib/libpthread.so.0 #12 0x7f384c2f00e3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f3844913700 (LWP 8233)): #0 0x7f384aeca415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f383f57bf5c in () at /usr/lib/dri/i965_dri.so #2 0x7f383f57bb58 in () at /usr/lib/dri/i965_dri.so #3 0x7f384aec457f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f384c2f00e3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f384639e700 (LWP 8232)): #0 0x7f384c2e5667 in poll () at /usr/lib/libc.so.6 #1 0x7f3848690130 in g_main_context_poll (priority=, n_fds=1, fds=0x7f3840005260, timeout=, context=0x7f384bf0) at ../glib/glib/gmain.c:4216 #2 0x7f3848690130 in g_main_context_iterate (context=context@entry=0x7f384bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3912 #3 0x7f3848690201 in g_main_context_iteration (context=0x7f384bf0, may_block=may_block@entry=1) at ../glib/glib/gmain.c:3978 #4 0x7f384c889a1c in QEventDispatcherGlib::processEvents(QFlags) (th
[frameworks-plasma] [Bug 397336] Tooltip timeout is too short and unalterable
https://bugs.kde.org/show_bug.cgi?id=397336 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #5 from Siddhartha Sahu --- This issue remains in plasma git master. I'd prefer tooltips to stay as long as the mouse is over the widgets. I have a bunch to timezones configured in the digital clock widget and face the short timeout issue when the tooltip showing the current time in different timezones closes while I'm still trying to lookup/process it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411917] Filter brush with Color Adjustment freezes Krita
https://bugs.kde.org/show_bug.cgi?id=411917 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Status|CONFIRMED |ASSIGNED Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com --- Comment #8 from Tymond --- I think I know what the issue is, or at least, Dmitry for sure knows, so let's set it assigned to me... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411917] Filter brush with Color Adjustment freezes Krita
https://bugs.kde.org/show_bug.cgi?id=411917 wolthera changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #7 from wolthera --- Ah, fantastic. I still cannot reproduce, but now we have a backtrace, we can try to figure out what is going on at the very least. --- Thread 31 (Thread 0x7fffc0f87700 (LWP 7381)): #0 0x7fffec4426b0 in ?? () from /usr/lib/liblcms2.so.2 #1 0x7fffe51d8fed in LcmsColorSpace::createPerChannelAdjustment (this=0x59abe5a0, transferValues=0x7fffa40e47c0) at /home/snu/Applications/kritadev/krita/plugins/color/lcms2engine/LcmsColorSpace.h:330 #2 0x7fffe5e46a61 in KisPerChannelFilter::createTransformation (this=, cs=0x59abe5a0, config=...) at /home/snu/Applications/kritadev/krita/plugins/filters/colorsfilters/kis_perchannel_filter.cpp:306 #3 0x75b13bb6 in KisColorTransformationConfiguration::colorTransformation (this=this@entry=0x7fffa401bf50, cs=cs@entry=0x59abe5a0, filter=filter@entry=0x5888df30) at /usr/include/c++/9.1.0/bits/atomic_base.h:318 #4 0x75b17528 in KisColorTransformationFilter::processImpl (this=0x5888df30, device=..., applyRect=..., config=..., progressUpdater=0x7fffa408fcf0) at /home/snu/Applications/kritadev/krita/libs/global/kis_shared_ptr.h:179 #5 0x75b115ec in KisFilter::process (this=0x5888df30, src=..., dst=..., selection=..., applyRect=..., config=..., progressUpdater=0x7fffa408fcf0) at /usr/include/c++/9.1.0/bits/atomic_base.h:318 #6 0x75b125a7 in KisFilter::process (this=, device=..., applyRect=..., config=..., progressUpdater=progressUpdater@entry=0x0) at /usr/include/c++/9.1.0/bits/atomic_base.h:318 #7 0x7fffe4843fd5 in KisFilterOp::paintAt (this=0x7fffa4094530, info=...) at /home/snu/Applications/kritadev/krita/libs/global/kis_shared_ptr.h:218 #8 0x75abaf38 in KisPaintInformation::paintAt (distanceInfo=0xe01c6f70, op=..., this=0x7fffc0f86670) at /home/snu/Applications/kritadev/krita/libs/image/kis_timing_information.h:24 #9 KisPaintOpUtils::paintLine (op=..., pi1=..., pi2=..., currentDistance=currentDistance@entry=0xe01c6f70, fanCornersEnabled=false, fanCornersStep=1) at /home/snu/Applications/kritadev/krita/libs/image/brushengine/kis_paintop_utils.h:96 #10 0x75aba7d0 in KisPaintOp::paintLine (currentDistance=0xe01c6f70, pi2=..., pi1=..., this=0x7fffa4094530) at /home/snu/Applications/kritadev/krita/libs/image/brushengine/kis_paintop.cc:156 #11 paintBezierCurve (paintOp=0x7fffa4094530, pi1=..., control1=..., control2=..., pi2=..., currentDistance=0xe01c6f70) at /home/snu/Applications/kritadev/krita/libs/image/brushengine/kis_paintop.cc:125 #12 0x75aba8e4 in paintBezierCurve (paintOp=0x7fffa4094530, pi1=..., control1=..., control2=..., pi2=..., currentDistance=0xe01c6f70) at /home/snu/Applications/kritadev/krita/libs/image/brushengine/kis_paintop.cc:137 #13 0x75aba8e4 in paintBezierCurve (paintOp=0x7fffa4094530, pi1=..., control1=..., control2=..., pi2=..., currentDistance=0xe01c6f70) at /home/snu/Applications/kritadev/krita/libs/image/brushengine/kis_paintop.cc:137 #14 0x75aba8e4 in paintBezierCurve (paintOp=0x7fffa4094530, pi1=..., control1=..., control2=..., pi2=..., currentDistance=0xe01c6f70) at /home/snu/Applications/kritadev/krita/libs/image/brushengine/kis_paintop.cc:137 #15 0x75aba8e4 in paintBezierCurve (paintOp=0x7fffa4094530, pi1=..., control1=..., control2=..., pi2=..., currentDistance=0xe01c6f70) at /home/snu/Applications/kritadev/krita/libs/image/brushengine/kis_paintop.cc:137 #16 0x75aba964 in KisPaintOp::paintBezierCurve (this=, pi1=..., control1=..., control2=..., pi2=..., currentDistance=) at /usr/include/eigen3/Eigen/src/Core/PlainObjectBase.h:901 #17 0x76ef9ce7 in KisMaskedFreehandStrokePainteroperator() (data=, data=, __closure=) at /home/snu/Applications/kritadev/krita/libs/ui/tool/strokes/KisMaskedFreehandStrokePainter.cpp:67 #18 KisMaskedFreehandStrokePainter::applyToAllPainters > (this=0x7fffa40df940, this@entry=0xe0f13d08, this=0x7fffa40df940, this@entry=0xe0f13d08, func=...) at /home/snu/Applications/kritadev/krita/libs/ui/tool/strokes/KisMaskedFreehandStrokePainter.cpp:43 #19 KisMaskedFreehandStrokePainter::paintBezierCurve (this=this@entry=0x7fffa40df940, pi1=..., control1=..., control2=..., pi2=...) at /home/snu/Applications/kritadev/krita/libs/ui/tool/strokes/KisMaskedFreehandStrokePainter.cpp:66 #20 0x76eed578 in FreehandStrokeStrategy::doStrokeCallback (this=0xe0f36920, data=) at /home/snu/Applications/kritadev/krita/libs/ui/tool/strokes/freehand_stroke.cpp:181 #21 0x75a61152 in KisStrok
[Breeze] [Bug 412170] New: Chromium incognito should (optionally) provide breeze-dark window borders, to match the GTK theme
https://bugs.kde.org/show_bug.cgi?id=412170 Bug ID: 412170 Summary: Chromium incognito should (optionally) provide breeze-dark window borders, to match the GTK theme Product: Breeze Version: 5.16.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: abrouw...@gmail.com Target Milestone: --- SUMMARY I use breeze-light color scheme, generally (with a few overrides, such as konsole). I was excited to read the following from the changelog for 5.17: "Our Breeze GTK theme now provides a better appearance for the Chromium/Chrome web browsers and applies your color scheme to GTK and GNOME apps." However, a feature I still find missing is launching chromium as an incognito instance. When selecting "use GTK theme" from chromiums settings, I get a darker theme, as expected. However, my window titlebars are still breeze-light, which looks poor. On gnome, for example, the title bar darkens to match the theme. Unfortunately, it doesn't seem possible to create a rule for an incognito instance, since it just shows "chromium." STEPS TO REPRODUCE 1. Set breeze-light, install breeze-gtk, set chromium to use "GTK" theme instead of classic 2. Open incognito instance of chromium OBSERVED RESULT Breeze-light window border does not match GTK theme. EXPECTED RESULT Breeze-dark would instead be used to match darker GTK theme SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412157] Plasma crashed when opening Clipboard manager
https://bugs.kde.org/show_bug.cgi?id=412157 --- Comment #2 from Uumas --- (In reply to David Edmundson from comment #1) > So Plasma was running for a while when it crashed? Yes. I also have 200 entries in clipboard history out of which ~20 are pictures of various size in case that's related somehow. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 412169] New: baloo_file crashes on each system boot
https://bugs.kde.org/show_bug.cgi?id=412169 Bug ID: 412169 Summary: baloo_file crashes on each system boot Product: frameworks-baloo Version: 5.55.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: dlh...@att.net Target Milestone: --- Application: baloo_file (5.55.0) Qt Version: 5.9.7 Frameworks Version: 5.55.0 Operating System: Linux 4.12.14-lp151.28.13-default x86_64 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: It happens everytime I boot this system. I have done nothing special that I am aware of, have not modified baloo in any way. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f85c9841900 (LWP 2080))] Thread 3 (Thread 0x7f85be123700 (LWP 2203)): [KCrash Handler] #6 0x7f85c719e160 in raise () from /lib64/libc.so.6 #7 0x7f85c719f741 in abort () from /lib64/libc.so.6 #8 0x7f85c4c36a82 in mdb_assert_fail (env=0x55b0298665c0, expr_txt=expr_txt@entry=0x7f85c4c386ab "pglast <= env->me_pglast", func=func@entry=0x7f85c4c38e40 <__func__.7176> "mdb_freelist_save", line=line@entry=3104, file=0x7f85c4c384f0 "mdb.c") at mdb.c:1487 #9 0x7f85c4c345de in mdb_freelist_save (txn=0x55b029867a20) at mdb.c:3104 #10 mdb_txn_commit (txn=0x55b029867a20) at mdb.c:3592 #11 0x7f85c8842c21 in Baloo::Transaction::commit (this=this@entry=0x7f85be122b20) at /usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/transaction.cpp:273 #12 0x55b028b56fc7 in Baloo::UnindexedFileIndexer::run (this=0x55b02989c540) at /usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/file/unindexedfileindexer.cpp:76 #13 0x7f85c7c98e22 in QThreadPoolThread::run (this=0x55b0298efde0) at thread/qthreadpool.cpp:99 #14 0x7f85c7c9bced in QThreadPrivate::start (arg=0x55b0298efde0) at thread/qthread_unix.cpp:368 #15 0x7f85c5095569 in start_thread () from /lib64/libpthread.so.0 #16 0x7f85c72609ef in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f85bec36700 (LWP 2085)): #0 0x7f85c725619b in poll () from /lib64/libc.so.6 #1 0x7f85c36111a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f85c36112bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f85c7ed396b in QEventDispatcherGlib::processEvents (this=0x7f85b8000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f85c7e7890a in QEventLoop::exec (this=this@entry=0x7f85bec35c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f85c7c96daa in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f85c8a699e5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f85c7c9bced in QThreadPrivate::start (arg=0x7f85c8cdcd60) at thread/qthread_unix.cpp:368 #8 0x7f85c5095569 in start_thread () from /lib64/libpthread.so.0 #9 0x7f85c72609ef in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f85c9841900 (LWP 2080)): #0 0x7f85c725619b in poll () from /lib64/libc.so.6 #1 0x7f85c36111a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f85c36112bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f85c7ed396b in QEventDispatcherGlib::processEvents (this=0x55b029851680, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f85c7e7890a in QEventLoop::exec (this=this@entry=0x7ffca8e0ab20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f85c7e819b4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1297 #6 0x55b028b4c13c in main (argc=, argv=) at /usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/file/main.cpp:104 [Inferior 1 (process 2080) detached] Possible duplicates by query: bug 390824. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411917] Filter brush with Color Adjustment freezes Krita
https://bugs.kde.org/show_bug.cgi?id=411917 --- Comment #6 from M --- Created attachment 122790 --> https://bugs.kde.org/attachment.cgi?id=122790&action=edit Backtrace from debug build My mistake, that was a backtrace from the distro package. Here's the output from the actual build with CMAKE_BUILD_TYPE Debug and KRITA_DEVS on. Had to figure out why logging didn't work before. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409821] Color Selector disappears / invalid color if attempting to type in colors in 32bit float depth mode
https://bugs.kde.org/show_bug.cgi?id=409821 --- Comment #6 from kram.f...@gmail.com --- Oh I should add: The buggy color behaves exactly as if it were completely transparent. It even shows up that way in the gradient preview -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412168] New: Wishlist: Feedback after scanning for faces
https://bugs.kde.org/show_bug.cgi?id=412168 Bug ID: 412168 Summary: Wishlist: Feedback after scanning for faces Product: digikam Version: 7.0.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- When scanning for new faces (or recognizing faces), at the moment the process ends, you only get a notification that the process has finished. I thought it would be more informative if it told the number of faces detected/recognized. Something like: "43 new faces have been found". Or "25 faces have been recognized" in the case of face recognition. It's just an idea that could be implemented, now that we are working on the face-workflow. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412168] Wishlist: Feedback after scanning for faces
https://bugs.kde.org/show_bug.cgi?id=412168 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409821] Color Selector disappears / invalid color if attempting to type in colors in 32bit float depth mode
https://bugs.kde.org/show_bug.cgi?id=409821 --- Comment #5 from kram.f...@gmail.com --- I have now updated to Krita version 4.3.0-prealpha (git 5f783c4) The precise behavior appears to have changed now, but still persists. Let me go through my first report point for point: > n the color selector you get when clicking one of the two swatches for your > current colors, if you are in 32bit float depth mode and type a number into > any of the fields, the color picker will disappear By "color picker" I meant the visual shape selector. It no longer disappears. > the corresponding swatch will go transparent. This still happens. (See attached file "Buggy Swatch [...]") > This persists if you click in the area the color picker would appear in That is no longer the case: Now that the visual shape selector no longer disappears, clicking anywhere inside it will fix this problem. Now for the new stuff: The visual color selector displays the color you manually type into the fields incorrectly. How exactly is unclear and inconsistent. See the attachment "visual shape selector doesn't update correctly" as an example. Note, the preview color on the bottom appears to actually be fully transparent. (Same as what happens in the swatch which updates to the same "color") - just for extra clarity, I also attached a third file for how the same typed-in color is actually supposed to look like (achieved by typing in the same values in other locations such as the Specific Color Selector) This happens whenever I type anything into the fields in 32bit float depth. On my first test in this new version, I briefly also found a secondary way to trigger the same issue but I can't reproduce that for now: If you use the color picker from inside the Select a Color window (rather than the one from the tool bar), sometimes the same issue seems to arise. I'm not sure when exactly though. I hope that helps. Do you need any more information? -- You are receiving this mail because: You are watching all bug changes.
[AudioCD-KIO] [Bug 399079] Plasma shows unnecessary notification when I open an audio cd with Dolphin via device notifier
https://bugs.kde.org/show_bug.cgi?id=399079 --- Comment #6 from Yuri Chornoivan --- Sorry, but to my knowledge, nothing can be done on the KIO-AudioCD side. The string "Examining" is sent by the generic KIO core after the stat() job. Plasma notification widget (Dolphin notifications are the separate thing) shows file operations by default (can be configured). And it adds this " (Finished)" part. Do not know what to do to make it work as expected without breaking some third-party parts. :( -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 412164] I have been trying to upgrade from 2.15.0 with no success,
https://bugs.kde.org/show_bug.cgi?id=412164 --- Comment #2 from Dave --- I believe l do. On Saturday, September 21, 2019, 02:39:53 p.m. EDT, Stephane MANKOWSKI wrote: https://bugs.kde.org/show_bug.cgi?id=412164 --- Comment #1 from Stephane MANKOWSKI --- Do you have free space on your device? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409821] Color Selector disappears / invalid color if attempting to type in colors in 32bit float depth mode
https://bugs.kde.org/show_bug.cgi?id=409821 --- Comment #4 from kram.f...@gmail.com --- Created attachment 122788 --> https://bugs.kde.org/attachment.cgi?id=122788&action=edit What visual shape selector should look like for example color -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 412164] I have been trying to upgrade from 2.15.0 with no success,
https://bugs.kde.org/show_bug.cgi?id=412164 --- Comment #1 from Stephane MANKOWSKI --- Do you have free space on your device? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409821] Color Selector disappears / invalid color if attempting to type in colors in 32bit float depth mode
https://bugs.kde.org/show_bug.cgi?id=409821 --- Comment #3 from kram.f...@gmail.com --- Created attachment 122787 --> https://bugs.kde.org/attachment.cgi?id=122787&action=edit visual shape selector doesn't update correctly -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409821] Color Selector disappears / invalid color if attempting to type in colors in 32bit float depth mode
https://bugs.kde.org/show_bug.cgi?id=409821 --- Comment #2 from kram.f...@gmail.com --- Created attachment 122786 --> https://bugs.kde.org/attachment.cgi?id=122786&action=edit buggy swatch when triggering the bug (top swatch is invalid color) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411917] Filter brush with Color Adjustment freezes Krita
https://bugs.kde.org/show_bug.cgi?id=411917 --- Comment #5 from wolthera --- Ah, I hadn't noticed the backtrace somehow! Hm... what is a little weird about that backtrace is that there seem to be debug symbols missing, which is what causes all the ??? here: --- Thread 33 (Thread 0x7fffa9ffa700 (LWP 4040)): #0 0x7fffe6ea36b0 in ?? () from /usr/lib/liblcms2.so.2 #1 0x7fffe54fd0bf in ?? () from /usr/lib/kritaplugins/kritalcmsengine.so #2 0x7fffe5f81f29 in ?? () from /usr/lib/kritaplugins/kritacolorsfilters.so #3 0x75eae7f8 in KisColorTransformationConfiguration::colorTransformation(KoColorSpace const*, KisColorTransformationFilter const*) const () from /usr/lib/libkritaimage.so.18 #4 0x75eb07ad in KisColorTransformationFilter::processImpl(KisSharedPtr, QRect const&, KisPinnedSharedPtr, KoUpdater*) const () from /usr/lib/libkritaimage.so.18 #5 0x75ead299 in KisFilter::process(KisSharedPtr, KisSharedPtr, KisSharedPtr, QRect const&, KisPinnedSharedPtr, KoUpdater*) const () from /usr/lib/libkritaimage.so.18 #6 0x75ead599 in KisFilter::process(KisSharedPtr, QRect const&, KisPinnedSharedPtr, KoUpdater*) const () from /usr/lib/libkritaimage.so.18 #7 0x7fffe4daf26b in ?? () from /usr/lib/kritaplugins/kritafilterop.so #8 0x75e8237c in ?? () from /usr/lib/libkritaimage.so.18 #9 0x75e8148a in ?? () from /usr/lib/libkritaimage.so.18 #10 0x75e815cb in ?? () from /usr/lib/libkritaimage.so.18 #11 0x75e815cb in ?? () from /usr/lib/libkritaimage.so.18 #12 0x75e815cb in ?? () from /usr/lib/libkritaimage.so.18 #13 0x75e815cb in ?? () from /usr/lib/libkritaimage.so.18 #14 0x75e8165a in KisPaintOp::paintBezierCurve(KisPaintInformation const&, QPointF const&, QPointF const&, KisPaintInformation const&, KisDistanceInformation*) () from /usr/lib/libkritaimage.so.18 #15 0x76f7d358 in KisMaskedFreehandStrokePainter::paintBezierCurve(KisPaintInformation const&, QPointF const&, QPointF const&, KisPaintInformation const&) () from /usr/lib/libkritaui.so.18 #16 0x76f77936 in FreehandStrokeStrategy::doStrokeCallback(KisStrokeJobData*) () from /usr/lib/libkritaui.so.18 #17 0x75e3624f in ?? () from /usr/lib/libkritaimage.so.18 #18 0x749fc9a2 in ?? () from /usr/lib/libQt5Core.so.5 #19 0x749f95b0 in ?? () from /usr/lib/libQt5Core.so.5 #20 0x7277457f in start_thread () from /usr/lib/libpthread.so.0 #21 0x7466e0e3 in clone () from /usr/lib/libc.so.6 -- It would've been nice to see what is going on in kritalcmsengine, for example, that causes this crash... You don't happen to know why there's debug symbols missing, do you? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411917] Filter brush with Color Adjustment freezes Krita
https://bugs.kde.org/show_bug.cgi?id=411917 --- Comment #4 from M --- For the GDB backtrace above I had use DISPLAY=:0 gdb krita (thanks to Dmitry for trick) from a virtual terminal, otherwise the whole session would stay frozen, correct. Same output from the build directory executable. What debugging could I do then? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393814] Importing passwords to KWallet backend causes excessive load without progress
https://bugs.kde.org/show_bug.cgi?id=393814 k...@trummer.xyz changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from k...@trummer.xyz --- System: Operating System: openSUSE Tumbleweed 20190918 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 Kernel Version: 5.2.14-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-2540M CPU @ 2.60GHz Memory: 15,5 GiB Falkon: 3.1.0 I tested this recently again (importing a Falkon password dump to the KWallet backend) and it worked now. Therefore I'll set this to "resolved". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411171] Vector tools have problems with selection and transformation
https://bugs.kde.org/show_bug.cgi?id=411171 --- Comment #2 from jamesnoec...@gmail.com --- As for the invisibility problem, it can be reproduced by selecting a vector layer, selecting the transform tool, then selecting the edit shapes tool. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412157] Plasma crashed when opening Clipboard manager
https://bugs.kde.org/show_bug.cgi?id=412157 --- Comment #1 from David Edmundson --- So Plasma was running for a while when it crashed? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411917] Filter brush with Color Adjustment freezes Krita
https://bugs.kde.org/show_bug.cgi?id=411917 --- Comment #3 from wolthera --- Hm... I'd suggest you to run Krita in GDB, but the problem is that the freeze happens in the brush editor, and that will make it impossible to switch to the terminal to do some debugging. Does anything interesting happen in the terminal when you run your own compiled Krita and make this freeze happen? -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 412167] New: Used space of a partition is incorrectly represented by white color instead of light blue when used space is 99%
https://bugs.kde.org/show_bug.cgi?id=412167 Bug ID: 412167 Summary: Used space of a partition is incorrectly represented by white color instead of light blue when used space is 99% Product: filelight Version: 19.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: martin.sandsm...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 122785 --> https://bugs.kde.org/attachment.cgi?id=122785&action=edit screenshot SUMMARY See the screenshot of Filelight 19.08.1 taken on Arch Linux please. Used space of 3 partitions is represented by light blue color. However, the same does not occur with SEAGATE partition. Its used space (99%) is incorrectly represented by white color. EXPECTED RESULT used space is always represented by light blue color. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411612] When using Tags Manager and then closing crashes digikam
https://bugs.kde.org/show_bug.cgi?id=411612 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||6.4.0 --- Comment #30 from caulier.gil...@gmail.com --- Problem definitively fixed with my last commit... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411917] Filter brush with Color Adjustment freezes Krita
https://bugs.kde.org/show_bug.cgi?id=411917 --- Comment #2 from M --- That's strange, it still happens on my system with master (git 59d8e62) and the newest Next AppImage (git a76f4c3). I checked multiple times, it was reproducible every try. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 411286] Discover crashes after opening when updates found, or clicking applications category
https://bugs.kde.org/show_bug.cgi?id=411286 Myriam Schweingruber changed: What|Removed |Added See Also||https://bugreports.qt.io/br ||owse/QTBUG-75203 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407598] Freezing at first stroke - git 7bc375b
https://bugs.kde.org/show_bug.cgi?id=407598 Boudewijn Rempt changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #6 from Boudewijn Rempt --- Let's close it then :-) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407598] Freezing at first stroke - git 7bc375b
https://bugs.kde.org/show_bug.cgi?id=407598 --- Comment #5 from Manga Tengu --- (In reply to wolthera from comment #4) > Hey MangaTengu, does this still happen with 4.2.6? It doesn't happen anymore. I even forgot about it 0_o -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 405405] System settings crashes on close after I try to install a local gtk2 theme
https://bugs.kde.org/show_bug.cgi?id=405405 Patrick Silva changed: What|Removed |Added Version|5.16.0 |5.16.90 --- Comment #7 from Patrick Silva --- This crash is still reproducible sometimes with the steps from comment 6 Operating System: Arch Linux KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f91a9519800 (LWP 17371))] Thread 6 (Thread 0x7f918dfa4700 (LWP 17466)): #0 0x7f919f2d73b1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #1 0x7f919f2c761e in () at /usr/lib/libpulse.so.0 #2 0x7f919ef8fd1c in () at /usr/lib/pulseaudio/libpulsecommon-13.0.so #3 0x7f91acdb857f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f91ae1e40e3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f91956e3700 (LWP 17424)): #0 0x7f91ae1d9667 in poll () at /usr/lib/libc.so.6 #1 0x7f91aa584130 in g_main_context_poll (priority=, n_fds=1, fds=0x7f9188004a30, timeout=, context=0x7f9188000bf0) at ../glib/glib/gmain.c:4216 #2 0x7f91aa584130 in g_main_context_iterate (context=context@entry=0x7f9188000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3912 #3 0x7f91aa584201 in g_main_context_iteration (context=0x7f9188000bf0, may_block=may_block@entry=1) at ../glib/glib/gmain.c:3978 #4 0x7f91ae77da1c in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f9188000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f91ae7244ec in QEventLoop::exec(QFlags) (this=this@entry=0x7f91956e2d80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f91ae556385 in QThread::exec() (this=this@entry=0x557609ddafb0) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f91ad861849 in QQmlThreadPrivate::run() (this=0x557609ddafb0) at /tmp/makepkg/qt5-declarative-debug/src/qtdeclarative-everywhere-src-5.13.1/src/qml/qml/ftw/qqmlthread.cpp:152 #8 0x7f91ae5575b0 in QThreadPrivate::start(void*) (arg=0x557609ddafb0) at thread/qthread_unix.cpp:360 #9 0x7f91acdb857f in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f91ae1e40e3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f9197a09700 (LWP 17423)): #0 0x7f91ae1d9676 in poll () at /usr/lib/libc.so.6 #1 0x7f91aa584130 in g_main_context_poll (priority=, n_fds=1, fds=0x7f9190004e30, timeout=, context=0x7f919bf0) at ../glib/glib/gmain.c:4216 #2 0x7f91aa584130 in g_main_context_iterate (context=context@entry=0x7f919bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3912 #3 0x7f91aa584201 in g_main_context_iteration (context=0x7f919bf0, may_block=may_block@entry=1) at ../glib/glib/gmain.c:3978 #4 0x7f91ae77da1c in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f919b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f91ae7244ec in QEventLoop::exec(QFlags) (this=this@entry=0x7f9197a08d80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f91ae556385 in QThread::exec() (this=this@entry=0x5576096e4ea0) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f91ad861849 in QQmlThreadPrivate::run() (this=0x5576096e4ea0) at /tmp/makepkg/qt5-declarative-debug/src/qtdeclarative-everywhere-src-5.13.1/src/qml/qml/ftw/qqmlthread.cpp:152 #8 0x7f91ae5575b0 in QThreadPrivate::start(void*) (arg=0x5576096e4ea0) at thread/qthread_unix.cpp:360 #9 0x7f91acdb857f in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f91ae1e40e3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f91a5c19700 (LWP 17412)): #0 0x7f91acdbe415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f91a5f4ef5c in () at /usr/lib/dri/i965_dri.so #2 0x7f91a5f4eb58 in () at /usr/lib/dri/i965_dri.so #3 0x7f91acdb857f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f91ae1e40e3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f91a8292700 (LWP 17402)): #0 0x7f91ae1d9667 in poll () at /usr/lib/libc.so.6 #1 0x7f91aa584130 in g_main_context_poll (priority=, n_fds=1, fds=0x7f91a0005260, timeout=, context=0x7f91abf0) at ../glib/glib/gmain.c:4216 #2 0x7f91aa584130 in g_main_context_iterate (context=context@entry=0x7f91abf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3912 #3 0x7f91aa584201 in g_main_context_iteration (context=0x7f91abf0, may_block=may_block@entry=1) at ../glib/glib/gmain.c:3978 #4 0x7f91ae77da1c in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f91ab20, flags=...) at kernel/qeventdispatcher_glib.cpp:42
[dolphin] [Bug 412166] New: Dolphin Not refreshing/loosing file association when renaming files
https://bugs.kde.org/show_bug.cgi?id=412166 Bug ID: 412166 Summary: Dolphin Not refreshing/loosing file association when renaming files Product: dolphin Version: 19.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: breathat.hun...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 122784 --> https://bugs.kde.org/attachment.cgi?id=122784&action=edit Just after filename change SUMMARY Dolphin loses file association upon renaming of the file. File type affected ppt, pptx etc. From local testing, it appears any doctype that is "compressed" once renamed it treats the file as a zip file and is not updated until a refresh. STEPS TO REPRODUCE 1. Have the default dolphin setup from Manjaro 2. Rename a ppt/pptx/doc/docx file OBSERVED RESULT File association is lost. Treated as a compressed file. EXPECTED RESULT File association to remain the same SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 18.1 (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406634] Isolated 'use' elements in a Vector Library .svg file should be ignored
https://bugs.kde.org/show_bug.cgi?id=406634 wolthera changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||griffinval...@gmail.com --- Comment #1 from wolthera --- yes. confirmed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407756] Dragging Krita window from one display to another hang-ups system for a couple of seconds
https://bugs.kde.org/show_bug.cgi?id=407756 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from wolthera --- boud is confirming it in the merge request. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408669] Animation Curves Docker Frame Scrubbing Doesn't Update Visual Indicator
https://bugs.kde.org/show_bug.cgi?id=408669 wolthera changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Yeah, I can confirm this here in 4.3 pre-alpha. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391113] Color selector triangle spins a bit when changing vector colors (Krita 4 beta appimage)
https://bugs.kde.org/show_bug.cgi?id=391113 wolthera changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||griffinval...@gmail.com --- Comment #7 from wolthera --- I'll mark this as resolved. Mvowada, if this happens again, please reopen the bugreport. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409842] Selecting color in Zoom Selector is laggy
https://bugs.kde.org/show_bug.cgi?id=409842 wolthera changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||griffinval...@gmail.com --- Comment #4 from wolthera --- I can confirm, it also happens with shift+i to call up the same widget. The Advanced color selector right now just doesn't like it if there's two copies of it on screen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409894] Rotation Shift+Space action drifts when rotating
https://bugs.kde.org/show_bug.cgi?id=409894 wolthera changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Considering there's a cause identified, I am going to mark this as confirmed. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 395977] Schedule Reports show both sides of transactions
https://bugs.kde.org/show_bug.cgi?id=395977 Thomas Baumgart changed: What|Removed |Added Latest Commit||https://commits.kde.org/kmy ||money/acf951afa3e2d716802e2 ||98efa660b0d55ef3152 Resolution|--- |FIXED Version Fixed In||5.0.7 Status|REPORTED|RESOLVED --- Comment #2 from Thomas Baumgart --- Git commit acf951afa3e2d716802e298efa660b0d55ef3152 by Thomas Baumgart. Committed on 21/09/2019 at 12:52. Pushed by tbaumgart into branch '5.0'. Improve schedule information report Don't show the splits twice and for a simple transaction only show one line. FIXED-IN: 5.0.7 M +13 -3kmymoney/plugins/views/reports/core/objectinfotable.cpp https://commits.kde.org/kmymoney/acf951afa3e2d716802e298efa660b0d55ef3152 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410552] A Keyboard Shortcut 'V' clashes with Canvas Input Setting 'V' + LMB, no warning given
https://bugs.kde.org/show_bug.cgi?id=410552 wolthera changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Yeah, we can confirm this, but the main issue is that our cnavas input settings live in a completely different world from the shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410553] İntuos 4 pen doesnt work outside canvas
https://bugs.kde.org/show_bug.cgi?id=410553 wolthera changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Hey, does this still happen with Krita 4.2.6? If so, can you set the appropriate version? Also, can you maybe tell us how your tablet is set up? Like, which version of windows are you using? Have you set it up to use windows ink or wintab int he settings, is this also reflected in the wacom control settings? The thing is that the intuous 4 is one of the main testing devices, and this is really the first time I have heard of this bug, so maybe it is a configuration hiccup. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 407072] Scheduled Transaction Report does not show amount
https://bugs.kde.org/show_bug.cgi?id=407072 Thomas Baumgart changed: What|Removed |Added Latest Commit||https://commits.kde.org/kmy ||money/a7a1d723353407aa2adde ||c864f85d70a0d941d7b Status|REOPENED|RESOLVED Resolution|--- |FIXED Version Fixed In||5.0.7 --- Comment #3 from Thomas Baumgart --- Git commit a7a1d723353407aa2addec864f85d70a0d941d7b by Thomas Baumgart. Committed on 21/09/2019 at 12:47. Pushed by tbaumgart into branch '5.0'. Show amount in schedule reports FIXED-IN: 5.0.7 M +2-2kmymoney/plugins/views/reports/core/objectinfotable.cpp https://commits.kde.org/kmymoney/a7a1d723353407aa2addec864f85d70a0d941d7b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411507] Zoom icon doesn’t update immediately when pressing ‘Ctrl’
https://bugs.kde.org/show_bug.cgi?id=411507 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from wolthera --- Confirmed on KDE Neon with current master. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411567] varying performance related to zoom
https://bugs.kde.org/show_bug.cgi?id=411567 wolthera changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||griffinval...@gmail.com --- Comment #1 from wolthera --- This is expected behaviour, this precision of the liquify changes with the zoom. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411612] When using Tags Manager and then closing crashes digikam
https://bugs.kde.org/show_bug.cgi?id=411612 --- Comment #29 from caulier.gil...@gmail.com --- Git commit 7d6b3812ee9f0a99682c5e7e53a9155c4d1d5e5f by Gilles Caulier. Committed on 21/09/2019 at 16:13. Pushed by cgilles into branch 'master'. Do not embed KMainWindow in a KMainWindow just to create a layout and plug KToolBar as well. KMainWindow => QMainWindow => it's not the main parent dialog everywhere. KToolBar => QToolBar Code cleanup, simplifications, and optimisations M +32 -34 core/libs/tags/manager/tagsmanager.cpp M +3-7core/libs/tags/manager/tagsmanager.h https://invent.kde.org/kde/digikam/commit/7d6b3812ee9f0a99682c5e7e53a9155c4d1d5e5f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411661] "Select a Color" dialog is modeless when setting fg color and modal when setting bg color
https://bugs.kde.org/show_bug.cgi?id=411661 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Severity|minor |wishlist --- Comment #1 from wolthera --- Yes, this is expected behaviour. I'll set this to wishlist. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411776] Gaussian Blur Filter Layer Doesn't Wrap Around Canvas like Gaussian Blur Filter Operation
https://bugs.kde.org/show_bug.cgi?id=411776 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from wolthera --- Hey Eoin, can you still reproduce this with master? I don't seem to be able to reproduce this here on KDE Neon. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396028] Imported Layer Styles Lose Properties
https://bugs.kde.org/show_bug.cgi?id=396028 wolthera changed: What|Removed |Added CC||cyr...@gmail.com --- Comment #5 from wolthera --- *** Bug 406759 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406759] [4.1.8 git a9ed8de] Use Layer Style from other document doesn't import all settings.
https://bugs.kde.org/show_bug.cgi?id=406759 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from wolthera --- *** This bug has been marked as a duplicate of bug 396028 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392265] Problems with icon on Create Template From Image
https://bugs.kde.org/show_bug.cgi?id=392265 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #8 from wolthera --- I cannot reproduce this here either(taking the exact same steps as the attached video) Does this still happen in the 4.2.x series? Is there anything unique about your resource folder? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412165] New: Discover crashed whilst installing snap app that required protection turning off.
https://bugs.kde.org/show_bug.cgi?id=412165 Bug ID: 412165 Summary: Discover crashed whilst installing snap app that required protection turning off. Product: Discover Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: k...@dandart.co.uk CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.16.5) Qt Version: 5.12.2 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: Ubuntu 19.04 -- Information about the crash: - What I was doing when the application crashed: Searched for Skype Pressed Install Tried to confirm the snap question to whether protections should be turned off Segfaulted -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9a309a5940 (LWP 23609))] Thread 10 (Thread 0x7f9a06ffd700 (LWP 23729)): #0 0x7f9a34bb0fb4 in __GI___libc_read (nbytes=16, buf=0x7f9a06ffca40, fd=20) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f9a34bb0fb4 in __GI___libc_read (fd=20, buf=0x7f9a06ffca40, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f9a339d3410 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9a3398c6cf in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9a3398cba0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9a3398cd1c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f9a35137063 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9a350e25bb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9a34f2d2c6 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f9a34f2e612 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9a3434e182 in start_thread (arg=) at pthread_create.c:486 #11 0x7f9a34bc1b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f9a077fe700 (LWP 23658)): #0 0x7f9a343543bb in futex_wait_cancelable (private=, expected=0, futex_word=0x55f71f024734) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f9a343543bb in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f71f0246e0, cond=0x55f71f024708) at pthread_cond_wait.c:502 #2 0x7f9a343543bb in __pthread_cond_wait (cond=0x55f71f024708, mutex=0x55f71f0246e0) at pthread_cond_wait.c:655 #3 0x7f9a34f34733 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9a34f34819 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9a36bd65d9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f9a36bd683a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f9a34f2e612 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9a3434e182 in start_thread (arg=) at pthread_create.c:486 #9 0x7f9a34bc1b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f9a07fff700 (LWP 23656)): #0 0x7f9a34bb5729 in __GI___poll (fds=0x7f99fc044a20, nfds=1, timeout=90329) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9a3398cbf6 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9a3398cd1c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9a35137063 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9a350e25bb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9a34f2d2c6 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9a34f2e612 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9a3434e182 in start_thread (arg=) at pthread_create.c:486 #8 0x7f9a34bc1b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f9a16224700 (LWP 23646)): #0 0x7f9a3398c515 in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9a3398cba0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9a3398cd1c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9a35137063 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9a350e25bb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9a34f2d2c6 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9a34f2e612 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9a3434e182 in start_thread (arg=) at pthread_create.c:486 #8 0x7f9a34bc1b1f in clone () at .
[krita] [Bug 395861] Contiguous Selection Tool is too slow
https://bugs.kde.org/show_bug.cgi?id=395861 wolthera changed: What|Removed |Added Severity|normal |wishlist CC||griffinval...@gmail.com --- Comment #5 from wolthera --- I am setting this to wishlist considering that while it is annoying, it would require rewriting the floodfill algorithm. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 412164] New: I have been trying to upgrade from 2.15.0 with no success,
https://bugs.kde.org/show_bug.cgi?id=412164 Bug ID: 412164 Summary: I have been trying to upgrade from 2.15.0 with no success, Product: skrooge Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: wind_ros...@yahoo.com CC: steph...@mankowski.fr Target Milestone: --- SUMMARY Skrooge 2.15.0 while adding items to an operation field l had keyed in the figures then pressed ADD when l had a red banner pop up indicating an error [ERR-5]: Operation creation failed [ERR-10001]: cannot rollback - no transaction is active Unable to fetch row [ERR-10010]: disk I/O error Unable to fetch row [ERR-10010]: COMMIT; I checked for a possible solution as best l could then resorted to closing the program and restarting after which all appears normal again but felt it should be noted. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397346] Color-to-Alpha filter mask range seems to give wrong results
https://bugs.kde.org/show_bug.cgi?id=397346 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #12 from wolthera --- We should give emmet bugzilla prowess. Setting this to confirmed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404519] Adding Hold Frames to a horizontal range often removes selection
https://bugs.kde.org/show_bug.cgi?id=404519 wolthera changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from wolthera --- Yeah, seeing it now, I can confirm this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412163] Checking for freespace BEFORE copy instead of during or once MERGE has been clicked.
https://bugs.kde.org/show_bug.cgi?id=412163 --- Comment #1 from dft --- Typo on #4 should say "missing 4GB" 4. Try resuming the copy - technically it should now only need to copy the missing 4GB. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406825] Krita doesn't respond during color space conversion
https://bugs.kde.org/show_bug.cgi?id=406825 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from wolthera --- If two developers agree on something being a bug, it is confirmed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412163] New: Checking for freespace BEFORE copy instead of during or once MERGE has been clicked.
https://bugs.kde.org/show_bug.cgi?id=412163 Bug ID: 412163 Summary: Checking for freespace BEFORE copy instead of during or once MERGE has been clicked. Product: dolphin Version: 19.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dieseltr...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Lets say I have 100GB free. I want to RESUME copying a folder onto the drive of 120GB. Lets say it only has 2GB of copying needed as I stopped it around 118GB copied. I will get an error saying "There is not enough space on the disk to write file". This is false as once the folder was merged I would have 98GB free. It falsely assumes I need space for the ENTIRE copy. This means I can't use Dolphin to resume a copy and have to open up another file manager that checks for free space DURING the copy not before. STEPS TO REPRODUCE 1. Format a 32GB partition 2. Try copy 20GB on to it 3. Cancel the copy at around 16GB copied - You should have 16GB free 4. Try resuming the copy - technically it should now only need to copy the missing 16GB. 5. It will fail as it assumes it needs 20GB free... OBSERVED RESULT "There is not enough space on the disk to write file" EXPECTED RESULT Copying should resume just fine when clicking merge. Available space needed should be an information message not a halt type message SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.16 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION This is a show stopper for Dolphin -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406697] Cut & Paste layers is possible inside locked group
https://bugs.kde.org/show_bug.cgi?id=406697 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from wolthera --- If two developers agree on something being a bug it is confirmed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407050] G'Mic filters don't work if they need multiple layers
https://bugs.kde.org/show_bug.cgi?id=407050 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407246] Not possible to choose bright colors for onion skin for HDR animation
https://bugs.kde.org/show_bug.cgi?id=407246 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from wolthera --- This is also because these values are stuck in QColor sRGB. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407401] Layer is saved without FX
https://bugs.kde.org/show_bug.cgi?id=407401 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from wolthera --- Yes, this is because the layer fx is something atop the layer. You can group the layer, and then export that group if you need the FX included? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407598] Freezing at first stroke - git 7bc375b
https://bugs.kde.org/show_bug.cgi?id=407598 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from wolthera --- Hey MangaTengu, does this still happen with 4.2.6? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407724] Unintuitive sorting of languages list in comic manager
https://bugs.kde.org/show_bug.cgi?id=407724 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Assignee|krita-bugs-n...@kde.org |griffinval...@gmail.com Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from wolthera --- Hm... I am not sure what I can do about this, but I'll set this as assigned. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407725] Country is not remembered as meta data in the comic manager.
https://bugs.kde.org/show_bug.cgi?id=407725 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Assignee|krita-bugs-n...@kde.org |griffinval...@gmail.com Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from wolthera --- Er, I'll set this as assigned. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407801] Recent colors vertical rows should be populated vertically
https://bugs.kde.org/show_bug.cgi?id=407801 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Severity|normal |wishlist --- Comment #1 from wolthera --- setting this to wishlist. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407851] Sidebar width not kept after restarting
https://bugs.kde.org/show_bug.cgi?id=407851 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #2 from wolthera --- setting this as resolved upstream then. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407896] Memory indicator widget bar is showing the memory used amount wrong
https://bugs.kde.org/show_bug.cgi?id=407896 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from wolthera --- If two developers agree something is a bug, the bug is confirmed. -- You are receiving this mail because: You are watching all bug changes.
