[Powerdevil] [Bug 457859] Powerdevil does not respect sleep inhibitors created with systemd-inhibit by unprivileged users
https://bugs.kde.org/show_bug.cgi?id=457859 --- Comment #2 from Oded Arbel --- I can still reproduce this issue on Plasma 6.0.2. I tested with sleeping on laptop lid close: 1. run `systemd-inhibit --what=idle:sleep:shutdown:handle-lid-switch --who=test --why=coz sleep 300` 2. close the laptop lid Observed result: Computer goes to sleep Expected result: Computer stays on I can workaround the issue by stopping PowerDevil using `systemctl --user stop plasma-powerdevil.service`, and then closing the lid without using `systemd-inhibit` puts the computer to sleep, while doing so while systemd-inhibit is running (as per the above command) correctly prevents the computer from sleeping. An related issue (though unrelated to the use of systemd-inhibit) is that the battery widget's "Manually block sleep and screen locking" doesn't prevent sleep by closing the lid either. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457859] Powerdevil does not respect sleep inhibitors created with systemd-inhibit by unprivileged users
https://bugs.kde.org/show_bug.cgi?id=457859 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457859] Powerdevil does not respect sleep inhibitors created with systemd-inhibit by unprivileged users
https://bugs.kde.org/show_bug.cgi?id=457859 Oded Arbel changed: What|Removed |Added Version|unspecified |6.0.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484130] New: Dolphin crashes when using the Configure dialog to enable "Git" context menu item.
https://bugs.kde.org/show_bug.cgi?id=484130 Bug ID: 484130 Summary: Dolphin crashes when using the Configure dialog to enable "Git" context menu item. Classification: Applications Product: dolphin Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: o...@geek.co.il CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (24.02.1) Qt Version: 6.6.2 Frameworks Version: 6.1.0 Operating System: Linux 6.5.0-26-generic x86_64 Windowing System: Wayland Distribution: KDE neon Testing Edition DrKonqi: 6.0.2 [CoredumpBackend] -- Information about the crash: 1. Start Dolphin 2. Menu -> Configure -> Configure Dolphin -> Context Menu 3. Make sure that "Git" is not enabled 4. Enable "Git". 5. Click OK. There should be a dialog box confirming that Dolphin will restart, but instead it crashes. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 586863] [New LWP 586864] [New LWP 586867] [New LWP 586875] [New LWP 586868] [New LWP 586865] [New LWP 586866] [New LWP 586874] [New LWP 586877] [New LWP 586878] [New LWP 586876] [New LWP 586869] [New LWP 586871] [New LWP 586905] [New LWP 586895] [New LWP 586894] [New LWP 586882] [New LWP 586892] [New LWP 586891] [New LWP 586893] [New LWP 586880] [New LWP 586904] [New LWP 586903] [New LWP 586913] [New LWP 586881] [New LWP 586879] [New LWP 586907] [New LWP 586870] [New LWP 586873] [New LWP 586901] [New LWP 586872] [New LWP 586902] This GDB supports auto-downloading debuginfo from the following URLs: https://debuginfod.neon.kde.org/: Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal] Debuginfod has been disabled. To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/dolphin'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=132866065644224) at ./nptl/pthread_kill.c:44 [Current thread is 1 (Thread 0x78d74aa53ac0 (LWP 586863))] Cannot QML trace cores :( [Current thread is 1 (Thread 0x78d74aa53ac0 (LWP 586863))] Thread 32 (Thread 0x78d6c8ffe640 (LWP 586902)): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x78d6c8ffd970, op=137, expected=0, futex_word=0x5dc262caa190) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x78d6c8ffd970, clockid=560, expected=0, futex_word=0x5dc262caa190) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5dc262caa190, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x78d6c8ffd970, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x78d74f693e9b in __pthread_cond_wait_common (abstime=0x78d6c8ffd970, clockid=1, mutex=0x5dc262caa140, cond=0x5dc262caa168) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_timedwait64 (cond=0x5dc262caa168, mutex=0x5dc262caa140, abstime=0x78d6c8ffd970) at ./nptl/pthread_cond_wait.c:652 #5 0x78d750162157 in QWaitConditionPrivate::wait_relative (deadline=..., this=0x5dc262caa140) at ./src/corelib/thread/qwaitcondition_unix.cpp:93 #6 QWaitConditionPrivate::wait (deadline=..., this=0x5dc262caa140) at ./src/corelib/thread/qwaitcondition_unix.cpp:101 #7 QWaitCondition::wait (this=, mutex=0x5dc26278e8e8, deadline=...) at ./src/corelib/thread/qwaitcondition_unix.cpp:181 #8 0x78d75015d431 in QThreadPoolThread::run (this=0x5dc262e579d0) at ./src/corelib/thread/qthreadpool.cpp:114 #9 0x78d75015ce7d in operator() (__closure=) at ./src/corelib/thread/qthread_unix.cpp:324 #10 (anonymous namespace)::terminate_on_exception > (t=...) at ./src/corelib/thread/qthread_unix.cpp:260 #11 QThreadPrivate::start (arg=0x5dc262e579d0) at ./src/corelib/thread/qthread_unix.cpp:283 #12 0x78d74f694ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #13 0x78d74f726850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 31 (Thread 0x78d72abfa640 (LWP 586872)): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x5dc26225f858) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x5dc26225f858) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5dc26225f858, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x78
[dolphin] [Bug 484130] Dolphin crashes when using the Configure dialog to enable "Git" context menu item.
https://bugs.kde.org/show_bug.cgi?id=484130 --- Comment #1 from Oded Arbel --- This is the relevant part of the crash: Thread 1 (Thread 0x78d74aa53ac0 (LWP 586863)): [KCrash Handler] #6 std::__atomic_base::load (__m=, this=, this=, __m=) at /usr/include/c++/12/bits/atomic_base.h:818 #7 std::atomic::load (__m=, this=, this=, __m=) at /usr/include/c++/12/atomic:579 #8 QAtomicOps::loadAcquire (_q_value=..., _q_value=...) at ./src/corelib/thread/qatomic_cxx11.h:213 #9 QBasicAtomicPointer::loadAcquire (this=, this=) at ./src/corelib/thread/qbasicatomic.h:179 #10 QObject::thread (this=this@entry=0x5dc263403e20) at ./src/corelib/kernel/qobject.cpp:1610 #11 0x78d7501d24af in QObject::QObject (this=, dd=..., parent=, this=, dd=..., parent=) at ./src/corelib/kernel/qobject.cpp:972 #12 0x78d751af6d03 in KMessageBox::createKMessageBox(QDialog*, QDialogButtonBox*, QIcon const&, QString const&, QList const&, QString const&, bool*, QFlags, QString const&, QMessageBox::Icon) () from /lib/x86_64-linux-gnu/libKF6WidgetsAddons.so.6 #13 0x78d751af83b7 in KMessageBox::createKMessageBox(QDialog*, QDialogButtonBox*, QMessageBox::Icon, QString const&, QList const&, QString const&, bool*, QFlags, QString const&) () from /lib/x86_64-linux-gnu/libKF6WidgetsAddons.so.6 #14 0x78d751afa0a1 in ?? () from /lib/x86_64-linux-gnu/libKF6WidgetsAddons.so.6 #15 0x78d751afa281 in KMessageBox::questionTwoActions(QWidget*, QString const&, QString const&, KGuiItem const&, KGuiItem const&, QString const&, QFlags) () from /lib/x86_64-linux-gnu/libKF6WidgetsAddons.so.6 #16 0x5dc261eb3800 in ContextMenuSettingsPage::applySettings (this=) at ./src/settings/contextmenu/contextmenusettingspage.cpp:206 I'm not sure what is going on - the crash location is an assert on the value of the memory_order field, where the value is hard coded in QAtomicOps::loadAcquire() and seems correct. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab
https://bugs.kde.org/show_bug.cgi?id=479094 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #16 from Oded Arbel --- I also experience frequent (daily) kwin_wayland complete freezes - though I'm unsure if it is related to this bug: - I don't believe it is related to task switcher or overview (I frankly almost never use either) - when kwin freezes, the main seat is completely dead - I can't even switch to a VT. I can only recover by SSHing to my machine and issuing kill -9. I'm running Neon testing - up to date as of today - but the issue has been happening since RC1 dropped. I managed to get a thread dump of the frozen kwin, and I can see that the main thread (that pegs the CPU) is running this: ---8<--- #0 0x7fb2e818445e in _mm_cmpeq_epi16(long long __vector(2), long long __vector(2)) (__B=..., __A=...) at ./src/corelib/text/qstring.cpp:599 #1 operator() (__closure=, offset=0) at ./src/corelib/text/qstring.cpp:626 #2 ucstrncmp_sse2<(::StringComparisonMode)0, char16_t> (l=, b=0x559bd2085280 u"/usr/share/plasma/desktoptheme/default/widgets/scrollbar.svgz", a=) at ./src/corelib/text/qstring.cpp:634 #3 ucstrncmp<(::StringComparisonMode)0> (l=, b=0x559bd2085280 u"/usr/share/plasma/desktoptheme/default/widgets/scrollbar.svgz", a=) at ./src/corelib/text/qstring.cpp:1294 #4 ucstreq (blen=, b=0x559bd2085280 u"/usr/share/plasma/desktoptheme/default/widgets/scrollbar.svgz", alen=, a=) at ./src/corelib/text/qstring.cpp:1364 #5 QtPrivate::equalStrings(QStringView, QStringView) (lhs=..., rhs=...) at ./src/corelib/text/qstring.cpp:1402 #6 0x7fb2eaf91844 in () at /lib/x86_64-linux-gnu/libKF6Svg.so.6 #7 0x7fb2eaf8634a in () at /lib/x86_64-linux-gnu/libKF6Svg.so.6 #8 0x7fb2eaf86bd9 in KSvg::Svg::hasElement(QStringView) const () at /lib/x86_64-linux-gnu/libKF6Svg.so.6 #9 0x7fb2eaf7c4fd in () at /lib/x86_64-linux-gnu/libKF6Svg.so.6 #10 0x7fb2eaf7dc75 in () at /lib/x86_64-linux-gnu/libKF6Svg.so.6 #11 0x7fb2c13eb325 in () at /usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/ksvg/libcorebindingsplugin.so #12 0x7fb2ea36b051 in QQuickItem::setSize(QSizeF const&) (this=this@entry=0x559bd167ec60, size=...) at ./src/quick/items/qquickitem.cpp:7576 #13 0x7fb2e1d9a8ae in QQuickScrollBarPrivate::resizeContent() (this=) at ./src/quicktemplates/qquickscrollbar.cpp:225 #14 0x7fb2e1d9538e in QQuickScrollBar::setSize(double) (this=0x559bd1596c10, size=0.95266567015445935) at ./src/quicktemplates/qquickscrollbar.cpp:420 #15 0x7fb2e8228a8b in doActivate(QObject*, int, void**) (sender=0x559bcfe32210, signal_index=6, argv=0x7ffd868d4750) at ./src/corelib/kernel/qobject.cpp:4033 #16 0x7fb2ea348e17 in QQuickFlickableVisibleArea::heightRatioChanged(double) (this=, _t1=) at ./obj-x86_64-linux-gnu/src/quick/Quick_autogen/include/moc_qquickflickable_p_p.cpp:304 #17 0x7fb2ea12cb58 in QQuickItemViewPrivate::layout() (this=0x559bd2079640) at ./src/quick/items/qquickitemview.cpp:1927 #18 0x7fb2ea30726b in QQuickWindowPrivate::polishItems() (this=0x559bd23f4230) at ./src/quick/items/qquickwindow.cpp:346 #19 0x7fb2ea20a09a in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*) (this=0x559bd1ccb670, window=0x559bd329b830) at ./src/quick/scenegraph/qsgrenderloop.cpp:586 #20 0x7fb2e87461a8 in QWindow::event(QEvent*) (this=0x559bd329b830, ev=0x7ffd868d4db0) at ./src/gui/kernel/qwindow.cpp:2553 #21 0x7fb2e95f1b1b in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x559bd329b830, e=0x7ffd868d4db0) at ./src/widgets/kernel/qapplication.cpp:3296 #22 0x7fb2e825fe58 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=receiver@entry=0x559bd329b830, event=event@entry=0x7ffd868d4db0) at ./src/corelib/kernel/qcoreapplication.cpp:1121 #23 0x7fb2e826037d in QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) (receiver=receiver@entry=0x559bd329b830, event=event@entry=0x7ffd868d4db0) at ./src/corelib/kernel/qcoreapplication.cpp:1553 ---8<--- Do you think this is related, or should I report a new bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab
https://bugs.kde.org/show_bug.cgi?id=479094 --- Comment #19 from Oded Arbel --- (In reply to hexchain from comment #17) > Do you see a lot of these lines in the log when it's frozen? If yes then it > could be related. > > kwin_scene_opengl: 0x1: GL_INVALID_OPERATION in glVertexAttribPointer(no > array object bound) > kwin_scene_opengl: 0x1: GL_INVALID_OPERATION in glDrawArrays I do not see messages about GL_INVALID_OPERATION in my kwin logs, so I'll conclude that this isn't the same issue as I'm having. I will wait to get a few more freezes and compare stack traces, and report a new bug as needed. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446389] On Wayland, KWin doesn't differentiate numberpad number key shortcuts from above-the-letters number key shortcuts
https://bugs.kde.org/show_bug.cgi?id=446389 --- Comment #24 from Oded Arbel --- With current build from Neon testing (4:5.91.90+p22.04+vstable+git20240128.0255-0) - which to the best of my understanding includes the patches that resolved this issue - numpad keys, with Num Lock turned on, indeed do not conflict with the main keyboard number keys. That being said - they now produce the cursor control symbols (arrows, home/end/ins/del, etc) regardless of the state of Num Lock, and as a result the shortcut configuration cannot distinguish between Home and numpad 1 or Insert and numpad 0. This has (kind of) the same implications as not differentiating between number keys and numpad keys (when Num Lock is on) - they cannot be used to set up different shortcuts. The situation is definitely better, in that the shortcut behavior of numpad keys is no longer dependent on the state of Num Lock - but I think what everyone was hoping is that when you program a shortcut with the wide key at the bottom of the shortcut , it would show up as something like "KP Insert" (at least that's what GTK is calling it) and I can also program a different shortcut set with the "real" Insert key. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 453661] Global shortcuts are not working across multiple keyboard layouts (US and CZ for me)
https://bugs.kde.org/show_bug.cgi?id=453661 Oded Arbel changed: What|Removed |Added CC||aaaj...@gmail.com --- Comment #38 from Oded Arbel --- *** Bug 423796 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462274] global shortcuts do not work for non-Latin symbols of foreign keyboard layouts, if active application has active input field
https://bugs.kde.org/show_bug.cgi?id=462274
Oded Arbel changed:
What|Removed |Added
CC||o...@geek.co.il
--- Comment #3 from Oded Arbel ---
I believe I can reproduce the issue on Plasma 6 RC1, my repro is using a
different keys (because my non-English layout has the same shift symbols for
the number row) but I believe it is the same issue.
Reproduction using "/" key on Hebrew layout - in the SI-1452 the "/" key is on
the left-most key of the top character row ("Q" in QWERTY layout):
1. Using the Shortcuts KCM assign some global shortcut to CTRL+/ (in my case I
used the "launch Dolphin" shortcut).
2. Activate a window with a text input and put text cursor in the text input
(for example, in Firefox on bugs.kde.org).
3. Switch to the Hebrew layout.
4. Press CTRL+/
Expected behavior:
Dolphin should be launched.
Actual behavior:
Nothing happens (or some Firefox action might happen if it is bound to CTRL+.)
On the other hand, pressing CTRL+Q (while in SI-1452 layout) does launch
Dolphin.
This is a **very** common issue and - depending on how you look at it - may not
actually be a bug. This factors into the discussion in bug #355046: when
creating a global shortcut with one layout, when another layout is active -
should the global shortcut bind to the physical key on the keyboard or to the
character emitted by the key in a specific layout.
Bug #453661 (which Yevhen added a link from to here), is another instance of
the same issue - though there its more about how to trigger global shortcuts
bound to a character that isn't actually available in the active layout.
But yes - I think these are all the same issue: IMO global shortcut (in
contrast with app-specific shortcuts) should be bound to the physical key,
though there are serious technical hurdles to implement this using the current
Qt-based approach to global shortcuts.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 423796] Alt+tilde/Alt+backtick shortcuts don't take into account that tilde and backtick characters may not be on the same physical key together
https://bugs.kde.org/show_bug.cgi?id=423796 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Oded Arbel --- Dupping against bug #453661, as that has a lot more relevant discussion (and also the ALT+` issue is mentioned) *** This bug has been marked as a duplicate of bug 453661 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] SDDM and kscreenlocker does not accept enter key
https://bugs.kde.org/show_bug.cgi?id=478875 --- Comment #29 from Oded Arbel --- (In reply to Lassi Väätämöinen from comment #28) > Not X11 -specific. Happens also with Wayland on Virtualbox I cannot repro in Wayland on hardware - which makes me thing the VirtualBox issue is a separate problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] SDDM and kscreenlocker does not accept enter key in X11
https://bugs.kde.org/show_bug.cgi?id=478875 --- Comment #34 from Oded Arbel --- (In reply to Lassi Väätämöinen from comment #33) > KDE Neon Unstable > SDDM login: enter does not work, when focus is in the password entry box. > You need to into the arrow button, then enter works. > KScreenlocker: works. Please note that SDDM default configuration is to run with X11 - even when you log in to a Wayland session, the SDDM login screen itself is running on X11, where the behavior described by this bug would happen. The workaround would be to run SDDM under Wayland, by having the following configuration in /etc/sddm.conf: ---8<--- [General] DisplayServer=wayland GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell [Wayland] CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1 ---8<--- If you don't have this configuration (or similar), then SDDM is running under X11 and this is problem is not actually happen with Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472369] Please allow disabling resize-both-windows when quick tiling
https://bugs.kde.org/show_bug.cgi?id=472369 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] SDDM and kscreenlocker does not accept enter key in X11
https://bugs.kde.org/show_bug.cgi?id=478875 --- Comment #38 from Oded Arbel --- (In reply to funkybomber from comment #37) > Just for the record I can also reproduce this bug in both X11 and Wayland > when running the latest KDE Neon unstable under QEMU. Can you please make sure that the Wayland issue is not as actually an X11 issue, as described in comment #34? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 475378] Selected text background does not scroll with text
https://bugs.kde.org/show_bug.cgi?id=475378 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #4 from Oded Arbel --- Created attachment 165701 --> https://bugs.kde.org/attachment.cgi?id=165701&action=edit Another screencast showing the problem I think this is the same problem - though for me I'm more troubled about the blank boxes that appear and hide the text. My repro is on Plasma 6 from testing, with Kate 24.01.95, and I didn't see this issue before Plasma 6 Operating System: KDE neon Testing Edition KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-17-generic (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460907] System tray sometimes overlaps the clock until plasmashell is restarted or screen layout is changed
https://bugs.kde.org/show_bug.cgi?id=460907 Oded Arbel changed: What|Removed |Added Resolution|WORKSFORME |DUPLICATE --- Comment #12 from Oded Arbel --- *** This bug has been marked as a duplicate of bug 482098 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482098] Overlapping widgets with Activities widget on panel
https://bugs.kde.org/show_bug.cgi?id=482098 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #18 from Oded Arbel --- *** Bug 460907 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #3 from Oded Arbel --- If I understand correctly, the problem is that kwin -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] After waking the system, the desktop gets displayed for a moment before the lock screen appears
https://bugs.kde.org/show_bug.cgi?id=316734 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 453224] Nothing happens when I click on 'Next' button
https://bugs.kde.org/show_bug.cgi?id=453224 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453580] New: kdeconnectd constantly crashing
https://bugs.kde.org/show_bug.cgi?id=453580 Bug ID: 453580 Summary: kdeconnectd constantly crashing Product: kdeconnect Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: o...@geek.co.il Target Milestone: --- Application: kdeconnectd (22.07.70) Qt Version: 5.15.3 Frameworks Version: 5.94.0 Operating System: Linux 5.15.0-27-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04 LTS DrKonqi: 5.24.80 [KCrashBackend] -- Information about the crash: the kdeconnect service crashes after a short while regardless of what is going on. Whenerver I start a kdeconnect operation, such as through the CLI or the plasma icon, after a few seconds kdeconnectd crashes and I get a crash report dialog. The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7f9fdbb92c3b in qobject_cast (object=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:524 #5 PulseAudioQt::Sink::setActivePortIndex (this=0x559c4a101350, port_index=984771552) at ./src/sink.cpp:58 #6 0x7f9fe80bccf6 in SystemvolumePlugin::sendSinkList() () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_systemvolume.so #7 0x7f9ff0271b83 in QtPrivate::QSlotObjectBase::call (a=0x7ffc3ab26e30, r=0x559c49bb2360, this=0x559c49f771f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x559c49f8c730, signal_index=3, argv=0x7ffc3ab26e30) at kernel/qobject.cpp:3886 #9 0x7f9ff026ae97 in QMetaObject::activate (sender=, m=m@entry=0x7f9fdca0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc3ab26e30) at kernel/qobject.cpp:3946 #10 0x7f9fdbb67fc3 in PulseAudioQt::Context::sinkAdded (this=, _t1=) at ./obj-x86_64-linux-gnu/src/KF5PulseAudioQt_autogen/EWIEGA46WW/moc_context.cpp:325 #11 0x7f9ff0271b83 in QtPrivate::QSlotObjectBase::call (a=0x7ffc3ab26f40, r=0x559c49f8c730, this=0x559c49f8b660) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x559c49c395a8, signal_index=4, argv=0x7ffc3ab26f40) at kernel/qobject.cpp:3886 #13 0x7f9ff026ae97 in QMetaObject::activate (sender=sender@entry=0x559c49c395a8, m=m@entry=0x7f9fdbe0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc3ab26f40) at kernel/qobject.cpp:3946 #14 0x7f9fdbb68a91 in PulseAudioQt::MapBaseQObject::added (this=this@entry=0x559c49c395a8, _t1=, _t1@entry=0, _t2=, _t2@entry=0x559c4a101350) at ./obj-x86_64-linux-gnu/src/KF5PulseAudioQt_autogen/EWIEGA46WW/moc_maps.cpp:175 #15 0x7f9fdbb82264 in PulseAudioQt::MapBase::insert (object=0x559c4a101350, this=0x559c49c395a8) at ./src/maps.h:111 #16 PulseAudioQt::MapBase::updateEntry (parent=, info=, this=0x559c49c395a8) at ./src/maps.h:130 #17 PulseAudioQt::MapBase::updateEntry (parent=, info=, this=0x559c49c395a8) at ./src/maps.h:117 #18 PulseAudioQt::ContextPrivate::sinkCallback (info=, this=0x559c49c395a0) at ./src/context.cpp:523 #19 PulseAudioQt::sink_cb (context=, eol=0, data=0x559c49c395a0, info=) at ./src/context.cpp:82 #20 PulseAudioQt::sink_cb (context=, info=, eol=, data=0x559c49c395a0) at ./src/context.cpp:76 #21 0x7f9fdbb16aa9 in context_get_sink_info_callback (pd=pd@entry=0x559c4a0ffd70, command=command@entry=2, tag=tag@entry=3, t=t@entry=0x559c4a1046d0, userdata=userdata@entry=0x559c49c258f0) at ../src/pulse/introspect.c:268 #22 0x7f9fdbab7383 in run_action (pd=0x559c4a0ffd70, r=0x559c49d10630, command=2, ts=0x559c4a1046d0) at ../src/pulsecore/pdispatch.c:291 #23 0x7f9fdbab85bf in pa_pdispatch_run (pd=0x559c4a0ffd70, packet=packet@entry=0x559c49c257f0, ancil_data=ancil_data@entry=0x559c4a0f88a8, userdata=userdata@entry=0x559c49f883c0) at ../src/pulsecore/pdispatch.c:344 #24 0x7f9fdbb10083 in pstream_packet_callback (p=, packet=0x559c49c257f0, ancil_data=0x559c4a0f88a8, userdata=0x559c49f883c0) at ../src/pulse/context.c:364 #25 0x7f9fdbabd487 in do_read (p=p@entry=0x559c4a0f8610, re=re@entry=0x559c4a0f8790) at ../src/pulsecore/pstream.c:1023 #26 0x7f9fdbabe28f in do_pstream_read_write (p=0x559c4a0f8610) at ../src/pulsecore/pstream.c:261 #27 0x7f9fe82c6916 in dispatch_func (source=0x559c49c35d40, callback=, userdata=) at ../src/pulse/glib-mainloop.c:581 #28 0x7f9fee6cdd1b in g_main_dispatch (context=0x7f9fe4005010) at ../../../glib/gmain.c:3417 #29 g_main_context_dispatch (context=0x7f9fe4005010) at ../../../glib/gmain.c:4135 #30 0x7f9fee7226f8 in g_main_context_iterate.constprop.0 (context=context@entry=0x7f9fe4005010, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4211 #31 0x7f9fee6cb3c3 in g_main_context_iteration (context=0x7f9fe400
[kdeconnect] [Bug 453580] kdeconnectd constantly crashing
https://bugs.kde.org/show_bug.cgi?id=453580 --- Comment #1 from Oded Arbel --- I'm running neon unstable jammy, but interestingly, I have libkf5pulseaudioqt3 installed from what appears to be the neon unstable focal (I upgraded from unstable focal to unstable jammy): ```$ apt policy libkf5pulseaudioqt3 libkf5pulseaudioqt3: Installed: 1.3+p20.04+tunstable+git20220306.0204-0 Candidate: 1.3+p20.04+tunstable+git20220306.0204-0 Version table: *** 1.3+p20.04+tunstable+git20220306.0204-0 100 100 /var/lib/dpkg/status 1.3-2 500 500 http://mirror.il-ta.kamatera.com/ubuntu jammy/universe amd64 Packages ``` I see that libkf5pulseaudioqt3 is currently failing to build: https://build.neon.kde.org/job/jammy_unstable_extras_pulseaudio-qt_bin_amd64/6/ -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 453855] New: Cannot get developer information or report bugs due to error: /ui/DeveloperPage.qml:68 Type RatingItem unavailable
https://bugs.kde.org/show_bug.cgi?id=453855 Bug ID: 453855 Summary: Cannot get developer information or report bugs due to error: /ui/DeveloperPage.qml:68 Type RatingItem unavailable Product: drkonqi Version: master Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: backtraceparsing Assignee: plasma-b...@kde.org Reporter: o...@geek.co.il Target Milestone: --- Running neon jammy unstable SUMMARY When DrKonqi opens after an application crash, trying to report a bug and clicking "Next" from "What do You Know About the Crash", nothing happens in the UI and in the console the following message is shown: QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:878: Error: Error while loading page: qrc:/ui/DeveloperPage.qml:68 Type RatingItem unavailable qrc:/ui/RatingItem.qml:14 Duplicate property name SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.24.5+p22.04+tunstable+git20220511.0116-0 KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 453855] Cannot get developer information or report bugs due to error: /ui/DeveloperPage.qml:68 Type RatingItem unavailable
https://bugs.kde.org/show_bug.cgi?id=453855 --- Comment #1 from Oded Arbel --- Probably related to this commit: https://invent.kde.org/plasma/drkonqi/-/commit/48f2e7606ad08ff7f4394e793ea9b0cfd82babd2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #399 from Oded Arbel --- This issues seems resolved from my side, but recently (running on Neon Jammy unstable) it started happening again: My `~/.config/plasma-org.kde.plasma.desktop-appletsrc` has this setup normally: ---8<--- [Containments][2] activityId= formfactor=2 immutability=1 lastScreen=0 location=4 plugin=org.kde.panel wallpaperplugin=org.kde.image ---8<--- and I have a few different screen setups I use with it - laptop only; laptop with one external HDMI screen; laptop with one external DP screen over USB-C; laptop with two external DP screens over Thunderbolt 3. Whenever I wake up or boot the computer on the last setup (laptop+2xDP), the panel moves to screen 2 (which is the left most one - all of my external screens are configured to be on the left of the laptop) and I can see that `~/.config/plasma-org.kde.plasma.desktop-appletsrc` has `lastScreen=2` for `[Containments][2]`. Its important to understand that when this is happening, opening up the display configuration KCM still shows the laptop screen as the main screen. Trying to fix the issue by messing with the KCM doesn't solve the problem - the only way to get the panel into screen 0 (the laptop screen, where it should be) is by nominating screen 2 as the main screen - which I don't want to do. I'm fixing this by editing the config file by hand and restarting plasmashell (no reboot, just `systemctl --user restart plasma-plasmashell`), but it will happen again if I shutdown/suspend, move to another setup, and come back to the 2xDP setup. Currently I'm only using the problematic setup twice a week (and sometimes continuously) so it isn't that horrible, but clearly its a regression. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453977] New: X11: window rule setting "No titlebar and frame" has no effect on GTK applications
https://bugs.kde.org/show_bug.cgi?id=453977 Bug ID: 453977 Summary: X11: window rule setting "No titlebar and frame" has no effect on GTK applications Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: o...@geek.co.il CC: isma...@gmail.com Target Milestone: --- SUMMARY Setting a window rule that includes the "Appearance & Fixes" clause "No titlebar and frame" has no effect on the targeted window's "No Border" feature (as can be see under the windows operation menu' "More Actions" sub menu), for GTK applications. I have tested the issue with various GTK and GNOME applications as well as with Google Chrome. This is running Neon Jammy unstable, but I've had the same behavior with previous builds. STEPS TO REPRODUCE 1. Start a GTK application 2. Create a new window rule by detecting the new application's window properties. select class or anything else that applies. 3. Add "No titlebar and frame" clause and set to "Force" and choose either "yes" or "no" for the setting. 4. Add "Titlebar color scheme" (for control) clause and set to "Force" and choose any value for the setting. 5. Click "Apply". 6. Change "No titlebar and frame" setting to the other value, and "Titlebar color scheme" to a different value (that is distinguishable) and click "Apply". OBSERVED RESULT The color scheme (and any other setting I tested) does change and take effect immediately, but the window border status does not change from the application's default - if it does not allow the window manager to draw borders, then setting "No titlebar and frame" to "No" does not do anything, and it it does allow the WM to draw borders, then setting "Yes" does not do anything. EXPECTED RESULT Setting "No titlebar and frame" to "Force" and "No" should force kwin to draw window borders regardless of the application internal settings, while setting "Force" and "Yes" should force kwin to not draw window borders. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I'm a bit confused about the window rules feature called "No titlebar and frame" while the kwin window's operation menu has a feature called "No border", but they seem to me to be the same thing with different text. That being said, with KDE applications I've tested, setting a rule with "No titlebar and frame" to "yes" indeed sets the "No border" checkbox in the kwin windows operation menu, while with GTK apps it does not. Using the "No border" feature, on the kwin windows operation menu, manually with GTK apps *does* work as expected - if the application requested "No border", it can be turned off to get the kwin window borders while if the application did not request that, turning it on removes the kwin window borders. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453977] X11: window rule setting "No titlebar and frame" has no effect on GTK applications
https://bugs.kde.org/show_bug.cgi?id=453977 --- Comment #2 from Oded Arbel --- Vlad, I'm quite confused by your response: 1. This issue is about X11 and not Wayland. I'm not sure of the behavior on Wayland, but I don't think it applies to this issue if the behavior there is as different from X11 as you describe. If you mean to say "Kwin team will not fix this issue on X11 because that platform is deprecated and the team is focusing on Wayland", that is one thing - but I would expect the resolution to be "WONTFIX" and not "NOT A BUG". 2. You said "... on X11, kwin can't force any decoration mode" - which is seems incorrect to me - as kwin rules successfully force the decoration mode for Qt apps, KDE apps, WxWidget apps, Libre Office, Thunderbird and Firefox (surprisingly? IIRC the last two are using GTK). But after investigating the issue a bit more, I think I understand it a bit more and it all probably starts from my misunderstanding of the idea of setting the rule "No titlebar and frame" to "No" and how it interoperates with GNOME client-side decorations and the gtk3-nocsd hack: - It is now my belief that "No titlebar and frame" means that kwin will hide the decorations for windows that assume server-side decoration. Setting it to "No" does not mean "force server-side decoration" (though I think that would have been useful). - GNOME apps request to disable server-side decorations, which kwin will always honor. - gtk3-nocsd disables the request to disable server-side decorations, causing kwin to draw titlebar and frame. - My main problem is actually Google Chrome apps that use "open as a window", which use CSD, aren't affected by gtk3-nocsd and I can't get kwin to draw reasonable borders around them (making their title bar unreadable due to the bad interaction between Google Chrome CSD colors and the Breeze theme). I'm still not sure why kwin refuses to hide the server side decoration when setting "No titlebar and frame" to "Force" "yes", for a GNOME apps loaded with gtk3-nocsd - it sounds like a bug to me, and possibly, relevant to this issue - but I'm actually not that interested in that problem. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 454964] crash on tab closing
https://bugs.kde.org/show_bug.cgi?id=454964 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445497] All Konsole windows crashed when a session which had launched a background application was closed
https://bugs.kde.org/show_bug.cgi?id=445497 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #1 from Oded Arbel --- This issue may be related to bug #454964 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455783] Regression (since pre 5.25): in present window, windows on a second screen can't be chosen by keyboard
https://bugs.kde.org/show_bug.cgi?id=455783 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #8 from Oded Arbel --- With the new unified behavior between "Overview" and "Present Windows", this issue is likely related to bug #456331 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414714] kde connect crash when delete notices
https://bugs.kde.org/show_bug.cgi?id=414714 Oded Arbel changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||o...@geek.co.il --- Comment #1 from Oded Arbel --- works with current neon unstable -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312 Oded Arbel changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from Oded Arbel --- As of neon unstable kwin X11 build 5.25.4+p22.04+tunstable+git20220815.0018-0 , this issues seems to be resolved - on session restart or kwin_x11 restart, the existing windows (or session restored windows) are mapped to the correct activities. I'm not sure if a specific work was done to address this issue, but I'm closing this issue for now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312 Oded Arbel changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #7 from Oded Arbel --- (In reply to Oded Arbel from comment #6) > As of neon unstable kwin X11 build > 5.25.4+p22.04+tunstable+git20220815.0018-0 , this issues seems to be > resolved - on session restart or kwin_x11 restart, the existing windows (or > session restored windows) are mapped to the correct activities. > > I'm not sure if a specific work was done to address this issue, but I'm > closing this issue for now. Apparently it was a fluke? Maybe I missed something during tests? But after another upgrade and restart, now running kwin-x11 5.25.4+p22.04+tunstable+git20220816.0249-0, activities are again not remembered after session restart or kwin_x11 restart. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312 --- Comment #8 from Oded Arbel --- Ok, sorry for the bug spam, but last update for today: Previously (i.e. as of last week, before 5.25.4+p22.04+tunstable+git20220815.0018-0) kwin_x11 would not remember windows activity assignment when it was shutdown - regardless if it was by logout/shutdown, `systemctl --user restart plasma-kwin_x11.service` or `kwin_x11 --replace` As of this week update, logging out and logging back puts the windows back into their assigned activities - the session log in is now a bit weird, because during log in - after the splash screen is hidden - the session switches to each activity to restore the windows to it, so if I logged out while in activity B, when I log back in it starts in activity B and then switches to activity A to restore the windows there, and stays there. It is a bit jarring, I may open another ticket on that. But restarting kwin (using either `systemctl --user restart plasma-kwin_x11.service` or `kwin_x11 --replace`) causes the activity assignment to be lost and all windows assigned to "all activities" - which is the original issue reported. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458836] New: [Wayland] global shortcuts do not work when a "Chrome app" is active
https://bugs.kde.org/show_bug.cgi?id=458836 Bug ID: 458836 Summary: [Wayland] global shortcuts do not work when a "Chrome app" is active Product: kwin Version: 5.25.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: o...@geek.co.il Target Milestone: --- SUMMARY Running kwin-wayland 4:5.25.5-0ubuntu1 on Kubuntu Kinetic, when a "Chrome app" (a website that was added to "chrome://apps" and then marked with "open as window") is open and active, none of the global shortcuts work - except ALT-F4 to close the window. That includes: - kwin window management shortcuts (such as window operations menu shortcut or switch to next app) - other applications global shortcuts (such as spectacle screen capture) STEPS TO REPRODUCE 1. Start a Wayland plasma session and install Chrome 2. Open a Chrome tab to "chrome://apps" 3. Either add a new app by opening another tab to a website that you want to "applify" and then dragging its "website information" icon (often shown as a lock) to the apps tab, or just use one of the existing pre-installed apps. 4. Right click the app you want to test and choose "Open as window" from the menu. 5. Click the app icon and wait for it to open. 6. try to switch to another app using the keyboard shortcut. OBSERVED RESULT Nothing happens EXPECTED RESULT Kwin should activate the original Chrome window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION When pressing global shortcuts in a "chrome app" window, the user journal has this to say: 8< Sep 07 16:25:59 vesho plasmashell[9328]: [9323:9323:0907/162559.973043:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_translate_keyboard_state: assertion 'GDK_IS_KEYMAP (keymap)' failed Sep 07 16:25:59 vesho plasmashell[9328]: [9323:9323:0907/162559.973076:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_add_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed Sep 07 16:25:59 vesho plasmashell[9328]: [9323:9323:0907/162559.973094:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent. Sep 07 16:26:00 vesho plasmashell[9328]: [9323:9323:0907/162600.196809:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_translate_keyboard_state: assertion 'GDK_IS_KEYMAP (keymap)' failed Sep 07 16:26:00 vesho plasmashell[9328]: [9323:9323:0907/162600.196824:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_add_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed Sep 07 16:26:00 vesho plasmashell[9328]: [9323:9323:0907/162600.196833:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent. Sep 07 16:26:00 vesho plasmashell[9328]: [9323:9323:0907/162600.301176:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_translate_keyboard_state: assertion 'GDK_IS_KEYMAP (keymap)' failed Sep 07 16:26:00 vesho plasmashell[9328]: [9323:9323:0907/162600.301217:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_add_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed Sep 07 16:26:00 vesho plasmashell[9328]: [9323:9323:0907/162600.301239:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent. Sep 07 16:26:00 vesho plasmashell[9328]: [9323:9323:0907/162600.359204:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_translate_keyboard_state: assertion 'GDK_IS_KEYMAP (keymap)' failed Sep 07 16:26:00 vesho plasmashell[9328]: [9323:9323:0907/162600.359232:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_add_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed Sep 07 16:26:00 vesho plasmashell[9328]: [9323:9323:0907/162600.359249:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent. 8< -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458836] [Wayland] global shortcuts do not work when a "Chrome app" is active
https://bugs.kde.org/show_bug.cgi?id=458836 --- Comment #1 from Oded Arbel --- My Google Chrome configuration is to use "classic" theme (not GTK+) with "Use system title bar and borders" - not that I think it makes a difference: I tried all other configurations and it behaves the same. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457049] Global hotkeys are not working when Chrome/Chromium PWA window is focused on wayland
https://bugs.kde.org/show_bug.cgi?id=457049 --- Comment #5 from Oded Arbel --- (In reply to Komorebi from comment #3) > There's also a workaround for Sway that can be investigated and probably > ported to Kwin. The workaround for Sway seems to me to be the same thing as going to Kwin configuration Window Rules and setting up an app rule with the property "Ignore global shortcuts" - "Force" - "No". Unfortunately, this doesn't work. The same issue I have with the window rule property "No titlebar and frame" (Bug 453977). Apparently for these types of properties (boolean?) setting "Force" - "No" means "don't cause a change of behavior" instead of the expected "prevent the app from making this request", which seems wrong to me. IMHO, if Chrome PWAs actually issue the "Ignore global shortcuts" request - even unnecessarily - then kwin should honor that. But the user should have the option of telling kwin to stop honor such requests for misbehaving apps (like Chrome PWAs) - and the UI for that is already there, we just need it to work. Having that override would be a good resolution for this ticket, IMHO, and the "correct" fix can be left for upstream (i.e. Chrome/ium developers). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409454] Second screen rotated triggers Gwenview to appear on primary screen exceeding borders
https://bugs.kde.org/show_bug.cgi?id=409454 --- Comment #9 from Oded Arbel --- Created attachment 141414 --> https://bugs.kde.org/attachment.cgi?id=141414&action=edit screencast of a repro (In reply to Germano Massullo from comment #8) > I am no longer experiencing this problem > > Plasma 5.22.4 > KDE Frameworks 5.85.0 > Qt 5.15.2 I can still repro using the steps I outlined in comment #7 with latest neon developer: Plasma 5.22.80; Frameworks 5.86.0; Qt 5.15.3. See attached screen cast (I had trouble capturing two screens with my normal tools, so this is an OBS scene that is scaled down and there are various artifacts such as the screens not being aligned properly and for some reason a double cursor on the right screen - not sure what is up with that, but this is 100% a legit capture of the process). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409454] Second screen rotated triggers Gwenview to appear on primary screen exceeding borders
https://bugs.kde.org/show_bug.cgi?id=409454 Oded Arbel changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #10 from Oded Arbel --- The issue reported in Bug 366632 sounds related - though it doesn't appear to be multi-screen related and the fix there is narrowly tailored to the issue if restoring window geometry of previously maximized windows. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409454] Second screen rotated triggers Gwenview to appear on primary screen exceeding borders
https://bugs.kde.org/show_bug.cgi?id=409454 --- Comment #11 from Oded Arbel --- (In reply to Oded Arbel from comment #10) > The issue reported in Bug 366632 sounds related - though it doesn't appear > to be multi-screen related and the fix there is narrowly tailored to the > issue if restoring window geometry of previously maximized windows. Also that issue is about the wayland platform while this issue - even though opened for X11 - is for both X11 and Wayland. Should I open a new ticket with platform-wayland as the component, so hopefully we can get this issue addressed considering much more effort is going into Wayland these days (I'm considering switching myself - giving it another test run). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429784] Dragging an icon over another icon causes a crash
https://bugs.kde.org/show_bug.cgi?id=429784 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #2 from Oded Arbel --- Created attachment 141675 --> https://bugs.kde.org/attachment.cgi?id=141675&action=edit screencast of a repro attempt I'm not sure I'm following the right steps, but I can't repro with dragging task bar entries. I also couldn't repro the "repeated clicking causes cursor to get stuck in drag mode" at all. Is this still an issue, and if so - can you review the screencast and let me know what I missed in my repro? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442654] New: Dragging a widget across screens drops the widget
https://bugs.kde.org/show_bug.cgi?id=442654 Bug ID: 442654 Summary: Dragging a widget across screens drops the widget Product: plasmashell Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: o...@geek.co.il CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When trying to drag a Plasma widget from one screen to another, as soon as the cursor enters the new screen, the widget is dropped and the dragging ends. Also, in my testing of dragging between differently sized and differently form-factored screen, in the new screen the widget gets resized to a smaller size (maybe a default size) which is often too small to correctly render the content. I'm not sure if its a related issue or not. STEPS TO REPRODUCE 1. Have two screens. 2. Add a widget on one screen. 3. Grab and drag the widget to the second screen. OBSERVED RESULT Dragging abruptly ends, without releasing the mouse button, when entering the new screen. EXPECTED RESULT Dragging should continue until the mouse button is released. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442657] New: First RMB click on "not active" desktop screen is ignored.
https://bugs.kde.org/show_bug.cgi?id=442657 Bug ID: 442657 Summary: First RMB click on "not active" desktop screen is ignored. Product: plasmashell Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: o...@geek.co.il CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY With multiple screens, Plasma seems to track which desktop containment is active, and when right clicking on a desktop containment on another screen - the first click makes the new desktop containment active but is otherwise ignored (i.e. when using RMB, the desktop menu is *not* opened). This reproduction is on Wayland - I'm not sure if this is an issue with X11 as well. STEPS TO REPRODUCE 1. Have two screens, where in both the desktop is visible. 2. Click the desktop on one screen (doesn't matter which mouse button). 3. Right click the desktop on the other screen. OBSERVED RESULT Nothing happens (if it is possible to observe whether the first desktop is "active", we can see it becomes inactive - see below for more details). EXPECTED RESULT The desktop context menu should be opened. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION It is sometimes possible to observe whether a desktop containment is "active" - when using the "Folder View" layout, we can select one of the file icons on the desktop and see whether it is active or not - i.e. when "activating" the other desktop containment, the icon selection box changes to "non focused selection" rendering (similar to how it looks when selecting a desktop file icon and then selecting a window). The problem goes away if you either purposefully activate the other desktop containment (e.g. by clicking it) before using RMB, or if you activate a window before using RMB on the other desktop. Interacting with panels on the other screen does not appear to "activate" the desktop in this regard (i.e. after interacting with a panel RMB cannot open the desktop context menu), while interacting with widgets on the other screen does work to "activate" the desktop. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 442346] Yakuake does not follow mouse when the mouse is on a second monitor and Wayland
https://bugs.kde.org/show_bug.cgi?id=442346 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Oded Arbel --- *** This bug has been marked as a duplicate of bug 440825 *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440825] open at mouse location not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=440825 Oded Arbel changed: What|Removed |Added CC||mig...@rozsas.eng.br --- Comment #1 from Oded Arbel --- *** Bug 442346 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 411681] Yakuake always shown on second monitor on wayland
https://bugs.kde.org/show_bug.cgi?id=411681 Oded Arbel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||o...@geek.co.il --- Comment #13 from Oded Arbel --- *** This bug has been marked as a duplicate of bug 440825 *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440825] open at mouse location not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=440825 Oded Arbel changed: What|Removed |Added CC||todaywe@nuke.africa --- Comment #2 from Oded Arbel --- *** Bug 411681 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428383] [Wayland] Yakuake is not minimizing/hiding when clicking on empty area of desktop
https://bugs.kde.org/show_bug.cgi?id=428383 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #4 from Oded Arbel --- *** This bug has been marked as a duplicate of bug 380497 *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 Oded Arbel changed: What|Removed |Added CC||avinashrocks1...@gmail.com --- Comment #12 from Oded Arbel --- *** Bug 428383 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 381541] KWin/Wayland integration broken with Qt >= 5.8
https://bugs.kde.org/show_bug.cgi?id=381541 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #2 from Oded Arbel --- Still an issue: Yakuake 21.11.70; Plasma 5.23.80; Frameworks 5.86.0; Qt 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #13 from Oded Arbel --- (In reply to Firlaev-Hans from comment #11) > I admit that I have very little understanding about how all this works but > after digging in the source code a bit it appears that the problem may not > be in Yakuake itself, but in KDE Frameworks, specifically in KWindowSystem. > > To detect a focus loss, Yakuake connects to the activeWindowChanged signal > in KWindowSystem, which exists in platforms/xcb but not platforms/wayland Looking at https://invent.kde.org/frameworks/kwindowsystem/-/blob/master/src/platforms/wayland/kwindowsystem.cpp the implementation is pretty bare - it doesn't emit any of the signals documented in https://api.kde.org/frameworks/kwindowsystem/html/classKWindowSystem.html that other platforms (even Windows) do emit. It seems likely that all of Yakuake's Wayland issues (this, the bucket list in Bug 433606, as well as Bug 433171, Bug 402634 and Bug 413636, to name a few) are caused by the non-existence of KWindowSystem Wayland's implementation. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 442662] KWindowSystem on Wayland is missing many signals, some of which are needed by Yakuake
https://bugs.kde.org/show_bug.cgi?id=442662 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397662] Activity Switcher not cycles through more than two activities on Wayland with Meta+Tab shortcut
https://bugs.kde.org/show_bug.cgi?id=397662 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #6 from Oded Arbel --- The activity switcher behavior is still very much broken under Wayland - I think all these issues are related, but I can't be sure: When using the "Walk through activities" shortcut by holding the modifiers (I use a non-default and more complex shortcut with multiple modifiers) and hitting the activation key repeatedly, the following behaviors can be observed - with no discernible reason as to which behavior is happening: - switcher moves to next activity as expected. - switcher cycles back and forth through only two activities (when there are more). - switcher appears to try to switch to the next activity (the selector in the activities bar jumps to the next activity and wallpaper changes briefly) but then immediately goes back to the current one. Sometimes hitting the activation key quickly multiple times can coax one of the other behaviors to appear, though for me the last one is the most consistent. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442654] Dragging a widget across screens drops the widget
https://bugs.kde.org/show_bug.cgi?id=442654 --- Comment #2 from Oded Arbel --- (In reply to Nate Graham from comment #1) > X11 or Wayland? Apparently both (I reported on it from Wayland, but on X11 its the same issue). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435743] REGRESSION: Switching activities does not remember current desktop
https://bugs.kde.org/show_bug.cgi?id=435743 Oded Arbel changed: What|Removed |Added Summary|Wayland: Switching |REGRESSION: Switching |activities does not |activities does not |remember current desktop|remember current desktop --- Comment #1 from Oded Arbel --- This issue had apparently been ported back to X11 - where kwin_x11 used to remember a different current virtual desktop for each activity, it is now also affected. This could be a recent change in kwin_x11 - I'm running on neon unstable, currently with kwin-x11 4:5.22.5+p20.04+tunstable+git20210923.0148-0 , or it could be an old behavior that was triggered by the fact that yesterday I removed all of my activities and recreated them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435743] REGRESSION: Switching activities does not remember current virtual desktop
https://bugs.kde.org/show_bug.cgi?id=435743 Oded Arbel changed: What|Removed |Added Summary|REGRESSION: Switching |REGRESSION: Switching |activities does not |activities does not |remember current desktop|remember current virtual ||desktop --- Comment #4 from Oded Arbel --- (In reply to Daniel P Pflager from comment #2) > I have observed a similar behavior with Plasma on X11. > > I have a dozen activities at least. Each one has a different custom folder. I think the issue you are discussing here is not the issue I reported - I was worried about the virtual desktop selected (i.e. you switch to desktop 1, change activity, switch to desktop 4, change back, you'd expect to be at desktop 1 and not 4). You seem to be talking about what the folder containment on activity desktop is set for - it seems to be a serious issue that should be reported, so I recommend you open a new ticket for that. Up until now I only use folder containment on one of my activities, so I didn't encounter it - but I will check. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 411681] Yakuake always shown on second monitor on wayland
https://bugs.kde.org/show_bug.cgi?id=411681 --- Comment #17 from Oded Arbel --- (In reply to Damian Kaczmarek from comment #15) > So web browsers already solved this. Any website can ask for permission to > use the camera, record audio, etc. I imagine KWin perhaps having a DBus API > for requesting permission to get the "current screen", user then allows > Yakuake to use it and voilà. There is an API, its called KWindowSystem. Unfortunately, it is completely unimplemented for Wayland - see bug 442662. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435743] REGRESSION: Switching activities does not remember current virtual desktop
https://bugs.kde.org/show_bug.cgi?id=435743 --- Comment #5 from Oded Arbel --- I forgot to mention that as part of the reproduction, you have to open System Settings, go to Workspace Behavior -> Activities -> Switching and check "Current Desktop: remember for each activity". Apparently this is not the default. I re-checked that on Plasma 5.18 in Kubuntu 20.04, and Plasma 5.21 in Kubuntu 21.04, "remember for each activity" works for X11 and doesn't work for Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435743] Wayland: Switching activities does not remember current virtual desktop
https://bugs.kde.org/show_bug.cgi?id=435743
Oded Arbel changed:
What|Removed |Added
Summary|REGRESSION: Switching |Wayland: Switching
|activities does not |activities does not
|remember current virtual|remember current virtual
|desktop |desktop
--- Comment #6 from Oded Arbel ---
Apparently the problem on X11 is that the Activity Manager service plugin
"org.kde.ActivityManager.VirtualDesktopSwitch" wasn't loaded for some reason
and executing `qdbus org.kde.ActivityManager /MainApplication
org.kde.ActivityManager.Application.loadPlugin
org.kde.ActivityManager.VirtualDesktopSwitch` solved the problem.
I'm not sure why it was not loaded, but I can see the following lines in the
logs:
8<
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: kf.coreaddons: Checking for
plugins in ("/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1",
"/usr/lib/x86_64-linux-gnu/libexec/kactivitymanagerd/1")
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Plugin Name is "org.kde.ActivityManager.ActivityRunner"
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_activityrunner.so"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Plugin Name is "org.kde.ActivityManager.ActivityTemplates"
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_activitytemplates.so"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Plugin Name is "org.kde.ActivityManager.EventSpy"
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_eventspy.so"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Plugin Name is "org.kde.ActivityManager.GlobalShortcuts"
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_globalshortcuts.so"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Plugin Name is "org.kde.ActivityManager.GtkEventSpy"
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_gtk_eventspy.so"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Plugin Name is "org.kde.ActivityManager.RunApplication"
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_runapplication.so"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Plugin Name is "org.kde.ActivityManager.SLC"
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_slc.so"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Plugin Name is "org.kde.ActivityManager.ResourceScoring"
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_sqlite.so"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Plugin Name is "org.kde.ActivityManager.VirtualDesktopSwitch"
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_virtualdesktopswitch.so"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Found 8 enabled plugins:
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Setting the name of 0x558b20255aa0 to
"org.kde.ActivityManager.ActivityRunner"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
[ OK ] loaded: "org.kde.ActivityManager.ActivityRunner"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Setting the name of 0x558b2022bed0 to
"org.kde.ActivityManager.ActivityTemplates"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
[ OK ] loaded: "org.kde.ActivityManager.ActivityTemplates"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
[ OK ] loaded: "org.kde.ActivityManager.EventSpy"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
[ OK ] loaded: "org.kde.ActivityManager.GlobalShortcuts"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
[ OK ] loaded: "org.kde.ActivityManager.GtkEventSpy"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
Setting the name of 0x558b2029a190 to
"org.kde.ActivityManager.RunApplication"
Sep 26 21:08:31 vesho kactivitymanagerd[4524]: org.kde.kactivities.application:
[ OK
[kwin] [Bug 439183] kwin wayland with latest activity integration doesn't "remember current virtual desktop used" when switching
https://bugs.kde.org/show_bug.cgi?id=439183 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #6 from Oded Arbel --- *** Bug 435743 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435743] Wayland: Switching activities does not remember current virtual desktop
https://bugs.kde.org/show_bug.cgi?id=435743 Oded Arbel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #7 from Oded Arbel --- With all the plugins loaded, the Wayland work in https://invent.kde.org/plasma/kactivitymanagerd/-/merge_requests/16 - for Plasma 5.23 - also appears to be working well, so the "remember for each activity" setting does now work for Wayland. That MR was merged at the beginning of the month, so it stands to reason it didn't work when this ticket was first opened - thank you David Redondo and David Edmundson! *** This bug has been marked as a duplicate of bug 439183 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450966] New: Dolphin crashes when dragging image from Gwenview over the details view
https://bugs.kde.org/show_bug.cgi?id=450966 Bug ID: 450966 Summary: Dolphin crashes when dragging image from Gwenview over the details view Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: o...@geek.co.il CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.03.70) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.13.0-30-generic x86_64 Windowing System: X11 Distribution: Ubuntu 21.10 DrKonqi: 5.24.80 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Dragged an image showing in gwenview (full image, not from folder browsing). The crash has been reproduced multiple times. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 KFilePlacesViewDelegate::previousVisibleIndex (this=this@entry=0x562571808470, index=...) at ./src/filewidgets/kfileplacesview.cpp:476 #5 0x7fe42d3c7fdb in KFilePlacesViewDelegate::previousVisibleIndex (index=..., this=0x562571808470) at ./src/filewidgets/kfileplacesview.cpp:494 #6 KFilePlacesViewDelegate::indexIsSectionHeader (index=..., this=0x562571808470) at ./src/filewidgets/kfileplacesview.cpp:495 #7 KFilePlacesViewDelegate::indexIsSectionHeader (this=0x562571808470, index=...) at ./src/filewidgets/kfileplacesview.cpp:488 #8 0x7fe42d3d130f in KFilePlacesView::paintEvent (this=0x56257181a3e0, event=) at /usr/include/c++/9/bits/unique_ptr.h:154 #9 0x7fe42bdeacf6 in QWidget::event (this=this@entry=0x56257181a3e0, event=event@entry=0x7fffa845a130) at kernel/qwidget.cpp:9020 #10 0x7fe42be9b3e2 in QFrame::event (this=0x56257181a3e0, e=0x7fffa845a130) at widgets/qframe.cpp:550 #11 0x7fe42c025f12 in QAbstractItemView::viewportEvent (this=0x56257181a3e0, event=0x7fffa845a130) at itemviews/qabstractitemview.cpp:1746 #12 0x7fe42b2c9f03 in QCoreApplicationPrivate::sendThroughObjectEventFilters (event=, receiver=) at kernel/qcoreapplication.cpp:1190 #13 QCoreApplicationPrivate::sendThroughObjectEventFilters (receiver=receiver@entry=0x5625717b88f0, event=event@entry=0x7fffa845a130) at kernel/qcoreapplication.cpp:1179 #14 0x7fe42bda7db2 in QApplicationPrivate::notify_helper (this=this@entry=0x5625711d7850, receiver=receiver@entry=0x5625717b88f0, e=e@entry=0x7fffa845a130) at kernel/qapplication.cpp:3626 #15 0x7fe42bdb0bb8 in QApplication::notify (this=0x7fffa845b620, receiver=0x5625717b88f0, e=0x7fffa845a130) at kernel/qapplication.cpp:3156 #16 0x7fe42b2ca19a in QCoreApplication::notifyInternal2 (receiver=0x5625717b88f0, event=0x7fffa845a130) at kernel/qcoreapplication.cpp:1064 #17 0x7fe42bde30aa in QWidgetPrivate::sendPaintEvent (this=this@entry=0x5625717aebb0, toBePainted=...) at kernel/qwidget.cpp:5467 #18 0x7fe42bde38d2 in QWidgetPrivate::drawWidget (this=0x5625717aebb0, pdev=0x562572121130, rgn=..., offset=..., flags=..., sharedPainter=, repaintManager=) at kernel/qwidget.cpp:5417 #19 0x7fe42bde4cd3 in QWidgetPrivate::paintSiblingsRecursive (this=this@entry=0x5625717affc0, pdev=pdev@entry=0x562572121130, siblings=..., index=, rgn=..., offset=..., flags=..., sharedPainter=0x0, repaintManager=0x562571bdacf0) at kernel/qwidget.cpp:5598 #20 0x7fe42bde35ec in QWidgetPrivate::drawWidget (this=0x5625717affc0, pdev=0x562572121130, rgn=..., offset=..., flags=..., sharedPainter=, repaintManager=) at kernel/qwidget.cpp:5458 #21 0x7fe42bde4cd3 in QWidgetPrivate::paintSiblingsRecursive (this=this@entry=0x562571c91910, pdev=pdev@entry=0x562572121130, siblings=..., index=, rgn=..., offset=..., flags=..., sharedPainter=0x0, repaintManager=0x562571bdacf0) at kernel/qwidget.cpp:5598 #22 0x7fe42bde35ec in QWidgetPrivate::drawWidget (this=0x562571c91910, pdev=0x562572121130, rgn=..., offset=..., flags=..., sharedPainter=, repaintManager=) at kernel/qwidget.cpp:5458 #23 0x7fe42bde4cd3 in QWidgetPrivate::paintSiblingsRecursive (this=this@entry=0x562571322200, pdev=pdev@entry=0x562572121130, siblings=..., index=, rgn=..., offset=..., flags=..., sharedPainter=0x0, repaintManager=0x562571bdacf0) at kernel/qwidget.cpp:5598 #24 0x7fe42bde35ec in QWidgetPrivate::drawWidget (this=this@entry=0x562571322200, pdev=0x562572121130, rgn=..., offset=..., flags=..., flags@entry=..., sharedPainter=sharedPainter@entry=0x0, repaintManager=) at kernel/qwidget.cpp:5458 #25 0x7fe42bdba499 in QWidgetRepaintManager::paintAndFlush (this=this@entry=0x562571bdacf0) at kernel/qwidgetrepaintmanager.cpp:1009 #26 0x7fe42bdbaf34 in QWidgetRepaintManager::sync (this=0x562571bdacf0) at kernel/qwidgetrepaintmanager.cpp:770 #27 0x7fe42bde4775 in QWidgetPrivate::syncBacki
[dolphin] [Bug 450966] Dolphin crashes when dragging image from Gwenview over the details view
https://bugs.kde.org/show_bug.cgi?id=450966 --- Comment #1 from Oded Arbel --- I cannot reproduce this issue with the "places" panel closed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 400047] Stat jobs that take longer than 500ms trigger unnecessary and unactionable "Examining: finished" notifications
https://bugs.kde.org/show_bug.cgi?id=400047 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 438153] [wayland] Tag editor combo box pull down menu sometimes appears as a window
https://bugs.kde.org/show_bug.cgi?id=438153 Oded Arbel changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Oded Arbel --- After the fix for bug #442375 I no longer experience this issue. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 433171] Yakuake Opens, but does not close under wayland
https://bugs.kde.org/show_bug.cgi?id=433171 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #2 from Oded Arbel --- Recently there were various changes to how Yakuake handles opening and closing on Wayland and X11 - can you please check if this is still an issue? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 393844] Yakuake always opens regardless of preferences
https://bugs.kde.org/show_bug.cgi?id=393844 Oded Arbel changed: What|Removed |Added Version|unspecified |master Assignee|h...@kde.org|k...@davidedmundson.co.uk Component|general |general Product|yakuake |ksmserver CC||o...@geek.co.il, ||plasma-b...@kde.org --- Comment #7 from Oded Arbel --- (In reply to Claudius Ellsel from comment #6) > To me that only happens on X11. Can anybody confirm? Happens to me on Wayland as well. Moving to session management as this is clearly not a Yakuake issue (I'm imaging there can be a workaround deployed in Yakuake, but I don't think its the Right Thing). -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 393844] Yakuake always opens regardless of preferences
https://bugs.kde.org/show_bug.cgi?id=393844 --- Comment #8 from Oded Arbel --- *** Bug 423163 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 423163] Yakuake opens expanded in Wayland when changed to an X session in between
https://bugs.kde.org/show_bug.cgi?id=423163 Oded Arbel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||o...@geek.co.il --- Comment #2 from Oded Arbel --- Dup of bug #393844, as discussed there. *** This bug has been marked as a duplicate of bug 393844 *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 386358] Keep window open when it loses focus (Doens't working)
https://bugs.kde.org/show_bug.cgi?id=386358 Oded Arbel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||o...@geek.co.il --- Comment #4 from Oded Arbel --- Dup of #380497, as discussed. *** This bug has been marked as a duplicate of bug 380497 *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 Oded Arbel changed: What|Removed |Added CC||ricardo.calimanis@sogkids.o ||rg --- Comment #18 from Oded Arbel --- *** Bug 386358 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 402634] Hotkey to open/retract yakuake doesn't work in Wayland if flag "Use Open/Retract action to focus window" is set
https://bugs.kde.org/show_bug.cgi?id=402634 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #1 from Oded Arbel --- Can repro on Neon unstable, Plasma 5.23.3, Frameworks 5.87, Qt 5.15.2. Also "Keep window above" doesn't work on Wayland (that is possibly bug #381541), which in combination with this issue makes "keep window open when it loses focus" almost useless, so I turned it off. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 442662] KWindowSystem on Wayland is missing many signals, some of which are needed by Yakuake
https://bugs.kde.org/show_bug.cgi?id=442662 --- Comment #2 from Oded Arbel --- (In reply to David Edmundson from comment #1) > Lets split this up as individual bugs on yakuake. There are already individual bugs on Yakuake - this ticket was to upstream all the issues that arise from Yakuake depending on KWindowSystem signaling for several features. @Firlaev-Hans - here is a summary of a discussion I had today on #plasma:kde.org: 8< David Redondo (regarding the activeWindowChanged() signal): The signal will never be more useful than QGuiApplication::focusWindowChanged because on wayland the only thing the application can know if it's focused or not. KWindowSystem was never necessary to know if you have focus zzag: it's a bit difficult. due to kwindowsystem being x11 oriented historically, activewindowchanged can be used to monitor the active window [me: this is a big no-no in Wayland] but yeah, with wayland, kwindowsystem makes sense only for things such as setting blur, server side drop shadows i.e. manipulating your own windows if you want to manage foreign windows, use libtaskmanager we need to deprecate and split a bunch of stuff for kwindowsystem in kf6, but due to being busy with other sutff, I don't think that anybody has started work on it 8< So, yea - Yakuake will either have to find cross-platform way of doing things that it relied on KWindowSystem for before (e.g. QGuiApplication::focusWindowChanged) or implement two different code paths for X11 and Wayland for more complicated things. As an example for this approach, I looked at the MR in https://invent.kde.org/plasma/kactivitymanagerd/-/merge_requests/16 , where KActivityManager's VirtualDesktopSwitchPlugin was modified to test `KWindowSystem::isPlatformX11()` and if so use KWindowSystem, otherwise use a Wayland-specific implementation. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 443292] New: Pasting text with a new line does not submit the command
https://bugs.kde.org/show_bug.cgi?id=443292 Bug ID: 443292 Summary: Pasting text with a new line does not submit the command Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: copy-paste Assignee: konsole-de...@kde.org Reporter: o...@geek.co.il Target Milestone: --- SUMMARY When copying multi-line text and pasting it into the terminal, the new lines do not cause the commands in the text to be executed. STEPS TO REPRODUCE 1. Have a text editor with some commands that can be executed in the terminal, each on a line. 2. With the cursor at the beginning of the file, hold shift and move one line down, selecting the entire line, then copy it to the clipboard. 3. In Konsole paste the text. OBSERVED RESULT After the text is pasted, the cursor is moved to the beginning of the next line in the terminal, but the command is not executed and the command prompt is not shown until the user presses the physical ENTER key. EXPECTED RESULT The new line at the end of the text should execute the command, which should start immediately after pasting and at the end of the execution, a command prompt should be seen - no further user input should be needed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION It used to work in the past. I'm not sure at which release it stopped working. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 443292] Pasting text with a new line does not submit the command
https://bugs.kde.org/show_bug.cgi?id=443292 --- Comment #2 from Oded Arbel --- Couldn't the issue of trickery be solved by a warning dialog to be shown when a user pastes text that contains a new line (with a "don't worry about it anymore" checkbox), like we get when pasting a large text box? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 443292] Pasting text with a new line does not submit the command
https://bugs.kde.org/show_bug.cgi?id=443292 --- Comment #4 from Oded Arbel --- (In reply to Nate Graham from comment #3) > The user would most likely ignore it, as most users don't read dialogs. Yea... make sense :-( -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 439697] Gwenview crashes when rotating image during startup
https://bugs.kde.org/show_bug.cgi?id=439697 --- Comment #1 from Oded Arbel --- Created attachment 142331 --> https://bugs.kde.org/attachment.cgi?id=142331&action=edit New crash information added by DrKonqi gwenview (21.11.70) using Qt 5.15.3 - What I was doing when the application crashed: Undoing a 90 degrees rotation right. This was done almost immediately after startup. -- Backtrace (Reduced): #4 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:391 #5 0x7effd52d9be7 in memcpy (__len=, __src=0x7effb448ec58, __dest=) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 #6 QImage::copy (this=0x56499fc9e3c0, r=...) at image/qimage.cpp:1239 #7 0x7effd6930a25 in Gwenview::RasterImageItem::paint (this=0x5649a00914b0, painter=0x7ffdb76a3010) at ./lib/documentview/rasterimageitem.cpp:106 #8 0x7effd5cc3e2c in QGraphicsScenePrivate::draw (this=this@entry=0x56499f3cea40, item=item@entry=0x5649a00914b0, painter=painter@entry=0x7ffdb76a3010, viewTransform=viewTransform@entry=0x0, transformPtr=, exposedRegion=exposedRegion@entry=0x56499f79d3f0, widget=, opacity=opacity@entry=1, effectTransform=, wasDirtyParentSceneTransform=, drawItem=) at graphicsview/qgraphicsscene.cpp:4981 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 439697] Gwenview crashes when rotating image during startup
https://bugs.kde.org/show_bug.cgi?id=439697 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430440] The "Show in Activities" menu does not work as expected
https://bugs.kde.org/show_bug.cgi?id=430440 --- Comment #11 from Oded Arbel --- (In reply to Gauthier from comment #7) > Should it get marked as resolved? Looking at the MR that was merged, it adds the workaround to the task bar context menu. This issue is about the window operations menu, so the MR does not solve this issue in that it doesn't fix the window operations menu. I'm not sure what is the use case for the task bar right click menu as I almost never use it and there is no keyboard shortcut to get to it. IMHO the window operations menu should be the target for any improved behavior its better accessible by both keyboard and mouse (Fitz law). (In reply to Gauthier from comment #8) > @Oded Have there been any progress on your MR for VDs, and if so, does it > seem likely to also work for activities? I did not move forward with my work on the checkboxed window operations submenus (I'm treating desktops and activities the same for this). I didn't have a lot of time for that, but more than that I'm very confused about the situation - in Kwin Wayland there is a workaround for the desktops menu that is very similar in behavior to https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/231, but not identical, and of course that it wasn't implemented for activities. I think before any additional work is done, there should be some effort to understand what is the UX that we are aiming for and how it should apply to all relevant use cases - wayland, x11, window operations menu, plasma shell task bar menus, activities, desktops, whatever else is relevant. Currently there are too many different behaviors for things that should basically be the same. I'm not sure how/where/when/with who to start such a discussion. On that note, I personally dislike the "dual control" UX that is offered in Wayland windows operation menu and the above mentioned MR: on my systems I have few activities (2 or 3 normally) and many virtual desktops (6 or 8) and while the "checkbox + move to items" is kind of manageable in the activities selection, it is almost unusable for virtual desktops (the wayland window operations desktops menu takes more than half the height of my screen now) - it actually takes noticeable time and thought to locate the menu option I need in order to just move this one window to desktop 4. I believe we can do better, and would like to have a discussion about that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430440] The "Show in Activities" menu does not work as expected
https://bugs.kde.org/show_bug.cgi?id=430440 --- Comment #15 from Oded Arbel --- (In reply to Gauthier from comment #14) > > The lack of keyboard shortcut to > > "move a window to activity X" > > > as been pointed out in Bug 411688 IMO, the ability of the user to assign a custom keyboard shortcut to a "move to activity" operation does not solve the inaccessibility of the taskbar to keyboard operation. Please don't conflate "being able to assign keyboard shortcuts" with "being able to use the keyboard to select and activate things". My point is that I understand that some people can make a good use the taskbar with a mouse, but as someone who prefers to use the keyboard - the taskbar is completely inaccessible to me and I use it as visual reference only. As such, adding capabilities to the taskbar is *not* a good replacement to missing window operations menu functionality (the window operations menu is *very* keyboard accessible). (In reply to Gauthier from comment #13) > Would it be possible to only keep the tick boxes, but ensure that the menu > stays open AND changes are only applied after either: the mouse moves out of > the menu (if using the mouse), or the ESC key is pressed (if navigating > using the keyboard)? Tying "apply operations" to mouse movement is a problematic proposition - some pointing devices (and some people) are very inaccurate and having a wrong move trigger an operation that takes significant effort to revert (its not just CTRL+Z), will be very frustrating to the user. ESC would work, but you do want additionally something that is both discoverable and can be operated by a mouse. I thought about this a bit and in the context of a menu we are precluded from a lot of guided interaction we can do with dialogs: you can't have explanatory text and you can't have an "apply" button. There are some use cases that are hard to do "properly" in a menu - so can we just stop pretending to care about them? I want to support the following use cases: 1. Show the window in all activities. 2. Add the window to this one additional activity. 3. Move the window to this one other activity. I don't want to support the following use cases as I think they are niche, can be achieved with a combination of actions (1), (2) and (3) (albeit slower, as the menu would need to be reopened), and not worth sacrificing the usability of (1), (2) and (3) for: 4. Add the window to 2 or more additional activities. 5. Move the window to 2 or more other activities. (all the above also applies to virtual desktops, as appropriate, as it is basically the same thing on a different axis). What do you think? Do you often find yourself moving a window from the current activity to 2 other activities (as described in comment #2)? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397662] Activity Switcher not cycles through more than two activities on Wayland with Meta+Tab shortcut
https://bugs.kde.org/show_bug.cgi?id=397662 --- Comment #8 from Oded Arbel --- (In reply to Shavez from comment #7) > Just updated to 5.23 and the Activity Switcher adds an entry to task manager > sometimes when I switch activities in quick successions with some windows > open in all activities. This happens both in X and Wayland. Huh! I was wandering what that new window, labeled "Plasma" with zero width, that started appearing recently. I didn't tie it to the activity switcher, but it looks like you are right - if I switch activities back and forth using the "Walk through activities" shortcut, I can see a new task manager entry labeled "Plasma" that disappears after a few seconds - and sometimes it doesn't disappear but remains until I close it with the taskbar context menu. This may warrant opening a new ticket? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443941] Activity switcher creates task manager entry when using "Walk through activities" shortcut
https://bugs.kde.org/show_bug.cgi?id=443941 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443968] When switching activities, sometimes a tiny "Plasma Desktop Workspace" window appears
https://bugs.kde.org/show_bug.cgi?id=443968 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #4 from Oded Arbel --- Can confirm on X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438273] Titlebar colors not changed correctly when switching from a header-color-using color scheme to a non-header-color-using color scheme
https://bugs.kde.org/show_bug.cgi?id=438273 --- Comment #12 from Oded Arbel --- (In reply to Nate Graham from comment #9) > In my case, I have a kdeglobals file located at > ~/.config/kdedefaults/kdeglobals which has color data in it for Breeze > Light. I don't have a ~/.config/kdedefaults in my system, but also - with the current Neon unstable builds - I can no longer reproduce the issue I reported on in comment #4. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 432924] New: drkonqi crash on wayland
https://bugs.kde.org/show_bug.cgi?id=432924 Bug ID: 432924 Summary: drkonqi crash on wayland Product: drkonqi Version: 5.20.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: o...@geek.co.il Target Milestone: --- SUMMARY Running 5.20.5+p20.04+git20210131.0022-0 , I get a crash notification and when activated I get a message that the KDE crash handler closed unexpectedly Running neon unstable, full updated. Here's the backtrace: Application: The KDE Crash Handler (drkonqi), signal: Segmentation fault [New LWP 13282] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f808d024aff in __GI___poll (fds=0x7e5d34e8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f8089b742c0 (LWP 13218))] Thread 2 (Thread 0x7f808804a700 (LWP 13282)): #0 0x7f808d024aff in __GI___poll (fds=0x7f8080005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f808bfa918e in g_main_context_poll (priority=, n_fds=1, fds=0x7f8080005240, timeout=, context=0x7f808c20) at ../../../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7f808c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4042 #3 0x7f808bfa92c3 in g_main_context_iteration (context=0x7f808c20, may_block=may_block@entry=1) at ../../../glib/gmain.c:4108 #4 0x7f808d60afbb in QEventDispatcherGlib::processEvents (this=0x7f808b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f808d5af1ab in QEventLoop::exec (this=this@entry=0x7f8088049cb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f808d3c9a12 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f808df34f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f808d3cabac in QThreadPrivate::start (arg=0x7f808dfb8d80) at thread/qthread_unix.cpp:329 #9 0x7f808c902609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f808d031293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f8089b742c0 (LWP 13218)): [KCrash Handler] #4 wl_proxy_marshal_constructor (proxy=0x0, opcode=0, interface=0x7f808bf4b640 ) at ../src/wayland-client.c:829 #5 0x7f808be64067 in QtWaylandClient::QWaylandDisplay::createSurface (this=, handle=handle@entry=0x5593cce289d0) at qwaylanddisplay.cpp:96 #6 0x7f808be78e0a in QtWaylandClient::QWaylandSurface::QWaylandSurface (this=0x5593cce289d0, display=) at qwaylandsurface.cpp:50 #7 0x7f808be6a8ba in QtWaylandClient::QWaylandWindow::initializeWlSurface (this=this@entry=0x5593cce05490) at qwaylandwindow.cpp:213 #8 0x7f808be6c096 in QtWaylandClient::QWaylandWindow::QWaylandWindow (this=0x5593cce05490, window=0x5593cceb13d0, display=0x5593ccb46940) at qwaylandwindow.cpp:93 #9 0x7f808be76f3d in QtWaylandClient::QWaylandShmWindow::QWaylandShmWindow (this=0x5593cce05490, window=, display=) at qwaylandshmwindow.cpp:52 #10 0x7f808be54b79 in QtWaylandClient::QWaylandIntegration::createPlatformWindow (this=, window=0x5593cceb13d0) at qwaylandintegration.cpp:171 #11 0x7f808d99c3f4 in QWindowPrivate::create(bool, unsigned long long) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7f808e2128b8 in QWidgetPrivate::create (this=this@entry=0x5593ccb700a0) at kernel/qwidget.cpp:1314 #13 0x7f808e212ebe in QWidget::create (this=0x5593ccca46d0, window=, initializeWindow=, destroyOldWindow=) at kernel/qwidget.cpp:1179 #14 0x7f808e22058b in QWidgetPrivate::setVisible (this=0x5593ccb700a0, visible=) at kernel/qwidget.cpp:8062 #15 0x7f808e220966 in QWidget::setVisible (this=this@entry=0x5593ccca46d0, visible=visible@entry=true) at kernel/qwidget.cpp:8043 #16 0x7f808e3e9cc8 in QDialog::setVisible (this=0x5593ccca46d0, visible=) at dialogs/qdialog.cpp:787 #17 0x5593cc44e4c1 in (anonymous namespace)::openDrKonqiDialog () at ./src/main.cpp:54 #18 0x5593cc44d8de in main (argc=, argv=) at ./src/main.cpp:219 [Inferior 1 (process 13218) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 431155] System Monitor crahes when viewing process list
https://bugs.kde.org/show_bug.cgi?id=431155 Oded Arbel changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Oded Arbel --- I can't say I know exactly what caused this issue, but I did try some more repro and this hadn't reproduced for me for a while, so closing for now. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 426307] quick edit Exif/IPTC/XMP tags tags
https://bugs.kde.org/show_bug.cgi?id=426307 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #1 from Oded Arbel --- (In reply to Alexander Fieroch from comment #0) > ... The disadvantage is > when you copy/move an image with additional information like rating or a > description to another computer these information are lost. The information is stored in xattr, so if you copy the image to another xattr supporting storage, all the information will be kept. That being said, propagating this data to image-file-specific meta-data storage would be a good idea. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 426800] New: [Neon unstable] tag editor starts with the first (alphabetically) tag already entered
https://bugs.kde.org/show_bug.cgi?id=426800 Bug ID: 426800 Summary: [Neon unstable] tag editor starts with the first (alphabetically) tag already entered Product: gwenview Version: Other (add details in bug description) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: o...@geek.co.il Target Milestone: --- Created attachment 131825 --> https://bugs.kde.org/attachment.cgi?id=131825&action=edit screenshot showing pre-filled text SUMMARY This issue started appearing about a week ago in Neon unstable builds: when opening the tag editor, the text edit box at the bottom is pre-filled with some text, so that if you want to put in another tag you have to first delete what is in there. The pre-filled text seems to be the first tag, in alphabetical order, from the Baloo tag database. As I have several hundred different tags in use on my system, the pre-populated text is very unlikely to be useful and it just adds another hassle. STEPS TO REPRODUCE 1. Have some tags already in the system and indexed. 2. Open an image file with Gwenview 3. Click "Edit" in the info pane under "Tags" or hit CTRL+T OBSERVED RESULT The tag editor's text box already has some text in it, which is unselected and the cursor positioned immediately after that - so any editing that isn't accepting the pre-filled text has to start by erasing the text. EXPECTED RESULT The tag editor's text box should be focused and empty. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I'm not sure what was the intent with having some text pre-filled, but if it is to speed up entry (and I think that is misguided as the chosen pre-filled text is very unlikely to be usable) then having that text also selected would be a better behavior - as quick entry can still be accomplished by just hitting ENTER while if the user is not interested in the pre-filled text, they can just start typing. I still think that choosing an arbitrary tag to be pre-filled is more confusing than helpful and the suggestion drop down menu is enough of a help for quick entry. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 426800] [Neon unstable] tag editor starts with the first (alphabetically) tag already entered
https://bugs.kde.org/show_bug.cgi?id=426800 --- Comment #1 from Oded Arbel --- Looking a bit more into the code, I can't identify a change in Gwenview code that would cause this, and I think this may be a behavior change in Qt. I'm still investigating. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 426800] [Neon unstable] tag editor starts with the first (alphabetically) tag already entered
https://bugs.kde.org/show_bug.cgi?id=426800 --- Comment #2 from Oded Arbel --- The problem seems to be a behavior change in Qt 5.15.0 (regression?) and specifically this commit: https://code.qt.io/cgit/qt/qtbase.git/commit/src/widgets/widgets/qcombobox.cpp?id=a4ea0d9eacd574a6a96f70b138dcb111e9d11d21 where before an editable QComboBox just created had its current index set to -1 but with that commit, `setModel()` would call `trySetValidIndex()` and that defaults to setting the current index to 0. I have a workaround MR in invent. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 426800] [Neon unstable] tag editor starts with the first (alphabetically) tag already entered
https://bugs.kde.org/show_bug.cgi?id=426800 --- Comment #3 from Oded Arbel --- MR: https://invent.kde.org/graphics/gwenview/-/merge_requests/13 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 426820] New: kdeconnectd occasionally crashes
https://bugs.kde.org/show_bug.cgi?id=426820 Bug ID: 426820 Summary: kdeconnectd occasionally crashes Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: o...@geek.co.il Target Milestone: --- SUMMARY I have kdeconnectd crashing a few times a day. As far as I'm aware it is not in response to anything I specifically do, but Android events that are relevant to kdeconnect happen all the time, so... I'm running Neon unstable fully up to date. Here is the relevant crash report: Thread 1 (Thread 0x7f91324fe800 (LWP 3819630)): [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f9135a62859 in __GI_abort () at abort.c:79 #6 0x7f9134e5eed2 in _dbus_abort () at ../../../dbus/dbus-sysdeps.c:93 #7 0x7f9134e81570 in _dbus_warn_check_failed (format=format@entry=0x7f9134e91dc8 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at ../../../dbus/dbus-internals.c:281 #8 0x7f9134e81cde in _dbus_warn_return_if_fail (function=function@entry=0x7f9134e906d0 <__func__.5446> "dbus_message_iter_append_basic", assertion=assertion@entry=0x7f9134e8fffe "*bool_p == 0 || *bool_p == 1", file=file@entry=0x7f9134e8ff3d "../../../dbus/dbus-message.c", line=line@entry=2777) at ../../../dbus/dbus-internals.c:936 #9 0x7f9134e726a9 in dbus_message_iter_append_basic (value=0x7ffdd9f04300, type=98, iter=0x7ffdd9f04440) at ../../../dbus/dbus-message.c:2777 #10 dbus_message_iter_append_basic (iter=iter@entry=0x7ffdd9f04440, type=type@entry=98, value=value@entry=0x7ffdd9f04300) at ../../../dbus/dbus-message.c:2732 #11 0x7f91364191b3 in q_dbus_message_iter_append_basic (value=0x7ffdd9f04300, type=98, iter=0x7ffdd9f04440) at qdbus_symbols_p.h:336 #12 qIterAppend (arg=0x7ffdd9f04300, type=98, ba=, it=0x7ffdd9f04440) at qdbusmarshaller.cpp:54 #13 QDBusMarshaller::append (arg=, this=0x7ffdd9f04420) at qdbusmarshaller.cpp:79 #14 QDBusMarshaller::appendVariantInternal (this=0x7ffdd9f04420, arg=...) at qdbusmarshaller.cpp:438 #15 0x7f913641a9c6 in QDBusMarshaller::append (this=this@entry=0x7ffdd9f04660, arg=...) at qdbusmarshaller.cpp:221 #16 0x7f91364189b0 in QDBusMarshaller::appendVariantInternal (this=this@entry=0x7ffdd9f04660, arg=...) at ../../include/QtDBus/../../src/dbus/qdbusextratypes.h:164 #17 0x7f91363e2c2f in QDBusMessagePrivate::toDBusMessage (message=..., capabilities=..., error=error@entry=0x7ffdd9f04800) at ../../include/QtCore/../../src/corelib/tools/qlist.h:313 #18 0x7f91363d0fa8 in QDBusConnectionPrivate::send (this=0x7f9124003a00, message=...) at qdbusintegrator.cpp:1931 #19 0x7f91363d5de0 in QDBusConnectionPrivate::activateInternalFilters (this=this@entry=0x7f9124003a00, node=..., msg=...) at qdbusintegrator.cpp:1423 #20 0x7f91363dbd87 in QDBusConnectionPrivate::activateObject (pathStartPos=, msg=..., node=..., this=0x7f9124003a00) at qdbusintegrator.cpp:1495 #21 QDBusConnectionPrivate::activateObject (this=0x7f9124003a00, node=..., msg=..., pathStartPos=) at qdbusintegrator.cpp:1436 #22 0x7f91363def6c in QDBusActivateObjectEvent::placeMetaCall (this=0x7f91240ca830) at qdbusintegrator.cpp:1606 #23 0x7f91360f0129 in QObject::event (this=0x5585114b8cc0, e=0x7f91240ca830) at kernel/qobject.cpp:1314 #24 0x7f9136c98cc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f9136ca1c70 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f91360c26aa in QCoreApplication::notifyInternal2 (receiver=0x5585114b8cc0, event=0x7f91240ca830) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #27 0x7f91360c4fa1 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x558510f3aa60) at kernel/qcoreapplication.cpp:1815 #28 0x7f913611d837 in postEventSourceDispatch (s=0x558511063450) at kernel/qeventdispatcher_glib.cpp:277 #29 0x7f9134748fbd in g_main_dispatch (context=0x7f912c005000) at ../../../glib/gmain.c:3309 #30 g_main_context_dispatch (context=context@entry=0x7f912c005000) at ../../../glib/gmain.c:3974 #31 0x7f9134749240 in g_main_context_iterate (context=context@entry=0x7f912c005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4047 #32 0x7f91347492e3 in g_main_context_iteration (context=0x7f912c005000, may_block=may_block@entry=1) at ../../../glib/gmain.c:4108 #33 0x7f913611ce92 in QEventDispatcherGlib::processEvents (this=0x55851106b290, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #34 0x7f91360c11bb in QEventLoop::exec (this=this@e
[kdeconnect] [Bug 426820] kdeconnectd occasionally crashes
https://bugs.kde.org/show_bug.cgi?id=426820 --- Comment #1 from Oded Arbel --- Created attachment 131857 --> https://bugs.kde.org/attachment.cgi?id=131857&action=edit New crash information added by DrKonqi kdeconnectd (1.4.0) using Qt 5.15.0 - What I was doing when the application crashed: Unlocking the phone. At this I got a KDE connect crash and a bunch of Plasma notifications from the phone - not sure in which order. -- Backtrace (Reduced): #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f6892a90859 in __GI_abort () at abort.c:79 #6 0x7f6891e8ced2 in _dbus_abort () at ../../../dbus/dbus-sysdeps.c:93 #7 0x7f6891eaf570 in _dbus_warn_check_failed (format=format@entry=0x7f6891ebfdc8 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at ../../../dbus/dbus-internals.c:281 #8 0x7f6891eafcde in _dbus_warn_return_if_fail (function=function@entry=0x7f6891ebe6d0 <__func__.5446> "dbus_message_iter_append_basic", assertion=assertion@entry=0x7f6891ebdffe "*bool_p == 0 || *bool_p == 1", file=file@entry=0x7f6891ebdf3d "../../../dbus/dbus-message.c", line=line@entry=2777) at ../../../dbus/dbus-internals.c:936 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 426820] kdeconnectd occasionally crashes
https://bugs.kde.org/show_bug.cgi?id=426820 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 426998] New: Audio settings KCM for pulseaudio has two scrollbars
https://bugs.kde.org/show_bug.cgi?id=426998
Bug ID: 426998
Summary: Audio settings KCM for pulseaudio has two scrollbars
Product: Phonon
Version: 4.11.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: settings
Assignee: sit...@kde.org
Reporter: o...@geek.co.il
CC: myr...@kde.org
Target Milestone: ---
Created attachment 131948
--> https://bugs.kde.org/attachment.cgi?id=131948&action=edit
screenshot showing the problem
SUMMARY
In the default size of the audio KCM (what you get if you press the audio
system tray icon and click the "settings" button), in the "Audio" settings
section (which looks to me to be basically the pulseaudio settings), the tab
content for the various pulseaudio stuff ("Devices", "Applications" and
"Advanced") is overflowing the screen and has a scrollbar inside the tab, but
also the parent widget itself has a scrollbar (see screenshot).
The external scrollbar is only useful for scrolling to the bottom of the tabbed
notebook widget - there are no additional controls after that.
I think that as the tab content does scrolling, the tabbed notebook widget
itself should autosize to the height of the window and should not force the
window to have an additional scrollbar.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.19.90
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.0
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-mediacenter] [Bug 377959] Media Controller hotkeys not working in chrome
https://bugs.kde.org/show_bug.cgi?id=377959 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #1 from Oded Arbel --- This is still an issue with Plasma 5.20. It is caused by the fact that the media controller consume the key press event using its global shortcuts so applications don't see them - I have the same problem with Kodi under Plasma - media buttons just don't work because the media controller eats them and converts them to MPRIS commands ( https://specifications.freedesktop.org/mpris-spec ). Normally it is not an issue with browser applications as media applications are supposed to use the `MediaSession` API (https://developer.mozilla.org/en-US/docs/Web/API/MediaSession) to receive media control events from the operating system and Plasma integrates well with both Chrome and Firefox to forward MPRIS commands to the `MediaSession` API (this also allows scripting, KDE Connect, Plasma media control desktop widgets, etc). I'm not sure this is something that can be fixed, or we even want to fix - the MPRIS setup is the "right thing" for most users and provides excellent experience out of the box with many many applications. The workaround you discovered - disabling the media controller global shortcuts - is the correct one. The fact that the application still received the media key press events after you disabled and re-enabled the media controller global shortcuts *is* a bug and I believe it is already fixed in Plasma 5.20 (I have not been able to reproduce it). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427284] Buttons on logout screen are not working
https://bugs.kde.org/show_bug.cgi?id=427284 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #7 from Oded Arbel --- I have noticed this as well in the last week, running on neon unstable. I though it was related to Plasma SystemD integration that I enabled at about the same time (http://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/) but it isn't - after nuking Plasma config and starting without SystemD (verified) it is still a problem. I checked logs for plasmashell and ksmserver, with and without SystemD and nothing is shown between the time the logout prompt is shown and a while after it is dismissed. It behaves the same regardless of which action logout action is chosen (logout, restart, etc) - which is nothing. I can logout using the KSMServer D-Bus interface - running qdbus org.kde.ksmserver /KSMServer logout 0 3 3 logs out immediately - though I also noticed that session save/restore does not work properly: no applications are reopened when I log back in. This could be related or could be another problem (I have a few additional problems right now with neon unstable, which seem unrelated, so I can't really tell). Running qdbus org.kde.ksmserver /KSMServer logout 1 3 3 shows the logout prompt and behaves like choosing "logout" from the kickoff menu - i.e. pressing "OK" does nothing. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 416194] The Power Management Service appears not to be running
https://bugs.kde.org/show_bug.cgi?id=416194 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #4 from Oded Arbel --- I have the same problem with current neon unstable - powerdevil does not seem to be running after login and the "energy saving" KCM shows the message "Power Management configuration module could not be loaded. The Power Management Service appears not to be running." I checked /etc/xdg/autostart/powerdevil.desktop, which seems to be fine. Executing /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil manually restores the functionality. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 416194] The Power Management Service appears not to be running
https://bugs.kde.org/show_bug.cgi?id=416194 --- Comment #5 from Oded Arbel --- Created attachment 132141 --> https://bugs.kde.org/attachment.cgi?id=132141&action=edit journalctl | grep powerdevil Grepping the journal for "powerdevil" I can only see logs for the KCM and complaints about the DBus service not being available. -- You are receiving this mail because: You are watching all bug changes.
