[krita] [Bug 416608] plugins-impex-kis_csv_test (Child aborted)
https://bugs.kde.org/show_bug.cgi?id=416608 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #1 from vanyossi --- For csv: KisCsvTest::testImportFromWriteonly() ASSERT: "!resource.isEmpty()" It fails to find "markers.svg" from the function KoResourcePaths::findResourceInternal The file is located at krita/libs/flake/styles/markers.svg, or "share/krita/styles/markers.svg" In my case (non standard path isntall), none of the paths checked by findResourceInternal exist. Setting EXTRA_RESOURCE_DIRS to the folder where the file is allows the test to PASS. 2020-01-25 01:40:53.864 kis_csv_test[47951:533929] ApplePersistenceIgnoreState: Existing state will not be touched. New state will be written to (null) * Start testing of KisCsvTest * Config: Using QtTest library 5.12.3, Qt 5.12.3 (x86_64-little_endian-lp64 shared (dynamic) release build; by Clang 10.0.1 (clang-1001.0.46.4) (Apple)) PASS : KisCsvTest::initTestCase() PASS : KisCsvTest::testFiles() QDEBUG : KisCsvTest::testImportFromWriteonly() Entering "TestUtil::prepareFile()" QFlags(0x2|0x4|0x20|0x40|0x200|0x400|0x2000|0x4000) QDEBUG : KisCsvTest::testImportFromWriteonly() Invalid profile : "/Library/ColorSync/Profiles//WebSafeColors.icc" "Web Safe Colors" QWARN : KisCsvTest::testImportFromWriteonly() KoColor debug runtime checks are active. QDEBUG : KisCsvTest::testImportFromWriteonly() findresourcePath "/Volumes/Osiris/programs/krita-master/testdata/kritatests/unittests/markers.svg" QDEBUG : KisCsvTest::testImportFromWriteonly() import result = Cannot read: 5 "Cannot open file for reading. Reason: The file could not be opened." PASS : KisCsvTest::testImportFromWriteonly() QDEBUG : KisCsvTest::testExportToReadonly() Entering "TestUtil::prepareFile()" QFlags(0x2|0x4|0x20|0x40|0x200|0x400|0x2000|0x4000) QDEBUG : KisCsvTest::testExportToReadonly() findresourcePath "/Volumes/Osiris/programs/krita-master/testdata/kritatests/unittests/markers.svg" QDEBUG : KisCsvTest::testExportToReadonly() Entering "TestUtil::testExportToReadonly()" QObject(0x0) QDEBUG : KisCsvTest::testExportToReadonly() export result = Cannot write: 0 "Cannot open file for writing. Reason: An error occurred when writing to the file." PASS : KisCsvTest::testExportToReadonly() QDEBUG : KisCsvTest::testImportIncorrectFormat() Entering "TestUtil::prepareFile()" QFlags(0x4|0x40|0x200|0x400|0x2000|0x4000) QDEBUG : KisCsvTest::testImportIncorrectFormat() findresourcePath "/Volumes/Osiris/programs/krita-master/testdata/kritatests/unittests/markers.svg" QDEBUG : KisCsvTest::testImportIncorrectFormat() findresourcePath "/Volumes/Osiris/programs/krita-master/testdata/kritatests/unittests/markers.svg" QDEBUG : KisCsvTest::testImportIncorrectFormat() import result = Error code = 4 "The file format cannot be parsed." PASS : KisCsvTest::testImportIncorrectFormat() PASS : KisCsvTest::cleanupTestCase() Totals: 6 passed, 0 failed, 0 skipped, 0 blacklisted, 807ms * Finished testing of KisCsvTest * -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416724] Latte dock consumes all free memory available and wont open
https://bugs.kde.org/show_bug.cgi?id=416724 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Michail Vourlakos --- Waiting memory information -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408617] Dolphin doesn't remember icon size per folder with 'remember properties for each folder' configuration
https://bugs.kde.org/show_bug.cgi?id=408617 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416724] Latte dock consumes all free memory available and wont open
https://bugs.kde.org/show_bug.cgi?id=416724 --- Comment #1 from Michail Vourlakos --- How much memory? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374332] External monitor message is not refreshed when the option is changed
https://bugs.kde.org/show_bug.cgi?id=374332 gvgeo changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||gv...@protonmail.com --- Comment #1 from gvgeo --- There are two problems with this message. 1. Suppression message change only when loading or change outputs. 2. Suppression message does not know the desired action for lid. But always warns about suspend. Possible needed changes. 1. Need to update "Triggers Lid Action". void HandleButtonEventsConfig::save() if ( m_triggerLidActionWhenExternalMonitorPresent != m_OLDtriggerLidActionWhenExternalMonitorPresent) Q_EMIT triggersLidActionChanged(HandleButtonEvents::triggersLidAction()); 2. Include lidAction in DBus. Display action in message, and display message only if needed. or 2. Change the message, and add m_lidAction != 0 in HandleButtonEvents::triggersLidAction(). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415332] [Snap] Okular does not show the dialogue to let me load a file
https://bugs.kde.org/show_bug.cgi?id=415332 Ben Creasy changed: What|Removed |Added CC||b...@bencreasy.com --- Comment #9 from Ben Creasy --- Adalbert, it would probably help if you attached a copy of the settings that you have when the bug appears - apparently copied from from the snap? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416443] QT Particles seem to overload and block KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=416443 --- Comment #8 from Mihai Sorin Dobrescu --- I've noticed another strange behaviour: in Dolphin, if I delete a file, the confirmation dialog appears and that Dolphin instance freezes after the user confirmation. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 403054] GeoIP.dat.gz
https://bugs.kde.org/show_bug.cgi?id=403054 Patrick Silva changed: What|Removed |Added CC||cplanto...@gmail.com --- Comment #26 from Patrick Silva --- *** Bug 416709 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 416709] error geolite databases
https://bugs.kde.org/show_bug.cgi?id=416709 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 403054 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416443] QT Particles seem to overload and block KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=416443 --- Comment #7 from Mihai Sorin Dobrescu --- Created attachment 125387 --> https://bugs.kde.org/attachment.cgi?id=125387=edit Plasma frozen It displays 05:31:11, the time when it froze, despite now is passed 08:00. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416725] New: KWIN Seg Fault on Session Login
https://bugs.kde.org/show_bug.cgi?id=416725 Bug ID: 416725 Summary: KWIN Seg Fault on Session Login Product: kwin Version: 5.17.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: anameles...@gmail.com Target Milestone: --- Application: kwin_x11 (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.66.0 Operating System: Linux 5.3.0-26-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I have set Kwin to start an empty session on login. - Custom settings of the application: Also set a few applications and scripts to auto-start -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f43c6242d00 (LWP 1681))] Thread 4 (Thread 0x7f439edbe700 (LWP 1816)): #0 0x7f43beae59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f43c22dffb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f43c22dff68, cond=0x7f43c22dff90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f43c22dff90, mutex=0x7f43c22dff68) at pthread_cond_wait.c:655 #3 0x7f43c1fea874 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f43c1fea8b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f43beadf6db in start_thread (arg=0x7f439edbe700) at pthread_create.c:463 #6 0x7f43c5b9d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f439700 (LWP 1813)): #0 0x7f43c5b90cf6 in __GI_ppoll (fds=fds@entry=0x7f4394000d28, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f43c30ce8a1 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f4394000d28) at kernel/qcore_unix.cpp:132 #3 qt_safe_poll (fds=0x7f4394000d28, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #4 0x7f43c30d0038 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f43c307306a in QEventLoop::exec (this=this@entry=0x7f439fffed00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f43c2e8e3aa in QThread::exec (this=) at thread/qthread.cpp:531 #7 0x7f43bd4eb815 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f43c2e8fb52 in QThreadPrivate::start (arg=0x5608baf326d0) at thread/qthread_unix.cpp:360 #9 0x7f43beadf6db in start_thread (arg=0x7f439700) at pthread_create.c:463 #10 0x7f43c5b9d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f43a7095700 (LWP 1791)): #0 0x7f43c5b90cf6 in __GI_ppoll (fds=fds@entry=0x7f43a000f0d8, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f43c30ce8a1 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f43a000f0d8) at kernel/qcore_unix.cpp:132 #3 qt_safe_poll (fds=0x7f43a000f0d8, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #4 0x7f43c30d0038 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f43c307306a in QEventLoop::exec (this=this@entry=0x7f43a7094cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f43c2e8e3aa in QThread::exec (this=) at thread/qthread.cpp:531 #7 0x7f43bc0b60e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f43c2e8fb52 in QThreadPrivate::start (arg=0x7f43bc32dd80) at thread/qthread_unix.cpp:360 #9 0x7f43beadf6db in start_thread (arg=0x7f43a7095700) at pthread_create.c:463 #10 0x7f43c5b9d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f43c6242d00 (LWP 1681)): [KCrash Handler] #6 0x in ?? () #7 0x7f43c234ac9f in KWin::belongToSameGroup (w2=0x5608bb291200, w1=0x5608bb1f9870) at ./effects/diminactive/diminactive.cpp:44 #8 KWin::DimInactiveEffect::canDimWindow (this=0x5608bb1dfed0, w=0x5608bb291200) at ./effects/diminactive/diminactive.cpp:182 #9 0x7f43c234b4bd in KWin::DimInactiveEffect::paintWindow (this=this@entry=0x5608bb1dfed0, w=, w@entry=0x5608bb291200, mask=mask@entry=2, region=..., data=...) at ./effects/diminactive/diminactive.cpp:131 #10 0x7f43c565980e in KWin::EffectsHandlerImpl::paintWindow (this=this@entry=0x5608bb137e50, w=0x5608bb291200, mask=mask@entry=2, region=..., data=...) at ./effects.cpp:436 #11
[plasmashell] [Bug 416443] QT Particles seem to overload and block KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=416443 Mihai Sorin Dobrescu changed: What|Removed |Added Resolution|NOT A BUG |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #6 from Mihai Sorin Dobrescu --- Hello, seems that updated Plasma version or the shorter time have lead it in a state when plasma is frozen, but tasks can still be changed and I have expanded a Yakuake, so I can issue commands. What could I do to diagnose it, as I might have a short window of time to do that? I can say that freeze occurs in less than 24 hours every time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416706] Krita last-used filter performance problem
https://bugs.kde.org/show_bug.cgi?id=416706 --- Comment #5 from vanyossi --- This bug is fixed and awaiting revision: https://invent.kde.org/kde/krita/merge_requests/229 (In reply to Ahab Greybeard from comment #4) > In a totally fresh kritarc file those entries do not exist. After use of > gaussian blur then HSV adjustment then Quit, I have, in order: > kritarc entries are created as they are needed, if you have keys missing its because you have not performed the action so they are created. That does not mean there is a problem with your krita installation. toSelector/LastUsedFilter is only created if you choose a filter from the filter list on the left of the filter dialog. filterdialog/rememberlastpreset is only created when you tick the ckeckbox on top of all filters to remember custom user fitler presets and the dialog is closed. showFilterGallery: is created when you press "Ok" to apply the filter. setShowFilterGalleryLayerMaskDialog is created after you have used at least one Filter Mask. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416534] Some ui files are not compilable after editing with designer
https://bugs.kde.org/show_bug.cgi?id=416534 --- Comment #9 from Thomas Baumgart --- *** Bug 416564 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416564] Big differences in the ui file after editing with designer
https://bugs.kde.org/show_bug.cgi?id=416564 Thomas Baumgart changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Thomas Baumgart --- *** This bug has been marked as a duplicate of bug 416534 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416662] Desktop not working after latest update
https://bugs.kde.org/show_bug.cgi?id=416662 Tom F changed: What|Removed |Added CC||tomfoley...@gmail.com --- Comment #9 from Tom F --- I think this is related to https://bugs.kde.org/show_bug.cgi?id=416617. Manually installing qml-module-org-kde-qqc2desktopstyle from a prior build will restore desktop visibility. A quick test proves it. Since I'm not set up for development, I just downloaded https://ubuntu.pkgs.org/19.10/kubuntu-backports-amd64/qml-module-org-kde-qqc2desktopstyle_5.66.0-0ubuntu1~ubuntu19.10~ppa1_amd64.deb.html and put that in it's place. It brought the desktop back. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413762] GTK2 themes are not working at all and the previews aren't working either for only gtk2
https://bugs.kde.org/show_bug.cgi?id=413762 b2.t...@gmx.com changed: What|Removed |Added CC||b2.t...@gmx.com --- Comment #7 from b2.t...@gmx.com --- Can someone provide a script to do the fix (i.e some a sh with `find` `mv`, etc) waiting for the Plasma fix ? For now it's not clear how to fix it manually. For example here on F31 I have the BSM themes in ~/.themes and they do not work (the preview yes but the few GTK2 apps I use, notably Lazarus and what is produced with it, don't apply them). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?
https://bugs.kde.org/show_bug.cgi?id=416361 --- Comment #6 from ferweer --- Information that it became qt5.14 could not be confirmed with the installation of neon just the other day. The qt version was still 5.12.4 in the system update. The confirmation was done on virtualbox and the neon iso used was neon-user-20200123-1116. Well, it is a wonder if this is updated in qt on kubuntu 19.10. Well, it is whether this is updated with qt of kubuntu19.10. If not, the next issue may be reported again. Of course, by the user operating the tablet stylus. > A / B / C / D or some apps cannot be operated with tablet stylus! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416724] Latte dock consumes all free memory available and wont open
https://bugs.kde.org/show_bug.cgi?id=416724 Mohammad changed: What|Removed |Added CC||mj19922...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416724] New: Latte dock consumes all free memory available and wont open
https://bugs.kde.org/show_bug.cgi?id=416724 Bug ID: 416724 Summary: Latte dock consumes all free memory available and wont open Product: lattedock Version: 0.9.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: mj19922...@yahoo.com Target Milestone: --- Created attachment 125386 --> https://bugs.kde.org/attachment.cgi?id=125386=edit System monitor SUMMARY When I click to open latte dock it drain all free memory and it wont open. I have to kill the process to stop it STEPS TO REPRODUCE 1. Launch latte-dock 2. Open System monitor to observe application behavior 3. See latte-dock drain all free memory 4. Kill the process. OBSERVED RESULT See latte-dock drain all free memory and wont open at all. EXPECTED RESULT The program open and run normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416706] Krita last-used filter performance problem
https://bugs.kde.org/show_bug.cgi?id=416706 --- Comment #4 from Ahab Greybeard --- I forgot that I'd changed showFilterGallery because I was fixating on filterdialog/rememberlastpreset In my 'normal/usual' kritarc file (the one I restore from backup after any tests or config clearing) I have the following, in order: Selector/LastUsedFilter=gaussian blur (this does not change after any filter use) filterdialog/rememberlastpreset=false setShowFilterGalleryLayerMaskDialog=true showFilterGallery=false In a totally fresh kritarc file those entries do not exist. After use of gaussian blur then HSV adjustment then Quit, I have, in order: filterdialog/rememberlastpreset=false showFilterGallery=false setShowFilterGalleryLayerMaskDialog (is not present) Selector/LastUsedFilter= (is not present after repeated use of filters and restarts) In the fresh config kritarc file that shows the reported fault after manual changes, I have, in order: FilterSelector/LastUsedFilter=halftone (manually entered and set, does not change) filterdialog/rememberlastpreset=true (manually set, I don't know how it's supposed to change) showFilterGallery=true (manually set, I don't know how it's supposed to change) setShowFilterGalleryLayerMaskDialog (is not present) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416723] New: Every time I try to go to the regional settings and formats it crashes
https://bugs.kde.org/show_bug.cgi?id=416723 Bug ID: 416723 Summary: Every time I try to go to the regional settings and formats it crashes Product: systemsettings Version: 5.17.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aar...@doofus.org Target Milestone: --- Application: systemsettings5 (5.17.90) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 4.12.14-lp151.28.36-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: 1. Open systemsettings5 2. Click Regional Settings 3. Click Formats It always crashes. Note that I see KMail also crashing in the same place when I start it in QT. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), 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 0x7f4d292dd900 (LWP 22426))] Thread 6 (Thread 0x7f4ceed73700 (LWP 22624)): #0 0x7f4d2471d19b in __GI___poll (fds=0x55ddc77dd670, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4d1da951a9 in g_main_context_poll (priority=, n_fds=1, fds=0x55ddc77dd670, timeout=, context=0x55ddc77db690) at gmain.c:4169 #2 0x7f4d1da951a9 in g_main_context_iterate (context=0x55ddc77db690, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3863 #3 0x7f4d1da95542 in g_main_loop_run (loop=0x55ddc77db7a0) at gmain.c:4064 #4 0x7f4cefcfae36 in () at /usr/lib64/libgio-2.0.so.0 #5 0x7f4d1dabcac6 in g_thread_proxy (data=0x55ddc794cca0) at gthread.c:784 #6 0x7f4d203c3569 in start_thread (arg=0x7f4ceed73700) at pthread_create.c:465 #7 0x7f4d247279ef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f4cef574700 (LWP 22623)): #0 0x7f4d2471d19b in __GI___poll (fds=0x55ddc794dde0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4d1da951a9 in g_main_context_poll (priority=, n_fds=1, fds=0x55ddc794dde0, timeout=, context=0x55ddc794ca90) at gmain.c:4169 #2 0x7f4d1da951a9 in g_main_context_iterate (context=context@entry=0x55ddc794ca90, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3863 #3 0x7f4d1da952bc in g_main_context_iteration (context=0x55ddc794ca90, may_block=may_block@entry=1) at gmain.c:3929 #4 0x7f4d1da95301 in glib_worker_main (data=) at gmain.c:5724 #5 0x7f4d1dabcac6 in g_thread_proxy (data=0x55ddc794cc00) at gthread.c:784 #6 0x7f4d203c3569 in start_thread (arg=0x7f4cef574700) at pthread_create.c:465 #7 0x7f4d247279ef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f4cfdacf700 (LWP 22599)): #0 0x7f4d2471d19b in __GI___poll (fds=0x7f4cf8004a30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4d1da951a9 in g_main_context_poll (priority=, n_fds=1, fds=0x7f4cf8004a30, timeout=, context=0x7f4cf8000bd0) at gmain.c:4169 #2 0x7f4d1da951a9 in g_main_context_iterate (context=context@entry=0x7f4cf8000bd0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3863 #3 0x7f4d1da952bc in g_main_context_iteration (context=0x7f4cf8000bd0, may_block=may_block@entry=1) at gmain.c:3929 #4 0x7f4d2507fa3b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f4cf8000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f4d2501f03a in QEventLoop::exec(QFlags) (this=this@entry=0x7f4cfdacec90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f4d24e30467 in QThread::exec() (this=) at thread/qthread.cpp:536 #7 0x7f4d229919e5 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f4d24e3193c in QThreadPrivate::start(void*) (arg=0x55ddc59bf970) at thread/qthread_unix.cpp:342 #9 0x7f4d203c3569 in start_thread (arg=0x7f4cfdacf700) at pthread_create.c:465 #10 0x7f4d247279ef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f4d0d484700 (LWP 22431)): #0 0x7f4d2471d19b in __GI___poll (fds=0x7f4d08014e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4d1da951a9 in g_main_context_poll (priority=, n_fds=1, fds=0x7f4d08014e60, timeout=, context=0x7f4d08000bd0) at gmain.c:4169 #2 0x7f4d1da951a9 in g_main_context_iterate (context=context@entry=0x7f4d08000bd0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3863 #3 0x7f4d1da952bc in g_main_context_iteration (context=0x7f4d08000bd0, may_block=may_block@entry=1) at gmain.c:3929 #4 0x7f4d2507fa3b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f4d08000b10, flags=...)
[Skanlite] [Bug 416098] Cannot resume multi-page scan after scanner reconnect
https://bugs.kde.org/show_bug.cgi?id=416098 --- 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.
[dolphin] [Bug 406624] dolphin titlebar garbled with baloosearch json query
https://bugs.kde.org/show_bug.cgi?id=406624 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #8 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.
[plasmashell] [Bug 415047] problem with players on logon
https://bugs.kde.org/show_bug.cgi?id=415047 --- 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.
[krita] [Bug 416722] New: Krita (7b6c721) can be softbricked by deleting files within share folder
https://bugs.kde.org/show_bug.cgi?id=416722 Bug ID: 416722 Summary: Krita (7b6c721) can be softbricked by deleting files within share folder Product: krita Version: git master Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: reptilli...@live.com Target Milestone: --- Created attachment 125385 --> https://bugs.kde.org/attachment.cgi?id=125385=edit Crashlog SUMMARY As I attempted to try to get rid of unused brushes or brushes that came with Krita by default by deleting resources within share folder, Krita becomes paper-weight or softbricked. I can't do a single thing at all. STEPS TO REPRODUCE 1. Delete Brushes and Bundles 2. Krita becomes softbricked OBSERVED RESULT You can't work on any image. It just exit. EXPECTED RESULT Continues to work as normally. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The git might be different, but there is no functional difference between the built Krita and the current master. The one that I have is using a non-used box convolution code that isn't used by Krita, and nothing else is linked to these codes. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 416721] New: KMail crashes after restarting
https://bugs.kde.org/show_bug.cgi?id=416721 Bug ID: 416721 Summary: KMail crashes after restarting Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: aar...@doofus.org Target Milestone: --- Application: kontact (5.13.1 (19.12.1)) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 4.12.14-lp151.28.36-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: When I attempted to fill in a previously used email address while writing an email, KMail crashed as it usually does. However, when I attempt to restart it it crashes immediately when it attempts to re-open the draft email I was typing. I have already reported the other crash (see bug# 416288 https://bugs.kde.org/show_bug.cgi?id=416288 ). The crash dump in this case is different, however. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), 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 0x7f887b96a980 (LWP 125685))] Thread 23 (Thread 0x7f87afdef700 (LWP 126334)): #0 0x7f887815c19b in __GI___poll (fds=0x7f87a8004600, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8871abb1a9 in g_main_context_poll (priority=, n_fds=1, fds=0x7f87a8004600, timeout=, context=0x7f87a8000bd0) at gmain.c:4169 #2 0x7f8871abb1a9 in g_main_context_iterate (context=context@entry=0x7f87a8000bd0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3863 #3 0x7f8871abb2bc in g_main_context_iteration (context=0x7f87a8000bd0, may_block=may_block@entry=1) at gmain.c:3929 #4 0x7f8878cd6a3b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f87a8000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f8878c7603a in QEventLoop::exec(QFlags) (this=this@entry=0x7f87afdeec30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f8878a87467 in QThread::exec() (this=) at thread/qthread.cpp:536 #7 0x7f8878a8893c in QThreadPrivate::start(void*) (arg=0x55e077ed0750) at thread/qthread_unix.cpp:342 #8 0x7f8873e8b569 in start_thread (arg=0x7f87afdef700) at pthread_create.c:465 #9 0x7f88781669ef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f87b8f22700 (LWP 125887)): #0 0x7f8873e918ad in futex_wait_cancelable (private=, expected=0, futex_word=0x7f87b8f21b18) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f8873e918ad in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f87b8f21ac8, cond=0x7f87b8f21af0) at pthread_cond_wait.c:502 #2 0x7f8873e918ad in __pthread_cond_wait (cond=0x7f87b8f21af0, mutex=0x7f87b8f21ac8) at pthread_cond_wait.c:655 #3 0x7f8868d1c5ba in base::ConditionVariable::Wait() () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:75 #4 0x7f8868d1d05c in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:235 #5 0x7f8868d1d16f in base::WaitableEvent::Wait() () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:155 #6 0x7f8868cd8c98 in base::internal::WorkerThread::Delegate::WaitForWork(base::WaitableEvent*) () at ./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:33 #7 0x7f8868cdd259 in base::internal::WorkerThread::RunWorker() () at ./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:317 #8 0x7f8868cdd594 in base::internal::WorkerThread::RunSharedWorker() () at ./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:235 #9 0x7f8868d1f1e5 in ThreadFunc() () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81 #10 0x7f8873e8b569 in start_thread (arg=0x7f87b8f22700) at pthread_create.c:465 #11 0x7f88781669ef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f87c35f4700 (LWP 125838)): #0 0x7f8878161269 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f8878a8ae94 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long long, int*, int) (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:116 #2 0x7f8878a8ae94 in QtLinuxFutex::futexWait >(QBasicAtomicInteger&, QBasicAtomicInteger::Type) (expectedValue=, futex=...) at thread/qfutex_p.h:135 #3 0x7f8878a8ae94 in futexSemaphoreTryAcquire_loop(QBasicAtomicInteger&, unsigned long long, unsigned long long, int) (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:219 #4 0x7f8878a8ae94 in
[kwin] [Bug 416720] New: Multiseat with single GPU fails
https://bugs.kde.org/show_bug.cgi?id=416720 Bug ID: 416720 Summary: Multiseat with single GPU fails Product: kwin Version: 5.17.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multihead Assignee: kwin-bugs-n...@kde.org Reporter: lo...@kde.bt.alestan.publicvm.com Target Milestone: --- SUMMARY When Wayland compositors start, they are supposed to limit themselves to only the hardware which is attached to the seat on which the compositor is running loginctl can split the outputs of a single graphics card into multiple seats; these split outputs count as primary devices for seats, allowing them to start up. kwin breaks in 2 ways when trying this. STEPS TO REPRODUCE 1. Set up kwin wayland, with logind or elogind 2. With a multi-output GPU, assign one port to seat1 3. Ask startplasma-wayland to start on seat0; note failure mode 1 4. Ask startplasma-wayland to start on seat1; note failure mode 2 OBSERVED RESULT In the seat0 case, kwin_wayland fails to start. It doesn't matter if there is a monitor attached to the output in question, or which output gets moved to seat1, it fails to start. In the seat1 case, it starts, and grabs all connected screens, regardless of which seat they are assigned. Seat1 doesn't own the tty, so you actually get the mouse cursor *over* the text of the tty, with various repaints fighting back and forth between kwin and the tty shell. EXPECTED RESULT In the worst case, a clear error message that split-gpu multiseat is not supported on KDE. In the ideal case, it should be possible to run a multi-seat setup with a single GPU the same as you can with multiple GPUs. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo 17.0, Linux 5.3.9 (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 19.08.3 Qt Version: 5.12.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 397602] Configuration files should contain only persistent configuration and not state
https://bugs.kde.org/show_bug.cgi?id=397602 --- Comment #6 from Ben Creasy --- Note: a bit of progress with this commit https://phabricator.kde.org/D26440 which adds a utility function for state files. I'm hopeful that with new features (e.g., https://phabricator.kde.org/T12192), the files will be clean of state. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password
https://bugs.kde.org/show_bug.cgi?id=415130 tliu0...@gmail.com changed: What|Removed |Added CC||tliu0...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416506] Opening .tga files only shows alpha channel while the rest of the image shows up as transparent.
https://bugs.kde.org/show_bug.cgi?id=416506 vanyossi changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from vanyossi --- Please do not change the status of the bug. ASSIGNED means it is confirmed and someone has taken the responsability of fixing it :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416719] Segmentation fault in Plasma when I try to open Dolphin (either directly or indirectly)
https://bugs.kde.org/show_bug.cgi?id=416719 RobinK changed: What|Removed |Added CC||ro...@xtra.co.nz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416719] Segmentation fault in Plasma when I try to open Dolphin (either directly or indirectly)
https://bugs.kde.org/show_bug.cgi?id=416719 RobinK changed: What|Removed |Added Summary|Segmentation fault in |Segmentation fault in |Plasma when I try to open |Plasma when I try to open |Dolphin (either directly or |Dolphin (either directly or |indirectly theough another |indirectly) |app | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416716] Some dialogs are created off screen
https://bugs.kde.org/show_bug.cgi?id=416716 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from vanyossi --- Hi, do you adjust screens [Adjust screens (e.g., with xrandr)] while krita is open? We usually can't do anything about window placement as that is decided by your window management and possibly Qt. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 --- Comment #9 from Darin Miller --- I never manually mirrored the screens. Kscreen seems to be working fine when all resolution and monitor position adjustments are made via kscreen. However, kscreen does not detect the current monitor states. So changes made via nvidia-setting are never captured. I upscale my 2k screen to 4K via nvidia setting as that is not possible with kscreen under xorg. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416719] New: Segmentation fault in Plasma when I try to open Dolphin (either directly or indirectly theough another app
https://bugs.kde.org/show_bug.cgi?id=416719 Bug ID: 416719 Summary: Segmentation fault in Plasma when I try to open Dolphin (either directly or indirectly theough another app Product: plasmashell Version: 5.17.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ro...@xtra.co.nz CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.90) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 4.12.14-lp151.28.36-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: I'd just updated a number of libQT5 packages (19 of them) to level 5.14.0-lp151.3.2 Now Dolphin doesn't work at all. Trying to open it from the command line gives me this: Icon theme "MacUltimate_Leopard" not found. Icon theme "Lero_0.3" not found. Icon theme "Papirus" not found. Segmentation fault (core dumped) The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f986f196900 (LWP 8119))] Thread 8 (Thread 0x7f980a965700 (LWP 8532)): #0 0x7f9865d508ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9868e47eeb in QWaitConditionPrivate::wait (deadline=..., this=0x562fe956cc30) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x562fe9c8cb40, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f9868e48069 in QWaitCondition::wait (this=this@entry=0x562fe9c8cb48, mutex=mutex@entry=0x562fe9c8cb40, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #4 0x7f986cf91fe3 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x562fe9c8cb38) at /usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:255 #5 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x562fe9c8caa0) at /usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:905 #6 0x7f986cf92441 in QSGRenderThread::run (this=0x562fe9c8caa0) at /usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1000 #7 0x7f9868e4193c in QThreadPrivate::start (arg=0x562fe9c8caa0) at thread/qthread_unix.cpp:342 #8 0x7f9865d4a569 in start_thread () from /lib64/libpthread.so.0 #9 0x7f98687379ef in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f9811de1700 (LWP 8509)): #0 0x7f9868728c98 in read () from /lib64/libc.so.6 #1 0x7f9862552880 in g_wakeup_acknowledge () from /usr/lib64/libglib-2.0.so.0 #2 0x7f986250b257 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f986250b6f0 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #4 0x7f986250b85c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f986908fa3b in QEventDispatcherGlib::processEvents (this=0x7f980c000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f986902f03a in QEventLoop::exec (this=this@entry=0x7f9811de0c70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f9868e40467 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7f9814703bd7 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #9 0x7f9868e4193c in QThreadPrivate::start (arg=0x562fe9b31860) at thread/qthread_unix.cpp:342 #10 0x7f9865d4a569 in start_thread () from /lib64/libpthread.so.0 #11 0x7f98687379ef in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f98239c9700 (LWP 8379)): #0 0x7f9865d508ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9868e47eeb in QWaitConditionPrivate::wait (deadline=..., this=0x562fe93fb8c0) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x562fe93fd9f0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f9868e48069 in QWaitCondition::wait (this=this@entry=0x562fe93fd9f8, mutex=mutex@entry=0x562fe93fd9f0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #4 0x7f986cf91fe3 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x562fe93fd9e8) at /usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:255 #5 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x562fe93fd950) at /usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:905 #6 0x7f986cf92441 in QSGRenderThread::run (this=0x562fe93fd950) at
[kstars] [Bug 416650] Crashes when imaging a sequence.
https://bugs.kde.org/show_bug.cgi?id=416650 --- Comment #3 from mountainai...@outlook.com --- Created attachment 125384 --> https://bugs.kde.org/attachment.cgi?id=125384=edit Crash report Crash report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416706] Krita last-used filter performance problem
https://bugs.kde.org/show_bug.cgi?id=416706 --- Comment #3 from Kruthers --- (In reply to Ahab Greybeard from comment #1) . . . > Maybe if you edit kritarc to have filterdialog/rememberlastpreset=false (if > it is set to true for you)? > > Does your FilterSelector/LastUsedFilter= entry ever change after using the > filters? I just quit out of Krita and checked my ~/.config/kritarc file and found the following: filterdialog/rememberlastpreset=false FilterSelector/LastUsedFilter=levels I didn't change rememberlastpreset so it was already false. And LastUsedFilter should not be levels; I haven't used that filter at all today (that I recall). The one I probably used last is the HSV/HSL filter which I'm using constantly. So that's confusing... Anyway, hope this is helpful. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 416650] Crashes when imaging a sequence.
https://bugs.kde.org/show_bug.cgi?id=416650 --- Comment #2 from mountainai...@outlook.com --- Here's a crash report from my oldest MacBook Pro (2013): Process: kstars [649] Path: /Applications/KStars.app/Contents/MacOS/kstars Identifier:??? Version: 3.3.9 (3.3.9) Code Type: X86-64 (Native) Parent Process:??? [1] Responsible: kstars [649] User ID: 501 Date/Time: 2020-01-22 21:32:32.406 -0800 OS Version:Mac OS X 10.15.2 (19C57) Report Version:12 Anonymous UUID:BB264918-3631-C88C-1529-2DF8687521E7 Time Awake Since Boot: 1500 seconds System Integrity Protection: enabled Crashed Thread:6 Thread (pooled) Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x Exception Note:EXC_CORPSE_NOTIFY Termination Signal:Segmentation fault: 11 Termination Reason:Namespace SIGNAL, Code 0xb Terminating Process: exc handler [649] VM Regions Near 0: --> __TEXT 0001008ae000-0001013b2000 [ 11.0M] r-x/r-x SM=COW /Applications/KStars.app/Contents/MacOS/kstars Thread 0:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x7fff706afce6 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x7fff70771185 _pthread_cond_wait + 701 2 org.qt-project.QtCore 0x00010379247b 0x10376a000 + 164987 3 org.qt-project.QtCore 0x000103792414 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 100 4 org.qt-project.QtCore 0x00010379422f QFutureInterfaceBase::waitForFinished() + 175 5 0x000101058053 FITSView::loadFITSFromData(FITSData*, QString const&) + 99 (fitsview.cpp:311) 6 0x00010094e44f FITSTab::loadFITSFromData(FITSData*, QUrl const&, FITSMode, FITSScale) + 111 7 0x000100939c5e FITSViewer::updateFITSFromData(FITSData*, QUrl const&, int, int*, FITSScale) + 222 (fitsviewer.cpp:538) 8 0x0001009088b1 ISD::CCD::processBLOB(IBLOB*) + 4737 (indiccd.cpp:1725) 9 0x0001008f9bbf INDIListener::processBLOB(IBLOB*) + 255 (qlist.h:308) 10 org.qt-project.QtCore 0x00010397a635 QMetaObject::activate(QObject*, int, int, void**) + 1765 11 0x000101125d0f ClientManager::newINDIBLOB(IBLOB*) + 63 12 org.qt-project.QtCore 0x000103973812 QObject::event(QEvent*) + 770 13 org.qt-project.QtWidgets0x000102b567c0 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272 14 org.qt-project.QtWidgets0x000102b57b75 QApplication::notify(QObject*, QEvent*) + 581 15 org.qt-project.QtCore 0x00010394ab74 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212 16 org.qt-project.QtCore 0x00010394bc86 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 774 17 libqcocoa.dylib 0x000106c72062 QCocoaEventDispatcherPrivate::processPostedEvents() + 322 (qcocoaeventdispatcher.mm:914) 18 libqcocoa.dylib 0x000106c72870 QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 32 19 com.apple.CoreFoundation0x7fff390aab21 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 20 com.apple.CoreFoundation0x7fff390aaac0 __CFRunLoopDoSource0 + 103 21 com.apple.CoreFoundation0x7fff390aa8d4 __CFRunLoopDoSources0 + 209 22 com.apple.CoreFoundation0x7fff390a9740 __CFRunLoopRun + 1272 23 com.apple.CoreFoundation0x7fff390a8bd3 CFRunLoopRunSpecific + 499 24 com.apple.HIToolbox 0x7fff37bff65d RunCurrentEventLoopInMode + 292 25 com.apple.HIToolbox 0x7fff37bff39d ReceiveNextEventCommon + 600 26 com.apple.HIToolbox 0x7fff37bff127 _BlockUntilNextEventMatchingListInModeWithFilter + 64 27 com.apple.AppKit0x7fff36270eb4 _DPSNextEvent + 990 28 com.apple.AppKit0x7fff3626f690 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352 29 com.apple.AppKit0x7fff362613ae -[NSApplication run] + 658 30 libqcocoa.dylib 0x000106c71779 QCocoaEventDispatcher::processEvents(QFlags) + 2937 (qcocoaeventdispatcher.mm:437) 31 org.qt-project.QtCore 0x00010394629f QEventLoop::exec(QFlags) + 431 32 org.qt-project.QtCore 0x00010394b1c2 QCoreApplication::exec() + 130 33 0x0001008c17a3 main + 19715 (qlist.h:829) 34 libdyld.dylib 0x7fff7056c7fd start + 1 Thread
[tellico] [Bug 416718] MobyGames data source improvements
https://bugs.kde.org/show_bug.cgi?id=416718 --- Comment #1 from Robby Stephenson --- Git commit 9b5a9d535336d19075c7d751523686a20ec02a99 by Robby Stephenson. Committed on 25/01/2020 at 00:45. Pushed by rstephenson into branch 'master'. mobygamesfetcher - check for error response and pass to user M +10 -0src/fetch/mobygamesfetcher.cpp https://commits.kde.org/tellico/9b5a9d535336d19075c7d751523686a20ec02a99 --- Comment #2 from Robby Stephenson --- Git commit 2cf8aa6525ca4a2a8ad5c63ed70b626380129b5f by Robby Stephenson. Committed on 25/01/2020 at 01:11. Pushed by rstephenson into branch 'master'. mobygamesfetcher: allow user selection of image size Covers are apparently grouped by country. Take the first one that has a "Front Cover" indication, falling back to "Media" if not found. Small images are thumbnails, large images are otherwise. M +57 -9src/fetch/mobygamesfetcher.cpp M +12 -0src/fetch/mobygamesfetcher.h M +1-1src/tests/mobygamesfetchertest.cpp https://commits.kde.org/tellico/2cf8aa6525ca4a2a8ad5c63ed70b626380129b5f -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 416718] MobyGames data source improvements
https://bugs.kde.org/show_bug.cgi?id=416718 --- Comment #1 from Robby Stephenson --- Git commit 9b5a9d535336d19075c7d751523686a20ec02a99 by Robby Stephenson. Committed on 25/01/2020 at 00:45. Pushed by rstephenson into branch 'master'. mobygamesfetcher - check for error response and pass to user M +10 -0src/fetch/mobygamesfetcher.cpp https://commits.kde.org/tellico/9b5a9d535336d19075c7d751523686a20ec02a99 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416640] Shadowless task switcher on Wayland
https://bugs.kde.org/show_bug.cgi?id=416640 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |LATER Version Fixed In||5.19.0 -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 416718] New: MobyGames data source improvements
https://bugs.kde.org/show_bug.cgi?id=416718 Bug ID: 416718 Summary: MobyGames data source improvements Product: tellico Version: 3.2.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: ro...@periapsis.org Target Milestone: --- Error messages should be properly handled and shown to the user. Configuration option for image sizes should be added. Entry updates and general searching should be able to include platform. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 416697] Last move not counted in Freecell
https://bugs.kde.org/show_bug.cgi?id=416697 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WAITINGFORINFO CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- This seems to be working fine for me. Could you try with the verison from flathub? https://flathub.org/apps/details/org.kde.kpat In case you're running an old version of things and we already fixed that? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414501] No accented characters in Desktop Effects filter
https://bugs.kde.org/show_bug.cgi?id=414501 --- Comment #2 from Petros --- (In reply to Vlad Zahorodnii from comment #1) > Created attachment 125280 [details] > run with `qmlscene test.qml` > > Can you run the attached "app" and check whether you're able to type in > accented Greek characters there? I did and I succeeded writing accented Greek chars as expected. My system has changed (to Arch) but the issue still exists. Also happened occasionally in the SystemSettings main filter textbox, but randomly, which is frustrating... Current KDE info: Operating System: Arch Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 4.19.96-1-lts OS Type: 64-bit Processors: 4 × Intel® Core™ i3 CPU M 380 @ 2.53GHz Memory: 7,5 GiB -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416703] Search results are hard to find on yellow-highlighted, annotated pdf text
https://bugs.kde.org/show_bug.cgi?id=416703 Albert Astals Cid changed: What|Removed |Added Severity|normal |wishlist CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 403643] Okular stops rendering PDF and uses up 100% cpu (possible regression)
https://bugs.kde.org/show_bug.cgi?id=403643 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #6 from Albert Astals Cid --- (In reply to Postix from comment #4) > (In reply to Oliver Sander from comment #3) > > Is this the same as https://bugs.kde.org/show_bug.cgi?id=396137 ? > > It could be, however I don't need to "scroll fast". > > Here's a backtrace when I just happened again. I tried to exit Okular, the > window closed, but the process kept running in the background for a while. > I will try to reproduce it at another time with debug symbols attached. :) > > ``` > [postix ~]# gdb attach `pidof okular` > GNU gdb (GDB) 8.3.1 > > (...) > > Attaching to process 4039 > [New LWP 4041] > [New LWP 4042] > [New LWP 4046] > [New LWP 4047] > [New LWP 4048] > [New LWP 4049] > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/usr/lib/libthread_db.so.1". > 0x7f429aece480 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 > /usr/lib/../share/gcc-9.2.0/python/libstdcxx/v6/xmethods.py:731: > SyntaxWarning: list indices must be integers or slices, not str; perhaps you > missed a comma? > refcounts = ['_M_refcount']['_M_pi'] > (gdb) bt > #0 0x7f429aece480 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 > #1 0x7f429af1da0c in g_main_context_prepare () at > /usr/lib/libglib-2.0.so.0 > #2 0x7f429af1e046 in () at /usr/lib/libglib-2.0.so.0 > #3 0x7f429af1e1f1 in g_main_context_iteration () at > /usr/lib/libglib-2.0.so.0 > #4 0x7f429ca78d40 in > QEventDispatcherGlib::processEvents(QFlags) > () at /usr/lib/libQt5Core.so.5 > #5 0x7f429ca1f41c in > QEventLoop::exec(QFlags) () at > /usr/lib/libQt5Core.so.5 > #6 0x7f42947bab7a in () at /usr/lib/libOkular5Core.so.9 > #7 0x7f42947bbe43 in Okular::Document::closeDocument() () at > /usr/lib/libOkular5Core.so.9 > #8 0x7f4294959513 in Okular::Part::closeUrl(bool) () at > /usr/lib/qt/plugins/okularpart.so > #9 0x562c14bdd7b6 in () > #10 0x562c14bdd8c9 in () > #11 0x7f429ca4df50 in QObject::event(QEvent*) () at > /usr/lib/libQt5Core.so.5 > #12 0x7f429d59678b in QWidget::event(QEvent*) () at > /usr/lib/libQt5Widgets.so.5 > #13 0x7f429d6b0865 in QMainWindow::event(QEvent*) () at > /usr/lib/libQt5Widgets.so.5 > #14 0x7f429dec045c in KMainWindow::event(QEvent*) () at > /usr/lib/libKF5XmlGui.so.5 > #15 0x7f429df0b988 in KXmlGuiWindow::event(QEvent*) () at > /usr/lib/libKF5XmlGui.so.5 > #16 0x7f429d552472 in QApplicationPrivate::notify_helper(QObject*, > QEvent*) () at /usr/lib/libQt5Widgets.so.5 > #17 0x7f429d55bc89 in QApplication::notify(QObject*, QEvent*) () at > /usr/lib/libQt5Widgets.so.5 > #18 0x7f429ca208b2 in QCoreApplication::notifyInternal2(QObject*, > QEvent*) () at /usr/lib/libQt5Core.so.5 > #19 0x7f429ca23116 in > QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at > /usr/lib/libQt5Core.so.5 > #20 0x7f429ca796f4 in () at /usr/lib/libQt5Core.so.5 > #21 0x7f429af1c39e in g_main_context_dispatch () at > /usr/lib/libglib-2.0.so.0 > #22 0x7f429af1e1b1 in () at /usr/lib/libglib-2.0.so.0 > #23 0x7f429af1e1f1 in g_main_context_iteration () at > /usr/lib/libglib-2.0.so.0 > #24 0x7f429ca78d40 in > QEventDispatcherGlib::processEvents(QFlags) > () at /usr/lib/libQt5Core.so.5 > #25 0x7f429ca1f41c in > QEventLoop::exec(QFlags) () at > /usr/lib/libQt5Core.so.5 > #26 0x7f429ca27426 in QCoreApplication::exec() () at > /usr/lib/libQt5Core.so.5 > #27 0x562c14bd379a in () > #28 0x7f429c3f0153 in __libc_start_main () at /usr/lib/libc.so.6 > #29 0x562c14bd47ce in () > ``` This backtrace is not useful, next time you need to trace all threads not just the main one "thread apply all bt" in gdb Also ideally do that before closing Also if you have a file in which it's relatively easy to reproduce, attach it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416652] Empty items in system tray area
https://bugs.kde.org/show_bug.cgi?id=416652 --- Comment #7 from hexchain --- Somehow those empty icons disappeared, probably because I logged out once? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416671] When using two screens, any window in full screen mode on your secondary screen can go out of bonds
https://bugs.kde.org/show_bug.cgi?id=416671 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Vlad Zahorodnii --- Yeah, I think we just restore geometry and not check workspace position. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416667] gcc10 ppc64le impossible constraint in 'asm' in test_isa
https://bugs.kde.org/show_bug.cgi?id=416667 --- Comment #7 from Mark Wielaard --- Created attachment 125383 --> https://bugs.kde.org/attachment.cgi?id=125383=edit GCC10 ppc64 asm constrainst update The attached patch is what I am testing now and seems to pass the compiler/build. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416640] Shadowless task switcher on Wayland
https://bugs.kde.org/show_bug.cgi?id=416640 --- Comment #4 from Vlad Zahorodnii --- (In reply to Nate Graham from comment #2) > So is there anything to be done for this bug No, I don't think so. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416667] gcc10 ppc64le impossible constraint in 'asm' in test_isa
https://bugs.kde.org/show_bug.cgi?id=416667
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0 |1
--- Comment #6 from Mark Wielaard ---
With the patch I am still seeing:
test_isa_2_07_part1.c:398:4: error: impossible constraint in 'asm'
398 |__asm__ __volatile__ ("mtvsrd %x0,%1" : "=ws" (vec_out) : "r"
(r14));
|^~~
test_isa_3_0.c: In function 'test_xscvdphp':
test_isa_3_0.c:1831:4: error: impossible constraint in 'asm'
1831 |__asm__ __volatile__ ("xscvdphp %x0, %x1 " : "+wi" (vec_xt) : "wi"
(vec_xb));
|^~~
I replaced the other "ws" constrainst in test_isa_2_07_part1.c with "wa" too.
For "wi" I found gcc:
commit e670418ff18f36f81f3f619c34578da03d102694
Author: Segher Boessenkool
Date: Tue Jun 4 18:27:45 2019 +0200
rs6000: wi->wa, wt->wa
"wi" and "wt" mean just the same as "wa" these days. Change them to
the simpler name.
And
commit 72e3386e136205dcc69e61e538b94643832cf22a
Author: Segher Boessenkool
Date: Wed Jun 5 01:31:32 2019 +0200
rs6000: ww -> wa
"ww" can always be "wa".
So I did that in test_isa_3_0.c
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 416673] VLC-related KWin crash
https://bugs.kde.org/show_bug.cgi?id=416673 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Vlad Zahorodnii --- *** This bug has been marked as a duplicate of bug 413179 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413179] Crash in libnvidia-glcore
https://bugs.kde.org/show_bug.cgi?id=413179 --- Comment #6 from Vlad Zahorodnii --- *** Bug 416673 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416706] Krita last-used filter performance problem
https://bugs.kde.org/show_bug.cgi?id=416706 vanyossi changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |ASSIGNED CC||ghe...@gmail.com Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com --- Comment #2 from vanyossi --- Confirming the strange behaviour. filterdialog/rememberlastpreset controls as far as the code is telling me, if a user preset for the current filter should reopen next session. It has no control over FilterSelector/LastUsedFilter FilterSelector/LastUsedFilter always gets written to the last entry, and from what I can see it also gets "triggered" to render when the filterGallery is open. This is indeed a bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415839] Resizing apps results in flickering or controls jumping around
https://bugs.kde.org/show_bug.cgi?id=415839 Vlad Zahorodnii changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |vlad.zahorod...@kde.org Flags||Wayland- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415839] Resizing apps results in flickering or controls jumping around
https://bugs.kde.org/show_bug.cgi?id=415839 --- Comment #7 from Vlad Zahorodnii --- Created attachment 125382 --> https://bugs.kde.org/attachment.cgi?id=125382=edit Potential fix I would be very grateful if someone could test my patch. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416516] Read/Write .mov and .mp4 rating metadata
https://bugs.kde.org/show_bug.cgi?id=416516 --- Comment #10 from Tim --- This seems to be the best ffmpeg copying for copying/importing metadata. ffmpeg -export_xmp 1 -export_all 1 -i -c copy -export_xmp 1 -export_all 1 -map_metadata 0 It will copy xmp tags and tags ffmpeg supports in the format of the output file. Xmp tags copied seem to be written correctly as Adobe Bridge still reads them. Supported Quicktime tags seem to copy across, but not completely. eg OpenSuse Linux 15.1 can read the copied QuickTime tag, but Windows cannot. There is another command that will attempt to copy mov tags unsupported by ffmpeg, but it doesn't seem to copy them exactly. Exiftool reports differences and in the case of the rating tags I am interested in neither Windows or Adobe Bridge reads them from the destination file. ffmpeg -export_xmp 1 -export_all 1 -i -c copy -export_xmp 1 -export_all 1 -movflags use_metadata_tags -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384764] Proxy clips on time line play slower than original clips
https://bugs.kde.org/show_bug.cgi?id=384764 CzAndrew changed: What|Removed |Added Version|Appimage - Refactoring |19.12.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384764] Proxy clips on time line play slower than original clips
https://bugs.kde.org/show_bug.cgi?id=384764 CzAndrew changed: What|Removed |Added CC||czart.and...@gmail.com --- Comment #12 from CzAndrew --- I confirm also that proxy clips doesn't work in the newest kdenlive (19.12.1; win10). The proxy clip play smooth in the Clip monitor, but when I add it to Project monitor, the playback speed is reduced to ~2 fps. I see that the proxy clip is being played both in the project and clip monitor (image resolution reduced), but the project monitor plays it very choppy. I tried to convert the proxy clips with different codecs, results are the same. Does anyone know a workaround for this? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416711] Missing german translation
https://bugs.kde.org/show_bug.cgi?id=416711 Thomas Baumgart changed: What|Removed |Added Latest Commit|https://commits.kde.org/kmy |https://commits.kde.org/kmy |money/68ea42edf0bb5bdb5642e |money/620a3907576f41a859f82 |c080c65fdaf0e94bbf2 |d9f6d0c0ad417ad0097 --- Comment #2 from Thomas Baumgart --- Git commit 620a3907576f41a859f82d9f6d0c0ad417ad0097 by Thomas Baumgart. Committed on 24/01/2020 at 23:12. Pushed by tbaumgart into branch 'master'. Make headers translatable FIXED-IN: 5.0.9 (cherry picked from commit 68ea42edf0bb5bdb5642ec080c65fdaf0e94bbf2) M +4-4kmymoney/views/khomeview_p.h https://commits.kde.org/kmymoney/620a3907576f41a859f82d9f6d0c0ad417ad0097 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416711] Missing german translation
https://bugs.kde.org/show_bug.cgi?id=416711 Thomas Baumgart changed: What|Removed |Added Version Fixed In||5.0.9 Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kmy ||money/68ea42edf0bb5bdb5642e ||c080c65fdaf0e94bbf2 --- Comment #1 from Thomas Baumgart --- Git commit 68ea42edf0bb5bdb5642ec080c65fdaf0e94bbf2 by Thomas Baumgart. Committed on 24/01/2020 at 23:11. Pushed by tbaumgart into branch '5.0'. Make headers translatable FIXED-IN: 5.0.9 M +4-4kmymoney/views/khomeview_p.h https://commits.kde.org/kmymoney/68ea42edf0bb5bdb5642ec080c65fdaf0e94bbf2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416717] New: Feature request: give a global option to force touchpad settings
https://bugs.kde.org/show_bug.cgi?id=416717 Bug ID: 416717 Summary: Feature request: give a global option to force touchpad settings Product: systemsettings Version: 5.17.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: fli...@vongellhorn.ch Target Milestone: --- I'm the plasma Maintainer at Solus and I discovered an issue reg the xdg "tapToClick=true" value inside the touchpadxlibinput file, it's device specific like Synaptics or Elan in my case, If I set synaptics the Elan touchpad "taptoclick" doesn't work till I manually set it. Having the possibility to have a global xdg settings which would activate it for all touchpads would be a nice to have. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416716] New: Some dialogs are created off screen
https://bugs.kde.org/show_bug.cgi?id=416716
Bug ID: 416716
Summary: Some dialogs are created off screen
Product: krita
Version: 4.2.8
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: krita-bugs-n...@kde.org
Reporter: eleanorh...@outlook.com
Target Milestone: ---
SUMMARY
When launched from the UI, some dialogs are created at the global screen
coordinate 0,0 which on my system is completely off screen, making the dialog
inaccessible.
I have observed this for the "Scale Image to New Size", "Resize Canvas", "Grow
Selection", "Shrink Selection", "Feather Selection", and "Border Selection"
dialogs. Other dialogs I have tried behave as expected.
STEPS TO REPRODUCE
1. Adjust screens (e.g., with xrandr) so that global coordinate 0,0 is off
screen.
2. Launch one of the above dialogs
OBSERVED RESULT
The Krita UI will fade to gray but no dialog will be visible.
xwininfo -root -tree will confirm that the dialog has been created at 0,0
EXPECTED RESULT
The dialog would appear in an accessible part of the screen -- presumably near
the center of the main Krita window
SOFTWARE/OS VERSIONS
Windows: N/A
macOS: N/A
Linux/KDE Plasma: Arch Linux, rolling, 4.19.97-1-lts Kernel
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0
ADDITIONAL INFORMATION
wmctrl is able to move the dialog onto the screen and except for its placement
everything else seems to be fine about its behavior. I have been using this
hacky bash script as a work-around:
while IFS= read -r window; do
wmctrl -r ${window} -e 0,0,733,-1,-1
done <<<"$(xwininfo -tree -root | grep -oP "(?<=\\\").*?Krita.*?(?=\\\")")"
Renaming my $HOME/.config/kritarc file or $HOME/.local/share/krita directory
did not affect the issue
I expect it is possible in xorg to place a screen at an arbitrary offset from
the global coordinates, but I do not know how practical this would be with the
more modern and intelligent screen adjustment tools. My system is in this
(admittedly unusual) state because I have two monitors side-by-side, with the
left screen about 700 pixels lower than the right one.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 416713] Plasmoids sometimes get stuck in the dragged state after being moved
https://bugs.kde.org/show_bug.cgi?id=416713 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416715] New: Dolphin crashes
https://bugs.kde.org/show_bug.cgi?id=416715 Bug ID: 416715 Summary: Dolphin crashes Product: dolphin Version: 19.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bruttafa...@libero.it CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (19.12.1) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 4.12.14-lp151.28.36-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.1" -- Information about the crash: Hello, I have OpenSuse Leap 15.1 with kernel 4.12.14-lp151.28.36-default - What I was doing when the application crashed: I simply tried to open Dolphin. After the last update, it doesn't open anymore. This is the error when I start dolphin by command: dolphin KCrash: Application 'dolphin' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Fermato dolphin I removed the .kde4 folder (I found this as a possible a solution) but nothing has changed. I have these repos, all updated to last version: https://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_15.1/ https://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_15.1/ https://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_15.1/ http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.1/ http://packman.inode.at/suse/openSUSE_Leap_15.1/Essentials/ http://download.opensuse.org/distribution/leap/15.1/repo/oss/ http://download.opensuse.org/update/leap/$releasever/oss/ http://download.opensuse.org/distribution/leap/15.1/repo/non-oss/ http://linux.teamviewer.com/yum/stable/main/binary-x86_64/ http://download.opensuse.org/update/leap/15.1/non-oss/ since I added the first three repo, every now and then I have little problems. I hope this helps, thank you. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7effca59ed80 (LWP 8689))] Thread 5 (Thread 0x7eff9a23c700 (LWP 8694)): #0 0x7effc9e11c98 in read () from /lib64/libc.so.6 #1 0x7effbb78fc80 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7effbb74acb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7effbb74b150 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7effbb74b2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7effc398ba3b in QEventDispatcherGlib::processEvents (this=0x7eff94000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7effc392b03a in QEventLoop::exec (this=this@entry=0x7eff9a23bcb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7effc373c467 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7effc373d93c in QThreadPrivate::start (arg=0x560d9666c960) at thread/qthread_unix.cpp:342 #9 0x7effbe4cf569 in start_thread () from /lib64/libpthread.so.0 #10 0x7effc9e209ef in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7effa339e700 (LWP 8693)): #0 0x7effbe4d58ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7effa36c29ab in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7effa36c26b7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7effbe4cf569 in start_thread () from /lib64/libpthread.so.0 #4 0x7effc9e209ef in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7effabbd3700 (LWP 8691)): #0 0x7effbb790fd4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7effbb74a9b4 in g_main_context_query () from /usr/lib64/libglib-2.0.so.0 #2 0x7effbb74b127 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7effbb74b2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7effc398ba3b in QEventDispatcherGlib::processEvents (this=0x7effa4000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7effc392b03a in QEventLoop::exec (this=this@entry=0x7effabbd2c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7effc373c467 in QThread::exec (this=) at thread/qthread.cpp:536 #7 0x7effc3e06115 in ?? () from /usr/lib64/libQt5DBus.so.5 #8 0x7effc373d93c in QThreadPrivate::start (arg=0x7effc407dda0) at thread/qthread_unix.cpp:342 #9 0x7effbe4cf569 in start_thread () from /lib64/libpthread.so.0 #10 0x7effc9e209ef in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7effb1c86700 (LWP 8690)): #0 0x7effc9e1619b in poll () from /lib64/libc.so.6 #1 0x7effbe094307 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7effbe095f3a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7effb4867fe0 in ?? () from
[digikam] [Bug 407049] Import fails to detect duplicate photos
https://bugs.kde.org/show_bug.cgi?id=407049 --- Comment #6 from daniel-other+kde...@dadosch.de --- Also, importing via MTP doesn't work properly (not a digikam issue), but I copy the files using adb instead. However, duplicate photos aren't detected when importing. Maybe it would be possible to use the fuzzy search algorithm if importing from a local storage? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 416714] New: KDevelop crashed when pressing "update signature" on problem solver
https://bugs.kde.org/show_bug.cgi?id=416714 Bug ID: 416714 Summary: KDevelop crashed when pressing "update signature" on problem solver Product: kdevelop Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: isma...@gmail.com Target Milestone: --- Application: kdevelop (5.5.40) (Compiled from sources) Qt Version: 5.12.4 Frameworks Version: 5.67.0 Operating System: Linux 5.3.0-23-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: Change a function declaration on a C++ header file, KDevelop marks it as possible error and suggests to update the signature as the solution. Clicking on the solution makes KDevelop crash. I'm using clang as the code analyzer The crash can be reproduced every time. -- Backtrace (Reduced): #6 0x7fb5941883eb in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7fb594167899 in __GI_abort () at abort.c:79 #8 0x7fb5945a8a99 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb5945a7ee7 in qt_assert_x(char const*, char const*, char const*, int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb55a77e5da in AdaptSignatureAction::execute() (this=0x559ae019bb70) at /home/isma/kde/src/kdevelop/plugins/clang/codegen/adaptsignatureaction.cpp:83 Possible duplicates by query: bug 416549, bug 416494, bug 416379, bug 416113, bug 416051. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 416714] KDevelop crashed when pressing "update signature" on problem solver
https://bugs.kde.org/show_bug.cgi?id=416714 --- Comment #1 from Ismael Asensio --- Created attachment 125381 --> https://bugs.kde.org/attachment.cgi?id=125381=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416577] Message Box Doesn't Size
https://bugs.kde.org/show_bug.cgi?id=416577 Thomas Baumgart changed: What|Removed |Added Latest Commit|https://commits.kde.org/kmy |https://commits.kde.org/kmy |money/07d70700b68b5df1e66c3 |money/ad0c921909a5ded1508e1 |1386b0248d3fdf3194c |42034bcff064f22c4fa --- Comment #3 from Thomas Baumgart --- Git commit ad0c921909a5ded1508e142034bcff064f22c4fa by Thomas Baumgart. Committed on 24/01/2020 at 21:51. Pushed by tbaumgart into branch 'master'. Fix layout handling in split correction dialog FIXED-IN: 5.0.9 (cherry picked from commit 07d70700b68b5df1e66c31386b0248d3fdf3194c) M +117 -145 kmymoney/dialogs/ksplitcorrectiondlg.ui https://commits.kde.org/kmymoney/ad0c921909a5ded1508e142034bcff064f22c4fa -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416713] New: Plasmoids sometimes get stuck in the dragged state after being moved
https://bugs.kde.org/show_bug.cgi?id=416713 Bug ID: 416713 Summary: Plasmoids sometimes get stuck in the dragged state after being moved Product: plasmashell Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: filipfila@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 125380 --> https://bugs.kde.org/attachment.cgi?id=125380=edit Visual evidence SUMMARY Moving plasmoids on the desktop can sometimes trigger a bug whereby the widget gets stuck in a dragged state even though it's been released. STEPS TO REPRODUCE 1. Move the widget around some. OBSERVED RESULT When placed somewhere the widget remains stuck in the dragged state. I don't seem to be able to get the controls to spawn again and move it. If the widget is removed the hover effect remains on the desktop. EXPECTED RESULT Dragged state evens when the widget is positioned somewhere. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Happens with stock themes as well. No plasmashell terminal output when it happens. Might be easier to reproduce if moving the item around a bit longer. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416577] Message Box Doesn't Size
https://bugs.kde.org/show_bug.cgi?id=416577 Thomas Baumgart changed: What|Removed |Added Version Fixed In||5.0.9 Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kmy ||money/07d70700b68b5df1e66c3 ||1386b0248d3fdf3194c --- Comment #2 from Thomas Baumgart --- Git commit 07d70700b68b5df1e66c31386b0248d3fdf3194c by Thomas Baumgart. Committed on 24/01/2020 at 21:50. Pushed by tbaumgart into branch '5.0'. Fix layout handling in split correction dialog FIXED-IN: 5.0.9 M +117 -145 kmymoney/dialogs/ksplitcorrectiondlg.ui https://commits.kde.org/kmymoney/07d70700b68b5df1e66c31386b0248d3fdf3194c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416706] Krita last-used filter performance problem
https://bugs.kde.org/show_bug.cgi?id=416706 Ahab Greybeard changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- I was initially unable to reproduce this on 4.2.6 to 4.2.9(Stable) appimages The kritarc entry for me was FilterSelector/LastUsedFilter=gaussian blur and was unchanged no matter which filter I used. I found filterdialog/rememberlastpreset=false and changed it to true and was unable to reproduce the fault. The entry for FilterSelector/LastUsedFilter= did not change no matter which filter I used. If I changed it to FilterSelector/LastUsedFilter=halftone then I could not reproduce the fault. However, if I deleted kritarc and restarted with fresh configuration the entry for FilterSelector/LastUsedFilter= did not get recorded in kritarc. I manually made filterdialog/rememberlastpreset=true and the FilterSelector/LastUsedFilter= line did not appear in kritarc after filter uses and restarts. Then I manually entered FilterSelector/LastUsedFilter=halftone and then the fault appeared exactly as described in the initial report. There are probably other entries in kritarc which I'm not aware of that may be significant in this matter. Maybe if you edit kritarc to have filterdialog/rememberlastpreset=false (if it is set to true for you)? Does your FilterSelector/LastUsedFilter= entry ever change after using the filters? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413778] Hibernate/Supsend icons are grayed out
https://bugs.kde.org/show_bug.cgi?id=413778 Sandro Knauß changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Version|5.14.5 |5.17.5 --- Comment #3 from Sandro Knauß --- I can reproduce the same behaviour under 5.17.5 (from Debian experimental). A workaround I found in meantime, if I restart the plasmashell (plasmashell --replace). I can access the Suspend/Hibernate from the applet, like expected. Any ideas how to debug? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 416712] Offline Plate-solving crashes as soon as I click on "Capture & Slew"
https://bugs.kde.org/show_bug.cgi?id=416712 Stanley Fertig changed: What|Removed |Added CC||stanl...@nyc.rr.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 416712] New: Offline Plate-solving crashes as soon as I click on "Capture & Slew"
https://bugs.kde.org/show_bug.cgi?id=416712 Bug ID: 416712 Summary: Offline Plate-solving crashes as soon as I click on "Capture & Slew" Product: kstars Version: 3.3.9 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: stanl...@nyc.rr.com Target Milestone: --- SUMMARY Plate solving using Astrometry offline crashes immediately. STEPS TO REPRODUCE 1. Slew to a target 2. After kStars says it's tracking it, click on "Capture and Slew" 3. OBSERVED RESULT 2020-01-24T16:23:16 Solver failed. Try again. 2020-01-24T16:23:16 Error starting solver: Process crashed 2020-01-24T16:23:16 Starting solver... 2020-01-24T16:23:16 Solver iteration #1 2020-01-24T16:23:16 Image received. 2020-01-24T16:23:13 Capturing image... 2020-01-24T16:23:02 Detected Astrometry.net version 0.76 2020-01-24T16:18:21 World Coordinate System (WCS) is enabled. CCD rotation must be set either manually in the CCD driver or by solving an image before proceeding to capture any further images, otherwise the WCS information may be invalid. 2020-01-24T16:18:20 Idle. EXPECTED RESULT Expect plate solving to find the object, not crash. SOFTWARE/OS VERSIONS Windows: macOS: 10.15.2 (Catalina) Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Because this was happening repeatedly, I entirely erased my MacBook Air and did a fresh install of OS X, then Xcode, then kStars. Added ALL the Astrometry files. Set up HomeBrew, Python 3* and Astrometry in kStars. Note: I repeatedly got a "Python installation failed" message when setting up Python in kStars so installed Python 3 using Terminal. Ekos now says that Home-brew, Python and Astrometry are "already set up." But it won't work. Am very frustrated. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416711] New: Missing german translation
https://bugs.kde.org/show_bug.cgi?id=416711 Bug ID: 416711 Summary: Missing german translation Product: kmymoney Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: translation Assignee: kmymoney-de...@kde.org Reporter: eu...@albiker.org Target Milestone: --- Created attachment 125379 --> https://bugs.kde.org/attachment.cgi?id=125379=edit red lines show the wrong german translation / green line is a correct translation SUMMARY In account Overview there is a missing german translation of 2 columns. Please see attached picture STEPS TO REPRODUCE 1. download Appimage KMyMoney-5.0.8-ccaadb2-x86_64.AppImage 2. 3. OBSERVED RESULT The columns headers are named "Anlagekonten / !M / C / !R / " EXPECTED RESULT The column headers should be: "Anlagekonten / !M / V / !A / " SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Frameworks 5.66.0 Qt 5.12.4 (kompiliert gegen 5.12.4) Das xcb Fenstersystem ADDITIONAL INFORMATION please see attached picture -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416687] Add support for .URL files to open Internet URL from file content via KDE Dolphin
https://bugs.kde.org/show_bug.cgi?id=416687 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Rocs] [Bug 416710] New: some files not installed while installing kde rocs software
https://bugs.kde.org/show_bug.cgi?id=416710 Bug ID: 416710 Summary: some files not installed while installing kde rocs software Product: Rocs Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: rocs-bugs-n...@kde.org Reporter: pscorp...@gmail.com Target Milestone: --- Created attachment 125378 --> https://bugs.kde.org/attachment.cgi?id=125378=edit terminal snapshot SUMMARY tried to install kde rocs on freshly installed ubuntu on macos virtual machine and but there were lots of missing files. I'll attatch terminal screenshot of what files were missing. 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.
[ktorrent] [Bug 416709] New: error geolite databases
https://bugs.kde.org/show_bug.cgi?id=416709 Bug ID: 416709 Summary: error geolite databases Product: ktorrent Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: cplanto...@gmail.com Target Milestone: --- Created attachment 125377 --> https://bugs.kde.org/attachment.cgi?id=125377=edit error geolite SUMMARY STEPS TO REPRODUCE 1. Open KTorrent OBSERVED RESULT geolite.maxmind.com not found EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Type OS: 64 bits OS Opensuse 19 Tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416708] New: system-settings crash immediately when choose traditonal chinese and us english
https://bugs.kde.org/show_bug.cgi?id=416708 Bug ID: 416708 Summary: system-settings crash immediately when choose traditonal chinese and us english Product: systemsettings Version: 5.17.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: wingtong...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. system-settings>locale>language 2. choose traditional chinese and any european language, system-settings crash immediately 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.
[kwin] [Bug 416707] New: Virtual desktop wrap-around doesn't work for qdbus org.kde.KWin /KWin org.kde.KWin.nextDesktop
https://bugs.kde.org/show_bug.cgi?id=416707 Bug ID: 416707 Summary: Virtual desktop wrap-around doesn't work for qdbus org.kde.KWin /KWin org.kde.KWin.nextDesktop Product: kwin Version: 5.17.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: raitarohik...@protonmail.com Target Milestone: --- SUMMARY There are shortcuts to switch to the next/prev virtual desktop. Those are: qdbus org.kde.KWin /KWin org.kde.KWin.nextDesktop qdbus org.kde.KWin /KWin org.kde.KWin.previousDesktop The problem is that running these in a terminal or calling them from sxhkd for example does not allow wrapping around of desktops, say 1-2-3-4-1 doesn't work and I am stuck at 1. STEPS TO REPRODUCE 1. go to the last desktop 2. in a terminal run `qdbus org.kde.KWin /KWin org.kde.KWin.nextDesktop` 3. make sure the setting to wrap around desktops is enabled (in the Virtual Desktops settings) 4. nothing happens when command is entered. Going to desktop 1 doesn't work, going back to previous does work, unless is run on first desktop in which case it won't wrap to last. OBSERVED RESULT Virtual desktop wrapping doesn't work if the above qdbus commands are used. On the other hand if the shortcuts from Global Shortcuts > Kwin are used then everything is totally fine and works as expected. On that note, invoking the shortcut with qdbus like this instead, does work: qdbus org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.invokeShortcut 'Switch to Next Desktop' EXPECTED RESULT qdbus commands should act the same way as the global shortcuts/invoke shortcut command. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 5.4.13-3-MANJARO OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416667] gcc10 ppc64le impossible constraint in 'asm' in test_isa
https://bugs.kde.org/show_bug.cgi?id=416667 --- Comment #5 from Carl Love --- Created attachment 125376 --> https://bugs.kde.org/attachment.cgi?id=125376=edit Patch, fix assembler constraints The attached patch changes the ww and ws assembler constraints to wa. Please test this patch in your environment and let me know if it fixes all of the issues. I am only able to partially reproduce the errors you saw in the initial bug report. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 394204] Kirigami showPassiveNotification with action button hijacks touch events after timeout
https://bugs.kde.org/show_bug.cgi?id=394204 Postix changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||pos...@posteo.eu --- Comment #1 from Postix --- Is this still the case? Can anyone confirm? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407361] Notifications in the history lack interactive features that are in their pop-ups (click on body to jump to app, clickable buttons, draggable images, etc)
https://bugs.kde.org/show_bug.cgi?id=407361 --- Comment #9 from Postix --- Is there a way to support buttons in the history for GTK apps notifications? Background: I got an invite within a chat app (Dino) which was displayed as a notification popup with two buttons: Accept and reject. However, when I waited too long the notification was gone and the history gave me no chance to react to the invite. :-/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407361] Notifications in the history lack interactive features that are in their pop-ups (click on body to jump to app, clickable buttons, draggable images, etc)
https://bugs.kde.org/show_bug.cgi?id=407361 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416705] Proposed two new options for the Latte Dock
https://bugs.kde.org/show_bug.cgi?id=416705 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Michail Vourlakos --- Option 2 is already supported through Behavior, Floating options Option 1 sorry but I am not that fond of it, I consider Option 2 to be the best to use at all cases. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405811] Rotoscope - Crash when playing or dragging on timeline
https://bugs.kde.org/show_bug.cgi?id=405811 emohr changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #9 from emohr --- I think it's solved. Please try with the Kdenlive_Nightly_Appimage https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416704] Mode debug
https://bugs.kde.org/show_bug.cgi?id=416704 --- Comment #1 from alain.pouchard1...@free.fr --- By deduction, the processing time for exports comes from loading the album list. Would it be possible, if only in testing can only download the list of albums only on request. That would be much more efficient and timely. Thank you Kind regards -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416706] New: Krita last-used filter performance problem
https://bugs.kde.org/show_bug.cgi?id=416706 Bug ID: 416706 Summary: Krita last-used filter performance problem Product: krita Version: 4.2.7 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: kruth...@kruthers.net Target Milestone: --- Krita appears to be executing the last-used-filter every time you bring up the filter dialog, then throwing the result away, before allowing you to make adjustments. I only noticed this when the "halftone" filter was remembered as the last-used filter, because it's very slow to calculate. See this forum topic for more details if interested: https://forum.kde.org/viewtopic.php?f=139=164322 (ie. Halftone filter "virus" infected my files) Also, this might be a second bug, but the other reason this was so noticable is that krita would remember the last-used filter as "halftone" even after I used the HSV adjust filter many times. So every HSV adjustment I made would have a long wait while the halftone filter was run then discarded. Tell me if you want me to open a 2nd report for this. The last-used filter ends up saved in the kritarc prefs file, so the problem continues even after quitting and restarting krita. STEPS TO REPRODUCE 1. Make a new document, make a stroke or something visible 2. Bring up the HSV filter dialog with the sidebar, go to artistic -> halftone, let it preview, then click cancel 2a. You may have to save the result of the halftone, then undo it? Hard to tell exactly when krita gets stuck on this filter 3. Bring up the HSV filter again, and there will be a long wait with a blue progress bar on the layer OBSERVED RESULT Long wait when bringing up the HSV dialog. EXPECTED RESULT No waiting. krita version: krita-4.2.7-beta1-x86_64.appimage (also happened in 4.2.8 when halftone was saved in prefs) Ubuntu 18.04.3 LTS kde plasma version: 5.12.9 kde frameworks version: 5.44.0 qt version: 5.9.5 kernel version: 4.15.0-74-generic -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416705] New: Proposed two new options for the Latte Dock
https://bugs.kde.org/show_bug.cgi?id=416705 Bug ID: 416705 Summary: Proposed two new options for the Latte Dock Product: lattedock Version: git (master) Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tresdex...@gmail.com Target Milestone: --- Watching a promotional video for KDE Plasma 5.18 (https://vimeo.com/384051225), the user "KonqiDragon", proposed and demonstrated several possible layouts in Plasma, thanks to you and the Latte Dock, the specific layout of the image 01 (https://imgur.com/nV26cSR), it caught my attention, it makes use of the floating feature present in the latest version of the Latte Dock, both in the lower dock and in the upper panel. I liked the floating design of the top panel, I don't know any Operating System that adopts this same concept, in the bottom dock there are several, it is a trend. There is a downside to using this design on the top panel today, you lose useful screen space both vertically and horizontally, as shown in image 02 (https://imgur.com/3wrJVpz). To get around this, I propose two new options to the Latte Dock. The first one, would be when a window was maximized, the panel would be automatically positioned at the edge of the screen, with this option, the vertical screen waste is resolved, however the horizontal remains, as shown in image 03 (https: // imgur.com/9i4oQyi). The second option would have the same behavior as the first, but it would extend the panel on both sides of the screen, as shown in image 04 (https://imgur.com/xwk7lGi). Undoubtedly the second option (image 04), is the one that has the best use of the screen, however users with large screens can choose to preserve the rounded corners, possible with the option of image 03. Both options are very important especially for people who have notebooks with small screens, as is my case. :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416704] New: Mode debug
https://bugs.kde.org/show_bug.cgi?id=416704 Bug ID: 416704 Summary: Mode debug Product: digikam Version: 7.0.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Versioning Assignee: digikam-bugs-n...@kde.org Reporter: alain.pouchard1...@free.fr Target Milestone: --- Hello I downloaded the debug version. I would have liked to generate a log to send you but I have not figured out how to do it. Thank you Kind regards -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416703] New: Search results are hard to find on yellow-highlighted, annotated pdf text
https://bugs.kde.org/show_bug.cgi?id=416703 Bug ID: 416703 Summary: Search results are hard to find on yellow-highlighted, annotated pdf text Product: okular Version: 1.8.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: tterrani...@gmail.com Target Milestone: --- SUMMARY When searching for text that is highlighted in yellow using PDF annotations, it is hard to find the search result as Okular highlights the search result also in yellow. It would be great if either: - the search highlighting color was configurable in the search "toolbar" - the search highlighting color was automatically set to a color contrasting the background. A similar request is #384267 but I am not sure it is the optimal solution, as the annotation color can still conflict with the systems settings color. -- You are receiving this mail because: You are watching all bug changes.
[libkface] [Bug 416266] digikam crashes during face detection
https://bugs.kde.org/show_bug.cgi?id=416266 --- Comment #6 from Thomas Beckler --- My pictures are stored on a NAS, so I was able to identify the picture by using Wireshark. It is a stitched panorama (using PTGui) with 32969x36403 pixel (1200.17Mpx) / 146 MByte. You can find the image at https://web.tresorit.com/l#GlHC02W2ld3zPL4nOJg9WA -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416702] New: Plasma desktop crashed at Configure Desktop opening
https://bugs.kde.org/show_bug.cgi?id=416702 Bug ID: 416702 Summary: Plasma desktop crashed at Configure Desktop opening Product: plasmashell Version: 5.17.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: msdobre...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.5) Qt Version: 5.12.5 Frameworks Version: 5.65.0 Operating System: Linux 5.3.0-sabayon x86_64 Distribution: Sabayon/Linux -- Information about the crash: - What I was doing when the application crashed: I was setting a desktop wallpaper. - Custom settings of the application: Not yet, it crashed at Configure Desktop opening. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #6 0x7ff0f528edb0 in () at /usr/lib64/libQt5Widgets.so.5 #7 0x7ff0f52ba492 in QWidget::insertAction(QAction*, QAction*) () at /usr/lib64/libQt5Widgets.so.5 #8 0x7ff0f52ba5c6 in QWidget::addActions(QList) () at /usr/lib64/libQt5Widgets.so.5 #9 0x7ff0ddef75ab in () at /usr/lib64/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #10 0x7ff0ddef8123 in () at /usr/lib64/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #11 0x7ff0f61c2e28 in QQuickItem::event(QEvent*) () at /usr/lib64/libQt5Quick.so.5 #12 0x7ff0ddeee6f6 in () at /usr/lib64/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #13 0x7ff0f52835b1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7ff0f528ab90 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x7ff0f47d33d2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #16 0x7ff0f61dc76c in QQuickWindowPrivate::deliverMatchingPointsToItem(QQuickItem*, QQuickPointerEvent*, bool) () at /usr/lib64/libQt5Quick.so.5 #17 0x7ff0f61dd682 in QQuickWindowPrivate::deliverPressOrReleaseEvent(QQuickPointerEvent*, bool) () at /usr/lib64/libQt5Quick.so.5 #18 0x7ff0f61ddafd in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () at /usr/lib64/libQt5Quick.so.5 #19 0x7ff0f61debcb in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () at /usr/lib64/libQt5Quick.so.5 #20 0x7ff0f61df90f in QQuickWindowPrivate::handleMouseEvent(QMouseEvent*) () at /usr/lib64/libQt5Quick.so.5 #21 0x7ff0f4b9ebf5 in QWindow::event(QEvent*) () at /usr/lib64/libQt5Gui.so.5 #22 0x7ff0f61e0bfb in QQuickWindow::event(QEvent*) () at /usr/lib64/libQt5Quick.so.5 #23 0x7ff0f52835b1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #24 0x7ff0f528ab90 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #25 0x7ff0f47d33d2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #26 0x7ff0f4b94f4b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib64/libQt5Gui.so.5 #27 0x7ff0f4b96425 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib64/libQt5Gui.so.5 #28 0x7ff0f4b73dbb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib64/libQt5Gui.so.5 #29 0x7ff0e1d134ea in () at /usr/lib64/libQt5XcbQpa.so.5 #30 0x7ff0f23115ae in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #31 0x7ff0f2311848 in () at /usr/lib64/libglib-2.0.so.0 #32 0x7ff0f23118dc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #33 0x7ff0f4824913 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #34 0x7ff0f47d22eb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #35 0x7ff0f47da132 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #36 0x55a651aa6223 in () #37 0x7ff0f41d0e4b in __libc_start_main () at /lib64/libc.so.6 #38 0x55a651aa664a in _start () [Inferior 1 (process 1554) detached] Possible duplicates by query: bug 416619, bug 416559, bug 416549, bug 416540, bug 416521. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416701] Can't use dead keys to insert accents
https://bugs.kde.org/show_bug.cgi?id=416701 Nate Graham changed: What|Removed |Added Component|general |general Target Milestone|--- |1.0 Version|unspecified |5.17.5 CC||n...@kde.org, ||plasma-b...@kde.org Product|kde |plasmashell Assignee|unassigned-b...@kde.org |k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416692] yes
https://bugs.kde.org/show_bug.cgi?id=416692 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Nate Graham --- I'm afraid there isn't any information in this bug report. It looks like Discover crashed, but there's no information about what you were doing or a backtrace. Please see https://community.kde.org/Get_Involved/Issue_Reporting#Crash_reports_must_include_backtraces -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 416694] Spectacle does not start using PrintScreen button after update
https://bugs.kde.org/show_bug.cgi?id=416694 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 410925 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 410925] Spectacle does not open after latest KDE-Neon update
https://bugs.kde.org/show_bug.cgi?id=410925 Nate Graham changed: What|Removed |Added CC||kdeb...@staznosti.sk --- Comment #8 from Nate Graham --- *** Bug 416694 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416695] Chord keyboard shortcuts that begin with Alt+D all open the desktop settings window
https://bugs.kde.org/show_bug.cgi?id=416695 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org Severity|minor |normal Summary|Context menu in Desktop |Chord keyboard shortcuts |Layout is confusing |that begin with Alt+D all ||open the desktop settings ||window -- You are receiving this mail because: You are watching all bug changes.
