[kmymoney] [Bug 395912] New: Number field not wide enough when directly entering transactions into list
https://bugs.kde.org/show_bug.cgi?id=395912 Bug ID: 395912 Summary: Number field not wide enough when directly entering transactions into list Product: kmymoney Version: 5.0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: chrisjoshtop...@gmail.com Target Milestone: --- Created attachment 113587 --> https://bugs.kde.org/attachment.cgi?id=113587=edit Number field too narrow for 3 digits The number field is too small when entering transactions directly into the list. Currently only two characters are visible in the number field but at least three should be visible if not 4. See the attached screenshot where I have entered the number 111 but only "11" is visible. Steps to reproduce: 1. Turn off transaction form (Settings->Configure KMyMoney->Ledger->Display tab). 2. Insert a new transaction in an account 3. See that only two characters are visible in the Number field. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 395820] Ark Crashes when opening ttf font inside a zip file
https://bugs.kde.org/show_bug.cgi?id=395820 --- Comment #3 from now-im --- I downloaded noto mono ttf from google website. From: Christoph Feck Sent: Wednesday, June 27, 2018 3:10:35 AM To: now.im@gmail.com Subject: [ark] [Bug 395820] Ark Crashes when opening ttf font inside a zip file https://bugs.kde.org/show_bug.cgi?id=395820 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 364746 *** -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[pimsettingexporter] [Bug 395911] New: pimsettingsexporter "contacts" directory path incorrect
https://bugs.kde.org/show_bug.cgi?id=395911 Bug ID: 395911 Summary: pimsettingsexporter "contacts" directory path incorrect Product: pimsettingexporter Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: iadzhu...@verizon.net Target Milestone: --- I tried to backup my PIM settings today and noticed the following error in the PIM Settings Exporter (pimsettingsexporter) log: Impossible to backup "/home/login_user/.local/share/share/contacts/". Apparently, the pathname it is looking for is wrong, it contains extra "share" component which should not be there. pimsettingsexporter version: 5.7.3 KDE 17.12.3 Plasma 5.12.5 Kubuntu 18.04 LTS w/backports PPA -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395910] New: KMail segfaults upon exit
https://bugs.kde.org/show_bug.cgi?id=395910 Bug ID: 395910 Summary: KMail segfaults upon exit Product: kmail2 Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: fritigerngot...@gmail.com Target Milestone: --- Application: kmail (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-23-lowlatency x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: - What I was doing when the application crashed: I exited the application by right-clicking the system tray icon and choosing "Quit". The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8cd1c9b80 (LWP 7498))] Thread 26 (Thread 0x7fb85effd700 (LWP 9411)): #0 0x7fb8bfbbb9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x564e21c15ee8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fb8bfbbb9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x564e21c15e98, cond=0x564e21c15ec0) at pthread_cond_wait.c:502 #2 0x7fb8bfbbb9f3 in __pthread_cond_wait (cond=0x564e21c15ec0, mutex=0x564e21c15e98) at pthread_cond_wait.c:655 #3 0x7fb8b4a5cc95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fb8b4a5d177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fb8b4a5df11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fb8b4a5a5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fb8bfbb56db in start_thread (arg=0x7fb85effd700) at pthread_create.c:463 #8 0x7fb8ca2c588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7fba3700 (LWP 7562)): #0 0x7fb8bfbbb9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x564e21c15eec) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fb8bfbbb9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x564e21c15e98, cond=0x564e21c15ec0) at pthread_cond_wait.c:502 #2 0x7fb8bfbbb9f3 in __pthread_cond_wait (cond=0x564e21c15ec0, mutex=0x564e21c15e98) at pthread_cond_wait.c:655 #3 0x7fb8b4a5cc95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fb8b4a5d177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fb8b4a5df11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fb8b4a5a5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fb8bfbb56db in start_thread (arg=0x7fba3700) at pthread_create.c:463 #8 0x7fb8ca2c588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fb7fd0eb700 (LWP 7561)): #0 0x7fb8bfbbb9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fb8b1327fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fb8bfbbb9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fb8b1327f68, cond=0x7fb8b1327f90) at pthread_cond_wait.c:502 #2 0x7fb8bfbbb9f3 in __pthread_cond_wait (cond=0x7fb8b1327f90, mutex=0x7fb8b1327f68) at pthread_cond_wait.c:655 #3 0x7fb8b10315f4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fb8b1031639 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fb8bfbb56db in start_thread (arg=0x7fb7fd0eb700) at pthread_create.c:463 #6 0x7fb8ca2c588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fb81effd700 (LWP 7533)): #0 0x7fb8ca2b40b4 in __GI___libc_read (fd=71, buf=0x7fb81effc85e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fb8a4fe2ff1 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7fb8ad9d39fe in pa_mainloop_prepare () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fb8ad9d4470 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fb8ad9d4530 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fb8ad9e2399 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fb8a50122a8 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7fb8bfbb56db in start_thread (arg=0x7fb81effd700) at pthread_create.c:463 #8 0x7fb8ca2c588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7fb81f7fe700 (LWP 7532)): #0 0x7fb8ca2d46ac in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7fb8ca2d6474 in ___fprintf_chk (fp=0x7fb8ca5918b0 <_IO_stdfile_2_lock>, flag=1, format=0x7fb8aba626a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7fb8aba4a9ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3
[latte-dock] [Bug 395909] New: Mouse wheel triggers application launch
https://bugs.kde.org/show_bug.cgi?id=395909 Bug ID: 395909 Summary: Mouse wheel triggers application launch Product: latte-dock Version: 0.7.95 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: mue...@gmail.com Target Milestone: --- Using the mouse wheel over an icon in the dock launches the application. Note: The version I'm running is 0.7.5, but I couldn't select it as a version in the bug tracker, as it's not part of the list. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395908] New: Choosing show on a system tray icon's visibility settings crashed plasmashell
https://bugs.kde.org/show_bug.cgi?id=395908 Bug ID: 395908 Summary: Choosing show on a system tray icon's visibility settings crashed plasmashell Product: plasmashell Version: 5.12.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: pau...@airmail.cc Target Milestone: 1.0 Created attachment 113585 --> https://bugs.kde.org/attachment.cgi?id=113585=edit The crash dump it said to upload I was looking at the settings to change it so qBittorrent's system icon is always visible if it's running (which it was), and when I changed it to 'show' instead of 'auto' it crashed plasma shell. When plasmashell the new setting had saved and the icon was there. I've attached the crash dump it generated -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395712] Save session right after login crashes KWin
https://bugs.kde.org/show_bug.cgi?id=395712 David Edmundson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/2693e288c57a66facbe6b9932 ||ce8628a53afb246 Resolution|--- |FIXED --- Comment #2 from David Edmundson --- Git commit 2693e288c57a66facbe6b9932ce8628a53afb246 by David Edmundson. Committed on 27/06/2018 at 00:36. Pushed by davidedmundson into branch 'Plasma/5.13'. Avoid potential assert in SM saving Summary: Sesison Manager stores all relevant clients. There's an assert if the window type is outside of the standard client window types. It assumed that all windows outside this would be Unmanaged windows rather than Client objects, something probably true but not something enforced. This particular crash was probably cased as we have a new window type in Plasma OSD, which does not set BypassWindowManager in Qt window flags. Test Plan: Set to restore session Logged out and back in Saw some windows Set to restore manually saved session Hit save No crash Reviewers: #kwin, graesslin Reviewed By: #kwin, graesslin Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D13715 M +8-0sm.cpp https://commits.kde.org/kwin/2693e288c57a66facbe6b9932ce8628a53afb246 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395906] KWin restarts after Composer fails to drag windows to the edges.
https://bugs.kde.org/show_bug.cgi?id=395906 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Which compiler do you use? -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 279563] [Windows] Using location bar to navigate to a file results in "File Not Found" and a slash (/) appended to end of address
https://bugs.kde.org/show_bug.cgi?id=279563 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UNMAINTAINED --- Comment #12 from Nate Graham --- Thanks Ben. Let's track with with a separate bug, since it seems to be a separate issue. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 395907] New: Ktorrent crashed after removing torrent file
https://bugs.kde.org/show_bug.cgi?id=395907 Bug ID: 395907 Summary: Ktorrent crashed after removing torrent file Product: ktorrent Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: mej1...@gmail.com Target Milestone: --- Application: ktorrent (5.1.0) Qt Version: 5.11.0 Frameworks Version: 5.47.0 Operating System: Linux 4.13.0-45-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: A torrent had completed downloading. I right clicked the torrent, seleced Remove, and the application crashed. When I restarted KTorrent the torrent was removed. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f04c818a900 (LWP 2312))] Thread 8 (Thread 0x7f048e758700 (LWP 2330)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f04c2f5a5cb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x1093770) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x1114ef0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f04c7a6edb3 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Torrent.so.6 #4 0x7f04c2f59727 in QThreadPrivate::start (arg=0x1114ee0) at thread/qthread_unix.cpp:367 #5 0x7f04be0226ba in start_thread (arg=0x7f048e758700) at pthread_create.c:333 #6 0x7f04c233241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f048ef59700 (LWP 2329)): #0 0x7f04c7a6f465 in net::Poll::add(QSharedPointer) () from /usr/lib/x86_64-linux-gnu/libKF5Torrent.so.6 #1 0x7f04c7a6bcd6 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Torrent.so.6 #2 0x7f04c7a6be56 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Torrent.so.6 #3 0x7f04c7a6c6b9 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Torrent.so.6 #4 0x7f04c2f59727 in QThreadPrivate::start (arg=0x81d230) at thread/qthread_unix.cpp:367 #5 0x7f04be0226ba in start_thread (arg=0x7f048ef59700) at pthread_create.c:333 #6 0x7f04c233241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f048f75a700 (LWP 2328)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f04c2f4a355 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=3, op=0, addr=) at thread/qfutex_p.h:92 #2 QtLinuxFutex::futexWait > (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at thread/qmutex_linux.cpp:145 #4 QBasicMutex::lockInternal (this=0x81cee8) at thread/qmutex_linux.cpp:162 #5 0x7f04c2f4a412 in QBasicMutex::lock (this=0x81cee8) at thread/qmutex.h:79 #6 QRecursiveMutexPrivate::lock (timeout=-1, this=0x81ced0) at thread/qmutex.cpp:708 #7 QMutex::lock (this=) at thread/qmutex.cpp:227 #8 0x7f04c7a6c4ac in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Torrent.so.6 #9 0x7f04c7a6c6b9 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Torrent.so.6 #10 0x7f04c2f59727 in QThreadPrivate::start (arg=0x81cf00) at thread/qthread_unix.cpp:367 #11 0x7f04be0226ba in start_thread (arg=0x7f048f75a700) at pthread_create.c:333 #12 0x7f04c233241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f0492d3a700 (LWP 2320)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0497e8c48b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7f0497e8c397 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7f04be0226ba in start_thread (arg=0x7f0492d3a700) at pthread_create.c:333 #4 0x7f04c233241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f04a9aea700 (LWP 2319)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0497e8c48b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7f0497e8c397 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7f04be0226ba in start_thread (arg=0x7f04a9aea700) at pthread_create.c:333 #4 0x7f04c233241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f04a92e9700 (LWP 2318)): #0 0x7f04c232674d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f04bc17d38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f04bc17d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f04c3171beb in QEventDispatcherGlib::processEvents (this=0x7f04a8c0, flags=...) at
[gwenview] [Bug 395890] No Error when same Picture name is selected
https://bugs.kde.org/show_bug.cgi?id=395890 --- Comment #3 from Henrik Fehlauer --- > Henrik, did you test with KIO 5.47.0? See also bug 394318. I now tested with KIO 5.47, but as I suspected the bug is still there. Bug 394318 was about pasting and unconditionally overwriting, while here the issue is with renaming and silently aborting if the file already exists. Sounds like a genuine Gwenview problem to me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395906] New: KWin restarts after Composer fails to drag windows to the edges.
https://bugs.kde.org/show_bug.cgi?id=395906 Bug ID: 395906 Summary: KWin restarts after Composer fails to drag windows to the edges. Product: kwin Version: 5.12.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: murilog...@gmail.com Target Milestone: --- Application: kwin_x11 (5.12.5) (Compiled from sources) Qt Version: 5.9.6 Frameworks Version: 5.47.0 Operating System: Linux 4.17.1-gentoo x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I was testing the effects of KDE, I just enabled the Composer, I changed it to OpenGL 3.1 and the rest is in the standards. When you try to drag any window to the edges, KWin closes unexpectedly. - Unusual behavior I noticed: KWin restarts to "seemingly" try to "find out" to which size the window would be resized. - Custom settings of the application: Render Infrastructure. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f67f3134800 (LWP 7847))] Thread 6 (Thread 0x7f673690c700 (LWP 7873)): #0 0x7f67eb9f626c in futex_wait_cancelable (private=, expected=0, futex_word=0x5591f8e7d020) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5591f8e7cfd0, cond=0x5591f8e7cff8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5591f8e7cff8, mutex=0x5591f8e7cfd0) at pthread_cond_wait.c:655 #3 0x7f6736eddcbb in cnd_wait (mtx=0x5591f8e7cfd0, cond=0x5591f8e7cff8) at /var/tmp/portage/media-libs/mesa-18.1.2/work/mesa-18.1.2/include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x5591f8e637b0) at /var/tmp/portage/media-libs/mesa-18.1.2/work/mesa-18.1.2/src/util/u_queue.c:255 #5 0x7f6736edda47 in impl_thrd_routine (p=) at /var/tmp/portage/media-libs/mesa-18.1.2/work/mesa-18.1.2/include/c11/threads_posix.h:87 #6 0x7f67eb9f0488 in start_thread (arg=0x7f673690c700) at pthread_create.c:463 #7 0x7f67f2ab8c9f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f67bb7ff700 (LWP 7866)): #0 0x7f67eb9f626c in futex_wait_cancelable (private=, expected=0, futex_word=0x7f67ef014f98 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f67ef014f48 , cond=0x7f67ef014f70 ) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f67ef014f70 , mutex=0x7f67ef014f48 ) at pthread_cond_wait.c:655 #3 0x7f67eed0acf9 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f67ef006ea0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #4 0x7f67eed0ae89 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #5 0x7f67eb9f0488 in start_thread (arg=0x7f67bb7ff700) at pthread_create.c:463 #6 0x7f67f2ab8c9f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f67c90bb700 (LWP 7865)): #0 0x7f67f2aaef82 in __GI_ppoll (fds=fds@entry=0x7f67cd28, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f67efe9bc0d in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f67cd28) at kernel/qcore_unix.cpp:81 #3 qt_safe_poll (fds=0x7f67cd28, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:102 #4 0x7f67efe9d46e in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f67efe46cfa in QEventLoop::exec (this=this@entry=0x7f67c90badb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f67efc6e9da in QThread::exec (this=this@entry=0x5591f8dc4d80) at thread/qthread.cpp:515 #7 0x7f67ea4435b5 in QQmlThreadPrivate::run (this=0x5591f8dc4d80) at qml/ftw/qqmlthread.cpp:147 #8 0x7f67efc7376e in QThreadPrivate::start (arg=0x5591f8dc4d80) at thread/qthread_unix.cpp:368 #9 0x7f67eb9f0488 in start_thread (arg=0x7f67c90bb700) at pthread_create.c:463 #10 0x7f67f2ab8c9f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f67cb652700 (LWP 7852)): #0 0x7f67f2aaef82 in __GI_ppoll (fds=fds@entry=0x7f67c400b148, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f67efe9bc0d in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f67c400b148) at kernel/qcore_unix.cpp:81 #3
[krita] [Bug 395070] Krita Crashes suddenly without warning
https://bugs.kde.org/show_bug.cgi?id=395070 --- Comment #7 from Bryan Willis --- Crash! Here's the log. Please let me know anything you can about this. (gdb) set pagination off (gdb) thread apply all bt Thread 11388 (Thread 0x7fff9e678700 (LWP 27448)): #0 0x74392881 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:78 #1 0x7fffee03f600 in __free_stacks (limit=41943040) at allocatestack.c:282 #2 0x7fffee03f600 in queue_stack (stack=) at allocatestack.c:305 #3 0x7fffee03f600 in __deallocate_stack (pd=) at allocatestack.c:806 #4 0x7fffee03f600 in __free_tcb (pd=) at pthread_create.c:367 #5 0x in () Thread 11387 (Thread 0x7fff963fd700 (LWP 27447)): #0 0x74308207 in tcache_get (tc_idx=0) at malloc.c:2943 #1 0x74308207 in __GI___libc_malloc (bytes=8) at malloc.c:3050 #2 0x7490d54c in operator new(unsigned long) () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x71fb42e2 in QList >::node_construct(QList >::Node*, KisSharedPtr const&) (this=0x7fff963fca10, t=..., n=0x7fff7c12e058) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:435 #4 0x71fb42e2 in QList >::append(KisSharedPtr const&) (this=this@entry=0x7fff963fca10, t=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:593 #5 0x71fadb4c in KisMementoManager::commit() (this=this@entry=0x7fff8809d080) at ./libs/image/tiles3/kis_memento_manager.cc:196 #6 0x71fae0c5 in KisMementoManager::getMemento() (this=0x7fff8809d080) at ./libs/image/tiles3/kis_memento_manager.cc:243 #7 0x7213b7c4 in KisTiledDataManager::getMemento() (this=0x7fff880d05e0, this=) at ./libs/image/tiles3/kis_tiled_data_manager.h:130 #8 0x7213b7c4 in KisDataManager::getMemento() (this=) at ./libs/image/kis_datamanager.h:86 #9 0x7213b7c4 in KisTransactionData::init(KisSharedPtr) (this=this@entry=0x7fff7c0c0200, device=...) at ./libs/image/kis_transaction_data.cpp:115 #10 0x7213c107 in KisTransactionData::KisTransactionData(KUndo2MagicString const&, KisSharedPtr, bool, KUndo2Command*) (this=0x7fff7c0c0200, name=..., device=..., resetSelectionOutlineCache=, parent=) at ./libs/image/kis_transaction_data.cpp:72 #11 0x7fffbb4ae4bd in KisTransaction::KisTransaction(KisSharedPtr, KUndo2Command*, int) (timedID=-1, parent=0x0, device=..., this=) at ./libs/image/kis_transaction.h:37 #12 0x7fffbb4ae4bd in TransformStrokeStrategy::doStrokeCallback(KisStrokeJobData*) (this=0x634f8a60, data=) at ./plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp:198 #13 0x721f4d0b in non-virtual thunk to KisUpdateJobItem::run() () at /usr/lib/x86_64-linux-gnu/libkritaimage.so.16 #14 0x74cb12a2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x74cb416d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fffee03f6db in start_thread (arg=0x7fff963fd700) at pthread_create.c:463 #17 0x7439288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11386 (Thread 0x7fff9d009700 (LWP 27446)): #0 0x74392881 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:78 #1 0x7fffee03fec5 in create_thread (thread_ran=, stackaddr=0x7fff9e677f00, stopped_start=, attr=0x7fff9d008680, pd=0x7fff9e678700) at ../sysdeps/unix/sysv/linux/createthread.c:100 #2 0x7fffee03fec5 in __pthread_create_2_1 (newthread=, attr=, start_routine=, arg=0x7fff880d4c50) at pthread_create.c:797 #3 0x74cb3666 in QThread::start(QThread::Priority) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74caf87d in QThreadPoolPrivate::startThread(QRunnable*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x74cb09ab in QThreadPoolPrivate::tryStart(QRunnable*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x74cb0fbb in QThreadPool::start(QRunnable*, int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x720a8247 in KisSimpleUpdateQueue::processOneJob(KisUpdaterContext&) (this=this@entry=0x63328168, updaterContext=...) at ./libs/image/kis_simple_update_queue.cpp:124 #8 0x720a911b in KisSimpleUpdateQueue::processQueue(KisUpdaterContext&) (this=0x63328168, updaterContext=...) at ./libs/image/kis_simple_update_queue.cpp:95 #9 0x720ac352 in KisUpdateScheduler::tryProcessUpdatesQueue() (this=) at ./libs/image/kis_update_scheduler.cpp:453 #10 0x720ac640 in KisUpdateScheduler::processQueues() (this=this@entry=0x6569fb18) at ./libs/image/kis_update_scheduler.cpp:410 #11 0x720aca62 in KisUpdateScheduler::updateProjection(KisSharedPtr, QVector const&, QRect const&) (this=0x6569fb18, node=..., rects=..., cropRect=...) at ./libs/image/kis_update_scheduler.cpp:166 #12 0x720bf1b0 in KisImage::requestProjectionUpdateImpl(KisNode*, QVector const&, QRect const&) (this=this@entry=0x6c266020, node=node@entry=0x7fffdc7939e0, rects=..., cropRect=...) at ./libs/image/kis_image.cc:1581 #13 0x720c6dff in
[kwin] [Bug 395818] Inaccurate mouse input in Nexuiz on Wayland
https://bugs.kde.org/show_bug.cgi?id=395818 --- Comment #3 from Rainer Finke --- I've tested the patch of the other 2 bug reports further. The mouse "jump" only happens if I play in a borderless window mode in my full monitor resolution. So the mouse seems to reach virtually an edge and then the mouse makes this jump from one place to another. If I switch to fullscreen, the input works well. The other issue regarding a slow and stuck mouse, that I've noticed before, seems to be gone completely. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395727] Blur with transparency not working in application menus
https://bugs.kde.org/show_bug.cgi?id=395727 --- Comment #13 from Michael D --- I have no problem with closing the bug for the very good reason you provided. However, the workaround is "trivial" only if the user knows what it is in advance, which is why it took me four days to figure it out. Unless you turn transparency on during an empty session, you'll probably be scratching your head for some time trying to figure out what's broken. That's why I'd prefer a user warning like the warning one receives when changing font settings, namely, "Some changes such as anti-aliasing or DPI will only affect newly started applications." -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395881] Display formatting is broken from last update
https://bugs.kde.org/show_bug.cgi?id=395881 Christoph Feck changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395897] Dolphin starts with blank spaces (empty panels) at bottom and right
https://bugs.kde.org/show_bug.cgi?id=395897 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 395881 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395881] Display formatting is broken from last update
https://bugs.kde.org/show_bug.cgi?id=395881 Christoph Feck changed: What|Removed |Added CC||fabrice.salva...@orange.fr --- Comment #3 from Christoph Feck --- *** Bug 395897 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 395890] No Error when same Picture name is selected
https://bugs.kde.org/show_bug.cgi?id=395890 --- Comment #2 from Christoph Feck --- Henrik, did you test with KIO 5.47.0? See also bug 394318. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364746] Crash when accessing 'Font Management' inside Fonts section of 'Settings'
https://bugs.kde.org/show_bug.cgi?id=364746 Christoph Feck changed: What|Removed |Added CC||now.im@gmail.com --- Comment #32 from Christoph Feck --- *** Bug 395820 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 395820] Ark Crashes when opening ttf font inside a zip file
https://bugs.kde.org/show_bug.cgi?id=395820 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 364746 *** -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 395844] Autocompletion popup doesn't work
https://bugs.kde.org/show_bug.cgi?id=395844 Nikita Sirgienko changed: What|Removed |Added Latest Commit||https://commits.kde.org/can ||tor/254761a6ec1d29a5912163d ||8ed42a730071ed5a1 Version Fixed In||18.04.3 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Nikita Sirgienko --- Git commit 254761a6ec1d29a5912163d8ed42a730071ed5a1 by Nikita Sirgienko. Committed on 26/06/2018 at 20:54. Pushed by sirgienko into branch 'master'. Fix bug with autocomplete popup in Sage backend FIXED-IN: 18.04.3 M +1-1src/backends/sage/sagecompletionobject.cpp https://commits.kde.org/cantor/254761a6ec1d29a5912163d8ed42a730071ed5a1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377985] I have 2 emails in outbox that I cannot delete
https://bugs.kde.org/show_bug.cgi?id=377985 --- Comment #3 from bjk...@web.de --- after update opensuse: all sent email are in the outbox. I can delete it. After the next lookup to the outbox folder they are back Is there a solution? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377985] I have 2 emails in outbox that I cannot delete
https://bugs.kde.org/show_bug.cgi?id=377985 --- Comment #2 from bjk...@web.de --- sorry, my english is not the best (german) and i am only a normal user ... -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377985] I have 2 emails in outbox that I cannot delete
https://bugs.kde.org/show_bug.cgi?id=377985 bjk...@web.de changed: What|Removed |Added CC||bjk...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395905] New: cannot add effect on to the track
https://bugs.kde.org/show_bug.cgi?id=395905 Bug ID: 395905 Summary: cannot add effect on to the track Product: kdenlive Version: 18.04.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: steven...@gmail.com Target Milestone: --- I cannot add an effect to a track only to clips. If I try to add an effect (by clicking in the Properties window) to a track I get an error message "Problem editing effect" OS: opensuse 42.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied for aurorae decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 --- Comment #7 from varlesh --- Created attachment 113584 --> https://bugs.kde.org/attachment.cgi?id=113584=edit yakuake skin (shadows) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied for aurorae decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 --- Comment #6 from varlesh --- This happened on Yakuake shadows skin too. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395904] New: cannot add new audio or video track
https://bugs.kde.org/show_bug.cgi?id=395904 Bug ID: 395904 Summary: cannot add new audio or video track Product: kdenlive Version: 18.04.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: steven...@gmail.com Target Milestone: --- I cannot add a new audio or video track because in the "Project->Peoject Settings" both spinboxes are inactive. It is possible only to set the initial value in the "Project Defaults" Version: Version 18.04.2 OS: Opensuse 42.3 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 395820] Ark Crashes when opening ttf font inside a zip file
https://bugs.kde.org/show_bug.cgi?id=395820 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Elvis Angelaccio --- Does not seem to crash here. Can you attach (or link) the zip file that you were using? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395897] Dolphin starts with blank spaces (empty panels) at bottom and right
https://bugs.kde.org/show_bug.cgi?id=395897 --- Comment #2 from Elvis Angelaccio --- Can you attach a screenshot showing the empty panels? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 395890] No Error when same Picture name is selected
https://bugs.kde.org/show_bug.cgi?id=395890 Henrik Fehlauer changed: What|Removed |Added CC||rk...@lab12.net Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Henrik Fehlauer --- Thanks for the report. I can confirm the issue with Gwenview 18.04.2. When pressing F2 in View mode, renaming is aborted, but no error is shown. Also I wonder whether we could show a "File already exists: Rename / Overwrite / Cancel" dialog (cf. Dolphin) instead of the plain error message for both View and Browse mode. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368287] Dolphin crashed while moving files
https://bugs.kde.org/show_bug.cgi?id=368287 Elvis Angelaccio changed: What|Removed |Added CC||e...@evanjt.com --- Comment #12 from Elvis Angelaccio --- *** Bug 395835 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395835] Crashes when moving a file from one location to another
https://bugs.kde.org/show_bug.cgi?id=395835 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- Thanks for the detailed report. We are already tracking this issue in #368287. Since you can reproduce the crash, please install debug symbols for kio and kcoreaddons and then post a new backtrace. Thanks! *** This bug has been marked as a duplicate of bug 368287 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381972] Krita crashes when trying to merge layers
https://bugs.kde.org/show_bug.cgi?id=381972 Antti Savolainen changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Antti Savolainen --- I'll close this since the original crash was fixed and the odd behavior was reported separately. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395727] Blur with transparency not working in application menus
https://bugs.kde.org/show_bug.cgi?id=395727 Nate Graham changed: What|Removed |Added Resolution|--- |INVALID Status|REOPENED|RESOLVED --- Comment #12 from Nate Graham --- Recommend closing the bug report. It's annoying, for sure, but there's a trivial workaround. I think fixing this is going to be a big project--much larger in scope than just what's listed here--and probably falls under the umbrella of a potential future "move to an instant-apply model" project. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395903] New: Krita merges layers it shouldn't
https://bugs.kde.org/show_bug.cgi?id=395903 Bug ID: 395903 Summary: Krita merges layers it shouldn't Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: antti.s...@gmail.com Target Milestone: --- The linked file was found from https://bugs.kde.org/show_bug.cgi?id=381972 The incorrect behavior can be replicated by following the original report but I'll repost the original steps Steps to reproduce: 1. download the file: https://www.dropbox.com/s/t3m7wh80glr4yxd/so_79_krita_crash.kra?dl=0 (I've created the file specifically for this case, and I have similar and stable crashes on another file) 2. Select all the layers from "select from this layer" to "to this", including group layer. 3. Press ctrl-e to merge 'em. //4. After the merge press ctrl-z to undo. //5. Krita crashes. Krita merges Layers 9 and 1 even if they were never selected Example video: https://youtu.be/P8GpTUs8FoI Build & Platform: krita 4.1.0-pre-alpha (git hash: 4a3af9a) Xubuntu 17.10 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] Turn off screen after lock screen
https://bugs.kde.org/show_bug.cgi?id=348529 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395727] Blur with transparency not working in application menus
https://bugs.kde.org/show_bug.cgi?id=395727 --- Comment #11 from Michael D --- At the least, shouldn't the user should a warning that they may need to restart applications for the new settings to take effect? I know some other settings do this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395727] Blur with transparency not working in application menus
https://bugs.kde.org/show_bug.cgi?id=395727 --- Comment #10 from Alex Nemeth --- (In reply to Michael D from comment #9) > It seems I figured out the problem. If an application is already running > when transparency is off, and then transparency is enabled, blur won't work. > After restarting the application with transparency already on, blur works. Several other settings have the same problem, this is not restricted just to widget settings, so I think this is normal behavior. Nate what do you think of this? This is not a bug with Breeze transparency as the title may suggest. Can we close/rename/reassign this report? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395681] libinput pointer kcm needs 11 ticks on the speed slider so that the middle one can correspond to 0.0
https://bugs.kde.org/show_bug.cgi?id=395681 Furkan Tokac changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-desktop/13b35bd8025a4bc ||f399670c32ee20327b0ace392 --- Comment #7 from Furkan Tokac --- Git commit 13b35bd8025a4bcf399670c32ee20327b0ace392 by Furkan Tokac. Committed on 26/06/2018 at 20:12. Pushed by furkantokac into branch 'master'. Mouse KCM Pointer Speed Slider Improvement Summary: Slider value to libinput value mapping algorithm is changed. Tested and everything is working fine. You can test it by changing value on slider and checking the libinput value from ~/.config/kcminputrc Reviewers: ngraham, romangg, #plasma, mart Reviewed By: ngraham, romangg, #plasma, mart Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D13672 M +9-6kcms/mouse/kcm/libinput/main.qml M +9-6kcms/mouse/kcm/libinput/main_deviceless.qml https://commits.kde.org/plasma-desktop/13b35bd8025a4bcf399670c32ee20327b0ace392 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 395902] New: kde-frameworks/baloo-5.47.0 - crash in the background
https://bugs.kde.org/show_bug.cgi?id=395902 Bug ID: 395902 Summary: kde-frameworks/baloo-5.47.0 - crash in the background Product: frameworks-baloo Version: 5.47.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: nheghathivhis...@gmail.com Target Milestone: --- Application: baloo_file (5.47.0) (Compiled from sources) Qt Version: 5.11.0 Frameworks Version: 5.47.0 Operating System: Linux 4.17.0-gentoo x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: Watching a local video file, rsyncing remote server backup to the same RAID 1 LUKS encrypted EXT4 volume where the file was played from - rsync was writing two big DB gzipped backup files during the crash. Found KDE crash reporter icon after rsync finished. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe3799087c0 (LWP 4428))] Thread 3 (Thread 0x7fe36d0d4700 (LWP 4546)): #0 g_mutex_unlock (mutex=0x7fa36bf0) at /var/tmp/portage/dev-libs/glib-2.54.3-r6/work/glib-2.54.3/glib/gthread-posix.c:1348 #1 0x7fe373ab5340 in g_main_context_prepare (context=context@entry=0x7fa36bf0, priority=priority@entry=0x7fe36d0d3a90) at /var/tmp/portage/dev-libs/glib-2.54.3-r6/work/glib-2.54.3/glib/gmain.c:3508 #2 0x7fe373ab5d7b in g_main_context_iterate (context=context@entry=0x7fa36bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.54.3-r6/work/glib-2.54.3/glib/gmain.c:3848 #3 0x7fe373ab5f5c in g_main_context_iteration (context=0x7fa36bf0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.54.3-r6/work/glib-2.54.3/glib/gmain.c:3929 #4 0x7fe37801e5bb in QEventDispatcherGlib::processEvents (this=0x7fa36b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fe377fcb20a in QEventLoop::exec (this=this@entry=0x7fe36d0d3cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x55a5bdcff01d in Baloo::FileContentIndexer::run (this=0x55a5bfc4de00) at /var/tmp/portage/kde-frameworks/baloo-5.47.0/work/baloo-5.47.0/src/file/filecontentindexer.cpp:73 #7 0x7fe377e32191 in QThreadPoolThread::run (this=0x55a5bfe7e790) at thread/qthreadpool.cpp:101 #8 0x7fe377e3a50f in QThreadPrivate::start (arg=0x55a5bfe7e790) at thread/qthread_unix.cpp:367 #9 0x7fe37635c9aa in start_thread (arg=0x7fe36d0d4700) at pthread_create.c:463 #10 0x7fe37732f79f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fe36dad6700 (LWP 4438)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67 #1 0x7fe377323c1b in __GI___poll (fds=0x7fe368003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #2 0x7fe373ab5e49 in g_main_context_poll (priority=, n_fds=1, fds=0x7fe368003ce0, timeout=, context=0x7fe368000bf0) at /var/tmp/portage/dev-libs/glib-2.54.3-r6/work/glib-2.54.3/glib/gmain.c:4169 #3 g_main_context_iterate (context=context@entry=0x7fe368000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.54.3-r6/work/glib-2.54.3/glib/gmain.c:3863 #4 0x7fe373ab5f5c in g_main_context_iteration (context=0x7fe368000bf0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.54.3-r6/work/glib-2.54.3/glib/gmain.c:3929 #5 0x7fe37801e5bb in QEventDispatcherGlib::processEvents (this=0x7fe368000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fe377fcb20a in QEventLoop::exec (this=this@entry=0x7fe36dad5db0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x7fe377e30bea in QThread::exec (this=this@entry=0x7fe379469d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:522 #8 0x7fe3791f1de5 in QDBusConnectionManager::run (this=0x7fe379469d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #9 0x7fe377e3a50f in QThreadPrivate::start (arg=0x7fe379469d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #10 0x7fe37635c9aa in start_thread (arg=0x7fe36dad6700) at pthread_create.c:463 #11 0x7fe37732f79f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fe3799087c0 (LWP 4428)): [KCrash Handler] #6 0x7fe37508f4c4 in mdb_midl_xmerge (idl=idl@entry=0x7fe36c835018, merge=merge@entry=0x7fa4a8b93010) at midl.c:207 #7 0x7fe375086c0f in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7ffd13bad348, mc=) at mdb.c:2271 #8 0x7fe375087089 in mdb_page_touch
[print-manager] [Bug 395885] Printer Settings should be saved under user profile, not global CUPS configuration
https://bugs.kde.org/show_bug.cgi?id=395885 Daniel Nicoletti changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Daniel Nicoletti --- print-manager doesn't touch any files by it's own, it only talks CUPS protocol, which is what other desktops also do, I won't even try to write changes to local user because that is likely to break since CUPS doesn't provide any API for that. I might accept a patch for this if this does look good. But most distros already have the main user as root so that you don't get prompted, and speaking of corporate CUPS process is so small that you usually will be talking to CUPS on your own machine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395898] High CPU usage when Atom text editor is open
https://bugs.kde.org/show_bug.cgi?id=395898 Michail Vourlakos changed: What|Removed |Added CC||mvourla...@gmail.com --- Comment #2 from Michail Vourlakos --- I reproduced this by using the plasma application menu bar. The plasmashell process after the atom editor opened was using constantly 100% of one of my processors -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395898] High CPU usage when Atom text editor is open
https://bugs.kde.org/show_bug.cgi?id=395898 Michail Vourlakos changed: What|Removed |Added Version|0.7.4 |5.13.1 CC||plasma-b...@kde.org Assignee|mvourla...@gmail.com|k...@privat.broulik.de Target Milestone|--- |1.0 Product|latte-dock |plasmashell Component|application |Global Menu -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 395901] New: Setting gamma for individual screens does not work
https://bugs.kde.org/show_bug.cgi?id=395901 Bug ID: 395901 Summary: Setting gamma for individual screens does not work Product: KScreen Version: 5.13.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: tho...@mitterfellner.at Target Milestone: --- I have two screens set up: my laptop's screen and an external monitor connected via HDMI. The "sync screens" checkbox is not checked, but strangely, the combo box is greyed and only shows "Screen 1" despite the Display section of the configuration module showing both monitors. Consequently, both screens are affected when I drag the slider. Am I misunderstanding what is written here: https://docs.kde.org/trunk5/en/kde-workspace/kcontrol/kgamma5/index.html – should it actually be possible to set the gamma for each display individually when I use two screens with only one graphics card? Is there a difference between a "screen", a "display" and a "monitor" in that context or are they same? If that should actually work, what can I do to debug it (provide debug info)? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395727] Blur with transparency not working in application menus
https://bugs.kde.org/show_bug.cgi?id=395727 Michael D changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395727] Blur with transparency not working in application menus
https://bugs.kde.org/show_bug.cgi?id=395727 --- Comment #9 from Michael D --- It seems I figured out the problem. If an application is already running when transparency is off, and then transparency is enabled, blur won't work. After restarting the application with transparency already on, blur works. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378656] Crash when we set color label filtering and try to select other layers with R click select
https://bugs.kde.org/show_bug.cgi?id=378656 Antti Savolainen changed: What|Removed |Added CC||antti.s...@gmail.com --- Comment #3 from Antti Savolainen --- Oh, this is exiting finding a working crash in old reports I followed your instructions and and kinda panicked when after left and right clicking layers started disappearing. I Ctrl+z a couple of times to reverse the changes, which came out not as it was supposed to and eventually a crash. Build & Platform: krita 4.1.0-pre-alpha (git hash: 4a3af9a) Xubuntu 17.10 Video demonstrating the crash: https://www.youtube.com/watch?v=Yn1TIg22ro0 Thread 1 "krita" received signal SIGSEGV, Segmentation fault. __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:489 489 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: No such file or directory. (gdb) bt #0 0x740230e5 in __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:489 #1 0x74a71aea in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74a71d03 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74a74358 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74ad98e5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x74a462be in QAbstractItemModel::rowsAboutToBeRemoved(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x74a4d21b in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x77008a9e in KisNodeModel::slotBeginRemoveDummy(KisNodeDummy*) (this=0x61a985e0, dummy=0x5981b020) at /home/managor/Sourcebuilding/krita/libs/ui/kis_node_model.cpp:348 #8 0x773ecd35 in KisNodeModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x61a985e0, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7fffc800) at /home/managor/Sourcebuilding/b-krita/libs/ui/kritaui_autogen/EWIEGA46WW/moc_kis_node_model.cpp:124 #9 0x74ad98e5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x773e2064 in KisDummiesFacadeBase::sigBeginRemoveDummy(KisNodeDummy*) (this=0x61fd00f0, _t1=0x5981b020) at /home/managor/Sourcebuilding/b-krita/libs/ui/kritaui_autogen/QUY67KCZCL/moc_kis_dummies_facade_base.cpp:281 #11 0x76f49be2 in KisDummiesFacadeBase::slotContinueRemoveNode(KisSharedPtr) (this=0x61fd00f0, node=...) at /home/managor/Sourcebuilding/krita/libs/ui/flake/kis_dummies_facade_base.cpp:153 #12 0x773e18b3 in KisDummiesFacadeBase::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x61fd00f0, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x7fffca70) at /home/managor/Sourcebuilding/b-krita/libs/ui/kritaui_autogen/QUY67KCZCL/moc_kis_dummies_facade_base.cpp:148 #13 0x74ad98e5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x773e1ef4 in KisDummiesFacadeBase::sigContinueRemoveNode(KisSharedPtr) (this=0x61fd00f0, _t1=...) at /home/managor/Sourcebuilding/b-krita/libs/ui/kritaui_autogen/QUY67KCZCL/moc_kis_dummies_facade_base.cpp:260 #15 0x76f497cc in KisDummiesFacadeBase::slotRemoveNode(KisSharedPtr) (this=0x61fd00f0, node=...) at /home/managor/Sourcebuilding/krita/libs/ui/flake/kis_dummies_facade_base.cpp:133 #16 0x773e17da in KisDummiesFacadeBase::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x61fd00f0, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x7fffcce0) at /home/managor/Sourcebuilding/b-krita/libs/ui/kritaui_autogen/QUY67KCZCL/moc_kis_dummies_facade_base.cpp:146 #17 0x74ad98e5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x71d33562 in KisImage::sigRemoveNodeAsync(KisSharedPtr) (this=0x61f46bf0, _t1=...) at /home/managor/Sourcebuilding/b-krita/libs/image/kritaimage_autogen/EWIEGA46WW/moc_kis_image.cpp:726 #19 0x71d3197f in KisImage::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x61f46bf0, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fffcfc0) at /home/managor/Sourcebuilding/b-krita/libs/image/kritaimage_autogen/EWIEGA46WW/moc_kis_image.cpp:317 #20 0x74ad98e5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x71d34dfc in KisImageSignalRouter::sigRemoveNodeAsync(KisSharedPtr) (this=0x61f0f100, _t1=...) at /home/managor/Sourcebuilding/b-krita/libs/image/kritaimage_autogen/EWIEGA46WW/moc_kis_image_signal_router.cpp:332 #22
[kdenlive] [Bug 395900] No Audio When Playing Clips Frame by Frame
https://bugs.kde.org/show_bug.cgi?id=395900 mickyrosenl...@tuta.io changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395900] New: No Audio When Playing Clips Frame by Frame
https://bugs.kde.org/show_bug.cgi?id=395900 Bug ID: 395900 Summary: No Audio When Playing Clips Frame by Frame Product: kdenlive Version: 18.04.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: mickyrosenl...@tuta.io Target Milestone: --- When playing a clip Frame by Frame, or maybe drag the timeline cursor (sometimes timeline cursor works if you drag quickly), then there is no audio. This problem has currently been reported on Windows and Linux Mint. Here is a forum thread that summerizes this problem clearly: https://forum.kde.org/viewtopic.php?f=271=152481 It seems as if Kdenlive 18 has only made Kdenlive worse for some Windows users. This bug importance varies from normal-major depending on the use cases of each user. I recommend fixing this quickly. There also seems to be a workaround for Windows: "Split video and audio so you can see the audio waves. Zoom into the timeline so you can cut according the wave peaks. " -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 386665] Drop dependency on pulseaudio-gconf
https://bugs.kde.org/show_bug.cgi?id=386665 Antonio Rojas changed: What|Removed |Added CC|aro...@archlinux.org| -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 386315] Media Frame widget memory leak
https://bugs.kde.org/show_bug.cgi?id=386315 --- Comment #5 from Mirek Mieszczak --- I suffer also from this bug, on Gentoo KDE Frameworks. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 386315] Media Frame widget memory leak
https://bugs.kde.org/show_bug.cgi?id=386315 Mirek Mieszczak changed: What|Removed |Added CC||mies...@mieszczak.com.pl -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379294] Implement OSC 8 hyperlink support
https://bugs.kde.org/show_bug.cgi?id=379294 --- Comment #8 from Egmont Koblinger --- (In reply to Martin Sandsmark from comment #7) > and I'm fairly certain konsole never implemented the escape sequences for > injecting keystrokes in the first place either Not arbitrary keystrokes, but certain ones. Try e.g. echo -ne '\e[>c' > about the clickable filenames it's a bit off topic for this bug, but you > need to turn in on in the settings. and how konsole tracks the current > directory depends on OS and shell (if it supports OCS7), but that feature is > much older, but earlier it was just used to display the current directory in > the window/tab title. Thanks, now I've found it. As expected, it only works for a simple "ls". As soon as I do an "ls some-other-directory", it no longer works, or even worse, can mistake a file for its counterpart of the same name from another directory. I don't even dare to try whitespaces and other weird characters in the filename. > > And you can't just blindly assume that 3-4 other components all have > > security issues > > I think that's where you and I disagree. you could make the same argument > against sandboxing and many other defense in depth strategies. Sandboxing is not just for security, sure its part of their stories, but other parts are about avoiding the hassle with conflicting libraries etc. And as for security, there it's an entire OS with plenty of features and plenty of potentially broken places, that is, gazillions of possible entry points for security bugs. A pretty wide system diagram, if you wish, whereas for the OSC 8 feature it's a simple stack with a very small number of components. And I'd like to emphasize again that the feature was modeled after web browsers, so if there's any security hole in its implementation, it's probably already there even without the terminal emulator. We didn't invent anything brand new, just applied something already seen on the web into terminal emulators. > but misunderstand me correctly; I'm not violently opposed to this, I just > don't believe the security/usefulness tradeoff is good here. Usefulness if of course another question. I myself often use it for local filenames, as printed by "ls". And as opposed to konsole where it works _sometimes_, for me it works _always_. I am still not convinced at all about security issues, especially if konsole decides to limit support to a few well-known schemes. And don't get me wrong, I'm not completely against security either, see e.g. another feature request for gnome-terminal at https://bugzilla.gnome.org/show_bug.cgi?id=795774 which, although could be a convenient one, I don't support due to its security implications. I just don't see the security problems in the hyperlink story. Anyway, I guess we need to agree that we disagree. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395818] Inaccurate mouse input in Nexuiz on Wayland
https://bugs.kde.org/show_bug.cgi?id=395818 --- Comment #2 from Rainer Finke --- The linked bugs are only partially related. I've tested the fix, but the mouse "jump" is still there either in the game and in the menu. It is impossible to control the mouse as of this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395815] Input in Nexuiz is not recognized until pressing ESC for 3 seconds (Wayland)
https://bugs.kde.org/show_bug.cgi?id=395815 --- Comment #3 from Rainer Finke --- I've tested the bug fix and it works as expected. Thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394974] Layer converted filter mask causes Krita crash most of the time.
https://bugs.kde.org/show_bug.cgi?id=394974 --- Comment #10 from Andras --- (In reply to Antti Savolainen from comment #9) > I recorded a video to ask you if I'm doing something or if I have some > setting differently than you have. Let me know. https://youtu.be/1Y2QfZKZx18 I don't really see differences on settings, maybe the Opacity or Flow option what I set to 75%. However I noticed that Krita calculates only those filter masks what you're currently editing, I mean one by one on your video. Well, Krita performs calculations on every single filter masks inside one group when I edit a single filter mask. It's annoying. Is there any setting to stop this behavior? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379294] Implement OSC 8 hyperlink support
https://bugs.kde.org/show_bug.cgi?id=379294 --- Comment #7 from Martin Sandsmark --- again, I was just coming up with hypothetical scenarios based on the use cases of the proposed feature (having "magic" links in mutt seems kind of reasonable, as does clickable files starting applications to view them). neomutt is probably a better hypothetical target, they're a bit less conservative in what kind of features they implement. and I'm fairly certain konsole never implemented the escape sequences for injecting keystrokes in the first place either (and was not susceptible to the window title escape sequence trick either). about the clickable filenames it's a bit off topic for this bug, but you need to turn in on in the settings. and how konsole tracks the current directory depends on OS and shell (if it supports OCS7), but that feature is much older, but earlier it was just used to display the current directory in the window/tab title. > And you can't just blindly assume that 3-4 other components all have security > issues I think that's where you and I disagree. you could make the same argument against sandboxing and many other defense in depth strategies. but misunderstand me correctly; I'm not violently opposed to this, I just don't believe the security/usefulness tradeoff is good here. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 395844] Autocompletion popup doesn't work
https://bugs.kde.org/show_bug.cgi?id=395844 Nikita Sirgienko changed: What|Removed |Added Ever confirmed|0 |1 CC||warqu...@gmail.com Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 371124] Frequent crash without apparent common cause, I have the reports from drmingw
https://bugs.kde.org/show_bug.cgi?id=371124 Boudewijn Rempt changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WORKSFORME --- Comment #57 from Boudewijn Rempt --- I'm sorry, Maria, but this is now quite old, and we've never been able to figure out what was going on. If you still have problems with the latest release (4.1.0 from tomorrow), please create a new bug report. But there just isn't anything we can do with this report right now, though you have spent so much effort helping us out. I'm really sorry! -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 395870] Kmymoney help center not launching properly
https://bugs.kde.org/show_bug.cgi?id=395870 --- Comment #11 from Jack --- Randall - this bug was filed against khelpcenter, not KMyMoney. However, any packaging questions have to be addressed to Mint. The KDE teams release software, but each distribution does the packaging. Older LTS versions of Mint might well still be using kdelibs4, which means they will be stuck with KMM 4.8. To use KMM 5.0 (5.0.1 has been released) you need a distribution that uses KF5 (KDE Frameworks.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363063] Crash while selecting colors with changed color spaces in selectors settings
https://bugs.kde.org/show_bug.cgi?id=363063 Antti Savolainen changed: What|Removed |Added CC||antti.s...@gmail.com Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Antti Savolainen --- This has been fixed -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 395880] Internal Astrometry Configuration File Write Error
https://bugs.kde.org/show_bug.cgi?id=395880 --- Comment #1 from Jean-Claude --- I solved the problem by copying the kstars folder and the preferences files from another machine. Please mark this report as solved. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 395898] High CPU usage when Atom text editor is open
https://bugs.kde.org/show_bug.cgi?id=395898 --- Comment #1 from Michail Vourlakos --- are you using global menu? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392870] Segfault after quickly closing a document after toggling layer visibility
https://bugs.kde.org/show_bug.cgi?id=392870 Antti Savolainen changed: What|Removed |Added Severity|normal |crash --- Comment #2 from Antti Savolainen --- Changing the importance and repasting my backtrace with symbols Thread 1 "krita" received signal SIGSEGV, Segmentation fault. 0x77008d34 in KisNodeModel::processUpdateQueue (this=0x61a1c1c0) at /home/managor/Sourcebuilding/krita/libs/ui/kis_node_model.cpp:387 387 QModelIndex index = m_d->indexConverter->indexFromDummy(dummy); (gdb) bt #0 0x77008d34 in KisNodeModel::processUpdateQueue() (this=0x61a1c1c0) at /home/managor/Sourcebuilding/krita/libs/ui/kis_node_model.cpp:387 #1 0x773ecd9b in KisNodeModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x61a1c1c0, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0x7fffd710) at /home/managor/Sourcebuilding/b-krita/libs/ui/kritaui_autogen/EWIEGA46WW/moc_kis_node_model.cpp:129 #2 0x74ad98e5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74ae63b7 in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74ae6718 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x74ada40b in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7582546c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7582cd34 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x772ca717 in KisApplication::notify(QObject*, QEvent*) (this=0x7fffde20, receiver=0x61a22b90, event=0x7fffdaa0) at /home/managor/Sourcebuilding/krita/libs/ui/KisApplication.cpp:626 #9 0x74aaade8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x74b0291e in QTimerInfoList::activateTimers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x74b03119 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fffec03cfb7 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fffec03d1f0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fffec03d27c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x74b0347f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x74aa8e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x74ab1da4 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x55e903cc in main(int, char**) (argc=1, argv=0x7fffdf88) at /home/managor/Sourcebuilding/krita/krita/main.cc:419 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395899] Color is applied as light instead of selected shade/color
https://bugs.kde.org/show_bug.cgi?id=395899 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from wolthera --- Hi Starwarfan, What you are describing is only one of the many ways a brush preset can function. Each brush preset has a different look and feel to them, and the artists that use Krita use different brushes for different effects, regardless of how real world tools work. You can customize how brushes work by using the brush settings: https://docs.krita.org/en/user_manual/loading_saving_brushes.html This is not a crash or any other kind of bug. It therefore does not belong on the bug tracker. For this reason I am going to close it as invalid. If you have questions on how to use brushes, I would recommend using the forum as there different people can give opinions on how they use their brushes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386127] After deleting a file layer that has a clone layer, krita crashes on loading the .kra file
https://bugs.kde.org/show_bug.cgi?id=386127 Antti Savolainen changed: What|Removed |Added Resolution|--- |FIXED CC||antti.s...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #8 from Antti Savolainen --- There is no way to fix opening the file so it'll keep crashing but these sort of files are no longer possible to be created. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395899] New: Color is applied as light instead of selected shade/color
https://bugs.kde.org/show_bug.cgi?id=395899 Bug ID: 395899 Summary: Color is applied as light instead of selected shade/color Product: krita Version: 4.0.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: starwarfa...@gmail.com Target Milestone: --- After selecting color, applying to correct shade selected requires several strokes of brush rather than applying the shade of color selected. Making work much like using an actual tool rather than digital. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379294] Implement OSC 8 hyperlink support
https://bugs.kde.org/show_bug.cgi?id=379294 --- Comment #6 from Egmont Koblinger --- > in that hypothetical scenario with mutt you could put the blame on mutt all > you want for not filtering out this new escape sequence (or supporting it), > it's still a security issue that wouldn't be there without this. If an email client emits the email's contents raw as-is (including control characters, escape sequences) to the terminal, than that is a serious problem that should be reported and fixed as soon as possible. And yes, in that case it's _that_ email client (or other console-based app) to blame! I'm quite confident mutt is not such a client. It's probably the most popular console-based email client across developers, geeks etc. who know what they're doing, and such a bug would almost sure have been discovered by now. Actually, it's one of the very few email clients immune to the recently discovered EFAIL (https://efail.de/) security issue, which makes me trust them to a reasonable degree. Moreover, it uses ncurses for screen rendering, so it _has_ to convert the email's contents into a different model anyway, and if it doesn't filter out the escape characters, then ncurses does it. In order to make mutt send an explicit hyperlink escape sequence to the terminal, triggered my a maliciously crafted email; you'd need to find a yet undiscovered bug in mutt or ncurses, which is probably not much more likely than finding a remote code execution bug. Or making it send an escape sequence to which the terminal emulator responds by injecting keystrokes (yes there are such escape sequences), potentially triggering further actions in mutt. Of course, we're not talking about "mutt", we're talking about "any email client", "any IRC client" etc. > as for the xdg-open thing; say you get xdg-open to launch via an URI handler > with the arguments %20--%20rm%20-f%20--no-preserve-root%20/, How do you get it to do this? Or if you can, what stops this from happening when clicking on a malicious URL in your favorite browser? Why would konsole launch xdg-open with this scheme-less URI as argument if it's potentially harmful? > and get it to > launch gnome-terminal with the passed arguments. Again, how would you do this? Why would xdg-open's parameter become a direct parameter to gnome-terminal (after URI decoding and splitting at spaces)? If that's the case then that's a security problem that can already be exploited at many other places. > entry point could be a > funnily named file displayed by e. g. tab completion or something else > non-obvious, since one of the use example functioning cases is clicking on > files displayed by ls. As per the specs, URIs should be fully qualified ones, beginning with a scheme. "ls" is only able to produce hyperlinks beginning with "file://", and so would be any shell implementing hyperlinks e.g. at tab completion. If I understand you correctly, you've come up with a vaguely outlined scenario of how things could go wrong, assuming that about 3 or 4 other components are all buggy in a way that probably each of them opens up security holes already, even without explicit hyperlink support in the terminal emulator. I really doubt any of these holes actually exist. If they do, they should be fixed. If you're unsure but worried, you could double-check these yourself, and file bugs if required. > (fwiw, konsole already supports clicking on filenames > by tracking the current directory + known mimetypes, without the security > issues.) Could you please elaborate on this? How can I try it out? (I have konsole 17.12.3.) Clicking, ctrl+clicking, right-clicking after an "ls" doesn't do anything for me. How does it know which directory is being listed, how does it know how the listed file's directory relates to the current working directory (especially in case of multiple arguments to ls, or recursive listing)? How does it know the working directory of the running command? The only thing it could do is to poll it, which is quite expensive, and subject to race condition. Oh wait, how does it even know which descendant process outputs the given data, i.e. which descendant process's working directory to check? How does it know what kind of escaping does "ls" do (see its --quoting-style parameter)? How does it recognize and treat filenames containing special characters? How does it know if "ls" was executed over an "ssh", hence its output refers to a remote file? For the explicit hyperlink support there is a specification answering all these. Is there for konsole's approach? Assuming that for start, you'd limit explicit hyperlink support to the "file", "http" and "https" schemes only. In that case I'm absolutely certain that OSC 8 is superior to what konsole does currently, even including security implications. > my point is that security is not binary, and security in depth is good. > basically; everywhere I see this could be useful it is a decrease in > security, providing a new
[Discover] [Bug 395455] Discover buttons install/remove/launch disappear
https://bugs.kde.org/show_bug.cgi?id=395455 Nate Graham changed: What|Removed |Added Version Fixed In||5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 395898] New: High CPU usage when Atom text editor is open
https://bugs.kde.org/show_bug.cgi?id=395898 Bug ID: 395898 Summary: High CPU usage when Atom text editor is open Product: latte-dock Version: 0.7.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: jacobbornhei...@gmail.com Target Milestone: --- Overview: Whenever Atom text editor is opened, latte-dock's CPU usage goes up from <1% to ~25%. At the same time, Atom's usage also reaches around 25%. This results in a pronounced slowdown. Minimizing/maximizing windows slows, as well as highlighting when hovering over the dock. This stabilizes after 15-20 seconds. However, the slowdown happens again when hovering over or interacting in any way with the dock. Can be replicated repeatedly. Tested with a number of other applications, none of which duplicate this bug. Steps to Reproduce: 1) install latte-dock via sudo apt install latte-dock 2) install atom via sudo snap install atom 3) open latte-dock 4) open atom Latte dock installed via apt. Latte version 0.7.4 Atom installed via snap. Atom version 1.27.2. OS: Kubuntu 18.04, 64-bit KDE Plasma version 5.12.5 Qt version 5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395865] Green Colour clip is only white
https://bugs.kde.org/show_bug.cgi?id=395865 mickyrosenl...@tuta.io changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from mickyrosenl...@tuta.io --- https://forum.kde.org/viewtopic.php?f=265=152541=400428#p400428 This post sums up the whole problem. It appears to apply to images and in on Manjaro only. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387564] Crash on closing Krita if a new window had been opened and closed previously
https://bugs.kde.org/show_bug.cgi?id=387564 Antti Savolainen changed: What|Removed |Added Resolution|--- |FIXED CC||antti.s...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Antti Savolainen --- Boudewijn has investigated and fixed this at some point. Reopen this report if this is untrue. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 387368] Ktorrent freezes after starting
https://bugs.kde.org/show_bug.cgi?id=387368 Stefano changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||erist...@cryptolab.net Ever confirmed|0 |1 --- Comment #4 from Stefano --- I have the same issue with ktorrent in my Arch Linux install. My workaround was uninstalling the kdewebkit package. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381972] Krita crashes when trying to merge layers
https://bugs.kde.org/show_bug.cgi?id=381972 Antti Savolainen changed: What|Removed |Added CC||antti.s...@gmail.com --- Comment #4 from Antti Savolainen --- The crash seems to be fixed but the merging is still odd. It merges all the layers to a single one even the ones that aren't selected. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395455] Discover buttons install/remove/launch disappear
https://bugs.kde.org/show_bug.cgi?id=395455 Aleix Pol changed: What|Removed |Added Latest Commit||https://commits.kde.org/dis ||cover/d5f7c102854c41e4ee9eb ||00cfb979993f2396233 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #8 from Aleix Pol --- Git commit d5f7c102854c41e4ee9eb00cfb979993f2396233 by Aleix Pol. Committed on 26/06/2018 at 17:29. Pushed by apol into branch 'master'. Adapt to new syntax for the header Fixes weird behavior on the Kirigami header M +1-1CMakeLists.txt M +2-9discover/qml/DiscoverWindow.qml https://commits.kde.org/discover/d5f7c102854c41e4ee9eb00cfb979993f2396233 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 395709] PPC64 is missing support for the xvnegsp instruction
https://bugs.kde.org/show_bug.cgi?id=395709 --- Comment #4 from Carl Love --- Argh. Comment 3 was the wrong commit. Should have been commit 1f69ed86e994ee152a0e6e3ee7031d0105f02a7e Author: Carl Love Date: Mon Jun 25 16:24:14 2018 -0500 Fix ppc32 results for test_isa_2_06_part3.c. The ppc32 results were not updated when the xvnegsp instruction support was added. Add the xvnegsp 32-bit results to ppc/test_isa_2_06_part3.stdout.exp. Signed-off-by: Carl Love -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 395749] Device pairings are lost between reboots
https://bugs.kde.org/show_bug.cgi?id=395749 --- Comment #6 from Tamás Barta --- I found https://bugs.kde.org/show_bug.cgi?id=368812 Is it possible, that they are related? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 395749] Device pairings are lost between reboots
https://bugs.kde.org/show_bug.cgi?id=395749 --- Comment #5 from Tamás Barta --- Sorry, I was too soon to comment. After another login, the file is erased again. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 395709] PPC64 is missing support for the xvnegsp instruction
https://bugs.kde.org/show_bug.cgi?id=395709 --- Comment #3 from Carl Love --- Missed updating the ppc32 expected results. commit 3df8d81f000a47c02a289ac9f4ba64fc4df9077e Author: Carl Love Date: Tue Jun 26 09:51:11 2018 -0500 PPC32, update expected results for jm_vec_isa_2_07.c. Add missing mtvsrwa, mtfprd, mtvrwa, mtvrd results. Signed-off-by: Carl Love -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385662] canvas input settings: deleting a shortcut is broken; deleting a shortcut if there is none crashes Krita.
https://bugs.kde.org/show_bug.cgi?id=385662 --- Comment #5 from Boudewijn Rempt --- I do remember fixing the crash, but there are still other issues with this thing... -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 395749] Device pairings are lost between reboots
https://bugs.kde.org/show_bug.cgi?id=395749 --- Comment #4 from Tamás Barta --- Versions same as above: Plasma 5.13, Arch Linux, Frameworks 5.47, KDE Connect 1.3.1. 5.13.2 just came out, could it fix this issue? I cannot reproduce it anymore, and the file's contents remain between sessions. Can you still reproduce, Tromzy? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 395749] Device pairings are lost between reboots
https://bugs.kde.org/show_bug.cgi?id=395749 --- Comment #3 from Tamás Barta --- Created attachment 113583 --> https://bugs.kde.org/attachment.cgi?id=113583=edit trusted_devices This is my file after successful pairing. Before pairing this file is completely empty. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395874] switch between splited windows by pressing TAB button
https://bugs.kde.org/show_bug.cgi?id=395874 --- Comment #2 from Patrice Grundmann --- OMG, excellent! Thanks for the tips, I searched in Dolphin shortcuts ^^ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394420] Folder view applet is expanded when in panel
https://bugs.kde.org/show_bug.cgi?id=394420 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 395870] Kmymoney help center not launching properly
https://bugs.kde.org/show_bug.cgi?id=395870 --- Comment #10 from Randal --- Is there a package for version 5. I am just starting out and would like to be up to date from the beginning. -Randal -Original Message- From: Luigi Toscano Sent: Jun 26, 2018 9:40 AM To: Randal Zell Subject: [khelpcenter] [Bug 395870] Kmymoney help center not launching properly https://bugs.kde.org/show_bug.cgi?id=395870 Luigi Toscano changed: What|Removed |Added Resolution|WAITINGFORINFO |DOWNSTREAM Status|NEEDSINFO |RESOLVED --- Comment #9 from Luigi Toscano --- Thanks for confirming. It's a packaging issue on the distribution. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 395870] Kmymoney help center not launching properly
https://bugs.kde.org/show_bug.cgi?id=395870 Luigi Toscano changed: What|Removed |Added Resolution|WAITINGFORINFO |DOWNSTREAM Status|NEEDSINFO |RESOLVED --- Comment #9 from Luigi Toscano --- Thanks for confirming. It's a packaging issue on the distribution. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g
https://bugs.kde.org/show_bug.cgi?id=393146 Ellis Breen changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g
https://bugs.kde.org/show_bug.cgi?id=393146
Ellis Breen changed:
What|Removed |Added
CC||ellis.br...@gmail.com
--- Comment #1 from Ellis Breen ---
Have seen the same. A quick workaround seems to shortcut is_DebugInfo_active:
>From be6aba76267a1302fb72db8836e83023e4971203 Mon Sep 17 00:00:00 2001
From: Ellis Breen
Date: Tue, 26 Jun 2018 17:32:54 +0100
Subject: [PATCH] 393146: Temporary workaround for Darwin
---
coregrind/m_debuginfo/debuginfo.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/coregrind/m_debuginfo/debuginfo.c
b/coregrind/m_debuginfo/debuginfo.c
index 13991b69a..ab05330b4 100644
--- a/coregrind/m_debuginfo/debuginfo.c
+++ b/coregrind/m_debuginfo/debuginfo.c
@@ -162,6 +162,8 @@ static inline Bool is_DebugInfo_allocated ( const
DebugInfo* di )
// Is this DebugInfo currently "active" (valid for the current epoch) ?
static inline Bool is_DebugInfo_active ( const DebugInfo* di )
{
+// Temporary workaround for 393146
+#ifndef VGO_darwin
if (!is_DiEpoch_INVALID(di->first_epoch)
&& is_DiEpoch_INVALID(di->last_epoch)) {
// Yes it is active. Sanity check ..
@@ -170,6 +172,9 @@ static inline Bool is_DebugInfo_active ( const DebugInfo*
di )
} else {
return False;
}
+#else
+ return True;
+#endif
}
// Is this DebugInfo currently "archived" ?
--
2.17.1
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 395881] Display formatting is broken from last update
https://bugs.kde.org/show_bug.cgi?id=395881 --- Comment #2 from Leon --- Created attachment 113582 --> https://bugs.kde.org/attachment.cgi?id=113582=edit Screen shot of incorrect alignment if window frames Notice the gap at the bottom, this remains in fullscreen mode, are when resizing. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395455] Discover buttons install/remove/launch disappear
https://bugs.kde.org/show_bug.cgi?id=395455 --- Comment #7 from Marco Martin --- Git commit 26b8bdea24c3930533be9abdef6a9202b507d1bc by Marco Martin. Committed on 26/06/2018 at 16:33. Pushed by mart into branch 'master'. Refactor the Global ToolBar concept Summary: The recomended toolbar to be used for kirigami applications used to need to be explicitly instantiated, and had an internal flickable that tried hard to be synchronized with the main PageRow. but this is pretty much impossible to have it glitch-free, it will there always be an edge case in which the two flickables gets out of sync, which is a strong sign of bad architecture. Page toolbars are now moved on top of Page itself, so on the same Flickable as the PageRow itself. (a global header is still used when we are in breadcrumbs mode) Is now also now possible to have multiple instances of PageRows, each one with its own globalToolBar. So, it's now also possible for AbstractApplicationHeader (and any subclass) to trach a different PageRow than the global one in ApplicationWindow. also, there have been requests to be possible while keeping the default toolbar, have a custom global one that goes on top of it (ApplicationWindow's header item) also, i wanted to have a way to make it possible to switch on the fly between a mobile-like and a desktop-like toolbar for further convergence plans in the future, it will be possible for pages to put their own component to replace the default toolbar Test Plan: tested all possible combinations of both the new way and the legacy compatibility mode. ApplicationHeader and ToolBarApplicationHeader still work if used explicitly. The patch shouldn't have significant visible UI changes. there is still an explicit FIXME tough i want to do it in a different turn, as would need a new component Reviewers: #kirigami, ngraham Reviewed By: #kirigami, ngraham Subscribers: apol, IlyaBizyaev, ngraham, davidedmundson, plasma-devel Tags: #kirigami Differential Revision: https://phabricator.kde.org/D13663 M +51 -19 examples/gallerydata/contents/ui/DesktopExampleApp.qml M +48 -14 examples/gallerydata/contents/ui/ExampleApp.qml M +1-1examples/gallerydata/contents/ui/gallery/LayersGallery.qml M +2-2examples/simpleexamples/simpleChatApp.qml M +6-0kirigami.qrc M +15 -3src/controls/AbstractApplicationHeader.qml M +1-0src/controls/ApplicationWindow.qml M +9-1src/controls/OverlayDrawer.qml M +72 -9src/controls/Page.qml M +67 -5src/controls/PageRow.qml M +1-0src/controls/ToolBarApplicationHeader.qml A +42 -0src/controls/private/AbstractPageHeader.qml [License: LGPL (v2+)] A +48 -0src/controls/private/PageRowGlobalToolBarStyleGroup.qml [License: LGPL (v2+)] A +96 -0src/controls/private/PageRowGlobalToolBarUI.qml [License: LGPL (v2+)] M +7-6src/controls/private/PrivateActionToolButton.qml A +47 -0src/controls/private/TitlesPageHeader.qml [License: LGPL (v2+)] A +119 -0src/controls/private/ToolBarPageHeader.qml [License: LGPL (v2+)] M +40 -33 src/controls/templates/AbstractApplicationHeader.qml M +22 -21 src/controls/templates/ApplicationHeader.qml M +17 -11 src/controls/templates/OverlayDrawer.qml M +2-3src/controls/templates/private/BackButton.qml M +2-4src/controls/templates/private/ForwardButton.qml M +3-1src/enums.h M +3-0src/styles/org.kde.desktop/AbstractApplicationHeader.qml M +13 -5src/styles/org.kde.desktop/OverlayDrawer.qml https://commits.kde.org/kirigami/26b8bdea24c3930533be9abdef6a9202b507d1bc -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 386665] Drop dependency on pulseaudio-gconf
https://bugs.kde.org/show_bug.cgi?id=386665 ml changed: What|Removed |Added CC||iivan...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394420] Folder view applet is expanded when in panel
https://bugs.kde.org/show_bug.cgi?id=394420 Andreas Blochberger changed: What|Removed |Added CC||andr...@blochberger.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 --- Comment #10 from Michail Vourlakos --- This issue is totally related to folderview changing from CompactRepresentation to FullRepresentation and vice versa... As mentioned also at https://bugs.kde.org/show_bug.cgi?id=394420 if the user sets a very high panel icon size e.g. 256px it should be solved... -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 395896] Application: Kamoso (kamoso), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1"
https://bugs.kde.org/show_bug.cgi?id=395896 Aleix Pol changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395897] Dolphin starts with blank spaces (empty panels) at bottom and right
https://bugs.kde.org/show_bug.cgi?id=395897 --- Comment #1 from fabrice salvaire --- same workaround with metadata panel. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395874] switch between splited windows by pressing TAB button
https://bugs.kde.org/show_bug.cgi?id=395874 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Julian Schraner --- Luckily, the feature you describe is already implemented :) Go to Settings->General->"Use tab for switching between right and left split view" and check the box next to it. Thanks for reporting your wish & have a nice day! -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 395896] Application: Kamoso (kamoso), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1"
https://bugs.kde.org/show_bug.cgi?id=395896 Shlomi Fish changed: What|Removed |Added CC||shlo...@shlomifish.org --- Comment #1 from Shlomi Fish --- KDE 4.x was end-of-lifed. I cannot reproduce the problem with kamoso-3.2.4 on plasna 5 on mageia v7 x86-64. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395897] New: Dolphin starts with blank spaces (empty panels) at bottom and right
https://bugs.kde.org/show_bug.cgi?id=395897 Bug ID: 395897 Summary: Dolphin starts with blank spaces (empty panels) at bottom and right Product: dolphin Version: 17.12.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: fabrice.salva...@orange.fr CC: elvis.angelac...@kde.org Target Milestone: --- At startup, dolphin shows blank spaces (empty panels) at bottom and right. A workaround is to enable the console panel, to resize it and disable it. Then dolphin refresh to the expected layout. This issue appeared just after an upgrade on Fedora to dolphin-17.12.2-2.fc27.x86_64 -- You are receiving this mail because: You are watching all bug changes.
