[frameworks-kio] [Bug 382459] Exec lines in service files must not have any path prefix on Windows
https://bugs.kde.org/show_bug.cgi?id=382459
--- Comment #2 from Ralf Habacker ---
(In reply to Christophe Giboudeaux from comment #1)
> I don't think these are different issues. This probably has to be fixed
> somewhere in ECM (same thing for bug 382460)
In kio the Exec line needs to be changed to something like
Exec=@NEW_VARIABLE_FOR CROSS_PLATTFORM_LIBEXEC_PATH@kiod5
ECM is responsible to setup these variable according to related platform e.g.
if(WIN32)
set(NEW_VARIABLE_FOR CROSS_PLATTFORM_LIBEXEC_PATH)
else()
set(NEW_VARIABLE_FOR CROSS_PLATTFORM_LIBEXEC_PATH
${KDE_INSTALL_FULL_LIBEXECDIR}/kf5/)
endif()
--
You are receiving this mail because:
You are watching all bug changes.
[kontact] [Bug 382560] New: Kontact crashed during first time start up
https://bugs.kde.org/show_bug.cgi?id=382560 Bug ID: 382560 Summary: Kontact crashed during first time start up Product: kontact Version: 5.4.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@vowleyfarm.co.uk Target Milestone: --- Application: kontact (5.4.3) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.11.10-200.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: Starting Kontact in the morning. The machine is on all the time, but I close down most apps overnight (since many KDE apps seems to experience memory bloat when left on for long periods). This morning I opened Kontact and it crashed before creating a (visible) window. Whilst it was opening I tried to show the autohiding menu bar. This lead to unusual behaviour. - Unusual behavior I noticed: After selecting Kontact to open I moved the mouse pointer down to the bottom of the screen to show the autohide menubar. It didn't fully show, only the top line of it being drawn before Kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f848b8c8940 (LWP 17292))] Thread 31 (Thread 0x7f8382ed0700 (LWP 1673)): #0 0x7f849a8c4809 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f849df7f002 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f849df55a99 in base::PosixDynamicThreadPool::WaitForTask() () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f849df55f85 in base::(anonymous namespace)::WorkerThread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f849df4e9e2 in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f849a8be73a in start_thread () from /lib64/libpthread.so.0 #6 0x7f84a40d5e0f in clone () from /lib64/libc.so.6 Thread 30 (Thread 0x7f8392675700 (LWP 1660)): #0 0x7f84a40c9ecd in poll () from /lib64/libc.so.6 #1 0x7f8495e23166 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f8495e2327c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f84a4ed06eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f84a4e8168a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f84a4cde5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f84a4ce29ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f849a8be73a in start_thread () from /lib64/libpthread.so.0 #8 0x7f84a40d5e0f in clone () from /lib64/libc.so.6 Thread 29 (Thread 0x7f832a177700 (LWP 23827)): #0 0x7ffc74ad5b12 in clock_gettime () #1 0x7f84a40e45a6 in clock_gettime () from /lib64/libc.so.6 #2 0x7f84a4d79b31 in qt_gettime() () from /lib64/libQt5Core.so.5 #3 0x7f84a4eced99 in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #4 0x7f84a4ecf195 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #5 0x7f84a4ed038c in timerSourcePrepareHelper(GTimerSource*, int*) () from /lib64/libQt5Core.so.5 #6 0x7f84a4ed0455 in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #7 0x7f8495e2269d in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #8 0x7f8495e2308b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #9 0x7f8495e2327c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #10 0x7f84a4ed06eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #11 0x7f84a4e8168a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #12 0x7f84a4cde5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #13 0x7f84a4ce29ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #14 0x7f849a8be73a in start_thread () from /lib64/libpthread.so.0 #15 0x7f84a40d5e0f in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7f832a978700 (LWP 23819)): #0 0x7ffc74ad5b12 in clock_gettime () #1 0x7f84a40e45a6 in clock_gettime () from /lib64/libc.so.6 #2 0x7f84a4d79b31 in qt_gettime() () from /lib64/libQt5Core.so.5 #3 0x7f84a4eced99 in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #4 0x7f84a4ecf195 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #5 0x7f84a4ed038c in timerSourcePrepareHelper(GTimerSource*, int*) () from /lib64/libQt5Core.so.5 #6 0x7f84a4ed0455 in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #7 0x7f8495e2269d in g_main
[krita] [Bug 382491] G'mic doesn't work in 3.2 beta
https://bugs.kde.org/show_bug.cgi?id=382491 --- Comment #14 from Boudewijn Rempt --- For the record: On Thursday, 20 July 2017 01:18:20 PDT Boudewijn Rempt wrote: > I just got this bug report: https://bugs.kde.org/show_bug.cgi?id=382491 , > which suggests that QSharedMemory only works if both applications were > built with the same version of Qt. Is that correct? I cannot find anything > about that in http://doc.qt.io/qt-5/qsharedmemory.html You can find it in the changelog, in the "Impotant Behavior Changes" section. http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.9.0#n35 - [QTBUG-60771] Reverted a change that caused Qt 5.6 through 5.8 not to connect to QSystemSemaphore and QSharedMemory created by running applications using Qt earlier than 5.6. Unfortunately, this means that Qt 5.9 will not connect to 5.6-5.8. Also, this is on Windows, where we ship one product, and the gmic team ships another product. Which is only called a plugin-because it used to be gimp-specific, where all plugins are in a separate process. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 382561] New: System Monitor + kernel 4.13 = Shows the wrong processor frequency
https://bugs.kde.org/show_bug.cgi?id=382561 Bug ID: 382561 Summary: System Monitor + kernel 4.13 = Shows the wrong processor frequency Product: ksysguard Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: cerebel...@ukr.net Target Milestone: --- Created attachment 106774 --> https://bugs.kde.org/attachment.cgi?id=106774&action=edit Screenshot with incorrect frequency I updated the kernel and noticed that the frequency shown is incorrect. The reason may be this https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.13-Power-Management "- x86 systems will no longer try to export their current CPU frequency to /proc/cpuinfo. There's also a way to rework how the CPU frequency is exported via sysfs too, using the registers for computing the current frequency rather than relying upon the CPUFreq driver. " -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 382561] System Monitor + kernel 4.13 = Shows the wrong processor frequency
https://bugs.kde.org/show_bug.cgi?id=382561 rооt changed: What|Removed |Added CC||cerebel...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 381207] Allow the use of a solid color as the background instead of a wallpaper
https://bugs.kde.org/show_bug.cgi?id=381207 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 382459] Exec lines in service files must not have any path prefix on Windows
https://bugs.kde.org/show_bug.cgi?id=382459 --- Comment #3 from Ralf Habacker --- https://cgit.kde.org/extra-cmake-modules.git/tree/kde-modules/KDEInstallDirs.cmake#n31 states # ``LIBEXECDIR`` # executables for internal use by programs and libraries (``BINDIR`` on # Windows, ``LIBDIR/libexec`` otherwise) [``LIBEXEC_INSTALL_DIR``] and at https://cgit.kde.org/extra-cmake-modules.git/tree/kde-modules/KDEInstallDirs.cmake#n440 there is defined LIBEXECDIR_KF5 which indicates that the ECM part has been done and that LIBEXECDIR_KF5 need to be used inside kio. -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 382531] dev-util/python2 fails, "Please make sure [Paths] PYTHON27 Points to a valid python installation."
https://bugs.kde.org/show_bug.cgi?id=382531 Kevin Funk changed: What|Removed |Added CC||vonr...@kde.org --- Comment #3 from Kevin Funk --- > I found two kdesettings.ini files, one in C:\KDE\craft and one in C:\KDE\etc. > Which do I need to modify? The one in C:\KDE\etc has a path for "Python" that > points into C:\KDE. You need to modify the one in C:\KDE\etc\. The other one is just a template. > KDE installed Python 3.6 itself, do I need to install Python 2.7 manually? Yes, I think you need to install that by yourself. @Hannah: Or is that not true? > Why did I not receive this error before? It looks like you're attempting to build KDevelop. In craft's master branch, KDevelop just started to depend on the QtWebEngine package, which requires Python2. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 382459] Exec lines in service files must not have any path prefix on Windows
https://bugs.kde.org/show_bug.cgi?id=382459
--- Comment #4 from Ralf Habacker ---
(In reply to Ralf Habacker from comment #3)
> https://cgit.kde.org/extra-cmake-modules.git/tree/kde-modules/KDEInstallDirs.
> cmake#n440 there is used
_define_non_cache(LIBEXECDIR_KF5 "${CMAKE_INSTALL_LIBEXECDIR}/kf5")
which is defined at
https://cgit.kde.org/extra-cmake-modules.git/tree/kde-modules/KDEInstallDirs.cmake#n387
which indicates that for kf5 libexec also KDE_INSTALL_FULL_LIBEXECDIR_KF5 could
be used on non windows. On windows this variable could not be used because it
would have a non empty prefix; instead an empty string or
KDE_INSTALL_LIBEXECDIR_KF5 (which should also be empty) should work
The conclusion is that in the services something like the following should be
used
Exec=@NEW_VARIABLE_FOR CROSS_PLATTFORM_LIBEXEC_PATH@kiod5
and in the top level CMakeLists.txt something like
if(WIN32)
set(NEW_VARIABLE_FOR CROSS_PLATTFORM_LIBEXEC_KF5_PATH )
else()
set(NEW_VARIABLE_FOR CROSS_PLATTFORM_LIBEXEC__KF5_PATH
${KDE_INSTALL_FULL_LIBEXECDIR_KF5})
endif()
or
if(WIN32)
set(NEW_VARIABLE_FOR CROSS_PLATTFORM_LIBEXEC_KF5_PATH
${KDE_INSTALL_LIBEXECDIR_KF5})
else()
set(NEW_VARIABLE_FOR CROSS_PLATTFORM_LIBEXEC__KF5_PATH
${KDE_INSTALL_FULL_LIBEXECDIR_KF5})
endif()
Exec=@SOME_PREFIX@kiod5
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 382435] Incorrect English in message
https://bugs.kde.org/show_bug.cgi?id=382435 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Philippe Waroquiers --- I am not sure to understand what is really wrong in this message, but it is like that since at least 2009 and nobody complained up to now about a difficulty to understand it. As tests are depending on this output, and possibly some users have scripts checking for this string, it looks better to not improve this message, as the cost/benefit seems not that good -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382435] Incorrect English in message
https://bugs.kde.org/show_bug.cgi?id=382435 Philippe Waroquiers changed: What|Removed |Added Resolution|FIXED |WONTFIX -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 382545] Beta259 with a private key ring, where the main key is not in but a special signing subkey.
https://bugs.kde.org/show_bug.cgi?id=382545 marc.arnold.b...@gmail.com changed: What|Removed |Added OS|Linux |MS Windows Platform|Other |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 382545] Beta259 with a private key ring, where the main key is not in but a special signing subkey.
https://bugs.kde.org/show_bug.cgi?id=382545 --- Comment #1 from marc.arnold.b...@gmail.com --- I use 2.3.0-gpg4win-3.0.0-beta259 -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 382545] Beta259 with a private key ring, where the main key is not in but a special signing subkey.
https://bugs.kde.org/show_bug.cgi?id=382545 marc.arnold.b...@gmail.com changed: What|Removed |Added CC||marc.arnold.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 381515] KScreen has problem with multiple monitors with different resolutions
https://bugs.kde.org/show_bug.cgi?id=381515 --- Comment #15 from Sebastian Kügler --- What does xrandr -q report, though? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 381515] KScreen has problem with multiple monitors with different resolutions
https://bugs.kde.org/show_bug.cgi?id=381515 --- Comment #16 from Petr Nehez --- Ahh, I forgot to execute this command. I'll do it next week when I am in the office with Dell, currently I am at home with Eizo. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382562] New: Hidden menu in kmail composer: no (obvious?) way to get it back (or hide it)
https://bugs.kde.org/show_bug.cgi?id=382562 Bug ID: 382562 Summary: Hidden menu in kmail composer: no (obvious?) way to get it back (or hide it) Product: kmail2 Version: 5.5.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: a...@mpe.mpg.de Target Milestone: --- KDE neon user edition: 5.5.3: For whatever reason the menu in the my kmail composer is hidden. Now there no obvious way to get it back: * Crtl-M, or Ctrl--M does not work (shift,alt,super) * No RMB Menu has such an action. * I've created a new user: kmail composer has menu, but I've found no way to hide the menu. I've expected to get a hint how to undo when hidding. Expected Behaviour: * Ctrl-Shift-M hide/shows menu (I guess Ctrl-M is in use by the input/text fields, so ctrl-shift has to be used like in konsole) * A menu item in Settings to show/hide menu like in kmail main window. Achim P.S. in b.k.o kmail version 5.5.3 is not in the list of available versions. Hint hint ;-) P.P.S I assume that menu was hidden when switching the global menu: menu plasmoid, window title and application, I'll file a new report when I can reproduce how to hide the menu -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 378498] Power settings missing scrollbar
https://bugs.kde.org/show_bug.cgi?id=378498 Sebastian Kügler changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||se...@kde.org --- Comment #7 from Sebastian Kügler --- *** This bug has been marked as a duplicate of bug 366299 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 366299] System setting "Energy Saving" window is too large for a standard laptop screen
https://bugs.kde.org/show_bug.cgi?id=366299 Sebastian Kügler changed: What|Removed |Added CC||t...@gmx.com --- Comment #16 from Sebastian Kügler --- *** Bug 378498 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 382558] FOV Indicator
https://bugs.kde.org/show_bug.cgi?id=382558 --- Comment #1 from Jasem Mutlaq --- You need to select Meters instead of Yards/Feet. -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 382550] man pages not created in kaffeine 2.0.12
https://bugs.kde.org/show_bug.cgi?id=382550
Mauro Carvalho Chehab changed:
What|Removed |Added
Summary|man pages not created in|man pages not created in
|2.0.12 |kaffeine 2.0.12
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0 |1
Assignee|mchehab+...@kernel.org |sit...@kde.org
Component|general |general
Product|kaffeine|releaseme
--- Comment #1 from Mauro Carvalho Chehab ---
For 2.0.12 tarball, I started using releaseme. It seems that releaseme
completely replaced Kaffeine's doc/CMakeLists.txt, instead of just appending
translations to it.
The original content of the file is:
kdoctools_create_handbook(index.docbook INSTALL_DESTINATION
${HTML_INSTALL_DIR}/
en SUBDIR kaffeine)
kdoctools_create_manpage (man-kaffeine.1.docbook 1 INSTALL_DESTINATION
${MAN_INS
TALL_DIR})
It got replaced by:
add_subdirectory(ca)
add_subdirectory(pt)
add_subdirectory(en)
add_subdirectory(sv)
add_subdirectory(uk)
add_subdirectory(pt_BR)
add_subdirectory(it)
add_subdirectory(nl)
Additionally, I had to remove a .gitignore file from that dir, as otherwise it
would be creating an add_subdirectory(.gitignore)
--
You are receiving this mail because:
You are watching all bug changes.
[kstars] [Bug 382558] FOV Indicator
https://bugs.kde.org/show_bug.cgi?id=382558 --- Comment #2 from Jean-Claude --- (In reply to Jasem Mutlaq from comment #1) > You need to select Meters instead of Yards/Feet. Of course ! Thank you. Thank you again Jasem (and all others) to bring out this lovely software. I'm playing with it since several days, exploring all its capabilities. To tell the truth I'm trying to get away from TheSkyX that I find clumbsy to master. In fact it is very badly written in comparison of KStars. I made a donation to kde.org and will continue to support the project. Have a nice day. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 382535] Impossible to predefine filters with --getopenfilename
https://bugs.kde.org/show_bug.cgi?id=382535 --- Comment #2 from Christoph Feck --- kdialog --getopenfile /tmp/ "Tar File (*.tar.gz)" is the official glob type syntax and works. I am not sure if your glob without a name and a correct pattern worked because of a bug, or if it was a documented feature. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 381087] Newly ported KF5 .desktop Exec line contains an invalid -caption option preventing ksudoku from launching via the icon menu.
https://bugs.kde.org/show_bug.cgi?id=381087 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com --- Comment #5 from Rex Dieter --- Reverted 17.04 branch commit: https://cgit.kde.org/ksudoku.git/commit/?id=15b9c4686b3adcea3d430bfd66716e95039490d0 -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 382535] Impossible to predefine filters with --getopenfilename
https://bugs.kde.org/show_bug.cgi?id=382535 --- Comment #3 from Nico Dorn --- Thanks for your answer! That works indeed. It used to work without wildcard. But it's correct to presume it's use. So I'd say, this is not a bug, but I would like to propse to add another helpline to kdialog --help, since filters can be used for several functions. Something like that: Arguments: [arg] Arguments - depending on main option [filter] File type filter - usage: "*.xml" or "XML file (*.xml)" -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382562] Hidden menu in kmail composer: no (obvious?) way to get it back (or hide it)
https://bugs.kde.org/show_bug.cgi?id=382562 Allen Winter changed: What|Removed |Added CC||win...@kde.org --- Comment #1 from Allen Winter --- Look in .config/kmail2rc search for the [Composer] section in there you'll probably see the line "MenuBar=Disabled".. remove that line. You'll want to quit Kontact/Kmail first. This happened to me once when I was playing with various Window Manager settings, I believe. I'm not sure if this is a KMail bug or some kind of plasma/WM bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] New: MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 Bug ID: 382563 Summary: MIPS MSA ASE support Product: valgrind Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: tamara.vlaho...@imgtec.com Target Milestone: --- Created attachment 106775 --> https://bugs.kde.org/attachment.cgi?id=106775&action=edit mips_msa_01 - Introduces new Iops in VEX necessary for implementing some MSA V128 operations Next few patches add support for MIPS MSA ASE. This is well tested on MIPS. Also regression tests on X86 were run. mips_msa_01.diff - Introduces new Iops in VEX necessary for implementing some MSA V128 operations: Iop_Scale2_32Fx4, Iop_Scale2_64Fx2, Iop_Log2_32Fx4, Iop_Log2_64Fx2, Iop_F32x4_2toQ16x8, Iop_F64x2_2toQ32x4, Iop_PackOddLanes8x16, Iop_PackEvenLanes8x16, Iop_PackOddLanes16x8, Iop_PackEvenLanes16x8, Iop_PackOddLanes32x4, Iop_PackEvenLanes32x4. mips_msa_02.diff - Adds support for new Iops in Memcheck. mips_msa_03.diff - Is implementation of MSA ASE for VEX. MIPS specific patch which adds support for disassembling of MSA instructions, selection of instructions for implemented (view patch comment) Iops, and generation of MSA instructions. mips_msa_04.diff - MIPS specific detection of MSA ASE (hwcaps, configure, etc). mips_msa_05.diff - MIPS specific. Adds support for guest V128 registers on MIPS in Memcheck mips_msa_06.diff - Adds set of regresion tests for MIPS MSA in none. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 --- Comment #1 from Tamara Vlahovic --- Created attachment 106776 --> https://bugs.kde.org/attachment.cgi?id=106776&action=edit Adds support for new Iops in Memcheck. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 --- Comment #2 from Tamara Vlahovic --- Created attachment 106777 --> https://bugs.kde.org/attachment.cgi?id=106777&action=edit mips_msa_03 - Implementation of MSA ASE for VEX. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 --- Comment #3 from Tamara Vlahovic --- Created attachment 106778 --> https://bugs.kde.org/attachment.cgi?id=106778&action=edit mips_msa_04 - MIPS specific detection of MSA ASE -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 --- Comment #4 from Tamara Vlahovic --- Created attachment 106779 --> https://bugs.kde.org/attachment.cgi?id=106779&action=edit mips_msa_05 - Adds support for guest V128 registers on MIPS in Memcheck -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 --- Comment #5 from Tamara Vlahovic --- Created attachment 106780 --> https://bugs.kde.org/attachment.cgi?id=106780&action=edit mips_msa_06 - MSA regression tests This is zipped patch. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 Tamara Vlahovic changed: What|Removed |Added Attachment #106776|Adds support for new Iops |mips_msa_02 - Adds support description|in Memcheck.|for new Iops in Memcheck. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 Tamara Vlahovic changed: What|Removed |Added CC||mips3...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382551] plasmashell has high cpu usage
https://bugs.kde.org/show_bug.cgi?id=382551 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- High CPU usage could have multiple causes, please see the "see also" fields of the linked report. *** This bug has been marked as a duplicate of bug 378010 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378010] Generic High CPU Usage Rendering
https://bugs.kde.org/show_bug.cgi?id=378010 David Edmundson changed: What|Removed |Added CC||michael.pols...@gmx.net --- Comment #44 from David Edmundson --- *** Bug 382551 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382556] Plasma crashes after modify "Positioning" item at "Configure Desktop" window.
https://bugs.kde.org/show_bug.cgi?id=382556 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 381105 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381105] Crash in uncontrolledAnimationFinished
https://bugs.kde.org/show_bug.cgi?id=381105 David Edmundson changed: What|Removed |Added CC||jhonvalencia...@gmail.com CC||teu.n...@outlook.com --- Comment #19 from David Edmundson --- *** Bug 382556 has been marked as a duplicate of this bug. *** --- Comment #20 from David Edmundson --- *** Bug 382559 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 382473] Breeze style breaks mouse input on Wayland compositors
https://bugs.kde.org/show_bug.cgi?id=382473 --- Comment #18 from Johan Klokkhammer Helsing --- This (qtwayland) patch should fix it: https://codereview.qt-project.org/#/c/200604/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382559] Plasma crash in wallpaper scaling
https://bugs.kde.org/show_bug.cgi?id=382559 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 381105 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381105] Crash in uncontrolledAnimationFinished
https://bugs.kde.org/show_bug.cgi?id=381105 David Edmundson changed: What|Removed |Added CC||jhonvalencia...@gmail.com --- Comment #19 from David Edmundson --- *** Bug 382556 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 380490] Selecting "Encrypt Folder" crashes Kleopatra
https://bugs.kde.org/show_bug.cgi?id=380490 nemeyes changed: What|Removed |Added CC||neme...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382562] Hidden menu in kmail composer: no (obvious?) way to get it back (or hide it)
https://bugs.kde.org/show_bug.cgi?id=382562 --- Comment #2 from Achim Bohnet --- Thx, Allen!! I've my menu back :-) Nevertheless IMHO, that's not 'obvious' for the average desktop/pim user. So a shortcut + menu entry would be very welcome. Thx again Allen and all PIMsters for all your work! Achim -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 380490] Selecting "Encrypt Folder" crashes Kleopatra
https://bugs.kde.org/show_bug.cgi?id=380490 --- Comment #2 from nemeyes --- Right button with mouse on dolphin and kleopatra opened by terminal or 1. Press "Sign/Encrypt Folder" in toolbar or in "File" menu. 2. Choose folder to encrypt. QObject(0x0) QObject(0x0) QObject(0x0) kleopatra: /build/kleopatra-zcOy1_/kleopatra-16.12.3/src/crypto/signencryptfilescontroller.cpp:275: std::shared_ptr getDefaultAd(): asserzione "!ads.empty()" non riuscita. Annullato (core dump creato) -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 382409] Preview pane does not display thunbnails
https://bugs.kde.org/show_bug.cgi?id=382409 --- Comment #1 from Robby Stephenson --- With Tellico 3, the thumbnails will be in the top area. There are buttons to switch between the column view and the icon view, and the lower right will only be for entry details. What sequence did you use to end up with the blank area? At start-up, Tellico should some introduction text there, and then whoever an entry is selected, the info is displayed. But it shouldn't ever go blank, that's definitely not intended. Selecting a group on the left will no longer filter by that group on selection, you have to right-click and "Filter by Group". Does that help? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 382506] Impossible to save an ISO file to an empty folder on Gnome
https://bugs.kde.org/show_bug.cgi?id=382506 Dr. Chapatin changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED --- Comment #9 from Dr. Chapatin --- read the comments from a gnome dev please https://bugzilla.gnome.org/show_bug.cgi?id=785228 reopening because this problem needs to be fixed... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381326] recognize re-convergent fanout before complaining about Uninitialized
https://bugs.kde.org/show_bug.cgi?id=381326 --- Comment #5 from Julian Seward --- (In reply to John Reiser from comment #4) Interesting, but I don't really understand it. What's the underlying insight here? In particular, why is it the case that knowing the two operands are equal allows us to mark the operands as more defined than they were originally? Is this specific to == and !=, or is it more general? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381326] recognize re-convergent fanout before complaining about Uninitialized
https://bugs.kde.org/show_bug.cgi?id=381326 --- Comment #6 from Julian Seward --- In particular I am trying to figure out if this can somehow be used to avoid the problems shown at https://bugs.llvm.org//show_bug.cgi?id=12319 and https://github.com/rust-lang/rust/issues/11710 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow
https://bugs.kde.org/show_bug.cgi?id=381000 --- Comment #70 from David Edmundson --- To summarise: It's clear QSGContext::endSync() isn't being called. It changed when it went from being done once to being up to the rendering engine to do it. This does it afer *all* windows have synced but not one. The change in QSGRenderThreadedLoop.cpp isn't relevant, that's just on the grab, it'll be the change in QSGRenderLoop.cpp I'm gonna need someone who can reliably reproduce this to throw some debug in there and get a list of m_windows after line 309 along with window and also to see if we hit the returns on line 394 and 400. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382564] New: Plasma crashes when closing IntelliJ windows
https://bugs.kde.org/show_bug.cgi?id=382564 Bug ID: 382564 Summary: Plasma crashes when closing IntelliJ windows Product: plasmashell Version: 5.10.1 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: frans.fli...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.1) (Compiled from sources) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.11.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I closed a few IntelliJ IDEA windows and then Plasma crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f85bb1cad80 (LWP 843))] Thread 9 (Thread 0x7f84e838f700 (LWP 13633)): #0 0x7f85af418a29 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f85af3d2a80 in g_main_context_acquire () at /usr/lib/libglib-2.0.so.0 #2 0x7f85af3d3ab5 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f85af3d3d0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f85b5140e9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f85b50e721a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f85b4f0940a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f85b8078645 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f85b4f0dcbd in () at /usr/lib/libQt5Core.so.5 #9 0x7f85b40d6297 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f85b482225f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f84fa6a6700 (LWP 1029)): #0 0x7f85af3d3361 in g_main_context_query () at /usr/lib/libglib-2.0.so.0 #1 0x7f85af3d3b77 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f85af3d3d0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f85b5140e9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f85b50e721a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f85b4f0940a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f84fd04a0a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7f85b4f0dcbd in () at /usr/lib/libQt5Core.so.5 #8 0x7f85b40d6297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f85b482225f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f85055d2700 (LWP 987)): #0 0x7f85b513ede7 in QTimerInfoList::repairTimersIfNeeded() () at /usr/lib/libQt5Core.so.5 #1 0x7f85b513ee63 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #2 0x7f85b514047e in () at /usr/lib/libQt5Core.so.5 #3 0x7f85af3d3138 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #4 0x7f85af3d3b2b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f85af3d3d0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #6 0x7f85b5140e9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f85b50e721a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #8 0x7f85b4f0940a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #9 0x7f85b8c30836 in () at /usr/lib/libQt5Quick.so.5 #10 0x7f85b4f0dcbd in () at /usr/lib/libQt5Core.so.5 #11 0x7f85b40d6297 in start_thread () at /usr/lib/libpthread.so.0 #12 0x7f85b482225f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f8594b78700 (LWP 951)): #0 0x7f85b40dc39d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f85ba94bac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7f85ba94bb09 in () at /usr/lib/libQt5Script.so.5 #3 0x7f85b40d6297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f85b482225f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f8596f72700 (LWP 929)): #0 0x7f85b48182bd in poll () at /usr/lib/libc.so.6 #1 0x7f85af3d3bf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f85af3d3d0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f85b5140e9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f85b50e721a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f85b4f0940a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f85b8078645 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f85b4f0dcbd in () at /usr/lib/libQt5Core.so.5 #8 0x7f85b40d6297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f85b482225f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f859d54e700 (LWP 895)): #0 0x7f85b48182bd in poll () at /usr/lib/libc.so.6 #1 0x7f85af3d3bf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f85af3d3d0c in g_main_context_i
[plasmashell] [Bug 382565] New: plasmashell crashes after Dolphin task finishes
https://bugs.kde.org/show_bug.cgi?id=382565 Bug ID: 382565 Summary: plasmashell crashes after Dolphin task finishes Product: plasmashell Version: 5.10.4 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sefa6...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.4) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.8.0-58-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: I was copying many files via Dolphin. After it finishes plasmashell chrashes. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7fef9d32d8c0 (LWP 3903))] Thread 34 (Thread 0x7fee5a0f9700 (LWP 26944)): #0 0x7fef97134360 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef9828a8eb in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x6fe7df0) at thread/qwaitcondition_unix.cpp:143 #2 0x7fef9828a8eb in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x60d03f8, mutex=mutex@entry=0x60d03f0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fef9b37410d in QSGRenderThread::processEventsAndWaitForMore() (wait=true, this=0x60d03e8) at scenegraph/qsgthreadedrenderloop.cpp:245 #4 0x7fef9b37410d in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x60d0370) at scenegraph/qsgthreadedrenderloop.cpp:701 #5 0x7fef9b374a05 in QSGRenderThread::run() (this=0x60d0370) at scenegraph/qsgthreadedrenderloop.cpp:730 #6 0x7fef98289989 in QThreadPrivate::start(void*) (arg=0x60d0370) at thread/qthread_unix.cpp:368 #7 0x7fef9712e6ba in start_thread (arg=0x7fee5a0f9700) at pthread_create.c:333 #8 0x7fef97b963dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 33 (Thread 0x7fee5bfff700 (LWP 25528)): #0 0x7fef97134360 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef9828a8eb in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x67b6530) at thread/qwaitcondition_unix.cpp:143 #2 0x7fef9828a8eb in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x6fab8f0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7feedcac007f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7feedcac4108 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7feedcabf26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7feedcac4162 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7feedcabf26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7feedcac4162 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7feedcabf26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7feedcac4162 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7feedcabf26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7feedcac4162 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7feedcabf26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7feedcac4162 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x7feedcabf26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x7feedcac4162 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #17 0x7feedcabf26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #18 0x7feedcac4162 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #19 0x7feedcabf26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #20 0x7feedcac4162 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #21 0x7feedcabf26d in ThreadWeaver::Weaver::apply
[plasmashell] [Bug 382565] plasmashell crashes after Dolphin task finishes
https://bugs.kde.org/show_bug.cgi?id=382565 Sefa Eyeoglu changed: What|Removed |Added Platform|unspecified |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow
https://bugs.kde.org/show_bug.cgi?id=381000 --- Comment #71 from gilaldpella...@gmail.com --- (In reply to David Edmundson from comment #70) > To summarise: > > It's clear QSGContext::endSync() isn't being called. > > It changed when it went from being done once to being up to the rendering > engine to do it. This does it afer *all* windows have synced but not one. > > The change in QSGRenderThreadedLoop.cpp isn't relevant, that's just on the > grab, it'll be the change in QSGRenderLoop.cpp > > I'm gonna need someone who can reliably reproduce this to throw some debug > in there and get a list of m_windows after line 309 along with window and > also to see if we hit the returns on line 394 and 400. Please count me in. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #9 from Nate Graham --- Nikos, I understand that you're frustrated, but please refrain from using sarcasm and insults. That's a sure way to get people to ignore you, even when you're right. Martin, I feel that you're being a bit inflexible here. If this feature is behaving as expected, then the expectation is incorrect. Activating a feature should not break another feature and require a user-initiated manual workaround to restore the broken functionality. The user should not need to understand the implementation in order to have a working Application Launcher with focus stealing prevention set to High or above. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kunitconversion] [Bug 379171] [PATCH] MPa and PSI aren't marked as common units
https://bugs.kde.org/show_bug.cgi?id=379171 --- Comment #8 from Nate Graham --- Thanks. Here you go: https://phabricator.kde.org/D6808 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382491] G'mic doesn't work in 3.2 beta
https://bugs.kde.org/show_bug.cgi?id=382491 --- Comment #15 from Alvin Wong --- (In reply to Boudewijn Rempt from comment #14) > For the record: > > On Thursday, 20 July 2017 01:18:20 PDT Boudewijn Rempt wrote: > > I just got this bug report: https://bugs.kde.org/show_bug.cgi?id=382491 , > > which suggests that QSharedMemory only works if both applications were > > built with the same version of Qt. Is that correct? I cannot find anything > > about that in http://doc.qt.io/qt-5/qsharedmemory.html > > You can find it in the changelog, in the "Impotant Behavior Changes" section. > http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.9.0#n35 > > - [QTBUG-60771] Reverted a change that caused Qt 5.6 through 5.8 not to >connect to QSystemSemaphore and QSharedMemory created by running >applications using Qt earlier than 5.6. Unfortunately, this means that Qt >5.9 will not connect to 5.6-5.8. This appears to affect only Linux and Mac, so let's not mix the two issues here. Considering the Windows situation, the timestamps between Krita sending a message and gmic-qt responding "gmic-qt: empty answer!" or "gmic-qt: Got the wrong answer!" are 2 seconds apart, which just so happens to match the timeout specified: https://github.com/c-koi/gmic-qt/blob/8e4511256c0b420f33252356d4741034044423ae/src/host_krita.cpp#L105 This could indicate that the QLocalSocket isn't flushing normally. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 343061] Yakuake creates task list entry when being opened
https://bugs.kde.org/show_bug.cgi?id=343061 Floreal changed: What|Removed |Added CC||floreal@flo-art.fr --- Comment #8 from Floreal --- Still present on KDE Neon User edition with plasma 5.10.4. Will this bug be solved? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 382566] New: Webengine does not support ad blocking, neither visualize man/info pages
https://bugs.kde.org/show_bug.cgi?id=382566 Bug ID: 382566 Summary: Webengine does not support ad blocking, neither visualize man/info pages Product: konqueror Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: webenginepart Assignee: konq-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- Enabling ad blocking in konqueror does nothing when using webengine Also, one cannot visualize man and info pages in webengine Both work in khtml, so I guess some porting is needed. I use up-to-date KDE neon User Edition. Konqueror 4:17.04.3, kf5 5.36 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382491] G'mic doesn't work in 3.2 beta
https://bugs.kde.org/show_bug.cgi?id=382491 Alvin Wong changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/cc105d5cf1eaa69432e240ac ||1f30c18bb72a0b27 --- Comment #16 from Alvin Wong --- Git commit cc105d5cf1eaa69432e240ac1f30c18bb72a0b27 by Alvin Wong. Committed on 21/07/2017 at 13:27. Pushed by alvinwong into branch 'krita/3.2'. Flush QLocalSocket in QMic plugin M +2-0plugins/extensions/qmic/QMic.cpp https://commits.kde.org/krita/cc105d5cf1eaa69432e240ac1f30c18bb72a0b27 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382491] G'mic doesn't work in 3.2 beta
https://bugs.kde.org/show_bug.cgi?id=382491 Alvin Wong changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/cc105d5cf1eaa69432e240ac |ta/ec23492455fb32a1cbc5ba1d |1f30c18bb72a0b27|a43e57826d086062 --- Comment #17 from Alvin Wong --- Git commit ec23492455fb32a1cbc5ba1da43e57826d086062 by Alvin Wong. Committed on 21/07/2017 at 13:26. Pushed by alvinwong into branch 'master'. Flush QLocalSocket in QMic plugin M +2-0plugins/extensions/qmic/QMic.cpp https://commits.kde.org/krita/ec23492455fb32a1cbc5ba1da43e57826d086062 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 382566] Webengine does not support ad blocking, neither visualize man/info pages
https://bugs.kde.org/show_bug.cgi?id=382566 林博仁 changed: What|Removed |Added CC||buo.ren@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 372777] no kwallet integration in 16.12
https://bugs.kde.org/show_bug.cgi?id=372777 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #6 from avlas --- Mmm, is it still possible to use qtwebkit mode in ported konqueror to kf5? I thought it was disabled but some comments here point to it... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 382567] New: konqueror package should recommend or suggest konq-tools
https://bugs.kde.org/show_bug.cgi?id=382567 Bug ID: 382567 Summary: konqueror package should recommend or suggest konq-tools Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: vdragon.tai...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Konqueror only provides "Performance" and "Bookmark" tabs in setting interface without konq-tools installed, yet `konqueror` package doesn't even suggest it. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 382506] Impossible to save an ISO file to an empty folder on Gnome
https://bugs.kde.org/show_bug.cgi?id=382506 Ernestas Kulik changed: What|Removed |Added CC||ernestas.ku...@gmail.com --- Comment #10 from Ernestas Kulik --- https://api.kde.org/frameworks/kio/html/classKUrlRequester.html#ad3ad89008d0ea59335d7495084a57fe9 The default seems to be AcceptOpen. Setting it to the correct value here https://github.com/KDE/k3b/blob/503b9d1583095408f41fc8e45540c19603a251ce/src/k3btempdirselectionwidget.cpp#L71 might do the trick. I would build and test locally, but I’m not exactly familiar with the platform. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 379346] webengine part can not activate fullscreen video on youtube
https://bugs.kde.org/show_bug.cgi?id=379346 avlas changed: What|Removed |Added CC||jsar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #10 from Martin Flöser --- For your information I forwarded this bug to the KDE community working group. You can reopen the bug as often as you won't, but I'm out of here. This bug won't be fixed because I won't do it and after this experience here I would even veto a bug fix. Well done! -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 372777] no kwallet integration in 16.12
https://bugs.kde.org/show_bug.cgi?id=372777 --- Comment #7 from Wolfgang Bauer --- (In reply to avlas from comment #6) > Mmm, is it still possible to use qtwebkit mode in ported konqueror to kf5? I > thought it was disabled but some comments here point to it... "qtwebkit mode" in Konqueror is (and always was) provided by a separate package named kwebkitpart. It has been ported to KF5/Qt5, the source code is here: https://cgit.kde.org/kwebkitpart.git/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #11 from Nate Graham --- Let's not let our tempers get in the way of creating incredible software for the world. We've all got the same goals here! -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 372777] no kwallet integration in 16.12
https://bugs.kde.org/show_bug.cgi?id=372777 --- Comment #8 from avlas --- Awesome! Unfortunately it is not part of KDE neon User edition (as far as I can see), I guess this explains why the mode disappeared when I installed Konqueror's kf5 version... I'll ask Jonathan Riddell whether he can package it... Thanks -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 382520] Many file types are recognized as Bitbake
https://bugs.kde.org/show_bug.cgi?id=382520 --- Comment #1 from Guo Yunhe --- See patch https://phabricator.kde.org/D6810 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 382567] konqueror package should recommend or suggest konq-tools
https://bugs.kde.org/show_bug.cgi?id=382567 --- Comment #1 from Ｖ字龍(Vdragon) --- Current konqueror package's dependency info: ``` Package: konqueror Version: 4:17.04.3-0neon+16.04+xenial+build18 Depends: Recommends: kfind Breaks: ``` While the same package in ubuntu archive: ``` Package: konqueror Version: 4:15.12.3-0ubuntu1 Depends: Recommends: dolphin4, kfind, konqueror-nsplugins (= 4:15.12.3-0ubuntu1), kpart-webkit Suggests: konq-plugins (>= 4:4.1~) Breaks: Replaces: ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379866] Sped-up animations on nVidia system
https://bugs.kde.org/show_bug.cgi?id=379866 --- Comment #9 from Fang He --- Sorry that I switched to Intel graphics card due to hot summer, and I switched to i3wm as well. I can not test your solutions right now. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 382506] Impossible to save an ISO file to an empty folder on Gnome
https://bugs.kde.org/show_bug.cgi?id=382506 --- Comment #11 from Leslie Zhai --- Hi Ernestas, Thanks for your hint! I will try it. Regards, Leslie Zhai -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382568] New: gmic-qt freezes randomly (deadlock)
https://bugs.kde.org/show_bug.cgi?id=382568 Bug ID: 382568 Summary: gmic-qt freezes randomly (deadlock) Product: krita Version: git master Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: G'Mic for Krita Assignee: krita-bugs-n...@kde.org Reporter: alvinhoc...@gmail.com Target Milestone: --- Created attachment 106781 --> https://bugs.kde.org/attachment.cgi?id=106781&action=edit DebugView output Krita: Thread 1: 1 ntdll!ZwDelayExecution 0x779ec07a 2 SleepEx 0x7fefd9e1203 3 QWindowsPipeReader::waitForPipeClosed qwindowspipereader.cpp 356 0x7feacf4b93f 4 QLocalSocket::waitForDisconnected qlocalsocket_win.cpp 408 0x7fe6cb5b285 5 QMic::connected QMic.cpp 297 0x7fe269688b8 ... gmic-krita-qt-2.0.3_pre-win64 (no debug symbols): Thread 1: 1 ntdll!ZwDelayExecution 0x779ec07a 2 SleepEx 0x7fefd9e1203 3 QWindowsPipeReader::waitForNotification(int) 0x66892356 4 QWindowsPipeReader::waitForReadyRead(int) 0x66892435 5 QLocalSocket::waitForReadyRead(int) 0x6d2adaf3 6 ?? 0x40988c 7 ?? 0x40b55d 8 ?? 0x478e86 9 ?? 0x47e321 10 QWidget::event(QEvent *) 0x17bcff8 11 QApplicationPrivate::notify_helper(QObject *, QEvent *) 0x1777f9c 12 QApplication::notify(QObject *, QEvent *) 0x177eefc 13 QCoreApplication::notifyInternal2(QObject *, QEvent *) 0x668cb812 14 QWidgetPrivate::sendPaintEvent(QRegion const&) 0x17b561d ... Judging from the time it takes to call `QLocalSocket::waitForReadyRead` (1 second), the deadlock probably happens here (unless the code has changed after the release): https://github.com/c-koi/gmic-qt/blob/8e4511256c0b420f33252356d4741034044423ae/src/host_krita.cpp#L92 Attached the DebugView output. "QLocalSocket::waitForDisconnected() is not allowed in UnconnectedState " appears rather frequently, it might be related. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 376664] Bridged connections are not visible in the applet
https://bugs.kde.org/show_bug.cgi?id=376664 buzzurro changed: What|Removed |Added CC||eur0nym...@hotmail.it --- Comment #15 from buzzurro --- It is frustrating to see again "WONTFIX". In our office, for example, the primary connection is delivered by vlan. For us it is not a choice. in this case a major feature are broken. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382568] gmic-qt freezes randomly (deadlock)
https://bugs.kde.org/show_bug.cgi?id=382568 --- Comment #1 from Alvin Wong --- An additional note, my Krita is compiled with Qt 5.9.1 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 382569] New: Konqueror webengine: middle-click of a file link fails to embed the file in the new tab
https://bugs.kde.org/show_bug.cgi?id=382569 Bug ID: 382569 Summary: Konqueror webengine: middle-click of a file link fails to embed the file in the new tab Product: konqueror Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: webenginepart Assignee: konq-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- Middle click in links that point to, e.g., pdf files, opens a tab but fails to show the preview of the file in it. Right click on the link to select embedded preview in current tab does work though. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 382570] New: No option to delete bookmarks
https://bugs.kde.org/show_bug.cgi?id=382570 Bug ID: 382570 Summary: No option to delete bookmarks Product: khelpcenter Version: 5.10.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: svadk...@gmail.com Target Milestone: --- The only way to delete bookmarks is to edit config file. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 Martin Flöser changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #12 from Martin Flöser --- I'm going to finally reset the status again and I'm urging to not change it again. In exchange I'm going to explain in more detail. First of all let's have a look at what the help provides: "New windows get activated only if no window is currently active or if they belong to the currently active application. This setting is probably not really usable when not using mouse focus policy." We can see here that the help already restricts the usefulness of this setting. Now let's look at it from a pure window manager perspective: The panel is not the active application, in fact the panel is marked to never gain focus. When clicking the app launcher a new window opens. It's a window just like any other window. The window manager does not know that it is an app launcher. We currently have a window activated and it's not Plasma, so the window won't get focus and won't activate. Which in turn results in the app launcher closing directly as it closes when losing focus. As I said in a previous comment: this works exactly as advertised! This is obviously an advance feature where we expect users to have knowledge about it. I'm now going to quote KWin's mission statement: "KWin is an easy to use, but flexible, composited Window Manger for Xorg windowing systems on Linux. Its primary usage is in conjunction with a Desktop Shell (e.g. KDE Plasma Desktop). KWin is designed to go out of the way; users should not notice that they use a window manager at all. Nevertheless KWin provides a steep learning curve for advanced features, which are available, if they do not conflict with the primary mission. KWin does not have a dedicated targeted user group, but follows the targeted user group of the Desktop Shell using KWin as it's Window Manager. " This setting is an advanced feature, we expect the user to have an understanding of the feature when using it. We expect the user to understand that this feature does not work with other elements in a perfect way - this is even documented! Now I understand that this is all fine, but when using a desktop this should work. But for the desktop it's the same. Our tagline is "simple by default, powerful when needed". By default all of this is working, the app launcher opens, it gets focus. But Plasma let's you adjust the window manager, you can set an advanced feature giving you the powerful when needed. Things might not work as expected, but again Plasma gives you the features to help yourself. With a simple window rule you can fine tune that the app launcher gets focus. It is powerful when needed! So is this here a bug? From KWin perspective: no, everything works as expected. Fixing it without breaking the focus stealing prevention is nearly impossible. >From an overall system perspective: maybe, but we are in the advanced feature section and there is a good and simple workaround. So overall this is a clear worksforme. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 382264] Black buttons unreadable on the black logout screen
https://bugs.kde.org/show_bug.cgi?id=382264 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382571] New: Icon pinned to task mnanaher shows wide tooltip
https://bugs.kde.org/show_bug.cgi?id=382571 Bug ID: 382571 Summary: Icon pinned to task mnanaher shows wide tooltip Product: plasmashell Version: 5.10.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: yy...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 106782 --> https://bugs.kde.org/attachment.cgi?id=106782&action=edit wide tooltip pin any icon to your task manager restart your plasma session mouseover your pinned icon See my screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382571] Icon pinned to task manager shows wide tooltip
https://bugs.kde.org/show_bug.cgi?id=382571 Dr. Chapatin changed: What|Removed |Added Summary|Icon pinned to task |Icon pinned to task manager |mnanaher shows wide tooltip |shows wide tooltip -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382571] Icon pinned to task mnanaher shows wide tooltip
https://bugs.kde.org/show_bug.cgi?id=382571 Dr. Chapatin changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382571] Icon pinned to task manager shows wide tooltip
https://bugs.kde.org/show_bug.cgi?id=382571 Eike Hein changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Eike Hein --- *** This bug has been marked as a duplicate of bug 380432 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380432] Icons pinned to task manager have huge tooltip
https://bugs.kde.org/show_bug.cgi?id=380432 --- Comment #9 from Eike Hein --- *** Bug 382571 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382568] gmic-qt freezes randomly (deadlock)
https://bugs.kde.org/show_bug.cgi?id=382568 --- Comment #2 from Alvin Wong --- Git commit eaa459e3c28951ef3b280271d8f370a848f92e16 by Alvin Wong. Committed on 21/07/2017 at 16:17. Pushed by alvinwong into branch 'krita/3.2'. Do not wait indefinitely for socket in QMic plugin This works around a possible lockups with gmic-qt. Instead of waiting for the socket forever, it should only freeze for a aximum of 8 seconds. M +14 -5plugins/extensions/qmic/QMic.cpp https://commits.kde.org/krita/eaa459e3c28951ef3b280271d8f370a848f92e16 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382568] gmic-qt freezes randomly (deadlock)
https://bugs.kde.org/show_bug.cgi?id=382568 --- Comment #3 from Alvin Wong --- Git commit 2c9c9cb2709f700d195bd0cfffd939f4a61b69e0 by Alvin Wong. Committed on 21/07/2017 at 16:16. Pushed by alvinwong into branch 'master'. Do not wait indefinitely for socket in QMic plugin This works around a possible lockups with gmic-qt. Instead of waiting for the socket forever, it should only freeze for a aximum of 8 seconds. M +12 -3plugins/extensions/qmic/QMic.cpp https://commits.kde.org/krita/2c9c9cb2709f700d195bd0cfffd939f4a61b69e0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382568] gmic-qt freezes randomly (deadlock)
https://bugs.kde.org/show_bug.cgi?id=382568 --- Comment #4 from Alvin Wong --- I made some changes to stop the lockups, but it just hides the actual bug, gmic-qt will sometimes not able to receive the image data properly and cause other errors. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 382520] Many file types are recognized as Bitbake
https://bugs.kde.org/show_bug.cgi?id=382520 Dominik Haumann changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://cgit.kde.org/syntax ||-highlighting.git/commit/?i ||d=354bbd21677ac709b7f52cc34 ||da483e Version Fixed In||5.37 --- Comment #2 from Dominik Haumann --- This was just fixed by Guo, see https://phabricator.kde.org/D6810. Thanks for the fix, Guo! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382571] Icon pinned to task manager shows wide tooltip
https://bugs.kde.org/show_bug.cgi?id=382571 --- Comment #2 from Dr. Chapatin --- this report is not a duplicate or 380432 is not fixed in plasma 5.10.4. The problem reported here happens on Arch running plasma 5.10.4. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 368897] VHDL syntax highlighting error
https://bugs.kde.org/show_bug.cgi?id=368897 Dominik Haumann changed: What|Removed |Added CC||chiggs...@gmail.com, ||j...@mueschelsoft.de, ||ro...@purdue.edu, ||ste...@endrullis.de --- Comment #2 from Dominik Haumann --- Add original authors to CC. Could you please look into this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382571] Icon pinned to task manager shows wide tooltip
https://bugs.kde.org/show_bug.cgi?id=382571 --- Comment #4 from Eike Hein --- I guess the icon's now right but the dialog sizing code wasn't adjusted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382571] Icon pinned to task manager shows wide tooltip
https://bugs.kde.org/show_bug.cgi?id=382571 Eike Hein changed: What|Removed |Added Resolution|DUPLICATE |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from Eike Hein --- True, thanks for catching. Kai? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 382341] Target Url not updated after renaming a desktop file in folder mode
https://bugs.kde.org/show_bug.cgi?id=382341 --- Comment #4 from David Faure --- Confirmed; thanks for the debugging. The thing is, shortly after KCoreDirLister::slotFileRenamed is called, desktopnotifier also triggers a full re-listing via KDirNotify::FilesAdded which calls KCoreDirLister::updateDirectory. That's when the dirlister should notice that the target URL of the item has changed. But it failed to do so because KFileItem::cmp() ignores UDS_LOCAL_PATH and UDS_TARGET_URL. Adding that fixes the bug. I'll work on a unittest and then commit that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 Valorie Zimmerman changed: What|Removed |Added CC||valorie.zimmer...@gmail.com --- Comment #13 from Valorie Zimmerman --- A reminder of our Code of Conduct [1], which states: "Be respectful In order for the KDE community to stay healthy its members must feel comfortable and accepted. Treating one another with respect is absolutely necessary for this. In a disagreement, in the first instance assume that people mean well." I would ask that all participants in what has become a debate: step back, reconsider, and in some days if necessary, think together about how to deal with this issue. Valorie, for the Community Working Group 1. https://www.kde.org/code-of-conduct/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running
https://bugs.kde.org/show_bug.cgi?id=382444 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382555] curved lines come out angular and jagged
https://bugs.kde.org/show_bug.cgi?id=382555 Alvin Wong changed: What|Removed |Added CC||alvinhoc...@gmail.com --- Comment #1 from Alvin Wong --- What operating system are you on and what smoothing options did you have enabled? Which tablet are you using? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 373713] [PATCH] JavaScript Syntax Highlighting broken when using E4X
https://bugs.kde.org/show_bug.cgi?id=373713 Dominik Haumann changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.37 Latest Commit||https://commits.kde.org/syn ||tax-highlighting/11a804b4f5 ||bb347ddb1d06bfa21a6d2eaff01 ||83a Status|UNCONFIRMED |RESOLVED --- Comment #3 from Dominik Haumann --- Git commit 11a804b4f5bb347ddb1d06bfa21a6d2eaff0183a by Dominik Haumann. Committed on 21/07/2017 at 17:32. Pushed by dhaumann into branch 'master'. JavaScript Highlighting: Add support for E4X xml extension Thanks to Andreas Schwier for the patch. FIXED-IN: 5.37 M +5-0autotests/folding/highlight.js.fold M +5-0autotests/html/highlight.js.html M +5-0autotests/input/highlight.js M +5-0autotests/reference/highlight.js.ref M +4-1data/syntax/javascript.xml https://commits.kde.org/syntax-highlighting/11a804b4f5bb347ddb1d06bfa21a6d2eaff0183a -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 381396] Add support for fish shell highlighting
https://bugs.kde.org/show_bug.cgi?id=381396 Dominik Haumann changed: What|Removed |Added Summary|fish shell highlighting |Add support for fish shell ||highlighting --- Comment #1 from Dominik Haumann --- It would be helpful, if you could provide a highlighting file. -- You are receiving this mail because: You are watching all bug changes.
