[systemsettings] [Bug 479569] New: Custom Shortcuts Refuse Cursor Input
https://bugs.kde.org/show_bug.cgi?id=479569 Bug ID: 479569 Summary: Custom Shortcuts Refuse Cursor Input Classification: Applications Product: systemsettings Version: 5.27.9 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: yusufsalihma...@gmail.com Target Milestone: --- Application: systemsettings (5.27.9) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.5.0-kali3-amd64 x86_64 Windowing System: X11 Distribution: Kali GNU/Linux Rolling DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: After selecting 'Autodetect' in 'System Settings->Custom Shortcuts->(any shortcut)->Conditions->New/Edit->New/Edit', cursor remains on window property detection mode on 'System Settings' window and all of its childs, does not function in their content pane. Title and frame are treated with normal cursor. Can navigate through the content with keyboard. No problems on other windows. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f3278cbf620 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3278cc086d in QUuid::toString() const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3240329847 in KHotKeys::ShortcutTrigger::shortcut() const () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #7 0x7f3240329c08 in KHotKeys::ShortcutTrigger::primaryShortcut() const () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #8 0x7f324039c3e9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_hotkeys.so #9 0x7f32403a5c7b in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_hotkeys.so #10 0x7f3278d05fcd in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f3278d07a29 in QSignalMapper::mapped(QString const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f3278d08f4f in QSignalMapper::map(QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f3278d05fcd in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f327a6c8942 in KKeySequenceWidget::keySequenceChanged(QKeySequence const&) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #15 0x7f3278d062b2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f32796fa894 in KGlobalAccel::globalShortcutChanged(QAction*, QKeySequence const&) () from /lib/x86_64-linux-gnu/libKF5GlobalAccel.so.5 #17 0x7f32796ffaf8 in ?? () from /lib/x86_64-linux-gnu/libKF5GlobalAccel.so.5 #18 0x7f3279700e4c in KGlobalAccel::setShortcut(QAction*, QList const&, KGlobalAccel::GlobalShortcutLoading) () from /lib/x86_64-linux-gnu/libKF5GlobalAccel.so.5 #19 0x7f32403391f4 in ?? () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #20 0x7f32403294e9 in KHotKeys::ShortcutTrigger::activate(bool) () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #21 0x7f32403292a0 in non-virtual thunk to KHotKeys::ShortcutTrigger::enable() () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #22 0x7f324032090b in KHotKeys::SimpleActionData::doEnable() () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #23 0x7f3240335840 in ?? () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #24 0x7f3240334e68 in ?? () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #25 0x7f3240335493 in ?? () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #26 0x7f3240335b5b in ?? () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #27 0x7f3240331bd0 in KHotKeys::Settings::read_settings(KHotKeys::ActionDataGroup*, KConfigBase const&, bool, KHotKeys::ActionState) () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #28 0x7f3240332f5b in KHotKeys::Settings::reread_settings(bool) () from /lib/x86_64-linux-gnu/libkhotkeysprivate.so.5 #29 0x7f324038e83e in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_hotkeys.so #30 0x7f3240387895 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_hotkeys.so #31 0x7f32797cd141 in KCModuleProxy::load() () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #32 0x7f327a761bc0 in ModuleView::resolveChanges(KCModuleProxy*) () from /lib/x86_64-linux-gnu/libsystemsettingsview.so.3 #33 0x55a11e29a749 in ?? () #34 0x7f327a6d10b5 in KMainWindow::closeEvent(QCloseEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #35 0x7f32799a5dc8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #36 0x7f327a7124a7 in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #37 0x7f3279962f32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #38 0x7f3278ccc748 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from
[plasmashell] [Bug 459082] Wayland - Notification on primary monitor in wrong place
https://bugs.kde.org/show_bug.cgi?id=459082 Yusuf changed: What|Removed |Added CC||e2ulmecb@randalthor23.anona ||ddy.me --- Comment #1 from Yusuf --- Hello, exact same thing has been happening to me as well. I have 2 monitors (left/right) my primary is left but on my Wayland sessions notification always display on my second monitor just like the attachment in this post. System Info: Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 If this is relevant my monitors: Left (Primary) Monitor: Samsung 1920x1080@75 HDMI Connection Right Monitor: Samsung 1920x1080@60 DVI-D Connection -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466769] New: Highlighted/selected options in text autofill popups in Kate editors use the wrong foreground color from the system color scheme rendering it unreadable
https://bugs.kde.org/show_bug.cgi?id=466769 Bug ID: 466769 Summary: Highlighted/selected options in text autofill popups in Kate editors use the wrong foreground color from the system color scheme rendering it unreadable Classification: Applications Product: kate Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: yusufjamal1...@gmail.com Target Milestone: --- Created attachment 156959 --> https://bugs.kde.org/attachment.cgi?id=156959=edit Screenshot of the autofill popup in kate. Shows the wrong foreground color being used for Selected/Highlighted text. SUMMARY The text color/foreground color of the highlighted entry in auto-fill/intellisense popups should use the 'Selection Text' color from the system (plasma) color scheme but uses 'View Text' color instead STEPS TO REPRODUCE 1. Type something in Kate or KWrite until you get the autofill suggestion popup. 2. Use the arrow keys on the keyboard to select one of the suggestions. OBSERVED RESULT The text color of the suggestion is the same as the 'View Text' color from the system color scheme EXPECTED RESULT The text color of the suggestion is the same as the 'Selection Text' color from the Plasma/system color scheme. SOFTWARE/OS VERSIONS: Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 461149] plasma-pa slider flickers and takes a short delay to settle at one location (after your cursor stops moving)
https://bugs.kde.org/show_bug.cgi?id=461149 --- Comment #4 from Yusuf Jamal --- It indeed does go away (which is why I mentioned I am using PA and not pipewire) but pipewire is very buggy for me -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 461149] plasma-pa slider flickers and takes a short delay to settle at one location (after your cursor stops moving)
https://bugs.kde.org/show_bug.cgi?id=461149 --- Comment #2 from Yusuf Jamal --- I forgot to mention that I am using pulseaudio and not pipewire because of other bugs I face with pipewire. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 461149] plasma-pa slider flickers and takes a short delay to settle at one location (after your cursor stops moving)
https://bugs.kde.org/show_bug.cgi?id=461149 --- Comment #1 from Yusuf Jamal --- *** Bug 461148 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 461148] Flickering while changing volume after connecting a bluetooth audio device
https://bugs.kde.org/show_bug.cgi?id=461148 Yusuf Jamal changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Yusuf Jamal --- *** This bug has been marked as a duplicate of bug 461149 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 461149] New: plasma-pa slider flickers and takes a short delay to settle at one location (after your cursor stops moving)
https://bugs.kde.org/show_bug.cgi?id=461149 Bug ID: 461149 Summary: plasma-pa slider flickers and takes a short delay to settle at one location (after your cursor stops moving) Classification: Plasma Product: plasma-pa Version: 5.26.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: yusufjamal1...@gmail.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- Created attachment 153293 --> https://bugs.kde.org/attachment.cgi?id=153293=edit plasma-pa applet volume slider flickering bug illustration SUMMARY When changing the volume for a bluetooth audio device (such as mine which is OnePlus Nord Buds), the plasma-pa applet's volume slider flickers as shown in the video attached STEPS TO REPRODUCE 1. Connect a bluetooth device 2. Change it's volume through the plasma-pa applet (using your mouse or touchpad) OBSERVED RESULT plasma-pa slider flickers and takes a short delay to settle at one location (after your cursor stops moving) EXPECTED RESULT The slider doesn't flicker SOFTWARE/OS VERSIONS Linux Distribution: Arch Linux KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99 Qt Version: Don't know how to find out -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 461148] New: Flickering while changing volume after connecting a bluetooth audio device
https://bugs.kde.org/show_bug.cgi?id=461148 Bug ID: 461148 Summary: Flickering while changing volume after connecting a bluetooth audio device Classification: Plasma Product: plasma-pa Version: 5.26.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: yusufjamal1...@gmail.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- Created attachment 153292 --> https://bugs.kde.org/attachment.cgi?id=153292=edit Flickering volume slider bug SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When changing the volume for a bluetooth audio device (such as mine which is OnePlus Nord Buds), the plasma-pa applet's volume slider flickers as shown in the video attached STEPS TO REPRODUCE 1. Connect a bluetooth device 2. Change it's volume through the plasma-pa applet (using your mouse or touchpad) OBSERVED RESULT The slider flickers and takes a short delay to settle where your mouse has reached EXPECTED RESULT The slider doesn't flicker SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99 Qt Version: Don't know how to find out ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457721] Most KDE Apps crash when they are dragged by their titlebar after being corner tiled.
https://bugs.kde.org/show_bug.cgi?id=457721 --- Comment #2 from Yusuf Jamal --- (In reply to Nate Graham from comment #1) > I can't reproduce this issue for any of my KDE apps with current git master. > > Can you attach a backtrace of one of these crashes? -- Backtrace: Application: KWrite (kwrite), signal: Segmentation fault [New LWP 35321] [New LWP 35322] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f56f10be99f in __GI___poll (fds=0x7fff734d6ff8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f56ec8e39c0 (LWP 35318))] Thread 3 (Thread 0x7f56e8aeb700 (LWP 35322)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55b3ca8fd808) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b3ca8fd7b8, cond=0x55b3ca8fd7e0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55b3ca8fd7e0, mutex=0x55b3ca8fd7b8) at pthread_cond_wait.c:647 #3 0x7f56e263a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f56e263a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f56ef953609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f56f10cb133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f56ea982700 (LWP 35321)): #0 0x7f56f144d9ea in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f56f168fc85 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f56eefa6da1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f56eefa7312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f56eefa74a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f56f168f5bb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f56f163376b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f56f144d372 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f56efb89f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f56f144e553 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f56ef953609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f56f10cb133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f56ec8e39c0 (LWP 35318)): [KCrash Handler] #4 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:262 #5 0x7f56ec4b1a32 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #6 0x7f56ec4b1dcb in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #7 0x7f56ec4b22d8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #8 0x7f56ec4b28b0 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7f56f1bde967 in QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x7f56f212b51d in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f56f212c325 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f56f212e77c in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f56f212f204 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f56f2158875 in QWidgetPrivate::syncBackingStore() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f56f2179801 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f56f217d412 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f56f211be83 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f56f2124c98 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f56f1634c6a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f56f1a1724f in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #21 0x7f56f1a1bce3 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x7f56f19f266c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #23 0x7f56ec4c03ee in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #24 0x7f56eefa717d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f56eefa7400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f56eefa74a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f56f168f5a2 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f56f163376b in QEventLoop::exec(
[dolphin] [Bug 457722] New: KDE Apps crash whenever they are dragged by the titlebar after being tiled to the corner
https://bugs.kde.org/show_bug.cgi?id=457722 Bug ID: 457722 Summary: KDE Apps crash whenever they are dragged by the titlebar after being tiled to the corner Product: dolphin Version: 22.04.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: yusufjamal1...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.04.3) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.15.0-46-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.25 DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: This crash happens with most KDE apps. KWrite, Dolphin and System Settings are consistent. It seems that once an app has crashed it won't crash again until I restart my PC. So if Dolphin has crashed for you after following the procedure, it won't crash again until you restart or log back in. Steps to reproduce: 1. Open Dolphin or Kwrite or System Settings 2. Drag it by the titlebar and tile it to one of the four screen corners 3. Try to drag the title bar again Observed behavior: Application crashes Expected Behavior: Shouldn't crash More logs: When trying this steps above with Dolphin, I see the below new entries in ~/.xsession-errors KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = dolphin path = /usr/bin pid = 6184 KCrash: Arguments: /usr/bin/dolphin KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 6187] [New LWP 6188] [New LWP 6193] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fc68af5599f in __GI___poll (fds=0x7ffe2ccee378, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7fc68640e9c0 (LWP 6184))] Thread 4 (Thread 0x7fc670845700 (LWP 6193)): #0 0x7fc688fbe374 in read@plt () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc68903bb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc688ff2ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc688ff3312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc688ff34a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc68b5265bb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc68b4ca76b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc68b2e4372 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc68b2e5553 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc689a66609 in start_thread (arg=) at pthread_create.c:477 #10 0x7fc68af62133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fc67cd44700 (LWP 6188)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564ec7547018) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564ec7546fc8, cond=0x564ec7546ff0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564ec7546ff0, mutex=0x564ec7546fc8) at pthread_cond_wait.c:647 #3 0x7fc67d1795eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fc67d1791eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fc689a66609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fc68af62133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fc684d39700 (LWP 6187)): #0 0x7fc68af5599f in __GI___poll (fds=0x7fc678015300, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc688ff336e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc688ff34a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc68b5265bb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc68b4ca76b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc68b2e4372 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc68c58af4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fc68b2e5553 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc689a66609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fc68af62133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fc68640e9c0 (LWP 6184)): [KCrash Handler] #4 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:262 #5
[plasmashell] [Bug 457721] New: Most KDE Apps crash when they are dragged by their titlebar after being corner tiled.
https://bugs.kde.org/show_bug.cgi?id=457721 Bug ID: 457721 Summary: Most KDE Apps crash when they are dragged by their titlebar after being corner tiled. Product: plasmashell Version: 5.25.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: yusufjamal1...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I don't know which app to insert logs for, it happens with most KDE apps like Dolphin, KWrite, System Settings. STEPS TO REPRODUCE 1. Open a KDE app (like Dolphin) 2. Drag the title bar of the opened app window and tile it to the corner of the screen (to make it a quarter of the size of the screen) and release the mouse 3. Try to drag it again OBSERVED RESULT The KDE app crashes EXPECTED RESULT App should normally u SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.25 (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.0-46-generic (64-bit) ADDITIONAL INFORMATION I got these logs for KWrite from ~/.xsession-errors whenever the crash happens: KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kwrite path = /usr/bin pid = 1761 KCrash: Arguments: /usr/bin/kwrite /home/sbeve72/.config/kwinrc KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi And similar logs from the same file for Dolphin: KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = dolphin path = /usr/bin pid = 6184 KCrash: Arguments: /usr/bin/dolphin KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi It seems that this crash happens only once after a restart for each app. So if Dolphin has crashed for you once, it won't crash again until you restart. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457706] New: Kwrite crashes when changing size
https://bugs.kde.org/show_bug.cgi?id=457706 Bug ID: 457706 Summary: Kwrite crashes when changing size Product: kate Version: 22.04.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: yusufjamal1...@gmail.com Target Milestone: --- Application: kwrite (22.04.3) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.15.0-43-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.25 DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: If Kwrite is tiled to be half of the screen and then I tile it to be a quarter of the screen, it crashes. This is consistent behavior on my PC. It happens every time. It's really annoying since changing position and size of the windows is a regular job in my workflow and kwrite is an essential app as well. The crash can be reproduced every time. -- Backtrace: Application: KWrite (kwrite), signal: Segmentation fault [New LWP 35321] [New LWP 35322] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f56f10be99f in __GI___poll (fds=0x7fff734d6ff8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f56ec8e39c0 (LWP 35318))] Thread 3 (Thread 0x7f56e8aeb700 (LWP 35322)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55b3ca8fd808) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b3ca8fd7b8, cond=0x55b3ca8fd7e0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55b3ca8fd7e0, mutex=0x55b3ca8fd7b8) at pthread_cond_wait.c:647 #3 0x7f56e263a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f56e263a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f56ef953609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f56f10cb133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f56ea982700 (LWP 35321)): #0 0x7f56f144d9ea in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f56f168fc85 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f56eefa6da1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f56eefa7312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f56eefa74a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f56f168f5bb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f56f163376b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f56f144d372 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f56efb89f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f56f144e553 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f56ef953609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f56f10cb133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f56ec8e39c0 (LWP 35318)): [KCrash Handler] #4 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:262 #5 0x7f56ec4b1a32 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #6 0x7f56ec4b1dcb in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #7 0x7f56ec4b22d8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #8 0x7f56ec4b28b0 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7f56f1bde967 in QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x7f56f212b51d in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f56f212c325 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f56f212e77c in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f56f212f204 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f56f2158875 in QWidgetPrivate::syncBackingStore() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f56f2179801 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f56f217d412 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f56f211be83 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f56f2124c98 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f56f1634c6a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f56f1a1724f in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #21
[dolphin] [Bug 454290] Dolphin sometimes crashes when I close the window or one of the tabs
https://bugs.kde.org/show_bug.cgi?id=454290
--- Comment #2 from Yusuf Jamal ---
(In reply to Ömer Fadıl USTA from comment #1)
> I start to believe the reason of this bug is version control plugin. The
> tab or window is closing before its job done
> and it is causing crash.
>
> Yusuf could you confirm that is this bug observable only exist on
> git/svn/cvs/... existed directories or not ?
>
> ```
> QMutexLocker pluginLocker(m_globalPluginMutex);
> QMap >::iterator it
> = m_itemStates.begin();
> for (; it != m_itemStates.end(); ++it) {
> if (m_plugin->beginRetrieval(it.key())) {
> QVector& items = it.value();
> const int count = items.count();
> for (int i = 0; i < count; ++i) {
> const KFileItem& item = items.at(i).first;
> const KVersionControlPlugin::ItemVersion version =
> m_plugin->itemVersion(item);
> items[i].second = version;
> }
> }
>
> m_plugin->endRetrieval();
> }
> ```
Well I had the version control plugin disabled when I reported this error and
it still happened. Since then it hasn't really happened.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 454290] New: Dolphin sometimes crashes when I close the window or one of the tabs
https://bugs.kde.org/show_bug.cgi?id=454290 Bug ID: 454290 Summary: Dolphin sometimes crashes when I close the window or one of the tabs Product: dolphin Version: 22.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: yusufjamal1...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.04.1) Qt Version: 5.15.4 Frameworks Version: 5.94.0 Operating System: Linux 5.13.0-44-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: It is highly unreliable but happens more often than not. dolphin crashes when I close its window. Crashing upon closing the tab is less common so I am not too sure whether the two problems are related but closing the window almost 60% of the time causes a crash. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 8659] [New LWP 8660] [New LWP 8661] [New LWP 8666] [New LWP 8704] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x7ffe9df277f8) at ../sysdeps/nptl/futex-internal.h:183 __preamble__ [Current thread is 1 (Thread 0x7f174e6de9c0 (LWP 8657))] Thread 6 (Thread 0x7f1723f7e700 (LWP 8704)): [KCrash Handler] #4 0x0060 in ?? () #5 0x7f1755a1e84f in UpdateItemStatesThread::run (this=0x564dc3abf950) at ./src/views/versioncontrol/updateitemstatesthread.cpp:41 #6 0x7f17535b4643 in QThreadPrivate::start (arg=0x564dc3abf950) at thread/qthread_unix.cpp:331 #7 0x7f1751d39609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f1753231133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f1738845700 (LWP 8666)): #0 0x7f17512c3370 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f17512c34a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f17537f5c8b in QEventDispatcherGlib::processEvents (this=0x7f171c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7f1753799eab in QEventLoop::exec (this=this@entry=0x7f1738844be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #4 0x7f17535b3462 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #5 0x7f17535b4643 in QThreadPrivate::start (arg=0x564dc3674d10) at thread/qthread_unix.cpp:331 #6 0x7f1751d39609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f1753231133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f1744cd4700 (LWP 8661)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564dc31a1cb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564dc31a1c68, cond=0x564dc31a1c90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564dc31a1c90, mutex=0x564dc31a1c68) at pthread_cond_wait.c:647 #3 0x7f17451075eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f17451071eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f1751d39609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f1753231133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f174ccda700 (LWP 8660)): #0 __GI___libc_read (nbytes=16, buf=0x7f174ccd99a0, fd=7) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=7, buf=0x7f174ccd99a0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f175130bb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f17512c2ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f17512c3312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f17512c34a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f17537f5c8b in QEventDispatcherGlib::processEvents (this=0x7f174b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f1753799eab in QEventLoop::exec (this=this@entry=0x7f174ccd9bb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7f17535b3462 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7f1754859f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7f17535b4643 in QThreadPrivate::start (arg=0x7f17548ddd80) at thread/qthread_unix.cpp:331 #11 0x7f1751d39609 in start_thread (arg=) at pthread_create.c:477 #12 0x7f1753231133 in clone () at
[systemsettings] [Bug 446571] New: Latest update to KDE Neon crashes system settings
https://bugs.kde.org/show_bug.cgi?id=446571
Bug ID: 446571
Summary: Latest update to KDE Neon crashes system settings
Product: systemsettings
Version: 5.23.4
Platform: Neon Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: yusufjamal1...@gmail.com
Target Milestone: ---
Application: systemsettings5 (5.23.4)
Qt Version: 5.15.3
Frameworks Version: 5.88.0
Operating System: Linux 5.11.0-41-generic x86_64
Windowing System: X11
Distribution: KDE neon User - Plasma 25th Anniversary Edition
DrKonqi: 5.23.4 [KCrashBackend]
-- Information about the crash:
No real info to tell apart from that as soon as I logged in after the update,
system settings started crashing upon opening
The crash can be reproduced every time.
-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
[New LWP 1650]
[New LWP 1651]
[New LWP 1652]
[New LWP 1653]
[New LWP 1654]
[New LWP 1655]
[New LWP 1660]
[New LWP 1661]
[New LWP 1665]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fb34d515aff in __GI___poll (fds=0x7ffcb0df6eb8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
drkonqi_qmltrace_thread:1
Failed to do pygdbmi parsing: No module named 'pygdbmi'
frame={level="0",func="expression for
topMargin",file="/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/FormLayout.qml",fullname="/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/FormLa".
-
(beware that frames may have been optimized out)
[Current thread is 1 (Thread 0x7fb348d4c9c0 (LWP 1648))]
Thread 10 (Thread 0x7fb30ef3d700 (LWP 1665)):
#0 __GI___libc_read (nbytes=16, buf=0x7fb30ef3c9b0, fd=25) at
../sysdeps/unix/sysv/linux/read.c:26
#1 __GI___libc_read (fd=25, buf=0x7fb30ef3c9b0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2 0x7fb34b64eb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fb34b605ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fb34b606312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7fb34b6064a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x7fb34dae361b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x7fb34da878ab in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x7fb34d8a12c2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x7fb34c930549 in QQmlThreadPrivate::run (this=0x55b4f751c260) at
qml/ftw/qqmlthread.cpp:155
#10 0x7fb34d8a245c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fb34bfc4609 in start_thread (arg=) at
pthread_create.c:477
#12 0x7fb34d522293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 9 (Thread 0x7fb30700 (LWP 1661)):
#0 0x7fb34d515aff in __GI___poll (fds=0x7fb304004a30, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7fb34b60636e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fb34b6064a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fb34dae361b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x7fb34da878ab in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x7fb34d8a12c2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x7fb34c930549 in QQmlThreadPrivate::run (this=0x55b4f73d8be0) at
qml/ftw/qqmlthread.cpp:155
#7 0x7fb34d8a245c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x7fb34bfc4609 in start_thread (arg=) at
pthread_create.c:477
#9 0x7fb34d522293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 8 (Thread 0x7fb331847700 (LWP 1660)):
#0 __GI___libc_read (nbytes=16, buf=0x7fb3318469b0, fd=20) at
../sysdeps/unix/sysv/linux/read.c:26
#1 __GI___libc_read (fd=20, buf=0x7fb3318469b0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2 0x7fb34b64eb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fb34b605ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fb34b606312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7fb34b6064a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x7fb34dae361b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x7fb34da878ab in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x7fb34d8a12c2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x7fb34c930549 in QQmlThreadPrivate::run
[kcalc] [Bug 431158] Wrong mulliplication symbol
https://bugs.kde.org/show_bug.cgi?id=431158 --- Comment #2 from Yusuf --- In Kwrite everything looks fine. In Kcalc i switch the font to another and back and everything was fine. Even after reboot. See the PDF Am Montag, Januar 04, 2021 21:53 CET, "Christoph Feck" schrieb: https://bugs.kde.org/show_bug.cgi?id=431158 --- Comment #1 from Christoph Feck --- How does the × character look in KWrite or KCharSelect when using the same font? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 431158] New: Wrong mulliplication symbol
https://bugs.kde.org/show_bug.cgi?id=431158 Bug ID: 431158 Summary: Wrong mulliplication symbol Product: kcalc Version: unspecified Platform: Netrunner OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: yu...@radoener.de Target Milestone: --- Created attachment 134550 --> https://bugs.kde.org/attachment.cgi?id=134550=edit Screenshot of wrong symbols SUMMARY Muliplication and division Button are the "same" Not really but the same. Just have a look at attachment STEPS TO REPRODUCE 1. just start and have a look to the "*"-Button (Multiplikation) 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424145] New: negligence of programmers
https://bugs.kde.org/show_bug.cgi?id=424145 Bug ID: 424145 Summary: negligence of programmers Product: krita Version: nightly build (please specify the git hash!) Platform: unspecified OS: Other Status: REPORTED Severity: critical Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: yaman.j...@gmail.com Target Milestone: --- Created attachment 130077 --> https://bugs.kde.org/attachment.cgi?id=130077=edit screenshot of user manual Krita 4.xxx SUMMARY STEPS TO REPRODUCE 1. open krita 2. put multiple guides 3. try to delete multiple guides on one step surprise, WTF .. !! i need delete one by one, is a bulshit, incredible that it does not have a way to delete multiple guides in one step, what the hell happens to them, even gimp has a multiple guide deletion OBSERVED RESULT bad work flow EXPECTED RESULT good work flow SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 4.3.1 alpha Qt Version: QT5 full ADDITIONAL INFORMATION fix that, because it is sad to see the stupidities that one finds in krita and not being able to defend them from PS is sad -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416217] New: open option not working
https://bugs.kde.org/show_bug.cgi?id=416217 Bug ID: 416217 Summary: open option not working Product: kdenlive Version: 19.12.1 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: webyusufk...@gmail.com Target Milestone: --- Open option not working, Open option not working, no window is opening. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395302] New: Discover Software Center crashes on search
https://bugs.kde.org/show_bug.cgi?id=395302 Bug ID: 395302 Summary: Discover Software Center crashes on search Product: Discover Version: 5.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: fayaz.yusuf.k...@gmail.com Target Milestone: --- Application: plasma-discover (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.14.13-041413-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: - What I was doing when the application crashed: Searching for "disk" usage tools. - Custom settings of the application: Root partition had about only 800MB of remaining space. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6a2842e5c0 (LWP 9805))] Thread 10 (Thread 0x7f69d79aa700 (LWP 9817)): #0 0x7f6a23b5e951 in __GI___poll (fds=0x7f69d002ac60, nfds=1, timeout=72877) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6a1e514169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a1e51427c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a2449e49b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a24443e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a242633ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a2426829d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6a203d37fc in start_thread (arg=0x7f69d79aa700) at pthread_create.c:465 #8 0x7f6a23b6ab5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f69ed5ec700 (LWP 9815)): #0 0x7f6a23b5e951 in __GI___poll (fds=0x7f69d8040c20, nfds=1, timeout=72877) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6a1e514169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a1e51427c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a2449e49b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a24443e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a242633ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a2426829d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6a203d37fc in start_thread (arg=0x7f69ed5ec700) at pthread_create.c:465 #8 0x7f6a23b6ab5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f69eeb34700 (LWP 9814)): #0 0x7f6a23b5e951 in __GI___poll (fds=0x7f69e40018c0, nfds=1, timeout=9877) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6a1e514169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a1e51427c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a2449e49b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a24443e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a242633ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a2426829d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6a203d37fc in start_thread (arg=0x7f69eeb34700) at pthread_create.c:465 #8 0x7f6a23b6ab5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f69efbef700 (LWP 9812)): #0 0x7f6a23b5e951 in __GI___poll (fds=0x565486d3be60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6a1e514169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a1e514502 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f69f1a53b26 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f6a1e53b645 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6a203d37fc in start_thread (arg=0x7f69efbef700) at pthread_create.c:465 #6 0x7f6a23b6ab5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f69f03f0700 (LWP 9811)): #0 0x7f6a23b5e951 in __GI___poll (fds=0x565486d130b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6a1e514169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a1e51427c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a1e5142c1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a1e53b645 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6a203d37fc in start_thread (arg=0x7f69f03f0700) at pthread_create.c:465 #6
[kdenlive] [Bug 358223] Rotoscoping effect crashes kdenlive when played
https://bugs.kde.org/show_bug.cgi?id=358223 --- Comment #14 from Yusuf Ismail <linkinpark_n...@yahoo.com> --- Using the third PPA, ppa:kdenlive/kdenlive-master Kdenlive now reports version 16.11.70. Tested adding the rotoscope effect on a 1080p 60fps clip, no crash. Rendered and the output works, the bug is indeed resolved. Thanks for the fix Jean-Baptiste Mardelle! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358223] Rotoscoping effect crashes kdenlive when played
https://bugs.kde.org/show_bug.cgi?id=358223 --- Comment #11 from Yusuf Ismail <linkinpark_n...@yahoo.com> --- On Ubuntu 16.04, tested using the version in both the stable PPA and the testing PPA and both still crash immediately upon adding the rotoscoping effect. stable: ppa:kdenlive/kdenlive-stable testing: ppa:kdenlive/kdenlive-testing Kdenlive is reporting version 16.08.1. System is fully up to date. Is this commit in either of these PPAs? If it is, then the problem is not resolved yet. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368674] partition manager crashes while checking highly corrupted partition (memory leak)
https://bugs.kde.org/show_bug.cgi?id=368674 Fayaz Yusuf Khan <fayaz.yusuf.k...@gmail.com> changed: What|Removed |Added CC||fayaz.yusuf.k...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368674] New: partition manager crashes while checking highly corrupted partition (memory leak)
https://bugs.kde.org/show_bug.cgi?id=368674 Bug ID: 368674 Summary: partition manager crashes while checking highly corrupted partition (memory leak) Product: partitionmanager Version: 1.2.1 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: fayaz.yusuf.k...@gmail.com Some context: My (ext4) partition is 207GiB in size. It had underwent some resize and move operations previously. After that the partition remained corrupted. I tried using alternate superblocks without any success. As a final effort I tried the "mkfs.ext4 -S". The subsequent 'fsck' is a seemingly never ending stream of "inode x invalid, clear? (y)" prompts. So I tried the "Check" option in the partition manager. But it runs for an hour until it slowly consumes all RAM (3.9GiB) and swap (3.8GiB) and then simply exits. No crash dialog is produced however. Reproducible: Always Steps to Reproduce: 1. Setup a large partition with several corrupted inodes. 2. Check the partition using partition manager. Actual Results: Process consumes all memory and exits afterwards. Expected Results: Handle the memory spike gracefully. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358223] Rotoscoping effect crashes kdenlive when played
https://bugs.kde.org/show_bug.cgi?id=358223 Yusuf Ismail <linkinpark_n...@yahoo.com> changed: What|Removed |Added CC||linkinpark_n...@yahoo.com --- Comment #2 from Yusuf Ismail <linkinpark_n...@yahoo.com> --- I want to add that I'm experiencing this crash as well. Rotoscoping is still completely unusable. I am running off the SVN PPA by Olivier Banus (last built 2 days ago from this post). I am on Ubuntu 15.10 64bit, working on a HD1080p 24fps project. Reproducible: Always Steps to Reproduce: 1. Add Clip to timeline 2. Add rotoscoping effect to it 3. Attempt to add points (bezier curve on first frame), or scroll on timeline or really anything. Once rotoscoping is added to a clip, it's only a short matter of time before it brings Kdenlive to it's knees. Actual Results: Segmentation fault Using version 15.13.0 I also went back to version 15.08.1 that is provided in Ubuntu by default, and this problem persists then as well. Tested also on 15.12.0 that is provided in Olivier's kdenlive-release PPA, same results. -- You are receiving this mail because: You are watching all bug changes.
