[systemsettings] [Bug 450031] New: Global Theme category padding(?) issue
https://bugs.kde.org/show_bug.cgi?id=450031 Bug ID: 450031 Summary: Global Theme category padding(?) issue Product: systemsettings Version: 5.24.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: sidebarview Assignee: plasma-b...@kde.org Reporter: fk...@yandex.ru CC: notm...@gmail.com Target Milestone: --- Created attachment 146592 --> https://bugs.kde.org/attachment.cgi?id=146592&action=edit screenshot1 In System Settings with sidebar view, there is a visual inconsistency with Global Theme entry. It seems shifted to the left in sidebar, compared to the other entries. This is observed only with Appearance -> Global Theme (screenshot1 in attachments). In all other categories padding is normal. STEPS TO REPRODUCE 1. Open System Settings 2. In menubar switch to sidebar view 3. Go to Appearance category OBSERVED RESULT Global Theme entry seems to have an absent padding (screenshot1), unlike every other entries in this category. EXPECTED RESULT The same padding in all entries of all categories of system settings. Which is exactly the case, if not only for this one. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed 20220207 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450031] Global Theme category padding(?) issue
https://bugs.kde.org/show_bug.cgi?id=450031 --- Comment #2 from Kirill --- (In reply to Nate Graham from comment #1) > This is intentional; it tells you that those other pages are children of the > Global Themes page. Well, at least that's what it's supposed to tell you. :) > > We've gone back and forth on this a few times now and this is the > least-worst option we've found, short of redoing everything to actually > embed all of the other pages inside the Global Themes page. ...Which is an > option, but a long-term one, as it would be a lot of work. OK, thanks for replying and clarifying the situation, I think I understand why this is so. Still, I guess something must be done with it, because it looks like a bug to anybody not knowing how global theme and its subcategories work. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 441764] New: Removing multiple episodes from the queue
https://bugs.kde.org/show_bug.cgi?id=441764 Bug ID: 441764 Summary: Removing multiple episodes from the queue Product: kasts Version: unspecified Platform: Flatpak OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: kirill.m...@gmail.com Target Milestone: --- Created attachment 141154 --> https://bugs.kde.org/attachment.cgi?id=141154&action=edit difference in control buttons layout SUMMARY It's hard to manage and remove items from the large queues. OBSERVED RESULT I had the queue option to automatically queue new episodes enabled for a few weeks and ended up with 100+ episodes in my queue. That amount was a bit overwhelming, therefore I decided to clean up my queue. Then I've found out that it is possible to remove only one item from the queue at a time. And after clicking on "Remove from Queue" button it takes about 4~5 seconds for selected item to be removed, during which the rest of the app is unresponsive. EXPECTED RESULT It'd like to have an option to select multiple episodes in the queue at once - either with Shift+LMB and through long tap on mobile device, and then perform all the usual action (download/remove, etc.) on all of them. Also more consistent action buttons would be welcomed: Right now, depending on Kasts window width and title of the selected episode, action buttons "Download", "Remove from Queue", "Mark as Played", "Label as New" may be displayed with icons and text, just as icons and could be hidden partly or fully in the overflow menu (see attachment). I had to search for the "Remove from Queue" button on every single episode, because its position was constantly shifting. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 441764] Removing multiple episodes from the queue
https://bugs.kde.org/show_bug.cgi?id=441764 --- Comment #2 from Kirill --- No, that was on rather capable desktop: Ryzen 7 2700X (Eight-Core) 16Gb DDR4 (2666 MHz) SSD (Read: 540 Mb/s; Write: 490 Mb/s) And nothing particularly resource-hungry were running at the same time. Freeze was around 4~5 seconds for removing each item, when I've started clearing out the queue with 100+ episodes. When queue was shortened to 40 episodes, the freeze time dropped to around 2 seconds. And the last 10-15 episodes were removed without a noticeable delay. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477458] New: Saved files cannot be opened
https://bugs.kde.org/show_bug.cgi?id=477458 Bug ID: 477458 Summary: Saved files cannot be opened Classification: Applications Product: krita Version: 5.2.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: kirill@mail.ru Target Milestone: --- Created attachment 163424 --> https://bugs.kde.org/attachment.cgi?id=163424&action=edit The program cannot open saved files. It says the file format is not supported. Save with .kra resolution SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 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.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 Kirill changed: What|Removed |Added CC||kyrylo.shaki...@gmail.com --- Comment #14 from Kirill --- I have it reproducible for a long time. Also, when, just after KCalc starts, I hover mouse pointer on drop-down menu on top, it became stroboscopic - quickly light up and light down like disco. And yes, I use 150% scaling in display settings if this is somehow related. kcalc 23.08.3-1 Operating System: Manjaro Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.2-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 62.1 GB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: Victus by HP Laptop 16-e0xxx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413380] Compositor crash
https://bugs.kde.org/show_bug.cgi?id=413380 Kirill changed: What|Removed |Added CC||kiryaso...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414797] New: Crash
https://bugs.kde.org/show_bug.cgi?id=414797 Bug ID: 414797 Summary: Crash Product: krita Version: 4.2.8 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: kiryaso...@gmail.com Target Milestone: --- Application: krita (4.2.8) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.0.0-36-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Activated Layer moving tool, if I remember. It also crashes when I try to close program The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc2ee22f800 (LWP 25516))] Thread 27 (Thread 0x7fc212de8700 (LWP 25863)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7fc2e8fc0801 in __GI_abort () at abort.c:79 #8 0x7fc2e8fb039a in __assert_fail_base (fmt=0x7fc2ee187622 "%s%s%s:%u: %s%s\320\237\321\200\320\276\320\262\320\265\321\200\320\276\321\207\320\275\320\276\320\265 \321\203\321\202\320\262\320\265\321\200\320\266\320\264\320\265\320\275\320\270\320\265 \302\253%s\302\273 \320\275\320\265 \320\262\321\213\320\277\320\276\320\273\320\275\320\265\320\275\320\276.\n%n", assertion=assertion@entry=0x7fc2631ad8f0 "this->is_initialized()", file=file@entry=0x7fc2631ad760 "/usr/include/boost/optional/optional.hpp", line=line@entry=1107, function=function@entry=0x7fc2631ad9a0 ::get()::__PRETTY_FUNCTION__> "boost::optional::reference_type boost::optional::get() [with T = ToolTransformArgs; boost::optional::reference_type = ToolTransformArgs&]") at assert.c:92 #9 0x7fc2e8fb0412 in __GI___assert_fail (assertion=assertion@entry=0x7fc2631ad8f0 "this->is_initialized()", file=file@entry=0x7fc2631ad760 "/usr/include/boost/optional/optional.hpp", line=line@entry=1107, function=function@entry=0x7fc2631ad9a0 ::get()::__PRETTY_FUNCTION__> "boost::optional::reference_type boost::optional::get() [with T = ToolTransformArgs; boost::optional::reference_type = ToolTransformArgs&]") at assert.c:101 #10 0x7fc26314fa01 in boost::optional::get (this=) at /usr/include/boost/optional/optional.hpp:1107 #11 boost::optional::operator*() & (this=) at /usr/include/boost/optional/optional.hpp:1124 #12 TransformStrokeStrategy::finishStrokeCallback (this=) at ./plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp:704 #13 0x7fc26319becc in TransformStrokeStrategy::cancelStrokeCallback (this=0x55b946a3bb30) at /usr/include/boost/optional/optional.hpp:697 #14 0x7fc2ebc34849 in non-virtual thunk to KisUpdateJobItem::run() () from /usr/lib/x86_64-linux-gnu/libkritaimage.so.18 #15 0x7fc2e99c0472 in QThreadPoolThread::run (this=0x7fc1e40038d0) at thread/qthreadpool.cpp:99 #16 0x7fc2e99bcb52 in QThreadPrivate::start (arg=0x7fc1e40038d0) at thread/qthread_unix.cpp:360 #17 0x7fc2e2d356db in start_thread (arg=0x7fc212de8700) at pthread_create.c:463 #18 0x7fc2e90a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7fc210ff9700 (LWP 25642)): #0 0x7fc2e2d3b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b950b800a8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b950b80058, cond=0x55b950b80080) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b950b80080, mutex=0x55b950b80058) at pthread_cond_wait.c:655 #3 0x7fc2cf76fa2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc2cf76f757 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc2e2d356db in start_thread (arg=0x7fc210ff9700) at pthread_create.c:463 #6 0x7fc2e90a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7fc22f7fe700 (LWP 25617)): #0 0x7fc2e2d3b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b94fc3b788) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b94fc3b738, cond=0x55b94fc3b760) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b94fc3b760, mutex=0x55b94fc3b738) at pthread_cond_wait.c:655 #3 0x7fc2cf76fa2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc2cf76f757 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc2e2d356db in start_thread (arg=0x7fc22f7fe700) at pthread_create.c:463 #6 0x7fc2e90a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fc22d7fa700 (LWP 25616)): #0 0x7fc2e2d3b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b94e2ad7bc
[plasmashell] [Bug 394777] New: Plasma krashes due to "Gmail Feed" plasmoid
https://bugs.kde.org/show_bug.cgi?id=394777 Bug ID: 394777 Summary: Plasma krashes due to "Gmail Feed" plasmoid Product: plasmashell Version: 5.12.5 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kirill.m...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.5) Qt Version: 5.10.1 Frameworks Version: 5.46.0 Operating System: Linux 4.14.44-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: I was trying to open the Gmail Feed's dropdown from the System tray. That plasmoid is working well as a standalone widget, but it's crashing every time if used inside of System Tray. - Custom settings of the application: "Gmail Feed" plasmoid installed from AUR. https://aur.archlinux.org/packages/kdeplasma-applets-gmailfeed The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa3ec6b5800 (LWP 6914))] Thread 16 (Thread 0x7fa2e37fe700 (LWP 8166)): #0 0x7fa3e54caffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa3e6313f9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa3ea1175fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa3ea117a84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa3e6312abd in () at /usr/lib/libQt5Core.so.5 #5 0x7fa3e54c5075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa3e5c1653f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fa2aa1a6700 (LWP 7932)): #0 0x7fa3e54caffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa3e6313f9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa3ea1175fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa3ea117a84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa3e6312abd in () at /usr/lib/libQt5Core.so.5 #5 0x7fa3e54c5075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa3e5c1653f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fa2e3fff700 (LWP 7516)): #0 0x7fa3e54caffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa3e6313f9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa3ea1175fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa3ea117a84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa3e6312abd in () at /usr/lib/libQt5Core.so.5 #5 0x7fa3e54c5075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa3e5c1653f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fa2f8b29700 (LWP 7510)): #0 0x7fa3e54caffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa3e6313f9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa3ea1175fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa3ea117a84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa3e6312abd in () at /usr/lib/libQt5Core.so.5 #5 0x7fa3e54c5075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa3e5c1653f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fa302515700 (LWP 7383)): #0 0x7fa3e54caffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa3e6313f9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa3ea1175fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa3ea117a84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa3e6312abd in () at /usr/lib/libQt5Core.so.5 #5 0x7fa3e54c5075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa3e5c1653f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fa303416700 (LWP 7365)): #0 0x7fa3e54caffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa3e6313f9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa3ea1175fa in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa3ea117a84 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa3e6312abd in () at /usr/lib/libQt5Core.so.5 #5 0x7fa3e54c5075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa3e5c1653f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fa309e35700 (LWP 7350)): #0 0x7fa3e5c07934 in read () at /usr/lib/libc.so.6 #1 0x7fa3e04a3ed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fa3e045dff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fa3e045e4c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fa3e045e63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fa3e655c254 in
[plasmashell] [Bug 377335] New: Ubuntu 16.04 - Plasma crashed via xrdp (o-Matic)
https://bugs.kde.org/show_bug.cgi?id=377335 Bug ID: 377335 Summary: Ubuntu 16.04 - Plasma crashed via xrdp (o-Matic) Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kiril...@yandex.ru CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-65-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: Firs login after installing xrdp with X11rdp. Plasma crashs 3 times. On clien side I use mstsc.exe to connect to my ubuntu desctop. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f8d339c1900 (LWP 9438))] Thread 8 (Thread 0x7f8d011b9700 (LWP 9515)): [KCrash Handler] #6 0x7f8d2e00b428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f8d2e00d02a in __GI_abort () at abort.c:89 #8 0x7f8d2e003bd7 in __assert_fail_base (fmt=, assertion=assertion@entry=0x7f8d3245dd78 "!xcb_xlib_too_much_data_requested", file=file@entry=0x7f8d3245d92b "../../src/xcb_io.c", line=line@entry=736, function=function@entry=0x7f8d3245dda0 "_XRead") at assert.c:92 #9 0x7f8d2e003c82 in __GI___assert_fail (assertion=0x7f8d3245dd78 "!xcb_xlib_too_much_data_requested", file=0x7f8d3245d92b "../../src/xcb_io.c", line=736, function=0x7f8d3245dda0 "_XRead") at assert.c:101 #10 0x7f8d323ebf42 in _XRead () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #11 0x7f8d2a27c5fe in ?? () from /usr/lib/nvidia-304/libGL.so.1 #12 0x7f8d2efce136 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f8d2efce5e2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7f8d2efdd63d in QOpenGLBuffer::create() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7f8d2effef18 in QOpenGLTextureGlyphCache::createTextureData(int, int) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7f8d2ef8c05c in QTextureGlyphCache::fillInPendingGlyphs() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7f8d31a48db7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7f8d31a46c4c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f8d31ad0677 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f8d31ad4a9c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #21 0x7f8d31ad1547 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #22 0x7f8d31acfcb8 in QQuickText::updatePaintNode(QSGNode*, QQuickItem::UpdatePaintNodeData*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #23 0x7f8d31a8e2d8 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #24 0x7f8d31a8eb4b in QQuickWindowPrivate::updateDirtyNodes() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #25 0x7f8d31a8ecc0 in QQuickWindowPrivate::syncSceneGraph() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #26 0x7f8d31a5ffc5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #27 0x7f8d31a60fa5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #28 0x7f8d31a6608c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #29 0x7f8d2e7c67be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f8d2a2c0754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #31 0x7f8d2d8b36ba in start_thread (arg=0x7f8d011b9700) at pthread_create.c:333 #32 0x7f8d2e0dc82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f8d019ba700 (LWP 9513)): #0 0x7f8d2e876b7e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f8d2e9fb279 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f8d2e9fb7e5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f8d2e9fcbce in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8d2ae6591d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8d2ae662bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f8d2ae6649c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f8d2e9fd7eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8d2e9a4b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f8d2e7c1834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/l
[plasmashell] [Bug 377335] Ubuntu 16.04 - Plasma crashed via xrdp (o-Matic)
https://bugs.kde.org/show_bug.cgi?id=377335 Kirill changed: What|Removed |Added CC||kiril...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377335] Ubuntu 16.04 - Plasma crashed via xrdp (o-Matic)
https://bugs.kde.org/show_bug.cgi?id=377335 --- Comment #1 from Kirill --- Created attachment 104601 --> https://bugs.kde.org/attachment.cgi?id=104601&action=edit New crash information added by DrKonqi plasmashell (5.5.5) using Qt 5.5.1 I login to my system using xrdp and X11rdp. All previosly worked programs, such as KMail, starts, bud plasma crashs. When I used xfce4 in my .xsession file, DM works properly using xrdp|X11RDP. But when I use "startkde@ in .xsession file the problem occures. -- Backtrace (Reduced): #6 0x7f8ed3a05428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f8ed3a0702a in __GI_abort () at abort.c:89 #8 0x7f8ed39fdbd7 in __assert_fail_base (fmt=, assertion=assertion@entry=0x7f8ed7e57d78 "!xcb_xlib_too_much_data_requested", file=file@entry=0x7f8ed7e5792b "../../src/xcb_io.c", line=line@entry=736, function=function@entry=0x7f8ed7e57da0 "_XRead") at assert.c:92 #9 0x7f8ed39fdc82 in __GI___assert_fail (assertion=0x7f8ed7e57d78 "!xcb_xlib_too_much_data_requested", file=0x7f8ed7e5792b "../../src/xcb_io.c", line=736, function=0x7f8ed7e57da0 "_XRead") at assert.c:101 #10 0x7f8ed7de5f42 in _XRead () from /usr/lib/x86_64-linux-gnu/libX11.so.6 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 377921] New: krunner fails via xrdp & X11rdp session. I connect to my ubuntu system usind RDP-client mstsc.exe.
https://bugs.kde.org/show_bug.cgi?id=377921 Bug ID: 377921 Summary: krunner fails via xrdp & X11rdp session. I connect to my ubuntu system usind RDP-client mstsc.exe. Product: krunner Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: kiril...@yandex.ru Target Milestone: --- Application: krunner (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-67-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: I send Windows menu (Alt+Space) via rdp client mstsc.exe. Plasma desktop fail 3 times before krunner fails. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f79f8071900 (LWP 6023))] Thread 4 (Thread 0x7f79cfa16700 (LWP 6883)): [KCrash Handler] #6 0x7f79f49ff428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f79f4a0102a in __GI_abort () at abort.c:89 #8 0x7f79f49f7bd7 in __assert_fail_base (fmt=, assertion=assertion@entry=0x7f79f427dd78 "!xcb_xlib_too_much_data_requested", file=file@entry=0x7f79f427d92b "../../src/xcb_io.c", line=line@entry=736, function=function@entry=0x7f79f427dda0 "_XRead") at assert.c:92 #9 0x7f79f49f7c82 in __GI___assert_fail (assertion=0x7f79f427dd78 "!xcb_xlib_too_much_data_requested", file=0x7f79f427d92b "../../src/xcb_io.c", line=736, function=0x7f79f427dda0 "_XRead") at assert.c:101 #10 0x7f79f420bf42 in _XRead () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #11 0x7f79f13d65fe in ?? () from /usr/lib/nvidia-304/libGL.so.1 #12 0x7f79f59c2136 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f79f59c25e2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7f79f74c7a29 in QSGBatchRenderer::Renderer::unmap(QSGBatchRenderer::Buffer*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7f79f74c9db9 in QSGBatchRenderer::Renderer::uploadBatch(QSGBatchRenderer::Batch*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f79f74d4e03 in QSGBatchRenderer::Renderer::render() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x7f79f74e0b6f in QSGRenderer::renderScene(QSGBindable const&) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7f79f74e13bb in QSGRenderer::renderScene(unsigned int) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f79f74f187e in QSGRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f79f753c0db in QQuickWindowPrivate::renderSceneGraph(QSize const&) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #21 0x7f79f750f9c8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #22 0x7f79f751508c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #23 0x7f79f51ba7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f79f141a754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #25 0x7f79f2d146ba in start_thread (arg=0x7f79cfa16700) at pthread_create.c:333 #26 0x7f79f4ad082d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f79d921d700 (LWP 6037)): #0 0x7f79f4ac069d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f79f141973c in ?? () from /usr/lib/nvidia-304/libGL.so.1 #2 0x7f79ed3dfbf7 in ?? () from /usr/lib/nvidia-304/tls/libnvidia-tls.so.304.135 #3 0x7f79f21d66f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f79f2192e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f79f2193330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f79f219349c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f79f53f17eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f79f5398b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f79f51b5834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f79f702d3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7f79f51ba7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f79f141a754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #13 0x7f79f2d146ba in start_thread (arg=0x7f79d921d700) at pthread_create.c:333 #14 0x7f79f4ad082d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f79e2e44700 (LWP 6030)): #0 0x7f79f4ac4b5d in poll () at ../sysdeps/unix/syscall-template.S
[kcalc] [Bug 497850] New: Square of -2 produces -4
https://bugs.kde.org/show_bug.cgi?id=497850 Bug ID: 497850 Summary: Square of -2 produces -4 Classification: Applications Product: kcalc Version: 24.12.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: evan.te...@gmail.com Reporter: kyrylo.shaki...@gmail.com CC: gabriel.barrantes@outlook.com Target Milestone: --- Created attachment 176857 --> https://bugs.kde.org/attachment.cgi?id=176857&action=edit screenshot of kcalc demonstrating the bug SUMMARY Square of -2 produces -4 when it must be 4 STEPS TO REPRODUCE 1. Put kcalc to engineering mode 2. Press 2 3. Press change sign button (+/-) 4. Press square button (x2) OBSERVED RESULT -4 EXPECTED RESULT 4 SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 Kernel Version: 6.12.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 58.7 ГиБ of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 497850] Square of -2 produces -4
https://bugs.kde.org/show_bug.cgi?id=497850
Kirill changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED|REOPENED
Resolution|NOT A BUG |---
--- Comment #3 from Kirill ---
+/- button on calculators do not add "-" character to expression, but reverses
it sign.
But if we suppose it does - what is not a common convention.
Then, following input sequences must work and produce valid results:
1. "(", "2", "+/-"
Should produce "(-2", but produces "-2"
2. "(", "+/-"
Should produce "(-" but produces "–(()" and "malformed expression" error.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 372169] New: Light source
https://bugs.kde.org/show_bug.cgi?id=372169 Bug ID: 372169 Summary: Light source Product: krita Version: 3.0.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: kustov1...@gmail.com Target Milestone: --- Created attachment 102088 --> https://bugs.kde.org/attachment.cgi?id=102088&action=edit Not correctly Hello! I set the angle of the light source -45 in drop shadow (Layer style). See attachment. Shadow moves to light source. It is not corectly. Shadow should be located in the lower right corner. The location of the shadow is not correctly in another angles too. Sorry for my English. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372169] Light source
https://bugs.kde.org/show_bug.cgi?id=372169 --- Comment #1 from Kirill Kustov --- Created attachment 102090 --> https://bugs.kde.org/attachment.cgi?id=102090&action=edit Circle Point I understood bug. The angle of the light source, location of the shadows are correctly. Circle Point is incorrect. See attachement. Circle Point is must be show angle of the light source. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372169] Light source
https://bugs.kde.org/show_bug.cgi?id=372169 Kirill Kustov changed: What|Removed |Added Alias|kustov1...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372169] Light source
https://bugs.kde.org/show_bug.cgi?id=372169 --- Comment #2 from Kirill Kustov --- The same problem in Inner Shadow. Circle point isn't moving correctly too. The shadow should be located on the opposite side of the circle (object). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372169] GUI angular control for Shadow light source shows incorrect angle (spinbox is correct)
https://bugs.kde.org/show_bug.cgi?id=372169 Kirill Kustov changed: What|Removed |Added Summary|GUI angular control for |GUI angular control for |Drop Shadow's light source |Shadow light source shows |shows incorrect angle |incorrect angle (spinbox is |(spinbox is correct)|correct) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484439] Regression with Alt+Shift layout switching
https://bugs.kde.org/show_bug.cgi?id=484439 --- Comment #11 from Kirill Zhumarin --- (In reply to Oded Arbel from comment #7) > (In reply to Wismill from comment #6) > > This is another occurrence of the infamous “need to kick hotkeys on release, > > not press” (see: https://gitlab.freedesktop.org/xorg/xserver/-/issues/258). > > This is not a bug per se, but a known limitation of the XKB protocol. > > With Plasma 6.1 this is no longer a problem - if you stop using the XKB > configuration grp:alt_shift_toggle and instead use the KDE "alternative > shortcut" that can now be configured to be Alt+Shift. With that > configuration the repro looks like this: > 1. Set up 2+ input layouts > 2. Clear "main shorcuts" and set up "alternative shortcut" to "Alt+Shift". > 3. Go to a text editor - hold [Alt]; hold [Shift]; release [Alt]; start > typing > > Observerd result: > The text is typed using the second layout's 2nd level. For example for me > the second layout is Hebrew, whose 2nd level is Latin caps so typing > produces uppercase English. Still broken. At least on X11. 1. Press `Alt` 2. Press `Shift` 3. Release ONLY `Alt` 4. Try to type text. Typed text is uppercase (ok), BUT layout actually is not changed (bad). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484439] Regression with Alt+Shift layout switching
https://bugs.kde.org/show_bug.cgi?id=484439 --- Comment #12 from Kirill Zhumarin --- (In reply to Kirill Zhumarin from comment #11) > (In reply to Oded Arbel from comment #7) > > (In reply to Wismill from comment #6) > > > This is another occurrence of the infamous “need to kick hotkeys on > > > release, > > > not press” (see: > > > https://gitlab.freedesktop.org/xorg/xserver/-/issues/258). > > > This is not a bug per se, but a known limitation of the XKB protocol. > > > > With Plasma 6.1 this is no longer a problem - if you stop using the XKB > > configuration grp:alt_shift_toggle and instead use the KDE "alternative > > shortcut" that can now be configured to be Alt+Shift. With that > > configuration the repro looks like this: > > 1. Set up 2+ input layouts > > 2. Clear "main shorcuts" and set up "alternative shortcut" to "Alt+Shift". > > 3. Go to a text editor - hold [Alt]; hold [Shift]; release [Alt]; start > > typing > > > > Observerd result: > > The text is typed using the second layout's 2nd level. For example for me > > the second layout is Hebrew, whose 2nd level is Latin caps so typing > > produces uppercase English. > > Still broken. At least on X11. > > 1. Press `Alt` > 2. Press `Shift` > 3. Release ONLY `Alt` > 4. Try to type text. Typed text is uppercase (ok), BUT layout actually is > not changed (bad). It looks like the layout changes when release both Alt and Shift. But it should change immediately after pressing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484439] Regression with Alt+Shift layout switching
https://bugs.kde.org/show_bug.cgi?id=484439 --- Comment #15 from Kirill Zhumarin --- (In reply to Oded Arbel from comment #14) > During the discussion around that work, the issue was > raised of triggering the shortcut by any key release, and work on that has > been submitted for Plasma 6.2 > (https://invent.kde.org/plasma/kglobalacceld/-/merge_requests/53). Thank you. This is truly what Alt-Shift users need. I tested the same behavior in windows. It also changes the language when releasing any of the modifiers. And it works as I expected. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 489032] New: Hotkeys stop working on X11 after switching X11 <-> Wayland.
https://bugs.kde.org/show_bug.cgi?id=489032 Bug ID: 489032 Summary: Hotkeys stop working on X11 after switching X11 <-> Wayland. Classification: Frameworks and Libraries Product: frameworks-kglobalaccel Version: 6.1.0 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: kirill.zhuma...@gmail.com Target Milestone: --- Created attachment 170851 --> https://bugs.kde.org/attachment.cgi?id=170851&action=edit Configs examples. SUMMARY Hotkeys stop working on X11 after switching X11 <-> Wayland. STEPS TO REPRODUCE 1. Switch from X11 to Wayland 2. Switch from Wayland to X11 OBSERVED RESULT Some global shortcuts (for e.g. Ctrl+Alt+T) stop working. Any hotkeys in Java with Swing also stop working. EXPECTED RESULT Working hotkeys/global shortcuts. SOFTWARE/OS VERSIONS KDE neon KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Seems to be: 1. X11 and Wayland have inconsistent settings in kglobalaccel. 2. "Defaults" button (or just removing kglobalshortcutsrc) doesn't fix the issue. 3. Only one way to fix is reset entire settings. Only after this procedure can we get working kglobalshortcutsrc for X11. This is how I fix it: ``` # Temporary reset configs to default settings mv ~/.config ~/.config-bad sudo systemctl restart sddm # Copy the right config cp ~/.config/kglobalshortcutsrc ~/.config-bad/kglobalshortcutsrc # Restore old configs rm -rf ~/.config mv ~/.config-bad ~/.config sudo systemctl restart sddm ``` See in attachments: config.diff - difference between good and bad configs. kglobalshortcutsrc-good - this config was generated after removing .confg (good) kglobalshortcutsrc-bad - this config was generated after removing only ~/.config/kglobalshortcutsrc (bad) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 489032] Hotkeys stop working on X11 after switching X11 <-> Wayland.
https://bugs.kde.org/show_bug.cgi?id=489032 Kirill Zhumarin changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Kirill Zhumarin --- The reason turned out to be different. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 489036] New: Some global shortcuts stop working if the "primary" layout is cyrillic.
https://bugs.kde.org/show_bug.cgi?id=489036 Bug ID: 489036 Summary: Some global shortcuts stop working if the "primary" layout is cyrillic. Classification: Frameworks and Libraries Product: frameworks-kglobalaccel Version: 6.3.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: kirill.zhuma...@gmail.com Target Milestone: --- Created attachment 170854 --> https://bugs.kde.org/attachment.cgi?id=170854&action=edit kglobalshortcutsrc configs SUMMARY Users with multiple layouts can get a semi-working OS if they add a non-English layout as the first layout. STEPS TO REPRODUCE 1. Settings -> Keyboard -> Configure Layout 2. Add any cyrillic layout, for e.g. Russian/Ukrainian/Belarusian 3. Add layout English (US) (Order is important!) OBSERVED RESULT 1. Some global shortcuts stop working. For e.g. Ctrl-Alt-T. 2. Any hotkeys in Java Swing applications stop working. EXPECTED RESULT The order of layouts doesn't affect shortcuts. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION kglobalshortcutsrc-good - config generated with "en, ru" order kglobalshortcutsrc-bad - config generated with "ru, en" order -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 489036] Some global shortcuts stop working if the "primary" layout is cyrillic.
https://bugs.kde.org/show_bug.cgi?id=489036 --- Comment #1 from Kirill Zhumarin --- 1. Bug with Ctrl+Alt+T reproduced only with X11 2. Bug with hotkeys in Swing reproduced with both X11 & Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484439] Regression with Alt+Shift layout switching
https://bugs.kde.org/show_bug.cgi?id=484439 --- Comment #8 from Kirill Zhumarin --- (In reply to Wismill from comment #6) > This is another occurrence of the infamous “need to kick hotkeys on release, > not press” (see: https://gitlab.freedesktop.org/xorg/xserver/-/issues/258). > This is not a bug per se, but a known limitation of the XKB protocol. Any reasons why broken XCB is still used for layout switching? This can be implemented on the KDE side. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484439] Regression with Alt+Shift layout switching
https://bugs.kde.org/show_bug.cgi?id=484439 --- Comment #9 from Kirill Zhumarin --- Oh, sorry, I mean XKB, not XCB :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484439] New: Regression with Alt+Shift layout switching
https://bugs.kde.org/show_bug.cgi?id=484439 Bug ID: 484439 Summary: Regression with Alt+Shift layout switching Classification: Plasma Product: kwin Version: 6.0.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: kirill.zhuma...@gmail.com Target Milestone: --- SUMMARY It is impossible to normally use `Alt+Shift`. STEPS TO REPRODUCE 1. Add 2+ input layouts. 2. Enable `Input devices` -\> `Keyboard` -\> `Advanced` -\> `Switching to another layout` -\> `[x] Alt+Shift` OBSERVED RESULT 1. Press `Alt` 2. Press `Shift` 3. Release ONLY `Alt` 4. Try to type text. Typed text is lowercase, `Shift` is ignored. EXPECTED RESULT 1. Press `Alt` 2. Press `Shift` 3. Release ONLY `Alt` 4. Try to type text. Typed text is uppercase. SOFTWARE/OS VERSIONS Bug is present in both Plasma 5 and Plasma 6. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484439] Regression with Alt+Shift layout switching
https://bugs.kde.org/show_bug.cgi?id=484439 --- Comment #1 from Kirill Zhumarin --- Workaround: https://github.com/Azq2/alt-shift-kbd-layout-switcher -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484439] Regression with Alt+Shift layout switching
https://bugs.kde.org/show_bug.cgi?id=484439 --- Comment #2 from Kirill Zhumarin --- P.S. In Unity, GNOME, Windows works fine. -- You are receiving this mail because: You are watching all bug changes.
[plasma-simplemenu] [Bug 480838] New: Option to expand panel in fit content mode while in fullscreen
https://bugs.kde.org/show_bug.cgi?id=480838 Bug ID: 480838 Summary: Option to expand panel in fit content mode while in fullscreen Classification: Plasma Product: plasma-simplemenu Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: h...@kde.org Reporter: jp...@kiri.su CC: plasma-b...@kde.org Target Milestone: --- Created attachment 165532 --> https://bugs.kde.org/attachment.cgi?id=165532&action=edit Dock in the fit content mode SUMMARY It would be better to add a switch to allow expanding dock at the fit content mode while entering fullscreen STEPS TO REPRODUCE 1. Enable fit content length mode 2. Enter fullscreen app 3. Dock would have free space from the both sides of dock OBSERVED RESULT Free space from both sides of dock while no another space left is not too good EXPECTED RESULT Dock should expand at the fit content mode only while entering fullscreen if switch is toggled SOFTWARE/OS VERSIONS Linux/KDE Plasma: KaOS (2024) KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 487529] New: Broken global shortcuts in X11 session
https://bugs.kde.org/show_bug.cgi?id=487529 Bug ID: 487529 Summary: Broken global shortcuts in X11 session Classification: Frameworks and Libraries Product: frameworks-kglobalaccel Version: 6.2.0 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: kirill.zhuma...@gmail.com Target Milestone: --- SUMMARY Some global shortcuts stop working in the X11 session. But in Wayland it works. STEPS TO REPRODUCE 1. Press Ctrl+Alt+T OBSERVED RESULT Nothing happens. EXPECTED RESULT Running Konsole SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I tested with clean installation of the KDE Neon (both user and testing) and a bug is still present. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 487529] Broken global shortcuts in X11 session
https://bugs.kde.org/show_bug.cgi?id=487529 --- Comment #1 from Kirill Zhumarin --- I don't see any output on the dbus-monitor when I press Ctrl+Alt+T. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 487529] Broken global shortcuts in X11 session
https://bugs.kde.org/show_bug.cgi?id=487529 Kirill Zhumarin changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Kirill Zhumarin --- Seems to be fixed by removing ~/.config Now I don't know how to reproduce this bug. Maybe switching between X11 and wayland and something more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472013] New: Unmapping an xdg_toplevel with an existing xdg_popup causes a segfault in KWin::XdgPopupWindow::sendRoleConfigure
https://bugs.kde.org/show_bug.cgi?id=472013 Bug ID: 472013 Summary: Unmapping an xdg_toplevel with an existing xdg_popup causes a segfault in KWin::XdgPopupWindow::sendRoleConfigure Classification: Plasma Product: kwin Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: vyi...@eclair.cafe Target Milestone: --- Thread 1 "kwin" received signal SIGSEGV, Segmentation fault. 0x77981db4 in KWin::XdgPopupWindow::sendRoleConfigure (this=0x56763e80) at /usr/src/debug/kwin-5.27.6-1.fc38.x86_64/src/xdgshellwindow.cpp:1960 1960const QPointF parentPosition = transientFor()->framePosToClientPos(transientFor()->pos()); (gdb) bt #0 0x77981db4 in KWin::XdgPopupWindow::sendRoleConfigure() const (this=0x56763e80) at /usr/src/debug/kwin-5.27.6-1.fc38.x86_64/src/xdgshellwindow.cpp:1960 #1 0x77974197 in KWin::XdgSurfaceWindow::sendConfigure() (this=0x56763e80) at /usr/src/debug/kwin-5.27.6-1.fc38.x86_64/src/xdgshellwindow.cpp:131 #2 0x75ee8461 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffd9e0, r=, this=0x5691c6c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #3 doActivate(QObject*, int, void**) (sender=0x5675b350, signal_index=3, argv=0x7fffd9e0) at kernel/qobject.cpp:3925 #4 0x75ee3387 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x76166560 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffd9e0) at kernel/qobject.cpp:3985 #5 0x75eeb9dd in QTimer::timeout(QTimer::QPrivateSignal) (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #6 0x75edec8b in QObject::event(QEvent*) (this=0x5675b350, e=0x7fffdb50) at kernel/qobject.cpp:1369 #7 0x753aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x5675b350, e=0x7fffdb50) at kernel/qapplication.cpp:3640 #8 0x75eb4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5675b350, event=0x7fffdb50) at kernel/qcoreapplication.cpp:1064 #9 0x75eb43a2 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #10 0x75f05a7b in QTimerInfoList::activateTimers() (this=this@entry=0x557302d8) at kernel/qtimerinfo_unix.cpp:643 #11 0x75f02e30 in QEventDispatcherUNIXPrivate::activateTimers() (this=this@entry=0x55730250) at kernel/qeventdispatcher_unix.cpp:249 #12 0x75f03c80 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:516 #13 0x556962c2 in QUnixEventDispatcherQPA::processEvents(QFlags) () #14 0x75eb2b4b in QEventLoop::exec(QFlags) (this=this@entry=0x7fffdcf0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #15 0x75ebaddb in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #16 0x76360edd in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1863 #17 0x753aeae9 in QApplication::exec() () at kernel/qapplication.cpp:2832 #18 0x555afe44 in main(int, char**) (argc=, argv=) at /usr/src/debug/kwin-5.27.6-1.fc38.x86_64/src/main_wayland.cpp:628 (gdb) call transientFor() $1 = (const KWin::Window *) 0x0 STEPS TO REPRODUCE 1. Run `build/cases/xdg_toplevel_unmap_before_popup` from randfall [1]. OBSERVED RESULT KWin crashes due to a segfault. EXPECTED RESULT KWin doesn't crash. ADDITIONAL INFORMATION KWin was launched as a standalone WM without any DE components. [1] https://gitlab.freedesktop.org/vyivel/randfall -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419235] Plasma + Wayland Alacritty Decoration/Title Bar Has Gap Between Window Unless Maximized/Resized or Moved
https://bugs.kde.org/show_bug.cgi?id=419235 Kirill Chibisov changed: What|Removed |Added CC||cont...@kchibisov.com --- Comment #7 from Kirill Chibisov --- Hi, to get better understanding why this could happen, let me explain how decorations are handled in alacritty, so you may have a better understanding why you're facing this bug in KDE. First of all, all decorations on Wayland in alacritty are done by this project[1]. So it handled them by ALWAYS creating 5 subsurfaces[2], when you try creating a window, and SSD/CSD mode doesn't really matter here, since it's fine to create them, but not draw anything to them(it's a bit ugly, but it's correct code, that is being handled by mostly all compositors correctly). So those 5 subsurfaces are 1 for title bar and 4 for borders, the title bar is 30px, so one call to window geometry is -30px offset for some initial drawing, however that subsurface is not presented. However you may see the `set_geometry` with -30, ones, however there will be a proper set geometry later AFAICS. So, my theory is that our subsurfaces setup is somehow confusing kwin and it thinks that it should allocate space for those subsurfaces, where in reality it shouldn't (sway handles it correctly here AFAIK). But it could be that geometry calls are confusing kwin as well and it not trying to redraw window, idk. Also, you don't need alacritty to test this bug on, just any example from [1] should do a job(It uses rust wayland impl by default, so WAYLAND_DEBUG could be a bit different in terms of how it looks). Just running 'cargo run --example kbd_input' on those examples will likely work to repro and the code is more transparent and could give a better understanding why it happens. [1] - https://github.com/Smithay/client-toolkit [2] - https://github.com/Smithay/client-toolkit/blob/3555b3ce138422dc117e5b9ae33a22f574aa32be/src/window/concept_frame.rs#L346 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419235] Plasma + Wayland Alacritty Decoration/Title Bar Has Gap Between Window Unless Maximized/Resized or Moved
https://bugs.kde.org/show_bug.cgi?id=419235 --- Comment #10 from Kirill Chibisov --- >Passing "-30" seems wrong Nah, it's not that wrong. It'll indeed create a gap if we don't resize later and update geometry, but we do resize and use proper geometry, so I don't see much issues. Unless you can repro when we don't update window geometry to proper values. >even better don't create sub-surfaces at all. That could be the right thing to do, but creating sub-surfaces here is absolutely valid thing, and compositor should handle, don't you think? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378716] Crashes on video playback
https://bugs.kde.org/show_bug.cgi?id=378716 --- Comment #3 from Kirill Shustov --- unfortunatly I have no this camera anymore, I cannot reproduce it -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417591] New: System settings crashed in Application Style
https://bugs.kde.org/show_bug.cgi?id=417591 Bug ID: 417591 Summary: System settings crashed in Application Style Product: systemsettings Version: 5.18.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: djal...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.0) Qt Version: 5.13.2 Frameworks Version: 5.67.0 Operating System: Linux 4.15.0-76-generic 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 tried to open Application Style settings. This happen every time I try The crash can be reproduced every time. -- Backtrace: Application: Параметры системы (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef2ae9b800 (LWP 28998))] Thread 6 (Thread 0x7feef168f700 (LWP 29013)): #0 0x7fef1fad9649 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fef1fa92470 in g_main_context_acquire () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fef1fa93485 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fef1fa936dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fef26d37acb in QEventDispatcherGlib::processEvents (this=0x7feeec16b2a0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fef26cd7f9a in QEventLoop::exec (this=this@entry=0x7feef168ed80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7fef26af33aa in QThread::exec (this=this@entry=0x55a9828938a0) at thread/qthread.cpp:531 #7 0x7fef24678815 in QQmlThreadPrivate::run (this=0x55a9828938a0) at qml/ftw/qqmlthread.cpp:152 #8 0x7fef26af4b52 in QThreadPrivate::start (arg=0x55a9828938a0) at thread/qthread_unix.cpp:360 #9 0x7fef21e526db in start_thread (arg=0x7feef168f700) at pthread_create.c:463 #10 0x7fef263f188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7feef9189700 (LWP 29005)): #0 0x7fef263e00b4 in __GI___libc_read (fd=33, buf=0x7feef9188b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fef1fad82d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fef1fa930b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fef1fa93570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fef1fa936dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fef26d37acb in QEventDispatcherGlib::processEvents (this=0x7feef4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fef26cd7f9a in QEventLoop::exec (this=this@entry=0x7feef9188d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fef26af33aa in QThread::exec (this=this@entry=0x55a9814833f0) at thread/qthread.cpp:531 #8 0x7fef24678815 in QQmlThreadPrivate::run (this=0x55a9814833f0) at qml/ftw/qqmlthread.cpp:152 #9 0x7fef26af4b52 in QThreadPrivate::start (arg=0x55a9814833f0) at thread/qthread_unix.cpp:360 #10 0x7fef21e526db in start_thread (arg=0x7feef9189700) at pthread_create.c:463 #11 0x7fef263f188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fef026d5700 (LWP 29003)): #0 0x7fef263e00b4 in __GI___libc_read (fd=20, buf=0x7fef026d4b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fef1fad82d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fef1fa930b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fef1fa93570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fef1fa936dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fef26d37acb in QEventDispatcherGlib::processEvents (this=0x7feefc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fef26cd7f9a in QEventLoop::exec (this=this@entry=0x7fef026d4d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fef26af33aa in QThread::exec (this=this@entry=0x55a981225310) at thread/qthread.cpp:531 #8 0x7fef24678815 in QQmlThreadPrivate::run (this=0x55a981225310) at qml/ftw/qqmlthread.cpp:152 #9 0x7fef26af4b52 in QThreadPrivate::start (arg=0x55a981225310) at thread/qthread_unix.cpp:360 #10 0x7fef21e526db in start_thread (arg=0x7fef026d5700) at pthread_create.c:463 #11 0x7fef263f188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fef0fbf1700 (LWP 29001)): #0 0x7fef263e4bf9 in __GI___poll (fds=0x7fef08004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fef1fa935c9 in ?? () from /usr/lib/x8
[krita] [Bug 418606] New: Local selection mask is not marked by the selection tool
https://bugs.kde.org/show_bug.cgi?id=418606 Bug ID: 418606 Summary: Local selection mask is not marked by the selection tool Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: kustov1...@gmail.com Target Milestone: --- SUMMARY When I create it from the paint layer through converting to the local selection mask it is not marked by the selection tool, but there is it here and I can draw in the mask. But I can not see the edge of the mask. STEPS TO REPRODUCE 1. Create a new document. 2. Create two layers (Layer # 1, Layer # 2) 3. Draw white square at Layer # 2. 4. Convert Layer # 2 to Selection Mask and move it to Layer # 1. 5. Switch to Layer # 1. OBSERVED RESULT The local selection mask (Layer # 2) is not marked by the selection tool at Layer # 1. EXPECTED RESULT The local selection mask (Layer # 2) is marked by the selection tool at Layer # 1. Must be select square which I have drawn at Layer # 2. SOFTWARE/OS VERSIONS Windows: Windows 10 ADDITIONAL INFORMATION If I draw at Layer # 1 there is square here but I can not see edge 'cause Selection Tool is not visible. When I create a local selection mask from the selection tool (not paint layer) it's all right. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418606] Local selection mask is not marked by the selection tool
https://bugs.kde.org/show_bug.cgi?id=418606 --- Comment #3 from Kirill Kustov --- I am glad that this bug was fixed. Bur sorry I don't like alpha, beta, etc. If you are not against, I'll wait for the next release. Thanks a lot. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418650] New: Not correct direction of Inner Shadow
https://bugs.kde.org/show_bug.cgi?id=418650 Bug ID: 418650 Summary: Not correct direction of Inner Shadow Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: kustov1...@gmail.com Target Milestone: --- Created attachment 126683 --> https://bugs.kde.org/attachment.cgi?id=126683&action=edit Wrong Inner Shadow SUMMARY The direction of Inner Shadow doesn't fit angle control. It has to show the contrary result. STEPS TO REPRODUCE 1. Create a document. 2. Draw Circle on Layer #1. 3. Welcome to Layer Styles of Layer #1. 4. Turn on Inner Shadow and play with Angle. 5. Wait for the rerendering preview. OBSERVED RESULT Inner Shadow is displayed on the wrong side of the circle. EXPECTED RESULT Inner Shadow is displayed on another side of the circle. SOFTWARE/OS VERSIONS Windows: Windows 10 ADDITIONAL INFORMATION The control shows us the direction a point of light to the object, then Inner Shadow has to appear on another side of the object, not a light side. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418650] Not correct direction of Inner Shadow
https://bugs.kde.org/show_bug.cgi?id=418650 --- Comment #1 from Kirill Kustov --- Created attachment 126684 --> https://bugs.kde.org/attachment.cgi?id=126684&action=edit Correct Inner Shadow -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418651] New: Strange black lines in Inner Shadow
https://bugs.kde.org/show_bug.cgi?id=418651 Bug ID: 418651 Summary: Strange black lines in Inner Shadow Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: kustov1...@gmail.com Target Milestone: --- Created attachment 126685 --> https://bugs.kde.org/attachment.cgi?id=126685&action=edit Strange black lines SUMMARY On canvas appear strange black lines when I play with options of Inner Shadow in Layer Styles. Attached screenshot. STEPS TO REPRODUCE 1. Create a document. Resolution - 1600x1200x100. (perhaps resolution make affect, maybe not). 2. Draw Circle on Layer #1. 3. Welcome to Layer Styles of Layer #1. 4. Turn on Inner Shadow and play with options (Angle, Distance, Choke, Size). 5. Wait for the rerendering preview. OBSERVED RESULT Strange black lines. EXPECTED RESULT They should not be there. SOFTWARE/OS VERSIONS Windows: Windows 10 ADDITIONAL INFORMATION Perhaps, if you don't see strange black lines you need to retry action 4. Sometimes they not appear first times. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418650] Not correct direction of Inner Shadow
https://bugs.kde.org/show_bug.cgi?id=418650
--- Comment #3 from Kirill Kustov ---
I consider the controller of angle and position of Inner Shadow. The black
point of the controller angle shows us the angle of light dropping on the
ball/circle. This information I read at the tip when I position the mouse on
the black point of the controller ("Set the angle of the light source"). If
the black point is the light source It means that ray of light spread from the
up-right corner to the down-left corner. And Inner Shadow must be drawn
down-left corner of ball/circle.
Now Inner Shadow is drawn on the light side od ball/circle - it is a bug.
Now it controller shows us the "Position of the shadow", not the light source
how tip shows us.
ps. Drop Shadow must be drawn down-left corner too if the position of the
controller the same.
In general, there is an illogical situation in the tip and drawing Inner
shadow.
I see two cases to fix the bug:
1. Rewrite tip to "Position of the shadow" - simple, but interface will be less
logical (I mean Drop shadow, etc. Tips will differ. User will be confused too.
He doesn't always look at the tip, he expect the tip has the same value - "Set
the angle of the light source".).
2. Fix shadow.
In both cases it'll fix the bug and interface will be more (second case) or
less (first case) logical.
Sorry for my English mistakes if any. I hope I clearly showed the bug that I
mean.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 418651] Strange black lines in Inner Shadow
https://bugs.kde.org/show_bug.cgi?id=418651 --- Comment #4 from Kirill Kustov --- I downloaded the portable version (krita-nightly-x64-v4.3.0-prealpha-1296-gb1637fee3a.zip). It does not contain a bug. Thanks a lot. I will wait for the next release. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418606] Local selection mask is not marked by the selection tool
https://bugs.kde.org/show_bug.cgi?id=418606 --- Comment #4 from Kirill Kustov --- I downloaded the portable version. The bug was fixed. Thanks a lot again. One question if I can. Do you have an especially dates for the next releases or it publishes when you finish current development? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418651] Strange black lines in Inner Shadow
https://bugs.kde.org/show_bug.cgi?id=418651 Kirill Kustov changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #6 from Kirill Kustov --- In 4.3 was fixed, but not in 4.2.9. Will in 4.2.9 bug be fixed? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418650] Not correct direction of Inner Shadow
https://bugs.kde.org/show_bug.cgi?id=418650 --- Comment #4 from Kirill Kustov --- Also, you can turn the global light on and you'll see this bug the inner shadow is opposite drop shadow when light rays beam from the up-right corner. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418650] Not correct direction of Inner Shadow
https://bugs.kde.org/show_bug.cgi?id=418650 --- Comment #6 from Kirill Kustov --- I have no PS, but I see the video. There is have the same function in PS. Perhaps it has a tip - 'Angle' - solution to this situation, this solution decide all questions. But I don't think tip shows us "Set the angle of the light source" in PS. I don't know. Although everything can be. As I have said I have no PS. For me 'standard' is simply and logically. If one of these conditions does not execute it's not 'standard'. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418606] Local selection mask is not marked by the selection tool
https://bugs.kde.org/show_bug.cgi?id=418606 --- Comment #6 from Kirill Kustov --- Thanks for the info... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418650] Not correct direction of Inner Shadow or no correct tip
https://bugs.kde.org/show_bug.cgi?id=418650 Kirill Kustov changed: What|Removed |Added Summary|Not correct direction of|Not correct direction of |Inner Shadow|Inner Shadow or no correct ||tip -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382876] Copy/Paste Layer Styles
https://bugs.kde.org/show_bug.cgi?id=382876 Kirill Kustov changed: What|Removed |Added CC||kustov1...@gmail.com --- Comment #2 from Kirill Kustov --- It would be nice if Krita has this functional. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401605] Alt+Tab made Kwin crash repeatedly
https://bugs.kde.org/show_bug.cgi?id=401605 Kirill Romanov changed: What|Removed |Added CC||djal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413542] Can't UNbind Meta+Space from the global shortcuts
https://bugs.kde.org/show_bug.cgi?id=413542 Kirill Berezin changed: What|Removed |Added CC||ene...@exsul.net --- Comment #17 from Kirill Berezin --- sudo rm /usr/bin/krunner Fixes it for me after each reboot. But this isn't serious. When its going to be fixed? Operating System: Arch Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.4.23-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i3-4005U CPU @ 1.70GHz Memory: 15,6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 Kirill Romanov changed: What|Removed |Added CC||djal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 --- Comment #13 from Kirill Romanov --- Created attachment 117511 --> https://bugs.kde.org/attachment.cgi?id=117511&action=edit New crash information added by DrKonqi kwin_x11 (5.14.5) using Qt 5.11.2 - What I was doing when the application crashed: Just open my laptop after suspen. This happens to me only when second monitor connected to my laptop -- Backtrace (Reduced): #6 KWin::ContrastEffect::uploadRegion (this=this@entry=0x564330207890, map=@0x7ffdb34cd698: 0x7f2954425790, region=...) at ./effects/backgroundcontrast/contrast.cpp:281 #7 0x7f2975638404 in KWin::ContrastEffect::uploadGeometry (this=this@entry=0x564330207890, vbo=vbo@entry=0x5643303b5230, region=...) at ./effects/backgroundcontrast/contrast.cpp:299 #8 0x7f2975639965 in KWin::ContrastEffect::doContrast (this=this@entry=0x564330207890, w=w@entry=0x564330563d50, shape=..., screen=..., opacity=0, screenProjection=...) at ./effects/backgroundcontrast/contrast.cpp:442 #9 0x7f297563a35b in KWin::ContrastEffect::drawWindow (this=this@entry=0x564330207890, w=w@entry=0x564330563d50, mask=mask@entry=2, region=..., data=...) at ./effects/backgroundcontrast/contrast.cpp:419 #10 0x7f29788ab11e in KWin::EffectsHandlerImpl::drawWindow (this=this@entry=0x5643303fd890, w=w@entry=0x564330563d50, mask=mask@entry=2, region=..., data=...) at ./effects.cpp:456 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399706] New: KWin crashed after switch application with "Magic lamp"
https://bugs.kde.org/show_bug.cgi?id=399706 Bug ID: 399706 Summary: KWin crashed after switch application with "Magic lamp" Product: kwin Version: 5.14.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: nourep...@gmail.com Target Milestone: --- Application: kwin_x11 (5.14.0) Qt Version: 5.12.0 Frameworks Version: 5.50.0 Operating System: Linux 4.18.12-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: 1. Have two opened application on the different virtual desktops 2. Minimize (Or open) the window with the "Magic lamp" at the same time switch to the application on another virtual desktop The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff0be65d840 (LWP 5860))] Thread 6 (Thread 0x7ff09a036700 (LWP 5871)): #0 0x7ff0bcdbdafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff0bdcf920c in () at /usr/lib/libQt5Script.so.5 #2 0x7ff0bdcf9229 in () at /usr/lib/libQt5Script.so.5 #3 0x7ff0bcdb7a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7ff0bf8b3b23 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7ff09b8d7700 (LWP 5870)): #0 0x7ff0bcdbdef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff0be1f4a19 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7ff0be1f4b57 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7ff0be1f2b74 in () at /usr/lib/libQt5Core.so.5 #4 0x7ff0be1ee98c in () at /usr/lib/libQt5Core.so.5 #5 0x7ff0bcdb7a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7ff0bf8b3b23 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7ff0a3b87700 (LWP 5867)): #0 0x7ff0bf8a8d16 in ppoll () at /usr/lib/libc.so.6 #1 0x7ff0be3fc28b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7ff0be3fd76b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7ff0be3a93fc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff0be1ed589 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7ff0bc56ee19 in () at /usr/lib/libQt5Qml.so.5 #6 0x7ff0be1ee98c in () at /usr/lib/libQt5Core.so.5 #7 0x7ff0bcdb7a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7ff0bf8b3b23 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7ff0b1c97700 (LWP 5866)): #0 0x7ff0bcdbdef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff0be1f4a19 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7ff0be1f4b57 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7ff0be1f2b74 in () at /usr/lib/libQt5Core.so.5 #4 0x7ff0be1ee98c in () at /usr/lib/libQt5Core.so.5 #5 0x7ff0bcdb7a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7ff0bf8b3b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7ff0b313f700 (LWP 5865)): #0 0x7ff0bf8a8d16 in ppoll () at /usr/lib/libc.so.6 #1 0x7ff0be3fc28b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7ff0be3fd76b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7ff0be3a93fc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff0be1ed589 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7ff0bbfdcba6 in () at /usr/lib/libQt5DBus.so.5 #6 0x7ff0be1ee98c in () at /usr/lib/libQt5Core.so.5 #7 0x7ff0bcdb7a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7ff0bf8b3b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7ff0be65d840 (LWP 5860)): [KCrash Handler] #6 0x7ff0bf7efd7f in raise () at /usr/lib/libc.so.6 #7 0x7ff0bf7da672 in abort () at /usr/lib/libc.so.6 #8 0x7ff0be1b47fc in () at /usr/lib/libQt5Core.so.5 #9 0x7ff0bdf7ce7a in KWin::WindowQuad::makeSubQuad(double, double, double, double) const () at /usr/lib/libkwineffects.so.11 #10 0x7ff0b09334fd in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #11 0x7ff0b093365c in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #12 0x7ff0b093d113 in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #13 0x7ff0b093d259 in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #14 0x7ff0bf62d3fc in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QR
[kdenlive] [Bug 401412] New: Rotation effect preview playback is croped by wrong video size limits
https://bugs.kde.org/show_bug.cgi?id=401412 Bug ID: 401412 Summary: Rotation effect preview playback is croped by wrong video size limits Product: kdenlive Version: 18.08.3 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: kirill.sus...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Take video rotated on 90 degrees 2. Choose rotate effect and rotate on +-90 degreed 3. swicth playback on preview (on high quality works correctly OBSERVED RESULT video is rotated but cropped by old size limits. EXPECTED RESULT video should be rotated and preview whole without crop. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION here is video capture how it looks like https://www.dropbox.com/s/kjirst7jnu0arl1/kdenlive_bug_rotation_preview.mkv?dl=0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377326] New: Crashes on playing stabilized clip after stab job
https://bugs.kde.org/show_bug.cgi?id=377326 Bug ID: 377326 Summary: Crashes on playing stabilized clip after stab job Product: kdenlive Version: 16.12.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: kirill.sus...@gmail.com Target Milestone: --- After stabilizing video by stab job, new clip crashes app on play. 1. create nedw project 2. add clip 3. stab clip with default settings 4. add new stabilized clip to track 1 5. clip play result: crash console * "\n\n \n \n 00:01:16:13\n pause\n /home/kitru/Desktop/0-02-05-65dac90b59ca4ea8da47b8265bfd8106f64504906072ee1dc48b1e6c8cc2e9b6_full.mp4\n 1\n 1\n 0\n 1\n 1\n avformat-novalidate\n -1\n 8711536\n e3d88a039e56980ba31c50f46f169e1b\n 1\n \n\n" ** QObject::startTimer: Timers cannot be started from another thread * * *Setting document xml root: "" [swscaler @ 0x7fb9686c0d20] Warning: data is not aligned! This can lead to a speedloss * * *CREATED PROD: "/home/kitru/Desktop/0-02-05-65dac90b59ca4ea8da47b8265bfd8106f64504906072ee1dc48b1e6c8cc2e9b6_full.mp4.mlt" = "/home/kitru/Desktop/0-02-05-65dac90b59ca4ea8da47b8265bfd8106f64504906072ee1dc48b1e6c8cc2e9b6_full.mp4.mlt" * * *Setting document xml root: "" Assertion 'newindex >= 0 && newindex < (int) flist->size' failed at pulsecore/flist.c:93, function stack_push(). Aborting. /tmp/.mount_QUKhcz/AppRun: line 55: 19198 Aborted (core dumped) kdenlive --config kdenlive-appimagerc $@ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386033] New: KWin crushes after resuming from RAM suspension
https://bugs.kde.org/show_bug.cgi?id=386033 Bug ID: 386033 Summary: KWin crushes after resuming from RAM suspension Product: kwin Version: 5.11.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: kbobyrev.opensou...@gmail.com Target Milestone: --- Steps to reproduce: * Suspend to RAM * Resume from suspension * Login to my Desktop * "KWin: Desktop effects were restarted due to a graphics reset" This was sometimes a case in Plasma 5.10 and is always the case since my update to 5.11. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378716] New: Crashes on video playback
https://bugs.kde.org/show_bug.cgi?id=378716 Bug ID: 378716 Summary: Crashes on video playback Product: kdenlive Version: 16.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: kirill.sus...@gmail.com Target Milestone: --- App crashes on video playback with key-frame rotation -900. As side affect negative angled does not rotate video in console I see follow log, project is broken after crash and crashes on every start up. [swscaler @ 0x7fd318bc1440] Warning: data is not aligned! This can lead to a speedloss *** FOUND GUIDES: 0 ** GL error 0x502 at ycbcr_input.cpp:63 Aborted (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378716] Crashes on video playback
https://bugs.kde.org/show_bug.cgi?id=378716 --- Comment #1 from Kirill Shustov --- On next clip import crashes again [swscaler @ 0x7f2b3756e340] Warning: data is not aligned! This can lead to a speedloss GL error 0x502 at effect_chain.cpp:1877 Aborted (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379407] New: Crash on video play or clip import
https://bugs.kde.org/show_bug.cgi?id=379407 Bug ID: 379407 Summary: Crash on video play or clip import Product: kdenlive Version: 17.04.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: kirill.sus...@gmail.com Target Milestone: --- On adding or playing clips app crashes with seg fault. [New Thread 0x7fff6fb13700 (LWP 11415)] [New Thread 0x7fff5e7fc700 (LWP 11416)] [New Thread 0x7fff44ffc700 (LWP 11417)] Thread 17 "FrameRenderer" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff90abb700 (LWP 11393)] 0x71741520 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 (gdb) (gdb) thread apply all bt Thread 40 (Thread 0x7fff44ffc700 (LWP 11417)): #0 0x706216ed in nanosleep () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fffa8259bf5 in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltsdl.so #2 0x7fffeecdd6da in start_thread (arg=0x7fff44ffc700) at pthread_create.c:456 #3 0x7065d17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 39 (Thread 0x7fff5e7fc700 (LWP 11416)): #0 0x70651251 in __GI_ppoll (fds=0x7fff60d8a470, nfds=3, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fffeb3b16ad in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fffeb3b1c9e in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fffa7ff3feb in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #4 0x7fffa7fc6920 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #5 0x7fffa7fd00b8 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #6 0x7fffa800ff49 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #7 0x7fffeecdd6da in start_thread (arg=0x7fff5e7fc700) at pthread_create.c:456 #8 0x7065d17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 38 (Thread 0x7fff6fb13700 (LWP 11415)): #0 0x7fffbbcbd342 in ?? () from /usr/lib/x86_64-linux-gnu/libswscale.so.4 #1 0x0010 in ?? () #2 0x7fffbbca600f in ?? () from /usr/lib/x86_64-linux-gnu/libswscale.so.4 #3 0x7fffbbc94351 in ?? () from /usr/lib/x86_64-linux-gnu/libswscale.so.4 #4 0x7fffbbc956b6 in sws_scale () from /usr/lib/x86_64-linux-gnu/libswscale.so.4 #5 0x7fffb0f8df6a in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltavformat.so #6 0x76fff928 in mlt_frame_get_image () from /usr/lib/x86_64-linux-gnu/libmlt.so.6 #7 0x77015919 in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6 #8 0x76fff8d7 in mlt_frame_get_image () from /usr/lib/x86_64-linux-gnu/libmlt.so.6 #9 0x770122dd in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6 #10 0x7fffeecdd6da in start_thread (arg=0x7fff6fb13700) at pthread_create.c:456 #11 0x7065d17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 37 (Thread 0x7fff70314700 (LWP 11414)): #0 0x7173ee97 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #1 0x719580b7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #2 0x719651e1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #3 0x719b1214 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #4 0x719b8442 in QRasterPaintEngine::drawImage(QPointF const&, QImage const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x719d614b in QPainter::drawImage(QPointF const&, QImage const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #6 0x7fffa7ba43fb in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltqt.so #7 0x76fff8d7 in mlt_frame_get_image () from /usr/lib/x86_64-linux-gnu/libmlt.so.6 #8 0x77015919 in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6 #9 0x76fff8d7 in mlt_frame_get_image () from /usr/lib/x86_64-linux-gnu/libmlt.so.6 Video cliup is created by phantom 4 PRO Codec: H264 - MPEG-4 AVC (part 10) (avc1) Resolution: 2720x1538 Display resolution: 2720x1530 Frame rate: 59.940060 Decoded format: Planar 4:2:0 YUV -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379407] Crash on video play or clip import
https://bugs.kde.org/show_bug.cgi?id=379407 --- Comment #2 from Kirill Shustov --- can not reproduce with latest build from https://s3-eu-central-1.amazonaws.com/ds9-apps/index.html#!/kdenlive-master-appimage%2F -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 505524] New: KRunner frequently crashes
https://bugs.kde.org/show_bug.cgi?id=505524 Bug ID: 505524 Summary: KRunner frequently crashes Classification: Plasma Product: krunner Version First 6.3.5 Reported In: Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kir...@ultracoder.org CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- Application: krunner (6.3.5) (Compiled from sources) ApplicationNotResponding [ANR]: false Qt Version: 6.8.3 Frameworks Version: 6.13.0 Operating System: Linux 6.12.31 x86_64 Windowing System: Wayland Distribution: "Gentoo Linux" DrKonqi: 6.3.5 [CoredumpBackend] -- Information about the crash: How to reproduce: 1. Start KRunner using global hotkey or from terminal. 2. Begin to type some application's name. Additional information: Backtrace is different each time after QObject::event() call. Maybe it is a use-after-free bug with some race going on. The crash can be reproduced sometimes. -- Backtrace (Reduced): #4 0x7f96a5654a28 in QQmlGuardImpl::remGuard (this=0x560e3c6d5cf8) at /var/tmp/portage/dev-qt/qtdeclarative-6.8.3/work/qtdeclarative-everywhere-src-6.8.3/src/qml/qml/qqmlguard_p.h:173 #5 QQmlGuardImpl::setObject (this=0x560e3c6d5cf8, g=0x0) at /var/tmp/portage/dev-qt/qtdeclarative-6.8.3/work/qtdeclarative-everywhere-src-6.8.3/src/qml/qml/qqmlguard_p.h:225 #6 QQmlData::destroyed (this=0x560e3c746498, object=0x560e3c7463b0) at /var/tmp/portage/dev-qt/qtdeclarative-6.8.3/work/qtdeclarative-everywhere-src-6.8.3/src/qml/qml/qqmlengine.cpp:1418 #7 0x7f96a3ccd1d7 in QObject::~QObject (this=this@entry=0x560e3c7463b0, __in_chrg=) at /var/tmp/portage/dev-qt/qtbase-6.8.3-r1/work/qtbase-everywhere-src-6.8.3/src/corelib/kernel/qobject.cpp:1044 #8 0x7f96a5efbace in QQuickPointerHandler::~QQuickPointerHandler (this=this@entry=0x560e3c7463b0, __in_chrg=) at /var/tmp/portage/dev-qt/qtdeclarative-6.8.3/work/qtdeclarative-everywhere-src-6.8.3/src/quick/handlers/qquickpointerhandler.cpp:69 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 505524] KRunner frequently crashes
https://bugs.kde.org/show_bug.cgi?id=505524 --- Comment #1 from Kirill Kirilenko --- Created attachment 182228 --> https://bugs.kde.org/attachment.cgi?id=182228&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381815] New: Assertion 'newfd >= VG_(fd_hard_limit)' failed
https://bugs.kde.org/show_bug.cgi?id=381815
Bug ID: 381815
Summary: Assertion 'newfd >= VG_(fd_hard_limit)' failed
Product: valgrind
Version: unspecified
Platform: unspecified
OS: OS X
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: kir...@korins.ky
Target Milestone: ---
Good day!
I've tried to run valgrind (trunk, revision 16457) on macOS 10.12.5 and it
failed if I setup a huge number as file descriptors at ulimit.
For example:
➜ /tmp cat test.c
int main() {
return 0;
}
➜ /tmp clang test.c
➜ /tmp ulimit -n 1024
➜ /tmp valgrind ./a.out
==28447== Memcheck, a memory error detector
==28447== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==28447== Using Valgrind-3.14.0.SVN and LibVEX; rerun with -h for copyright
info
==28447== Command: ./a.out
==28447==
==28447== Syscall param msg->desc.port.name points to uninitialised byte(s)
==28447==at 0x1003A734A: mach_msg_trap (in
/usr/lib/system/libsystem_kernel.dylib)
==28447==by 0x1003A6796: mach_msg (in
/usr/lib/system/libsystem_kernel.dylib)
==28447==by 0x1003A0485: task_set_special_port (in
/usr/lib/system/libsystem_kernel.dylib)
==28447==by 0x10053C10E: _os_trace_create_debug_control_port (in
/usr/lib/system/libsystem_trace.dylib)
==28447==by 0x10053C458: _libtrace_init (in
/usr/lib/system/libsystem_trace.dylib)
==28447==by 0x1000A59DF: libSystem_initializer (in
/usr/lib/libSystem.B.dylib)
==28447==by 0x100017A1A:
ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) (in
/usr/lib/dyld)
==28447==by 0x100017C1D:
ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) (in
/usr/lib/dyld)
==28447==by 0x1000134A9:
ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned
int, char const*, ImageLoader::InitializerTimingList&,
ImageLoader::UninitedUpwards&) (in /usr/lib/dyld)
==28447==by 0x100013440:
ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned
int, char const*, ImageLoader::InitializerTimingList&,
ImageLoader::UninitedUpwards&) (in /usr/lib/dyld)
==28447==by 0x100012523:
ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int,
ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) (in
/usr/lib/dyld)
==28447==by 0x1000125B8:
ImageLoader::runInitializers(ImageLoader::LinkContext const&,
ImageLoader::InitializerTimingList&) (in /usr/lib/dyld)
==28447== Address 0x10488accc is on thread 1's stack
==28447== in frame #2, created by task_set_special_port (???:)
==28447==
==28447==
==28447== HEAP SUMMARY:
==28447== in use at exit: 18,307 bytes in 162 blocks
==28447== total heap usage: 178 allocs, 16 frees, 24,451 bytes allocated
==28447==
==28447== LEAK SUMMARY:
==28447==definitely lost: 408 bytes in 8 blocks
==28447==indirectly lost: 6,888 bytes in 8 blocks
==28447== possibly lost: 72 bytes in 3 blocks
==28447==still reachable: 32 bytes in 1 blocks
==28447== suppressed: 10,907 bytes in 142 blocks
==28447== Rerun with --leak-check=full to see details of leaked memory
==28447==
==28447== For counts of detected and suppressed errors, rerun with: -v
==28447== Use --track-origins=yes to see where uninitialised values come from
==28447== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4)
➜ /tmp ulimit -n 262144
➜ /tmp valgrind ./a.out
valgrind: m_libcfile.c:68 (Int vgPlain_safe_fd(Int)): Assertion 'newfd >=
VG_(fd_hard_limit)' failed.
[1]28477 segmentation fault valgrind ./a.out
➜ /tmp
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #2 from Kirill A. Korinsky --- Thanks for update. OS X doesn't have strace but it has dtruss that works only from root. and this bug doesn't reproduce from root user. Let me take some time to find a way to get the trace. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #3 from Kirill A. Korinsky --- Tom, I have one idea. Can you confirm that fd_hard_limit is getting from getrlimit? If so I think the right way to OS X is using getdtablesize and be sure that F_DUPFD argument less that returned value by getdtablesize. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed
https://bugs.kde.org/show_bug.cgi?id=381815
--- Comment #4 from Kirill A. Korinsky ---
Hey,
I can't trace valgrind because it calls fcntl over this code:
https://gist.github.com/catap/a20b8b1f46b0ba79b9f7297e73df0563
But I can run it in lldb ant provide some output to you.
With ulimit -n 1024:
➜ bin ulimit -n 1024
➜ bin env RETRACE_CONFIG=./retrace.conf.rnp
VALGRIND_LAUNCHER=/Users/catap/Documents/Riboseinc/valgrind/bin/executable_path=./valgrind
lldb -- ../lib/valgrind/memcheck-amd64-darwin /tmp/a.out
(lldb) target create "../lib/valgrind/memcheck-amd64-darwin"
Current executable set to '../lib/valgrind/memcheck-amd64-darwin' (x86_64).
(lldb) settings set -- target.run-args "/tmp/a.out"
(lldb) b vgPlain_safe_fd
Breakpoint 1: where = memcheck-amd64-darwin`vgPlain_safe_fd + 18 at
m_libcfile.c:59, address = 0x000258081452
(lldb) r
Process 14822 launched: '../lib/valgrind/memcheck-amd64-darwin' (x86_64)
Process 14822 stopped
* thread #1, stop reason = breakpoint 1.1
frame #0: 0x000258081452 memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:59
56 {
57 Int newfd;
58
-> 59 vg_assert(VG_(fd_hard_limit) != -1);
60
61 newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
62 if (newfd != -1)
(lldb) n
Process 14822 stopped
* thread #1, stop reason = step over
frame #0: 0x0002580814ac memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:61
58
59 vg_assert(VG_(fd_hard_limit) != -1);
60
-> 61 newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
62 if (newfd != -1)
63 VG_(close)(oldfd);
64
(lldb) n
Process 14822 stopped
* thread #1, stop reason = step over
frame #0: 0x0002580814ba memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:62
59 vg_assert(VG_(fd_hard_limit) != -1);
60
61 newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
-> 62 if (newfd != -1)
63 VG_(close)(oldfd);
64
65 /* Set the close-on-exec flag for this fd. */
(lldb) p newfd
(Int) $0 = 1024
(lldb) ^D
With ulimit 262144:
➜ bin env RETRACE_CONFIG=./retrace.conf.rnp
VALGRIND_LAUNCHER=/Users/catap/Documents/Riboseinc/valgrind/bin/executable_path=./valgrind
lldb -- ../lib/valgrind/memcheck-amd64-darwin /tmp/a.out
(lldb) target create "../lib/valgrind/memcheck-amd64-darwin"
Current executable set to '../lib/valgrind/memcheck-amd64-darwin' (x86_64).
(lldb) settings set -- target.run-args "/tmp/a.out"
(lldb) b vgPlain_safe_fd
Breakpoint 1: where = memcheck-amd64-darwin`vgPlain_safe_fd + 18 at
m_libcfile.c:59, address = 0x000258081452
(lldb) r
Process 14653 launched: '../lib/valgrind/memcheck-amd64-darwin' (x86_64)
Process 14653 stopped
* thread #1, stop reason = breakpoint 1.1
frame #0: 0x000258081452 memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:59
56 {
57 Int newfd;
58
-> 59 vg_assert(VG_(fd_hard_limit) != -1);
60
61 newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
62 if (newfd != -1)
(lldb) n
Process 14653 stopped
* thread #1, stop reason = step over
frame #0: 0x0002580814ac memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:61
58
59 vg_assert(VG_(fd_hard_limit) != -1);
60
-> 61 newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
62 if (newfd != -1)
63 VG_(close)(oldfd);
64
(lldb) n
Process 14653 stopped
* thread #1, stop reason = step over
frame #0: 0x0002580814ba memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:62
59 vg_assert(VG_(fd_hard_limit) != -1);
60
61 newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
-> 62 if (newfd != -1)
63 VG_(close)(oldfd);
64
65 /* Set the close-on-exec flag for this fd. */
(lldb) p newfd
(Int) $0 = -1
(lldb)
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #5 from Kirill A. Korinsky --- Created attachment 106527 --> https://bugs.kde.org/attachment.cgi?id=106527&action=edit don't crash on huge limits -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #6 from Kirill A. Korinsky --- Anyway, I just fixed it :) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed
https://bugs.kde.org/show_bug.cgi?id=381815 Kirill A. Korinsky changed: What|Removed |Added CC||kir...@korins.ky -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370356] New: very slow when delete photos and albums
https://bugs.kde.org/show_bug.cgi?id=370356 Bug ID: 370356 Summary: very slow when delete photos and albums Product: digikam Version: 5.2.0 Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: kirill_...@yahoo.com After right-click on empty or non-empty album or photo and click Delete Album or Move to Trash procedure of album or photo deleting take 2 to 5 minutes. Reproducible: Always Steps to Reproduce: 1. Right-click on Album 2. Click Delete Album 3. Click Delete button (or Move to trash button, does not matter) Actual Results: Deleting takes from 2 to 5 minutes Expected Results: Deleting should take 1 second or less I am using MySQL DB on remote server (local home network, 20 meters between iMac and server) for digikam databases, wired connection at 1 Gb/s between my iMac and DB server. 39000+ photos -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370356] very slow when delete photos and albums
https://bugs.kde.org/show_bug.cgi?id=370356 --- Comment #1 from Kirill --- Additional info. 1. Photos collection located at mounted network disk. 2. 2-5 minutes for deleting photos and folder only in case if collection located in root of Albums. Like this : Albums | -->My Collection | -->Photo1 | -->Photo2 | -->etc... But, if we place all folders 1 level deep (see schema bellow) from root - everything will start working very fast as expected: Albums | --> My Collection | -->All photos | -->Photo1 | -->Photo2 | -->etc... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 371550] New: Suggestion of an linked layers feature that will allow to transform several layers at the same time.
https://bugs.kde.org/show_bug.cgi?id=371550 Bug ID: 371550 Summary: Suggestion of an linked layers feature that will allow to transform several layers at the same time. Product: krita Version: unspecified Platform: unspecified OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: kirill.m...@gmail.com Sometimes there's a need for couple of layers to be connected to each other but they can't be merged or moved into one group, because they should remain on their specific places in the Layer's hierarchy. Here's image example: https://lut.im/thMjz4F7rD/zCbsjugFORZV9Hlo.png I have one object (hair) divided into two layers. First one is a forelock and it's top layer, since it's covering parts of the face, body and clothes. Second one is the rest of the hair, which is hanging behind the whole body, so it's placed at the bottom (not counting background layer). So there's no easy way to manipulate with these layers right now. If you want to move whole hair you need to manually select both layers and move them. If you want to transform them at the same time you need to create a group, put both of them there, transform them in the group and then put them back into their places. Also you'll need to set things like opacity and visibility individually for each layer. What I would like to see is an "Link" option in dropdown menu in Layers docker. It should be somewhat similar to grouping layers but while leaving them in their places. When highlighted, layer and all linked to it layers would be marked with an icon. When trying to move or apply transformation to one layer, you'll be manipulating with all linked to it layers at the same time. Reproducible: Couldn't Reproduce -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 357046] New: Pedestrian routing not working.
https://bugs.kde.org/show_bug.cgi?id=357046 Bug ID: 357046 Summary: Pedestrian routing not working. Product: marble Version: 1.13 (KDE Applications 15.12) Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: data Assignee: marble-b...@kde.org Reporter: kirill...@yandex.ru In pedestrian mode, only OSRM routing works, other not working with varying options, also Monav not installing downlaoded data, stack at the 100% download complete. Car shortest now torking - no warning messages, Bicycle not working. Reproducible: Always Steps to Reproduce: 1. make start point 2. make end point 3. swich routing modes Actual Results: no routings at pedestrian, bicycle, car (shortest) modes Expected Results: build route with selected mode: pedestrian, bicycle, car (shortest) intel, win 8.1 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 357046] Pedestrian routing not working.
https://bugs.kde.org/show_bug.cgi?id=357046 Kirill changed: What|Removed |Added Version|1.13 (KDE Applications |1.11 (KDE Applications |15.12) |15.04) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 357122] New: KDE Login error
https://bugs.kde.org/show_bug.cgi?id=357122 Bug ID: 357122 Summary: KDE Login error Product: kdelibs Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kded Assignee: unassigned-b...@kde.org Reporter: kiril...@yandex.ru Application: kded4 (4.14.13) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 3.13.0-45-generic i686 Distribution: Ubuntu 14.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: 1) Start remote session using xrdp & X11rdp 2) After KDE first screen starts appear error message The crash can be reproduced every time. -- Backtrace: Application: Служба KDE (kded4), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [KCrash Handler] #7 0xae438027 in XRandR11::config() const () from /usr/lib/kde4/plugins/kscreen/KSC_XRandR11.so #8 0xae40a956 in KScreen::Config::current() () from /usr/lib/libkscreen.so.1 #9 0xae563a65 in KScreenDaemon::monitorConnectedChange (this=this@entry=0x9936338) at /build/buildd/kscreen-1.0.2.1/kded/daemon.cpp:196 #10 0xae564284 in KScreenDaemon::KScreenDaemon (this=0x9936338, parent=0x97ee860) at /build/buildd/kscreen-1.0.2.1/kded/daemon.cpp:72 #11 0xae565121 in KPluginFactory::createInstance (parentWidget=0x0, parent=0x97ee860, args=...) at /usr/include/KDE/../kpluginfactory.h:477 #12 0xb70d0f44 in KPluginFactory::create (this=0x99315a8, iface=0xb71260e0 "KDEDModule", parentWidget=0x0, parent=0x97ee860, args=..., keyword=...) at ../../kdecore/util/kpluginfactory.cpp:203 #13 0xb52b8704 in create (args=..., parent=0x97ee860, this=) at ../../kdecore/util/kpluginfactory.h:507 #14 Kded::loadModule (this=0x97ee860, s=..., onDemand=onDemand@entry=false) at ../../kded/kded.cpp:409 #15 0xb52b9003 in Kded::initModules (this=0x97ee860) at ../../kded/kded.cpp:268 #16 0xb52b98ac in Kded::recreateDone (this=this@entry=0x97ee860) at ../../kded/kded.cpp:580 #17 0xb52b992b in Kded::recreate (this=0x97ee860, initial=true) at ../../kded/kded.cpp:547 #18 0xb52bc4c0 in KDEDApplication::newInstance (this=0xbfdbd2bc) at ../../kded/kded.cpp:833 #19 0xb7499b5f in KUniqueApplicationAdaptor::newInstance (this=this@entry=0x98e4c80, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:442 #20 0xb7499be6 in KUniqueApplicationAdaptor::qt_static_metacall (_o=_o@entry=0x98e4c80, _id=_id@entry=0, _a=_a@entry=0xbfdbca8c, _c=QMetaObject::InvokeMetaMethod) at ./kuniqueapplication_p.moc:57 #21 0xb7499e73 in qt_static_metacall (_a=0xbfdbca8c, _id=0, _c=QMetaObject::InvokeMetaMethod, _o=0x98e4c80) at ./kuniqueapplication_p.moc:100 #22 KUniqueApplicationAdaptor::qt_metacall (this=0x98e4c80, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfdbca8c) at ./kuniqueapplication_p.moc:101 #23 0xb5b2721e in QDBusConnectionPrivate::deliverCall (this=this@entry=0x97f2660, object=object@entry=0x98e4c80, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:951 #24 0xb5b2848e in QDBusConnectionPrivate::activateCall (this=0x97f2660, object=0x98e4c80, flags=337, msg=...) at qdbusintegrator.cpp:856 #25 0xb5b28b97 in QDBusConnectionPrivate::activateObject (this=0x97f2660, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1427 #26 0xb5b28f78 in QDBusActivateObjectEvent::placeMetaCall (this=0x98fb1d8) at qdbusintegrator.cpp:1541 #27 0xb6d836fb in QObject::event (this=this@entry=0xbfdbd2bc, e=e@entry=0x98fb1d8) at kernel/qobject.cpp:1194 #28 0xb6d6ea9a in QCoreApplication::event (this=0xbfdbd2bc, e=0x98fb1d8) at kernel/qcoreapplication.cpp:1765 #29 0xb627bd0f in QApplication::event (this=0xbfdbd2bc, e=0x98fb1d8) at kernel/qapplication.cpp:2549 #30 0xb62767f4 in QApplicationPrivate::notify_helper (this=0x97f1848, receiver=0xbfdbd2bc, e=0x98fb1d8) at kernel/qapplication.cpp:4567 #31 0xb627d2d3 in QApplication::notify (this=0xbfdbd2bc, receiver=receiver@entry=0xbfdbd2bc, e=e@entry=0x98fb1d8) at kernel/qapplication.cpp:4353 #32 0xb7491ce4 in KApplication::notify (this=0xbfdbd2bc, receiver=0xbfdbd2bc, event=0x98fb1d8) at ../../kdeui/kernel/kapplication.cpp:311 #33 0xb6d69e4a in QCoreApplication::notifyInternal (this=0xbfdbd2bc, receiver=receiver@entry=0xbfdbd2bc, event=event@entry=0x98fb1d8) at kernel/qcoreapplication.cpp:953 #34 0xb6d6d70d in sendEvent (event=0x98fb1d8, receiver=0xbfdbd2bc) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #35 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x9784f80) at kernel/qcoreapplication.cpp:1577 #36 0xb6d6dc1c in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470 #37 0xb6d9a23e in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #
[kdelibs] [Bug 357253] New: xrdp - Crash after logon
https://bugs.kde.org/show_bug.cgi?id=357253 Bug ID: 357253 Summary: xrdp - Crash after logon Product: kdelibs Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kded Assignee: unassigned-b...@kde.org Reporter: kiril...@yandex.ru Application: kded4 (4.14.13) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 3.13.0-45-generic i686 Distribution: Ubuntu 14.04.3 LTS -- Information about the crash: System crashs after logon. X11RDP + xrdp, client - mstsc The crash can be reproduced every time. -- Backtrace: Application: Служба KDE (kded4), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [KCrash Handler] #7 0xae4ea027 in XRandR11::config() const () from /usr/lib/kde4/plugins/kscreen/KSC_XRandR11.so #8 0xae4bc956 in KScreen::Config::current() () from /usr/lib/libkscreen.so.1 #9 0xae615a65 in KScreenDaemon::monitorConnectedChange (this=this@entry=0xa1579e0) at /build/buildd/kscreen-1.0.2.1/kded/daemon.cpp:196 #10 0xae616284 in KScreenDaemon::KScreenDaemon (this=0xa1579e0, parent=0x9ff8258) at /build/buildd/kscreen-1.0.2.1/kded/daemon.cpp:72 #11 0xae617121 in KPluginFactory::createInstance (parentWidget=0x0, parent=0x9ff8258, args=...) at /usr/include/KDE/../kpluginfactory.h:477 #12 0xb7181f44 in KPluginFactory::create (this=0xa157368, iface=0xb71d70e0 "KDEDModule", parentWidget=0x0, parent=0x9ff8258, args=..., keyword=...) at ../../kdecore/util/kpluginfactory.cpp:203 #13 0xb5369704 in create (args=..., parent=0x9ff8258, this=) at ../../kdecore/util/kpluginfactory.h:507 #14 Kded::loadModule (this=0x9ff8258, s=..., onDemand=onDemand@entry=false) at ../../kded/kded.cpp:409 #15 0xb536a003 in Kded::initModules (this=0x9ff8258) at ../../kded/kded.cpp:268 #16 0xb536a8ac in Kded::recreateDone (this=this@entry=0x9ff8258) at ../../kded/kded.cpp:580 #17 0xb536a92b in Kded::recreate (this=0x9ff8258, initial=true) at ../../kded/kded.cpp:547 #18 0xb536d4c0 in KDEDApplication::newInstance (this=0xbf8ffa3c) at ../../kded/kded.cpp:833 #19 0xb754ab5f in KUniqueApplicationAdaptor::newInstance (this=this@entry=0xa10f3d8, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:442 #20 0xb754abe6 in KUniqueApplicationAdaptor::qt_static_metacall (_o=_o@entry=0xa10f3d8, _id=_id@entry=0, _a=_a@entry=0xbf8ff20c, _c=QMetaObject::InvokeMetaMethod) at ./kuniqueapplication_p.moc:57 #21 0xb754ae73 in qt_static_metacall (_a=0xbf8ff20c, _id=0, _c=QMetaObject::InvokeMetaMethod, _o=0xa10f3d8) at ./kuniqueapplication_p.moc:100 #22 KUniqueApplicationAdaptor::qt_metacall (this=0xa10f3d8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf8ff20c) at ./kuniqueapplication_p.moc:101 #23 0xb5bd821e in QDBusConnectionPrivate::deliverCall (this=this@entry=0x9ff97c0, object=object@entry=0xa10f3d8, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:951 #24 0xb5bd948e in QDBusConnectionPrivate::activateCall (this=0x9ff97c0, object=0xa10f3d8, flags=337, msg=...) at qdbusintegrator.cpp:856 #25 0xb5bd9b97 in QDBusConnectionPrivate::activateObject (this=0x9ff97c0, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1427 #26 0xb5bd9f78 in QDBusActivateObjectEvent::placeMetaCall (this=0xa129c10) at qdbusintegrator.cpp:1541 #27 0xb6e346fb in QObject::event (this=this@entry=0xbf8ffa3c, e=e@entry=0xa129c10) at kernel/qobject.cpp:1194 #28 0xb6e1fa9a in QCoreApplication::event (this=0xbf8ffa3c, e=0xa129c10) at kernel/qcoreapplication.cpp:1765 #29 0xb632cd0f in QApplication::event (this=0xbf8ffa3c, e=0xa129c10) at kernel/qapplication.cpp:2549 #30 0xb63277f4 in QApplicationPrivate::notify_helper (this=0x9ff8b30, receiver=0xbf8ffa3c, e=0xa129c10) at kernel/qapplication.cpp:4567 #31 0xb632e2d3 in QApplication::notify (this=0xbf8ffa3c, receiver=receiver@entry=0xbf8ffa3c, e=e@entry=0xa129c10) at kernel/qapplication.cpp:4353 #32 0xb7542ce4 in KApplication::notify (this=0xbf8ffa3c, receiver=0xbf8ffa3c, event=0xa129c10) at ../../kdeui/kernel/kapplication.cpp:311 #33 0xb6e1ae4a in QCoreApplication::notifyInternal (this=0xbf8ffa3c, receiver=receiver@entry=0xbf8ffa3c, event=event@entry=0xa129c10) at kernel/qcoreapplication.cpp:953 #34 0xb6e1e70d in sendEvent (event=0xa129c10, receiver=0xbf8ffa3c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #35 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x9f8bf80) at kernel/qcoreapplication.cpp:1577 #36 0xb6e1ec1c in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470 #37 0xb6e4b23e in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #38 postEventSourceDispatch (s=0x9ff8eb8) at kernel/qeventdispatcher_glib.cpp:287
[kaddressbook] [Bug 357361] New: KAddressBook crash's during GMail Sync
https://bugs.kde.org/show_bug.cgi?id=357361 Bug ID: 357361 Summary: KAddressBook crash's during GMail Sync Product: kaddressbook Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kiril...@yandex.ru CC: to...@kde.org Application: kaddressbook (4.14.3) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 3.13.0-45-generic i686 Distribution: Ubuntu 14.04.3 LTS -- Information about the crash: RAddressBook crash's after GMAil sync The crash can be reproduced every time. -- Backtrace: Application: KAddressBook (kaddressbook), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb0d9d780 (LWP 10457))] Thread 2 (Thread 0xadcd9b40 (LWP 10459)): #0 0xb4d6dd0e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb4d6e0d8 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb4d29398 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb4d29528 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb639095f in QEventDispatcherGlib::processEvents (this=0xad300468, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #5 0xb635f823 in QEventLoop::processEvents (this=this@entry=0xadcd9218, flags=...) at kernel/qeventloop.cpp:149 #6 0xb635fb49 in QEventLoop::exec (this=this@entry=0xadcd9218, flags=...) at kernel/qeventloop.cpp:204 #7 0xb624c23d in QThread::exec (this=this@entry=0x90da780) at thread/qthread.cpp:537 #8 0xb633fc44 in QInotifyFileSystemWatcherEngine::run (this=0x90da780) at io/qfilesystemwatcher_inotify.cpp:265 #9 0xb624eb6f in QThreadPrivate::start (arg=0x90da780) at thread/qthread_unix.cpp:349 #10 0xb4e0ef70 in start_thread (arg=0xadcd9b40) at pthread_create.c:312 #11 0xb601fbee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 1 (Thread 0xb0d9d780 (LWP 10457)): [KCrash Handler] #7 0xb22fa184 in prison::DataMatrixBarcode::toImage(QSizeF const&) () from /usr/lib/i386-linux-gnu/libprison.so.0 #8 0xb50fa19c in Akonadi::ContactViewer::Private::updateView (this=0x8e79348, localCustomFieldDescriptions=..., addressBookName=...) at ../../../akonadi/contact/contactviewer.cpp:124 #9 0xb50f8d00 in slotParentCollectionFetched (job=, this=) at ../../../akonadi/contact/contactviewer.cpp:213 #10 Akonadi::ContactViewer::qt_static_metacall (_o=, _id=, _a=0xbff27f88, _c=) at ./moc_contactviewer.cpp:78 #11 0xb63760f7 in QMetaObject::activate (sender=sender@entry=0xae7f4c0, m=m@entry=0xb677752c , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0xbff27f88) at kernel/qobject.cpp:3539 #12 0xb65d6e65 in KJob::result (this=this@entry=0xae7f4c0, _t1=_t1@entry=0xae7f4c0) at ./kjob.moc:207 #13 0xb65d6eb2 in KJob::emitResult (this=this@entry=0xae7f4c0) at ../../kdecore/jobs/kjob.cpp:318 #14 0xb53598a7 in Akonadi::JobPrivate::delayedEmitResult (this=0x985ab68) at ../../akonadi/job.cpp:165 #15 0xb63728aa in QMetaCallEvent::placeMetaCall (this=0xae05cc8, object=0xae7f4c0) at kernel/qobject.cpp:524 #16 0xb637a6fb in QObject::event (this=0xae7f4c0, e=0xae05cc8) at kernel/qobject.cpp:1194 #17 0xb68b87f4 in QApplicationPrivate::notify_helper (this=0x8e3c3a0, receiver=0xae7f4c0, e=0xae05cc8) at kernel/qapplication.cpp:4567 #18 0xb68bf2d3 in QApplication::notify (this=0xbff285e8, receiver=receiver@entry=0xae7f4c0, e=e@entry=0xae05cc8) at kernel/qapplication.cpp:4353 #19 0xb74cace4 in KApplication::notify (this=0xbff285e8, receiver=0xae7f4c0, event=0xae05cc8) at ../../kdeui/kernel/kapplication.cpp:311 #20 0xb6360e4a in QCoreApplication::notifyInternal (this=0xbff285e8, receiver=receiver@entry=0xae7f4c0, event=event@entry=0xae05cc8) at kernel/qcoreapplication.cpp:953 #21 0xb636470d in sendEvent (event=0xae05cc8, receiver=0xae7f4c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x8e032a0) at kernel/qcoreapplication.cpp:1577 #23 0xb6364c1c in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470 #24 0xb639123e in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #25 postEventSourceDispatch (s=0x8e3c788) at kernel/qeventdispatcher_glib.cpp:287 #26 0xb4d291e3 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #27 0xb4d29468 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #28 0xb4d29528 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #29 0xb639093b in QEventDispatcherGlib::processEvents (this=this@entry=0x8e03e10, flags=...) at kernel/qeventdispatcher_glib.cpp:434 #30 0xb696d60e in
[kontact] [Bug 359461] New: Kontakt crashs after mailbox folder settings changed
https://bugs.kde.org/show_bug.cgi?id=359461 Bug ID: 359461 Summary: Kontakt crashs after mailbox folder settings changed Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kiril...@yandex.ru Application: kontact (4.14.3) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 3.19.0-49-generic x86_64 Distribution: Ubuntu 14.04.3 LTS -- Information about the crash: Kontakt crashs after mailbox folder settings changed The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff65e1be800 (LWP 16121))] Thread 5 (Thread 0x7ff63d63d700 (LWP 16122)): #0 0x7ff655685414 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7ff658f6081d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7ff658f60859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7ff655681182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7ff65b73447d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7ff5fcd22700 (LWP 16123)): #0 0x7ff655685414 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7ff658ca120d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7ff658f8ffd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7ff655681182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7ff65b73447d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7ff5ecb62700 (LWP 16158)): #0 0x7ff65b72712d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7ff6551a1fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff6551a20ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff65bead7be in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7ff65be7f0af in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7ff65be7f3a5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7ff65bd7bc5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7ff65be60823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7ff65bd7e32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7ff655681182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7ff65b73447d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7ff5e6c0d700 (LWP 16218)): #0 0x7ff6556835c0 in pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7ff6551e3981 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff6551a1ed5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff6551a20ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff65bead7be in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7ff65be7f0af in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7ff65be7f3a5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7ff65bd7bc5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7ff65bd7e32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7ff655681182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7ff65b73447d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7ff65e1be800 (LWP 16121)): [KCrash Handler] #5 0x7ff65b670cc9 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x7ff65b6740d8 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7ff65bd73c92 in qt_message_output(QtMsgType, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7ff65bd73ff9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7ff65bd74804 in qFatal(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7ff5f2864bc7 in MailCommon::Kernel::self() () from /usr/lib/libmailcommon.so.4 #11 0x7ff5f28a9c90 in MailCommon::FolderCollection::writeConfig() const () from /usr/lib/libmailcommon.so.4 #12 0x7ff5f28aa492 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib/libmailcommon.so.4 #13 0x7ff5f28aa509 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib/libmailcommon.so.4 #14 0x7ff5f28a8dc4 in ?? () from /usr/lib/libmailcommon.so.4 #15 0x7ff65b676259 in ??
[plasmashell] [Bug 347554] System tray is messed up after login
https://bugs.kde.org/show_bug.cgi?id=347554 Kirill Bogdanenko changed: What|Removed |Added CC||kirill.bogdane...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347554] System tray is messed up after login
https://bugs.kde.org/show_bug.cgi?id=347554 --- Comment #17 from Kirill Bogdanenko --- BTW, the icon appears for me if I go into "System Tray Widget Settings" and do Hide -> Apply -> Show -> Apply with the plasma-pa item. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup
https://bugs.kde.org/show_bug.cgi?id=352055 Kirill Bogdanenko changed: What|Removed |Added CC||kirill.bogdane...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup
https://bugs.kde.org/show_bug.cgi?id=352055 --- Comment #50 from Kirill Bogdanenko --- (In reply to Olivier Churlaud from comment #49) > Killing and starting again plasmashell solves the issue... You can also try toggling off and on plasma-pa widget in systemtray settings -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353418] External display is overlapped with laptop's screen on boot
https://bugs.kde.org/show_bug.cgi?id=353418 --- Comment #6 from Kirill Bogdanenko --- Probably, the bug is in SDDM's side. Because it has a similar problem initially: when SDDM shows up, the laptop's screen is attached by the upper left corner to the upper left corner of external screen. Here is the video of SDDM/plasma bootup process: https://youtu.be/tvLjQBa3Hd4 Also, I've noticed that plasma crashes when I connect/disconnect my external screen. This might be related or another bug as vell. (I'll attach debug information later) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353418] External display is overlapped with laptop's screen on boot
https://bugs.kde.org/show_bug.cgi?id=353418 --- Comment #7 from Kirill Bogdanenko --- Created attachment 96694 --> https://bugs.kde.org/attachment.cgi?id=96694&action=edit KWin stacktrace when disconnecting external screen (SIGABRT) KWIn, Plasma and KRunner crash when I disconnnect the external screen. Attaching their backtraces. Also, when I connect the external screen, (laptop's) display switches to tty1 (while X is on tty7) and after switching back to tty7 I see login screen again (plasma session closed, probably SDDM crashed) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353418] External display is overlapped with laptop's screen on boot
https://bugs.kde.org/show_bug.cgi?id=353418 --- Comment #8 from Kirill Bogdanenko --- Created attachment 96695 --> https://bugs.kde.org/attachment.cgi?id=96695&action=edit Plasmashell stacktrace when disconnecting external screen -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353418] External display is overlapped with laptop's screen on boot
https://bugs.kde.org/show_bug.cgi?id=353418 --- Comment #9 from Kirill Bogdanenko --- Created attachment 96696 --> https://bugs.kde.org/attachment.cgi?id=96696&action=edit Krunner stacktrace when disconnecting external screen -- You are receiving this mail because: You are watching all bug changes.
