[plasmashell] [Bug 469308] New: Please add option for enable confirmation before delete autostart item in KDE Plasma System Settings -> Startup and Shutdown -> Autostart.
https://bugs.kde.org/show_bug.cgi?id=469308 Bug ID: 469308 Summary: Please add option for enable confirmation before delete autostart item in KDE Plasma System Settings -> Startup and Shutdown -> Autostart. Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: igor_penz...@bk.ru CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 158650 --> https://bugs.kde.org/attachment.cgi?id=158650&action=edit Screenshot SUMMARY: Sadly (but not critical), I'm deleted necessary autostart item with Plasma Settings GUI (Plasma System Settings -> Startup and Shutdown -> Autostart), but not remember his name for recover it. I'm have btrfs backups, but this snapshots dont include $HOME folder (in $HOME/.config/autostart I have several items). Please add option for enable confirmation before delete item in KDE Plasma System Settings -> Startup and Shutdown -> Autostart. STEPS TO REPRODUCE: 1. Goto Plasma System Settings -> Startup and Shutdown -> Autostart 2. Press "-" (delete) button for autostart item OBSERVED RESULT: Optional confirmation before delete EXPECTED RESULT: No optional confirmation before delete SOFTWARE/OS VERSIONS: Linux/KDE Plasma: all (I'm use Arch Linux/Fedora/Debian/OpenSUSE) KDE Plasma Version: all (5.*) KDE Frameworks Version: all (5.*) Qt Version: all (5.*) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 464900] New: Spotify crashes Plasma
https://bugs.kde.org/show_bug.cgi?id=464900 Bug ID: 464900 Summary: Spotify crashes Plasma Classification: Applications Product: krusader Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: igor_penz...@bk.ru CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.8.0 "A New Day") Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 6.1.4-203.fsync.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Nobara Linux 37 (KDE Plasma) DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: When I'm playing music in Spotify, I switch to another app in taskbar. And sometimes after it Plasma crashed. In error log I see Spotify. The crash can be reproduced sometimes. -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault [KCrash Handler] #4 0x7fc4f8ad2ad3 in QObject::property(char const*) const () from /lib64/libQt5Core.so.5 #5 0x7fc4fa073794 in KUiServerV2JobTracker::registerJob(KJob*) () from /lib64/libKF5JobWidgets.so.5 #6 0x7fc4fa0707fc in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libKF5JobWidgets.so.5 #7 0x7fc4f8adbc26 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7fc4f8adbc26 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7fc4f9dd6843 in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /lib64/libQt5DBus.so.5 #10 0x7fc4f9dd7182 in QDBusServiceWatcher::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5DBus.so.5 #11 0x7fc4f9dd763b in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/libQt5DBus.so.5 #12 0x7fc4f9d880bb in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5 #13 0x7fc4f8ad2ec4 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7fc4f97aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7fc4f8aa8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7fc4f8aab5e4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #17 0x7fc4f8af9897 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #18 0x7fc4f7319cbf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #19 0x7fc4f736f598 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #20 0x7fc4f7316f40 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #21 0x7fc4f8af938a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7fc4f8aa6cca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7fc4f8aaed92 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #24 0x563372c5416f in main () [Inferior 1 (process 17392) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 464900] Spotify crashes Plasma
https://bugs.kde.org/show_bug.cgi?id=464900 Igor changed: What|Removed |Added Version|unspecified |2.8.0 CC||igor_penz...@bk.ru -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 408890] Livepreview runs BibTeX instead of Biber
https://bugs.kde.org/show_bug.cgi?id=408890 Igor changed: What|Removed |Added CC||i...@sai.msu.ru --- Comment #3 from Igor --- Five years since the original bug report, and I just run across the same bug with kile 2.9.94. When using biblatex with the biber backend in my source latex file, pressing "latex" button still runs bibtex instead of biber, which results in the error message "[BibTex] Finished with the exit code 2". Inspecting logs shows that (quite naturally) bibtex did not find any citations. The difference with the bug report above is that in my case the Build->Biber setting includes "biber" in the command line (not /usr/bin/biber). For the bug report author this solved the problem. For me, it does not. The rough workaround is to change "bibtex" by "biber" in the command line of the Build->Bibtex setting. This is clearly not the best solution. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484536] Unable to login using Wayland after OS update.
https://bugs.kde.org/show_bug.cgi?id=484536 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 482015] Kup system tray icon and settings module missing on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482015 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 484098] New: Keysmith does not encrypt your data
https://bugs.kde.org/show_bug.cgi?id=484098 Bug ID: 484098 Summary: Keysmith does not encrypt your data Classification: Applications Product: Keysmith Version: 24.02.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: bhus...@gmail.com Reporter: igorpa...@tutanota.com Target Milestone: --- If a malicious person gains access to a person's computer. It will have full access to Keysmith data in "~/.config/org.kde.keysmith". This is because the data is not encrypted. -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 484098] Keysmith does not encrypt your data
https://bugs.kde.org/show_bug.cgi?id=484098 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Show non-linear virtual desktop arrangements again
https://bugs.kde.org/show_bug.cgi?id=475077 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457637] New: window selector in wayland
https://bugs.kde.org/show_bug.cgi?id=457637 Bug ID: 457637 Summary: window selector in wayland Product: systemsettings Version: 5.25.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: igorpa...@tutanota.com Target Milestone: --- Application: systemsettings (5.25.4) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.18.15-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: In the window selector when you press the display button, on the side where you choose the task selection effects, it does not close automatically. The crash can be reproduced every time. -- Backtrace: Application: Configurações do sistema (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f0622d1e645 in wl_map_insert_at (map=map@entry=0x55aa9a885020, flags=flags@entry=1, i=112, data=) at ../src/wayland-util.c:276 #5 0x7f0622d1e7a3 in proxy_destroy (proxy=0x55aa9b36b2e0) at ../src/wayland-client.c:510 #6 0x7f0622d20306 in wl_proxy_destroy_caller_locks (proxy=0x55aa9b36b2e0) at ../src/wayland-client.c:530 #7 wl_proxy_marshal_array_flags (proxy=proxy@entry=0x55aa9b36b2e0, opcode=opcode@entry=0, interface=interface@entry=0x0, version=version@entry=1, flags=flags@entry=1, args=args@entry=0x7ffdc30601f0) at ../src/wayland-client.c:868 #8 0x7f0622d20e05 in wl_proxy_marshal_flags (proxy=0x55aa9b36b2e0, opcode=0, interface=0x0, version=1, flags=1) at ../src/wayland-client.c:791 #9 0x7f0600f7df8e in wl_buffer_destroy (wl_buffer=0x55aa9b36b2e0) at /usr/include/wayland/wayland-client-protocol.h:2025 #10 KWayland::Client::WaylandPointer::release (this=0x55aa9b36d4d8) at /usr/src/debug/kwayland-5.96.0-1.1.x86_64/src/client/wayland_pointer_p.h:44 #11 KWayland::Client::Buffer::Private::~Private (this=, this=) at /usr/src/debug/kwayland-5.96.0-1.1.x86_64/src/client/buffer.cpp:38 #12 QScopedPointerDeleter::cleanup (pointer=0x55aa9b36d4d0) at /usr/include/qt5/QtCore/qscopedpointer.h:60 #13 QScopedPointerDeleter::cleanup (pointer=0x55aa9b36d4d0) at /usr/include/qt5/QtCore/qscopedpointer.h:52 #14 QScopedPointer >::~QScopedPointer (this=, this=) at /usr/include/qt5/QtCore/qscopedpointer.h:107 #15 KWayland::Client::Buffer::~Buffer (this=, this=) at /usr/src/debug/kwayland-5.96.0-1.1.x86_64/src/client/buffer.cpp:58 #16 0x7f0600fb46f2 in QtSharedPointer::CustomDeleter::execute (this=) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:187 #17 QtSharedPointer::ExternalRefCountWithCustomDeleter::deleter (self=) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:205 #18 0x7f0600fb98a6 in QtSharedPointer::ExternalRefCountData::destroy (this=0x55aa9b36b340) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:149 #19 QSharedPointer::deref (dd=0x55aa9b36b340) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:458 #20 QSharedPointer::deref (dd=0x55aa9b36b340) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:454 #21 QSharedPointer::deref (this=0x55aa9b36b360) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:453 #22 QSharedPointer::~QSharedPointer (this=, this=) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:310 #23 QList >::node_destruct (this=, to=0x55aa9bf98da8, from=0x55aa9bf98da8) at /usr/include/qt5/QtCore/qlist.h:524 #24 QList >::dealloc(QListData::Data*) [clone .isra.0] (data=0x55aa9bf98d90, this=) at /usr/include/qt5/QtCore/qlist.h:921 #25 0x7f0600fa9dc5 in QList >::~QList (this=, this=) at /usr/include/qt5/QtCore/qlist.h:871 #26 QList >::~QList (this=, this=) at /usr/include/qt5/QtCore/qlist.h:871 #27 QList >::operator= (other=..., this=) at /usr/include/qt5/QtCore/qlist.h:167 #28 QList >::clear (this=) at /usr/include/qt5/QtCore/qlist.h:930 #29 KWayland::Client::ShmPool::release (this=this@entry=0x55aa9b36d520) at /usr/src/debug/kwayland-5.96.0-1.1.x86_64/src/client/shm_pool.cpp:65 #30 0x7f0600fa9e3a in KWayland::Client::ShmPool::~ShmPool (this=, this=) at /usr/src/debug/kwayland-5.96.0-1.1.x86_64/src/client/shm_pool.cpp:60 #31 0x7f0600fa9f09 in KWayland::Client::ShmPool::~ShmPool (this=, this=) at /usr/src/debug/kwayland-5.96.0-1.1.x86_64/src/client/shm_pool.cpp:61 #32 0x7f061d94ba4d in QScopedPointerDeleter::cleanup (pointer=) at /usr/include/qt5/QtCore/qscopedpointer.h:60 #33 QScopedPointer >::~QScopedPointer (this=, this=) at /usr/include/qt5/QtCore/qscopedpointer.h:107 #34 WindowShadowTile::~WindowShadowTile (this=, this=) at /usr/src/debug/kwayland-integration-5.25.4-1.1.x86_64/src/windowsystem/windowshadow.cpp:18 #35 WindowShadowTile::~WindowShadowTile (this=, this=) at /usr/src/debug/kwayland-integration-5.25.4-1.1.x86_64/src/windowsystem/windowshadow.cpp:18 #36 0x7f05d4839fea in QtSharedPointer::ExternalRefCountData::destroy
[systemsettings] [Bug 457637] window selector in wayland
https://bugs.kde.org/show_bug.cgi?id=457637 --- Comment #2 from Igor --- He really got confused. I put an Imgur image to facilitate understanding. https://i.imgur.com/XOzWwQk.png -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457637] window selector in wayland
https://bugs.kde.org/show_bug.cgi?id=457637 --- Comment #3 from Igor --- When clicked there on the wayland it creates a preview window, however, it is not closed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427476] When the top layer is set to invisible (eye closed), you can't create a "new layer from visible"
https://bugs.kde.org/show_bug.cgi?id=427476 Igor changed: What|Removed |Added CC||igortechnicalm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427476] When the top layer is set to invisible (eye closed), you can't create a "new layer from visible"
https://bugs.kde.org/show_bug.cgi?id=427476 --- Comment #2 from Igor --- The bug uprose with version 4.4 of Krita, in 4.3 is Ok. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435593] New: System Settings crash
https://bugs.kde.org/show_bug.cgi?id=435593 Bug ID: 435593 Summary: System Settings crash Product: systemsettings Version: 5.21.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: igorpa...@tutanota.com Target Milestone: --- Application: systemsettings5 (5.21.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.11-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.21.3 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: After installing a global theme and switching to the application style the system Settings closes. The crash can be reproduced sometimes. -- Backtrace: Application: Configurações do sistema (systemsettings5), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fe8a6f3bf80 (LWP 6174))] [KCrash Handler] #6 QScopedPointer >::operator->() const (this=0x8) at /usr/include/qt5/QtCore/qscopedpointer.h:116 #7 qGetPtrHelper > >(QScopedPointer >&) (ptr=...) at /usr/include/qt5/QtCore/qglobal.h:1135 #8 QQmlEngine::d_func() (this=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-3.1.x86_64/src/qml/qml/qqmlengine.h:172 #9 QQmlEnginePrivate::get(QQmlEngine*) (e=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-3.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmlengine_p.h:424 #10 QQmlPropertyPrivate::initProperty(QObject*, QString const&) (this=0x55b4cfe75e40, obj=, name=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-3.1.x86_64/src/qml/qml/qqmlproperty.cpp:277 #11 0x7fe8a906146d in QQmlProperty::QQmlProperty(QObject*, QString const&, QQmlContext*) (this=0x7ffee4691290, obj=0x55b4cfba3df0, name=..., ctxt=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-3.1.x86_64/src/qml/qml/qqmlproperty.cpp:207 #12 0x7fe854d2991b in SizeGroup::adjustItems(SizeGroup::Mode) (this=this@entry=0x55b4ced59a80, whatChanged=) at /usr/src/debug/kirigami2-5.80.0-1.1.x86_64/src/sizegroup.cpp:106 #13 0x7fe854d29d5e in SizeGroup::connectItem(QQuickItem*) (item=, this=0x55b4ced59a80) at /usr/src/debug/kirigami2-5.80.0-1.1.x86_64/src/sizegroup.cpp:43 #14 SizeGroup::appendItem(QQmlListProperty*, QQuickItem*) (prop=, value=) at /usr/src/debug/kirigami2-5.80.0-1.1.x86_64/src/sizegroup.cpp:16 #15 0x7fe8a90c6ac1 in QV4::PropertyListPrototype::method_push(QV4::FunctionObject const*, QV4::Value const*, QV4::Value const*, int) (b=, thisObject=, argv=, argc=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-3.1.x86_64/src/qml/qml/qqmllistwrapper.cpp:255 #16 0x7fe8a8fb78ca in QV4::FunctionObject::call(QV4::Value const*, QV4::Value const*, int) const (argc=1, argv=0x7fe831bb4518, thisObject=0x7fe831bb4538, this=0x7ffee4691428) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-3.1.x86_64/src/qml/jsruntime/qv4functionobject_p.h:172 #17 QV4::Runtime::CallPropertyLookup::call(QV4::ExecutionEngine*, QV4::Value const&, unsigned int, QV4::Value*, int) (engine=0x55b4ce9d8450, base=..., index=, argv=0x7fe831bb4518, argc=1) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-3.1.x86_64/src/qml/jsruntime/qv4runtime.cpp:1460 #18 0x7fe845610f6b in () #19 0x in () [Inferior 1 (process 6174) detached] Possible duplicates by query: bug 434804, bug 434156, bug 428294, bug 426090, bug 422963. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419827] Reload original preset doesn't work
https://bugs.kde.org/show_bug.cgi?id=419827 Igor changed: What|Removed |Added CC||kero...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 473137] New: Latte Dock crashes when try to find a widget
https://bugs.kde.org/show_bug.cgi?id=473137 Bug ID: 473137 Summary: Latte Dock crashes when try to find a widget Classification: Plasma Product: lattedock Version: 0.10.8 Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: igor2010...@yandex.ru Target Milestone: --- Application: latte-dock (0.10.8) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-26-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Latte dock crashes when trying to find a new widget The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7f7aa439dd34 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f7aa43ccc0f in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f7aa43b5295 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f7aa43ba525 in QSGBatchRenderer::Renderer::renderBatches() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f7aa43bb086 in QSGBatchRenderer::Renderer::render() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f7aa43a27b4 in QSGRenderer::renderScene(QSGBindable const&) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f7aa440f1f2 in QSGOpenGLLayer::grab() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f7aa440f7f5 in QSGOpenGLLayer::updateTexture() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f7aa457bea6 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f7aa43a2f0c in QSGRenderer::preprocess() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f7aa43a277b in QSGRenderer::renderScene(QSGBindable const&) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7f7aa43a2c63 in QSGRenderer::renderScene(unsigned int) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f7aa44070d7 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x7f7aa4475779 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7f7aa44152e7 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f7aa44161c7 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f7aa207 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f7aa188f18a in start_thread (arg=) at ./nptl/pthread_create.c:444 #22 0x7f7aa191dbd0 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 19 (Thread 0x7f7a2cbfe6c0 (LWP 131682) "latte-do:gdrv0"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x5613e76403a8) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5613e76403a8, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f7aa188e0c8 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5613e7640358, cond=0x5613e7640380) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x5613e7640380, mutex=0x5613e7640358) at ./nptl/pthread_cond_wait.c:627 #5 0x7f7a96111f8d in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x7f7a960c239b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7f7a96111ebb in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x7f7aa188f18a in start_thread (arg=) at ./nptl/pthread_create.c:444 #9 0x7f7aa191dbd0 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 18 (Thread 0x7f7a2d4216c0 (LWP 131681) "latte-:traceq0"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x5613e76338d0) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5613e76338d0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f7aa188e0c8 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5613e7633880, cond=0x5613e76338a8) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x5613e76338a8, mutex=0x5613e7633880) at ./nptl/pthread_cond_wait.c:627 #5 0x7f7a96111f8d in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x7f7a960c239b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7f7a96111
[Alligator] [Bug 465220] [Feature] Selection mode for posts, and then mark posts as read/unread
https://bugs.kde.org/show_bug.cgi?id=465220 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 475785] Add a filter bar
https://bugs.kde.org/show_bug.cgi?id=475785 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 475427] Import/export functionality
https://bugs.kde.org/show_bug.cgi?id=475427 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 476689] New: Numerical list with incorrect order
https://bugs.kde.org/show_bug.cgi?id=476689 Bug ID: 476689 Summary: Numerical list with incorrect order Classification: Applications Product: ghostwriter Version: 23.08.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: igorpa...@tutanota.com Target Milestone: --- SUMMARY When a numeric list is created, the numbers are confused when using the keyboard shortcuts. STEPS TO REPRODUCE 1. Start a numeric list and add any text and press enter 2. Again add some text and press enter 3. press tab and add any text 4. lastly, apert shift + tab is the error that occurs OBSERVED RESULT The list is as follows: 1. any 2. any 1. any 2. any The view is correct only in the editor is incorrect. Image: https://i.imgur.com/7eCgqpC.png EXPECTED RESULT 1. any 2. any 1. any 3. any SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231106 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-1-default (64-bit) Graphics Platform: X11 Processors: 6 × AMD Ryzen 5 3500 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series Manufacturer: Colorful Technology And Development Co.,LTD Product Name: A320M-K PRO -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 463992] New: Valgrind fails to run
https://bugs.kde.org/show_bug.cgi?id=463992 Bug ID: 463992 Summary: Valgrind fails to run Classification: Developer tools Product: valgrind Version: 3.18.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: ikoro...@gmail.com Target Milestone: --- SUMMARY Trying to run valgrind I get the following output: [code] igor@WaylandGnome ~/dbhandler/Debug/dbhandler $ valgrind --leak-check=full --verbose dbhandler ==6136== Memcheck, a memory error detector ==6136== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==6136== Using Valgrind-3.18.1-42b08ed5bd-20211015 and LibVEX; rerun with -h for copyright info ==6136== Command: dbhandler ==6136== --6136-- Valgrind options: --6136----leak-check=full --6136----verbose --6136-- Contents of /proc/version: --6136-- Linux version 5.10.52-gentoo (root@WaylandGnome) (gcc (Gentoo 10.3.0-r2 p3) 10.3.0, GNU ld (Gentoo 2.35.2 p1) 2.35.2) #19 SMP Tue Aug 31 09:20:30 CDT 2021 --6136-- --6136-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c --6136-- Page sizes: currently 4096, max supported 4096 --6136-- Valgrind library directory: /usr/libexec/valgrind --6136-- Reading syms from /usr/local/bin/dbhandler --6136-- Reading syms from /lib64/ld-2.33.so --6136-- Considering /usr/lib/debug/lib64/ld-2.33.so.debug .. --6136-- .. CRC is valid --6136-- Reading syms from /usr/libexec/valgrind/memcheck-amd64-linux --6136-- Considering /usr/lib/debug/usr/libexec/valgrind/memcheck-amd64-linux.debug .. --6136-- .. CRC is valid --6136--object doesn't have a dynamic symbol table --6136-- Scheduler: using generic scheduler lock implementation. --6136-- Reading suppressions file: /usr/libexec/valgrind/default.supp ==6136== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-6136-by-igor-on-??? ==6136== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-6136-by-igor-on-??? ==6136== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-6136-by-igor-on-??? ==6136== ==6136== TO CONTROL THIS PROCESS USING vgdb (which you probably ==6136== don't want to do, unless you know exactly what you're doing, ==6136== or are doing some strange experiment): ==6136== /usr/libexec/valgrind/../../bin/vgdb --pid=6136 ...command... ==6136== ==6136== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==6136== /path/to/gdb dbhandler ==6136== and then give GDB the following command ==6136== target remote | /usr/libexec/valgrind/../../bin/vgdb --pid=6136 ==6136== --pid is optional if only one valgrind process is running ==6136== vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4 0x0 0x0 0x89 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==6136== valgrind: Unrecognised instruction at address 0x40197cf. ==6136==at 0x40197CF: get_common_indices.constprop.0 (in /lib64/ld-2.33.so) ==6136==by 0x401ACB6: init_cpu_features.constprop.0 (in /lib64/ld-2.33.so) ==6136==by 0x401BE1D: _dl_sysdep_start (in /lib64/ld-2.33.so) ==6136==by 0x4001FDB: _dl_start (in /lib64/ld-2.33.so) ==6136==by 0x4001057: ??? (in /lib64/ld-2.33.so) ==6136== Your program just tried to execute an instruction that Valgrind ==6136== did not recognise. There are two possible reasons for this. ==6136== 1. Your program has a bug and erroneously jumped to a non-code ==6136==location. If you are running Memcheck and you just saw a ==6136==warning about a bad jump, it's probably your program's fault. ==6136== 2. The instruction is legitimate but Valgrind doesn't handle it, ==6136==i.e. it's Valgrind's fault. If you think this is the case or ==6136==you are not sure, please let us know and we'll try to fix it. ==6136== Either way, Valgrind will now raise a SIGILL signal which will ==6136== probably kill your program. ==6136== ==6136== Process terminating with default action of signal 4 (SIGILL) ==6136== Illegal opcode at address 0x40197CF ==6136==at 0x40197CF: get_common_indices.constprop.0 (in /lib64/ld-2.33.so) ==6136==by 0x401ACB6: init_cpu_features.constprop.0 (in /lib64/ld-2.33.so) ==6136==by 0x401BE1D: _dl_sysdep_start (in /lib64/ld-2.33.so) ==6136==by 0x4001FDB: _dl_start (in /lib64/ld-2.33.so) ==6136==by 0x4001057: ??? (in /lib64/ld-2.33.so) ==6136== ==6136== HEAP SUMMARY: ==6136== in use at exit: 0 bytes in 0 blocks ==6136== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==6136== ==6136== All heap blocks were freed -- no leaks are possible ==6136== ==6136== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Illegal instruction igor@WaylandGnome ~/d
[krita] [Bug 448254] New: zoom / movement of the canvas does not work
https://bugs.kde.org/show_bug.cgi?id=448254 Bug ID: 448254 Summary: zoom / movement of the canvas does not work Product: krita Version: 5.0.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: kero...@gmail.com Target Milestone: --- After switching the language (shift+alt) and enabling / disabling the grid with short keys (shift + ctrl + '), zoom / movement of the canvas does not work STEPS TO REPRODUCE 1. switching the language (shift+alt) 2. show grid (shift + ctrl + ') 3. zoom / movement of the canvas does not work SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447030] New: Ctrl+click at thumbnail for selection should not make the clicked layer active and just make a selection
https://bugs.kde.org/show_bug.cgi?id=447030 Bug ID: 447030 Summary: Ctrl+click at thumbnail for selection should not make the clicked layer active and just make a selection Product: krita Version: 4.4.8 Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: igortechnicalm...@gmail.com Target Milestone: --- Ctrl+Click at thumbnail for selection should not make the clicked layer active and just make only a selection Usage: -- Now while working in certain layer and need only selection from pixels that have other layer you need to additionally click back into working layer. The proposal feature removes this unnecessary step. -- It would be more comfortable for artists who use other painting apps parallel with Krita Discussion is here: https://krita-artists.org/t/make-selection-from-layer-without-selecting-jumping-to-layer-itself/33278/12 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429628] Dolphin Crashes on Start
https://bugs.kde.org/show_bug.cgi?id=429628 Igor changed: What|Removed |Added CC||svoek...@bk.ru --- Comment #17 from Igor --- This method helped me. Try not just to call the Dolphin. Try to open some directory, for example: `dolphin /home/username/Downloads`. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429628] Dolphin Crashes on Start
https://bugs.kde.org/show_bug.cgi?id=429628 Igor changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REPORTED --- Comment #27 from Igor --- The problem repeats if I use the search in the Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429628] Dolphin Crashes on Start
https://bugs.kde.org/show_bug.cgi?id=429628 --- Comment #31 from Igor --- This is a strange bug. Once more, i have the dolphin crash after using search. The dolphin also crashed at startup every time. Then I downloaded some file and clicked "open folder" from the browser interface. And the the dolphin started working! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413533] Tools disappear from toolbar after closing program
https://bugs.kde.org/show_bug.cgi?id=413533 Igor changed: What|Removed |Added CC||igortechnicalm...@gmail.com --- Comment #4 from Igor --- I noticed some similar thing. Any tool from “Toolbox” is disappeared in “Toolbar” after restart. Krita version is 4.4.1 and 4.4.2 beta 2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461912] New: Artifacts with rectangular grid
https://bugs.kde.org/show_bug.cgi?id=461912 Bug ID: 461912 Summary: Artifacts with rectangular grid Classification: Applications Product: krita Version: 5.1.3 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: kero...@gmail.com Target Milestone: --- Created attachment 153810 --> https://bugs.kde.org/attachment.cgi?id=153810&action=edit Artifacts with rectangular grid Artifacts with rectangular grid STEP TO REPRODUCE 1. Create a new document 2. Select any brush (basic-1) 3. Select black (dark) color 4. Move the brush over the grid (not painting, move cursor), paint, again move the brush over the grid OBSERVED RESULT Artifacts appear and disappear on a rectangular grid. (grid is colored) EXPECTED RESULT Grid must not be painted SOFTWARE/OS VERSIONS Windows 11 Pro 22H2 22621.819 ADDITIONAL INFORMATION Artifacts only on a rectangular grid, no artifacts on an isometric grid -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489638] Plasma crashed in QWindowPrivate::connectToScreen() when trying to open Klipper paste menu with keyboard shortcut Meta+V
https://bugs.kde.org/show_bug.cgi?id=489638 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 408890] Livepreview runs BibTeX instead of Biber
https://bugs.kde.org/show_bug.cgi?id=408890 --- Comment #7 from Igor --- (In reply to Andrew Nowa Ammerlaan from comment #6) > As a workaround: In ~/.config/kilerc ... Thanks for your comments. With this workaround, will bibtex be also auto-detected? If not, it has no advantage over my workaround - to replace "bibtex" by "biber" in the Build-BibTex setting. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420006] system settings crash
https://bugs.kde.org/show_bug.cgi?id=420006 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420093] New: Crash: global short cuts
https://bugs.kde.org/show_bug.cgi?id=420093 Bug ID: 420093 Summary: Crash: global short cuts Product: systemsettings Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: igorpa...@tutanota.com Target Milestone: --- Application: systemsettings5 (5.18.4) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.5.17-xanmod1 x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I pressed the standard button and you are in current component. Also I can't see all the default shortcuts shows the error: org.freedesktop.DBus.Error.NoReply The crash can be reproduced every time. -- Backtrace: Application: Configurações do Sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc3e9336800 (LWP 30988))] Thread 7 (Thread 0x7fc3a7b3b700 (LWP 30999)): #0 0x7fc3e47a20b4 in __GI___libc_read (fd=13, buf=0x7fc3a7b3abde, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fc3b0942021 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7fc3b0bc0a2e in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fc3b0bc14a0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fc3b0bc1560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fc3b0bcf3c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fc3b0971318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7fc3e01de6db in start_thread (arg=0x7fc3a7b3b700) at pthread_create.c:463 #8 0x7fc3e47b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fc3c0ed3700 (LWP 30994)): #0 0x7fc3e01e49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55df7ee6f798) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55df7ee6f748, cond=0x55df7ee6f770) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55df7ee6f770, mutex=0x55df7ee6f748) at pthread_cond_wait.c:655 #3 0x7fc3c35694fb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fc3c35690e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fc3e01de6db in start_thread (arg=0x7fc3c0ed3700) at pthread_create.c:463 #6 0x7fc3e47b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fc3c16d4700 (LWP 30993)): #0 0x7fc3e01e49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55df7ee6f798) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55df7ee6f748, cond=0x55df7ee6f770) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55df7ee6f770, mutex=0x55df7ee6f748) at pthread_cond_wait.c:655 #3 0x7fc3c35694fb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fc3c35690e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fc3e01de6db in start_thread (arg=0x7fc3c16d4700) at pthread_create.c:463 #6 0x7fc3e47b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fc3c1ed5700 (LWP 30992)): #0 0x7fc3e01e49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55df7ee6f798) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55df7ee6f748, cond=0x55df7ee6f770) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55df7ee6f770, mutex=0x55df7ee6f748) at pthread_cond_wait.c:655 #3 0x7fc3c35694fb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fc3c35690e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fc3e01de6db in start_thread (arg=0x7fc3c1ed5700) at pthread_create.c:463 #6 0x7fc3e47b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fc3c26d6700 (LWP 30991)): #0 0x7fc3e01e49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55df7ee6f798) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55df7ee6f748, cond=0x55df7ee6f770) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55df7ee6f770, mutex=0x55df7ee6f748) at pthread_cond_wait.c:655 #3 0x7fc3c35694fb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fc3c35690e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fc3e01de6db in start_thread (arg=0x7fc3c26d6700) at pthread_create.c:463 #6 0x7fc3e47b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
[krita] [Bug 417040] New: No pressure at first stamp in floating dock mode
https://bugs.kde.org/show_bug.cgi?id=417040
Bug ID: 417040
Summary: No pressure at first stamp in floating dock mode
Product: krita
Version: 4.2.8
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: Dockers
Assignee: krita-bugs-n...@kde.org
Reporter: igortechnicalm...@gmail.com
Target Milestone: ---
SUMMARY
I lost pressure sensitivity at first stroke after switching from float docks (I
use brush preset, history of brushes, artistic color picker) . It doesn’t
happen each time, about 2/3 or 2/4.
Screenshot:
https://krita-artists.org/uploads/default/original/2X/e/e10a7fc50393190be95545ff60c1284afa648105.jpeg
Video:
https://youtu.be/6X9kABr41Zw
The same effect if I switching from other program e.g. browser or video player
back to Krita.
In attached dock mode all OK except switching from other programs.
It happens only in WinTab mode. WinInk doesn't have such bug (but alas have
other)
The current “First stump” issue is only Krita “feature” (other painting
software is ok).
I and other users tested it with the same result on various systems:
Ryzen 1600 + GTX960
Athlon 200GE + internal GPU
I3 6100 + internal GPU
i3 4030 + internal GPU
i7 9700K + RTX 2070
Intuos5, Cintiq 13hd + ProPen (KP-503E stylus)
Systems used with Single Display and with Two displays.
Windows 7, 8, 10
It seems concern only senior series of wacom tablets (Intuos 4, 5, Pro, Pro2
and Cintiqs). Wacom Intuos Draw ("Bamboo" types) doesn't have that issue.
STEPS TO REPRODUCE
0. Need Wacom Intuos (from 4 up to Pro2) or any Cintiq
1. Be sure using WinTab mode
2. Undock (make float) color selector
3. Make a brush stroke, change color
4. Repeat №3 several times
ADDITIONAL INFORMATION
forum discussion link:
https://krita-artists.org/t/no-pressure-at-first-stamp-in-floating-dock-mode/1847
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 417040] No pressure at first stamp in floating dock mode
https://bugs.kde.org/show_bug.cgi?id=417040 --- Comment #3 from Igor --- (In reply to Boudewijn Rempt from comment #1) > Could you please make a tablet log, too? I'm afraid that it'll turn out to > be a driver problem (because behaviour differs from tablet to tablet) and > that we cannot do much, but a tablet log would show whether we get tablet > events at all when the main window get focus. See > https://docs.krita.org/en/contributors_manual/user_support.html#gathering- > information Log: https://invent.kde.org/uploads/-/system/user/983/a32e3b1523e13b830a4442380bdc7fbc/tablet_log2 Screenshot with strokes during logging: https://invent.kde.org/uploads/-/system/user/983/8d55a8e2fa16a9c3d60cb2ffe15fd424/tablet_log2_strokes.jpg -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417040] No pressure at first stamp in floating dock mode
https://bugs.kde.org/show_bug.cgi?id=417040 --- Comment #6 from Igor --- (In reply to Boudewijn Rempt from comment #5) > I'm sorry, but those links are broken :-( Hmm, log is opened without problem, only image has a problem. I reuploaded files to "yandex" https://yadi.sk/d/N0Nvg1auErvLgg -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395449] Show used tool and/or brush in undo history entries
https://bugs.kde.org/show_bug.cgi?id=395449 Igor changed: What|Removed |Added CC||igortechnicalm...@gmail.com --- Comment #1 from Igor --- Vote for the feature. And link to discussion https://krita-artists.org/t/exact-name-of-brush-presets-in-the-undo-history/4350/4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417040] No pressure at first stamp in floating dock mode
https://bugs.kde.org/show_bug.cgi?id=417040 Igor changed: What|Removed |Added Version|4.2.8 |4.2.9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419922] New: Plasma crash
https://bugs.kde.org/show_bug.cgi?id=419922 Bug ID: 419922 Summary: Plasma crash Product: plasmashell Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: igorpa...@tutanota.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.4) Qt Version: 5.14.1 Frameworks Version: 5.68.0 Operating System: Linux 5.5.15-xanmod1 x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I pressed the right mouse button - Unusual behavior I noticed: The panel disappeared, but it came right back. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4c299fe800 (LWP 3474))] Thread 26 (Thread 0x7f4b66e1f700 (LWP 11254)): #0 0x7f4c22dd70b4 in __GI___libc_read (fd=38, buf=0x7f4b66e1ebde, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f4bd2dd5021 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f4bd3487a2e in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f4bd34884a0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f4bd3488560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f4bd34963c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f4bd2e04318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7f4c201736db in start_thread (arg=0x7f4b66e1f700) at pthread_create.c:463 #8 0x7f4c22de888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f4b81034700 (LWP 10136)): #0 0x7f4c201799f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560910acfff0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560910acffa0, cond=0x560910acffc8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560910acffc8, mutex=0x560910acffa0) at pthread_cond_wait.c:655 #3 0x7f4c234f9d9b in QWaitConditionPrivate::wait (deadline=..., this=0x560910acffa0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x560906735240, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f4c234f9f19 in QWaitCondition::wait (this=0x56090e190718, mutex=0x560906735240, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f4bdac95855 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f4bdac996b8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f4bdac94b1d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f4bdac99712 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f4bdac94b1d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f4bdac99712 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7f4bdac94b1d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7f4bdac99712 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7f4bdac94b1d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x7f4bdac9757b in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x7f4c234f37ec in QThreadPrivate::start (arg=0x56090a81f620) at thread/qthread_unix.cpp:342 #17 0x7f4c201736db in start_thread (arg=0x7f4b81034700) at pthread_create.c:463 #18 0x7f4c22de888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f4b81835700 (LWP 10135)): #0 0x7f4c201799f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560910acfff0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560910acffa0, cond=0x560910acffc8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560910acffc8, mutex=0x560910acffa0) at pthread_cond_wait.c:655 #3 0x7f4c234f9d9b in QWaitConditionPrivate::wait (deadline=..., this=0x560910acffa0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x560906735240, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f4c234f9f19 in QWaitCondition::wait (this=0x56090e190718, mutex=0x56090673
[ktorrent] [Bug 414374] New: Remove Unnecessary code
https://bugs.kde.org/show_bug.cgi?id=414374 Bug ID: 414374 Summary: Remove Unnecessary code Product: ktorrent Version: 5.1 Platform: Compiled Sources OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: i...@itn.ru Target Milestone: --- Created attachment 124049 --> https://bugs.kde.org/attachment.cgi?id=124049&action=edit Unnecessary code. SUMMARY Unnecessary code. STEPS TO REPRODUCE 1. Start ktorrent OBSERVED RESULT 1. Do not touch the original torrent files (useless overwriting the file without changes). 2. At startup, I save 16GB of virtual memory (on 16,600 torrents). 3. Faster Startup. EXPECTED RESULT See OBSERVED RESULT SOFTWARE/OS VERSIONS FreeBSD 12.1-STABLE, last KDE5 (It does not matter) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387236] Library "sequences" not correctly rendered.
https://bugs.kde.org/show_bug.cgi?id=387236 igor changed: What|Removed |Added CC||igor...@visi1.org --- Comment #1 from igor --- In my case is video FadeIN, FadeOUT Tested in kdenlive version: - Win7 Pro sp1 64bit - Kdenlive-17.04.3-w64 - Kdenlive-17.08.2-2-w64 - Kdenlive-17.12.0-w64 Linux Mint 18.1 mate 64bit "serena" - kdenlive-17.08.1-x86_64.AppImage - kdenlive-17.12-x86_64.AppImage About my video: 1280x720px 25fps MOV --> video fade-In-OUT 1) In only one video track "Video1" I insert two clips of a trim video: clip_01 (6 sec) + clip_02 (7sec). 2) Insert the effects "Fade from Black" (FFB) and "Fade to Black" (FTB) into start and end of the two clips: FFB=2sec, FTB=2sec. This is a view in Timeline: [##][###] 2.1) In "Project Monitor" play is OK. 3) In Timeline select all: the two clips and effects 4) In "Library" tab I click on "Add Timeline Section To Library" icon, and insert the name: "seq1_fade-IN_fade-OUT"(.mlt). 5) In "Library" tab I click on "Add clip To Project" icon. 6) In "Project Bin" I see my sequence "seq1_fade-IN_fade-OUT.mlt" and drag and drop in Timeline. 7) In "Project Monitor" player I see only the "Fade from Black" and "Fade to Black" relative at first clip (clip_01); the second clip (clip_02) haven't fade. This is a play: [##][###] 8) In a text editor I open the "seq1_fade-IN_fade-OUT.mlt" file by the Library folder and I try to read/understand. /* *** */ /* *** SOURCE from Library (part of file) *** */ /* *** */ /* OK */ 1 brightness fade_to_black brightness 2 0 /* OK */ 0 brightness fade_from_black brightness 3 1 /* MISTAKE_01 ??? */ 1 brightness fade_to_black brightness 2 0 /* MISTAKE_02 ??? */ 0 brightness fade_from_black brightness 3 1 /* * */ /* *** MODIFIED with text editor by me and OK (part of file) *** */ /* * */ /* OK */ 1 brightness fade_to_black brightness 2 0 /* OK */ 0 brightness fade_from_black brightness 3 1 /* MODIFIED by me */ 1 brightness fade_to_black brightness 2 0 /* MODIFIED by me */ 0 brightness fade_from_black brightness 3 1 9) After modified the file "seq1_fade-IN_fade-OUT.mlt" I used it in Timeline. Now I can also expand the clip sequence; before with original Library clip I can't. I don't know if these changes are align with the mlt/kdenlive code. I hope it can be help developers to fix the issue. Thanks so much. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387236] Library "sequences" not correctly rendered.
https://bugs.kde.org/show_bug.cgi?id=387236 --- Comment #3 from igor --- (In reply to emohr from comment #2) > It seems you import an MLT library. If yes this function is broken somewhere > around version 16.12. It is re-implemented in the Refactoring version. > > If you like you can test with the current Kdenlive_Nightly_Appimage: > https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/ > lastSuccessfulBuild/artifact/ Hi emohr, thanks for the info. I used the Library features. I just tested it with "kdenlive-19.03.70-f5c88b4-x86_64.appimage" in LinuxMint-18.1-64bit and after some crash it works right. Then that issue can be closed if Davy Bartoloni or others users think so. However, since february 2018 I am using another NLE, Cinelerra-gg for its performance and stability: https://www.cinelerra-gg.org/ Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380112] New: Plasma crashed when i tried to resize panel
https://bugs.kde.org/show_bug.cgi?id=380112 Bug ID: 380112 Summary: Plasma crashed when i tried to resize panel Product: plasmashell Version: 5.9.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: stalker...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.10.15-200.fc25.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: 1. Added new panel "Application Menu Bar" 2. Added a few standard widgets (system tray and lauch menu, idk how it calls in english) to this panel 3. Tried to resize this panel, nd it's gone I saw some similar posts, but they had this crash while removing panel or widgets, and no one while resizing, so i created a new one. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1767167040 (LWP 1707))] Thread 7 (Thread 0x7f166bbb7700 (LWP 26465)): #0 0x7f1773de701d in poll () from /lib64/libc.so.6 #1 0x7f176cb6f166 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f176cb6f27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f1774bed6eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f1774b9e68a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f17749fb5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f168c3f82c7 in KCupsConnection::run() () from /lib64/libkcupslib.so #7 0x7f17749ff9ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f17731396ca in start_thread () from /lib64/libpthread.so.0 #9 0x7f1773df2f7f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f16bc87e700 (LWP 2021)): #0 0x7f177ac41030 in __tls_get_addr () from /lib64/ld-linux-x86-64.so.2 #1 0x7f17749fe906 in QThreadData::current(bool) () from /lib64/libQt5Core.so.5 #2 0x7f1774bed58a in postEventSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #3 0x7f176cb6e69d in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #4 0x7f176cb6f08b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #5 0x7f176cb6f27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #6 0x7f1774bed6eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f1774b9e68a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #8 0x7f17749fb5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #9 0x7f17785fe8b6 in QQuickPixmapReader::run() () from /lib64/libQt5Quick.so.5 #10 0x7f17749ff9ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #11 0x7f17731396ca in start_thread () from /lib64/libpthread.so.0 #12 0x7f1773df2f7f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f174e39d700 (LWP 1978)): #0 0x7f177313f460 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f177a6bf2f4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7f177a6bf339 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7f17731396ca in start_thread () from /lib64/libpthread.so.0 #4 0x7f1773df2f7f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f174700 (LWP 1948)): #0 0x7f1773de701d in poll () from /lib64/libc.so.6 #1 0x7f176cb6f166 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f176cb6f27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f1774bed6eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f1774b9e68a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f17749fb5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f1777c734e5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f17749ff9ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f17731396ca in start_thread () from /lib64/libpthread.so.0 #9 0x7f1773df2f7f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f1755b71700 (LWP 1866)): #0 0x7f1773e00faf in __libc_enable_asynccancel () from /lib64/libc.so.6 #1 0x7f1773de7012 in poll () from /lib64/libc.so.6 #2 0x7f176cb6f166 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f176cb6f27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f1774bed6eb in QEventDispatcherGlib::pro
[kwin] [Bug 380140] New: Kwin crash
https://bugs.kde.org/show_bug.cgi?id=380140 Bug ID: 380140 Summary: Kwin crash Product: kwin Version: 5.8.6 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: igor.nataly.grinb...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.6) (Compiled from sources) Qt Version: 5.6.2 Frameworks Version: 5.29.0 Operating System: Linux 3.17.7-gentoo x86_64 Distribution: "Gentoo Base System release 2.3" -- Information about the crash: - What I was doing when the application crashed: During the login. Now I have the DE but w/o the window manager... The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57be1f27c0 (LWP 6208))] Thread 4 (Thread 0x7f57bd02d700 (LWP 6211)): #0 0x7f57d276520d in poll () from /lib64/libc.so.6 #1 0x7f57d18c38f2 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1 #2 0x7f57d18c56df in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f57bdf00e09 in QXcbEventReader::run() () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f57d04acb3c in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #5 0x7f57d2a27454 in start_thread () from /lib64/libpthread.so.0 #6 0x7f57d276e28d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f57b7359700 (LWP 6213)): #0 0x7f57d2766f13 in select () from /lib64/libc.so.6 #1 0x7f57d0692f2f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib64/libQt5Core.so.5 #2 0x7f57d06945de in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib64/libQt5Core.so.5 #3 0x7f57d0694af2 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f57d0646fda in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f57d04a8724 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f57d2f73475 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #7 0x7f57d04acb3c in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7f57d2a27454 in start_thread () from /lib64/libpthread.so.0 #9 0x7f57d276e28d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f57b54dc700 (LWP 6225)): #0 0x7f57d2a2d3d8 in pthread_cond_timedwait () from /lib64/libpthread.so.0 #1 0x7f57d04ad168 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f57d04a9c02 in QThreadPoolThread::run() () from /usr/lib64/libQt5Core.so.5 #3 0x7f57d04acb3c in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #4 0x7f57d2a27454 in start_thread () from /lib64/libpthread.so.0 #5 0x7f57d276e28d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f57be1f27c0 (LWP 6208)): [KCrash Handler] #6 0x7f57b4b77610 in vtable for Oxygen::Decoration () from /usr/lib64/qt5/plugins/org.kde.kdecoration2/oxygendecoration.so #7 0x7f57d0650b39 in QMetaObject::cast(QObject const*) const () from /usr/lib64/libQt5Core.so.5 #8 0x7f57b493e421 in Oxygen::Button::create(KDecoration2::DecorationButtonType, KDecoration2::Decoration*, QObject*) () from /usr/lib64/qt5/plugins/org.kde.kdecoration2/oxygendecoration.so #9 0x7f57cef6714f in KDecoration2::DecorationButtonGroup::DecorationButtonGroup(KDecoration2::DecorationButtonGroup::Position, KDecoration2::Decoration*, std::function) () from /usr/lib64/libkdecorations2.so.5 #10 0x7f57b49481c0 in Oxygen::Decoration::createButtons() () from /usr/lib64/qt5/plugins/org.kde.kdecoration2/oxygendecoration.so #11 0x7f57b4949c04 in Oxygen::Decoration::init() () from /usr/lib64/qt5/plugins/org.kde.kdecoration2/oxygendecoration.so #12 0x7f57d2389768 in KWin::Decoration::DecorationBridge::createDecoration(KWin::AbstractClient*) () from /usr/lib64/libkwin.so.5 #13 0x7f57d2261f71 in KWin::Client::createDecoration(QRect const&) () from /usr/lib64/libkwin.so.5 #14 0x7f57d2262bdb in KWin::Client::updateDecoration(bool, bool) () from /usr/lib64/libkwin.so.5 #15 0x7f57d22c5c07 in KWin::Client::manage(unsigned int, bool) () from /usr/lib64/libkwin.so.5 #16 0x7f57d2242504 in KWin::Workspace::createClient(unsigned int, bool) () from /usr/lib64/libkwin.so.5 #17 0x7f57d2249284 in KWin::Workspace::init() () from /usr/lib64/libkwin.so.5 #18 0x7f57d2249f17 in KWin::Workspace::Workspace(QString const&) () from /usr/lib64/libkwin.so.5 #19 0x7f57d22a4133 in KWin::Application::createWorkspace() () from /usr/lib64/libkwin.so.5 #20 0x7f57d2c4302e in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /usr/lib64/libkdeinit5_k
[kwin] [Bug 380140] Kwin crash
https://bugs.kde.org/show_bug.cgi?id=380140 Igor changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Platform|Compiled Sources|Gentoo Packages Resolution|--- |WORKSFORME --- Comment #1 from Igor --- I went through the backtrace stack and gathered all the involved packages. Then I've rebuilt them and kwin stopped crashing... The packages I've rebuilt: dev-qt/qtcore dev-qt/qtdbus dev-qt/qtgui dev-qt/qtwidgets kde-frameworks/kwindowsystem kde-plasma/kdecoration kde-plasma/kwin kde-plasma/oxygen sys-libs/glibc I suspect that rebuilding only the kde-plasma/oxygen would be fine, but I was eager to make kwin finally working, so I did them all... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 374115] New: settings options crash
https://bugs.kde.org/show_bug.cgi?id=374115 Bug ID: 374115 Summary: settings options crash Product: systemsettings Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: igormarques...@gmail.com Target Milestone: --- Application: systemsettings5 (5.8.4) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: just exploring setting option when app crash. is like 3 times this happen The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc0daf711c0 (LWP 1179))] Thread 7 (Thread 0x7fc097923700 (LWP 1206)): #0 0x7fc0d75a775b in ?? () from /usr/lib/libQt5Core.so.5 #1 0x7fc0d1067c89 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7fc0d10686ab in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7fc0d106889c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fc0d75a82db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fc0d7551d3a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fc0d7374063 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7fc0d56c7e75 in ?? () from /usr/lib/libQt5Qml.so.5 #8 0x7fc0d7378cf8 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7fc0d2d53454 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7fc0d6c8e7df in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7fc0a8a75700 (LWP 1188)): #0 0x7fc0d6c8548d in poll () from /usr/lib/libc.so.6 #1 0x7fc0d1068786 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fc0d106889c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fc0d75a82db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fc0d7551d3a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fc0d7374063 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fc0d56c7e75 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7fc0d7378cf8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fc0d2d53454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fc0d6c8e7df in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7fc0aa94f700 (LWP 1186)): #0 0x7fc0d6c814ed in read () from /usr/lib/libc.so.6 #1 0x7fc0d10aca10 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fc0d1068235 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7fc0d1068724 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7fc0d106889c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7fc0d75a82db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fc0d7551d3a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7fc0d7374063 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7fc0d56c7e75 in ?? () from /usr/lib/libQt5Qml.so.5 #9 0x7fc0d7378cf8 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7fc0d2d53454 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7fc0d6c8e7df in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fc0b46d7700 (LWP 1184)): #0 0x7fc0d10addd4 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7fc0d106877a in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fc0d106889c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fc0d75a82db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fc0d7551d3a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fc0d7374063 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fc0d56c7e75 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7fc0d7378cf8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fc0d2d53454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fc0d6c8e7df in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fc0bf201700 (LWP 1182)): #0 0x7fc0d10addb0 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 #1 0x7fc0d1068184 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7fc0d1068724 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7fc0d106889c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fc0d75a82db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fc0d7551d3a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fc0d7374063 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7
[kcachegrind] [Bug 379438] New: kcachegrind duplicates calls
https://bugs.kde.org/show_bug.cgi?id=379438 Bug ID: 379438 Summary: kcachegrind duplicates calls Product: kcachegrind Version: 0.7.4kde Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: josef.weidendor...@gmx.de Reporter: igor.bonda...@hotmail.com Target Milestone: --- Created attachment 105310 --> https://bugs.kde.org/attachment.cgi?id=105310&action=edit pictures Hi guys! I'm trying to understand the callgrind format and stuck with some little problem in kcachegrind. I wrote this simple example: events: Ir fn=(105) func1 fn=(1) main cfn=(105) calls=1 1 0 1 fn=(105) cfn=(105) calls=5 0 0 1 In kcachegrind it looks like in pincture 1 - summary number of calls is 6. But when I double clicked on func1 it multiplicates "self calls" by 2 (pic. 2) - now there are 10 calls (but row named "called" holds normal number - 6). What is this and how I can disable this multiplication? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384465] New: With Compact Flash Card Created date in thumbnails is wrong
https://bugs.kde.org/show_bug.cgi?id=384465 Bug ID: 384465 Summary: With Compact Flash Card Created date in thumbnails is wrong Product: digikam Version: 5.6.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import-Rename Assignee: digikam-bugs-n...@kde.org Reporter: igor...@visi1.org Target Milestone: --- Created attachment 107731 --> https://bugs.kde.org/attachment.cgi?id=107731&action=edit compact flash with Created Date wrong Description: In "Import Window", with only Compact Flash Card "Created date" in thumbnails is wrong but the "Metadata date" is correct. Software ver: digiKam v.5.6.-01-win64 OS: Microsoft OS-version: Win7-64bit. Reproducibility: always Steps: 1) A Compact Flash card in a Card Readers plug in and I go on Import menu. 2) "Import Window" shows all the thumbnails with the "Created date: 31/12/1979 23:00" but in the "Metadata properties" the dates is correct. A) I tested this issue with other CF (Compact Flash)card also of the other Camera but the "Created date" always is 31/12/1979 23:00". B) If I connect a SD card the "Creates date" is in sync with metadata. PS: I tested this also in a old version for windows "digiKam-installer-4.12.0-win32" with the same issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384465] With Compact Flash Card Created date in thumbnails is wrong
https://bugs.kde.org/show_bug.cgi?id=384465 --- Comment #2 from igor --- Hi Maik, thanks for your fast reply. I have found the option in... Menu-> Settings-> Configure digiKam-> Cameras-> Behavior Tab-> "Use file metadata (makes connection slower)" disabled. I just changed that option to Enabled and now the "Created Date" is correct. Great! I'm so sorry for open a new (inexistent) bug but I havent't found nothing in the web/forum for this question. Thanks so much Maik. Igor -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 494927] With Qt 6.8 after monitor wake-up, can't unlock lock screen by pressing enter button on password field or clicking arrow button (error TypeError: Property 'respond' of ob
https://bugs.kde.org/show_bug.cgi?id=494927 Igor changed: What|Removed |Added CC||bik...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494927] With Qt 6.8 and multiple monitors, controls to unlock screen are non-functional on some monitors ("TypeError: [thing] is not a function" error) until switching TTYs
https://bugs.kde.org/show_bug.cgi?id=494927 Igor changed: What|Removed |Added CC|bik...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 Igor Tarasov changed: What|Removed |Added CC||tarasov.i...@gmail.com --- Comment #96 from Igor Tarasov --- But maybe it could be also added to 5.8.3, since it is a bugfix and also does not involve any major changes? Thus users would get it in November already. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 Igor Zhuravlov changed: What|Removed |Added CC|zhuravlov...@ya.ru | -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 429859] KDevelop keeps changing active launch
https://bugs.kde.org/show_bug.cgi?id=429859 Igor Kushnir changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/72b925 ||d1761a3fb7e08ee3ceba8b76ce8 ||4d8c086 Status|REPORTED|RESOLVED CC||igor...@gmail.com Version Fixed In||5.8.220400 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 449793] switching project build type changes current launch config
https://bugs.kde.org/show_bug.cgi?id=449793 Igor Kushnir changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||igor...@gmail.com --- Comment #2 from Igor Kushnir --- Yes, this is a duplicate. Already fixed in KDevelop master. *** This bug has been marked as a duplicate of bug 429859 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 429859] KDevelop keeps changing active launch
https://bugs.kde.org/show_bug.cgi?id=429859 Igor Kushnir changed: What|Removed |Added CC||jarmo.tii...@gmail.com --- Comment #3 from Igor Kushnir --- *** Bug 449793 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 450094] Crash while looking up autocomplete suggestions in freshly parsed QML files
https://bugs.kde.org/show_bug.cgi?id=450094 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Is this a regression since frameworks 5.91.0? Could be a KTextEditor regression. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 379474] KScreen wakes up the monitor right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=379474 Igor Tarasov changed: What|Removed |Added CC||tarasov.i...@gmail.com --- Comment #13 from Igor Tarasov --- Confirming with latest KDE Neon (5.24.1). For me this issue appears only when I connect my HDMI monitor via USB-C hub (which is used for all comms + power delivery). When I connect the monitor directly everything works okay, and it does go to powersave mode. Disabling and stopping KScreen 2 in background jobs solves the issue. Also, this is kind of known issue: https://www.reddit.com/r/kde/comments/ewbqst/display_doesnt_sleep_in_power_save_mode/ https://www.reddit.com/r/kde/comments/cnef1v/kde_doesnt_sleep_or_turn_off_monitor_when_inactive/ -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 450316] Unable to Copy File Into the Same Directory using Projects Viewer
https://bugs.kde.org/show_bug.cgi?id=450316 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- This report is very similar to Bug 435235. But if the user is able to dismiss the dialog (if the dialog can be interacted with), then that's already better than the previously reported bug :) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 450316] Unable to Copy File Into the Same Directory using Projects Viewer
https://bugs.kde.org/show_bug.cgi?id=450316 Igor Kushnir changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 435235 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 435235] When pasting file using Projects tool view, "File Already Exists" window cannot be interacted with
https://bugs.kde.org/show_bug.cgi?id=435235 Igor Kushnir changed: What|Removed |Added CC||ekigw...@gmail.com --- Comment #4 from Igor Kushnir --- *** Bug 450316 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 435235] When pasting file using Projects tool view, "File Already Exists" window cannot be interacted with
https://bugs.kde.org/show_bug.cgi?id=435235 Igor Grkavac changed: What|Removed |Added CC||grkavac.i...@gmail.com --- Comment #5 from Igor Grkavac --- Hi all, The issue is happening due to the blocking calls of KJobs exec() functions that are called every time a Cut/Copy/Paste function is called. The explanation for this behavior can be seen here: https://invent.kde.org/frameworks/kcoreaddons/-/blob/master/src/lib/jobs/kjob.h#L268 The complete solution would be to abandon synchronous calls and connect signals and slots that wait for the Paste process to finish. I managed to create a working solution for Cut action just to confirm it is doable, however, there is still a lot of refactoring left as a lot of different parts must be changed (ProjectManagerViewPlugin, CutCopyPasteHelper, AbstractFileManagerPlugin, ...) so, if anyone starts working on this, they will probably have a lot of code to write/change. I will continue on this work and if any maintainer confirms this is a good strategy I will create a PR when I'm done. Kind regards, Igor Grkavac -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 445872] kde default template for kirigami app (c++) throws errors at opening of project
https://bugs.kde.org/show_bug.cgi?id=445872 Igor Grkavac changed: What|Removed |Added CC||grkavac.i...@gmail.com --- Comment #4 from Igor Grkavac --- Hi, Did You manage to build the app after that errors? You didn't specify the KDevelop version You are using. I tested on 5.7.211202 and I don't get these errors. I get an error that "testappconfig.h" is missing but after building, the error disappears. Can You build the Kirigami default app from the terminal, or from KDevelop? Kind regards -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 435235] When pasting file using Projects tool view, "File Already Exists" window cannot be interacted with
https://bugs.kde.org/show_bug.cgi?id=435235 Igor Kushnir changed: What|Removed |Added CC||aar...@doofus.org --- Comment #7 from Igor Kushnir --- *** Bug 454430 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 454430] Copy paste file will not accept input
https://bugs.kde.org/show_bug.cgi?id=454430 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 435235 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 452766] Cannot open projects with -p or --project command line option or any other way on command line
https://bugs.kde.org/show_bug.cgi?id=452766 --- Comment #3 from Igor Kushnir --- > I think i need this in daily life and this bug reduces productivity. Fortunately KDevelop is free software. You can implement the feature to boost productivity. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 454685] updated kdevelop on debian today, crashed while parsing a just imported project
https://bugs.kde.org/show_bug.cgi?id=454685 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #2 from Igor Kushnir --- Judging by the common "getBitWidthValue" line in the backtraces, this and Bug 438249 are both duplicates of Bug 431811. In the oldest of these bugs the following workaround is proposed: > If I change > decl->setBitWidth(clang_getFieldDeclBitWidth(cursor)); > to > decl->setBitWidth(-1); > , KDevelop will finish the parsing without issue. Could you try if that works for you? What LLVM versions did you use to build and run KDevelop? In that same Bug 431811 I proposed this: > If other users experience this crash with LLVM version < 11, then KDevelop > should probably disable the new feature by calling decl->setBitWidth(-1) when > it is compiled against an older LLVM version. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #3 from Igor Kushnir --- Judging by the common "getBitWidthValue" line in the backtraces, this and Bug 454685 are both duplicates of Bug 431811. Strange that this crash affects only some users. And there is no clear LLVM version pattern: * in Bug 431811 it occurred in LLVM 10 and disappeared in LLVM 11; * in this bug on Arthur's system it occurred in system LLVM 11, but not in the AppImage with LLVM 10; * in this bug on Andrei's system it was absent in LLVM 13, but appeared in LLVM 14. * in Bug 454685 it occurs in LLVM 13. Andrei Slavoiu, could you try the workaround that works for other reporters? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #5 from Igor Kushnir --- > Hi, I assume the workaround was applying this patch: Yes, thank you for confirming. Since blaming some specific LLVM versions does not figure, we need to find something else in common that may be the root cause of this crash. The reporter of Bug 431811 indicated that the crash occurred with wxWidgets-3.1.4 but not wxWidgets-3.0.4. Arthur, Andrei, do your projects use wxWidgets? Also, when you write that the crash started occurring after an update/rebuild of KDevelop, were your projects or some libraries they use updated at the same time too? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #7 from Igor Kushnir --- Could someone try to get the backtrace of this crash with assertions enabled? (NDEBUG not defined) When I navigate through the crash call stacks from https://code.woboq.org/llvm/clang/tools/libclang/CXType.cpp.html#374, I see several assert() calls, especially here: https://code.woboq.org/llvm/clang/lib/AST/ExprConstant.cpp.html#_ZNK5clang4Expr21EvaluateKnownConstIntERKNS_10ASTContextEPN4llvm15SmallVectorImplISt4pairINS_14SourceLocationENS_17PartialDiagnostic -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #8 from Igor Kushnir --- (In reply to Igor Kushnir from comment #7) > Could someone try to get the backtrace of this crash with assertions > enabled? (NDEBUG not defined) I mean: assertions enabled/NDEBUG not defined while building Clang. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 454685] updated kdevelop on debian today, crashed while parsing a just imported project
https://bugs.kde.org/show_bug.cgi?id=454685 Igor Kushnir changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #5 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 438249 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #9 from Igor Kushnir --- *** Bug 454685 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 431811] KDevelop crashes when parsing projects that use wxWidgets-3.1.4
https://bugs.kde.org/show_bug.cgi?id=431811 Igor Kushnir changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #5 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 438249 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 Igor Kushnir changed: What|Removed |Added CC||kogiokkaf...@gmail.com --- Comment #10 from Igor Kushnir --- *** Bug 431811 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #13 from Igor Kushnir --- > Delays in responding to your problem solving request. This is not an urgent request. No need to apologize for a delay so verbosely :) > "No ffs implementation found" No idea about this, sorry. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #15 from Igor Kushnir --- > Assertion `!isValueDependent() && "Expression evaluator can't be called on a > dependent expression."' failed. Thanks for checking this so quickly! This must really be an upstream libclang bug because clang_getFieldDeclBitWidth() has no preconditions. From https://clang.llvm.org/doxygen/group__CINDEX__TYPES.html#ga80bbb872dde5b2f26964081338108f91: > CINDEX_LINKAGE int clang_getFieldDeclBitWidth(CXCursor C) > Retrieve the bit width of a bit field declaration as an integer. > If a cursor that is not a bit field declaration is passed in, -1 is returned. In order to report the libclang bug, we need to figure out which data member of which class causes it first. Can someone try inserting the line `qCritical() << "setDeclData" << decl->toString() << decl->comment();` just above the crashing `decl->setBitWidth` line in KDevelop's builder.cpp, reproduce the crash and hopefully determine a minimum reproducible example based on the last "setDeclData" line printed before the crash? Note that `decl->toString()` returns the type and the name of the data member and `decl->comment()` returns the data member's associated documentation. Also note that KDevelop parses data members of a class in order, so the lines immediately preceding the last one before the crash could help identify the class and the data member that causes the crash. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249
--- Comment #19 from Igor Kushnir ---
(In reply to Andrei Slavoiu from comment #17)
> No, not std::string. boost::string. Found the culprit:
>
> //This is the structure controlling a long string
>struct long_t
>{
> size_type is_short : 1;
> size_type length: (sizeof(size_type)*CHAR_BIT - 1);
> And another correction, it's boost::container::string. Looks like boost has
> multiple string implementations.
Apparently Clang 14 considers the bit width of long_t::length value-dependent.
Perhaps clang::FieldDecl::getBitWidthValue() should check if the bit width is
value-dependent before calling Expr::EvaluateKnownConstInt(). Or perhaps
clang_getFieldDeclBitWidth() should check that. If you can reproduce the crash
consistently with Clang 14 (I cannot with my system Clang 13), report the bug.
> Also, I compiled kdevelop with clang-13 again, and no more crash. Weird.
Does KDevelop compiled against Clang 13 call Clang 14 implementation at runtime
or does it keep using the Clang 13 version it was compiled against?
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #21 from Igor Kushnir --- If you want to play with this some more, you could try building Clang 13 with assertions enabled and see if the assertion is triggered. If yes, then the absence of the crash is accidental. If the assertion does not fail, then maybe it's a regression in Clang 14. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #23 from Igor Kushnir --- > Hah, good point. The assert fails on clang-13 as well when built with DEBUG. > Probably on 13 it just happened to return some junk instead of crashing. What bit width does it return? > Perhaps clang::FieldDecl::getBitWidthValue() should check if the bit width is > value-dependent before calling Expr::EvaluateKnownConstInt(). > Or perhaps clang_getFieldDeclBitWidth() should check that. You can attempt to fix the bug yourself with placing a check in one of these two functions. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #25 from Igor Kushnir --- > Compiled clang-13 back without DEBUG and now I get the same crash with it as > well. Perhaps the crash started occurring because of the toolchain (g++/libstdc++/glibc) upgrade or different comper flags, not Clang upgrade. So when Clang 13 was recompiled against the newer toolchain version, the crash appeared. But in any case Clang's assertion fails, so it is probably a Clang bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 455533] Kdevelop crashes upon exit
https://bugs.kde.org/show_bug.cgi?id=455533 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- > #5 0x7f81bb18e2d4 in () at > /usr/lib/qt/plugins/kdevplatform/36/kdevcmakemanager.so Could you please build KDevelop with debug symbols to generate a more useful backtrace? Or try to download the debug symbols via https://wiki.archlinux.org/title/Debugging/Getting_traces#Debuginfod. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 465687] Wrong ui behavior
https://bugs.kde.org/show_bug.cgi?id=465687 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Could be a GNOME-specific bug. Does not occur on my Xfce system and probably doesn't occur on KDE used by most KDevelop developers. You can check in another desktop environment on your system to be sure. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 465640] KDevelop ignores build target paths
https://bugs.kde.org/show_bug.cgi?id=465640 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Does this bug affect only Meson projects? Not CMake? If so, the component should be changed to "Build tools: Meson". -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373536] Order of tools in bottom dock change
https://bugs.kde.org/show_bug.cgi?id=373536 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 466165] Feature request: Regular expression based project filters
https://bugs.kde.org/show_bug.cgi?id=466165 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Wouldn't having both syntaxes be confusing? One more column with the syntax choice would have to be added. I suspect the rare regex use case doesn't justify the effort, code and UI complexity increase. Porting to QRegularExpression is welcome. But it is not straightforward, because QRegularExpression::wildcardToRegularExpression() does not match slashes with '*'. See the discussion here: https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/439#note_623331 So we need to deal with this general issue before porting individual wildcard QRegExp uses. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #28 from Igor Kushnir --- (In reply to Arthur Gruzauskas from comment #27) > Happy to supply any info, or do any suggested bug hunting. Someone has to propose a LLVM fix and get it in. I plan to do so if I manage to reproduce the bug locally. But not sure when I get to it. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 458827] Context menu actions "Compress" and "Extract" don't work.
https://bugs.kde.org/show_bug.cgi?id=458827 --- Comment #3 from Igor Mironchik --- (In reply to Davide Gianforte from comment #2) > This bug was solved in the last Krusader release (2.8.0). Can you manage to > update to latest version and check if issue happens again? I can't do it. I run Kubuntu 22.04 LTS, I updated KDE: ``` Operating System: Kubuntu 22.04 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-67-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: HP Product Name: HP ProBook 640 G3 ``` But there `Krusader` is 2.7.2 still. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 458827] Context menu actions "Compress" and "Extract" don't work.
https://bugs.kde.org/show_bug.cgi?id=458827 --- Comment #4 from Igor Mironchik --- I'be built from sourses. In Krusader 2.8.0 problem is solved. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 466791] Background parser causes crash
https://bugs.kde.org/show_bug.cgi?id=466791 Igor Kushnir changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||igor...@gmail.com --- Comment #2 from Igor Kushnir --- The C++ backtrace is the same as in Bug 438249. Marking as a duplicate. The second backtrace is different and should be logged against kdev-php, which is most likely the culprit. *** This bug has been marked as a duplicate of bug 438249 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 Igor Kushnir changed: What|Removed |Added CC||anonymous11oneeleven@gmail. ||com --- Comment #29 from Igor Kushnir --- *** Bug 466791 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 466826] Kdevelop Snippets ${date} etc are ignored
https://bugs.kde.org/show_bug.cgi?id=466826 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Maybe this date feature simply doesn't exist? I don't see anything date-related in the relevant code: https://invent.kde.org/kdevelop/kdevelop/-/blob/master/plugins/appwizard/appwizardplugin.cpp#L255 You can implement the feature yourself if you need it badly enough. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 466826] Kdevelop Snippets ${date} etc are ignored
https://bugs.kde.org/show_bug.cgi?id=466826 --- Comment #2 from Igor Kushnir --- There *is* , and support, but only in file templates, not app templates: https://invent.kde.org/kdevelop/kdevelop/-/blob/333b00441f10b8c4f8af35405d20338356fb14a9/plugins/filetemplates/licensepage.cpp#L242 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 Igor Kushnir changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #30 from Igor Kushnir --- Managed to reproduce the assertion failure in KDevelop master built against fresh libclang version 17.0.0-git by opening the file /usr/include/boost/container/string.hpp in a session containing a couple of tiny projects and waiting for the background parser to parse this file. Found the upstream bug https://github.com/llvm/llvm-project/issues/56644 and mentioned this KDevelop crash in a comment to it. The backtrace: *** Program received signal SIGABRT (Aborted) *** #0 0x7f42848a08ec in () at /usr/lib/libc.so.6 #1 0x7f4284851ea8 in raise () at /usr/lib/libc.so.6 #2 0x7f428483b53d in abort () at /usr/lib/libc.so.6 #3 0x7f428483b45c in () at /usr/lib/libc.so.6 #4 0x7f428484a9f6 in () at /usr/lib/libc.so.6 #5 0x7f421116303d in clang::Expr::EvaluateKnownConstInt(clang::ASTContext const&, llvm::SmallVectorImpl >*) const (this=, Ctx=, Diag=Diag@entry=0x0) at llvm-project/clang/lib/AST/ExprConstant.cpp:15473 #6 0x7f421104e7a5 in clang::FieldDecl::getBitWidthValue(clang::ASTContext const&) const (this=, Ctx=) at llvm-project/clang/lib/AST/Decl.cpp:4309 #7 0x7f421b0b972b in (anonymous namespace)::Visitor::setDeclData<(CXCursorKind)6>(CXCursor, KDevelop::ClassMemberDeclaration*) const (this=0x7f421a702ff0, cursor=..., decl=0x7f420202d170) at kdevelop/plugins/clang/duchain/builder.cpp:1159 #8 0x7f421b0a6d4a in (anonymous namespace)::Visitor::createDeclarationCommon<(CXCursorKind)6, KDevelop::ClassMemberDeclaration>(CXCursor, KDevelop::Identifier const&) (this=0x7f421a702ff0, cursor=..., id=...) at kdevelop/plugins/clang/duchain/builder.cpp:445 #9 0x7f421b09a789 in (anonymous namespace)::Visitor::createDeclaration<(CXCursorKind)6, KDevelop::ClassMemberDeclaration>(CXCursor, KDevelop::Identifier const&, KDevelop::DUContext*) (this=0x7f421a702ff0, cursor=..., id=..., context=0x0) at kdevelop/plugins/clang/duchain/builder.cpp:456 #10 0x7f421b093591 in (anonymous namespace)::Visitor::buildDeclaration<(CXCursorKind)6, KDevelop::ClassMemberDeclaration, false>(CXCursor) (this=0x7f421a702ff0, cursor=...) at kdevelop/plugins/clang/duchain/builder.cpp:1293 #11 0x7f421b088e99 in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)6>(CXCursor, CXCursor) (this=0x7f421a702ff0, cursor=..., parent=...) at kdevelop/plugins/clang/duchain/builder.cpp:1009 #12 0x7f421b082309 in (anonymous namespace)::visitCursor(CXCursor, CXCursor, CXClientData) (cursor=..., parent=..., data=0x7f421a702ff0) at kdevelop/plugins/clang/duchain/builder.cpp:1675 #13 0x7f4210f2b400 in clang::cxcursor::CursorVisitor::Visit(CXCursor, bool) (this=0x7f421a700ec0, Cursor=..., CheckedRegionOfInterest=) at llvm-project/clang/tools/libclang/CIndex.cpp:220 #14 0x7f4210f31e66 in clang::cxcursor::CursorVisitor::handleDeclForVisitation(clang::Decl const*) (this=0x7f421a700ec0, D=0x7f41e0443490) at llvm-project/clang/tools/libclang/CIndex.cpp:682 #15 0x7f4210f32021 in clang::cxcursor::CursorVisitor::VisitDeclContext(clang::DeclContext*) (this=0x7f421a700ec0, DC=0x7f41e0443148) at llvm-project/clang/tools/libclang/CIndex.cpp:643 #16 0x7f4210f2aca8 in clang::cxcursor::CursorVisitor::VisitChildren(CXCursor) (this=0x7f421a700ec0, Cursor=...) at llvm-project/clang/tools/libclang/CIndex.cpp:509 #17 0x7f4210f2b2c1 in clang_visitChildren(CXCursor, CXCursorVisitor, CXClientData) (parent=..., visitor=0x7f421b081f0f <(anonymous namespace)::visitCursor(CXCursor, CXCursor, CXClientData)>, client_data=0x7f421a702ff0) at llvm-project/clang/tools/libclang/CIndex.cpp:4827 #18 0x7f421b0a42f8 in (anonymous namespace)::Visitor::buildDeclaration<(CXCursorKind)2, KDevelop::ClassDeclaration, true>(CXCursor) (this=0x7f421a702ff0, cursor=...) at kdevelop/plugins/clang/duchain/builder.cpp:1290 #19 0x7f421b0999dd in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)2, (Decision)0, (Decision)0>(CXCursor, CXCursor) (this=0x7f421a702ff0, cursor=..., parent=...) at kdevelop/plugins/clang/duchain/builder.cpp:1009 #20 0x7f421b092ac7 in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)2, (Decision)0, (Decision)2>(CXCursor, CXCursor) (this=0x7f421a702ff0, cursor=..., parent=...) at kdevelop/plugins/clang/duchain/builder.cpp:984 #21 0x7f421b088a79 in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)2>(CXCursor, CXCursor) (this=0x7f421a702ff0, cursor=..., parent=...) at kdevelop/plugins/clang/duchain/builder.cpp:972 #22 0x7f421b082185 in (anonymous namespace)::visitCursor(CXCursor, CXCursor, CXClientData) (cursor=..., parent=..., data=0x7f421a702ff
[krusader] [Bug 466961] New: Extra line endings in the integrated console output window
https://bugs.kde.org/show_bug.cgi?id=466961 Bug ID: 466961 Summary: Extra line endings in the integrated console output window Classification: Applications Product: krusader Version: 2.8.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: igor.mironc...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY Extra line endings in the integrated console output window STEPS TO REPRODUCE 1. Run ctest from CMake in build directory with test. OBSERVED RESULT I see extra line ending in the output, like: ``` Test project /path/to Start 1: test.funcs.qt 1/10 Test #1: test.funcs.qt Passed0.01 sec Start 2: test.funcs.stl 2/10 Test #2: test.funcs.stl ... Passed0.00 sec Start 3: test.md_parser.qt 3/10 Test #3: test.md_parser.qt Passed0.06 sec Start 4: test.md_parser.stl 4/10 Test #4: test.md_parser.stl ... Passed0.07 sec Start 5: test.md_parser.commonmark.qt 5/10 Test #5: test.md_parser.commonmark.qt . Passed0.12 sec Start 6: test.md_parser.commonmark.stl 6/10 Test #6: test.md_parser.commonmark.stl Passed0.15 sec Start 7: test.md_parser.gfm.qt 7/10 Test #7: test.md_parser.gfm.qt Passed0.01 sec Start 8: test.md_parser.gfm.stl 8/10 Test #8: test.md_parser.gfm.stl ... Passed0.01 sec Start 9: test.internal_string.qt 9/10 Test #9: test.internal_string.qt .. Passed0.01 sec Start 10: test.internal_string.stl 10/10 Test #10: test.internal_string.stl . Passed0.00 sec 100% tests passed, 0 tests failed out of 10 Total Test time (real) = 0.44 sec ``` EXPECTED RESULT In the standard console I see text like: ``` Test project /path/to Start 1: test.funcs.qt 1/10 Test #1: test.funcs.qt Passed0.01 sec Start 2: test.funcs.stl 2/10 Test #2: test.funcs.stl ... Passed0.00 sec Start 3: test.md_parser.qt 3/10 Test #3: test.md_parser.qt Passed0.04 sec Start 4: test.md_parser.stl 4/10 Test #4: test.md_parser.stl ... Passed0.05 sec Start 5: test.md_parser.commonmark.qt 5/10 Test #5: test.md_parser.commonmark.qt . Passed0.11 sec Start 6: test.md_parser.commonmark.stl 6/10 Test #6: test.md_parser.commonmark.stl Passed0.15 sec Start 7: test.md_parser.gfm.qt 7/10 Test #7: test.md_parser.gfm.qt Passed0.01 sec Start 8: test.md_parser.gfm.stl 8/10 Test #8: test.md_parser.gfm.stl ... Passed0.01 sec Start 9: test.internal_string.qt 9/10 Test #9: test.internal_string.qt .. Passed0.00 sec Start 10: test.internal_string.stl 10/10 Test #10: test.internal_string.stl . Passed0.00 sec 100% tests passed, 0 tests failed out of 10 Total Test time (real) = 0.39 sec ``` SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.04 LTS (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 466961] Extra line endings in the integrated console output window
https://bugs.kde.org/show_bug.cgi?id=466961 --- Comment #1 from Igor Mironchik --- Created attachment 157055 --> https://bugs.kde.org/attachment.cgi?id=157055&action=edit Screenshot of the console uotput window -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 466961] Extra line endings in the integrated console output window
https://bugs.kde.org/show_bug.cgi?id=466961 Igor Mironchik changed: What|Removed |Added Attachment #157055|Screenshot of the console |Screenshot of the console description|uotput window |output window -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 466975] kdevelop crashes when parsing wxWidgets source files
https://bugs.kde.org/show_bug.cgi?id=466975 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #3 from Igor Kushnir --- (In reply to nmset from comment #2) > This workaround no longer works : > > https://bugs.kde.org/show_bug.cgi?id=438249#c4 In my version of KDevelop (master), plugins/clang/duchain/builder.cpp:1157 points to the line `decl->setBitWidth(clang_getFieldDeclBitWidth(cursor));`. If the line of code is the same in your version, then the workaround *must* work and this is a duplicate of Bug 438249. The fix is being actively reviewed here: https://reviews.llvm.org/D130303. So there is a good chance the bug will be gone in LLVM/Clang version 17. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 466975] kdevelop crashes when parsing wxWidgets source files
https://bugs.kde.org/show_bug.cgi?id=466975 Igor Kushnir changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 438249 *** -- You are receiving this mail because: You are watching all bug changes.
