[krita] [Bug 432685] macOS: Krita Finder menu item not localized/localizable despite non-English system locale
https://bugs.kde.org/show_bug.cgi?id=432685 --- Comment #10 from vanyossi --- Git commit ab9b603ff4bd3b13fd47e525c8a47c59df39d8f8 by Ivan Yossi. Committed on 22/09/2022 at 05:59. Pushed by ivany into branch 'master'. Attempt to fix missing localization on macOS app menu M +10 -0packaging/macos/osxdeploy.sh https://invent.kde.org/graphics/krita/commit/ab9b603ff4bd3b13fd47e525c8a47c59df39d8f8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432685] macOS: Krita Finder menu item not localized/localizable despite non-English system locale
https://bugs.kde.org/show_bug.cgi?id=432685 --- Comment #9 from vanyossi --- I remember trying this before, but never dig enough to come with a proper fix. On my system at least the empty .lproj folders on krita does nothing, however the folder for each location is required so I might as well start with that :). locversion.plist do work to change "krita" to "crayola" when I select spanish, however the other menu entries remain in english. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457311] Color picker no longer sets left-clicked color to clipboard
https://bugs.kde.org/show_bug.cgi?id=457311 ratijas changed: What|Removed |Added Status|RESOLVED|REPORTED CC||m...@ratijas.tk, ||qydwhotm...@gmail.com Resolution|DUPLICATE |--- --- Comment #2 from ratijas --- Color Picker plasmoid has recently had a refactoring. Though I doubt it was shipped with 5.25 update. Maybe we really lost the defaults in that change. PS unmarking as duplicate, because clearly these are two entirely different bugreports. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433059] "Active/Inactive Titlebar" colors are visible and editable but confusingly unused when Header colors are present
https://bugs.kde.org/show_bug.cgi?id=433059 --- Comment #13 from Hirad --- (In reply to Nate Graham from comment #12) > Yeah, because nobody's fixed this yet. :) Shouldn't the developer who added the header section in first place and forgot to add inactive color to fix it? Or anyone that is in charge of maintaining system settings or KColorSchemeEditor to be specific. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455538] Option to keep floating panels -floating- when windows are maximized
https://bugs.kde.org/show_bug.cgi?id=455538 Subham Poddar changed: What|Removed |Added CC||raninepa...@gmail.com --- Comment #2 from Subham Poddar --- I would like to state that I also second this request. It would be helpful if there was a option for floating panel to be always floating, instead of becoming like normal panel when window is maximized regardless whether Kwin Script "Maximized Window Gap" is used. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 458112] info center breaks few moments after open
https://bugs.kde.org/show_bug.cgi?id=458112 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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 458095] Option for manual inhibition to expire after a time, like DND mode
https://bugs.kde.org/show_bug.cgi?id=458095 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459062] Shapes darken when selected
https://bugs.kde.org/show_bug.cgi?id=459062 Bug Janitor Service changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #15 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 457908] NeoChat crashes if you do not provide a file description
https://bugs.kde.org/show_bug.cgi?id=457908 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458488] View > Show Canvas Only exits fullscreen on Mac when green button used
https://bugs.kde.org/show_bug.cgi?id=458488 --- Comment #4 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.
[kwin] [Bug 454425] Windows are resized to a minimal height if I unplug external monitors
https://bugs.kde.org/show_bug.cgi?id=454425 --- Comment #15 from Peter Tselios --- (In reply to Grzegorz from comment #14) > looks from duplicate to https://bugs.kde.org/show_bug.cgi?id=452118 I will be able to see if this is somehow fixed after the latest commits regarding other bugs about position of the screens etc and Fedora brings those packages. I also promise to find some time to test different scenarios, like changing screen positions, primary screen etc. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447116] kwin crashes after pressing alt-tab twice
https://bugs.kde.org/show_bug.cgi?id=447116
Fushan Wen changed:
What|Removed |Added
CC||qydwhotm...@gmail.com
--- Comment #12 from Fushan Wen ---
Got a crash after trying to open Overview effect, but cannot reproduce again
after kwin_x11 was restarted.
(gdb) bt
#0 __GI___pthread_sigmask (how=1, newmask=, oldmask=0x0) at
pthread_sigmask.c:43
#1 0x7fbaef5edb2d in __GI___sigprocmask (how=,
set=, oset=) at
../sysdeps/unix/sysv/linux/sigprocmask.c:25
#2 0x7fbaf2fe788b in KCrash::setCrashHandler(void (*)(int))
(handler=handler@entry=0x0) at
/usr/src/debug/kcrash-5.99.0git.20220917T130720~d2f3085-ku.2.2.x86_64/src/kcrash.cpp:415
#3 0x7fbaf2fe9da6 in KCrash::defaultCrashHandler(int) (sig=11) at
/usr/src/debug/kcrash-5.99.0git.20220917T130720~d2f3085-ku.2.2.x86_64/src/kcrash.cpp:632
#4 0x7fbaef5ed910 in () at /lib64/libc.so.6
#5 QScopedPointer
>::operator->() const (this=0x8) at
/usr/include/qt5/QtCore/qscopedpointer.h:116
#6 qGetPtrHelper > >(QScopedPointer >&) (ptr=...) at
/usr/include/qt5/QtCore/qglobal.h:1143
#7 QSGTexture::d_func() (this=0x0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-ku.1.1.x86_64/src/quick/scenegraph/coreapi/qsgtexture.h:57
#8 QSGTexture::setFiltering(QSGTexture::Filtering) (this=0x0,
filter=filter@entry=QSGTexture::Linear) at
/usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-ku.1.1.x86_64/src/quick/scenegraph/coreapi/qsgtexture.cpp:576
#9 0x7fbaf2bd4606 in
KWin::ThumbnailTextureProvider::setTexture(std::shared_ptr
const&) (this=0x26f7560, nativeTexture=std::shared_ptr (use
count 2, weak count 0) = {...}) at /usr/include/c++/12/bits/unique_ptr.h:191
#10 0x7fbaf2bd4d03 in KWin::WindowThumbnailItem::updatePaintNode(QSGNode*,
QQuickItem::UpdatePaintNodeData*) (this=0x253ff60, oldNode=0x0) at
/mnt/data/home/qydw/Develop/KDE/Plasma/kwin/src/scripting/windowthumbnailitem.cpp:227
#11 0x7fbaf25887c8 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*)
(this=0x16f6270, item=0x253ff60) at
/usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-ku.1.1.x86_64/src/quick/items/qquickwindow.cpp:3871
#12 0x7fbaf2588dcb in QQuickWindowPrivate::updateDirtyNodes()
(this=this@entry=0x16f6270) at
/usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-ku.1.1.x86_64/src/quick/items/qquickwindow.cpp:3616
#13 0x7fbaf258a93d in QQuickWindowPrivate::syncSceneGraph()
(this=0x16f6270) at
/usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-ku.1.1.x86_64/src/quick/items/qquickwindow.cpp:523
#14 0x7fbaf2615b49 in QQuickRenderControl::sync() (this=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-ku.1.1.x86_64/src/quick/items/qquickrendercontrol.cpp:297
#15 0x7fbaf0781806 in KWin::OffscreenQuickView::update()
(this=0x7fba941040f0) at
/mnt/data/home/qydw/Develop/KDE/Plasma/kwin/src/libkwineffects/kwinoffscreenquickview.cpp:296
#16 KWin::OffscreenQuickView::update() (this=this@entry=0x7fba941040f0) at
/mnt/data/home/qydw/Develop/KDE/Plasma/kwin/src/libkwineffects/kwinoffscreenquickview.cpp:261
#17 0x7fbaf0783e00 in
KWin::QuickSceneEffect::prePaintScreen(KWin::ScreenPrePaintData&,
std::chrono::duration >) (this=,
data=, presentTime=...) at
/mnt/data/home/qydw/Develop/KDE/Plasma/kwin/src/libkwineffects/kwinquickeffect.cpp:313
#18 0x7fbaf2b2b561 in
KWin::EffectsHandlerImpl::prePaintScreen(KWin::ScreenPrePaintData&,
std::chrono::duration >) (this=0x13fbec0,
data=, presentTime=...) at
/mnt/data/home/qydw/Develop/KDE/Plasma/kwin/src/effects.cpp:388
#19 0x7fbaf2ba7d01 in KWin::Scene::prePaint(KWin::Output*) (this=0x13a33d0,
output=) at
/mnt/data/home/qydw/Develop/KDE/Plasma/kwin/src/scene.cpp:291
#20 0x7fbaf2aea53f in KWin::Compositor::prePaintPass(KWin::RenderLayer*)
(this=this@entry=0x1051860, layer=layer@entry=0x13ea160) at
/mnt/data/home/qydw/Develop/KDE/Plasma/kwin/src/composite.cpp:682
#21 0x7fbaf2aed88f in KWin::Compositor::composite(KWin::RenderLoop*)
(this=0x1051860, renderLoop=0xfe2390) at
/mnt/data/home/qydw/Develop/KDE/Plasma/kwin/src/composite.cpp:626
#22 0x7fbaf2aee1ab in KWin::X11Compositor::composite(KWin::RenderLoop*)
(this=0x1051860, renderLoop=0xfe2390) at
/mnt/data/home/qydw/Develop/KDE/Plasma/kwin/src/composite.cpp:906
#23 0x7fbaf123ce6f in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffe39135ac0, r=0x1051860, this=0x105cb90) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#24 doActivate(QObject*, int, void**) (sender=0xfe2390, signal_index=5,
argv=0x7ffe39135ac0) at kernel/qobject.cpp:3886
#25 0x7fbaf123622f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7fbaf2ee9440
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffe39135ac0)
at kernel/qobject.cpp:3946
#26 0x7fbaf2aa9952 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*)
(this=, _t1=) at
[dolphin] [Bug 459505] New: Dolphin crashed while browsing NFS folder
https://bugs.kde.org/show_bug.cgi?id=459505 Bug ID: 459505 Summary: Dolphin crashed while browsing NFS folder Classification: Applications Product: dolphin Version: 22.04.3 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: d7ghrr...@mozmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.04.3) Qt Version: 5.15.4 Frameworks Version: 5.97.0 Operating System: Linux 5.19.0-1-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux bookworm/sid DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: I was browsing NFS folder and clicked sort by Modified, started scrolling. One second later Dolphin crashed. The crash does not seem to be reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 0x7fe9d1a3a83c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x7fe9d19eea52 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x7fe9d19d9469 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7fe9d1a2ec18 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x7fe9d1ac9c62 in __fortify_fail () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x7fe9d1ac9c40 in __stack_chk_fail () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x7fe9d3abb705 in KFileItem::overlays() const () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #11 0x7fe9d40e8347 in KFileItemModelRolesUpdater::rolesData(KFileItem const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #12 0x7fe9d40eb883 in KFileItemModelRolesUpdater::slotGotPreview(KFileItem const&, QPixmap const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #13 0x7fe9d20b49af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fe9d3d811d7 in KIO::PreviewJob::gotPreview(KFileItem const&, QPixmap const&) () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #15 0x7fe9d3d8560b in ?? () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #16 0x7fe9d3d8677a in ?? () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #17 0x7fe9d20b49af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fe9d3b27194 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #19 0x7fe9d20b49af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fe9d3af8dd2 in KIO::SlaveInterface::data(QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #21 0x7fe9d3afb24a in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #22 0x7fe9d3af9696 in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #23 0x7fe9d3afe949 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #24 0x7fe9d20b49af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fe9d20a92a0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fe9d2b4ef4e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7fe9d207d618 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7fe9d20805b1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fe9d20d5ae3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7fe9cfaf2729 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7fe9cfaf29b8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7fe9cfaf2a4c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7fe9d20d51c6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7fe9d207c09b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7fe9d2084206 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x562311ab5d55 in ?? () #37 0x7fe9d19da20a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #38 0x7fe9d19da2bc in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #39 0x562311ab612a in ?? () [Inferior 1 (process 2816942) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 459504] Skanlite Crash
https://bugs.kde.org/show_bug.cgi?id=459504 Ritche Gerona changed: What|Removed |Added Platform|Compiled Sources|Snap -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 459504] New: Skanlite Crash
https://bugs.kde.org/show_bug.cgi?id=459504 Bug ID: 459504 Summary: Skanlite Crash Classification: Applications Product: Skanlite Version: 22.04.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: ritchegero...@gmail.com Target Milestone: --- Application: skanlite (22.04.3) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.95.0 Operating System: Linux 5.17.0-1016-oem x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.1 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Restart the application - Unusual behavior I noticed: Pop-up and keep notifying that the Skanlite crash The crash can be reproduced sometimes. -- Backtrace: Application: Skanlite (skanlite), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140239381341760) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140239381341760) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140239381341760, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f8c1302b476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f8c130117f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f8c130726f6 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8c131c4943 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:155 #10 0x7f8c1311f76a in __GI___fortify_fail (msg=msg@entry=0x7f8c131c48e9 "buffer overflow detected") at ./debug/fortify_fail.c:26 #11 0x7f8c1311e0c6 in __GI___chk_fail () at ./debug/chk_fail.c:28 #12 0x7f8c1306a95f in _IO_str_chk_overflow (fp=, c=) at ./libio/iovsprintf.c:35 #13 0x7f8c13076eb4 in __GI__IO_default_xsputn (n=, data=, f=) at ./libio/genops.c:399 #14 __GI__IO_default_xsputn (f=0x7f8c06818600, data=, n=15) at ./libio/genops.c:370 #15 0x7f8c1306008c in outstring_func (done=17, length=15, string=0x7f8c06818870 "192.168.254.126", s=0x7f8c06818600) at ../libio/libioP.h:947 #16 __vfprintf_internal (s=s@entry=0x7f8c06818600, format=format@entry=0x7f8bf1ea7142 "%s_%s", ap=ap@entry=0x7f8c06818740, mode_flags=mode_flags@entry=6) at ./stdio-common/vfprintf-internal.c:1517 #17 0x7f8c1306aa09 in __vsprintf_internal (string=0x7f8bfc042e70 "MF642C/643C/644C_192.168.254.12", maxlen=, format=0x7f8bf1ea7142 "%s_%s", args=args@entry=0x7f8c06818740, mode_flags=6) at ./libio/iovsprintf.c:95 #18 0x7f8c1311dbe1 in ___sprintf_chk (s=, flag=, slen=, format=) at ./debug/sprintf_chk.c:40 #19 0x7f8bf1e89e36 in ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1 #20 0x7f8bf1ea5983 in ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1 #21 0x7f8bf1ea62f6 in sanei_bjnp_find_devices () from /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1 #22 0x7f8bf1e9701f in sanei_pixma_collect_devices () from /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1 #23 0x7f8bf1e95055 in sane_pixma_get_devices () from /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1 #24 0x7f8c12fb6d3a in sane_dll_get_devices () from /lib/x86_64-linux-gnu/libsane.so.1 #25 0x7f8c14f37476 in ?? () from /lib/x86_64-linux-gnu/libKF5Sane.so.5 #26 0x7f8c13507ca1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f8c1307db43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #28 0x7f8c1310fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 3 (Thread 0x7f8c0cd09640 (LWP 15818) "QDBusConnection"): #1 0x7f8c11e8c185 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8c11e8d7eb in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8c11ee25c3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8c11e8b3c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8c1374e12e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8c136f375b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8c13506af2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8c148b0f0b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f8c13507ca1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f8c1307db43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #11 0x7f8c1310fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 2 (Thread 0x7f8c0e5eb640 (LWP 15817) "QXcbEventQueue"): #1 0x7f8c117587e2 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f8c1175a22c in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f8c0e730d08 in ?? () from
[plasmashell] [Bug 435715] Plasma crashes in SystemTrayContainer::internalSystrayChanged() on start
https://bugs.kde.org/show_bug.cgi?id=435715 --- Comment #7 from Fushan Wen --- Created attachment 152321 --> https://bugs.kde.org/attachment.cgi?id=152321=edit New crash information added by DrKonqi plasmashell (5.26.80) using Qt 5.15.5 After updating the whole system today, plasmashell always crashed on startup. -- Backtrace (Reduced): #6 QQmlRefPointer::QQmlRefPointer(QQmlRefPointer const&) (other=..., this=this@entry=0x7f1027ffd410) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:152 #7 QQmlType::QQmlType(QQmlType const&) (this=this@entry=0x7f1027ffd410) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-ku.1.1.x86_64/src/qml/qml/qqmltype.cpp:121 #8 0x7f105a5ad94b in QQmlPropertyCacheCreator::propertyCacheForObject(QmlIR::Object const*, QQmlBindingInstantiationContext const&, QQmlError*) const (this=this@entry=0x7f1027ffd7b0, obj=obj@entry=0x7f10049abd68, context=..., error=error@entry=0x7f1027ffd4a8) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:333 #9 0x7f105a5b08a0 in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&, QQmlPropertyCacheCreator::VMEMetaObjectIsRequired) (this=this@entry=0x7f1027ffd7b0, objectIndex=, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:264 #10 0x7f105a5b0ab9 in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&, QQmlPropertyCacheCreator::VMEMetaObjectIsRequired) (this=0x7f1027ffd7b0, objectIndex=objectIndex@entry=0, context=, isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at /usr/include/qt5/QtCore/qendian.h:290 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435715] Plasma crashes in SystemTrayContainer::internalSystrayChanged() on start
https://bugs.kde.org/show_bug.cgi?id=435715 Fushan Wen changed: What|Removed |Added CC||qydwhotm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459490] SELinux is preventing /app/bin/krita from execmod access on the file /memfd:JITCode:/app/lib/libQt5Qml.so.5
https://bugs.kde.org/show_bug.cgi?id=459490 --- Comment #11 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1592 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459490] SELinux is preventing /app/bin/krita from execmod access on the file /memfd:JITCode:/app/lib/libQt5Qml.so.5
https://bugs.kde.org/show_bug.cgi?id=459490 amyspark changed: What|Removed |Added Ever confirmed|0 |1 Assignee|krita-bugs-n...@kde.org |a...@amyspark.me Status|NEEDSINFO |ASSIGNED Resolution|WAITINGFORINFO |--- --- Comment #10 from amyspark --- I've got the branch ready, will try to build it tomorrow. Sending the draft MR just in case. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459499] The possibility to disable persons
https://bugs.kde.org/show_bug.cgi?id=459499 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412393] Scale Image dialogue pops up on the wrong screen when crop/transform was used before
https://bugs.kde.org/show_bug.cgi?id=412393 --- Comment #15 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1591 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455913] [Wayland + Nvidia] Krunner stops showing after opening / closing it a few times
https://bugs.kde.org/show_bug.cgi?id=455913 marvelren...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #9 from marvelren...@gmail.com --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 260986] Akregator crashes on KDE shutdown
https://bugs.kde.org/show_bug.cgi?id=260986 Chris Samuel changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #14 from Chris Samuel --- Hi Justin, I believe this was solved a few years ago as per this comment: https://bugs.kde.org/show_bug.cgi?id=260986#c12 I'll try and close this now. All the best, Chris -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459503] windows disappear after alt+tabing quick on krunner
https://bugs.kde.org/show_bug.cgi?id=459503 o.x...@protonmail.com changed: What|Removed |Added Summary|windows disappear after |windows disappear after |alt+tabing quick|alt+tabing quick on krunner -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459503] windows disappear after alt+tabing quick
https://bugs.kde.org/show_bug.cgi?id=459503 o.x...@protonmail.com changed: What|Removed |Added Summary|windows disappear after |windows disappear after |switch |alt+tabing quick -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459503] New: windows disappear after switch
https://bugs.kde.org/show_bug.cgi?id=459503 Bug ID: 459503 Summary: windows disappear after switch Classification: Plasma Product: kwin Version: 5.25.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: o.x...@protonmail.com Target Milestone: --- Hello, Each time i have opened krunner and runned a program, if i quickly alt+tab, all windows disappear It only happens if i do it before the program's window appear When you alt+tab quick right after running a program there most be a bug that breaks something And after this happen i can not switch to any window anymore, i can select them but not switch Thanks! STEPS TO REPRODUCE 1. Open krunner 2. Type a program name and run it 3. Before the program window appear switch to another window by shortcut 4. If you wanna catch the bug, then you have to be faster then... him! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413104] Left-click mouse actions on Desktop don't work in Desktop layout, works fine in Folderview
https://bugs.kde.org/show_bug.cgi?id=413104 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 167644] Alt+tab to show desktop
https://bugs.kde.org/show_bug.cgi?id=167644 o.x...@protonmail.com changed: What|Removed |Added CC||o.x...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459502] when i disconnect and reconnect external monitor kwin crash
https://bugs.kde.org/show_bug.cgi?id=459502 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 Random Guy changed: What|Removed |Added CC||ericgreenwood...@gmail.com --- Comment #13 from Random Guy --- I believe I am having this same issue, in KDE version 5.25 on Wayland. I have a PC with 2 monitors connected, and I have a projector on which I watch films/TV shows. When I turn off the monitors and connect the projector the display sometimes freezes without the rest of the system crashing - music remains playing indefinitely in the background. The same crash also occasionally happens when waking from sleep. I presume the fix mentioned in this thread is enough for most use cases, however I have one old monitor and one new monitor so my main setup is 1680*1050 @ 60hz on DVI and a gaming monitor using 1920*1050 @ up to 144hz (with AMD freesync) on HDMI so I think it is testing this fix quite hard (along with many other parts of the system - it took me a while to get it working at all). It is not a dealbreaker as I can restart and retry when it breaks which is about 1 in 3 attempts, however I wanted to log the fact that this is still an issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459490] SELinux is preventing /app/bin/krita from execmod access on the file /memfd:JITCode:/app/lib/libQt5Qml.so.5
https://bugs.kde.org/show_bug.cgi?id=459490 --- Comment #9 from amyspark --- There's no 5.15 AppImage as it's a Qt version we don't support it officially. But I think I found the reason for this issue, Qt truly fixed their JIT much later: https://codereview.qt-project.org/c/qt/qtdeclarative/+/329522 Unfortunately it's a mix of three different Qt branches, which makes it a royal mess to cherry-pick safely. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459498] Saving .psd shows a mistaken warning about fractional frame durations
https://bugs.kde.org/show_bug.cgi?id=459498 amyspark changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/7c68d0750 ||588eb3f3417f83db756b3d37dbd ||1859 --- Comment #1 from amyspark --- Git commit 7c68d0750588eb3f3417f83db756b3d37dbd1859 by L. E. Segovia. Committed on 21/09/2022 at 23:17. Pushed by lsegovia into branch 'master'. impex: don't check for framerates if the image isn't animated M +4-0libs/impex/IntegralFrameDuration.h https://invent.kde.org/graphics/krita/commit/7c68d0750588eb3f3417f83db756b3d37dbd1859 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 441256] Feature request: switch to force single instance
https://bugs.kde.org/show_bug.cgi?id=441256 --- Comment #5 from Axel --- Thank you -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459502] when i disconnect and reconnect external monitor kwin crash
https://bugs.kde.org/show_bug.cgi?id=459502 Ehsan Tork changed: What|Removed |Added Target Milestone|--- |5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459502] New: when i disconnect and reconnect external monitor kwin crash
https://bugs.kde.org/show_bug.cgi?id=459502
Bug ID: 459502
Summary: when i disconnect and reconnect external monitor kwin
crash
Classification: Plasma
Product: kwin
Version: 5.25.5
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: journaleh...@gmail.com
Target Milestone: ---
Flags: Wayland+, X11-, Catalyst-, dpi+, Gallium3D-, Intel+,
Mesa+, nouveau-, NVIDIA-, r300g-, r600g-,
Decision-Required-, Triaged-, ReviewRequest-
SUMMARY
When I disconnect monitor and then connect external monitor via HDMI and resize
or move any window, suddenly all application closed and kwin crash with akonadi
server crash on me. its so annoying because i cant logout i only can kill all
apps from current session with killall --user username .
STEPS TO REPRODUCE
1. disconnect monitor in wayland with different dpi scale
2. connect monitor again with hdmi or vga
3. move or resize window in second (external monitor)
OBSERVED RESULT
Crash kwin, all apllication closed and ther's no way to logout,reboot other
than that everything work perfect after that and i must rerun evey apps like
latte-dock and conky , but for logout i must killall all apps in current
user
EXPECTED RESULT
I expect everything work normall :)
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro/Arch KDE plasma 5.25.5
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
ADDITIONAL INFORMATION
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
[KCrash Handler]
#4 0x5638aa051563 in ?? ()
#5 0x7fc1a07ba2f0 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#6 0x7fc1a079695c in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#7 0x7fc1a0797483 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#8 0x7fc1a07dd478 in ?? () from /usr/lib/libQt5Core.so.5
#9 0x7fc19eb38b2b in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#10 0x7fc19eb8ee79 in ?? () from /usr/lib/libglib-2.0.so.0
#11 0x7fc19eb36252 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#12 0x7fc1a07e125c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#13 0x7fc1a078f11c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#14 0x7fc1a0799c49 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#15 0x5638aa046edd in ?? ()
#16 0x7fc1a00ee2d0 in ?? () from /usr/lib/libc.so.6
#17 0x7fc1a00ee38a in __libc_start_main () from /usr/lib/libc.so.6
#18 0x5638aa049c85 in ?? ()
[Inferior 1 (process 5803) detached]
--
Application: Latte Dock (latte-dock), signal: Segmentation fault
[KCrash Handler]
#4 0x77e4462d in KWayland::Client::PlasmaWindowManagement::windows()
const () from /usr/lib/libKF5WaylandClient.so.5
#5 0x55758ffa in Latte::WindowSystem::WaylandInterface::winIdFor
(this=0x55b0cee0, appId=..., title=...) at
/home/ehsant/Codes/GitHub/Espresso-dock/app/wm/waylandinterface.cpp:607
#6 0x5570ad69 in Latte::ViewPart::Positioner::updateWaylandId
(this=0x55ca49c0) at
/home/ehsant/Codes/GitHub/Espresso-dock/app/view/positioner.cpp:236
#7 0x55715264 in QtPrivate::FunctorCall,
QtPrivate::List<>, void, void (Latte::ViewPart::Positioner::*)()>::call(void
(Latte::ViewPart::Positioner::*)(), Latte::ViewPart::Positioner*, void**)
(f=(void (Latte::ViewPart::Positioner::*)(Latte::ViewPart::Positioner * const))
0x5570acaa ,
o=0x55ca49c0, arg=0x7fffc0d0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:152
#8 0x55715008 in QtPrivate::FunctionPointer::call, void>(void
(Latte::ViewPart::Positioner::*)(), Latte::ViewPart::Positioner*, void**)
(f=(void (Latte::ViewPart::Positioner::*)(Latte::ViewPart::Positioner * const))
0x5570acaa ,
o=0x55ca49c0, arg=0x7fffc0d0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:185
#9 0x55714c6f in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1,
this_=0x563cdf80, r=0x55ca49c0, a=0x7fffc0d0, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:418
#10 0x7537e0d1 in ?? () from /usr/lib/libQt5Core.so.5
#11 0x758ae24a in QWindow::windowTitleChanged(QString const&) () from
/usr/lib/libQt5Gui.so.5
#12 0x557175da in operator() (__closure=0x55ca5b20) at
/home/ehsant/Codes/GitHub/Espresso-dock/app/view/view.cpp:133
#13 0x557226c7 in QtPrivate::FunctorCall,
QtPrivate::List<>, void, Latte::View::View(Plasma::Corona*, QScreen*,
bool):: >::call(struct {...} &, void **) (f=..., arg=0x7fffc320)
at
[Discover] [Bug 459496] Error : Unable to load applications Please check Internet connectivity
https://bugs.kde.org/show_bug.cgi?id=459496 --- Comment #3 from Jack --- Hello Aleix Pol , just to be complete, I type this info on the same laptop as where I have the Discover issue so Internet connection is fine. Kind regards, Jack -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 459496] Error : Unable to load applications Please check Internet connectivity
https://bugs.kde.org/show_bug.cgi?id=459496 --- Comment #2 from Jack --- Hello Aleix Pol , The output of the nmcli on my laptop while using the LAN connection : jack@jv:~$ nmcli eno1: connected to Wired connection 1 "Realtek RTL8111/8168/8411" ethernet (r8169), 2C:41:38:60:80:23, hw, mtu 1500 ip4 default, ip6 default inet4 192.168.2.27/24 route4 192.168.2.0/24 metric 100 route4 default via 192.168.2.254 metric 100 route4 169.254.0.0/16 metric 1000 inet6 2a02:a46b:30:1:47cf:b61f:d89d:595a/64 inet6 fe80::730c:ba4a:4d0:c2bc/64 route6 fe80::/64 metric 1024 route6 2a02:a46b:30:1::/64 metric 100 route6 default via fe80::26d3:f2ff:fe97:a394 metric 100 wlo1: unavailable "Intel Centrino 1030" wifi (iwlwifi), AC:72:89:C3:2D:05, sw disabled, hw, mtu 1500 lo: unmanaged "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536 DNS configuration: servers: 192.168.2.13 192.168.2.254 domains: home interface: eno1 servers: fe80::26d3:f2ff:fe97:a394 interface: eno1 Use "nmcli device show" to get complete information about known devices and "nmcli connection show" to get an overview on active connection profiles. Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details. jack@jv:~$ date do 22 sep 2022 0:34:20 CEST jack@jv:~$ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459490] SELinux is preventing /app/bin/krita from execmod access on the file /memfd:JITCode:/app/lib/libQt5Qml.so.5
https://bugs.kde.org/show_bug.cgi?id=459490 --- Comment #8 from Long Vu --- (In reply to amyspark from comment #6) > Does AlmaLinux also have SELinux enabled by default? Yes, I spun up AlmaLinux 9 on a VM and can repo the issue mentioned there using the AppImage. I can also verify SELinux is enabled out of the box. I'm not sure if the policy shipped by AlmaLinux and CentOS differ from the Fedora ones as Fedora works fine. SELinux status: enabled SELinuxfs mount:/sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 33 > Hm, a better question is: if you run Krita under SELinux with Qt 5.15, does > it show the issue? Is there a AppImage of Krita using Qt 5.15 for testing? The distro repos don't seem to include Krita. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439748] Composite and transform keyframe timestamps are off
https://bugs.kde.org/show_bug.cgi?id=439748 Julius Künzel changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/mult ||imedia/kdenlive/commit/2466 ||82a095700df3081b258bb062365 ||9209336b8 Resolution|--- |FIXED Version Fixed In||22.08.2 --- Comment #6 from Julius Künzel --- Git commit 246682a095700df3081b258bb0623659209336b8 by Julius Künzel. Committed on 21/09/2022 at 22:05. Pushed by jlskuz into branch 'release/22.08'. Fix wrong timecode offset in keyframewidget of transitions FIXED-IN: 22.08.2 M +0-3src/assets/view/widgets/keyframewidget.cpp https://invent.kde.org/multimedia/kdenlive/commit/246682a095700df3081b258bb0623659209336b8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459501] New: Application Style crash System Settings when clicked
https://bugs.kde.org/show_bug.cgi?id=459501 Bug ID: 459501 Summary: Application Style crash System Settings when clicked Classification: Applications Product: systemsettings Version: 5.25.5 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bud...@gmail.com Target Milestone: --- Application: systemsettings (5.25.5) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.9-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: System Settings / Global Theme / Application Style, crash the shole System Settings window when clicked, reverting theme to defaults dont fix the issue The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 0x7f4306aba49c in () at /usr/lib/libc.so.6 #5 0x7f4306a6a958 in raise () at /usr/lib/libc.so.6 #6 0x7f4306a5453d in abort () at /usr/lib/libc.so.6 #7 0x7f4306ef1ede in qt_assert(char const*, char const*, int) () at /usr/lib/libQt5Core.so.5 #8 0x7f4306f0fb77 in () at /usr/lib/libQt5Core.so.5 #9 0x7f42e8226ca4 in () at /usr/lib/qt/plugins/styles/libqgtk2style.so #10 0x7f4307cd3634 in QStyleFactory::create(QString const&) () at /usr/lib/libQt5Widgets.so.5 #11 0x7f42e932af08 in () at /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_style.so #12 0x7f4304ff7651 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #13 0x7f4304f9dbdf in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #14 0x7f4304f9e586 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib/libQt5Qml.so.5 #15 0x7f43023c6896 in () at /usr/lib/libQt5QmlModels.so.5 #16 0x7f430544de39 in () at /usr/lib/libQt5Quick.so.5 #17 0x7f430543c3d2 in () at /usr/lib/libQt5Quick.so.5 #18 0x7f430544d69a in () at /usr/lib/libQt5Quick.so.5 #19 0x7f430544f9f3 in () at /usr/lib/libQt5Quick.so.5 #20 0x7f430539e2ea in QQuickWindowPrivate::polishItems() () at /usr/lib/libQt5Quick.so.5 #21 0x7f430542fec4 in QQuickRenderControl::polishItems() () at /usr/lib/libQt5Quick.so.5 #22 0x7f43056d9ec8 in () at /usr/lib/libQt5QuickWidgets.so.5 #23 0x7f43056db61f in QQuickWidget::timerEvent(QTimerEvent*) () at /usr/lib/libQt5QuickWidgets.so.5 #24 0x7f43071024c6 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #25 0x7f4307c64b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #26 0x7f43070deb88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #27 0x7f4307128d53 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #28 0x7f4307129392 in () at /usr/lib/libQt5Core.so.5 #29 0x7f4305739b2b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #30 0x7f430578fe79 in () at /usr/lib/libglib-2.0.so.0 #31 0x7f4305737252 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #32 0x7f430712950c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #33 0x7f43070d732c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #34 0x7f43070e1e59 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #35 0x556b409c0b7a in () #36 0x7f4306a55290 in () at /usr/lib/libc.so.6 #37 0x7f4306a5534a in __libc_start_main () at /usr/lib/libc.so.6 #38 0x556b409c14d5 in () [Inferior 1 (process 5181) detached] The reporter indicates this bug may be a duplicate of or related to bug 451008, bug 452467, bug 453895, bug 456954, bug 457570. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459490] SELinux is preventing /app/bin/krita from execmod access on the file /memfd:JITCode:/app/lib/libQt5Qml.so.5
https://bugs.kde.org/show_bug.cgi?id=459490 --- Comment #7 from amyspark --- Hm, a better question is: if you run Krita under SELinux with Qt 5.15, does it show the issue? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456418] Color picker applet doesn't pick a color
https://bugs.kde.org/show_bug.cgi?id=456418 MountainX changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #7 from MountainX --- (In reply to Antonio Rojas from comment #6) > > *** This bug has been marked as a duplicate of bug 454974 *** Bug 454974 reports that the result is "returns black". This bug appears to be different and not a duplicate of 454974. Furthermore, this bug is not resolved as of plasmashell 5.25.4 while 454974 was marked as fixed in 5.24.7. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454974] DBus method ColorPicker.pick fails to retrieve color (returns black)
https://bugs.kde.org/show_bug.cgi?id=454974 MountainX changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #24 from MountainX --- (In reply to MountainX from comment #23) > (In reply to Antonio Rojas from comment #22) > > *** Bug 457311 has been marked as a duplicate of this bug. *** > > That bug says the result is "returns black". This bug appears to be > different and not a duplicate. Furthermore, this bug is not resolved as of > plasmashell 5.25.4 while that bug was marked as fixed in 5.24.7. I apologize. I added this comment to the wrong bug. Will add it to 456418 where it belongs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454974] DBus method ColorPicker.pick fails to retrieve color (returns black)
https://bugs.kde.org/show_bug.cgi?id=454974 MountainX changed: What|Removed |Added Resolution|FIXED |--- CC||davestechs...@gmail.com Status|RESOLVED|REOPENED --- Comment #23 from MountainX --- (In reply to Antonio Rojas from comment #22) > *** Bug 457311 has been marked as a duplicate of this bug. *** That bug says the result is "returns black". This bug appears to be different and not a duplicate. Furthermore, this bug is not resolved as of plasmashell 5.25.4 while that bug was marked as fixed in 5.24.7. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459490] SELinux is preventing /app/bin/krita from execmod access on the file /memfd:JITCode:/app/lib/libQt5Qml.so.5
https://bugs.kde.org/show_bug.cgi?id=459490 --- Comment #6 from amyspark --- Does AlmaLinux also have SELinux enabled by default? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 459496] Error : Unable to load applications Please check Internet connectivity
https://bugs.kde.org/show_bug.cgi?id=459496 --- Comment #1 from Aleix Pol --- Can you check that your NetworkManager state is indeed set as connected? You can check by running "nmcli". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied to decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435690] [Wayland] Kickoff, Krunner, and other applets open in the wrong place
https://bugs.kde.org/show_bug.cgi?id=435690 Christian González changed: What|Removed |Added CC||chgonzal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459500] New: System Settings crushes - firewall - View Connections
https://bugs.kde.org/show_bug.cgi?id=459500 Bug ID: 459500 Summary: System Settings crushes - firewall - View Connections Classification: Applications Product: systemsettings Version: 5.25.5 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mjasis...@gmail.com Target Milestone: --- Application: systemsettings (5.25.5) Qt Version: 5.15.4 Frameworks Version: 5.98.0 Operating System: Linux 5.19.0-15-generic x86_64 Windowing System: X11 Distribution: Ubuntu Kinetic Kudu (development branch) DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Hello, every time when I click on the button "View Connections" in System Settings in the section Firewall. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f1251839a04 in NetworkManager::WirelessDevice::activeAccessPoint() const () at /lib/x86_64-linux-gnu/libKF5NetworkManagerQt.so.6 #5 0x7f125183b204 in () at /lib/x86_64-linux-gnu/libKF5NetworkManagerQt.so.6 #6 0x7f126b9a047c in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f12517f3522 in NetworkManager::AccessPoint::signalStrengthChanged(int) () at /lib/x86_64-linux-gnu/libKF5NetworkManagerQt.so.6 #8 0x7f125181972a in () at /lib/x86_64-linux-gnu/libKF5NetworkManagerQt.so.6 #9 0x7f12517f73d3 in () at /lib/x86_64-linux-gnu/libKF5NetworkManagerQt.so.6 #10 0x7f126ab5723b in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #11 0x7f126b9949d0 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f126c577f42 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f126b967d78 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f126b96adf1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f126b9c2187 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f1269fcc4e9 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f126a021098 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f1269fc9ca0 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f126b9c184a in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f126b96670b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f126b96eb6a in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x55f54c59e0b3 in () #23 0x7f126b29f550 in __libc_start_call_main (main=main@entry=0x55f54c59d610, argc=argc@entry=1, argv=argv@entry=0x7fff98795468) at ../sysdeps/nptl/libc_start_call_main.h:58 #24 0x7f126b29f609 in __libc_start_main_impl (main=0x55f54c59d610, argc=1, argv=0x7fff98795468, init=, fini=, rtld_fini=, stack_end=0x7fff98795458) at ../csu/libc-start.c:381 #25 0x55f54c59e9f5 in () [Inferior 1 (process 3351) detached] The reporter indicates this bug may be a duplicate of or related to bug 459028. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied to decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 SirLennox changed: What|Removed |Added CC||sirlennox...@gmail.com Resolution|FIXED |--- Status|RESOLVED|REPORTED Ever confirmed|1 |0 --- Comment #88 from SirLennox --- To fix this bug window borders must be clearly defined by any window decoration that adds transparent pixels that shouldn't be blurred AND the blur effect has to implement the window borders, so it won't blur pixels outside of the borders. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459499] New: The possibility to disable persons
https://bugs.kde.org/show_bug.cgi?id=459499 Bug ID: 459499 Summary: The possibility to disable persons Classification: Applications Product: digikam Version: 7.8.0 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: eu...@albiker.org Target Milestone: --- SUMMARY *** I think it would be a improvement if the user can deactivate persons. The reason is: - The user know, that there will be no NEW pictures on which the person (perhaps the person is dead or any other reason) - The user knows, that he met the person in a holiday and will never meet the person again In Digikam I have 600 different persons tags on 110.000 pictures. (Another 35.000 Faces I have in the "ignored" Tag) I know I will never get any other/newer picture of some persons and want to disable them. Possible advantages if I can disable some persons: - In menu "Tools - Maintenance - "Clear and rebuild all training data" will be faster, if there will be processed less persons/faces - Recognition of people is faster because fewer people are active - Recognition of persons is better, because only persons are active who the user assumes are also to be seen in images What do you think? Greetings Eugen -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442143] System Monitor crashes when switching to "Applications" section
https://bugs.kde.org/show_bug.cgi?id=442143 --- Comment #5 from brazjoaope...@ymail.com --- Created attachment 152320 --> https://bugs.kde.org/attachment.cgi?id=152320=edit New crash information added by DrKonqi plasma-systemmonitor (5.25.5) using Qt 5.15.6 Crashes when opening either the Processes Page or Applications Page -- Backtrace (Reduced): #5 0x7f3937ce0b1b in QQuickItemLayer::~QQuickItemLayer (this=0x55fdd7b98540, __in_chrg=) at items/qquickitem.cpp:8433 #6 0x7f3937ce0b8d in QQuickItemLayer::~QQuickItemLayer (this=0x55fdd7b98540, __in_chrg=) at items/qquickitem.cpp:8431 #7 0x7f3937e6b287 in QAccessibleQuickItem::role (this=0x55fdd77d6330) at ../../include/QtQuick/../../src/quick/items/qquickitem.h:468 #8 0x7f393e07d7ca in AtSpiAdaptor::pathForInterface (this=this@entry=0x55fdd57ea170, interface=0x55fdd77d6330) at atspiadaptor.cpp:1540 #9 0x7f393e080ba7 in AtSpiAdaptor::notifyStateChange (this=this@entry=0x55fdd57ea170, interface=, state=..., value=1) at atspiadaptor.cpp:875 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442143] System Monitor crashes when switching to "Applications" section
https://bugs.kde.org/show_bug.cgi?id=442143 brazjoaope...@ymail.com changed: What|Removed |Added CC||brazjoaope...@ymail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455450] Slide desktop animation is slower in 5.25, especially compared to other animations
https://bugs.kde.org/show_bug.cgi?id=455450 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455450] Slide desktop animation is slower in 5.25, especially compared to other animations
https://bugs.kde.org/show_bug.cgi?id=455450 Nate Graham changed: What|Removed |Added Keywords||regression, usability Resolution|INTENTIONAL |--- Status|RESOLVED|REPORTED --- Comment #16 from Nate Graham --- We keep getting bug reports about this; it's clear that users aren't happy about the slower effective speed of the Slide effect in 5.25 and later. Re-opening. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407133] Copy text from rotated pdf gives rubbish
https://bugs.kde.org/show_bug.cgi?id=407133 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459357] New "Slide virtual desktops" is too slow and causes render bugs
https://bugs.kde.org/show_bug.cgi?id=459357 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 455450 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455450] Slide desktop animation is slower in 5.25, especially compared to other animations
https://bugs.kde.org/show_bug.cgi?id=455450 Nate Graham changed: What|Removed |Added CC||ppeli...@gmail.com --- Comment #15 from Nate Graham --- *** Bug 459357 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 459353] Application: Subtitle Composer (subtitlecomposer), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=459353
--- Comment #6 from carlos ---
(In reply to Mladen Milinkovic, Max from comment #5)
> (In reply to carlos from comment #4)
> > As I don't have the info handy now, the crash happened with the following
> > ffmpeg
> >
> > 1adfd28f9e (HEAD -> master, origin/master, origin/HEAD) qsvenc_{hevc,h264}:
> > add scenario option
> >
> > and tit also happened with he latest ffmpeg ( hours before submitting the
> > crash
> >
> > 1af0051977 (HEAD -> master, origin/master, origin/HEAD) doc/filters: add
> > speechnorm examples
>
> Could you please try using stable ffmpeg release? You're using ffmpeg builds
> from master branch if I'm not wrong.
>
I agree.
But, out of curiosity, would it normally happen (crashing while opening a video
file)
if you were to compile it against an ffmpeg devel release?
In other words, I just can't recall if it was compiled at first against an
unstable vs stable
release. That part I can't remember. But I've always, usually, run the latest
ffmpeg and never
had an issue.
> Just to confirm, the crash happens with any/every video file?
>
Yes.
> I don't see anything wrong with SC code where it's crashing, it wasn't
> checking for nullptr there, but that was fixed.
Thanks Max. Unfortunately there's so much I can do on that particular system
with the segmentation fault, from this point forward,
as I pointed out earlier with the unrelated issue from the kernel etc. I'm
pretty much stuck there.
As a side note: there was an error while trying to configure porcketsphinx
with ` autoreconfig -ivf`
as outlined on the wiki building from sources.
I ended up cmake -S . -B build per the README documentation
```
Building CXX object
src/speechplugins/pocketsphinx/CMakeFiles/pocketsphinxasr.dir/pocketsphinxconfig.cpp.o
[100%] Linking CXX shared module pocketsphinxasr.so
/usr/bin/ld: CMakeFiles/pocketsphinxasr.dir/pocketsphinxplugin.cpp.o: in
function `SubtitleComposer::PocketSphinxPlugin::init()':
subtitlecomposer/src/subtitlecomposer/src/speechplugins/pocketsphinx/pocketsphinxplugin.cpp:34:
undefined reference to `cmd_ln_init'
/usr/bin/ld:
subtitlecomposer/src/subtitlecomposer/src/speechplugins/pocketsphinx/pocketsphinxplugin.cpp:60:
undefined reference to `cmd_ln_int_r'
/usr/bin/ld: CMakeFiles/pocketsphinxasr.dir/pocketsphinxplugin.cpp.o: in
function `SubtitleComposer::PocketSphinxPlugin::cleanup()':
subtitlecomposer/src/subtitlecomposer/src/speechplugins/pocketsphinx/pocketsphinxplugin.cpp:79:
undefined reference to `cmd_ln_free_r'
collect2: error: ld returned 1 exit status
make[2]: ***
[src/speechplugins/pocketsphinx/CMakeFiles/pocketsphinxasr.dir/build.make:181:
src/speechplugins/pocketsphinx/pocketsphinxasr.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:722:
src/speechplugins/pocketsphinx/CMakeFiles/pocketsphinxasr.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
```
All in all, you're probably correct. ffmpeg may have been the culprit when
composer was compiled
on that system recently, as opposed to a year or so ago when… perhaps ffmpeg
was the stable release.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 459108] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=459108 Lothar changed: What|Removed |Added CC||loh@googlemail.com --- Comment #6 from Lothar --- Hi, Eric pointed me to this report. (In reply to Oded Arbel from comment #5) > The problem appears to me to have been introduced in this commit: > https://invent.kde.org/utilities/kate/-/commit/ > 1b93ede0e09fcc5ef069cf5c3be33e914c660162#1d89091b7718b0df550ed065e31436f1fab5 > 217c_1112_1123 > where the new code for KateMDI::Sidebar::saveSession assumes (without > checking) that all items in the tab bar are already initialized tool views, > but the problem is that the KateFileBrowser tool view - when it can't > immediately identify the location from its configuration as a valid folder - > starts a KIO stat job, which takes time to complete - and calls into the > QEventLoop. The event loop may cause the SMC save_yourself API to be called > to save the current session state - calling on KateMDI::Sidebar::saveSession > to save the state of a partially initialized sidebar. You seems to have located the issue very well, thank you. Will try to reproduce the issue and fix it... > I believe more error checking all around would be useful ...probably this way. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 458933] Konqueror crashes when clicking "Places"
https://bugs.kde.org/show_bug.cgi?id=458933 Stefano Crocco changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/konqueror/commit/c9f3d1 ||957f7b6c168a025b5b4014e46a5 ||f49bb63 --- Comment #6 from Stefano Crocco --- Git commit c9f3d1957f7b6c168a025b5b4014e46a5f49bb63 by Stefano Crocco. Committed on 21/09/2022 at 17:27. Pushed by dfaure into branch 'master'. Fix crash caused by using original view rather than actual view UrlLoader::decideEmbedOrSave used the original view when deciding whether it could be reused to open the URL, instead of using the view provided using UrlLoader::setView. If the URL was opened by clicking on a sidebar item, this caused a sidebar view to be used, rather than the correct dolphin part. This lead to a crash because the sidebar view is a passive view, which caused KonqViewManager::chooseNextView to return nullptr M +1-1src/konqmainwindow.cpp M +6-8src/urlloader.cpp https://invent.kde.org/network/konqueror/commit/c9f3d1957f7b6c168a025b5b4014e46a5f49bb63 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455913] [Wayland + Nvidia] Krunner stops showing after opening / closing it a few times
https://bugs.kde.org/show_bug.cgi?id=455913 S. Bryant changed: What|Removed |Added CC||st...@bawue.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459367] Global theme chooser seems like a generic dark/light mode preference and confuses people
https://bugs.kde.org/show_bug.cgi?id=459367 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1170 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459498] Saving .psd shows a mistaken warning about fractional frame durations
https://bugs.kde.org/show_bug.cgi?id=459498 Halla Rempt changed: What|Removed |Added Ever confirmed|0 |1 Assignee|krita-bugs-n...@kde.org |a...@amyspark.me Status|REPORTED|ASSIGNED CC||ha...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 452403] Okular needs ability to sanitize and redact PDF (and possibly other types of) documents.
https://bugs.kde.org/show_bug.cgi?id=452403 Ernie changed: What|Removed |Added CC||gother@gmail.com --- Comment #1 from Ernie --- This is seriously an important feature and it's almost always premium, it would make a lot of people switch from Adobe Acrobat Pro probably -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459498] New: Saving .psd shows a mistaken warning about fractional frame durations
https://bugs.kde.org/show_bug.cgi?id=459498 Bug ID: 459498 Summary: Saving .psd shows a mistaken warning about fractional frame durations Classification: Applications Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: penguinflyer2...@gmail.com Target Milestone: --- Saving a .psd shows a dialog that reads: >You will lose information when saving this image as a Photoshop image. Reason: >The image is animated with a frame duration in fractions of a millisecond. The >format cannot represent this, and the frame duration will be rounded to the >nearest millisecond. even though the file is not animated and the warning message is intended for .webp and .jxl formats. SOFTWARE/OS VERSIONS Krita 5.2.x git hash d1ffb35 ADDITIONAL INFORMATION The commit where the message was added: https://invent.kde.org/graphics/krita/-/commit/0f2a6ff76624668cac606f8e848db1e908bd49eb -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459367] Global theme chooser seems like a generic dark/light mode preference and confuses people
https://bugs.kde.org/show_bug.cgi?id=459367 Nate Graham changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459367] Global theme chooser seems like a generic dark/light mode preference and confuses people
https://bugs.kde.org/show_bug.cgi?id=459367 Nate Graham changed: What|Removed |Added Summary|The dark/light mode |Global theme chooser seems |preference is completely|like a generic dark/light |broken |mode preference and ||confuses people CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- These aren't generic "dark/light" toggles; they're simply quick shortcuts to the Breeze Dark and Breeze Light global themes. So when you use a different global theme, you're not using Breeze Dark or Breeze Light, so neither is selected. This seems to cause a lot of confusion, so maybe we should rename them to their real names, not generic "dark" and "light". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459490] SELinux is preventing /app/bin/krita from execmod access on the file /memfd:JITCode:/app/lib/libQt5Qml.so.5
https://bugs.kde.org/show_bug.cgi?id=459490 Long Vu changed: What|Removed |Added CC||h...@vulongm.com --- Comment #5 from Long Vu --- One of the commenters mentioned on the issue it also occurred for them using the AppImage on AlmaLinux 9 https://github.com/flathub/org.kde.krita/issues/66#issuecomment-1252893268 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455913] [Wayland + Nvidia] Krunner stops showing after opening / closing it a few times
https://bugs.kde.org/show_bug.cgi?id=455913 jsdecker...@gmail.com changed: What|Removed |Added CC||jsdecker...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453621] Error while opening the database
https://bugs.kde.org/show_bug.cgi?id=453621 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.9.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459497] Digikam fails to load images
https://bugs.kde.org/show_bug.cgi?id=459497 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |WAITINGFORINFO Severity|critical|normal --- Comment #1 from Maik Qualmann --- Is it an Ubuntu Snap package from digiKam? Snap packages use a sandbox and are unusable for using digiKam. Try our AppImage from www.digikam.org. Otherwise, we need the debug output from the terminal, as described here: https://www.digikam.org/contribute/ Maik -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407133] Copy text from rotated pdf gives rubbish
https://bugs.kde.org/show_bug.cgi?id=407133 Albert Astals Cid changed: What|Removed |Added Priority|HI |NOR CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459497] New: Digikam fails to load images
https://bugs.kde.org/show_bug.cgi?id=459497 Bug ID: 459497 Summary: Digikam fails to load images Classification: Applications Product: digikam Version: 7.8.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: LightTable-Canvas Assignee: digikam-bugs-n...@kde.org Reporter: raquel_t...@yahoo.com.br Target Milestone: --- Created attachment 152319 --> https://bugs.kde.org/attachment.cgi?id=152319=edit A screenshot that shows the error. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open Digikam 7.8.0 2. Click on the thumbnail of any image (or set of images) contained in an album 3. Click on "Light table" OBSERVED RESULT Images do not load. There is a warning sign: "Failed to load image" Most of the thumbnails usually appear; however, some of them do not appear, too. EXPECTED RESULT Images should appear on Light table. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 18.04.6 LTS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I have been using Digikam for a while and had never had those problems before. It started when some thumbnails would not open (even before trying to open the images in the Light Table). Now, none of my photos appear in the Light Table. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 457604] When file operation fails due to a filename too long (or presumably other reasons), kid3 confusingly asks user to change permissions of the file
https://bugs.kde.org/show_bug.cgi?id=457604
--- Comment #1 from Urs Fleisch ---
I have now fixed this so that the error description ("File name too long" in
this case) is displayed too. Note that you will still get a dialog asking if
you want to change permissions because the `QFileInfo::isWritable()` check,
which is made after an error occurs, is still true. The error description for
"File name too long" is not displayed on Windows, even using the native low
level Win32 API instead of POSIX errno does not help there, it just reports an
unknown error. You can find a fixed version git20220921 in
https://sourceforge.net/projects/kid3/files/kid3/development/.
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 459496] New: Error : Unable to load applications Please check Internet connectivity
https://bugs.kde.org/show_bug.cgi?id=459496 Bug ID: 459496 Summary: Error : Unable to load applications Please check Internet connectivity Classification: Applications Product: Discover Version: 5.24.6 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: jackvera...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 152318 --> https://bugs.kde.org/attachment.cgi?id=152318=edit plasma-discover startupscreen with unable-to-load-applications SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Start Discover from the ubuntu menu or from command line by plasma-discover 2. Application starts and shows window with message : Unable to load applications Please check Internet connectivity 3. This message does not go away and I do not get Applications but other things seem to work OBSERVED RESULT Clicking Applications gives the error again : Unable to load applications Please check Internet connectivity Clicking on Application Addons shows a lot of icons Clicking on Plasma Addons show a lot of icons Clicking Installed shows "Nothing found" Clicking Settings shows Ubuntu 22.04.01 LTS and lots of boxes with just some checked Clicking About shows About info including version 5.24.6 Clicking Applications gives the error again : Unable to load applications Please check Internet connectivity EXPECTED RESULT After starting the application I would expect to be able to browse to Applications and categories and find applications which I can install / remove SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.04.1 LTS : lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3(built against 5.15.3) ADDITIONAL INFORMATION I am not sure but I think I may have this issue since I upgraded from Ubuntu 22.04 LTS to 22.04.1 LTS. apt update, apt remove plasma-discover followed by apt install plasma-discover did not solve this. deleting the ~/.cache/discover cache does not help either. I do have Internet connectivity via my home LAN and WiFi and also tried by WiFi via a hotspot on my phone. Always the same error. I removed plasma discover and installed and older version plasma-discover_5.24.4-0ubuntu1_amd64.deb for which I also needed to apt remove plasma-discover-common and apt install plasma-discover-common=5.24.4-0ubuntu1 Same result. However, there were updates for plasma-discover and plasma-discover-common to version 5.24.6 which I began with and since applying these the application is back on version 5.24.6. So update mechanism works. I tested with an other user, same result. I created a new user and tested with that, same result. Maybe the error is wrong and something needs to be changed somewhere in a configuration file. I am lost. Please help -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 458662] Leading zeros are interpreted as octal numbers in "fromtag '%{disk}'" in kid3-cli
https://bugs.kde.org/show_bug.cgi?id=458662 Urs Fleisch changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 405227] kinit: kdeinit crashes with EXC_GUARD on Mac
https://bugs.kde.org/show_bug.cgi?id=405227 --- Comment #7 from RJVB --- Because my system doesn't run anything newer than Qt 5.9 -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 457655] Kid3 Crashed Upon Closing
https://bugs.kde.org/show_bug.cgi?id=457655 --- Comment #1 from Urs Fleisch --- I remember having seen this on macOS, but never on Linux. At the moment, I am not able to reproduce it, not even on macOS. So if you find a way to reproduce it, please let me know. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453621] Error while opening the database
https://bugs.kde.org/show_bug.cgi?id=453621 Raquel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459495] Remove layer restrictions for "ten scripts"
https://bugs.kde.org/show_bug.cgi?id=459495 Halla Rempt changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |ha...@valdyas.org Ever confirmed|0 |1 CC||ha...@valdyas.org Status|REPORTED|CONFIRMED --- Comment #1 from Halla Rempt --- Ah, good point. It also shows how dangerous it is to fix bugs in relatively obscure features, because since the moment I fixed a bug there, requests have been coming in :-) But there is no reason for these actions to be limited to anything. If I'm not totally tired out by today's outing to visit a faraway friend, I might look into it tomorrow. There are more improvements I've seen out on k-a. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459495] New: Remove layer restrictions for "ten scripts"
https://bugs.kde.org/show_bug.cgi?id=459495 Bug ID: 459495 Summary: Remove layer restrictions for "ten scripts" Classification: Applications Product: krita Version: 5.1.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: thetwo...@foxmail.com Target Milestone: --- On some layer types, the plug-in cannot run scripts, and the buttons are grayed out. （ clone layer, file layer, vector layer, group layer and transform mask） I think its judging condition is whether the layer has editable pixels.Ideally, 10 scripts shouldn’t judge if a script is executable or not as some script may not be related to layer management… KA thread：https://krita-artists.org/t/how-to-delete-all-empty-layers/48197/6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #41 from Michael Mikowski --- (In reply to Nate Graham from comment #40) > The issue only affected Plasma 5.25+Frameworks 5.98. The combination of > Plasma 5.24+Frameworks 5.98 isn't affected. > > Regardless, patching this fix into your 5.98 and then later shipping the > re-spun 5.98 is highly recommended! Thanks Nate! I'll pass that along! -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 438649] fingerprint login not working on kubuntu
https://bugs.kde.org/show_bug.cgi?id=438649 --- Comment #20 from Amnon --- I have uploaded screenshots (a video of the boot sequence, and a closeup of the errors) here: https://drive.google.com/file/d/1tXqgyFG4CheKtf7vKw5cSUutd2SsYs0Z/view?usp=sharing https://drive.google.com/file/d/1tbCe35ueDi5lmo_UHacL5hhG_ZlM-AOQ/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456142] Display scale is reset on logout
https://bugs.kde.org/show_bug.cgi?id=456142 --- Comment #9 from poperi...@mailbox.org --- (In reply to David Edmundson from comment #4) > qtdiag ran under xwayland. That's rather unexpected. > > Screens: 1, High DPI scaling: inactive > # 0 "XWAYLAND0" Depth: 24 Primary: yes > Manufacturer: > Model: > Serial number: > Geometry: 2256x1504+0+0 Available: 2256x1438+0+66 > Physical size: 280x190 mm Refresh: 59.9259 Hz Power state: 0 > Physical DPI: 204.651,201.061 Logical DPI: 96,96 Subpixel_None > DevicePixelRatio: 1 Pixel density: 1 > Primary orientation: 2 Orientation: 2 Native orientation: 0 > OrientationUpdateMask: 0 > > It indeed shows us having the scale of 1. > > --- > > Next up can I have output of ` kscreen-console bug` after setting the value, > and after login Hey, just wanted to update that I submitted the required information. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 457766] "Choose A for All Unsolved Conflicts" makes unexpected changes
https://bugs.kde.org/show_bug.cgi?id=457766 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/commit/0dd54bde01b7b |kdiff3/commit/975618cf99dc1 |9c966109a45eee9bfa5ce9d89b0 |187caba7db6ba41f85cb409f6c6 --- Comment #3 from michael --- Git commit 975618cf99dc1187caba7db6ba41f85cb409f6c6 by Michael Reeves. Committed on 21/09/2022 at 18:14. Pushed by mreeves into branch 'master'. Ingnore manually editted blocks when resolving unresolved conflicts FIXED-IN:1.10.0 M +1-1src/MergeEditLine.cpp M +4-0src/MergeEditLine.h https://invent.kde.org/sdk/kdiff3/commit/975618cf99dc1187caba7db6ba41f85cb409f6c6 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 457766] "Choose A for All Unsolved Conflicts" makes unexpected changes
https://bugs.kde.org/show_bug.cgi?id=457766 michael changed: What|Removed |Added Version Fixed In||1.10.0 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/commit/0dd54bde01b7b ||9c966109a45eee9bfa5ce9d89b0 Status|CONFIRMED |RESOLVED --- Comment #2 from michael --- Git commit 0dd54bde01b7b9c966109a45eee9bfa5ce9d89b0 by Michael Reeves. Committed on 21/09/2022 at 18:39. Pushed by mreeves into branch '1.10'. Ignore manually editted blocks when resolving unresolved conflicts FIXED-IN:1.10.0 M +1-1src/MergeEditLine.cpp M +4-0src/MergeEditLine.h https://invent.kde.org/sdk/kdiff3/commit/0dd54bde01b7b9c966109a45eee9bfa5ce9d89b0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 459493] Make the volume list easy and intuitive
https://bugs.kde.org/show_bug.cgi?id=459493 --- Comment #1 from ratijas --- The only problem I see here are the "(LISP (brackets))" in some input/output labels.Other than that, if that's the names the hardware provides us with, then that's what applet displays. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 438649] fingerprint login not working on kubuntu
https://bugs.kde.org/show_bug.cgi?id=438649 --- Comment #19 from Amnon --- By the way, your instructions were a bit incorrect. you wrote: sudo dpkg -i libfprint-2-tod1-goodix_0.0.4-0ubuntu1somerville1_amd64.deb should be: sudo dpkg -i libfprint-2-tod1-goodix_0.0.6-0ubuntu1~somerville1_amd64.deb Anyhow, I entered the BIOS setup with F2 and unchecked the fingerprint reader options (two of them). I can now boot to my computer -- but there are some new error messages in the boot sequence, that were not there before. **I wish to revert* *How od I do that? On 21/09/2022 21:34, Amnon Yekutieli wrote: Thanks but no thanks. I followed your instruction up until Reboot and check if the fingerprint options are shown in User settings. Now you should be able to add your fingerprint(s). If this doesn't work for you, consider downgrading fprintd to version 1.90.9-1. Also you could try to add them manually using `fprintd-enroll`. Now assuming you have enrolled your fingerprint(s). You can check if the fingerprint is working for lock screen and login screen. Keep in mind that login in with fingerprint works but it won't unlock the KWallet so I recommend login in with password, but you can unlock screen or use approve sudo commands with fingerprint. In case this is not automatically setup by KDE you can do: sudo pam-auth-update (use space bar to enable the "Fingerprint authentication") I enrolled two figerprints. Logging in after "lock" worked - almost: I had to press "enter" and then got a prompt to touch the fp device. That was ok. Then I tried to log out and log in -- and theh sytem is **now frozen**. I am unable to log in in any way I can think of!!! *How can I revert to my working system, from 10 minutes ago?* On 20/09/2022 10:30, bugzilla_nore...@kde.org[1] wrote: * Comment # 16[2] on bug 438649[3] from zzra...@protonmail.com[4] * It appears that there is an issue with the driver. First of all make sure to install libfprint-2-tod1: sudo apt install libfprint-2-tod1 XPS 9310 fingerprint reader needs proprietary drivers to work which you can get here: http://dell.archive.canonical.com/updates/pool/public/libf/libfprint-2-tod1-goodix/ You would want to download `libfprint-2-tod1-goodix_0.0.6-0ubuntu1~somerville1_amd64.deb` then move to the folder where you have downloaded the file and run: sudo dpkg -i libfprint-2-tod1-goodix_0.0.4-0ubuntu1somerville1_amd64.deb Reboot and check if the fingerprint options are shown in User settings. Now you should be able to add your fingerprint(s). If this doesn't work for you, consider downgrading fprintd to version 1.90.9-1. Also you could try to add them manually using `fprintd-enroll`. Now assuming you have enrolled your fingerprint(s). You can check if the fingerprint is working for lock screen and login screen. Keep in mind that login in with fingerprint works but it won't unlock the KWallet so I recommend login in with password, but you can unlock screen or use approve sudo commands with fingerprint. In case this is not automatically setup by KDE you can do: sudo pam-auth-update (use space bar to enable the "Fingerprint authentication") In case this command doesn't work either, you can edit the .pam files manually and the following at the beginning of the file. File: /etc/pam.d/sddm ``` auth[success=1 new_authtok_reqd=1 default=ignore] pam_unix.so try_first_pass likeauth nullok authsufficient pam_fprintd.so ``` (Login screen. First line ensures that a password login will automatically unlock KWallet, second one adds support for fingerprint.) File: /etc/pam.d/kde ``` authsufficient pam_unix.so try_first_pass likeauth nullok authsufficient pam_fprintd.so ``` (Lock screen. The first line looks different from the corresponding /etc/pam.d/sddm configuration because the KDE lock screen does not need to run the KWallet pam module.) File: /etc/pam.d/sudo ``` authsufficient pam_unix.so try_first_pass likeauth nullok authsufficient pam_fprintd.so ``` (Sudo commands.) You can also check for other files inside /etc/pam.d/ folder if you would want use fingerprint for other stuff. Hope this helps. - You are receiving this mail because: * You reported the bug. * You are on the CC list for the bug. -- Amnon Yekutieli amye...@gmail.com [5] www.math.bgu.ac.il/~amyekut [6] www.sites.google.com/view/amyekut [7] -- Amnon Yekutieli amye...@gmail.com [5] www.math.bgu.ac.il/~amyekut [6]
[kwin] [Bug 459328] Top and bottom side not clickable
https://bugs.kde.org/show_bug.cgi?id=459328
--- Comment #10 from Yoann Laissus ---
(In reply to David Edmundson from comment #9)
> Is there anything interesting about your input devices? In particular I'm
> looking for a calibration matrix set?
>
>
> Given you bisected I assume you can build your own kwin.
> I have a theory, but it's unproven:
>
> Can you mod surface_interface.cpp:773 to read:
>
> ```
> SurfaceInterfacePrivate::inputContains(const QPointF )
> {
> return contains(position);
> }
> ```
> deleting everything from '&& ..'
>
> and tell me if that changes anything?
It's still the same with the changes to surface_interface.cpp.
But you were totally right about the input devices.
I currently use a Logitech G502 and I can't reproduce the problem with other
mouses (even another Logitech model).
With the G502, the problem appears only in Adaptive mode for the acceleration
profile. It's ok on the Flat mode.
I also tried with different DPI on the different mouses (configurable with a
button on the logitech ones), it's the same behavior.
--
You are receiving this mail because:
You are watching all bug changes.
[ksplash] [Bug 438649] fingerprint login not working on kubuntu
https://bugs.kde.org/show_bug.cgi?id=438649 --- Comment #18 from Amnon --- Thanks but no thanks. I followed your instruction up until Reboot and check if the fingerprint options are shown in User settings. Now you should be able to add your fingerprint(s). If this doesn't work for you, consider downgrading fprintd to version 1.90.9-1. Also you could try to add them manually using `fprintd-enroll`. Now assuming you have enrolled your fingerprint(s). You can check if the fingerprint is working for lock screen and login screen. Keep in mind that login in with fingerprint works but it won't unlock the KWallet so I recommend login in with password, but you can unlock screen or use approve sudo commands with fingerprint. In case this is not automatically setup by KDE you can do: sudo pam-auth-update (use space bar to enable the "Fingerprint authentication") I enrolled two figerprints. Logging in after "lock" worked - almost: I had to press "enter" and then got a prompt to touch the fp device. That was ok. Then I tried to log out and log in -- and theh sytem is **now frozen**. I am unable to log in in any way I can think of!!! *How can I revert to my working system, from 10 minutes ago?* On 20/09/2022 10:30, bugzilla_nore...@kde.org[1] wrote: * Comment # 16[2] on bug 438649[3] from zzra...@protonmail.com[4] * It appears that there is an issue with the driver. First of all make sure to install libfprint-2-tod1: sudo apt install libfprint-2-tod1 XPS 9310 fingerprint reader needs proprietary drivers to work which you can get here: http://dell.archive.canonical.com/updates/pool/public/libf/libfprint-2-tod1-goodix/ You would want to download `libfprint-2-tod1-goodix_0.0.6-0ubuntu1~somerville1_amd64.deb` then move to the folder where you have downloaded the file and run: sudo dpkg -i libfprint-2-tod1-goodix_0.0.4-0ubuntu1somerville1_amd64.deb Reboot and check if the fingerprint options are shown in User settings. Now you should be able to add your fingerprint(s). If this doesn't work for you, consider downgrading fprintd to version 1.90.9-1. Also you could try to add them manually using `fprintd-enroll`. Now assuming you have enrolled your fingerprint(s). You can check if the fingerprint is working for lock screen and login screen. Keep in mind that login in with fingerprint works but it won't unlock the KWallet so I recommend login in with password, but you can unlock screen or use approve sudo commands with fingerprint. In case this is not automatically setup by KDE you can do: sudo pam-auth-update (use space bar to enable the "Fingerprint authentication") In case this command doesn't work either, you can edit the .pam files manually and the following at the beginning of the file. File: /etc/pam.d/sddm ``` auth[success=1 new_authtok_reqd=1 default=ignore] pam_unix.so try_first_pass likeauth nullok authsufficient pam_fprintd.so ``` (Login screen. First line ensures that a password login will automatically unlock KWallet, second one adds support for fingerprint.) File: /etc/pam.d/kde ``` authsufficient pam_unix.so try_first_pass likeauth nullok authsufficient pam_fprintd.so ``` (Lock screen. The first line looks different from the corresponding /etc/pam.d/sddm configuration because the KDE lock screen does not need to run the KWallet pam module.) File: /etc/pam.d/sudo ``` authsufficient pam_unix.so try_first_pass likeauth nullok authsufficient pam_fprintd.so ``` (Sudo commands.) You can also check for other files inside /etc/pam.d/ folder if you would want use fingerprint for other stuff. Hope this helps. - You are receiving this mail because: * You reported the bug. * You are on the CC list for the bug. -- Amnon Yekutieli amye...@gmail.com [5] www.math.bgu.ac.il/~amyekut [6] www.sites.google.com/view/amyekut [7] 1. mailto:bugzilla_nore...@kde.org 2. https://bugs.kde.org/show_bug.cgi?id=438649#c16 3. https://bugs.kde.org/show_bug.cgi?id=438649 4. mailto:zzra...@protonmail.com 5. mailto:amye...@gmail.com 6. http://www.math.bgu.ac.il/~amyekut 7. http://www.sites.google.com/view/amyekut -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423217] Wallpaper plugins dont receive left click events in desktop view layout
https://bugs.kde.org/show_bug.cgi?id=423217 --- Comment #5 from gnoumph --- (In reply to Nate Graham from comment #4) > Ah, this. It's the same as Bug 413104 which is being fixed imminently. > That's for the reminder! > > *** This bug has been marked as a duplicate of bug 413104 *** Oh glad to see that :) Thanks! Just to notice: I already saw this issue but I wasn't sure this was the same bug, because in this case left click isn't working in Desktop view nor in Folder view (but in Folder view it seems normal I guess). -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 438649] fingerprint login not working on kubuntu
https://bugs.kde.org/show_bug.cgi?id=438649 --- Comment #17 from Amnon --- (In reply to zzrakic from comment #16) > It appears that there is an issue with the driver. > > First of all make sure to install libfprint-2-tod1: > > sudo apt install libfprint-2-tod1 > > XPS 9310 fingerprint reader needs proprietary drivers to work which you can > get here: > http://dell.archive.canonical.com/updates/pool/public/libf/libfprint-2-tod1- > goodix/ > > You would want to download > `libfprint-2-tod1-goodix_0.0.6-0ubuntu1~somerville1_amd64.deb` then move to > the folder where you have downloaded the file and run: > > sudo dpkg -i libfprint-2-tod1-goodix_0.0.4-0ubuntu1somerville1_amd64.deb > > Reboot and check if the fingerprint options are shown in User settings. Now > you should be able to add your fingerprint(s). > If this doesn't work for you, consider downgrading fprintd to version > 1.90.9-1. > > Also you could try to add them manually using `fprintd-enroll`. > > Now assuming you have enrolled your fingerprint(s). You can check if the > fingerprint is working for lock screen and login screen. > Keep in mind that login in with fingerprint works but it won't unlock the > KWallet so I recommend login in with password, but you can unlock screen or > use approve sudo commands with fingerprint. > > In case this is not automatically setup by KDE you can do: > > sudo pam-auth-update > (use space bar to enable the "Fingerprint authentication") > > In case this command doesn't work either, you can edit the .pam files > manually and the following at the beginning of the file. > > File: /etc/pam.d/sddm > ``` > auth [success=1 new_authtok_reqd=1 default=ignore] > pam_unix.so > try_first_pass likeauth nullok > auth sufficient pam_fprintd.so > ``` > (Login screen. First line ensures that a password login will automatically > unlock KWallet, second one adds support for fingerprint.) > > File: /etc/pam.d/kde > ``` > auth sufficient pam_unix.so try_first_pass likeauth > nullok > auth sufficient pam_fprintd.so > ``` > (Lock screen. The first line looks different from the corresponding > /etc/pam.d/sddm configuration because the KDE lock screen does not need to > run the KWallet pam module.) > > File: /etc/pam.d/sudo > ``` > auth sufficient pam_unix.so try_first_pass likeauth nullok > auth sufficient pam_fprintd.so > ``` > (Sudo commands.) > > You can also check for other files inside /etc/pam.d/ folder if you would > want use fingerprint for other stuff. > Hope this helps. Thanks but no thanks. I followed your instruction up until Reboot and check if the fingerprint options are shown in User settings. Now you should be able to add your fingerprint(s). If this doesn't work for you, consider downgrading fprintd to version 1.90.9-1. Also you could try to add them manually using `fprintd-enroll`. Now assuming you have enrolled your fingerprint(s). You can check if the fingerprint is working for lock screen and login screen. Keep in mind that login in with fingerprint works but it won't unlock the KWallet so I recommend login in with password, but you can unlock screen or use approve sudo commands with fingerprint. In case this is not automatically setup by KDE you can do: sudo pam-auth-update (use space bar to enable the "Fingerprint authentication") I enrolled two figerprints. Logging in after "lock" worked - almost: I had to press "enter" and then got a prompt to touch the fp device. That was ok. Then I tried to log out and log in -- and theh sytem is **now frozen**. I am unable to log in in any way I can think of!!! How can I revert to my working system, from 10 minutes ago? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413104] Left-click mouse actions on Desktop don't work in Desktop layout, works fine in Folderview
https://bugs.kde.org/show_bug.cgi?id=413104 Nate Graham changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413104] Left-click mouse actions on Desktop don't work in Desktop layout, works fine in Folderview
https://bugs.kde.org/show_bug.cgi?id=413104 Nate Graham changed: What|Removed |Added CC||richte...@protonmail.com --- Comment #26 from Nate Graham --- *** Bug 423217 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423217] Wallpaper plugins dont receive left click events in desktop view layout
https://bugs.kde.org/show_bug.cgi?id=423217 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Nate Graham --- Ah, this. It's the same as Bug 413104 which is being fixed imminently. That's for the reminder! *** This bug has been marked as a duplicate of bug 413104 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #40 from Nate Graham --- The issue only affected Plasma 5.25+Frameworks 5.98. The combination of Plasma 5.24+Frameworks 5.98 isn't affected. Regardless, patching this fix into your 5.98 and then later shipping the re-spun 5.98 is highly recommended! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423217] Wallpaper plugins dont receive left click events in desktop view layout
https://bugs.kde.org/show_bug.cgi?id=423217 k...@gnoumph.mozmail.com changed: What|Removed |Added CC||k...@gnoumph.mozmail.com --- Comment #3 from k...@gnoumph.mozmail.com --- This issue is still there on KDE Plasma 5.25.5, KDE Frameworks 5.97.0 and Qt 5.15.5. Trying to find a workaround but nothing for now... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #39 from Michael Mikowski --- (In reply to Nate Graham from comment #38) > ^^ That should fix it for people with Plasma 5.25 > > The fix will officially land in Frameworks 5.99 and we're coordinating to > have a re-spin of Frameworks 5.98 released. Even if that doesn't end up > happening (but I think it will), distros will be patching this in directly > ASAP. Nate, can you or another confirm if this is or is not recommended for Frameworks 5.98 + Plasma 5.24 LTS? As posted in comment 24, I didn't see any problems with this combination. I tried to copy Rik Mills for Kubuntu, but can't find him on the CC list. He certainly would be interested as that is the current state of Kubuntu + backports. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442782] KDE Connect is draining battery
https://bugs.kde.org/show_bug.cgi?id=442782 --- Comment #4 from Jaroslav Skarvada --- +1, please add option to disable and manual enable only when needed. Otherwise it's unusable for me. Moreover, it's better for security not to run services you don't need at the moment. -- You are receiving this mail because: You are watching all bug changes.
