[systemsettings] [Bug 345743] The multimedia key 'toggle touchpad' does nothing, and setting it as a shortcut for kcm_touchpad behaves weird
https://bugs.kde.org/show_bug.cgi?id=345743 Savor d'Isavano changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454031] New: Specific Color Selector does not show color in the RGB sliders
https://bugs.kde.org/show_bug.cgi?id=454031 Bug ID: 454031 Summary: Specific Color Selector does not show color in the RGB sliders Product: krita Version: 5.0.6 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: anohigisa...@gmail.com Target Milestone: --- Created attachment 148984 --> https://bugs.kde.org/attachment.cgi?id=148984=edit Observed result STEPS TO REPRODUCE 1. Open Krita and create a new file 2. Open "Specific Color Selector" from Settings -> Dockers -> Specific Color Selector OBSERVED RESULT The RGB sliders are blank. EXPECTED RESULT The RGB sliders should show the grandient colors (https://docs.krita.org/en/reference_manual/dockers/specific_color_selector.html) 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.
[systemsettings] [Bug 345743] The multimedia key 'toggle touchpad' does nothing, and setting it as a shortcut for kcm_touchpad behaves weird
https://bugs.kde.org/show_bug.cgi?id=345743 --- Comment #7 from Savor d'Isavano --- Hi. Unfortunately my Inspiron 14R Turbo has retired. My current laptop is a Lenovo Gaming 80N8. I think the touchpad control on this model is somewhat hardware based i.e. different keycodes are generated on each press, one Touchpad On, the next Touchpad Off, etc... This works out of the box, and I see no issue setting them as shortcuts either. Unless someone else can still reproduce this issue, I have no more information to add. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423202] New: In Plasma wayland, touchpad scroll direction is incorrect in some situations.
https://bugs.kde.org/show_bug.cgi?id=423202 Bug ID: 423202 Summary: In Plasma wayland, touchpad scroll direction is incorrect in some situations. Product: plasmashell Version: 5.19.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: anohigisa...@gmail.com Target Milestone: 1.0 SUMMARY In wayland mode, scrolling is opposite in some apps than in other apps. For example, with "Invert scroll direction (Natural scrolling)" disabled, Kate, Chromium, Dolphin (I only tested with those) work correctly, while System Settings left pane, latte dock panel settings work in the opposite direction. The issue occurs for both double-finger scrolling and edge scrolling. STEPS TO REPRODUCE 1. Open the some apps mentioned above. 2. Scroll the touchpad and note the behavior. 3. Go to System Settings -> Input Devices, tick/untick "Invert scroll direction (Natural scrolling)" checkbox. 4. Play with the touchpad again. OBSERVED RESULT EXPECTED RESULT All applications honor the setting correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.7.2-zen1-1-zen/5.19.1 (available in About System) KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor
https://bugs.kde.org/show_bug.cgi?id=380456 Savor d'Isavano changed: What|Removed |Added CC||anohigisa...@gmail.com --- Comment #13 from Savor d'Isavano --- As of baloo 5.63.0, the issue persists. Memory consumption increases by ~2MB/s. CPU consumption is also considerable. Luckily I noticed the CPU fan spinning noisily and disabled baloo before it was too late to save my work (>9GB memory at the time). See this screencast: https://vimeo.com/366988108 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 397264] Cantor crashes with Python 2 backend when importing matplotlib.pyplot
https://bugs.kde.org/show_bug.cgi?id=397264 --- Comment #13 from Savor d'Isavano --- (In reply to Nikita Sirgienko from comment #12) > Git commit 2329f29edc8d83b4823995a184ed454b580f0809 by Nikita Sirgienko. > Committed on 04/07/2019 at 21:45. > Pushed by sirgienko into branch 'master'. > > [Python] Don't use Qt in pythonserver executable for avoding problems with > PyQt5 > Related: bug 407362 > FIXED-IN: 19.08 > > M +33 -33 src/backends/python/pythonserver.cpp > M +11 -13 src/backends/python/pythonserver.h > M +93 -95 src/backends/python/pythonservermain.cpp > M +14 -2src/backends/python/pythonsession.cpp > M +1-1src/backends/python2/CMakeLists.txt > M +1-1src/backends/python3/CMakeLists.txt > > https://commits.kde.org/cantor/2329f29edc8d83b4823995a184ed454b580f0809 (In reply to Nikita Sirgienko from comment #11) > The problem have found: it is conflict between already loaded qt libraries > (often from system installation) and qt libraries loading by PyQt5, when > matplotlib import PyQt5 on pythons2server. When qt version of system and > pyqt5 don't match, crash have been happening. > I will fix it in a day, or two. Thank you. I love you. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 397264] Cantor crashes with Python 2 backend when importing matplotlib.pyplot
https://bugs.kde.org/show_bug.cgi?id=397264 --- Comment #8 from Savor d'Isavano --- (In reply to Alexander Semke from comment #7) > Can you please re-test it again with the recent version of Cantor? We don't > crash the main process also for python2 anymore in case the python > interpreter crashes (Cantor > 18.12 required). Maybe also the problem with > PySide on Arch was solved in-between. Hi. Python 2 sessions do not crash anymore. Python 3 will still complain about 'The name org.kde.Cantor.Python3-17062 was not provided by any .service files'. calling plt.show() has no effect in either way. I'm running Cantor 19.04.0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345473] Double click on titlebar to maximize suddenly stops working
https://bugs.kde.org/show_bug.cgi?id=345473 --- Comment #58 from Savor d'Isavano --- (In reply to David Edmundson from comment #57) > link doens't work Sorry, never used vimeo before. Please try this: https://vimeo.com/327057535?activityReferer=1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345473] Double click on titlebar to maximize suddenly stops working
https://bugs.kde.org/show_bug.cgi?id=345473 --- Comment #56 from Savor d'Isavano --- Look, I think I have got a reliable way to reproduce the bug. People please take a look and have a try at your end, thank you. Go to System Settings -> Applications -> Default Applications -> Web Browser, change how urls are opened any way you like. Try double-clicking. It should stop working. Take a look at this screencast: https://vimeo.com/user93204887/review/327057535/ba77f5a39c -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403023] Items overlap when there are too many widgets on the dock
https://bugs.kde.org/show_bug.cgi?id=403023 --- Comment #5 from Savor d'Isavano --- (In reply to Michail Vourlakos from comment #4) > (In reply to Savor d'Isavano from comment #3) > > (In reply to Savor d'Isavano from comment #2) > > > (In reply to Michail Vourlakos from comment #1) > > > > Have you enabled decrease applets when needed in Tweaks page? > > > > > > Oh yes that would work somehow. But the icons tend to get too small and > > > some > > > widgets will behave differently. > > > > so what is the proposal to improve this? I would suggest how it works in the GNOME extension Dash-to-Dock: the overflowing icons will be hidden, but by placing the pointer at the left/right edges the content will scroll. (I'm okay with mouse wheel too). -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403023] Items overlap when there are too many widgets on the dock
https://bugs.kde.org/show_bug.cgi?id=403023 --- Comment #3 from Savor d'Isavano --- (In reply to Savor d'Isavano from comment #2) > (In reply to Michail Vourlakos from comment #1) > > Have you enabled decrease applets when needed in Tweaks page? > > Oh yes that would work somehow. But the icons tend to get too small and some > widgets will behave differently. IMHO it should well-behave no matter what option combinations a user applies. It might not be the case for hidden, hacky tweaks like manually modifying configuration files though. Just my personal, very biased opinion. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403023] Items overlap when there are too many widgets on the dock
https://bugs.kde.org/show_bug.cgi?id=403023 --- Comment #2 from Savor d'Isavano --- (In reply to Michail Vourlakos from comment #1) > Have you enabled decrease applets when needed in Tweaks page? Oh yes that would work somehow. But the icons tend to get too small and some widgets will behave differently. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403023] New: Items overlap when there are too many widgets on the dock
https://bugs.kde.org/show_bug.cgi?id=403023 Bug ID: 403023 Summary: Items overlap when there are too many widgets on the dock Product: latte-dock Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: anohigisa...@gmail.com Target Milestone: --- Created attachment 117350 --> https://bugs.kde.org/attachment.cgi?id=117350=edit Reproduction of the bug SUMMARY STEPS TO REPRODUCE 1. Add a dock and change its type to "Panel" 2. Add a latte plasmoid on the left of the splitter, and some other widgets on the right of the splitter. 3. Open a lot of applications OBSERVED RESULT The icons overlap EXPECTED RESULT Maybe the widget on the left could push the rightmost widgets off the screen (but then we need a scrolling mechanism) Or whatever approach that makes sense SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.53.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391613] Plasma sometimes crashes when typing in the search box of the application launcher
https://bugs.kde.org/show_bug.cgi?id=391613 --- Comment #21 from Savor d'Isavano --- So what's up with this bug report? It's been alive for 9 months and the status is not even CONFIRMED? No one replies? What are you guys busy with? If no one cares why would we bother reporting? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401612] New: Plasma crashes when searching in application launcher
https://bugs.kde.org/show_bug.cgi?id=401612 Bug ID: 401612 Summary: Plasma crashes when searching in application launcher Product: plasmashell Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: anohigisa...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.4) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.19.4-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: When I clicked the application launcher and searched for Bilibili live helper, Plasma crashed instantly after the candidates showed up. The next time it is back to normal. This issue is not related to any specific search word. I have been having this crash issue with application launcher like forever. Couldn't find anything in common each time this issue arises. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f19a23a80c0 (LWP 1098))] Thread 22 (Thread 0x7f192affd700 (LWP 3032)): #0 0x7f19a6bc3afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f19a7ca571c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1987c8d469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f1987c91339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f1987c91392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f1987c91392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f1987c91392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f1987c91392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f1987c8f389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f19a7ca4f65 in () at /usr/lib/libQt5Core.so.5 #15 0x7f19a6bbda9d in start_thread () at /usr/lib/libpthread.so.0 #16 0x7f19a7989b23 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f192b7fe700 (LWP 3031)): #0 0x7f19a6bc3afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f19a7ca571c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1987c8d469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f1987c91339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f1987c91392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f1987c91392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f1987c91392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f1987c91392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f1987c91392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f1987c91392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7f1987c91392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7f1987c8c52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #19
[cantor] [Bug 397264] Cantor crashes with Python 2 backend when importing matplotlib.pyplot
https://bugs.kde.org/show_bug.cgi?id=397264 --- Comment #6 from Savor d'Isavano --- (In reply to Nikita Sirgienko from comment #5) > Did you build Cantor byself? No it's the binary package acquired from the Arch official repo, i.e. extra/cantor. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 397264] Cantor crashes with Python 2 backend when importing matplotlib.pyplot
https://bugs.kde.org/show_bug.cgi?id=397264 --- Comment #3 from Savor d'Isavano --- (In reply to Alexander Semke from comment #1) > The error seems to come from PySide/QtCore.so. I cannot reproduce this > problem here on openSuse. Does this import step works for when using python2 > directly in the terminal? Hi, it works: Python 2.7.15 (default, Jun 27 2018, 13:05:28) [GCC 8.1.1 20180531] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import matplotlib.pyplot as plt >>> plt >>> I'm running Arch and I have PySide2-5.11.0 and python-pyside-1.2.4 installed. Also note that the Python 3 session does not crash when running the import statement, but if doing actual plotting the backend server process terminates while Cantor remains running. (I may open a separate issue for this, but IMHO this behavior is saner than crashing) -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 397264] New: Cantor crashes with Python 2 backend when importing matplotlib.pyplot
https://bugs.kde.org/show_bug.cgi?id=397264 Bug ID: 397264 Summary: Cantor crashes with Python 2 backend when importing matplotlib.pyplot Product: cantor Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: fil...@kde.org Reporter: anohigisa...@gmail.com CC: alexander.se...@web.de, alexanderrie...@gmail.com Target Milestone: --- Application: cantor (18.04.3) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.17.11-arch1 x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I simply started a Python 2 session and input one line of code: ```python import matplotlib.pyplot as plt ``` Cantor instantly crashed. The crash can be reproduced every time. -- Backtrace: Application: Cantor (cantor), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9e766db140 (LWP 12048))] Thread 4 (Thread 0x7f9e5efc3700 (LWP 12051)): #0 0x7f9e7da8eaec in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9e5fbe31a4 in ?? () from /usr/lib/dri/i965_dri.so #2 0x7f9e5fbe2e98 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7f9e7da88a8d in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f9e812bd823 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f9e69709700 (LWP 12050)): #0 0x7f9e7bcfa030 in g_ptr_array_set_size () from /usr/lib/libglib-2.0.so.0 #1 0x7f9e7bd2793a in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7f9e7bd2844e in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f9e7bd2863e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f9e817f4054 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f9e8179f94c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f9e815e8a99 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f9e7e130976 in ?? () from /usr/lib/libQt5DBus.so.5 #8 0x7f9e815f2b45 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f9e7da88a8d in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f9e812bd823 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f9e72e0c700 (LWP 12049)): #0 0x7f9e812b2991 in poll () from /usr/lib/libc.so.6 #1 0x7f9e7babf180 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f9e7bac0e4b in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f9e75bbb22a in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f9e815f2b45 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f9e7da88a8d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f9e812bd823 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f9e766db140 (LWP 12048)): [KCrash Handler] #6 0x7f9e811f9b5f in raise () from /usr/lib/libc.so.6 #7 0x7f9e811e4452 in abort () from /usr/lib/libc.so.6 #8 0x7f9e815af33c in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #9 0x7f9e815c261b in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f9e817b76e8 in QMetaType::registerType(char const*, void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void const*), int, QFlags, QMetaObject const*) () from /usr/lib/libQt5Core.so.5 #11 0x7f9e817b776f in QMetaType::registerType(char const*, void (*)(void*), void* (*)(void const*)) () from /usr/lib/libQt5Core.so.5 #12 0x7f9e42bf50ae in ?? () from /usr/lib/python2.7/site-packages/PySide/QtCore.so #13 0x7f9e42bc01c3 in initQtCore () from /usr/lib/python2.7/site-packages/PySide/QtCore.so #14 0x7f9e57b2b520 in _PyImport_LoadDynamicModule () from /usr/lib/libpython2.7.so.1.0 #15 0x7f9e57ad504e in import_submodule () from /usr/lib/libpython2.7.so.1.0 #16 0x7f9e57b2b987 in ensure_fromlist.part () from /usr/lib/libpython2.7.so.1.0 #17 0x7f9e57ad5fd4 in PyImport_ImportModuleLevel () from /usr/lib/libpython2.7.so.1.0 #18 0x7f9e57adc22a in builtin___import__.lto_priv.1313 () from /usr/lib/libpython2.7.so.1.0 #19 0x7f9e57a3e0e3 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0 #20 0x7f9e57af47d1 in PyEval_CallObjectWithKeywords () from /usr/lib/libpython2.7.so.1.0 #21 0x7f9e57a9d8a8 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #22 0x7f9e57a9a9d0 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #23 0x7f9e57a9a9d0 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #24 0x7f9e57af50da in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 #25 0x7f9e57b1430a in PyEval_EvalCode () from /usr/lib/libpython2.7.so.1.0 #26 0x7f9e57b2afb1 in PyImport_ExecCodeModuleEx () from /usr/lib/libpython2.7.so.1.0 #27 0x7f9e57b2b19a in
[kwin] [Bug 345473] Double click on titlebar to maximize suddenly stops working
https://bugs.kde.org/show_bug.cgi?id=345473 Savor d'Isavano changed: What|Removed |Added Resolution|FIXED |--- CC||anohigisa...@gmail.com Status|RESOLVED|REOPENED --- Comment #49 from Savor d'Isavano --- Hi. In my end on 5.13.2 this issue persists. Triple-clicking does not work. However, if I: 1. right-click on the title bar while keep the right mouse button pressed. (the context menu will pop up) 2. Move the cursor away from the menu, but still on the title bar. 3. Double-click on the title bar. This will work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382580] New: Plasma crashes when searching in application launcher
https://bugs.kde.org/show_bug.cgi?id=382580 Bug ID: 382580 Summary: Plasma crashes when searching in application launcher Product: plasmashell Version: 5.10.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: anohigisa...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.4) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.11.9-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was trying to search for 'kvantum' and it crashed before I finished typing. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc96c6e3d80 (LWP 2879))] Thread 24 (Thread 0x7fc84effd700 (LWP 3678)): #0 0x7fc9655dc1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc9664105ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc8ace233cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fc8ace282b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fc8ace28312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fc8ace28312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fc8ace28312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7fc8ace28312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7fc8ace28312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7fc8ace28312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7fc8ace28312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7fc8ace28312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7fc8ace25b6b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7fc96640f15b in () at /usr/lib/libQt5Core.so.5 #23 0x7fc9655d6049 in start_thread () at /usr/lib/libpthread.so.0 #24 0x7fc965d22f0f in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7fc84f7fe700 (LWP 3677)): #0 0x7fc9655dc1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc9664105ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc8ace233cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fc8ace282b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fc8ace28312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fc8ace28312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fc8ace22913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fc8ace25b6b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fc96640f15b in () at /usr/lib/libQt5Core.so.5 #11 0x7fc9655d6049 in start_thread () at /usr/lib/libpthread.so.0 #12 0x7fc965d22f0f in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fc847fff700 (LWP 3676)): #0 0x7fc9655dc1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc9664105ec in
