[drkonqi] [Bug 372108] New: drconqi segmentation fault creating bug-report
https://bugs.kde.org/show_bug.cgi?id=372108 Bug ID: 372108 Summary: drconqi segmentation fault creating bug-report Product: drkonqi Version: 5.7.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: backtraceparsing Assignee: unassigned-b...@kde.org Reporter: ken20...@ukr.net Target Milestone: --- kwin_x11 creashed but then drconqi crashed too: Application: drkonqi (drkonqi), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffabe89b8c0 (LWP 23635))] Thread 4 (Thread 0x7ffa98300700 (LWP 23646)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ffa9c0754d3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #2 0x7ffa9c074c17 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #3 0x7ffab8e7170a in start_thread (arg=0x7ffa98300700) at pthread_create.c:333 #4 0x7ffabacce0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7ffaa544a700 (LWP 23637)): #0 0x7ffabacc20bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7ffab84eb9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffab84ebaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffabb5f04ab in QEventDispatcherGlib::processEvents (this=0x7ffaa8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7ffabb5980fa in QEventLoop::exec (this=this@entry=0x7ffaa5449cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7ffabb3bdd43 in QThread::exec (this=this@entry=0x7ffabe9ced60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500 #6 0x7ffabe95a575 in QDBusConnectionManager::run (this=0x7ffabe9ced60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:171 #7 0x7ffabb3c2c68 in QThreadPrivate::start (arg=0x7ffabe9ced60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:341 #8 0x7ffab8e7170a in start_thread (arg=0x7ffaa544a700) at pthread_create.c:333 #9 0x7ffabacce0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7ffaacf39700 (LWP 23636)): #0 0x7ffabacc20bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7ffab668bc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ffab668d8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ffaaf490299 in QXcbEventReader::run (this=0x56478bf49c70) at qxcbconnection.cpp:1325 #4 0x7ffabb3c2c68 in QThreadPrivate::start (arg=0x56478bf49c70) at thread/qthread_unix.cpp:341 #5 0x7ffab8e7170a in start_thread (arg=0x7ffaacf39700) at pthread_create.c:333 #6 0x7ffabacce0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7ffabe89b8c0 (LWP 23635)): [KCrash Handler] #6 0x56478acaab12 in ?? () #7 0x7ffabba41978 in QSyntaxHighlighterPrivate::reformatBlock (this=this@entry=0x56478d0fdc70, block=...) at text/qsyntaxhighlighter.cpp:195 #8 0x7ffabba41bde in QSyntaxHighlighterPrivate::reformatBlocks (this=0x56478d0fdc70, from=, charsRemoved=, charsAdded=) at text/qsyntaxhighlighter.cpp:176 #9 0x7ffabb5c7b49 in QMetaObject::activate (sender=sender@entry=0x56478c0bdbc0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcdca5db20) at kernel/qobject.cpp:3730 #10 0x7ffabb5c80f7 in QMetaObject::activate (sender=sender@entry=0x56478c0bdbc0, m=m@entry=0x7ffabbd6aee0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcdca5db20) at kernel/qobject.cpp:3595 #11 0x7ffabbc9773a in QTextDocument::contentsChange (this=this@entry=0x56478c0bdbc0, _t1=, _t2=, _t3=) at .moc/moc_qtextdocument.cpp:382 #12 0x7ffabb9ff41e in QTextDocumentPrivate::finishEdit (this=0x56478c0bdbe0) at text/qtextdocument_p.cpp:1209 #13 0x7ffabb9ff663 in QTextDocumentPrivate::endEditBlock (this=) at text/qtextdocument_p.cpp:1193 #14 0x7ffabb9ff6be in QTextDocumentPrivate::endEditBlock (this=) at text/qtextdocument_p.cpp:1179 #15 0x7ffabba2b9fa in QTextCursor::endEditBlock (this=this@entry=0x7ffcdca5dc00) at text/qtextcursor.cpp:2504 #16 0x7ffabc0b42fe in QWidgetTextControlPrivate::append (this=0x56478c0bda60, text=..., format=format@entry=Qt::AutoText) at widgets/qwidgettextcontrol.cpp:3100 #17 0x7ffabc0b438e in QWidgetTextControl::append (this=, text=...) at widgets/qwidgettextcontrol.cpp:3106 #18 0x7ffabc091b59 in QTextEdit::append (this=, text=...) at widgets/qtextedit.cpp:2568 #19 0x56478ac98b2d in ?? () #20 0x7ffabb5c7bec in QtPrivate::QSlotObjectBase::call (a=0x7ffcdca5ddf0, r=0x56478c0c8610, this=) at ../../includ
[kwin] [Bug 372109] New: kwin_x11 crashes while minimizing/maximizing Firefox window
https://bugs.kde.org/show_bug.cgi?id=372109 Bug ID: 372109 Summary: kwin_x11 crashes while minimizing/maximizing Firefox window Product: kwin Version: 5.7.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ken20...@ukr.net Target Milestone: --- Application: kwin_x11 (5.7.5) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.8.0-26-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: - What I was doing when the application crashed: kwin_x11 crashes while when I'm doing some changes to Firefox window, for example minimizing/maximizing it. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9bef5ad940 (LWP 23982))] Thread 6 (Thread 0x7f9bc1023700 (LWP 24049)): #0 0x7f9bef0a6ea3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9becf28caf in qt_safe_select (nfds=56, fdread=fdread@entry=0x7f9bb8000a78, fdwrite=fdwrite@entry=0x7f9bb8000d08, fdexcept=fdexcept@entry=0x7f9bb8000f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7f9becf2a754 in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f9bb8000f98, writefds=0x7f9bb8000d08, readfds=0x7f9bb8000a78, nfds=, this=0x7f9bb80008c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f9bb80008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7f9becf2ac6a in QEventDispatcherUNIX::processEvents (this=0x7f9bb80008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7f9beced50fa in QEventLoop::exec (this=this@entry=0x7f9bc1022c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f9beccfad43 in QThread::exec (this=) at thread/qthread.cpp:500 #7 0x7f9be77abc65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f9beccffc68 in QThreadPrivate::start (arg=0x55ca9c9b00d0) at thread/qthread_unix.cpp:341 #9 0x7f9be864d70a in start_thread (arg=0x7f9bc1023700) at pthread_create.c:333 #10 0x7f9bef0b10af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f9bc0822700 (LWP 23993)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9bec094574 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f9bec0945b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f9be864d70a in start_thread (arg=0x7f9bc0822700) at pthread_create.c:333 #4 0x7f9bef0b10af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f9bc1824700 (LWP 23991)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9bcda3f4d3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #2 0x7f9bcda3ec17 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #3 0x7f9be864d70a in start_thread (arg=0x7f9bc1824700) at pthread_create.c:333 #4 0x7f9bef0b10af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f9bcf10a700 (LWP 23990)): #0 0x7f9becf2a934 in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f9bbc0008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:186 #1 0x7f9becf2ac6a in QEventDispatcherUNIX::processEvents (this=0x7f9bbc0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #2 0x7f9beced50fa in QEventLoop::exec (this=this@entry=0x7f9bcf109c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #3 0x7f9beccfad43 in QThread::exec (this=) at thread/qthread.cpp:500 #4 0x7f9be77abc65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7f9beccffc68 in QThreadPrivate::start (arg=0x55ca9c983d20) at thread/qthread_unix.cpp:341 #6 0x7f9be864d70a in start_thread (arg=0x7f9bcf10a700) at pthread_create.c:333 #7 0x7f9bef0b10af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7f9bd85fc700 (LWP 23987)): #0 0x7f9bef0a6ea3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9becf28caf in qt_safe_select (nfds=4, fdread=fdread@entry=0x7f9bda78, fdwrite=fdwrite@entry=0x7f9bdd08, fdexcept=fdexcept@entry=0x7f9bdf98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7f9becf2a754 in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f9bdf98, writefds=0x7f9bdd08, readfds=0x7f9bda78, nfds=, this=0x7f9bd8c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate
[kwin] [Bug 372109] kwin_x11 crashes while minimizing/maximizing Firefox window
https://bugs.kde.org/show_bug.cgi?id=372109 --- Comment #2 from Eugene --- I don't know, Martin, may be it's some kind of coincidence. But today kwin crashed several times in a row and then it stops. I don't know really by what it was really caused. When It happened first time I've been working with firefox. When it crashed I've pushed firefox button on kickoff panel to minimize it to button but then it crashed again. And so on several times. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372109] kwin_x11 crashes while minimizing/maximizing Firefox window
https://bugs.kde.org/show_bug.cgi?id=372109 --- Comment #3 from Eugene --- Update. I've been configuring a 'Hide Caption Titlebar Plus' Firefox plugin which hides title bar for it and ca add some additional options. May it caused the crash? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 372757] New: Ark segmentation fault trying uncompress rar
https://bugs.kde.org/show_bug.cgi?id=372757 Bug ID: 372757 Summary: Ark segmentation fault trying uncompress rar Product: ark Version: 16.04.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: ken20...@ukr.net CC: rthoms...@gmail.com Target Milestone: --- Trying to unpack rar-archive ARK crashes. Kubuntu 16.10 Kernel 4.9RC6 x86_64 Application: Ark (ark), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8d44201d40 (LWP 9064))] Thread 3 (Thread 0x7f8d39bb3700 (LWP 9066)): #0 0x7f8d4fab9c8d in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f8d4c3cdc60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8d4c389485 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8d4c389974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8d4c389aec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8d503ec4ab in QEventDispatcherGlib::processEvents (this=0x7f8d340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #6 0x7f8d503940fa in QEventLoop::exec (this=this@entry=0x7f8d39bb2cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f8d501b9d43 in QThread::exec (this=this@entry=0x7f8d4e4a0d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500 #8 0x7f8d4e42c575 in QDBusConnectionManager::run (this=0x7f8d4e4a0d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:171 #9 0x7f8d501bec68 in QThreadPrivate::start (arg=0x7f8d4e4a0d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:341 #10 0x7f8d4cac370a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7f8d4faca0af in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f8d4175c700 (LWP 9065)): #0 0x7f8d4fabe0bd in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f8d49d96c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f8d49d988d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f8d43cb3299 in QXcbEventReader::run (this=0x55eef01f8190) at qxcbconnection.cpp:1325 #4 0x7f8d501bec68 in QThreadPrivate::start (arg=0x55eef01f8190) at thread/qthread_unix.cpp:341 #5 0x7f8d4cac370a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f8d4faca0af in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f8d44201d40 (LWP 9064)): [KCrash Handler] #6 0x55eeef6cb1b6 in ?? () #7 0x7f8d503cfe76 in QtPrivate::QSlotObjectBase::call (a=0x7fff28446d10, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #8 QSingleShotTimer::timerEvent (this=0x55eef02f2480) at kernel/qtimer.cpp:310 #9 0x7f8d503c4653 in QObject::event (this=0x55eef02f2480, e=) at kernel/qobject.cpp:1278 #10 0x7f8d50cd18ac in QApplicationPrivate::notify_helper (this=, receiver=0x55eef02f2480, e=0x7fff28446fe0) at kernel/qapplication.cpp:3804 #11 0x7f8d50cd6d4f in QApplication::notify (this=0x7fff28447380, receiver=0x55eef02f2480, e=0x7fff28446fe0) at kernel/qapplication.cpp:3561 #12 0x7f8d503963b0 in QCoreApplication::notifyInternal2 (receiver=0x55eef02f2480, event=event@entry=0x7fff28446fe0) at kernel/qcoreapplication.cpp:1015 #13 0x7f8d503eb3ae in QCoreApplication::sendEvent (event=0x7fff28446fe0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225 #14 QTimerInfoList::activateTimers (this=0x55eef022e5e0) at kernel/qtimerinfo_unix.cpp:637 #15 0x7f8d503eb8d1 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:176 #16 0x7f8d4c3897d7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f8d4c389a40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f8d4c389aec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f8d503ec48f in QEventDispatcherGlib::processEvents (this=0x55eef0234320, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #20 0x7f8d503940fa in QEventLoop::exec (this=this@entry=0x7fff28447230, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #21 0x7f8d5039c90c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1285 #22 0x55eeef6c63f5 in ?? () #23 0x7f8d4f9e23f1 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #24 0x55eeef6c712a in _start () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Placement policy 'Remember'
https://bugs.kde.org/show_bug.cgi?id=15329 Eugene changed: What|Removed |Added CC||ken20...@ukr.net --- Comment #78 from Eugene --- 2023 is on the street, and it is impossible to switch between the windows of Wayland and XWayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Placement policy 'Remember'
https://bugs.kde.org/show_bug.cgi?id=15329 Eugene changed: What|Removed |Added OS|Other |Linux Platform|Mandrake RPMs |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Placement policy 'Remember'
https://bugs.kde.org/show_bug.cgi?id=15329 Eugene changed: What|Removed |Added Version|unspecified |5.26.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 459679] New: distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 Bug ID: 459679 Summary: distorted mouse pointer in Kubuntu 22.10 under wayland Classification: Plasma Product: plasma-wayland-protocols Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ken20...@ukr.net CC: aleix...@kde.org Target Milestone: --- Created attachment 152426 --> https://bugs.kde.org/attachment.cgi?id=152426&action=edit mouse pointer screenshot STEPS TO REPRODUCE 1. Upgrade to Kubuntu 22.10 dev OBSERVED RESULT Look at mouse pointer. It is distorted. See attached screenshot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.19.0-15-generic KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #2 from Eugene --- (In reply to Aleix Pol from comment #1) > It would be useful to get some details as to what could be special to your > system. > > Would you be able to see what's special about it? This is not something we > (I?) have seen before. > > Some ideas: > Can you reproduce this on 22.04? How about on another distro like Fedora? > Note that to test them you can generally just boot into their live images on > USB, no need to go all the way. > What graphics card and drivers are you using? > Do you get any outstanding error messages in > ~/.?local/share/sddm/wayland-session.log Hello, Aleix. How can I reproduce it if it happened only once I upgraded to 22.10 from 22.04? This is new to me also. I never experienced such before. And I am sorry, I forgot to specify my adapter: $ lspci | grep -i vga 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 XT [Radeon HD 4670] Log is empty: ~/.local/share/sddm$ ls -lh загалом 0 -rw--- 1 eugene eugene 0 вер 27 10:20 wayland-session.log -rw--- 1 eugene eugene 0 вер 25 02:52 xorg-session.log I will try Fedora ASAP. Thanks you for your answer. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #3 from Eugene --- P.S. I am using distro drivers. There is No any additional vendor drivers installations. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 Eugene changed: What|Removed |Added Version|unspecified |5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #4 from Eugene --- I checked Fedora KDE 37 Beta. And the mouse pointer looks the same (screenshot attached). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #5 from Eugene --- Created attachment 152481 --> https://bugs.kde.org/attachment.cgi?id=152481&action=edit mouse pointer in Fedora 37 beta -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #6 from Eugene --- For any additional info, please, ask. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #7 from Eugene --- $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: X.Org (0x1002) Device: AMD RV730 (DRM 2.50.0 / 5.19.0-15-generic, LLVM 15.0.1) (0x9490) Version: 22.2.0 Accelerated: yes Video memory: 1024MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 Memory info (GL_ATI_meminfo): VBO free memory - total: 1023 MB, largest block: 1023 MB VBO free aux. memory - total: 1021 MB, largest block: 1021 MB Texture free memory - total: 1023 MB, largest block: 1023 MB Texture free aux. memory - total: 1021 MB, largest block: 1021 MB Renderbuffer free memory - total: 1023 MB, largest block: 1023 MB Renderbuffer free aux. memory - total: 1021 MB, largest block: 1021 MB Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 1024 MB Total available memory: 2045 MB Currently available dedicated video memory: 1023 MB OpenGL vendor string: X.Org OpenGL renderer string: AMD RV730 (DRM 2.50.0 / 5.19.0-15-generic, LLVM 15.0.1) OpenGL core profile version string: 3.3 (Core Profile) Mesa 22.2.0 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 3.0 Mesa 22.2.0 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.0 Mesa 22.2.0 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Save and remember positions of all windows
https://bugs.kde.org/show_bug.cgi?id=15329 --- Comment #83 from Eugene --- (In reply to Nate Graham from comment #82) > FWIW, as a workaround while this feature remains unimplemented, you should > be able to use Window Rules on Wayland to manually force windows to appear > where you want them. I would be very appreciate if you would show working window rules for Telegram window to always appear in upper right screen corner on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #8 from Eugene --- Created attachment 152566 --> https://bugs.kde.org/attachment.cgi?id=152566&action=edit dmesg -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #9 from Eugene --- Created attachment 152567 --> https://bugs.kde.org/attachment.cgi?id=152567&action=edit syslog -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 Eugene changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #10 from Eugene --- https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1990783 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456306] Wayland-exclusive mouse cursor graphical artifacts
https://bugs.kde.org/show_bug.cgi?id=456306 Eugene changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #8 from Eugene --- There is screenshot in duplicated report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460510] New: Desktop settings drops to default after reboot or session switch
https://bugs.kde.org/show_bug.cgi?id=460510 Bug ID: 460510 Summary: Desktop settings drops to default after reboot or session switch Classification: Plasma Product: plasmashell Version: 5.26.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: eugene.bee...@yandex.ru CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460510] Desktop settings drops to default after reboot or session switch
https://bugs.kde.org/show_bug.cgi?id=460510 --- Comment #2 from Eugene --- hello! 1) My hardware is ASUS Laptop with hybrid Intel HD4600/NV-GTX-850M graphics. 2) I'm using only one screen, only one desktop 3) Yes, wallpaper settings, all widgets disappear and all icons set to default size and positions. Nothing else was noticed On 10/16/22 06:13, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=460510 > > Nate Graham changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > CC||n...@kde.org > Severity|critical|normal > > --- Comment #1 from Nate Graham --- > Thanks for the bug report, but I'm afraid we're going to need more information > to debug it. Can you answer the following questions: > > 1. What is your hardware setup like? > 2. How many screens are you using? > 3. What exactly resets to the default? The wallpaper, widgets, and desktop > icon > positions? Or something else? > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460510] Desktop settings drops to default after reboot or session switch
https://bugs.kde.org/show_bug.cgi?id=460510 --- Comment #4 from Eugene --- Got it. Thank you, sir! Wish you good luck! On 10/17/22 22:19, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=460510 > > Nate Graham changed: > > What|Removed |Added > > Resolution|WAITINGFORINFO |DUPLICATE > Status|NEEDSINFO |RESOLVED > > --- Comment #3 from Nate Graham --- > Unfortunately this very annoying issue is impossible to truly fix with the > current broken-by-design system of mapping containments to screens. We are > rewriting it to work properly in Plasma 5.27. My apologies this happened, and > hopefully issues of this nature will finally be completely fixed for good in > Plasma 5.27. > > *** This bug has been marked as a duplicate of bug 450068 *** > -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 483638] TAB key not functional inside rdp windows client
https://bugs.kde.org/show_bug.cgi?id=483638 --- Comment #8 from eugene --- Manjaro Linux Testing ver. 24.0.2 + KDE 6.05 + KRDC 24.05.0-1: tab key still doesn't work in remote system window. The last working version of krdc is 23.08 :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488465] Plasma crashes after reinstalling the video driver
https://bugs.kde.org/show_bug.cgi?id=488465 --- Comment #1 from Eugene --- Created attachment 170482 --> https://bugs.kde.org/attachment.cgi?id=170482&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.
[plasmashell] [Bug 488465] New: Plasma crashes after reinstalling the video driver
https://bugs.kde.org/show_bug.cgi?id=488465 Bug ID: 488465 Summary: Plasma crashes after reinstalling the video driver Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: e.kolodin...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.0.5) Qt Version: 6.7.1 Frameworks Version: 6.3.0 Operating System: Linux 6.9.4-arch1-1 x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 6.0.5 [CoredumpBackend] -- Information about the crash: After deleting the Nvidia driver files and reinstalling the driver, when I hovered the mouse over any icon in the panel, the icon disappeared. A new icon also appeared next to the volume control; after clicking on it, a window for selecting graphics acceleration opened. In automatic mode, software acceleration was always turned on. After forcing hardware acceleration, crashes began. How can I call up the graphics acceleration selection window to select other options? The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #6 0x723a1cca8eb3 in __pthread_kill_internal (threadid=, signo=6) at pthread_kill.c:78 #7 0x723a1cc50a30 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x723a1cc384c3 in __GI_abort () at abort.c:79 #9 0x723a1fb346e4 in wl_abort (fmt=fmt@entry=0x723a1fb397f0 "Tried to add event to destroyed queue\n") at ../wayland-1.23.0/src/wayland-util.c:476 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 483638] TAB key not functional inside rdp windows client
https://bugs.kde.org/show_bug.cgi?id=483638 eugene changed: What|Removed |Added CC||eug...@zvyagintsev.com --- Comment #2 from eugene --- Manjaro Linux, krdc 24.02 + freerdp2, tab key doesn't work in remote system window. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445960] New: Hover and focus colors applied inconsistently throughout different widgets
https://bugs.kde.org/show_bug.cgi?id=445960 Bug ID: 445960 Summary: Hover and focus colors applied inconsistently throughout different widgets Product: systemsettings Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: bertyf...@gmail.com CC: jpwhit...@kde.org, mwoehlke.fl...@gmail.com Target Milestone: --- SUMMARY I've been playing with the color scheme editor, tweaking colors for better accessibility, and have found that Push buttons and comboboxes misuse Selection color for all their states, while checkboxes and radios misuse Focus color for the hover state. I understand that this component may not be the right place for this report, but I really don't know where else to place it. STEPS TO REPRODUCE 1. Set Selection Background to blue, Focus Decoration to green, Hover Decoration to red. 2. Hover over different widgets in the Application Style settings. 3. ... OBSERVED RESULT Radio button and checkbox on hover: green Push button and Combo box on hover: blue Push button and Combo box on focus: blue EXPECTED RESULT Radio button and checkbox on hover: red Push button and Combo box on hover: red Push button and Combo box on focus: green SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445964] New: A gap between the panel and a maximized window at 200% scale
https://bugs.kde.org/show_bug.cgi?id=445964 Bug ID: 445964 Summary: A gap between the panel and a maximized window at 200% scale Product: plasmashell Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bertyf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 143858 --> https://bugs.kde.org/attachment.cgi?id=143858&action=edit Plasma desktop in default configuration SUMMARY There is a visible line of background between the panel and a maximized window when Display scaling is used. STEPS TO REPRODUCE 1. Set Global scale to 200%. 2. Set background color to red. 3. Maximize a window. OBSERVED RESULT A gap between the panel and the window. EXPECTED RESULT No gap. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Graphics Platform: X11 Graphics Processor: Mesa Intel® HD Graphics 530 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 445960] Hover and focus colors applied inconsistently throughout different widgets
https://bugs.kde.org/show_bug.cgi?id=445960 Eugene changed: What|Removed |Added Product|systemsettings |Breeze Component|kcm_colors |general --- Comment #1 from Eugene --- I'm refiling this to Breeze, as colors work as intended in the Oxygen theme. I need to mention also that the plasma widgets also misuse the colors, in the Breeze theme which should follow the color scheme most widgets just use Selection color for all states. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391956] Maximized windows too small when scaling is applied on X11
https://bugs.kde.org/show_bug.cgi?id=391956 --- Comment #17 from Eugene --- While the issue is present with the Breeze and Plastik themes, the Oxygen window decorations step around it somehow, I've tested with multiple apps and it just works. -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 446207] New: Regression: Missing toolbar actions
https://bugs.kde.org/show_bug.cgi?id=446207 Bug ID: 446207 Summary: Regression: Missing toolbar actions Product: kfontview Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bertyf...@gmail.com Target Milestone: --- SUMMARY I've noticed a regression in functions recently, previously available toolbar buttons like Change text, Unicode block selector, zoom in/out are missing. STEPS TO REPRODUCE 1. Open the Font Viewer 2. Look at the toolbar 3. OBSERVED RESULT Toolbar buttons like Change text, Unicode block selector, zoom in/out are missing. EXPECTED RESULT Toolbar buttons like Change text, Unicode block selector, zoom in/out are present. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-2-MANJARO (64-bit) Graphics Platform: X11 Graphics Processor: Mesa Intel® HD Graphics 530 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 446509] New: Still not working import from discogs (loads nothing)
https://bugs.kde.org/show_bug.cgi?id=446509 Bug ID: 446509 Summary: Still not working import from discogs (loads nothing) Product: kid3 Version: 3.8.x Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: mteug...@gmail.com Target Milestone: --- OS MOJAVE 10.14.6 (18G103) but same trouble was on latest version of macOS -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 446509] Still not working import from discogs (loads nothing)
https://bugs.kde.org/show_bug.cgi?id=446509 Eugene changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Eugene --- thank you so much! it's working! -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start
https://bugs.kde.org/show_bug.cgi?id=408468 Eugene changed: What|Removed |Added Summary|[Wayland] Yakuake on|[Wayland] Yakuake on |Wayland always appears |Wayland appears under top |under top panel |panel at start -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start
https://bugs.kde.org/show_bug.cgi?id=408468 Eugene changed: What|Removed |Added Version|3.0.5 |21.08.1 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start
https://bugs.kde.org/show_bug.cgi?id=408468 --- Comment #24 from Eugene --- On 21.08.1 bug is still present. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start
https://bugs.kde.org/show_bug.cgi?id=408468 --- Comment #31 from Eugene --- It is not fixed still. So, please, do not mislead anyone. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 Eugene changed: What|Removed |Added CC||ken20...@ukr.net --- Comment #16 from Eugene --- A am also for that! Please, bring the cube back! -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 426542] New: [wayland] Yakuake window appears background of the task bar on first F12 hotkey pressing
https://bugs.kde.org/show_bug.cgi?id=426542 Bug ID: 426542 Summary: [wayland] Yakuake window appears background of the task bar on first F12 hotkey pressing Product: yakuake Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: ken20...@ukr.net Target Milestone: --- Created attachment 131660 --> https://bugs.kde.org/attachment.cgi?id=131660&action=edit Yakuake window overlapped by task bar SUMMARY Yakuake window on Wayland appears background of the task bar on first F12 press. Task bar overlaps it. STEPS TO REPRODUCE 1. Launch yakuake app. 2. Press F12 to bring up the application window OBSERVED RESULT Yakuake window appears background of the task bar on first F12 press. Thereby a command prompt is not visible because task bat overlaps it. If push F12 to hide the yakuake window and push F12 again to make it visible, now all is ok - yakuake appears foreground as it should always be. SOFTWARE/OS VERSIONS Linux: 5.8.9 x86_64 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Kubuntu 20.10 (development branch) Yakuake: 20.08.1 Please look at screenshot in attachment. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 385882] Yakuake Wayland: when launching Yakuake the second time it appears in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=385882 Eugene changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #11 from Eugene --- Currently it is not appears in the middle but overlapped by task bar. Created another one report. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 427224] New: baloo_file crashed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=427224 Bug ID: 427224 Summary: baloo_file crashed unexpectedly Product: frameworks-baloo Version: 5.74.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: stefan.bru...@rwth-aachen.de Reporter: ken20...@ukr.net Target Milestone: --- SUMMARY Just did serfing in browser when crash happened. Application: baloo_file (baloo_file), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7fad774eb864 in __GI_abort () at abort.c:79 #6 0x7fad769c1a83 in mdb_assert_fail (env=0x564c00f642f0, expr_txt=expr_txt@entry=0x7fad769c419b "pglast <= env->me_pglast", func=func@entry=0x7fad769c4940 <__func__.7464> "mdb_freelist_save", line=line@entry=3155, file=0x7fad769c4010 "mdb.c") at mdb.c:1542 #7 0x7fad769bf205 in mdb_freelist_save (txn=0x564c00f656b0) at mdb.c:3108 #8 mdb_txn_commit (txn=0x564c00f656b0) at mdb.c:3643 #9 0x7fad77f3fabb in Baloo::Transaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #10 0x564bff7a20ae in ?? () #11 0x7fad77aac812 in QThreadPoolThread::run (this=0x564c00f9d190) at thread/qthreadpool.cpp:99 #12 0x7fad77aa8a41 in QThreadPrivate::start (arg=0x564c00f9d190) at thread/qthread_unix.cpp:342 #13 0x7fad76a24590 in start_thread (arg=0x7fad725ad640) at pthread_create.c:463 #14 0x7fad775de223 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 #1 0x7fad7624772e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fad76247863 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fad77ce185b in QEventDispatcherGlib::processEvents (this=0x7fad6c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fad77c88a4b in QEventLoop::exec (this=this@entry=0x7fad730bfcb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7fad77aa78b2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7fad77f6d4cb in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fad77aa8a41 in QThreadPrivate::start (arg=0x7fad77fdbda0) at thread/qthread_unix.cpp:342 #8 0x7fad76a24590 in start_thread (arg=0x7fad730c0640) at pthread_create.c:463 #9 0x7fad775de223 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 #1 0x7fad7624772e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fad76247863 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fad77ce1843 in QEventDispatcherGlib::processEvents (this=0x564c00f4a530, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7fad77c88a4b in QEventLoop::exec (this=this@entry=0x7ffea0cb91f0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7fad77c90fc6 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x564bff796cc0 in ?? () #7 0x7fad774edcb2 in __libc_start_main (main=0x564bff796a70, argc=1, argv=0x7ffea0cb9578, init=, fini=, rtld_fini=, stack_end=0x7ffea0cb9568) at ../csu/libc-start.c:314 #8 0x564bff796ebe in ?? () [Inferior 1 (process 49901) detached] SOFTWARE/OS VERSIONS Linux: 5.8.12 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Kubuntu 20.10 (development branch) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland always appears under top panel
https://bugs.kde.org/show_bug.cgi?id=408468 Eugene changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #15 from Eugene --- It is not fixed fully as it should be. First appearing of Yakuake is still occurs behind taskbar and only from second call of Yakuake it appears correctly. Similar report: https://bugs.kde.org/show_bug.cgi?id=426542 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland always appears under top panel
https://bugs.kde.org/show_bug.cgi?id=408468 --- Comment #17 from Eugene --- (In reply to Nate Graham from comment #16) > What versions of Yakuake and Plasma are you using? Hello, Nate. Yakuake: 20.08.1 Plasma KDE: 5.19.5 Frameworks KDE: 5.74.0 QT: 5.14.2 Linux: 5.8.0-20-generic Kubuntu 20.10 (development branch) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland always appears under top panel
https://bugs.kde.org/show_bug.cgi?id=408468 Eugene changed: What|Removed |Added Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- --- Comment #20 from Eugene --- (In reply to Nate Graham from comment #19) > Darn. I wonder if this requires Plasma 5.20 stuff. Can you test with that, > if possible? It's a pity but there is no packages of Plasma 5.20 for Kubuntu 20.10, so I am not able to test with that. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland always appears under top panel
https://bugs.kde.org/show_bug.cgi?id=408468 Eugene changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 427505] New: kdeinit5 Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=427505 Bug ID: 427505 Summary: kdeinit5 Segmentation fault Product: frameworks-kinit Version: 5.74.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: ken20...@ukr.net CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Kdeinit5 crashed unexpectedly during usual working in system. Application: kdeinit5 (kdeinit5), signal: Segmentation fault [KCrash Handler] #4 0x7f8b88c68347 in XAddExtension (dpy=dpy@entry=0x55e7737a91b0) at ../../src/InitExt.c:73 #5 0x7f8b5492d7bd in _XftDisplayInfoGet (createIfNecessary=1, dpy=0x55e7737a91b0) at ../../src/xftdpy.c:91 #6 _XftDisplayInfoGet (dpy=dpy@entry=0x55e7737a91b0, createIfNecessary=createIfNecessary@entry=1) at ../../src/xftdpy.c:62 #7 0x7f8b5493235e in XftFontInfoFill (dpy=dpy@entry=0x55e7737a91b0, pattern=pattern@entry=0x55e773bae480, fi=fi@entry=0x7ffc03d021b0) at ../../src/xftfreetype.c:367 #8 0x7f8b54932c23 in XftFontOpenPattern (dpy=0x55e7737a91b0, pattern=0x55e773bae480) at ../../src/xftfreetype.c:1015 #9 0x7f8b7806d9bc in KFI::CFcEngine::getFont (this=this@entry=0x55e7737dc8a8, size=size@entry=8) at ./kcms/kfontinst/lib/FcEngine.cpp:1299 #10 0x7f8b7806de18 in KFI::CFcEngine::queryFont (this=this@entry=0x55e7737dc8a8) at ./kcms/kfontinst/lib/FcEngine.cpp:1233 #11 0x7f8b7806e5e8 in KFI::CFcEngine::getSizes (this=0x55e7737dc8a8) at ./kcms/kfontinst/lib/FcEngine.cpp:1391 #12 KFI::CFcEngine::getSizes (this=0x55e7737dc8a8) at ./kcms/kfontinst/lib/FcEngine.cpp:1383 #13 0x7f8b7806fc10 in KFI::CFcEngine::draw (this=this@entry=0x55e7737dc8a8, name=..., style=style@entry=4294967295, faceNo=faceNo@entry=0, txt=..., bgnd=..., w=128, h=128, thumb=true, range=..., chars=0x0) at ./kcms/kfontinst/lib/FcEngine.cpp:876 #14 0x7f8b78078a0c in KFI::CFontThumbnail::create (this=this@entry=0x55e7737dc8a0, path=..., width=width@entry=128, height=128, img=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qscopedpointer.h:116 #15 0x7f8b88df1715 in ThumbnailProtocol::get (this=0x7ffc03d02870, url=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:118 #16 0x7f8b842dc36e in KIO::SlaveBase::dispatch (this=0x7ffc03d02870, command=67, data=...) at ./src/core/slavebase.cpp:1193 #17 0x7f8b842dcc56 in KIO::SlaveBase::dispatchLoop (this=0x7ffc03d02870) at ./src/core/slavebase.cpp:325 #18 0x7f8b88def774 in kdemain (argc=, argv=0x55e773785790) at ./thumbnail/thumbnail.cpp:138 #19 0x55e771944a5e in launch (argc=4, _name=0x55e7737853d8 "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so", args=0x55e773785484 "", cwd=, envc=0, envs=, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x55e771948187 "0") at ./src/kdeinit/kinit.cpp:696 #20 0x55e771945e71 in handle_launcher_request (sock=8, who=) at ./src/kdeinit/kinit.cpp:1134 #21 0x55e77194661c in handle_requests (waitForPid=0) at ./src/kdeinit/kinit.cpp:1327 #22 0x55e7719420ef in main (argc=3, argv=0x7ffc03d02e80) at ./src/kdeinit/kinit.cpp:1765 [Inferior 1 (process 93688) detached] SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux: 5.8.0-21 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Kubuntu 20.10 (development branch) (wayland session) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 427505] kdeinit5 Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=427505 Eugene changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 424630] Unable to create io-slave: Error loading /usr/local/lib/qt5/plugins/kf5/kio/gdrive.so
https://bugs.kde.org/show_bug.cgi?id=424630 Eugene changed: What|Removed |Added CC||ken20...@ukr.net --- Comment #7 from Eugene --- Created attachment 139924 --> https://bugs.kde.org/attachment.cgi?id=139924&action=edit Dolphin error -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 424630] Unable to create io-slave: Error loading /usr/local/lib/qt5/plugins/kf5/kio/gdrive.so
https://bugs.kde.org/show_bug.cgi?id=424630 --- Comment #8 from Eugene --- Greetings. I have the same issue with version 21.04.2 on Kubuntu 21.04. Plasma 5.22.3 Frameworks 5.83.0 Qt 5.15.2 $ LANG=C kioclient5 exec gdrive:/ kf.kio.core: couldn't create slave: "klauncher said: Помилка під час завантаження «/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so»." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436180] New: Plasma crashed during keyboard layout switching
https://bugs.kde.org/show_bug.cgi?id=436180 Bug ID: 436180 Summary: Plasma crashed during keyboard layout switching Product: plasmashell Version: 5.21.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ken20...@ukr.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.21.4) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.11.0-16-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: I just switched keyboard layout several times when crash happened. The crash does not seem to be reproducible. -- Backtrace: Application: Плазма (plasmashell), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f2dd70f7864 in __GI_abort () at abort.c:79 #6 0x7f2dd715a736 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f2dd727f953 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:155 #7 0x7f2dd71f93fa in __GI___fortify_fail (msg=msg@entry=0x7f2dd727f93b "stack smashing detected") at fortify_fail.c:26 #8 0x7f2dd71f93c6 in __stack_chk_fail () at stack_chk_fail.c:24 #9 0x7f2dc832d209 in ?? () from /lib/x86_64-linux-gnu/libKF5ItemModels.so.5 #10 0x7f2dd77c6b44 in doActivate (sender=0x55d5ba06c950, signal_index=3, argv=argv@entry=0x7fffeec8ac90) at kernel/qobject.cpp:3898 #11 0x7f2dd77bfcb8 in QMetaObject::activate (sender=sender@entry=0x55d5ba06c950, m=m@entry=0x7f2dd7a27640 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffeec8ac90) at kernel/qobject.cpp:3946 #12 0x7f2dd7728459 in QAbstractItemModel::dataChanged (this=this@entry=0x55d5ba06c950, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #13 0x7f2dc8301ee8 in StatusNotifierModel::dataUpdated (this=0x55d5ba06c950, sourceName=..., data=...) at ./applets/systemtray/systemtraymodel.cpp:442 #14 0x7f2dd77c6b44 in doActivate (sender=0x55d5b9feacc0, signal_index=3, argv=0x7fffeec8ae70) at kernel/qobject.cpp:3898 #15 0x7f2dd962461b in Plasma::DataContainer::dataUpdated(QString const&, QMap const&) () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #16 0x7f2dd9624f40 in Plasma::DataContainer::checkForUpdate() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #17 0x7f2d8c12d3af in StatusNotifierItemSource::refreshCallback (this=, call=) at ./dataengines/statusnotifieritem/statusnotifieritemsource.cpp:382 #18 0x7f2dd77c6b0e in QtPrivate::QSlotObjectBase::call (a=0x7fffeec8b0f0, r=0x55d5b9feacc0, this=0x7f2dcc02a440) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate (sender=0x55d5bbd0c0f0, signal_index=3, argv=0x7fffeec8b0f0) at kernel/qobject.cpp:3886 #20 0x7f2dd81676f3 in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #21 0x7f2dd77bc2a1 in QObject::event (this=0x55d5bbd0c0f0, e=0x7f2dc4069c40) at kernel/qobject.cpp:1314 #22 0x7f2dd8453173 in QApplicationPrivate::notify_helper (this=, receiver=0x55d5bbd0c0f0, e=0x7f2dc4069c40) at kernel/qapplication.cpp:3632 #23 0x7f2dd778f22a in QCoreApplication::notifyInternal2 (receiver=0x55d5bbd0c0f0, event=0x7f2dc4069c40) at kernel/qcoreapplication.cpp:1063 #24 0x7f2dd7791d01 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55d5b8cae320) at kernel/qcoreapplication.cpp:1817 #25 0x7f2dd77e8f37 in postEventSourceDispatch (s=0x55d5b8d93440) at kernel/qeventdispatcher_glib.cpp:277 #26 0x7f2dd5b5d84b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f2dd5bb0c68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f2dd5b5af83 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f2dd77e8594 in QEventDispatcherGlib::processEvents (this=0x55d5b8d9d150, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #30 0x7f2dd778db8b in QEventLoop::exec (this=this@entry=0x7fffeec8b4c0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #31 0x7f2dd7796024 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #32 0x55d5b899ae5e in main (argc=, argv=0x7fffeec8b630) at ./shell/main.cpp:251 [Inferior 1 (process 1394) detached] Possible duplicates by query: bug 436129, bug 436072, bug 436021, bug 435760, bug 435008. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436180] Plasma crashed during keyboard layout switching
https://bugs.kde.org/show_bug.cgi?id=436180 --- Comment #1 from Eugene --- Recently checked: it crashes again and again. Just need to switch layouts again and again several times. I am using three layouts (English, Russian, Ukrainian). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436180] Plasma crashed during keyboard layout switching
https://bugs.kde.org/show_bug.cgi?id=436180 --- Comment #4 from Eugene --- I am sorry but I am not able to reproduce it currently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436180] Plasma crashed during keyboard layout switching
https://bugs.kde.org/show_bug.cgi?id=436180 --- Comment #5 from Eugene --- (In reply to Andrey from comment #3) > How do you switching the layout - using old SNI widget in systray, using > "main" shortcut set in Keyboard KCM, "additional" shortcut there, or using > the shortcut specific for that particular layout? > Does it also happens with disabled keyboard layout indicator in the Keyboard > KCM? > Could you also try to reproduce on Wayland session? My layout is usually changing through Alt+Shift hotkey. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436180] Plasma crashed during keyboard layout switching
https://bugs.kde.org/show_bug.cgi?id=436180 Eugene changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #8 from Eugene --- (In reply to Konrad Materka from comment #6) > can you install additional debug symbols? > sudo apt install libkf5itemmodels5-dbgsym > > You crash report is missing line number: > #9 0x7f2dc832d209 in ?? () from > /lib/x86_64-linux-gnu/libKF5ItemModels.so.5 Unfortunately I am not able to reproduce this crash. I tried several times. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436988] New: Dolphin crashes while attempting to create a folder in GoogleDrive
https://bugs.kde.org/show_bug.cgi?id=436988 Bug ID: 436988 Summary: Dolphin crashes while attempting to create a folder in GoogleDrive Product: dolphin Version: 20.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ken20...@ukr.net CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.3) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.12.2-051202-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: I entered a folder in Google Drive and tried to create a subfolder when Dolphin crashed. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0xf78948f574f68548) at /usr/include/c++/10/bits/atomic_base.h:420 #5 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0xf78948f574f68548) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::ref (this=0xf78948f574f68548) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #8 QString::QString (other=..., this=0x7fff1e5ac968) at ../../include/QtCore/../../src/corelib/text/qstring.h:1094 #9 QWidgetLineControl::text (this=0x7f8dc1965bc0 , void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)>) at ../../include/QtWidgets/5.15.2/QtWidgets/private/../../../../../src/widgets/widgets/qwidgetlinecontrol_p.h:241 #10 QLineEdit::text (this=) at widgets/qlineedit.cpp:312 #11 0x7f8dc1587e58 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5 #12 0x7f8dbf74bb0e in QtPrivate::QSlotObjectBase::call (a=0x7fff1e5acb40, r=0x55a527d76e50, this=0x55a5289e5760) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x55a528b528d0, signal_index=6, argv=0x7fff1e5acb40) at kernel/qobject.cpp:3886 #14 0x7f8dc09024a0 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #15 0x7f8dc09073bb in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #16 0x7f8dbf74bb0e in QtPrivate::QSlotObjectBase::call (a=0x7fff1e5acc80, r=0x55a528b528d0, this=0x55a52858a800) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate (sender=0x55a5287235d0, signal_index=5, argv=0x7fff1e5acc80) at kernel/qobject.cpp:3886 #18 0x7f8dc109cbaa in KIO::SlaveInterface::error(int, QString const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #19 0x7f8dc109ecf7 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #20 0x7f8dc109d30d in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #21 0x7f8dc10a1c92 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #22 0x7f8dbf74bb0e in QtPrivate::QSlotObjectBase::call (a=0x7fff1e5acec0, r=0x55a5287235d0, this=0x55a528b71e80) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #23 doActivate (sender=0x55a528925b00, signal_index=3, argv=0x7fff1e5acec0) at kernel/qobject.cpp:3886 #24 0x7f8dbf7412a1 in QObject::event (this=0x55a528925b00, e=0x55a5287e7210) at kernel/qobject.cpp:1314 #25 0x7f8dc01f1173 in QApplicationPrivate::notify_helper (this=, receiver=0x55a528925b00, e=0x55a5287e7210) at kernel/qapplication.cpp:3632 #26 0x7f8dbf71422a in QCoreApplication::notifyInternal2 (receiver=0x55a528925b00, event=0x55a5287e7210) at kernel/qcoreapplication.cpp:1063 #27 0x7f8dbf716d01 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55a527a9c890) at kernel/qcoreapplication.cpp:1817 #28 0x7f8dbf76df37 in postEventSourceDispatch (s=0x55a527b89ac0) at kernel/qeventdispatcher_glib.cpp:277 #29 0x7f8dbd57584b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f8dbd5c8c68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f8dbd572f83 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7f8dbf76d594 in QEventDispatcherGlib::processEvents (this=0x55a527b8ee80, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #33 0x7f8dbf712b8b in QEventLoop::exec (this=this@entry=0x7fff1e5ad2b0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #34 0x7f8dbf71b024 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #35 0x7f8dc1953570 in
[dolphin] [Bug 436988] Dolphin crashes while attempting to create a folder in Google Drive
https://bugs.kde.org/show_bug.cgi?id=436988 Eugene changed: What|Removed |Added Summary|Dolphin crashes while |Dolphin crashes while |attempting to create a |attempting to create a |folder in GoogleDrive |folder in Google Drive -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 425189] New: krunner crashed while trying to lunch Firefox
https://bugs.kde.org/show_bug.cgi?id=425189 Bug ID: 425189 Summary: krunner crashed while trying to lunch Firefox Product: krunner Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: ken20...@ukr.net CC: plasma-b...@kde.org Target Milestone: --- Application: krunner (5.18.5) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.8.0-050800-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Just tried to launch Firefox through krunner when it crashed. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x7ffe28584048) at ../sysdeps/nptl/futex-internal.h:183 [Current thread is 1 (Thread 0x7fd17860d800 (LWP 4274))] Thread 18 (Thread 0x7fd12a7fc700 (LWP 4308)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5634a9fcb9b0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5634a9fcb960, cond=0x5634a9fcb988) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5634a9fcb988, mutex=0x5634a9fcb960) at pthread_cond_wait.c:638 #3 0x7fd17c5bbb0f in QWaitConditionPrivate::wait (deadline=..., this=0x5634a9fcb960) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x5634a9fcb5c0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fd17c5bbc01 in QWaitCondition::wait (this=0x5634a9fcb8c8, mutex=0x5634a9fcb5c0, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #6 0x7fd16c020050 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fd16c023d4e in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fd16c01f222 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fd16c023da9 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fd16c01f222 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fd16c021cb3 in ThreadWeaver::Thread::run() () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7fd17c5b59d2 in QThreadPrivate::start (arg=0x7fd1140056f0) at thread/qthread_unix.cpp:361 #13 0x7fd17b900609 in start_thread (arg=) at pthread_create.c:477 #14 0x7fd17c244103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fd12affd700 (LWP 4307)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fd17c5b5c75 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=3, op=0, addr=0x5634aa31f250) at thread/qfutex_p.h:105 #2 QtLinuxFutex::futexWait > (expectedValue=0x3, futex=...) at thread/qfutex_p.h:107 #3 lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at thread/qmutex_linux.cpp:142 #4 QBasicMutex::lockInternal (this=0x5634aa31f250) at thread/qmutex_linux.cpp:159 #5 0x7fd17c5b5e6e in QMutex::lock (this=this@entry=0x5634aa31f250) at thread/qmutex.cpp:227 #6 0x7fd14292629b in QMutexLocker::QMutexLocker (m=0x5634aa31f250, this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:206 #7 InstallerRunner::findComponentsByString (this=this@entry=0x5634aa31f220, query=...) at ./runners/appstream/appstreamrunner.cpp:118 #8 0x7fd1429267a1 in InstallerRunner::match (this=0x5634aa31f220, context=...) at ./runners/appstream/appstreamrunner.cpp:85 #9 0x7fd16333f1f8 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () from /lib/x86_64-linux-gnu/libKF5Runner.so.5 #10 0x7fd16335059c in ?? () from /lib/x86_64-linux-gnu/libKF5Runner.so.5 #11 0x7fd16c02345d in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7fd16c022177 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7fd16c021d51 in ThreadWeaver::Thread::run() () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7fd17c5b59d2 in QThreadPrivate::start (arg=0x7fd1140029e0) at thread/qthread_unix.cpp:361 #15 0x7fd17b900609 in start_thread (arg=) at pthread_create.c:477 #16 0x7fd17c244103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fd12b7fe700 (LWP 4306)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7fd17c1
[krunner] [Bug 425189] krunner crashed while trying to lunch Firefox
https://bugs.kde.org/show_bug.cgi?id=425189 --- Comment #2 from Eugene --- (In reply to Alexander Lohnau from comment #1) > Can you reproduce this bug or did it only occur once? Occurred once today first time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429031] New: Black borders around some menus
https://bugs.kde.org/show_bug.cgi?id=429031 Bug ID: 429031 Summary: Black borders around some menus Product: kwin Version: 5.20.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bertyf...@gmail.com Target Milestone: --- Created attachment 133270 --> https://bugs.kde.org/attachment.cgi?id=133270&action=edit Black border around context menu in Dolphin SUMMARY Since the 5.20 release I'm seeing black borders around some menus. STEPS TO REPRODUCE 1. Open Dolphin. 2. Right click at the Menu bar. OBSERVED RESULT The menu has a rectangular black border. EXPECTED RESULT The menu has a usual grey border. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.8.18-1-MANJARO Graphics Processor: Mesa Intel® HD Graphics 530 ADDITIONAL INFORMATION Without compositing everything looks the same. Some other places displaying the same effect: - the hamburger menu in sidebar-style System Settings; - the menubar menu in kwrite, gwenview and other apps where it's applicable; -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Google authentication process gets stuck due to excessively old version of signon-ui library
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #79 from Eugene --- (In reply to Bernie Innocenti from comment #73) > I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from > the Fedora COPR repo "hazel-bunny/ports". > > I confirm it fixes this particular bug: the authentication window renders > and you can type your login and password. > > I still couldn't log into my Google account because it has 2FA enabled and > the webengine doesn't seem to support USB security keys :-( > It seems KDE would be better off switching to gnome-online-accounts or other > actively developed framework. Tried it recently. Now it is stuck on reading the drive after login. :( -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456306] Wayland-exclusive mouse cursor graphical artifacts
https://bugs.kde.org/show_bug.cgi?id=456306 --- Comment #13 from Eugene --- Hello. I can confirm, in KDE 5.26 mouse cursor is ok. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 391442] Can't unlock the session from the first time while it has been locked in VM
https://bugs.kde.org/show_bug.cgi?id=391442 --- Comment #4 from Eugene --- Not actual at the moment. All is ok. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 448542] New: Show active folder and profile in the title
https://bugs.kde.org/show_bug.cgi?id=448542 Bug ID: 448542 Summary: Show active folder and profile in the title Product: krusader Version: 2.7.2 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: bertyf...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY It would be helpful to have this info in the title to better distinguish multiple running instances of the program. I believe both should be optional to account for privacy and single-profile usage. E.g.: 1) [x] Show active folder in the title [] Show active profile in the title "%activefolder% -- Krusader" 2) [] Show active folder in the title [x] Show active profile in the title "[%activeprofile%] -- Krusader" 3) [x] Show active folder in the title [x] Show active profile in the title "%activefolder% -- [%activeprofile%] -- Krusader" -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start
https://bugs.kde.org/show_bug.cgi?id=408468 --- Comment #34 from Eugene --- Interesting thing: under X Yakuake window first time appears above the kickoff panel overlapping it. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start
https://bugs.kde.org/show_bug.cgi?id=408468 Eugene changed: What|Removed |Added Status|ASSIGNED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start
https://bugs.kde.org/show_bug.cgi?id=408468 Eugene changed: What|Removed |Added Version|21.08.1 |21.08.3 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start
https://bugs.kde.org/show_bug.cgi?id=408468 --- Comment #37 from Eugene --- (In reply to trmdi from comment #35) > Can anyone who heavily uses Yakuake test the patch in the comment 32? Recently I tried to compile yakuake with that additional string in patch and it weems it works well. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start
https://bugs.kde.org/show_bug.cgi?id=408468 --- Comment #38 from Eugene --- Created attachment 144772 --> https://bugs.kde.org/attachment.cgi?id=144772&action=edit yakuake compiled with patch -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start
https://bugs.kde.org/show_bug.cgi?id=408468 --- Comment #39 from Eugene --- Anyone can test it now fron attachment. Now how can we pull it in main codebase? I don't understand all thouse programming rules. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start
https://bugs.kde.org/show_bug.cgi?id=408468 --- Comment #42 from Eugene --- At last! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390079] System tray layout indicator does not show chosen layout under Wayland
https://bugs.kde.org/show_bug.cgi?id=390079 --- Comment #8 from Eugene --- (In reply to ruruoli from comment #7) > Any progress on this? Nope.8/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 Eugene changed: What|Removed |Added CC||bertyf...@gmail.com --- Comment #7 from Eugene --- It looks like the GDK_DPI_SCALE variable used to offset the font size isn't being used anymore by GTK4 https://github.com/GNOME/gtk/blob/0579220546f7daff16a907f4c3256098c344e40c/NEWS.pre-4.0#L1308. My workaround is to halve the font size in the settings.ini. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 Eugene changed: What|Removed |Added CC||ken20...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 Eugene changed: What|Removed |Added Version|5.19.4 |5.19.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390079] System tray layout indicator does not show chosen layout under Wayland
https://bugs.kde.org/show_bug.cgi?id=390079 Eugene changed: What|Removed |Added Version|5.17.3 |5.19.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390079] System tray layout indicator does not show chosen layout under Wayland
https://bugs.kde.org/show_bug.cgi?id=390079 Eugene changed: What|Removed |Added Status|ASSIGNED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390079] System tray layout indicator does not show chosen layout under Wayland
https://bugs.kde.org/show_bug.cgi?id=390079 --- Comment #10 from Eugene --- Just moved to Kubuntu 20.10 (dev branch) Plasma: 5.19.5 Frameworks: 5.73.0 QT: 5.14.2 Layout switching is working but it is unknown which layout is active at the moment. Tray indicator still not displaying any useful info. It would be great if it would be fixed till 20.10 release. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426368] New: Plasma crashed while switching between Global Themes
https://bugs.kde.org/show_bug.cgi?id=426368 Bug ID: 426368 Summary: Plasma crashed while switching between Global Themes Product: plasmashell Version: 5.19.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ken20...@ukr.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.5) Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.8.7-050807-generic x86_64 Windowing system: Wayland Distribution: Ubuntu Groovy Gorilla (development branch) -- Information about the crash: - What I was doing when the application crashed: I just switched between Global Themes when plasma crash happened. -- Backtrace: Application: Плазма (plasmashell), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f1688089859 in __GI_abort () at abort.c:79 #6 0x7f16884c7ba3 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffd3909f950, msg=msg@entry=0x7f1683e351c0 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:893 #8 0x7f1683d93084 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlogging.h:90 #9 0x7f1683d930de in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55c14a4eb060) at qwaylanddisplay.cpp:209 #10 0x7f168871a320 in doActivate (sender=0x55c14a5031e0, signal_index=3, argv=0x7ffd3909fa30, argv@entry=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #11 0x7f1688714068 in QMetaObject::activate (sender=sender@entry=0x55c14a5031e0, m=m@entry=0x7f168896f840 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #12 0x7f16886e0b24 in QAbstractEventDispatcher::aboutToBlock (this=this@entry=0x55c14a5031e0) at .moc/moc_qabstracteventdispatcher.cpp:143 #13 0x7f168873b818 in QEventDispatcherGlib::processEvents (this=0x55c14a5031e0, flags=...) at kernel/qeventdispatcher_glib.cpp:410 #14 0x7f16886e2a4b in QEventLoop::exec (this=this@entry=0x7ffd3909fb50, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #15 0x7f16886eafc6 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #16 0x55c14a44684b in main (argc=, argv=) at ./shell/main.cpp:224 [Inferior 1 (process 1206) detached] Possible duplicates by query: bug 425987, bug 425361, bug 424923, bug 424922, bug 424921. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland always appears under top panel
https://bugs.kde.org/show_bug.cgi?id=408468 --- Comment #21 from Eugene --- yakuake 21.04.1 First start it appears in background - under kickoff panel. Double push F12 brings it foreground. So second start looks normal. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland always appears under top panel
https://bugs.kde.org/show_bug.cgi?id=408468 Eugene changed: What|Removed |Added Version Fixed In|20.08.0 | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418699] Keyboard Switching policy Application always shows keyboard change OSD notification on Wayland
https://bugs.kde.org/show_bug.cgi?id=418699 Eugene <30secondtob...@gmail.com> changed: What|Removed |Added CC||30secondtob...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437512] New: The OSD panel is not shown when switching keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=437512 Bug ID: 437512 Summary: The OSD panel is not shown when switching keyboard layouts Product: systemsettings Version: 5.21.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: 30secondtob...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install Manjaro KDE stable 64-bit 2. After starting the operating system, when you press a key combination to switch the keyboard layout (standard, custom), the OSD panel is not displayed. In Manjaro 19 this OSD panel worked 3. I mean the panel as when you press start + space in windows 10 OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437802] New: Plasmashell segmentation fault
https://bugs.kde.org/show_bug.cgi?id=437802 Bug ID: 437802 Summary: Plasmashell segmentation fault Product: plasmashell Version: 5.21.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ken20...@ukr.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.7-051207-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: Just tried to start Krunner while surfing the web and compying some text to clipboard from a web page. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Плазма (plasmashell), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::operator++ (this=0x1) at /usr/include/c++/10/bits/atomic_base.h:325 #5 QAtomicOps::ref (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:283 #6 QBasicAtomicInteger::ref (this=0x1) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:118 #7 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x5582204b2bc0) at tools/qsharedpointer.cpp:1398 #8 0x7f95a61b714a in QV4::QQmlQPointer::init (o=0x5582204b2bc0, this=0x7f957b574698) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/memory/qv4heap_p.h:218 #9 QV4::QQmlQPointer::init (o=0x5582204b2bc0, this=0x7f957b574698) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/memory/qv4heap_p.h:218 #10 QV4::Heap::QObjectWrapper::init (object=0x5582204b2bc0, this=0x7f957b574680) at jsruntime/qv4qobjectwrapper_p.h:83 #11 QV4::MemoryManager::allocate (this=0x55821dbd01b0) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/memory/qv4mm_p.h:245 #12 QV4::QObjectWrapper::create (engine=, object=0x5582204b2bc0) at jsruntime/qv4qobjectwrapper.cpp:694 #13 0x7f95a61b9140 in QV4::QObjectWrapper::wrap_slowPath (engine=0x55821dad0c80, object=0x5582204b2bc0) at jsruntime/qv4qobjectwrapper.cpp:614 #14 0x7f95a61b94a8 in loadProperty (v4=0x55821dad0c80, object=0x55821fc13220, property=...) at jsruntime/qv4qobjectwrapper.cpp:205 #15 0x7f95a61d8611 in QV4::Moth::VME::interpret (frame=0x7ffd5211b330, engine=0x55821dad0c80, code=0x7f956f2835d8 ":\037pL\023. \030\a.!\030\b\024") at jsruntime/qv4vme_moth.cpp:638 #16 0x7f95a61dcc17 in QV4::Moth::VME::exec (frame=frame@entry=0x7ffd5211b330, engine=engine@entry=0x55821dad0c80) at jsruntime/qv4vme_moth.cpp:463 #17 0x7f95a617724d in QV4::Function::call (this=this@entry=0x55821f74edd0, thisObject=, argv=argv@entry=0x7f95881c1500, argc=, context=) at jsruntime/qv4function.cpp:69 #18 0x7f95a62f20c5 in QQmlJavaScriptExpression::evaluate (this=this@entry=0x55821ff458f0, callData=callData@entry=0x7f95881c14d0, isUndefined=isUndefined@entry=0x0) at qml/qqmljavascriptexpression.cpp:212 #19 0x7f95a62a55eb in QQmlBoundSignalExpression::evaluate (this=, a=) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #20 0x7f95a62a5ad0 in QQmlBoundSignal_callback (e=0x55821f7398e0, a=0x0) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmlboundsignalexpressionpointer_p.h:69 #21 0x7f95a62d5b8d in QQmlNotifier::emitNotify (endpoint=, a=0x0) at qml/qqmlnotifier.cpp:104 #22 0x7f95a4d456a5 in doActivate (sender=0x55822027fe60, signal_index=26, argv=argv@entry=0x0) at kernel/qobject.cpp:3778 #23 0x7f95a4d3ecb8 in QMetaObject::activate (sender=sender@entry=0x55822027fe60, m=m@entry=0x7f956ce29480 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #24 0x7f956cdc52b4 in RunnerModel::countChanged (this=this@entry=0x55822027fe60) at ./obj-x86_64-linux-gnu/applets/kicker/kickerplugin_autogen/7RBZBFH7CH/moc_runnermodel.cpp:310 #25 0x7f956cdfe5b8 in RunnerModel::matchesChanged (this=, matches=...) at ./applets/kicker/plugin/runnermodel.cpp:244 #26 0x7f95a4d45b0e in QtPrivate::QSlotObjectBase::call (a=0x7ffd5211d1d0, r=0x55822027fe60, this=0x55821f790730) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #27 doActivate (sender=0x5582200fb250, signal_index=3, argv=argv@entry=0x7ffd5211d1d0) at kernel/qobject.cpp:3886 #28 0x7f95a4d3ecb8 in QMetaObject::activate (sender=sender@entry=0x5582200fb250, m=m@entry=0x7f956cd6b080 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd5211d1d0) at kernel/qobject.cpp:3946 #29 0x7f956cd52a56 in Plasma::RunnerManager::matchesChanged (this=this@entry=0x5582200fb250, _t1=...) at ./obj-x86_64-linux-gnu/src/KF5Runner_autogen/include/moc_runnerman
[kfontview] [Bug 390966] Font preview doesn't scale properly
https://bugs.kde.org/show_bug.cgi?id=390966 Eugene changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Eugene --- This was fixed some time ago and cannot be reproduced as of version 5.20.3. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434260] New: Dolphin segmentation fault while trying to create folder in kio-gdrive
https://bugs.kde.org/show_bug.cgi?id=434260 Bug ID: 434260 Summary: Dolphin segmentation fault while trying to create folder in kio-gdrive Product: dolphin Version: 20.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ken20...@ukr.net CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.3) Qt Version: 5.15.2 Frameworks Version: 5.79.0 Operating System: Linux 5.11.4-051104-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.2 Distribution: Ubuntu Hirsute Hippo (development branch) -- Information about the crash: - What I was doing when the application crashed: Just tried to create a folder in my Google Drive folder connected through Dolphin with kio-gdrive. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 QString::QString (other=..., this=0x7ffea46b6878) at ../../include/QtCore/../../src/corelib/text/qstring.h:1093 #5 QWidgetLineControl::text (this=0x0) at ../../include/QtWidgets/5.15.2/QtWidgets/private/../../../../../src/widgets/widgets/qwidgetlinecontrol_p.h:241 #6 QLineEdit::text (this=) at widgets/qlineedit.cpp:312 #7 0x7f4a80e428fc in ?? () from /lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5 #8 0x7f4a7f059b0e in QtPrivate::QSlotObjectBase::call (a=0x7ffea46b6a50, r=0x558e2d675a60, this=0x558e2e0f3c70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate (sender=0x558e2dedf440, signal_index=6, argv=0x7ffea46b6a50) at kernel/qobject.cpp:3886 #10 0x7f4a80213f20 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #11 0x7f4a80214a9b in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #12 0x7f4a7f059b0e in QtPrivate::QSlotObjectBase::call (a=0x7ffea46b6b90, r=0x558e2dedf440, this=0x558e2e17d3a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x7f4a74008d00, signal_index=5, argv=argv@entry=0x7ffea46b6b90) at kernel/qobject.cpp:3886 #14 0x7f4a7f052cb8 in QMetaObject::activate (sender=sender@entry=0x7f4a74008d00, m=m@entry=0x7f4a80a78fe0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffea46b6b90) at kernel/qobject.cpp:3946 #15 0x7f4a809b209a in KIO::SlaveInterface::error (this=this@entry=0x7f4a74008d00, _t1=, _t2=...) at ./obj-x86_64-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:452 #16 0x7f4a809b43fc in KIO::SlaveInterface::dispatch (this=0x7f4a74008d00, _cmd=102, rawdata=...) at ./src/core/slaveinterface.cpp:180 #17 0x7f4a809b27fd in KIO::SlaveInterface::dispatch (this=0x7f4a74008d00) at ./src/core/slaveinterface.cpp:77 #18 0x7f4a809b61f2 in KIO::Slave::gotInput (this=0x7f4a74008d00) at ./src/core/slave.cpp:394 #19 0x7f4a7f059b0e in QtPrivate::QSlotObjectBase::call (a=0x7ffea46b6dd0, r=0x7f4a74008d00, this=0x558e2e11a1f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #20 doActivate (sender=0x558e2de09600, signal_index=3, argv=0x7ffea46b6dd0) at kernel/qobject.cpp:3886 #21 0x7f4a7f04f2a1 in QObject::event (this=0x558e2de09600, e=0x558e2d7d8ed0) at kernel/qobject.cpp:1314 #22 0x7f4a7faff173 in QApplicationPrivate::notify_helper (this=, receiver=0x558e2de09600, e=0x558e2d7d8ed0) at kernel/qapplication.cpp:3632 #23 0x7f4a7f0a in QCoreApplication::notifyInternal2 (receiver=0x558e2de09600, event=0x558e2d7d8ed0) at kernel/qcoreapplication.cpp:1063 #24 0x7f4a7f024d01 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x558e2d37fef0) at kernel/qcoreapplication.cpp:1817 #25 0x7f4a7f07bf37 in postEventSourceDispatch (s=0x558e2d47afd0) at kernel/qeventdispatcher_glib.cpp:277 #26 0x7f4a7ce7f01b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f4a7ce7f2c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f4a7ce7f393 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f4a7f07b594 in QEventDispatcherGlib::processEvents (this=0x558e2d48a630, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #30 0x7f4a7f020b8b in QEventLoop::exec (this=this@entry=0x7ffea46b71c0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #31 0x7f4a7f029024 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #32 0x7f4a8120a570 in kdemain (argc=, argv=) at ./src/main.cpp:222 #33 0x7f4a80ff3565 in __libc_start_main (main=0x558e2bd54060 , argc=1, argv=0x7ffea46b7488, init=, fini=, rtld_fini=, stack_end=0x7ffea46b7478) at ../csu/libc-s
[dolphin] [Bug 433993] Dolphin Crash when creating a folder in kio-Gdrive
https://bugs.kde.org/show_bug.cgi?id=433993 Eugene changed: What|Removed |Added CC||ken20...@ukr.net Platform|Neon Packages |Ubuntu Packages Version|20.12.2 |20.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 462056] New: KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 Bug ID: 462056 Summary: KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings Classification: I don't know Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.bee...@yandex.ru Target Milestone: --- 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 *** KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT files are being moved to Trash on system SSD EXPECTED RESULT files to be moved to created Trash folder on HDD SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 489853] _Unnecessary sending of notifications after blocking/unblocking PC
https://bugs.kde.org/show_bug.cgi?id=489853 Eugene changed: What|Removed |Added CC||eugene0w0g...@gmail.com Summary|Unnecessary sending of |_Unnecessary sending of |notifications after |notifications after |blocking/unblocking PC |blocking/unblocking PC -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #2 from Eugene --- Hello! It"s been mounted with gdisks with parameters nosuid,nodev,nofail,x-gvfs-show, read/write works well in this case. If I remove this line from fstab and mount drive at boot - trash settings can see this partition and use it for moving deleted files accordingly. This situation I can see on EndeavourOS too. On 11/30/22 01:38, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > Nate Graham changed: > > What|Removed |Added > > CC||kdelibs-b...@kde.org, > ||n...@kde.org > Assignee|unassigned-b...@kde.org |fa...@kde.org > Version|unspecified |5.100.0 > Product|kde |frameworks-kio > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO >Component|general |Trash > > --- Comment #1 from Nate Graham --- > Is the NTFS disk mounted read/write, or read-only? > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #4 from Eugene --- Hello! The problem is there if i mount the drive even with all the same args manually as the default one. Basically with the line in fstab trash doesn't work for the partition On 12/1/22 23:50, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > Nate Graham changed: > > What|Removed |Added > > Status|NEEDSINFO |RESOLVED > Resolution|WAITINGFORINFO |NOT A BUG > > --- Comment #3 from Nate Graham --- > Indeed, the trash code is picky about which args a disk is mounted with to be > counted as a volume with its own trash, because the functionality needs some > special mount options to work properly. As you've discovered, some of those > parameters break this and falling back to the default settings makes it work. > So I would recommend doing that. > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #6 from Eugene --- If I mount the partition manually at each boot - trash settings see it, if i use fstab automount with all the same aguments that terminal "mount" command gives me - the partition is not available in trash settings On 12/2/22 20:56, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #5 from Nate Graham --- > You said: >> If I remove this line from fstab and mount drive at boot - trash settings >> can see this partition and use it for moving deleted files accordingly. > I interpreted that to mean that it was working. Is that incorrect? > -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 462619] New: Screen oss shortcut
https://bugs.kde.org/show_bug.cgi?id=462619 Bug ID: 462619 Summary: Screen oss shortcut Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.bee...@yandex.ru Target Milestone: --- SUMMARY If i'm in X11 session and use shortcut for screen off it turns off the screen only for approx 1-1,5 second and then screen turns back on again STEPS TO REPRODUCE 1. Log in to X11 session 2. Set up shortcut for screen off 3. Press the combination OBSERVED RESULT Screen off only for approximately 1 sec EXPECTED RESULT Screen off until i move mouse or press any key SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: EndeavourOS/5.26.4 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #8 from Eugene --- Yes sir! That's exactly what i do though, but the problem is that i have to type password after boot to mount it and always reset the disc usage widget because it loads before the mount happens. So the solution is not replacement for the fstab line. On 12/5/22 21:10, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #7 from Nate Graham --- > Then don't use fstab automount; if you want it to automount, use KDE's own > automounting system in System Settings > Removable Storage > Removable Devices > which should mount the disk with the correct options to make trash support > work. > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #10 from Eugene --- The original bus is that automount with fstab using all the same parameters that "mount" command gives me in terminal makes trash workable only on root partition, if use automount through system parameters - I have to type password, the rest is just side effects of it On 12/5/22 23:04, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #9 from Nate Graham --- >> i have to type password after boot to mount it > That's a bug in your distro's polkit rules. I can reproduce it. It should be > fixed there, rather than worked around. Can you file a bug report at > https://bugzilla.redhat.com/ and paste the link to it here? > >> always reset the disc usage widget because it loads before the mount happens > That's a different bug, similar to Bug 441556, but not quite the same thing. > Can you file a new bug report for it and paste the link to it here? > > > As a general matter, when you have a problem, you should file a bug on the > problem. If you seek a workaround, and the workaround has problems too, we're > just going to ask you what the original problem is that you were trying to > work > around. :) We want to fix the original bug that caused yu to seek a > workaround, > not bugs caused by the workaround. > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #12 from Eugene --- OK i will report that automount with KDE setting cause need for password after boot to mount the device. The widget problem is expected because it loads on login and after that i type password a mount the device (it just don't give me information about it because I mount it after widget loads) On 12/6/22 03:06, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #11 from Nate Graham --- > (In reply to Eugene from comment #10) >> The original bus is that automount with fstab using all the same >> parameters that "mount" command gives me in terminal makes trash >> workable only on root partition, if use automount through system >> parameters - I have to type password, the rest is just side effects of it > And that's not a bug, it's expected behavior since you need to use special > mount flags to make trash functionality work. The `mount` command doesn't know > what those are, so it's expected that you use the KDE automount system > instead. > > If using the KDE automount system is causing other bugs (e.g. having to enter > your password on boot or disk space widgets not working until plasmashell is > restarted) those are the bugs that need to be fixed. Can you file bug reports > for them, please? > -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 462708] New: Automount NTFS HDD
https://bugs.kde.org/show_bug.cgi?id=462708 Bug ID: 462708 Summary: Automount NTFS HDD Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.bee...@yandex.ru Target Milestone: --- SUMMARY Automount NTFS HDD with KDE setting cause need for password after boot to mount the device STEPS TO REPRODUCE 1. Set automount in settings 2. Reboot OBSERVED RESULT Asks for password to mount the device EXPECTED RESULT Automount without password SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Kernel 6.0.11-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #14 from Eugene --- I'm sorry I don't use Fedora, I use EndeavourOS On 12/6/22 17:44, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #13 from Nate Graham --- > Thanks. Because the password issue is a Fedora bug, can you file it at > https://bugzilla.redhat.com? And then please paste the link here as I'm > interested in having that fixed as well. :) > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #16 from Eugene --- I don't know sir )) Maybe smb else with similar problem. it's fine I understand you discuss stuff with many people at the same time. On 12/6/22 18:39, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #15 from Nate Graham --- > Oh sorry. Where did I get the idea you use Fedora? That's odd. > -- You are receiving this mail because: You are watching all bug changes.
