[digikam] [Bug 389046] Face suggestions disappair each time i confirm one
https://bugs.kde.org/show_bug.cgi?id=389046 --- Comment #9 from Maik Qualmann --- I can not reproduce the problem. Can you please post your metadata settings or a screenshot of it. Do you use sidecar, if so, also the exact settings. Maik -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828
--- Comment #15 from Julian Seward ---
Hmm, ignore my previous suggestion. What's evident from the
failure message is that
1. t13 is declared to be an I32
2. however, it is assigned an I64 value, as created by ReinterpF64asI64,
which is why the sanity check failed
3. it is then used as an I32 value: 32HLto64(t13,t13).
So (1) and (3) are consistent but (2) isn't.
+ t8:V128 t9:F64 t10:F64 t11:I32 t12:I32 t13:I32 t14:I64
+ t13 =
ReinterpF64asI64(RoundF64toF32(Xor32(t11,And32(Shl32(t11,0x:I8),0x:I32)),DivF64(Xor32(t11,And32(Shl32(t11,0x:I8),0x:I32)),F64i{0x},t9)))
+ PUT(784) = 64HLtoV128(ReinterpF64asI64(32HLto64(t13,t13)),0x:I64)
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 406170] New: There are two actions (New Tab, New Tab) that want to use the same shortcut.
https://bugs.kde.org/show_bug.cgi?id=406170 Bug ID: 406170 Summary: There are two actions (New Tab, New Tab) that want to use the same shortcut. Product: dolphin Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: charleshi...@earthlink.net CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY There are two actions (New Tab, New Tab) that want to use the same shortcut. STEPS TO REPRODUCE 1. In Mate, clink on the menu link that has always previously opened Dolphin. OBSERVED RESULT Dialog box with the message: There are two actions (New Tab, New Tab) that want to use the same shortcut (Ctrl+T). This is most probably a bug. Please report it in bugs.kde.org EXPECTED RESULT Dolphin should open a window into my home directory. SOFTWARE/OS VERSIONS Debian testing update all as of 2019/04/02 (N.B.: My Window manager is Mate.) Linux/KDE Plasma (available in About System) KDE Plasma Version: 5:100 (from synaptic) KDE Frameworks Version: 5.54.0-1 (from synaptic) Qt Version: 4:4.8.7+dfsg-17+b1 and 5.11.3 ADDITIONAL INFORMATION libvirt is throwning errors during the update/upgrade process unfortunately, I can't copy the errors over from konsole, as I can't figure out how to copy text. But it starts off: Setting up libvirt-daemon-system (5.0.0-1) ... virtlockd.service is a disabled or a static unit, not starting it. Job for virtlogd-admin.socket failed. See "systemctl status virtlogd-admin.socket" and "journalctl -xe" for details A dependency job for virtlogd.service failed. See 'journalctl -xe' for details. invoke-rc.d: initscript virtlogd, action "start" failed. @ virtlogd.service - Virtual machine log manager And it keeps on going for about 9 more lines that don't tell me much of anything useful. But this as if it might tie in with the dolphin error message when I try to open another window "Unable to create io-slave. klauncher said: Error loading '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'." -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828
--- Comment #14 from Julian Seward ---
(In reply to Mark Wielaard from comment #13)
> > +t13 =
> > ReinterpF64asI64(RoundF64toF32(Xor32(t11,And32(Shl32(t11,0x:I8),0x...
> > .:I32)),DivF64(Xor32(t11,And32(Shl32(t11,0x:I8),0x:I32)),
> > F64i{0x},t9)))
> + t8:V128 t9:F64 t10:F64 t11:I32 t12:I32 t13:I32 t14:I64
> So t13 has type I32, but ReinterpF64asI64 returns an I64.
>
> I think you had wanted to use Iop_ReinterpF32asI32.
RoundF64toF32 has a bit of a misleading name. The result type is still F64,
but the value itself is rounded to F32 range:
typeOfPrimop(..) contains:
case Iop_RoundF64toF32:
BINARY(ity_RMode,Ity_F64, Ity_F64);
So I think in this case, t13 (is that the two-be-used-twice value?) needs
to be an I64. That is, be initialised with newTemp(Ity_I64).
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 405005] Disappearing menu (edited)
https://bugs.kde.org/show_bug.cgi?id=405005 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405618] Ist nach 10h zeichnen beim zwischen speichern abgestürzt die ganzen 10 h arbeit wurden nicht gespeichert.
https://bugs.kde.org/show_bug.cgi?id=405618 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405052] sieve editor can't be opened
https://bugs.kde.org/show_bug.cgi?id=405052 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 405603] Local Collection does't scan files with special characters or accents (latin)
https://bugs.kde.org/show_bug.cgi?id=405603 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406169] New: Network Manager crash when disconnecting from USB modem
https://bugs.kde.org/show_bug.cgi?id=406169 Bug ID: 406169 Summary: Network Manager crash when disconnecting from USB modem Product: plasmashell Version: 5.15.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: isirase...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.15.3) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 5.0.5-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I disconnected from my USB 3G modem when a dialog appeared stating that a crash had occurred. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f66e4d40880 (LWP 700))] Thread 16 (Thread 0x7f667b273700 (LWP 14496)): #0 0x7f66e8de4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66e9ae6c4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f66e9ae6d3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f66eb83691d in () at /usr/lib/libQt5Quick.so.5 #4 0x7f66eb836b8c in () at /usr/lib/libQt5Quick.so.5 #5 0x7f66e9ae096c in () at /usr/lib/libQt5Core.so.5 #6 0x7f66e8ddea9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f66e97cab23 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f66b49c3700 (LWP 2710)): #0 0x7f66e8de4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66e9ae6c4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f66e9ae6d3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f66eb83691d in () at /usr/lib/libQt5Quick.so.5 #4 0x7f66eb836b8c in () at /usr/lib/libQt5Quick.so.5 #5 0x7f66e9ae096c in () at /usr/lib/libQt5Core.so.5 #6 0x7f66e8ddea9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f66e97cab23 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f66b52ad700 (LWP 2685)): #0 0x7f66e8de4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66e9ae6c4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f66e9ae6d3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f66eb83691d in () at /usr/lib/libQt5Quick.so.5 #4 0x7f66eb836b8c in () at /usr/lib/libQt5Quick.so.5 #5 0x7f66e9ae096c in () at /usr/lib/libQt5Core.so.5 #6 0x7f66e8ddea9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f66e97cab23 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f66b5b68700 (LWP 1690)): #0 0x7f66e97bfc21 in poll () at /usr/lib/libc.so.6 #1 0x7f66d0111673 in () at /usr/lib/libpulse.so.0 #2 0x7f66d0102990 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7f66d0102fe0 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f66d0103091 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f66d01115ae in () at /usr/lib/libpulse.so.0 #6 0x7f66c3bcd9fc in () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #7 0x7f66e8ddea9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f66e97cab23 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f66b73fe700 (LWP 909)): #0 0x7f66e8de4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66e9ae6c4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f66e9ae6d3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f66eb83691d in () at /usr/lib/libQt5Quick.so.5 #4 0x7f66eb836b8c in () at /usr/lib/libQt5Quick.so.5 #5 0x7f66e9ae096c in () at /usr/lib/libQt5Core.so.5 #6 0x7f66e8ddea9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f66e97cab23 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f66b63fc700 (LWP 887)): [KCrash Handler] #6 0x7f66eb800e10 in QSGSimpleTextureNode::texture() const () at /usr/lib/libQt5Quick.so.5 #7 0x7f66d1aa6055 in () at /usr/lib/qt/qml/org/kde/kquickcontrolsaddons/libkquickcontrolsaddonsplugin.so #8 0x7f66e9cc7980 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #9 0x7f66eb88ba03 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7f66eb832d90 in () at /usr/lib/libQt5Quick.so.5 #11 0x7f66eb836b48 in () at /usr/lib/libQt5Quick.so.5 #12
[kdenlive] [Bug 406102] Can't open or save projects
https://bugs.kde.org/show_bug.cgi?id=406102 --- Comment #4 from hardcorebu...@yahoo.com --- Sorry, but your assumption is not correct. I did NOT enable MOVIT, and I don't think this has anything at all to do with OpenGL. When referring to hardware acceleration, I am referring explicitly to the encoding part only (for proxy files and/or the final output). Not to effects, transitions, etc. (which I recognize are CPU driven, unfortunately). Custom encoding profiles pass flags to ffmpeg. With the right flags, ffmpeg will use hardware acceleration to create proxy video files & exported video files. And I have verified this works properly when ffmpeg 4.x is used in Kdenlive. But (again, to clarify), using ffmpeg 4.x does not work in the current AppImage version, which is packaged with ffmpeg 3.3.4--and manually specifying an ffmpeg path results in an error. But even without custom encoding profiles, the Open / Save dialogs (for the overall project) do not pop up in the FlatPak version. This means that I cannot open or save any projects in FlatPak Kdenlive. And I cannot use hardware acceleration for proxy file & export file rendering in AppImage Kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406164] control screen magnify- and invert-effect in lock-screen
https://bugs.kde.org/show_bug.cgi?id=406164 Martin Flöser changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405831] Crash with audio clips in Kdenlive Win 19.04beta-git2019
https://bugs.kde.org/show_bug.cgi?id=405831 --- Comment #17 from Justin Irwin --- For me it only crashes on audio and no matter how many subsequent attempts I make, it always crashes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405920] Display is blurry after waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=405920 --- Comment #6 from techxga...@outlook.com --- After enabling Flipping, the blurry stuff happens much less frequently, but it happens a lot more frequently compared to 5.14. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404855] Crash and visual update issue with transform tool
https://bugs.kde.org/show_bug.cgi?id=404855 --- Comment #6 from Quiralta --- Just an update, the krita I build locally still shows the same behavior as described in my last comment. The Appimage though (4.2.0-pre-alpha (git 6448150)) works just fine even without a clean setup (keeping the .local/krita folder as is). I guess whatever Arch has newer than the appimage makes the difference, maybe qt? If you guys need me to do something else just let me know. :) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 406168] New: Crash when clicking on KDevelop while during startup
https://bugs.kde.org/show_bug.cgi?id=406168 Bug ID: 406168 Summary: Crash when clicking on KDevelop while during startup Product: kdevelop Version: 5.3.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: arca...@ivanov.biz Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.11.3 Frameworks Version: 5.55.0 Operating System: Linux 5.0.4-200.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: - What I was doing when the application crashed: I launched KDevelop. The application appeared in the panel, but the main windows was still not visible. I clicked on the app in the panel and KDevelop immediately crashed. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f76b8bc2980 (LWP 10169))] Thread 4 (Thread 0x7f76aa14f700 (LWP 10172)): #0 0x7f76c0aaa421 in poll () from /lib64/libc.so.6 #1 0x7f76bd6fb3a6 in ?? () from /lib64/libglib-2.0.so.0 #2 0x7f76bd6fb4d0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f76c11595ab in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f76c1107e0b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f76c0f6fe86 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f76c1b82f89 in ?? () from /lib64/libQt5DBus.so.5 #7 0x7f76c0f792fb in ?? () from /lib64/libQt5Core.so.5 #8 0x7f76bfecd58e in start_thread () from /lib64/libpthread.so.0 #9 0x7f76c0ab56a3 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f76aaf38700 (LWP 10171)): #0 0x7f76c0aaa421 in poll () from /lib64/libc.so.6 #1 0x7f76ba78239f in ?? () from /lib64/libxcb.so.1 #2 0x7f76ba78401a in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f76b825dbf9 in ?? () from /lib64/libQt5XcbQpa.so.5 #4 0x7f76c0f792fb in ?? () from /lib64/libQt5Core.so.5 #5 0x7f76bfecd58e in start_thread () from /lib64/libpthread.so.0 #6 0x7f76c0ab56a3 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f76b8bbc700 (LWP 10170)): #0 0x7f76bfed373c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f76c0ddc6f0 in std::condition_variable::wait(std::unique_lock&) () from /lib64/libstdc++.so.6 #2 0x7f76bcb2397a in ?? () from /lib64/libQt5WebKit.so.5 #3 0x7f76bcb23aaf in ?? () from /lib64/libQt5WebKit.so.5 #4 0x7f76c0de29a3 in ?? () from /lib64/libstdc++.so.6 #5 0x7f76bfecd58e in start_thread () from /lib64/libpthread.so.0 #6 0x7f76c0ab56a3 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f76b8bc2980 (LWP 10169)): [KCrash Handler] #6 0x7f76c09f053f in raise () from /lib64/libc.so.6 #7 0x7f76c09da895 in abort () from /lib64/libc.so.6 #8 0x7f76c3942011 in KDevelop::ItemRepositoryRegistry::registerRepository (this=0x55d1279449b0, repository=repository@entry=0x7f76c449b868 , manager=0x0) at /usr/src/debug/kdevelop-5.3.2-1.fc29.x86_64/kdevplatform/serialization/itemrepositoryregistry.cpp:208 #9 0x7f76c3be9043 in KDevelop::ItemRepository::ItemRepository (manager=0x0, repositoryVersion=1, registry=0x55d1279449b0, repositoryName=..., this=0x7f76c449b868 ) at /usr/include/bits/string_fortified.h:71 #10 Utils::SetDataRepository::SetDataRepository (registry=0x55d1279449b0, name=..., _setRepository=0x7f76c449b860 , this=0x7f76c449b868 ) at /usr/src/debug/kdevelop-5.3.2-1.fc29.x86_64/kdevplatform/language/util/basicsetrepository.h:176 #11 Utils::BasicSetRepository::BasicSetRepository (this=0x7f76c449b860 , name=..., registry=0x55d1279449b0, delayedDeletion=) at /usr/src/debug/kdevelop-5.3.2-1.fc29.x86_64/kdevplatform/language/util/setrepository.cpp:900 #12 0x7f76c3ad955c in KDevelop::RecursiveImportRepository::repository () at /usr/src/debug/kdevelop-5.3.2-1.fc29.x86_64/kdevplatform/language/duchain/topducontext.cpp:51 #13 KDevelop::RecursiveImportRepository::repository () at /usr/src/debug/kdevelop-5.3.2-1.fc29.x86_64/kdevplatform/language/duchain/topducontext.cpp:50 #14 0x7f76c3aabc0a in KDevelop::DUChain::initialize () at /usr/src/debug/kdevelop-5.3.2-1.fc29.x86_64/kdevplatform/language/duchain/duchain.cpp:1161 #15 0x7f76c4b5546f in KDevelop::CorePrivate::initialize (this=0x55d1274fd400, mode=KDevelop::Core::Default, session=...) at /usr/src/debug/kdevelop-5.3.2-1.fc29.x86_64/kdevplatform/shell/core.cpp:237 #16 0x7f76c4b569cd in KDevelop::Core::initialize (mode=KDevelop::Core::Default, session=...) at /usr/src/debug/kdevelop-5.3.2-1.fc29.x86_64/kdevplatform/shell/core.cpp:339 #17 0x55d126fc9652 in main (argc=, argv=) at
[plasmashell] [Bug 399864] Folder view crashes when moving file from popup views into parent view
https://bugs.kde.org/show_bug.cgi?id=399864 rantovich changed: What|Removed |Added CC||rantow...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406167] New: Show all messages in mbox
https://bugs.kde.org/show_bug.cgi?id=406167 Bug ID: 406167 Summary: Show all messages in mbox Product: kmail2 Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: jsc...@posteo.net Target Milestone: --- I find it handy to download mbox files with multiple messages, mostly for the sake of working with Debian's BTS. Opening an mbox for a bug shows "The file contains multiple messages. Only the first message is shown." It would be nice to see the other messages inside. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406131] Loan balance reused when changing loan settings
https://bugs.kde.org/show_bug.cgi?id=406131 --- Comment #4 from lp.allar...@gmail.com --- Seems like I wasn't doing anything wrong but I asked because 5 years ago I did renew my mortgage term (so did exactly the same as Im trying to do now) and somehow I made it work back then, but again, I didnt manually reduce the remaining payments left (amortization). I wonder, if KMM is not meant to handle this kind of situation, why in the "Edit Account > Modify Other loan information" KMM let me change the number of payments? Is it assumed that the number entered there is the number of payments from inception to full payoff? If so, this is incoherent. The loan has obviously been processed to an extent, so KMM should detect this and there on assume this is from NOW until full payment. Now the real question is: if I create a new schedule to simulate what the loan wizard would normally do, how will KMM compute interests and interest payments and properly calculate residual balance of the loan? If I create a manual schedule, and lets say enter $300 as payment on the capital, and $80 of interests, this will be the same from first payment until the last, which is NOT the case with an interest loan. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 406166] New: taskbar icons always show on all desktops for Qt5.9.1 based application windows
https://bugs.kde.org/show_bug.cgi?id=406166 Bug ID: 406166 Summary: taskbar icons always show on all desktops for Qt5.9.1 based application windows Product: kde Version: unspecified Platform: OpenBSD Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: p...@cadence.com Target Milestone: --- SUMMARY On SLES11 SP4 system running KDE 4.3.5 window icons for applications based on Qt 5.9.1 appear on the taskbar for all desktops even though both "Only show tasks from the current desktop" and "Only show tasks from the current screen" are selected in the Task Manager Settings. This does not occur with a RedHat 6 system running KDE 4.3.4 running the same Qt 5.9.1 based application. Note that in both cases KDE is running in a VNC server. On the SuSE system I noticed that when remote displaying to the VNC session from another display, the problem did not occur. I compared the environment variables from both terminal session and noted that the VNC terminal session defined VNCDESKTOP with a value of "X". If I "unsetenv VNCDESKTOP" (I'm using csh) and start the application then the problem no longer occurs and the window icons only show in the taskbar of the same desktop they are in. Doing "setenv VNCDESKTOP X" restored the wrong behavior. This is a critical issue because our software is being blamed for this by our customers, even though we do not set anything that I can determine would cause this. Note that thie problem does not occur on RedHat Linux, only on SuSE Linux (SLES). Also, note that unsetting an environment variable that I assume should have no effect on how taskbar icons are displayed changes how they are displayed. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: SLES 11 SP4 (available in About System) KDE Plasma Version: 4.3.5 KDE Frameworks Version: Qt Version: 5.9.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828
--- Comment #13 from Mark Wielaard ---
(In reply to Will Schmidt from comment #12)
> Created attachment 119219 [details]
> vex : sanityCheckFail: exiting due to bad IR
>
> I got this error when regression testing this patch on a P8 BE system.
> Probably obvious, but I don't immediately understand what this is telling
> me. (I'll look more tomorrow)
>
> +IN STATEMENT:
> +
> +t13 =
> ReinterpF64asI64(RoundF64toF32(Xor32(t11,And32(Shl32(t11,0x:I8),0x...
> .:I32)),DivF64(Xor32(t11,And32(Shl32(t11,0x:I8),0x:I32)),
> F64i{0x},t9)))
> +
> +ERROR = IRStmt.Put.Tmp: tmp and expr do not match
See just before:
+IR SANITY CHECK FAILURE
+
+IRSB {
+ t0:I64 t1:I64 t2:I64 t3:I64 t4:I64 t5:I64 t6:I64 t7:V128
+ t8:V128 t9:F64 t10:F64 t11:I32 t12:I32 t13:I32 t14:I64
t15:I64
+ t16:I64 t17:V128 t18:I64 t19:I64 t20:I64 t21:I32 t22:I32
t23:I32
+ t24:I64 t25:I32 t26:I32 t27:I32
So t13 has type I32, but ReinterpF64asI64 returns an I64.
I think you had wanted to use Iop_ReinterpF32asI32.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828
--- Comment #12 from Will Schmidt ---
Created attachment 119219
--> https://bugs.kde.org/attachment.cgi?id=119219=edit
vex : sanityCheckFail: exiting due to bad IR
I got this error when regression testing this patch on a P8 BE system.
Probably obvious, but I don't immediately understand what this is telling me.
(I'll look more tomorrow)
+IN STATEMENT:
+
+t13 =
ReinterpF64asI64(RoundF64toF32(Xor32(t11,And32(Shl32(t11,0x:I8),0x:I32)),DivF64(Xor32(t11,And32(Shl32(t11,0x:I8),0x:I32)),F64i{0x},t9)))
+
+ERROR = IRStmt.Put.Tmp: tmp and expr do not match
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828 Will Schmidt changed: What|Removed |Added Attachment #119203|0 |1 is obsolete|| --- Comment #11 from Will Schmidt --- Created attachment 119218 --> https://bugs.kde.org/attachment.cgi?id=119218=edit proposed patch (v3) reworked per feedback. (thanks). possibly one more spin after this. see subsequent comment/attachment. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 331646] Files are damaged and lost when rotating on full disk
https://bugs.kde.org/show_bug.cgi?id=331646 Skála changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||skala.vacla...@seznam.cz --- Comment #3 from Skála --- I confirm this bug is not in actual version. When rotating and saving on full disk you will get error message "Unknown error" and in error output in console is written "libpng error: Write Error" but original image is left intact. I think we can close this bug as RESOLVED. SOFTWARE/OS VERSIONS Gwenview: 18.12.2 Linux/KDE Plasma: Fedora 29 KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.55.0 Qt Version: 5.11.3 Advice when testing this bug Better then filling your disk is making some small file. Then format it to some filesystem, mount this file it to some folder, add image to this folder and than fill this image using dd if=/dev/zero of=fill.txt -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #53 from caulier.gil...@gmail.com --- Nicofo, This is the contents of my /etc/pky under Mageia 7 beta 2 : [gilles@localhost etc]$ tree /etc/pki /etc/pki ├── java │ └── cacerts ├── nssdb │ ├── cert8.db │ ├── key3.db │ └── secmod.db ├── rpm-gpg │ └── RPM-GPG-KEY-Mageia └── tls ├── cert.pem -> certs/ca-bundle.crt ├── certs │ ├── ca-bundle.crt │ ├── httpd.pem │ ├── Makefile │ └── postfix.pem ├── misc ├── mozilla │ └── certdata.txt ├── openssl.cnf ├── private │ ├── httpd.pem │ └── postfix.pem └── rootcerts ├── 02265526.0 -> entrust-root-certification-authority-01.pem ├── 03179a64.0 -> staat-der-nederlanden-ev-root-ca.pem ├── 062cdee6.0 -> globalsign-01.pem ├── 064e0aa9.0 -> quovadis-root-ca-2-g3.pem ├── 06dc52d5.0 -> ssl-com-ev-root-certification-authority-00.pem ├── 080911ac.0 -> quovadis-root-certification-authority.pem ├── 09789157.0 -> starfield-services-root-certificate.pem ├── 0a775a30.0 -> gts-root-r3.pem ├── 0b1b94ef.0 -> cfca-ev-root.pem ├── 0b7c536a.0 -> d-trust-root-ca-3-2013.pem ├── 0bf05006.0 -> ssl-com-root-certification-authority-01.pem ├── 0c4c9b6c.0 -> global-chambersign-root-2008.pem ├── 0f5dc4f3.0 -> uca-extended-validation-root.pem ├── 0f6fa695.0 -> gdca-trustauth-r5-root.pem ├── 1001acf7.0 -> gts-root-r1.pem ├── 106f3e4d.0 -> entrust-root-certification-authority-02.pem ├── 116bf586.0 -> geotrust-primary-certification-02.pem ├── 128805a3.0 -> ee-certification-centre-root-ca.pem ├── 1320b215.0 -> symantec-class-2-public-primary-00.pem ├── 14bc7599.0 -> emsign-ecc-root-ca-g3.pem ├── 157753a5.0 -> addtrust-external-ca-root.pem ├── 1636090b.0 -> hellenic-academic-and-research-00.pem ├── 18856ac4.0 -> securesign-rootca11.pem ├── 1d3472b9.0 -> globalsign-03.pem ├── 1e08bfd1.0 -> identrust-public-sector-root-ca.pem ├── 1e09d511.0 -> t-telesec-globalroot-class-2.pem ├── 244b5494.0 -> digicert-high-assurance-ev-root.pem ├── 26312675.0 -> symantec-class-1-public-primary-00.pem ├── 2923b3f9.0 -> emsign-root-ca-g1.pem ├── 2ae6433e.0 -> ca-disig-root-r2.pem ├── 2b349938.0 -> affirmtrust-commercial.pem ├── 2c543cd1.0 -> geotrust-global-ca.pem ├── 2e4eed3c.0 -> thawte-primary-root-ca.pem ├── 2e5ac55d.0 -> dst-root-ca-x3.pem ├── 32888f65.0 -> hellenic-academic-and-research-01.pem ├── 349f2832.0 -> ec-acc.pem ├── 3513523f.0 -> digicert-global-root-ca.pem ├── 3bde41ac.0 -> autoridad-de-certificacion-firmaprofesional.pem ├── 3e44d2f7.0 -> trustcor-rootcert-ca-2.pem ├── 3e45d192.0 -> hongkong-post-root-ca-1.pem ├── 3efd4dc0.0 -> swisscom-root-ca-2.pem ├── 40193066.0 -> certum-trusted-network-ca-2.pem ├── 4042bcee.0 -> isrg-root-x1.pem ├── 40547a79.0 -> comodo-certification-authority.pem ├── 406c9bb1.0 -> emsign-root-ca-c1.pem ├── 4304c5e5.0 -> network-solutions-certificate-authority.pem ├── 442adcac.0 -> certum-ca.pem ├── 46f053f0.0 -> diginotar-root-ca.pem ├── 480720ec.0 -> geotrust-primary-certification-00.pem ├── 48bec511.0 -> certum-trusted-network-ca.pem ├── 4a6481c9.0 -> globalsign-00.pem ├── 4b718d9b.0 -> emsign-ecc-root-ca-c3.pem ├── 4bfab552.0 -> starfield-root-certificate-authority.pem ├── 4d4ba017.0 -> symantec-class-2-public-primary-01.pem ├── 4f316efb.0 -> swisssign-gold-ca-g2.pem ├── 5273a94c.0 -> e-tugra-certification-authority.pem ├── 5443e9e3.0 -> t-telesec-globalroot-class-3.pem ├── 54657681.0 -> buypass-class-2-root-ca.pem ├── 57bcb2da.0 -> swisssign-silver-ca-g2.pem ├── 5a4d6896.0 -> staat-der-nederlanden-root-ca-g3.pem ├── 5ad8a5d6.0 -> globalsign-root-ca.pem ├── 5c44d531.0 -> staat-der-nederlanden-root-ca-g2.pem ├── 5cd81ad7.0 -> teliasonera-root-ca-v1.pem ├── 5d3033c5.0 -> trustcor-rootcert-ca-1.pem ├── 5f15c80c.0 -> twca-global-root-ca.pem ├── 607986c7.0 -> digicert-global-root-g2.pem ├── 626dceaf.0 -> gts-root-r2.pem ├── 62744ee1.0 -> symantec-class-1-public-primary-01.pem ├── 6410666e.0 -> government-root-certification-authority.pem ├── 653b494a.0 -> baltimore-cybertrust-root.pem ├── 68dd7389.0 -> hongkong-post-root-ca-3.pem ├── 6b99d060.0 -> entrust-root-certification-authority-00.pem ├── 6d41d539.0 -> amazon-root-ca-2.pem ├── 6fa5da56.0 -> ssl-com-root-certification-authority-00.pem ├── 706f604c.0 -> xramp-global-certification-authority.pem ├── 749e9e03.0 -> quovadis-root-ca-1-g3.pem ├── 75d1b2ed.0 -> digicert-trusted-root-g4.pem ├──
[systemsettings] [Bug 386748] Some icons are missing in tooltips
https://bugs.kde.org/show_bug.cgi?id=386748 --- Comment #20 from Patrick Silva --- Created attachment 119217 --> https://bugs.kde.org/attachment.cgi?id=119217=edit icon view, plasma 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377857] Ideas to improve usability of metadata sidebar
https://bugs.kde.org/show_bug.cgi?id=377857 --- Comment #15 from caulier.gil...@gmail.com --- Thanks Jens, I will take a look when time permit. Actually i'm busy to finalize 6.1.0 release planed for newt week end : all bundles must be perfect... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 406165] New: KOrganizer crashed
https://bugs.kde.org/show_bug.cgi?id=406165 Bug ID: 406165 Summary: KOrganizer crashed Product: korganizer Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: reinhardau...@gmx.at Target Milestone: --- Application: korganizer (5.10.3) Qt Version: 5.9.7 Frameworks Version: 5.55.0 Operating System: Linux 5.0.5-lp151.23-default x86_64 Distribution: "openSUSE Leap 15.1Beta" -- Information about the crash: - What I was doing when the application crashed: I was using KOrganizer and trying to add a new appointment, when, suddenly, KOrganizer crashed. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fb2f1de9940 (LWP 314))] Thread 9 (Thread 0x7fb2ae73f700 (LWP 407)): #0 0x7fb2e50258ad in futex_wait_cancelable (private=, expected=0, futex_word=0x7fb2de370fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fb2de370f68, cond=0x7fb2de370f90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fb2de370f90, mutex=0x7fb2de370f68) at pthread_cond_wait.c:655 #3 0x7fb2de07b574 in ?? () from /usr/lib64/libQt5Script.so.5 #4 0x7fb2de07b5b9 in ?? () from /usr/lib64/libQt5Script.so.5 #5 0x7fb2e501f569 in start_thread (arg=0x7fb2ae73f700) at pthread_create.c:465 #6 0x7fb2ed5389af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fb2bb93f700 (LWP 401)): #0 0x7fb2c0318b17 in pa_srbchannel_read () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #1 0x7fb2c03150c0 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #2 0x7fb2c0317dbb in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #3 0x7fb2c0318159 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #4 0x7fb2c03189df in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #5 0x7fb2c057e4e8 in pa_mainloop_dispatch () from /usr/lib64/libpulse.so.0 #6 0x7fb2c057e8be in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #7 0x7fb2c057e940 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #8 0x7fb2c058c7a9 in ?? () from /usr/lib64/libpulse.so.0 #9 0x7fb2c0328428 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #10 0x7fb2e501f569 in start_thread (arg=0x7fb2bb93f700) at pthread_create.c:465 #11 0x7fb2ed5389af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fb2c375f700 (LWP 350)): #0 0x7fb2e50258ad in futex_wait_cancelable (private=, expected=0, futex_word=0x55a2650827a8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55a265082758, cond=0x55a265082780) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55a265082780, mutex=0x55a265082758) at pthread_cond_wait.c:655 #3 0x7fb2c8e6088b in ?? () from /usr/lib64/dri/r600_dri.so #4 0x7fb2c8e60597 in ?? () from /usr/lib64/dri/r600_dri.so #5 0x7fb2e501f569 in start_thread (arg=0x7fb2c375f700) at pthread_create.c:465 #6 0x7fb2ed5389af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fb2c40df700 (LWP 349)): #0 0x7fb2e50258ad in futex_wait_cancelable (private=, expected=0, futex_word=0x55a265081c14) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55a265081bc0, cond=0x55a265081be8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55a265081be8, mutex=0x55a265081bc0) at pthread_cond_wait.c:655 #3 0x7fb2c8e6088b in ?? () from /usr/lib64/dri/r600_dri.so #4 0x7fb2c8e60597 in ?? () from /usr/lib64/dri/r600_dri.so #5 0x7fb2e501f569 in start_thread (arg=0x7fb2c40df700) at pthread_create.c:465 #6 0x7fb2ed5389af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fb2d01ff700 (LWP 330)): #0 0x7fb2e318bfd9 in g_mutex_lock (mutex=mutex@entry=0x55a264a47950) at gthread-posix.c:1336 #1 0x7fb2e31451d4 in g_main_context_release (context=0x55a264a47950) at gmain.c:3242 #2 0x7fb2e3146166 in g_main_context_iterate (context=context@entry=0x55a264a47950, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3870 #3 0x7fb2e31462bc in g_main_context_iteration (context=0x55a264a47950, may_block=may_block@entry=1) at gmain.c:3929 #4 0x7fb2ee09796b in QEventDispatcherGlib::processEvents (this=0x55a264ad2590, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fb2ee03c90a in QEventLoop::exec (this=this@entry=0x7fb2d01fec70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7fb2ede5adaa in
[digikam] [Bug 192020] Tool to export as plasma backgrounds
https://bugs.kde.org/show_bug.cgi?id=192020 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||6.1.0 Latest Commit||https://commits.kde.org/dig ||ikam/51aeb061222513cfb3cda5 ||2fb80084e04ba5da8f Resolution|DUPLICATE |FIXED --- Comment #2 from caulier.gil...@gmail.com --- Git commit 51aeb061222513cfb3cda52fb80084e04ba5da8f by Gilles Caulier. Committed on 02/04/2019 at 21:26. Pushed by cgilles into branch 'master'. add new plugin from Igor Antropov to set image as linux desktop wall paper. FIXED-IN: 6.1.0 Related: bug 254932 M +4-1NEWS M +4-0core/dplugins/generic/tools/CMakeLists.txt A +26 -0core/dplugins/generic/tools/wallpaper/CMakeLists.txt A +138 -0core/dplugins/generic/tools/wallpaper/wallpaperplugin.cpp [License: GPL (v2+)] A +64 -0core/dplugins/generic/tools/wallpaper/wallpaperplugin.h [License: GPL (v2+)] https://commits.kde.org/digikam/51aeb061222513cfb3cda52fb80084e04ba5da8f -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 254932] New tool to export images as desktop wallpaper folder [patch]
https://bugs.kde.org/show_bug.cgi?id=254932 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||6.1.0 Latest Commit||https://commits.kde.org/dig ||ikam/51aeb061222513cfb3cda5 ||2fb80084e04ba5da8f Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from caulier.gil...@gmail.com --- Git commit 51aeb061222513cfb3cda52fb80084e04ba5da8f by Gilles Caulier. Committed on 02/04/2019 at 21:26. Pushed by cgilles into branch 'master'. add new plugin from Igor Antropov to set image as linux desktop wall paper. FIXED-IN: 6.1.0 Related: bug 192020 M +4-1NEWS M +4-0core/dplugins/generic/tools/CMakeLists.txt A +26 -0core/dplugins/generic/tools/wallpaper/CMakeLists.txt A +138 -0core/dplugins/generic/tools/wallpaper/wallpaperplugin.cpp [License: GPL (v2+)] A +64 -0core/dplugins/generic/tools/wallpaper/wallpaperplugin.h [License: GPL (v2+)] https://commits.kde.org/digikam/51aeb061222513cfb3cda52fb80084e04ba5da8f -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 405941] Spacing in worksheet is distorted
https://bugs.kde.org/show_bug.cgi?id=405941 Nikita Sirgienko changed: What|Removed |Added Latest Commit||https://commits.kde.org/can ||tor/de92516d91b13c595e0e383 ||78a2ba391b66a052b Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||19.04 --- Comment #2 from Nikita Sirgienko --- Git commit de92516d91b13c595e0e38378a2ba391b66a052b by Nikita Sirgienko. Committed on 02/04/2019 at 21:07. Pushed by sirgienko into branch 'Applications/19.04'. Fix bug with merging consecutive spaces FIXED-IN: 19.04 M +1-0src/lib/textresult.cpp https://commits.kde.org/cantor/de92516d91b13c595e0e38378a2ba391b66a052b -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 360821] Gimp 2.10 xcf files cannot be loaded
https://bugs.kde.org/show_bug.cgi?id=360821 --- Comment #39 from Christoph Feck --- Packages depend on the ImageMagick binary, not the libraries. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 360821] Gimp 2.10 xcf files cannot be loaded
https://bugs.kde.org/show_bug.cgi?id=360821 --- Comment #38 from Boudewijn Rempt --- Either they don't care, or they have the manpower to follow the api changes, or whatever. I'm not here to argue with you: I give you the benefit of my experience with ImageMagick, but if you want to come up with a patch that rewrites kimageformats to use ImageMagick, well, we'll see. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 254932] New tool to export images as desktop wallpaper folder [patch]
https://bugs.kde.org/show_bug.cgi?id=254932 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 254932] New tool to export images as desktop wallpaper folder [patch]
https://bugs.kde.org/show_bug.cgi?id=254932 caulier.gil...@gmail.com changed: What|Removed |Added Summary|New tool to export images |New tool to export images |as desktop wallpaper folder |as desktop wallpaper folder ||[patch] -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 254932] New tool to export images as desktop wallpaper folder
https://bugs.kde.org/show_bug.cgi?id=254932 Igor Antropov changed: What|Removed |Added CC||antrop...@yahoo.com --- Comment #5 from Igor Antropov --- Created attachment 119216 --> https://bugs.kde.org/attachment.cgi?id=119216=edit Patch with plugin to export img as wallpaper I made a simple plugin to set selected image as wallpaper. It is located in Tools->Export as wallpaper. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406101] Window "Keep above" overrides "Show Desktop"
https://bugs.kde.org/show_bug.cgi?id=406101 Vlad Zagorodniy changed: What|Removed |Added Latest Commit||https://commits.kde.org/kwi ||n/1e2a0028c3151cb38f252baa7 ||8a5f22b8cd7c7e6 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from Vlad Zagorodniy --- Git commit 1e2a0028c3151cb38f252baa78a5f22b8cd7c7e6 by Vlad Zagorodniy. Committed on 02/04/2019 at 20:44. Pushed by vladz into branch 'master'. Move keep-above clients to the Normal layer when showing desktop Summary: Implementation of the Show Desktop feature moves desktop windows to the Above layer, but it doesn't take into account existing clients that belong to the Above layer. If there are any, we have to move them to a layer below (e.g. normal), otherwise those clients will be visible when showing the desktop. Reviewers: #kwin, graesslin Reviewed By: #kwin, graesslin Subscribers: graesslin, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D20153 M +1-1abstract_client.cpp M +3-1workspace.cpp https://commits.kde.org/kwin/1e2a0028c3151cb38f252baa78a5f22b8cd7c7e6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 360821] Gimp 2.10 xcf files cannot be loaded
https://bugs.kde.org/show_bug.cgi?id=360821 --- Comment #37 from maderios --- (In reply to Boudewijn Rempt from comment #35) > The ImageMagick API's are very unstable: there is no guarantee of source > compatibility between versions. In this case, why 91 softwares (see Arch IM page) depend on ImageMagick? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 --- Comment #17 from Osvaldo Painequeo --- Y tiene solución, no soy programador pero trato de entender lo mas que puedo. Saludos. El mar., 2 abr. 2019 a las 13:19, Christoph Feck () escribió: > https://bugs.kde.org/show_bug.cgi?id=400010 > > Christoph Feck changed: > >What|Removed |Added > > > CC||josepaineq...@gmail.com > > --- Comment #16 from Christoph Feck --- > *** Bug 406046 has been marked as a duplicate of this bug. *** > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386748] Some icons are missing in tooltips
https://bugs.kde.org/show_bug.cgi?id=386748 --- Comment #19 from Nate Graham --- New screenshot please. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405494] Problems with Qt's Windows Ink implementation
https://bugs.kde.org/show_bug.cgi?id=405494 Boudewijn Rempt changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #17 from Boudewijn Rempt --- Note: for some reason the top part of the rocker switch gets redefined to double-click when you switch the wacom driver to windows ink. It can be sett to middle-click, and then panning works again. -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 402091] clock no works with freechess.org
https://bugs.kde.org/show_bug.cgi?id=402091 Alexander Semke changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386748] Some icons are missing in tooltips
https://bugs.kde.org/show_bug.cgi?id=386748 Patrick Silva changed: What|Removed |Added Version|5.15.3 |5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386748] Some icons are missing in tooltips
https://bugs.kde.org/show_bug.cgi?id=386748 Patrick Silva changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #18 from Patrick Silva --- bug persists when icon view is used. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405454] Desktop names don't appear in the pager applet, only "..."
https://bugs.kde.org/show_bug.cgi?id=405454 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||bugsefor...@gmx.com --- Comment #5 from Patrick Silva --- Fixed in plasma 5.15.4. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377857] Ideas to improve usability of metadata sidebar
https://bugs.kde.org/show_bug.cgi?id=377857 --- Comment #14 from Jens --- How about this idea, any chances of implementing it in Digikam 6.x? I am here to help designing, I just need some help with the code. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 406144] HTML Export theme names/descriptions are not translatable
https://bugs.kde.org/show_bug.cgi?id=406144 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||johan...@zarl-zierl.at --- Comment #1 from Johannes Zarl-Zierl --- For others following along: the relevant code is in the function HTMLDialog::populateThemesCombo(). I have to admit that localization is not an area where I have too much expertise, just immense gratitude to the translators who make the magic happen… So bear with me if I'm asking stupid questions. I guess wrapping the strings that we read from the theme files with i18n() calls won't be sufficient to fix this. How can I feed text from non-source files into the translation workflow? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406164] New: control screen magnify- and invert-effect in lock-screen
https://bugs.kde.org/show_bug.cgi?id=406164 Bug ID: 406164 Summary: control screen magnify- and invert-effect in lock-screen Product: kwin Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: private_l...@yahoo.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. enable magnify effect and enlarge screen 2. wait for screensaver or press shortcut to lock screen 3. The assigned shortcuts cannot control magnification OBSERVED RESULT Lockscreen is also magnified EXPECTED RESULT reset magnify level to standard or allow control of magnification SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: 4.18.0-16 (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Invert effect of whole screen will invert lockscreen too. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405802] Export metadata to csv file
https://bugs.kde.org/show_bug.cgi?id=405802 --- Comment #20 from Maurizio --- The solution proposed in: https://github.com/paulhurleyuk/DigikamR which uses R to perform operations on the database is very interesting. I installed R and the various libraries needed. Unfortunately the example refers to the old version of the Digikam database. Entering the command lines will result in several errors of objects not found in the database. Unfortunately I don't know where to put my hands. Do you have any ideas? Thank you -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406163] New: Qt 5.12.2 - Test failure - DolphinMainWindowTest::testNewFileMenuEnabled(home)
https://bugs.kde.org/show_bug.cgi?id=406163 Bug ID: 406163 Summary: Qt 5.12.2 - Test failure - DolphinMainWindowTest::testNewFileMenuEnabled(home) Product: dolphin Version: 18.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rikmi...@kubuntu.org CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY With Qt 5.12.2 the DolphinMainWindowTest::testNewFileMenuEnabled(home) test fails with: FAIL! : DolphinMainWindowTest::testNewFileMenuEnabled(home) Compared values are not the same Actual (newFileMenu->isEnabled()): 0 Expected (expectedEnabled) : 1 Loc: [/tmp/autopkgtest.AlAChC/build.UlA/src/src/tests/dolphinmainwindowtest.cpp(250)] http://autopkgtest.ubuntu.com/packages/d/dolphin/disco/amd64 Linux: Ubuntu 19.04 KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56 Qt Version: 5.12.2 Testing on an actual system, the menu does have the correct enabled/disabled status in home/root/trash, so fail is incorrect. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405831] Crash with audio clips in Kdenlive Win 19.04beta-git2019
https://bugs.kde.org/show_bug.cgi?id=405831 --- Comment #16 from emohr --- I can reproduce the crash on Win10 and Win7. If you start Kdenlive the first time and add a file (audio or video) Kdenlive crashes. To reproduce it: Win+r -> appdata -> local -> delete the “Kdenlive” folder and the “Kdenliverc” & “KDE…” file. Start Kdenlive import or drag/drop an audio or video file -> crash. If you start Kdenlive after the crash I can import audio or video files. Thank you reporting this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405943] Crash when saving file with vector layer. (Only with an ASAN build)
https://bugs.kde.org/show_bug.cgi?id=405943 wolthera changed: What|Removed |Added Summary|Crash when saving file with |Crash when saving file with |vector layer. |vector layer. (Only with an ||ASAN build) --- Comment #3 from wolthera --- So, this only seems to happen with a build with an address sanitizer enabled, but it does not give an address sanitizer backtrace? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405494] Problems with Qt's Windows Ink implementation
https://bugs.kde.org/show_bug.cgi?id=405494 --- Comment #16 from Boudewijn Rempt --- Build https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/511/ properly disabled our own wintab/winink implementation and enables Qt's implementation. On the Yoga 920 with wacom that only supports windows pointer api, everything works as expected: pressure, eraser barrel button, right-click barrel button. On the Wacom Mobile Studio Pro, if windows ink is selected in the calibration panel, the eraser end works, the right-click barrel button works, the middle-click barrel button does not work, pressure wors. If the windows ink checkbox is disabled, nothing works (probably as expected, because the Windows Pointer API is present, so qt doesn't fall through to Wintab, because Qt seems to believe that Wintab was obsoleted with Windows 8). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 395131] Akonadi consumes all memory
https://bugs.kde.org/show_bug.cgi?id=395131 --- Comment #12 from Dennis Schridde --- I also notice regularly (maybe related?) that `akonadictl fsck` finds a lot of "Cleaning up missing external file: ..." and "Found unreferenced external file: ...". ~/.local/share/akonadi/file_lost+found/ contains 3.5 million files. Akonadi regularly re-downloads entire folders via IMAP, after printing on the console that it detected a mismatch in the number of emails in that folder between itself and the IMAP server. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 367892] During folder synchronisation Akonadi blocks out other operations like deleting or viewing mails
https://bugs.kde.org/show_bug.cgi?id=367892 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397580] Write / flush emails that are missing at disk
https://bugs.kde.org/show_bug.cgi?id=397580 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406162] Digital Clock widget not affected by parabolic effect
https://bugs.kde.org/show_bug.cgi?id=406162 Michail Vourlakos changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406162] Digital Clock widget not affected by parabolic effect
https://bugs.kde.org/show_bug.cgi?id=406162 --- Comment #3 from Michail Vourlakos --- That is intentional... Parabolic effect is provided only for applets that are rectangular or less than rectangular in their length axis... The specific applet in big at its length axis so parabolic effect can be supported for it -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406102] Can't open or save projects
https://bugs.kde.org/show_bug.cgi?id=406102 --- Comment #3 from emohr --- I assume you enabled MOVIT. MOVIT is not really working (lot of bugs). The not working open/save dialog could be coming from that. You can try with the refactoring version because some “MOVIT” bugs are solved there. But you have to compile by yourselves at the moment as there is a Nightly-Build AppImage only. https://community.kde.org/Kdenlive/Development. One person is working on the openGL implementation at the moment. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406162] Digital Clock widget not affected by parabolic effect
https://bugs.kde.org/show_bug.cgi?id=406162 --- Comment #2 from Christian Muehlhaeuser --- Created attachment 119214 --> https://bugs.kde.org/attachment.cgi?id=119214=edit Parabolic effect missing for digital clock widget -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 377505] Let Kate automatically reload
https://bugs.kde.org/show_bug.cgi?id=377505 Lothar changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||5.57 Latest Commit||https://commits.kde.org/kte ||xteditor/81a8d573ecaf4ed0cf ||c803b081d3cbec99f8a787 --- Comment #2 from Lothar --- Git commit 81a8d573ecaf4ed0cfc803b081d3cbec99f8a787 by loh tar. Committed on 02/04/2019 at 17:49. Pushed by lohtar into branch 'master'. DocumentPrivate: Add option "Auto Reload Document" to View menu ...and a "Enable Auto Reload" button to the ModOnHdPrompt. There are a couple of request for such feature with different details and some opinions against it at all. Not only because KTextEditor is not well suited to work like 'tail -f'. However, this option should not cause any harm. Currently jump the view after an update sometimes/often but that may fixed later e.g. by D17857 - The max update interval is set to 3sec. Shorter intervals would cause a bad user experience - As long as the user scrolls around updates are blocked - The cursor is set to first/last line of the view when scroll above/below. This is currently not the best solution and cause also the mentioned jumps. Setting to the middle of the view would reduce this odd jumping but it shouldn't jump in any case - Placing the cursor into the last line cause to work like 'tail -f' Related: bug 375361, bug 384384 FIXED-IN: 5.57 Differential Revision: https://phabricator.kde.org/D19517 M +2-1src/data/katepart5ui.rc M +6-0src/dialogs/katedialogs.cpp M +2-1src/dialogs/katedialogs.h M +58 -0src/document/katedocument.cpp M +11 -0src/document/katedocument.h M +30 -0src/view/kateview.cpp M +6-3src/view/kateview.h M +1-0src/view/kateviewinternal.cpp https://commits.kde.org/ktexteditor/81a8d573ecaf4ed0cfc803b081d3cbec99f8a787 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 384384] Documents modified on disk dialog should stop to trigger after first occurrence
https://bugs.kde.org/show_bug.cgi?id=384384 Lothar changed: What|Removed |Added Latest Commit||https://commits.kde.org/kte ||xteditor/81a8d573ecaf4ed0cf ||c803b081d3cbec99f8a787 Resolution|--- |FIXED Status|REOPENED|RESOLVED Version Fixed In||5.57 --- Comment #5 from Lothar --- Git commit 81a8d573ecaf4ed0cfc803b081d3cbec99f8a787 by loh tar. Committed on 02/04/2019 at 17:49. Pushed by lohtar into branch 'master'. DocumentPrivate: Add option "Auto Reload Document" to View menu ...and a "Enable Auto Reload" button to the ModOnHdPrompt. There are a couple of request for such feature with different details and some opinions against it at all. Not only because KTextEditor is not well suited to work like 'tail -f'. However, this option should not cause any harm. Currently jump the view after an update sometimes/often but that may fixed later e.g. by D17857 - The max update interval is set to 3sec. Shorter intervals would cause a bad user experience - As long as the user scrolls around updates are blocked - The cursor is set to first/last line of the view when scroll above/below. This is currently not the best solution and cause also the mentioned jumps. Setting to the middle of the view would reduce this odd jumping but it shouldn't jump in any case - Placing the cursor into the last line cause to work like 'tail -f' Related: bug 375361, bug 377505 FIXED-IN: 5.57 Differential Revision: https://phabricator.kde.org/D19517 M +2-1src/data/katepart5ui.rc M +6-0src/dialogs/katedialogs.cpp M +2-1src/dialogs/katedialogs.h M +58 -0src/document/katedocument.cpp M +11 -0src/document/katedocument.h M +30 -0src/view/kateview.cpp M +6-3src/view/kateview.h M +1-0src/view/kateviewinternal.cpp https://commits.kde.org/ktexteditor/81a8d573ecaf4ed0cfc803b081d3cbec99f8a787 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 375361] Possibility to watch a file like tail -f
https://bugs.kde.org/show_bug.cgi?id=375361 Lothar changed: What|Removed |Added Latest Commit||https://commits.kde.org/kte ||xteditor/81a8d573ecaf4ed0cf ||c803b081d3cbec99f8a787 Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||5.57 --- Comment #2 from Lothar --- Git commit 81a8d573ecaf4ed0cfc803b081d3cbec99f8a787 by loh tar. Committed on 02/04/2019 at 17:49. Pushed by lohtar into branch 'master'. DocumentPrivate: Add option "Auto Reload Document" to View menu ...and a "Enable Auto Reload" button to the ModOnHdPrompt. There are a couple of request for such feature with different details and some opinions against it at all. Not only because KTextEditor is not well suited to work like 'tail -f'. However, this option should not cause any harm. Currently jump the view after an update sometimes/often but that may fixed later e.g. by D17857 - The max update interval is set to 3sec. Shorter intervals would cause a bad user experience - As long as the user scrolls around updates are blocked - The cursor is set to first/last line of the view when scroll above/below. This is currently not the best solution and cause also the mentioned jumps. Setting to the middle of the view would reduce this odd jumping but it shouldn't jump in any case - Placing the cursor into the last line cause to work like 'tail -f' Related: bug 377505, bug 384384 FIXED-IN: 5.57 Differential Revision: https://phabricator.kde.org/D19517 M +2-1src/data/katepart5ui.rc M +6-0src/dialogs/katedialogs.cpp M +2-1src/dialogs/katedialogs.h M +58 -0src/document/katedocument.cpp M +11 -0src/document/katedocument.h M +30 -0src/view/kateview.cpp M +6-3src/view/kateview.h M +1-0src/view/kateviewinternal.cpp https://commits.kde.org/ktexteditor/81a8d573ecaf4ed0cfc803b081d3cbec99f8a787 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406162] Digital Clock widget not affected by parabolic effect
https://bugs.kde.org/show_bug.cgi?id=406162 --- Comment #1 from Michail Vourlakos --- Screenshot please, which one? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406158] Mouse wheel behavior over widgets
https://bugs.kde.org/show_bug.cgi?id=406158 --- Comment #8 from Michail Vourlakos --- (In reply to Christian Muehlhaeuser from comment #7) > > There is an option for disabling wheel behavior in v0.8 at Tasks tab > > Is that also affecting the widgets? What's the definition of Task in latte? > I assumed it refers to the taskbar (app icons), but not the widgets. Yep it affects also widgets. Tasks is just the Tasks plasmoid and refers only to the taskbar. That option should be In Behavior tab but it didn't catch up for v0.8 This is why it was moved to Behavior tab to refer both for widgets and tasks -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406162] New: Digital Clock widget not affected by parabolic effect
https://bugs.kde.org/show_bug.cgi?id=406162 Bug ID: 406162 Summary: Digital Clock widget not affected by parabolic effect Product: lattedock Version: 0.8.7 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: mue...@fribbledom.com Target Milestone: --- I replaced the default analog clock with the digital clock widget, but it's not being affected by the parabolic effect, like the other widgets & tasks. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406158] Mouse wheel behavior over widgets
https://bugs.kde.org/show_bug.cgi?id=406158 --- Comment #7 from Christian Muehlhaeuser --- > There is an option for disabling wheel behavior in v0.8 at Tasks tab Is that also affecting the widgets? What's the definition of Task in latte? I assumed it refers to the taskbar (app icons), but not the widgets. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406158] Mouse wheel behavior over widgets
https://bugs.kde.org/show_bug.cgi?id=406158 --- Comment #6 from Christian Muehlhaeuser --- I'd love to, but for that I have to first understand the current intentions: "What is the intention of intercepting the mouse wheel event here? Why should the widget behave differently in latte than elsewhere on the desktop?" -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828
--- Comment #10 from Julian Seward ---
(In reply to Will Schmidt from comment #9)
> > (2) If (1) isn't the case, and instead, the test program produces different
> > results when run directly vs when run on V, then V is buggy.
>
> ^ this one (option 2). :-)
Ok, thanks for the clarification. In that case, the patch looks OK, except
for the fact that it duplicates the entire subtree for calculation of the
first 32 bits of the result. That will cause the tree to be evaluated twice,
unless you get lucky and the IR optimiser removes the duplication. But
that usually doesn't happen, since CSE is expensive and is only used in
specific situations.
Please can you fix this by binding the duplicated subtrees to a new IRTemp
and instead use the IRTemps twice? Here's an example for case 0x212
(xscvdpsp);
the other cases should be obvious:
case 0x212: // xscvdpsp (VSX Scalar round Double-Precision to single-precision
and
// Convert to Single-Precision format
// Apr 2019 update - write the result to both halves of the
// target VSR. (see bug 401827,401828).
DIP("xscvdpsp v%u,v%u\n", XT, XB);
IRTemp resultI32 = newTemp(Ity_I32);
assign(resultI32, unop( Iop_ReinterpF32asI32,
unop( Iop_TruncF64asF32,
binop( Iop_RoundF64toF32,
get_IR_roundingmode(),
mkexpr( xB ) ) ) );
putVSReg( XT,
binop( Iop_64HLtoV128,
binop( Iop_32HLto64, mkexpr(resultI32),
mkexpr(resultI32) ),
mkU64( 0ULL ) ) );
break;
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 406158] Mouse wheel behavior over widgets
https://bugs.kde.org/show_bug.cgi?id=406158 Michail Vourlakos changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 405994] Show elapsed time when audio CD is read out complete
https://bugs.kde.org/show_bug.cgi?id=405994 Johannes Obermayr changed: What|Removed |Added Latest Commit||https://commits.kde.org/k3b ||/70cb5a5e8259602a908091c1bc ||d8e9e2166eaddd Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Johannes Obermayr --- Git commit 70cb5a5e8259602a908091c1bcd8e9e2166eaddd by Johannes Obermayr. Committed on 02/04/2019 at 17:02. Pushed by jobermayr into branch 'master'. Fix no Elapsed time information issue after finished job.. See also: https://cgit.kde.org/k3b.git/commit/?id=026a29ea79 M +2-2src/k3bjobprogressdialog.cpp https://commits.kde.org/k3b/70cb5a5e8259602a908091c1bcd8e9e2166eaddd -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406158] Mouse wheel behavior over widgets
https://bugs.kde.org/show_bug.cgi?id=406158 --- Comment #5 from Michail Vourlakos --- There is an option for disabling wheel behavior in v0.8 at Tasks tab in master version the option is pretty visible in Behavior page. Plenty of things work differently in Latte than Plasma, if you think you have a better proposal for things and at the same time does not break current functionality feel free to contribute -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406158] Mouse wheel behavior over widgets
https://bugs.kde.org/show_bug.cgi?id=406158 --- Comment #4 from Christian Muehlhaeuser --- Yeah, I'm realizing that now: without the parabolic effect it looks a bit alienated in the panel. What is the intention of intercepting the mouse wheel event here? Why should the widget behave differently in latte than elsewhere on the desktop? Can I disable the wheel interaction by any other means, but keep the parabolic effects and tooltips? I also think the lock button seemingly having a different effect here than in the regular panels feels off to me. This breaks (at least my personal) user expectations in multiple ways: wheel & lock behavior. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406143] we can't modify or delete a storage location
https://bugs.kde.org/show_bug.cgi?id=406143 Erik Duisters changed: What|Removed |Added CC||e.duiste...@gmail.com --- Comment #5 from Erik Duisters --- This is weird. How can you not have a granted permission when you do have a storage location configured? I'll try to look into this during the weekend. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406158] Mouse wheel behavior over widgets
https://bugs.kde.org/show_bug.cgi?id=406158 --- Comment #3 from Michail Vourlakos --- Lock button disables any Latte specific behavior, e.g. parabolic effect, Latte tooltips, applet activation through wheel -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 406100] Choqok crashed after File > Quit
https://bugs.kde.org/show_bug.cgi?id=406100 Brandon Taylor changed: What|Removed |Added CC||donnie126_2...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406158] Mouse wheel behavior over widgets
https://bugs.kde.org/show_bug.cgi?id=406158 --- Comment #2 from Christian Muehlhaeuser --- That indeed works, however I don't understand what the lock does here or why it affects the mouse wheel behavior. Can you give me some insight? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406158] Mouse wheel behavior over widgets
https://bugs.kde.org/show_bug.cgi?id=406158 --- Comment #1 from Michail Vourlakos --- Lock it from applet tooltip -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406161] New: copy-paste "transitions" transformations
https://bugs.kde.org/show_bug.cgi?id=406161 Bug ID: 406161 Summary: copy-paste "transitions" transformations Product: kdenlive Version: Appimage - Refactoring Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: j...@cspv.hu Target Milestone: --- SUMMARY you can go TL;DR - - - I just realized it at the end that what I was trying to suggest already exists :) it would be GREAT to be able to COPY and PASTE simple "transitions" (from now: transformations)... now you can right click on a transformation and COPY... but I don't know what is being copied at times like this... in any case, if you click "remove" the transformation will be removed.. so, you might logically expect that after COPY the transformation could be pasted :) pasted on another clip... even if it works only approximately... the number of key frames and the opacity and the percentage of the clip where it's at... for example... it would be GREAT... cause you wouldn't have to do it all manually from scratch... BUT when tho clips are identical in length, one being typically above the other... the help that COPY/PASTING Transformations would mean would be IMMENSE cause in that case an ACCURATE copy-paste could be implemented :) fade-ins, fade-outs and dissolves are the 0s and 1s of editing :) any type of logical simplicity can be so (!!) LIBERATING :) - - - PS: - - - we can see that a HUGE re-thinking and re-building has been done (!!!), including the retirement of the Affine thing... and the introduction of the universal "compositions and transformations" concept... I mean, it is obvious that you are putting a great deal of thinking in it :) - - - thank you for developing kdenlive!! - - - PS: I just realized that it ALREADY works !! it is only NOT perfect yet !!! - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - TL;DR --- down to here - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - so, now that I realized that it works... here is how it could work even better... (I didn't delete what I wrote because like this I can say one more "THANK YOU !!!" :) ) STEPS TO REPRODUCE 1. create a transformation effect (old Affine) and throw it on a clip... 2. set the key frames and the Opacity values, for example... 3. right click and click "COPY" 4/A. select another clip and try to paste it from right click menu 4/B. try to paste it by hitting CTRL+V OBSERVED RESULT A. from right click there is NO option to paste the transformation (old Affine) on the clip... B. if you hit CTRL+V... it will be magically pasted somewhere near the clip :) (in version 18.12.b closer... in 19.4 farther :) ) EXPECTED RESULT it should be there available in the context menu "paste transformation"... also, either by hitting CTRL+V or clicking "paste transformation" should paste it ON the selected clip... unless it is impossoble SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395981] Merge with Layer Below in Isolate Layer mode either switches off or keeps Isolate mode randomly
https://bugs.kde.org/show_bug.cgi?id=395981 Dmitry Kazakov changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #9 from Dmitry Kazakov --- Sorry, the patch was reverted. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 372880] baloo_file crashes in Baloo::IdFilenameDB::get()
https://bugs.kde.org/show_bug.cgi?id=372880 --- Comment #11 from Reinhard Auner --- Created attachment 119213 --> https://bugs.kde.org/attachment.cgi?id=119213=edit New crash information added by DrKonqi baloo_file (5.55.0) using Qt 5.9.7 - What I was doing when the application crashed: I had open Google Chrome and was surfing the internet - additionally, amarok was running. -- Backtrace (Reduced): #6 Baloo::IdFilenameDB::get (this=this@entry=0x7f33d3bcb9f0, docId=, docId@entry=11059540789267) at /usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/idfilenamedb.cpp:96 #7 0x7f73de612d1f in Baloo::DocumentUrlDB::get (this=this@entry=0x7f33d3bcba70, docId=docId@entry=11059540789267) at /usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/documenturldb.cpp:134 #8 0x7f73de623734 in Baloo::Transaction::documentUrl (this=this@entry=0x7f33d3bcbb20, id=id@entry=11059540789267) at /usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/transaction.cpp:104 #9 0x55baa424071e in Baloo::UnindexedFileIndexer::run (this=0x55baa696fec0) at /usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/file/unindexedfileindexer.cpp:62 #10 0x7f73dda6fe22 in QThreadPoolThread::run (this=0x55baa6977100) at thread/qthreadpool.cpp:99 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406131] Loan balance reused when changing loan settings
https://bugs.kde.org/show_bug.cgi?id=406131 --- Comment #3 from Jack --- It's certainly not you doing anything wrong. However, I think of it less as a bug (incorrect code) than a design decision not to handle this situation. (As Thomas says, that code was written long ago, so there is probably no way to be sure of what was intended at the time.) As a workaround, I would just create a new schedule, staring with the current balance and remaining payments, and then close the original schedule. Separately, even if you are able to use the appimage build, support for Mint 17.3 ends this month, so you are going to need to upgrade in the near future, or find you are unable to use newer versions of more and more programs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395981] Merge with Layer Below in Isolate Layer mode either switches off or keeps Isolate mode randomly
https://bugs.kde.org/show_bug.cgi?id=395981 Dmitry Kazakov changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/759ecacbacdf1a6f62880604 ||a51bdf52ea46f4ab --- Comment #8 from Dmitry Kazakov --- Git commit 759ecacbacdf1a6f62880604a51bdf52ea46f4ab by Dmitry Kazakov. Committed on 02/04/2019 at 16:42. Pushed by dkazakov into branch 'master'. Fix activation of Isolate Mode when merging the layers down When merging layers down, a null layer is activated for a short period of time. It happens because the following: 1) When we remove the top layer, LayerBox adjusts the currently selected index to the lower node. And tries to activate it. 2) The activated node is passed further by the signals chain, and then in KisNodeManager::slotNonUiActivatedNode() we find out that this node has also been removed from the node graph. Therefore we pass 0 to the lower-level code. 3) Isolate mode code sees that there is no layer selected and stops the isolated mode. The patch fixes the issue by storing a separate flag, marking marking the presence of isolated mode. Even when there is no layer to isolate, we still save the sate and try to activate it when a valid node comes. M +7-1libs/ui/kis_node_manager.cpp https://commits.kde.org/krita/759ecacbacdf1a6f62880604a51bdf52ea46f4ab -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406143] we can't modify or delete a storage location
https://bugs.kde.org/show_bug.cgi?id=406143 --- Comment #4 from Nicolas Fella --- My phone was in a weird state so deleting usually works fine. https://invent.kde.org/kde/kdeconnect-android/merge_requests/47 tries to solve the corner case I hit -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 406115] Both "Devices" and "Removable devices" sections are missing in folder selector started by flatpaks
https://bugs.kde.org/show_bug.cgi?id=406115 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|NOT A BUG |--- --- Comment #5 from Nate Graham --- (In reply to Jan Grulich from comment #2) > This is because selecting folders is not supported by portals That, um, seems like a fundamental flaw in the portal spec. How is software that asks the user to choose a folder supposed to work? It just... doesn't? How can we fix this? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405975] Crash when changing Mail Folder name in KMail
https://bugs.kde.org/show_bug.cgi?id=405975 --- Comment #3 from Allen Winter --- https://phabricator.kde.org/D20207 has a possible patch -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 404286] Absurd "cancel" polish translation
https://bugs.kde.org/show_bug.cgi?id=404286 --- Comment #12 from Luigi Toscano --- Any update on this? Apart from Plasma and Frameworks, which have more frequent releases, we are going to have a major release of many applications as part of KDE Applications in few days. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406046] Buenas tardes, el programa es genial y lo ocupo a diario, el problema es que desde la última actualización el programa se cierra y desconoce mi teléfono.
https://bugs.kde.org/show_bug.cgi?id=406046 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #5 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 400010 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 Christoph Feck changed: What|Removed |Added CC||josepaineq...@gmail.com --- Comment #16 from Christoph Feck --- *** Bug 406046 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #52 from Nicofo --- Their reply: > You need to use "supported" openssl library or use the > OPENSSL_CONF=/etc/pki/openssl10.cnf workaround (with installed > compat-openssl10 package). (and indeed with "export OPENSSL_CONF=/etc/pki/openssl10.cnf", no crash) What do you think ? I suppose you have also 2 config files ? - /etc/pki/openssl10.cnf (from compat-openssl10-1.0.2o-3 package) - /etc/pki/tls/openssl.cnf (from openssl-libs-1.1.1b-3 package) In your case the compat. config file if used ?? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 406160] New: Move VPN connections to different list
https://bugs.kde.org/show_bug.cgi?id=406160 Bug ID: 406160 Summary: Move VPN connections to different list Product: plasma-nm Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: dylamsam...@hotmail.com Target Milestone: --- Created attachment 119212 --> https://bugs.kde.org/attachment.cgi?id=119212=edit mockup of how it would look like Right now all connections are shown on the same "Available Connections" list, this gets quickly cumbersome as the available VPN connections grow. Its even worse if you also have multiple wi-fi adapters connected, my suggestion is to move the VPN connections to a different tab within the applet window such that VPN connections remain separated from physical connections, it would be even better if you could group VPN connections on their providers/countries. i attached a small image showing how i'd like to see it -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 406085] libsmbclient gives error while attempting to browse network
https://bugs.kde.org/show_bug.cgi?id=406085 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- If the error messages come from libsmbclient itself, then this isn't a KDE problem. I recommend reporting this to the Samba people. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406143] we can't modify or delete a storage location
https://bugs.kde.org/show_bug.cgi?id=406143 --- Comment #3 from Nicolas Fella --- (In reply to Nicolas Fella from comment #2) > Actually editing is possible by tapping the entry NVM, editing the actual path is not possible -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406143] we can't modify or delete a storage location
https://bugs.kde.org/show_bug.cgi?id=406143 --- Comment #2 from Nicolas Fella --- Actually editing is possible by tapping the entry -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406159] New: make the project monitor's toolbar editable
https://bugs.kde.org/show_bug.cgi?id=406159 Bug ID: 406159 Summary: make the project monitor's toolbar editable Product: kdenlive Version: Appimage - Refactoring Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: j...@cspv.hu Target Milestone: --- it would open up huge perspectives if it becomes editable... then we'll be able to add: "GO to project start / end"... also "GO to zone start / zone end" to start with... :) even on an average screen with a 16:9 aspect ratio there's plenty of room below the project monitor... and if some items of the "monitor" menu could be placed there, it would be invaluable :) - - - thank you for developing kdenlive! - - - -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406143] we can't modify or delete a storage location
https://bugs.kde.org/show_bug.cgi?id=406143 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- I don't think a dedicated edit mode adds much value. It would be rarely done and the same can be achieved by deleting the old location and adding a new one. Deleting is possible by long-pressing and tapping the trash icon. However, it causes an exception for me: java.lang.SecurityException: No permission grants found for UID 10133 and Uri content://com.android.externalstorage.documents/tree/primary: at android.os.Parcel.createException(Parcel.java:1950) at android.os.Parcel.readException(Parcel.java:1918) at android.os.Parcel.readException(Parcel.java:1868) at android.app.IActivityManager$Stub$Proxy.releasePersistableUriPermission(IActivityManager.java:7486) at android.content.ContentResolver.releasePersistableUriPermission(ContentResolver.java:2173) at org.kde.kdeconnect.Plugins.SftpPlugin.SftpSettingsFragment.onActionItemClicked(SftpSettingsFragment.java:477) at androidx.appcompat.app.AppCompatDelegateImpl$ActionModeCallbackWrapperV9.onActionItemClicked(AppCompatDelegateImpl.java:2171) at androidx.appcompat.app.WindowDecorActionBar$ActionModeImpl.onMenuItemSelected(WindowDecorActionBar.java:1123) at androidx.appcompat.view.menu.MenuBuilder.dispatchMenuItemSelected(MenuBuilder.java:840) at androidx.appcompat.view.menu.MenuItemImpl.invoke(MenuItemImpl.java:158) at androidx.appcompat.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:991) at androidx.appcompat.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:981) at androidx.appcompat.widget.ActionMenuView.invokeItem(ActionMenuView.java:625) at androidx.appcompat.view.menu.ActionMenuItemView.onClick(ActionMenuItemView.java:151) at android.view.View.performClick(View.java:6597) at android.view.View.performClickInternal(View.java:6574) at android.view.View.access$3100(View.java:778) at android.view.View$PerformClick.run(View.java:25885) at android.os.Handler.handleCallback(Handler.java:873) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:193) at android.app.ActivityThread.main(ActivityThread.java:6718) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858) Caused by: android.os.RemoteException: Remote stack trace: at com.android.server.am.ActivityManagerService.releasePersistableUriPermission(ActivityManagerService.java:10580) at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:2175) at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3377) at android.os.Binder.execTransact(Binder.java:731) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406158] New: Mouse wheel behavior over widgets
https://bugs.kde.org/show_bug.cgi?id=406158 Bug ID: 406158 Summary: Mouse wheel behavior over widgets Product: lattedock Version: 0.8.7 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: mue...@fribbledom.com Target Milestone: --- SUMMARY I've added the audio mixer widget to my latte dock. Scrolling down over the widget lowers the volume as expected. However scrolling up behaves differently: it first opens the widget, only the second scroll-up event will then raise the volume. EXPECTED RESULT I can only observe this behavior when the audio mixer widget is contained in latte dock. For example in the regular plasma panels, it simply raises the volume on the first "up" event and doesn't slide out the widget altogether. I'd expect it to behave the same within latte dock. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828 --- Comment #9 from Will Schmidt --- (In reply to Julian Seward from comment #8) > I'm confused about the top level diagnosis here. I see two possibilities: > > (1) If the test program, when run directly (meaning, not on V) produces > different results depending on compiler version and/or optimisation > level, then the test program is buggy. > > (2) If (1) isn't the case, and instead, the test program produces different > results when run directly vs when run on V, then V is buggy. ^ this one (option 2). :-) The testcase only fails when the testcase is run under valgrind and the testcase is built with a newer gcc. > Note that"run directly" really does mean run directly on the machine, > and not merely "whatever is in the .stdout.exp file". Correct. As part of running this down I iterated on debug while running the test both standalone and under valgrind. > Will: have you definitely excluded (1) as a possibility? My initial > assumption here was that this problem is (1), but from the comments above > it's hard to be sure either way. Yup. Comment 1 should have include that detail, but lots of associated subsequent noise to help confuse. I have previously spoken to Michael Meissner to confirm the behavior of the GCC change, this explanation is based on his comments, and in hindsight fits and explains what we were seeing. The xscvdpsp,xscvdpspn,xscvdpuxws instructions each convert double precision values to single precision values, and write the results into bits 0-32 of the 128 bit target register. To get the value into the normal position for a scalar register it needed to be right-shifted 32 bits, so gcc always did that. For Power9 we (toolchain) requested hardware put the result into the second 32-bit section so we could avoid the shift. It was then that we realized hardware was already putting the result into *both* of those 32-bit sections, so the compiler removed the (redundant) shift. Valgrind emulation only wrote the result to the first 32-bit section, so the issue was exposed when GCC dropped doing that redundant shift. The proposed patch duplicates the result into the second 32-bit section of the target register. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406157] New: Krita hangs on converting color space
https://bugs.kde.org/show_bug.cgi?id=406157 Bug ID: 406157 Summary: Krita hangs on converting color space Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Krita hangs on converting color space Posted as per request of Dmitry Backtrace: https://pastebin.com/8g7b27G5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 406156] New: Executable: kglobalaccel5 PID: 3301 Signal: Floating point exception (8) Time: 4/2/19 18:47:47
https://bugs.kde.org/show_bug.cgi?id=406156 Bug ID: 406156 Summary: Executable: kglobalaccel5 PID: 3301 Signal: Floating point exception (8) Time: 4/2/19 18:47:47 Product: frameworks-kglobalaccel Version: 5.56.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: m...@morphius.uu.me Target Milestone: --- Created attachment 119211 --> https://bugs.kde.org/attachment.cgi?id=119211=edit Crash information SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406155] New: Flattening the image resets background color and opacity
https://bugs.kde.org/show_bug.cgi?id=406155 Bug ID: 406155 Summary: Flattening the image resets background color and opacity Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Flattening the image resets background color to #00 and opacity to 0. This results in the image having a transparent BG even if it didn't have before. STEPS TO REPRODUCE 1. Set Image background color and opacity to any value 2. Flatten image OBSERVED RESULT BG color and opacity are reset EXPECTED RESULT BG color and opacity should be preserved SOFTWARE/OS VERSIONS Krita Version: 4.2.0-pre-alpha (git 9dac9dc) Languages: en_US Hidpi: false Qt Version (compiled): 5.12.2 Version (loaded): 5.12.2 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.0.5-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 Swap Location: /tmp -- You are receiving this mail because: You are watching all bug changes.
