[krunner] [Bug 480531] New: KRunner inserts search results under the cursor after I've started navigating to others with the keyboard
https://bugs.kde.org/show_bug.cgi?id=480531 Bug ID: 480531 Summary: KRunner inserts search results under the cursor after I've started navigating to others with the keyboard Classification: Plasma Product: krunner Version: 5.27.10 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: philipp.reichm...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY When I type a search string into KRunner, I often begin navigating to the desired item with the keyboard as soon as it appears. However, after I've already started navigating, sometimes other search results appear at the top of the list if KRunner prioritizes them higher. These new items displace my desired item downwards, but the cursor stays at the position it is. Effectively the item under the cursor changes as KRunner inserts new items at the top of the list. Sometimes it happens that I'm already on the desired item, but before I manage to press Enter, KRunner has inserted some other item under the cursor, and when I press Enter, I inadvertently open that other item instead. This is undesirable. As soon as I've started navigating with the keyboard, KRunner should never change the item under the cursor. If KRunner decides to add N items at or above the cursor after I've started navigating with the keyboard. the cursor should move down N positions to stay on the item it was on. At least it should be configurable whether keyboard navigation should take precedence over late list additions or not. STEPS TO REPRODUCE This is hard to reproduce 1:1 because of caching and different priorities apps everywhere, but here is how I have the problem pop up: 1. Open KRunner 2. Start typing "code" (to open VS Code). KRunner starts to build a list of search results. 3. Applications appear first; as VS Code appears under "Applications", press the down arrow key to navigate to it 4. Then folders with names such as "codecs" begin to appear at the top of the list, displacing VS Code towards the bottom 5. I hit Enter and inadvertently open a "codecs" folder that KRunner has inserted under the cursor, not the VS Code that my cursor was on OBSERVED RESULT As new results appear at the top of the list, displacing the ones I already saw and was navigating to, the cursor stays at the position I managed to navigate to (e.g. 2nd or 3rd from the top). But the item at that position under the cursor changes, and the item I wanted to navigate to moves further and further away. EXPECTED RESULT As new results appear at the top of the list, the cursor should stay on the item that I managed to navigate to when new items appeared above it. If N items appear above the cursor, I expect the cursor to move down N positions. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240125 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.1-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476530] New: E-mail, calendar and groupware accounts should be configurable through the Online Accounts KCM in System Settings
https://bugs.kde.org/show_bug.cgi?id=476530 Bug ID: 476530 Summary: E-mail, calendar and groupware accounts should be configurable through the Online Accounts KCM in System Settings Classification: Applications Product: systemsettings Version: 5.27.9 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_kaccounts Assignee: plasma-b...@kde.org Reporter: philipp.reichm...@gmail.com CC: ad...@leinir.dk Target Milestone: --- Created attachment 162853 --> https://bugs.kde.org/attachment.cgi?id=162853=edit KAccounts asks for access to Google calendar, contacts and tasks, but does not set up a PIM account to actually access them. SUMMARY The Online Accounts KCM is very limited in the kinds of accounts you can set up through it. For example I can't set up Google or EWS PIM accounts through the Online Accounts KCM. This is in spite of the fact that when I set up a Google account, I am explicitly prompted to give KDE Online Accounts access to my Google calendar, contacts and tasks. (See screenshot.) This is very confusing for users; it is not obvious why a PIM account can't be set up in this way. To a user it may also seem suspicious; after all why is KDE Online Accounts asking me for access to my calendar, if then it's not going to give that access to me? I should be able to use System Settings as a single place to manage all my Online Accounts, which includes PIM accounts. STEPS TO REPRODUCE 1. Go to System Settings → Online Accounts 2. Click "Add new account", select Google account 3. Give KDE Online Accounts permission to access your files, calendar, contacts and tasks 4. Open KOrganizer or Merkuro and look for calendars from the Google account you just created OBSERVED RESULT The account you just added does not appear in KDE PIM apps. The only thing I can use it for is uploading videos to Youtube. If I want to set up a Google or EWS groupware account, I cannot set this up using the Online Accounts KCM - I have to go through a separate UI in the KDE PIM apps. EXPECTED RESULT I should be able to add groupware accounts through System Settings - either through the Online Accounts KCM, or through some other KCM for setting up KDE PIM accounts. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231026 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.8-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 476528] New: No events from O365 calendar via EWS are visible. Same events are visible if accessed via DAVmail and CalDAV.
https://bugs.kde.org/show_bug.cgi?id=476528 Bug ID: 476528 Summary: No events from O365 calendar via EWS are visible. Same events are visible if accessed via DAVmail and CalDAV. Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-b...@kde.org Reporter: philipp.reichm...@gmail.com CC: c...@carlschwan.eu, kri...@op.pl Target Milestone: --- SUMMARY Events from an O365 calendar accessed via EWS resource are not shown in KOrganizer, Merkuro or the clock widget. Events from the same O365 calendar accessed via DAVmail are shown. STEPS TO REPRODUCE 1. Set up an EWS resource for an O365 account. 2. Make sure e-mails show up in KMail. For extra comparison, set up DAVmail for the O365 account, and set up a CalDAV resource for the same calendar. OBSERVED RESULT In KOrganizer, Merkuro or the calendar widgets the EWS resource shows no events, while the CalDAV resource does. In addition, when right-clicking the EWS resource in Merkuro, the gear icon spins forever and nothing happens. EXPECTED RESULT KDE apps should show events from the EWS resource. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231026 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0, KOrganizer 5.24.2 (23.08.2), Merkuro 23.08.2 Qt Version: 5.15.11 Kernel Version: 6.5.8-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412722] KOrganizer does not show some events from EWS resource
https://bugs.kde.org/show_bug.cgi?id=412722 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com Summary|KOrganizer does not show|KOrganizer does not show |events from EWS resource|some events from EWS ||resource -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409183] Using Password based authentication when Oauth2 is selected
https://bugs.kde.org/show_bug.cgi?id=409183 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #7 from phrxmd --- Part of the problem could have to do with the bad UI behaviour described in bug 476527 - if I want OAuth2, the "OK" button should be clickable without having to enter random data for the username and password. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 476527] Can't add EWS account with OAuth2 authentication, "OK" button stays greyed out until I enter random data for username and password
https://bugs.kde.org/show_bug.cgi?id=476527 phrxmd changed: What|Removed |Added Summary|Can't add EWS account with |Can't add EWS account with |OAuth2 authentication, "OK" |OAuth2 authentication, "OK" |button stays greyed out |button stays greyed out |until I enter random data |until I enter random data |for for username and|for username and password |password| -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 476527] Can't add EWS account with OAuth2 authentication, "OK" button stays greyed out until I enter random data for for username and password
https://bugs.kde.org/show_bug.cgi?id=476527 --- Comment #1 from phrxmd --- This could be behind part of the problem described in bug 409183. However, bug 409183 is about username/password authentication being used according to the logs. This bug here has nothing to do with the logs, it's just about a UI issue in the account setup window. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 476527] New: Can't add EWS account with OAuth2 authentication, "OK" button stays greyed out until I enter random data for for username and password
https://bugs.kde.org/show_bug.cgi?id=476527 Bug ID: 476527 Summary: Can't add EWS account with OAuth2 authentication, "OK" button stays greyed out until I enter random data for for username and password Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-b...@kde.org Reporter: philipp.reichm...@gmail.com CC: c...@carlschwan.eu, kri...@op.pl Target Milestone: --- SUMMARY I can't add an EWS account with OAuth2 authentication because the "OK" button stays grayed out. If I enter random data in the username/password fields and then deselect username/password authentication and select OAuth2 instead, the "OK" button becomes clickable and the account can be added. STEPS TO REPRODUCE 1. Follow steps to add a new EWS account in Merkuro or KOrganizer - e.g. in Merkuro go to "Settings" → "Configure Merkuro Calendar" → "Accounts", click "Add Account", select "Microsoft Exchange Server (EWS)" 2. Enter e-mail address (e.g. an O365 account address) 3. Deselect automatic server recognition, enter EWS URL, e.g. https://outlook.office365.com/EWS/Exchange.asmx for O365 4. Select "OAuth2" authentication OBSERVED RESULT The "OK" button stays grayed out and the account cannot be added. The workaround is to deselect "OAuth2" and select "Username/Password", deselect the domain checkbox, enter any random strings in the username and password fields, and then deselect "Username/Password" and select "OAuth2" again, then the OK button is clickable. EXPECTED RESULT The OK button should be clickable without having to enter random data for the username/password field that doesn't get used anyway. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231026 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.8-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 476526] New: Can't add Google account: after authenticating, the account in the list shows "Configured account does not exist" (have to set it up in KOrganizer, which has a Refresh butt
https://bugs.kde.org/show_bug.cgi?id=476526 Bug ID: 476526 Summary: Can't add Google account: after authenticating, the account in the list shows "Configured account does not exist" (have to set it up in KOrganizer, which has a Refresh button) Classification: Applications Product: Merkuro Version: 23.08.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: philipp.reichm...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY I can't set up a Google Groupware account through Merkuro Calendar. I run into bug 473897 where a newly-added account is shown in the list as "Configured account does not exist". However, unlike KOrganizer that allows me to manually refresh the list through a Reload button, Merkuro has no such button and I can't force it to refresh its account list. As a result, the account stays non-functional. STEPS TO REPRODUCE 1. Go to "Settings" → "Configure Merkuro Calendar" → "Accounts", hit "Add Account" 2. Select "Google Groupware" 3. Hit "Setup" 4. Go to the browser window that appears, enter your Google account data, authenticate against Google, allow Akonadi to access your account 5. Go back to Merkuro. You now have an Akonadi window with the calendars and tasks from your Google account. Hit "OK" 6. The account list now shows your new Google account, but it says "Configured account does not exist". OBSERVED RESULT The account list now shows your new Google account, but it says "Configured account does not exist". Probably Akonadi hasn't refreshed its account list yet, apparently it doesn't do that automatically. The workaround is to set up the account not in Merkuro, but in KOrganizer, where the account list has a "Reload" button that does a force-refresh. The underlying behaviour is bug 473897. However, in KOrganizer there is a workaround in the form of the Reload button. That way setting up Google accounts is awkward, but possible. In Merkuro it's impossible. EXPECTED RESULT The account list should show your new Google account and it should be populated and functional immediately. This would probably require fixing bug 473987? If fixing the underlying bug is impossible, Merkuro should have a force-reload button like KOrganizer does. SOFTWARE/OS VERSIONS Merkuro Version: 23.08.2 Operating System: openSUSE Tumbleweed 20231026 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.8-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475728] Event content in tooltips badly formatted, links overrun the tooltip border and cover the desktop; event content is otherwise inaccessible
https://bugs.kde.org/show_bug.cgi?id=475728 phrxmd changed: What|Removed |Added Summary|Event content in tooltips |Event content in tooltips |that are badly formatted, |badly formatted, links |links overrun the tooltip |overrun the tooltip border |border and cover the|and cover the desktop; |desktop; event content is |event content is otherwise |otherwise inaccessible |inaccessible -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444602] LyX menu stops opening after a while
https://bugs.kde.org/show_bug.cgi?id=444602 --- Comment #1 from phrxmd --- Is there a way to get debug information from KDE for the global menu? The problem persists and the LyX devs are asking for it (https://www.lyx.org/trac/ticket/12415#comment:4). -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 473617] Cannot enter the name when i first launch the app
https://bugs.kde.org/show_bug.cgi?id=473617 --- Comment #6 from phrxmd --- Seems fixed in the Git version, I can enter the name in both the Wayland and X11 UIs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429700] Links in calendar event text are not clickable
https://bugs.kde.org/show_bug.cgi?id=429700 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #4 from phrxmd --- In the absence of clickable links in tooltips, it would be good if the event content would be accessible from the Digital Clock widget in some other way. Clicking the event could open it in a calendar app, for example. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475728] Event content in tooltips that are badly formatted, links overrun the tooltip border and cover the desktop; event content is otherwise inaccessible
https://bugs.kde.org/show_bug.cgi?id=475728 --- Comment #1 from phrxmd --- The issue with links not being clickable was reported in bug 429700. This is a fundamental issue with tooltips. However, in the era of video conferencing, events with links are common. So in the absence of clickable links in tooltips, there should be some other UI for accessing the content of an event from Digital Clock - maybe double-clicking the event should open it in a calendar app or something. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475728] New: Event content in tooltips that are badly formatted, links overrun the tooltip border and cover the desktop; event content is otherwise inaccessible
https://bugs.kde.org/show_bug.cgi?id=475728 Bug ID: 475728 Summary: Event content in tooltips that are badly formatted, links overrun the tooltip border and cover the desktop; event content is otherwise inaccessible Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: 1.0 Created attachment 162367 --> https://bugs.kde.org/attachment.cgi?id=162367=edit Tooltip popup hovering over an event whose description contains long links. The links are badly formatted and are not clickable. SUMMARY When hovering the mouse over an event in the calendar part of the Digital Clock widget, and the event has long links, the tooltip that pops up is badly formatted, the text overruns the tooltip and covers part of the desktop. Links are also not clickable. Unfortunately the tooltip is the only way to view the content of the event - clicking on the event itself does nothing. As a result, when an event contains a link (such as a video conference invitation), there is no way to access the link other than looking up the event in another app such as KOrganizer or Merkuro. STEPS TO REPRODUCE 1. Install KDEPIM, configure Digital Clock to show a calendar with events that have long links 2. Hover mouse over one of these events until a tooltip appears OBSERVED RESULT A tooltip pops up that is badly formatted, the text for long links overruns the edge of the tooltip and covers other parts of the UI (see attached screenshot with a link from a MS Teams invitation). EXPECTED RESULT An informative, good-looking display whose text does not overrun the border and does not cover other parts of the desktop. A way to access event content that makes links should clickable. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231011 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.5.6-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 475656] Crash in QV4 engine upon Merkuro startup when no LANG environment variable is specified
https://bugs.kde.org/show_bug.cgi?id=475656 phrxmd changed: What|Removed |Added Summary|Crash in QV4 engine upon|Crash in QV4 engine upon |Merkuro startup |Merkuro startup when no ||LANG environment variable ||is specified -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 475656] Crash in QV4 engine upon Merkuro startup
https://bugs.kde.org/show_bug.cgi?id=475656 --- Comment #2 from phrxmd --- Workaround: specify a language via command line variables. These work: > LANG=de_DE.UTF-8 LANGUAGE=C merkuro-calendar > LANG=C merkuro-calendar This crashes: > merkuro-calendar -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 475656] Crash in QV4 engine upon Merkuro startup
https://bugs.kde.org/show_bug.cgi?id=475656 --- Comment #1 from phrxmd --- Created attachment 162321 --> https://bugs.kde.org/attachment.cgi?id=162321=edit Backtrace 2 - crash in QV4::Heap::Object::setUsedAsProto() The precise crash location is not exactly reproducible, sometimes I also get this crash instead. -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 475656] New: Crash in QV4 engine upon Merkuro startup
https://bugs.kde.org/show_bug.cgi?id=475656 Bug ID: 475656 Summary: Crash in QV4 engine upon Merkuro startup Classification: Applications Product: Merkuro Version: 23.08.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: philipp.reichm...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 162320 --> https://bugs.kde.org/attachment.cgi?id=162320=edit Backtrace 1 - crash in QV4::QQmlValueTypeWrapper::create() SUMMARY Kalendar/Merkuro crashes on startup. The backtrace points to the QV4 javascript engine. No window ever appears. Additionally, no KDE crash handler comes up. STEPS TO REPRODUCE 1. Start Merkuro (from the commandline with merkur-calendar) OBSERVED RESULT > merkuro-calendar file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/ToolBarPageHeader.qml:32:9: QML Loader (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" [1]10537 segmentation fault (core dumped) merkuro-calendar EXPECTED RESULT The app should come up normally. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231011 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.5.6-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION This is in the Wayland session, if I start with QT_QPA_PLATFORM=xcb, the UI comes up briefly, but then the app also crashes: > QT_QPA_PLATFORM=xcb merkuro-calendar qrc:/BasicMonthListView.qml:216:21: QML Button: Binding loop detected for property "implicitWidth" qrc:/BasicMonthListView.qml:216:21: QML Button: Binding loop detected for property "implicitWidth" [1]11061 segmentation fault (core dumped) QT_QPA_PLATFORM=xcb merkuro-calendar -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 473617] Cannot enter the name when i first launch the app
https://bugs.kde.org/show_bug.cgi?id=473617 phrxmd changed: What|Removed |Added Keywords||wayland --- Comment #3 from phrxmd --- Added note: this seems to be a Wayland-related issue. When I launch KTouch from the command line with QT_QPA_PLATFORM=xcb ktouch, it works. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 474941] Can't use app because of screen don't let me write my name
https://bugs.kde.org/show_bug.cgi?id=474941 phrxmd changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from phrxmd --- *** This bug has been marked as a duplicate of bug 473617 *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 473617] Cannot enter the name when i first launch the app
https://bugs.kde.org/show_bug.cgi?id=473617 phrxmd changed: What|Removed |Added CC||bluedream1...@proton.me --- Comment #2 from phrxmd --- *** Bug 474941 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 473617] Cannot enter the name when i first launch the app
https://bugs.kde.org/show_bug.cgi?id=473617 phrxmd changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||philipp.reichm...@gmail.com Ever confirmed|0 |1 --- Comment #1 from phrxmd --- I see the same behaviour with KTouch 23.08.1 on OpenSUSE. This is in the Wayland session. KTouch is unusable because I can't enter the name. Here's the package information: Information for package ktouch: --- Repository : repo:oss Name : ktouch Version: 23.08.1-1.2 Arch : x86_64 Vendor : openSUSE Installed Size : 4.3 MiB Installed : Yes Status : up-to-date Source package : ktouch-23.08.1-1.2.src Upstream URL : https://apps.kde.org/ktouch Summary: Touch Typing Tutor Description: A KDE program that helps you to learn and practice touch typing. Here's the system information: Operating System: openSUSE Tumbleweed 20231010 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.5.6-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 474941] Can't use app because of screen don't let me write my name
https://bugs.kde.org/show_bug.cgi?id=474941 phrxmd changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||philipp.reichm...@gmail.com --- Comment #1 from phrxmd --- Same here with KTouch 23.08.1 on OpenSUSE. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 phrxmd changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||philipp.reichm...@gmail.com --- Comment #5 from phrxmd --- I can confirm this, am seeing the same behaviour. Operating System: openSUSE Tumbleweed 20230917 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.3-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 20LDCTO1WW System Version: ThinkPad X1 Yoga 3rd Here is the backtrace (upon calling `krfb-virtualmonitor --name Virtual --resolution 1024x768 --password password --port 5900`): #0 __memcpy_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:660 #1 0x7f05c00196ac in ?? () from /usr/lib64/qt5/plugins/krfb/framebuffer/pw.so #2 0x7f05c7b25812 in QtPrivate::QSlotObjectBase::call (a=0x7ffd25c0baf0, r=0x55848d758f30, this=0x55848d759a70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #3 doActivate (sender=0x55848d7b3790, signal_index=7, argv=0x7ffd25c0baf0) at kernel/qobject.cpp:3925 #4 0x7f05b85e10c5 in PipeWireSourceStream::frameReceived(PipeWireFrame const&) () from /lib64/libKPipeWire.so.5 #5 0x7f05b85ec78b in PipeWireSourceStream::handleFrame(pw_buffer*) () from /lib64/libKPipeWire.so.5 #6 0x7f05b85ecfb7 in PipeWireSourceStream::process() () from /lib64/libKPipeWire.so.5 #7 0x7f05b8441760 in do_call_process (loop=, async=, seq=, data=, size=, user_data=0x55848d870a50) at ../src/pipewire/stream.c:449 #8 do_call_process (loop=, async=, seq=, data=, size=, user_data=0x55848d870a50) at ../src/pipewire/stream.c:442 #9 0x7f05b83a6bb1 in flush_items (impl=0x55848d84d678) at ../spa/plugins/support/loop.c:171 #10 0x7f05b83a5d15 in source_event_func (source=0x55848d6769b0) at ../spa/plugins/support/loop.c:650 #11 0x7f05b83a7576 in loop_iterate (object=0x55848d84d678, timeout=) at ../spa/plugins/support/loop.c:483 #12 0x7f05b85e2ee9 in ?? () from /lib64/libKPipeWire.so.5 #13 0x7f05c7b25812 in QtPrivate::QSlotObjectBase::call (a=0x7ffd25c0c190, r=0x55848d7fa9e0, this=0x55848d7eb8b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate (sender=0x55848d7f7f30, signal_index=3, argv=0x7ffd25c0c190) at kernel/qobject.cpp:3925 #15 0x7f05c7b1e47f in QMetaObject::activate (sender=sender@entry=0x55848d7f7f30, m=m@entry=0x7f05c7dc7860, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd25c0c190) at kernel/qobject.cpp:3985 #16 0x7f05c7b28b0f in QSocketNotifier::activated (this=this@entry=0x55848d7f7f30, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #17 0x7f05c7b29315 in QSocketNotifier::event (this=0x55848d7f7f30, e=) at kernel/qsocketnotifier.cpp:302 #18 0x7f05c87a519e in QApplicationPrivate::notify_helper (this=, receiver=0x55848d7f7f30, --Type for more, q to quit, c to continue without paging-- e=0x7ffd25c0c290) at kernel/qapplication.cpp:3640 #19 0x7f05c7aed568 in QCoreApplication::notifyInternal2 (receiver=0x55848d7f7f30, event=0x7ffd25c0c290) at kernel/qcoreapplication.cpp:1064 #20 0x7f05c7aed72e in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #21 0x7f05c7b46f7d in socketNotifierSourceDispatch (source=0x55848d6a64a0) at kernel/qeventdispatcher_glib.cpp:107 #22 0x7f05c5d169d8 in g_main_dispatch (context=0x7f05bc000ee0) at ../glib/gmain.c:3460 #23 g_main_context_dispatch (context=context@entry=0x7f05bc000ee0) at ../glib/gmain.c:4200 #24 0x7f05c5d16de8 in g_main_context_iterate (context=context@entry=0x7f05bc000ee0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4276 #25 0x7f05c5d16e7c in g_main_context_iteration (context=0x7f05bc000ee0, may_block=1) at ../glib/gmain.c:4343 #26 0x7f05c7b464a6 in QEventDispatcherGlib::processEvents (this=0x55848d635390, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #27 0x7f05c7aebffb in QEventLoop::exec (this=this@entry=0x7ffd25c0c4a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #28 0x7f05c7af4490 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #29 0x55848bf2a701 in ?? () #30 0x7f05c70281b0 in __libc_start_call_main (main=main@entry=0x55848bf29c10, argc=argc@entry=9, argv=argv@entry=0x7ffd25c0c848) at ../sysdeps/nptl/libc_start_call_main.h:58 #31 0x7f05c7028279 in __libc_start_main_impl (main=0x55848bf29c10, argc=9, argv=0x7ffd25c0
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 --- Comment #34 from phrxmd --- Updated my OpenSUSE to Plasma 5.27.7, and to GTK 3.24.38 (which according to GNOME Gitlab should have the patch), and I still get no menu. Does this need anything else? Or is there additional information I can provide to help debug this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 --- Comment #32 from phrxmd --- (In reply to Naxdy from comment #31) > For me, global menu is still in the GTK3 apps, not in the global menu bar... But you do get a menu at all, even if it's in the app window? I don't get that either, I reported that as bug 450038 but got referred back here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 --- Comment #30 from phrxmd --- Created attachment 160873 --> https://bugs.kde.org/attachment.cgi?id=160873=edit GTK3 app in Plasma 5.27.6 with no menu at all (neither local nor global) What version should that be fixed in? According to that kded commit, it should work in 5.27.4. However, I just tested with Inkscape 1.2 on 5.27.6 and the behaviour with GTK3 apps on Wayland is the same: - by default on Wayland, nothing in the global menu, and no menu bar in the window either (see screenshot) - if I add Inkscape to the `org.appmenu.gtk-module` blacklist, I at least get a menu bar in the window - if I start Inkscape with GDK_BACKEND=x11, I get the global menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448078] Global Menu does not work in Qt6
https://bugs.kde.org/show_bug.cgi?id=448078 --- Comment #7 from phrxmd --- Electron apps aside, I can still reproduce this with Qt6 apps such as Telegram Desktop and qBittorrent. Steps to reproduce: 1. Launch app with QT_QPA_PLATFORM=xcb → menu appears in the Global Menu applet 2. Launch app with QT_QPA_PLATFORM=wayland → no menu at all (neither in the Global Menu applet nor in the app window). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372496] Support tmux control mode
https://bugs.kde.org/show_bug.cgi?id=372496 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 phrxmd changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #20 from phrxmd --- Can't reproduce it with 5.27.4 anymore. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type
https://bugs.kde.org/show_bug.cgi?id=340283 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #55 from phrxmd --- KRunner is great - the best launcher I've used so far - but I would be very happy if this was customizable to some extent. For example, I'd like to be able to have applications ranked higher than recently opened files. Here are two use cases for that: - I open a downloaded AppImage to test it, then make a desktop file in ~/.local/share/applications for it. However since the AppImage counts as a recently opened file, the AppImage file is always listed above the desktop entry. - Sometimes when typing an app name in KRunner and hitting Enter quickly, the list of search results gets updated with some files from Baloo before I hit Enter. So Enter then opens a file instead of the app, and henceforth the file will now be ranked higher than the app because it now is a recently opened file. This has happened to me with Telegram: in between me typing "telegram" and hitting Enter, Baloo served up the Telegram icon file "telegram.svg", and since it now counts as a recently opened file, the icon file always gets ranked higher than the app and I need to press a few arrow keys to get the app. So an UI that would consistently have me rank certain results above or below certain other results would help me a lot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453134] KWin Wayland locks up whenever the Zoom comms app enters/leaves a breakout session
https://bugs.kde.org/show_bug.cgi?id=453134 phrxmd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from phrxmd --- I haven't seen this happen for a while, possibly due to changes in Zoom. If/when it happens again, I will try to ssh in and get a backtrace. Closing for now, will reopen if it happens again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461755] KWin hard freeze when opening a Brave browser Tor window from the command line
https://bugs.kde.org/show_bug.cgi?id=461755 phrxmd changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461755] KWin hard freeze when opening a Brave browser Tor window from the command line
https://bugs.kde.org/show_bug.cgi?id=461755 --- Comment #3 from phrxmd --- Created attachment 153760 --> https://bugs.kde.org/attachment.cgi?id=153760=edit Backtrace with KWin in frozen state after brave-browser --tor hangs Here is a backtrace. I'm unsure whether I got it by the correct procedure - I connect via ssh, attach GDB to the kwin_wayland process by issuing `sudo gdb -pid $(pidof kwin_wayland)`, then I set the logging file and `set logging enabled on` and `continue`. When KWin freezes, there is no signal issued, so I stop KWin manually by issuing SIGINT from GDB with Ctrl+C, then I get the backtrace with `bt full`. I noticed that KWin seems to be doing something (just not reacting to mouse events), so I've done the Ctrl+C - `bt full` - `continue` cycle a few times in the backtrace. Also when I detach GDB again, I can kill the brave processes from SSH which frees up KWin again, after which I get a bunch of output in the console where I started Brave: > brave-browser --tor Nov 15 10:04:15.063 [notice] Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1s, Zlib 1.2.13, Liblzma N/A, Libzstd N/A and Glibc 2.35 as libc. Nov 15 10:04:15.063 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/ Nov 15 10:04:15.063 [notice] Read configuration file "/home/reichmuth/.config/BraveSoftware/Brave-Browser/biahpgbdmdkfgndcmfiipgcebobojjkp/1.0.29/tor-torrc". Nov 15 10:04:15.063 [notice] Read configuration file "/home/reichmuth/.config/BraveSoftware/Brave-Browser/biahpgbdmdkfgndcmfiipgcebobojjkp/1.0.29/tor-torrc". Nov 15 10:04:15.066 [notice] Opening Socks listener on 127.0.0.1:0 Nov 15 10:04:15.066 [notice] Socks listener listening on port 36655. Nov 15 10:04:15.066 [notice] Opened Socks listener connection (ready) on 127.0.0.1:36655 Nov 15 10:04:15.066 [notice] Opening Control listener on 127.0.0.1:0 Nov 15 10:04:15.066 [notice] Control listener listening on port 41319. Nov 15 10:04:15.066 [notice] Opened Control listener connection (ready) on 127.0.0.1:41319 Nov 15 10:04:15.000 [notice] Bootstrapped 0% (starting): Starting [3630:3630:1115/100415.305621:ERROR:CONSOLE(1)] "This document requires 'TrustedScript' assignment.", source: chrome://newtab/private_new_tab.bundle.js (1) Nov 15 10:04:15.000 [notice] Starting with guard context "default" [3630:3630:1115/100415.781030:ERROR:CONSOLE(1)] "This document requires 'TrustedScript' assignment.", source: chrome://newtab/private_new_tab.bundle.js (1) Nov 15 10:04:16.000 [notice] Bootstrapped 5% (conn): Connecting to a relay Nov 15 10:04:16.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay Nov 15 10:04:17.000 [notice] New control connection opened from 127.0.0.1. Nov 15 10:04:36.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay Nov 15 10:04:36.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done Nov 15 10:04:36.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits Nov 15 10:04:36.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits Nov 15 10:04:36.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit Nov 15 10:04:37.000 [notice] Bootstrapped 100% (done): Done [3630:3630:1115/100444.657464:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=512 [3846:3846:1115/100444.814583:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [3846:3846:1115/100444.816511:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [3846:3846:1115/100444.897497:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! [3630:3630:1115/100529.845188:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=512 [3889:3889:1115/100530.029862:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [3889:3889:1115/100530.030710:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [1115/100600.065734:ERROR:process_memory_linux.cc(49)] pread64: Input/output error (5) [3630:3630:1115/100600.075494:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=512 [3728:8:1115/100600.145970:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. [3728:8:1115/100600.146316:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. [1]3624 terminated brave-browser --tor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461755] New: KWin hard freeze when opening a Brave browser Tor window from the command line
https://bugs.kde.org/show_bug.cgi?id=461755 Bug ID: 461755 Summary: KWin hard freeze when opening a Brave browser Tor window from the command line Classification: Plasma Product: kwin Version: 5.26.0 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- SUMMARY KWin freezes when starting up Brave browser from the command line with the `--tor` option. The mouse pointer locks up. Can be resolved only with a hard reboot. Opening a private window with Tor from within Brave works normally. This is with Brave 1.44.112-1 in the KWin Wayland session STEPS TO REPRODUCE 1. Start Brave from the command line with `brave-browser --tor`. Unfortunately there is no --verbose output before the lockup. OBSERVED RESULT KWin locks up completely. EXPECTED RESULT The window should open normally, or it should fail gracefully. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20221015 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.1-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 20LDCTO1WW System Version: ThinkPad X1 Yoga 3rd ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460708] Panel edit mode toolbar becomes unusable when screen is in vertical orientation
https://bugs.kde.org/show_bug.cgi?id=460708 --- Comment #1 from phrxmd --- The workaround is to flip the screen to horizontal, edit the toolbar and flip it back. But that's a bit clumsy. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460708] New: Panel edit mode toolbar becomes unusable when screen is in vertical orientation
https://bugs.kde.org/show_bug.cgi?id=460708 Bug ID: 460708 Summary: Panel edit mode toolbar becomes unusable when screen is in vertical orientation Classification: Plasma Product: plasmashell Version: 5.26.0 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: philipp.reichm...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 153029 --> https://bugs.kde.org/attachment.cgi?id=153029=edit Edit Mode Toolbar on vertical screen SUMMARY The panel edit mode toolbar can become unusable on vertical screens, because then the effective horizontal resolution becomes too low for all the UI elements that Plasma tries to fit into one line. Plasma is built with screens with a minimum resolution in mind, but when the screen is in vertical orientation it can be narrower than that. STEPS TO REPRODUCE 1. Have a screen configuration with a narrow screen (e.g. in vertical orientation) 2. Enter Edit Mode OBSERVED RESULT UI elements in the toolbar overlap with each other and can become unusable. See screenshot from a 2540x1440 screen in vertical orientation with 2x HiDPI scaling (effective width 720). It gets worse with labels in a "wordy" language like German. EXPECTED RESULT UI elements should use smarter placement, possibly in several lines. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20221015 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 20LDCTO1WW System Version: ThinkPad X1 Yoga 3rd ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459973] New: Touch mode on convertible laptop gets activated even when there is an USB keyboard & mouse attached
https://bugs.kde.org/show_bug.cgi?id=459973 Bug ID: 459973 Summary: Touch mode on convertible laptop gets activated even when there is an USB keyboard & mouse attached Classification: Plasma Product: kwin Version: 5.25.5 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- SUMMARY I use a Thinkpad X1 Yoga, which is a convertible laptop. I often use it in a monitor stand, where I flip the keyboard to the back, hang the notebook next to my monitor vertically and use it as a second screen. I have an USB keyboard and mouse attached to the notebook through a Thunderbolt dock. Whenever I flip the keyboard to the back, Touch Mode gets enabled. That is very useful when using the laptop as a tablet, but not at my desktop where I have an USB keyboard and mouse attached at all times. STEPS TO REPRODUCE 1. Set Touch Mode to "Automatically enabled" in System settings 2. Attach a USB keyboard and mouse 3. Flip the convertible laptop screen over OBSERVED RESULT The laptop's built in keyboard is disabled (as expected), but Touch Mode is enabled as well. EXPECTED RESULT Touch Mode should be enabled only when there is no keyboard and mouse at all. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220929 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.8-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 20LDCTO1WW System Version: ThinkPad X1 Yoga 3rd -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450038] No menubar at all in Wayland with GTK3 applications (neither global nor in app window)
https://bugs.kde.org/show_bug.cgi?id=450038 --- Comment #3 from phrxmd --- A somewhat crude workaround is to blacklist each app in the GTK appmenu plugin. E.g. to get a working menu back with Inkscape: ``` > gsettings get org.appmenu.gtk-module blacklist ['anjuta', 'freeciv', 'freeciv-gtk2', 'freeciv-gtk3', 'glade', 'gwyddion'] > gsettings set org.appmenu.gtk-module blacklist "['inkscape', 'anjuta', > 'freeciv', 'freeciv-gtk2', 'freeciv-gtk3', 'glade', 'gwyddion']" > gsettings get org.appmenu.gtk-module blacklist ['inkscape', 'anjuta', 'freeciv', 'freeciv-gtk2', 'freeciv-gtk3', 'glade', 'gwyddion'\] ``` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364321] GUI to switch from JEDEC to SI units
https://bugs.kde.org/show_bug.cgi?id=364321 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448078] Global Menu does not work in Qt6
https://bugs.kde.org/show_bug.cgi?id=448078 phrxmd changed: What|Removed |Added Resolution|NOT A BUG |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from phrxmd --- I'm reopening this because (with all due respect) I think this is not about porting KDE applications to Qt6, but about making sure that in the meantime Qt6 applications show at least SOME kind of menu, even if the Global menu currently doesn't support them. I'm seeing the same behaviour with Qt6 applications: the app window doesn't contain a menu, the global menu doesn't show anything, it's as if the menu got swallowed somewhere. -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 455155] No menu at all for Qt6 apps in Wayland
https://bugs.kde.org/show_bug.cgi?id=455155 phrxmd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from phrxmd --- *** This bug has been marked as a duplicate of bug 448078 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448078] Global Menu does not work in Qt6
https://bugs.kde.org/show_bug.cgi?id=448078 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #2 from phrxmd --- *** Bug 455155 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450038] No menubar at all in Wayland with GTK3 applications (neither global nor in app window)
https://bugs.kde.org/show_bug.cgi?id=450038 --- Comment #2 from phrxmd --- (In reply to David Edmundson from comment #1) > *** This bug has been marked as a duplicate of bug 424485 *** Is this really the same bug? Bug 424485 is about how GDBus-DBbusMenu-Proxy does not detect the menu exported by GTK3 apps, which is why the global menu shows nothing. This bug is about how in that case the app doesn't show an in-window local menu either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else
https://bugs.kde.org/show_bug.cgi?id=450068 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #25 from phrxmd --- Same issue here. I have two screens, my laptop screen and an external screen connected through DisplayPort to a Thunderbolt dock. On both screens I have a containment with a panel. Every time I send the the notebook, dock and monitor to standby and wake them up again, the external screen ends up on a different output DP-[34567]. So every time I have to do a little dance through the containment management window to move the panel from the output where it was to the output where the screen now is. The ScreenConnectors section of .config/plasmashellrc looks like this (right now I'm on DP-3): [ScreenConnectors] 0=eDP-1 1=HDMI-1 2=DP-1-8 3=DP-1-2 4=HDMI-A-1 5=DP-4 6=DP-3 7=DP-5 The output of `kscreen-doctor -o` is as follows (but shouldn't probably matter): > kscreen-doctor -o Output: 1 AU Optronics eDP-1-unknown enabled connected primary Panel Modes: 0:2560x1440@60*! 1:1280x1024@60 2:1920x1200@60 3:1280x800@60 4:1600x900@60 Geometry: 0,0 720x1280 Scale: 2 Rotation: 8 Overscan: 0 Vrr: incapable RgbRange: Automatic primary Output: 2 Samsung Electric Company U28E590/H4LMA02988 enabled connected DisplayPort Modes: 0:3840x2160@60*! 1:3840x2160@30 2:3840x2160@30 3:2560x1440@60 4:1920x1080@60 5:1920x1080@60 6:1920x1080@60 7:1680x1050@60 8:1600x900@60 9:1280x1024@75 10:1280x1024@60 11:1440x900@60 12:1280x800@60 13:1152x864@75 14:1280x720@60 15:1280x720@60 16:1024x768@75 17:1024x768@70 18:1024x768@60 19:832x624@75 20:800x600@75 21:800x600@72 22:800x600@60 23:800x600@56 24:640x480@75 25:640x480@73 26:640x480@67 27:640x480@60 28:640x480@60 29:720x400@70 30:1600x1200@60 31:2560x1600@60 32:1920x1200@60 33:3200x1800@60 34:2880x1620@60 35:1368x768@60 Geometry: 720,0 1920x1080 Scale: 2 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 --- Comment #22 from phrxmd --- In addition, shouldn't this be "High priority" aka a "15-minute bug"? There's 8 duplicates and the problem appears in the default configuration as soon as you enable the global menu on Wayland - people are highly likely to use GTK applications and having their menus inaccessible is a problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 phrxmd changed: What|Removed |Added CC||gona...@ulm-dsl.de --- Comment #21 from phrxmd --- *** Bug 453600 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 453600] electron-qt-apps + wayland: no working global menu (= no menus, unuseable) - needed dependecies? roadmap?
https://bugs.kde.org/show_bug.cgi?id=453600 phrxmd changed: What|Removed |Added Status|REPORTED|RESOLVED CC||philipp.reichm...@gmail.com Resolution|--- |DUPLICATE --- Comment #3 from phrxmd --- *** This bug has been marked as a duplicate of bug 424485 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 --- Comment #20 from phrxmd --- (In reply to Gerry Agbobada from comment #17) > Hello, > > I don't know if any easy enough solution for this bug has been found (and > I'm definitely not claiming to have one), but I think it's worth considering > adding this bug to the showstopper list [1], as not being able to access the > menu from GTK apps vs. Qt apps feels like a big enough regression to me when > going from X11 to Wayland. > > [1]: https://community.kde.org/Plasma/Wayland_Showstoppers +1 on adding this to the Wayland Showstoppers list. Currently I have to start GTK applications with `QT_QPA_PLATFORM=xcb` if I want to access any menu functions - otherwise I get no menu at all, global, in-window or otherwise. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440406] Virtualbox doesn't receive any mouse input after a VM starts
https://bugs.kde.org/show_bug.cgi?id=440406 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #15 from phrxmd --- I'm seeing the same with VirtualBox 6.1.34 on OpenSUSE Tumbleweed (Thinkpad X1 Yoga 3rd, Intel graphics). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448102] Crash in KWin::Workspace::clientArea called from QML after monitor changes
https://bugs.kde.org/show_bug.cgi?id=448102 phrxmd changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||philipp.reichm...@gmail.com Resolution|--- |FIXED --- Comment #12 from phrxmd --- It seems that https://invent.kde.org/plasma/kwin/-/merge_requests/2517/ has fixed this (see bug 449957). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when connecting/disconnecting, enabling/disabling screens.
https://bugs.kde.org/show_bug.cgi?id=449957 phrxmd changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #35 from phrxmd --- Just tested with master and it seems to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when connecting/disconnecting, enabling/disabling screens.
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #30 from phrxmd --- (In reply to Ta-Lun Yen from comment #28) > phrxmd: Is there by any chance, you have plugins like grid-tiling-kwin or > bismuth installed? If so, please try > https://invent.kde.org/plasma/kwin/-/merge_requests/2509 I have bismuth installed. That merge request fixes this bug for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when connecting/disconnecting, enabling/disabling screens.
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #29 from phrxmd --- (In reply to Ta-Lun Yen from comment #28) > phrxmd: Is there by any chance, you have plugins like grid-tiling-kwin or > bismuth installed? If so, please try > https://invent.kde.org/plasma/kwin/-/merge_requests/2509 I'll try, but it might take me a few days as I've never compiled KDE from source before. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when connecting/disconnecting, enabling/disabling screens.
https://bugs.kde.org/show_bug.cgi?id=449957 phrxmd changed: What|Removed |Added Summary|KWin crash in |KWin crash in |KWin::PlacementArea() when |KWin::PlacementArea() when |disabling, unplugging or|connecting/disconnecting, |turning off output with |enabling/disabling screens. |windows on it | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when disabling, unplugging or turning off output with windows on it
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #27 from phrxmd --- Created attachment 149621 --> https://bugs.kde.org/attachment.cgi?id=149621=edit Backtrace when this happens as a DisplayPort screen comes online Another very annoying instance where this has recently started to happen is whenever I try to log into the Plasma session with an external screen attached via DisplayPort to my Thunderbolt dock. In this configuration, Plasma is now unbootable. KWin comes up, initializes the screen, crashes, comes up again, initializes the screen again, crashes and so on. After going through this crash loop a few times, I'm dropped back into the display manager. This happens whenever a DisplayPort monitor attached to the dock comes up (see backtrace attached). I'm not sure what led to this change. However, before the recent system update (pre-kernel 5.17??), the eGPU in the dock and the DisplayPort screen attached to the dock would come up already during the boot process, and I'd see boot messages scrolling by on the external screen that duplicate those on the internal desktop. Since the change, the external screen stays dark during the boot process (maybe the eGPU in the dock gets initialized later?), and when KWin tries to bring it up, KWin crashes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when disabling, unplugging or turning off output with windows on it
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #26 from phrxmd --- Created attachment 149618 --> https://bugs.kde.org/attachment.cgi?id=149618=edit Backtrace when this happens after waking up from monitor standby Since a recent system update (since kernel 5.17 or so) I start seeing this much more often. One situation where it happens reproducibly is whenever a screen is connected to the laptop's internal HDMI port, KWin wakes up from monitor standby and the external screen comes online. (The workaround is to disable monitor standby in System Settings). System as of now: Operating System: openSUSE Tumbleweed 20220609 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.18.2-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 455155] New: No menu at all for Qt6 apps in Wayland
https://bugs.kde.org/show_bug.cgi?id=455155 Bug ID: 455155 Summary: No menu at all for Qt6 apps in Wayland Product: kded-appmenu Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: export Assignee: plasma-b...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- SUMMARY When using the global menu on Wayland, Qt6 application are rendered without any menu. There is no global menu (bug 448078), but there is also no in-application menu. Any functionality that is reached through the menu is inaccessible to the user. Tested with qbittorrent (a Qt6 application) that gives me a global menu when started under XWayland, but no menu at all under Wayland. STEPS TO REPRODUCE 1. On Wayland, enable the Global Menu widget, or some other widget that enables the global menu 2. Launch QBittorrent with QT_QPA_PLATFORM=wayland 3. No menu! 4. Exit QBittorrent, launch it again with QT_QPA_PLATFORM=xcb, compare OBSERVED RESULT Under Wayland QBittorrent has no menu at all, global or not. Under XCB/CWayland QBittorrent has a global menu. EXPECTED RESULT The global menu should be exported correctly whatever the platform. Barring that, as long as KDE isn't ported to Qt6, the menu should be displayed in-application. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220609 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Qt6 Version: 6.3.0 Kernel Version: 5.18.2-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Tested with QBittorrent 4.4.3.1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454645] Wishlist: support for adding headless outputs - iPad as second screen using VNC or RDP - like Gnome and Sway
https://bugs.kde.org/show_bug.cgi?id=454645 --- Comment #2 from phrxmd --- Thank you! That's great information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454645] New: Wishlist: support for adding headless outputs - iPad as second screen using VNC or RDP - like Gnome and Sway
https://bugs.kde.org/show_bug.cgi?id=454645 Bug ID: 454645 Summary: Wishlist: support for adding headless outputs - iPad as second screen using VNC or RDP - like Gnome and Sway Product: kwin Version: 5.24.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- I want to repurpose some old tablets as secondary displays. They're slow, but fast enough to run a VNC or RDP client. If I could set up some virtual/headless outputs that are accessible via VNC or RDP, I would find it very useful, because I could use any old tablet to extend my screen real estate. Gnome and Sway can already do this, and so can KWin with X11: - Sway has had an option to configure headless outputs since 2020, you can then run a VNC server on those outputs: https://www.reddit.com/r/swaywm/comments/k1zl41/thank_you_devs_free_ipad_repurposed_as_a_second/, https://github.com/swaywm/sway/issues/5553 - Gnome has support for virtual monitors via RDP since Gnome 42, support was merged a few months ago: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/69 - With KWin X11 I used to be able to achieve this in a hackish way by setting up a virtual output in XRandR, similar to this: https://askubuntu.com/questions/28608/how-do-you-use-an-android-tablet-as-a-second-display. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389568] Feature to reset all settings to default values
https://bugs.kde.org/show_bug.cgi?id=389568 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #34 from phrxmd --- I would really appreciate this. One moment when I wished I had something like this was when I switched to Wayland. I found it hard to get my old X11 configuration to produce acceptable output in Wayland without different sorts of visual glitches, so at some moment the only way out for me was to try and reset the Plasma configuration by deleting all the config files that I thought had something to do with Plasma. Because there are so many and the names and locations are quite non-obvious, I wished Plasma had a "reset to defaults" button. Even so I find it is not so difficult to get Plasma into a state where the configuration is broken or suboptimal in some ways. It comes with the complexity. Of course the default response to this would be that this shouldn't happen and that all of this should be reported as bugs - but it does not help the user who is stuck and wants to get back to a clean system. Plasma has come some way thanks to indicating changed settings in System Settings - but this only highlights that Plasma clearly knows what the defaults are, so it should be possible to reset to them with one click of a button, instead of setting each of them individually, no? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when disabling, unplugging or turning off output with windows on it
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #23 from phrxmd --- Further clarification: on 5.24.5 this crash happens only when... (a) unplugging a primary display, whether it has windows on it or not (b) unplugging a non-primary display if and only if it has windows on it E.g. on my home setting, where I have an monitor connected to the docking station that is marked primary, KWin crashes whenever I unplug the docking station, unplug the monitor from the docking station or switch off the monitor. In that situation I can avoid the crash by moving all windows off the external monitor, marking the notebook screen as primary and then unplugging the (now-secondary) monitor. It seems that it is triggered by the recalculation of window coordinates that happens either when a window is on a disabled output and needs to be placed somewhere else, or when the primary display goes down. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430210] Font previews do not show up on Wayland
https://bugs.kde.org/show_bug.cgi?id=430210 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #4 from phrxmd --- I can still reproduce this on Plasma 5.24.5 on OpenSUSE TW. -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #7 from phrxmd --- Can reproduce under Plasma 5.24.5 on OpenSUSE TW. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when disabling, unplugging or turning off output with windows on it
https://bugs.kde.org/show_bug.cgi?id=449957 phrxmd changed: What|Removed |Added Summary|KWin crash in |KWin crash in |KWin::PlacementArea() when |KWin::PlacementArea() when |turning off or unplugging |disabling, unplugging or |monitor with windows on it |turning off output with ||windows on it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor with windows on it
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #22 from phrxmd --- Upon further experimentation, I get the same crash when hitting Meta-P and switching to the internal display, without disconnecting the monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor with windows on it
https://bugs.kde.org/show_bug.cgi?id=449957 phrxmd changed: What|Removed |Added Component|wayland-generic |multi-screen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] All windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #6 from phrxmd --- Can you re-check whether it works on Wayland, now that you are on 5.24? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor with windows on it
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #21 from phrxmd --- Potentially important information: I can connect/disconnect the external monitor *as long as there are no windows on it*. A Plasma panel seems to be fine. However, as soon as there is an application window on the disconnected output, I get this crash. In my regular work setup I would always have windows on the output because it's my main monitor; I'm now testing this in a road warrior setting with a projector, and here I can reproducibly crash KWin by putting a window on the projector and then disconnecting it, while the projector disconnects just fine as long as there is no window there. It seems like KWin tries to redraw the windows on the lost output by placing them on the remaining outputs, and that the crash happens during the recalculation of the placement coordinates. As long as there is nothing to place, there is no crash. (Subject line edited accordingly) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor with windows on it
https://bugs.kde.org/show_bug.cgi?id=449957 phrxmd changed: What|Removed |Added Summary|KWin crash in |KWin crash in |KWin::PlacementArea() when |KWin::PlacementArea() when |turning off or unplugging |turning off or unplugging |monitor |monitor with windows on it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453134] KWin Wayland locks up whenever the Zoom comms app enters/leaves a breakout session
https://bugs.kde.org/show_bug.cgi?id=453134 --- Comment #1 from phrxmd --- What would be the best way to get more information on where it's locking up or what's causing it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor
https://bugs.kde.org/show_bug.cgi?id=449957
--- Comment #20 from phrxmd ---
Created attachment 148439
--> https://bugs.kde.org/attachment.cgi?id=148439=edit
Somewhat more detailed backtrace /bt full/
Here's a backtrace with a few more details - here's the portion from Thread 1
in KWin::Workspace::ClientArea():
Thread 1 (Thread 0x7f63142d0980 (LWP 2734) "kwin_wayland"):
#0 KWin::Workspace::clientArea(KWin::clientAreaOption, KWin::AbstractOutput
const*, KWin::VirtualDesktop const*) const (this=0x55bcea23f920,
opt=KWin::PlacementArea, output=, desktop=) at
/usr/src/debug/kwin5-5.24.4-1.1.x86_64/src/workspace.cpp:2288
workArea = {x1 = 0, y1 = 0, x2 = -1, y2 = -1}
effectiveOutput = 0x0
screenArea = {x1 = 0, y1 = , x2 = -1, y2 = -1}
#1 0x7f63197896e6 in
KWin::WorkspaceWrapper::clientArea(KWin::WorkspaceWrapper::ClientAreaOption,
int, int) const (this=0x55bcea5877b0, desktop=,
screen=, option=) at
/usr/src/debug/kwin5-5.24.4-1.1.x86_64/src/scripting/workspace_wrapper.cpp:270
_r = {x1 = , y1 = , x2 = ,
y2 = }
_t = 0x55bcea5877b0
#2 KWin::WorkspaceWrapper::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) (_o=_o@entry=0x55bcea5877b0,
_c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=91,
_a=_a@entry=0x7fff1ab62a70) at
/usr/src/debug/kwin5-5.24.4-1.1.x86_64/build/src/kwin_autogen/7KDSW62DQT/moc_workspace_wrapper.cpp:676
_r = {x1 = , y1 = , x2 = ,
y2 = }
_t = 0x55bcea5877b0
#3 0x7f631978a17b in
KWin::WorkspaceWrapper::qt_metacall(QMetaObject::Call, int, void**)
(this=this@entry=0x55bcea5877b0, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=91, _a=_a@entry=0x7fff1ab62a70) at
/usr/src/debug/kwin5-5.24.4-1.1.x86_64/build/src/kwin_autogen/7KDSW62DQT/moc_workspace_wrapper.cpp:946
#4 0x7f631978a1a1 in
KWin::DeclarativeScriptWorkspaceWrapper::qt_metacall(QMetaObject::Call, int,
void**) (this=0x55bcea5877b0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff1ab62a70) at
/usr/src/debug/kwin5-5.24.4-1.1.x86_64/build/src/kwin_autogen/7KDSW62DQT/moc_workspace_wrapper.cpp:1327
#5 0x7f6318bc51ed in QQmlObjectOrGadget::metacall(QMetaObject::Call, int,
void**) const (this=this@entry=0x7fff1ab62d00,
type=type@entry=QMetaObject::InvokeMetaMethod, index=,
index@entry=96, argv=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.1.x86_64/src/qml/qml/qqmlobjectorgadget.cpp:51
#6 0x7f6318aa4210 in CallMethod (callType=, callArgs=0x2,
engine=, argTypes=, argCount=,
returnType=, index=, object=...) at
/usr/include/qt5/QtCore/qvarlengtharray.h:189
args = {a = 9, s = 4, ptr = 0x7fff1ab62ad0, {array =
"\300\343\274\352\274U\000\000\023\000\000@c\177\000\000\b\b\225\352\274U\000\000\320*\266\032\377\177\000\000\377\377\377\377\000\000\000\000\000\000\000\000c\177\000\000\b\000\000\000\000\000\000\000\000\032f\333\036\215\060x\000\354\240\031c\177\000\000\002\000\000\000\377\377\377\377\001",
'\000' ,
"\354\240\031c\177\000\000\210+\266\032\377\177\000\000\002\000\000\000\000\000\000\000\001\000\000\000c\177\000\000\200+\266\032\377\177\000\000\000\032f\333\036\215\060x\000\354\240\031c\177\000\000\002\000\000\000\377\377\377\377\002",
'\000' , "\300\343\274\352\274U\000\000\001", '\000' ..., q_for_alignment_1 = 94269880460224, q_for_alignment_2 =
4.6575509372957679e-310}}
argData = {a = 9, s = 4, ptr = 0x7fff1ab62a70, {array =
"\314\343\274\352\274U\000\000\370*\266\032\377\177\000\000
+\266\032\377\177\000\000H+\266\032\377\177\000\000\000\000\000\000\000\000@\234\000\032f\333\036\215\060x\000\000\000\000\000\000\000\000\360\376\377\377\377\377\377\377\002\000\000\000\000\000\000",
q_for_alignment_1 = 94269880460236, q_for_alignment_2 =
4.6575509372963607e-310}}
args =
storage = {a = 9, s = 0, ptr = 0x7fff1ab62a30, {array =
"\b+\266\032\377\177\000\000\000\000\000\000\000\000
N\000\000\000\000\000\000\000\000\004\000\000\000\000\000\000\000L+\266\032",
q_for_alignment_1 = 140733641534216, q_for_alignment_2 =
6.9531657496192907e-310}}
unknownTypeError = {d = 0x55bce99ccea0 }
returnType =
#7 CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&,
QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) (object=...,
data=, engine=engine@entry=0x55bcea7c8a10,
callArgs=callArgs@entry=0x7f62ed559a08,
callType=callType@entry=QMetaObject::InvokeMetaMethod) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1569
args =
storage = {a = 9, s = 0, ptr = 0x7fff1ab62a30, {array =
"\b+\266\032\377\177\000\000\000\000\000\000\000\000
N\000\000\000\000\000\000\000\000\004\000\000\000\000\000\000\000L+\266\032",
q_for_alignment_1 = 140733641534216, q_for_alignment_2 =
6.9531657496192907e-310}}
unknownTypeError = {d = 0x55bce99ccea0 }
returnType =
#8 0x7f6318aa5ffb in CallOverloaded (callType=,
propertyCache=, callArgs=, engine
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor
https://bugs.kde.org/show_bug.cgi?id=449957 phrxmd changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #19 from phrxmd --- Unfortunately I can still reproduce the problem in recent 5.24.4 (on OpenSuSE Tumbleweed updated today). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453134] New: KWin Wayland locks up whenever the Zoom comms app enters/leaves a breakout session
https://bugs.kde.org/show_bug.cgi?id=453134 Bug ID: 453134 Summary: KWin Wayland locks up whenever the Zoom comms app enters/leaves a breakout session Product: kwin Version: 5.24.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- SUMMARY KWin Wayland locks up when entering or leaving breakout groups in Zoom (the comms app from https://zoom.us). The mouse pointer freezes and no keyboard input is accepted. The only way out is REISUB or a hard reboot. This happens regardless of whether Zoom is started in regular Wayland, in XWayland (`QT_QPA_PLATFORM=xcb zoom`), or in a separate kwin_wayland session (`export `dbus_launch `, `kwin_wayland --socket test`, `WAYLAND_DISPLAY=test zoom`) Tested with KWin 5.24.4 and the factory RPMs for Zoom 5.10.4 (2845) 64bit on OpenSUSE Tumbleweed. STEPS TO REPRODUCE 1. Open Zoom, join a Zoom conference 2. In the conference, enter or leave breakout groups. OBSERVED RESULT Zoom opens a floating popup window that tells you you're joining the breakout group or rejoining the main session. At this moment KWin locks up. This might be a DBus issue; however, even after waiting for 10 minutes the session does not unfreeze again. EXPECTED RESULT Whatever bugs Zoom may have (see below for other Wayland issues), KWin should not freeze. SOFTWARE/OS VERSIONS Zoom Version: 5.10.4 (2845) Operating System: openSUSE Tumbleweed 20220415 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.2-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Zoom is a Qt application. Zoom has other window management issues on Wayland as well; e.g. when starting Zoom in regular Wayland (i.e. not in XWayland) the Zoom process quits often upon entering a conference. If this happens in a nested Wayland session, an "Error in client communication" message is generated, with the Zoom PID. While this is probably a Zoom bug, these bugs should not lead KWin to lock up. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #16 from phrxmd --- I'm on a trip at the moment and will test again as soon as I have access to the dock, this will be in about 10 days. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450073] System tray applet windows & tray popups mispositioned
https://bugs.kde.org/show_bug.cgi?id=450073 --- Comment #6 from phrxmd --- Seems to be Wayland-specific. It happens to me on some logins, and not on others, right now it's happening again. Is there a way to get more precise information from the system regarding how widgets and popups get their positoning info? I realize that with just screenshots this bug description is not very helpful. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450036] KWin effect animations and desktop switcher flicker and appear pixelated instead of blurred on screen attached to Thunderbolt dock (Wayland)
https://bugs.kde.org/show_bug.cgi?id=450036 phrxmd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #6 from phrxmd --- The Mesa update has fixed the issue. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450405] After moving a native Wayland window to a different virtual desktop it is still considered focused
https://bugs.kde.org/show_bug.cgi?id=450405 phrxmd changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #3 from phrxmd --- I can reproduce this with Kate: if I open Kate on desktop 1, and then use a keyboard shortcut to move it to desktop 2, when I stay on desktop 1 and continue typing the Kate window on desktop 2 receives my keyboard input. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450073] System tray applet windows & tray popups mispositioned
https://bugs.kde.org/show_bug.cgi?id=450073 phrxmd changed: What|Removed |Added Summary|System tray applets |System tray applet windows |mispositioned |& tray popups mispositioned -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450036] KWin effect animations and desktop switcher flicker and appear pixelated instead of blurred on screen attached to Thunderbolt dock (Wayland)
https://bugs.kde.org/show_bug.cgi?id=450036 --- Comment #5 from phrxmd --- (In reply to Fabian Vogt from comment #4) > FWICT, it's part of 21.3.6, which should be part of the next snapshot, > 20220211. OK, when that lands I will test again and report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450073] System tray applets mispositioned
https://bugs.kde.org/show_bug.cgi?id=450073 --- Comment #3 from phrxmd --- Created attachment 146625 --> https://bugs.kde.org/attachment.cgi?id=146625=edit Tray popup opens on the right edge of screen next to the primary screen with the system tray. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450073] System tray applets mispositioned
https://bugs.kde.org/show_bug.cgi?id=450073 --- Comment #2 from phrxmd --- Created attachment 146624 --> https://bugs.kde.org/attachment.cgi?id=146624=edit Tray popup opens on the left edge of the primary screen, when the system tray is on the right. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450073] System tray applets mispositioned
https://bugs.kde.org/show_bug.cgi?id=450073 --- Comment #1 from phrxmd --- Created attachment 146623 --> https://bugs.kde.org/attachment.cgi?id=146623=edit Tray applet opens on the left edgeof the primary screen, when the system tray is on the right. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450073] New: System tray applets mispositioned
https://bugs.kde.org/show_bug.cgi?id=450073 Bug ID: 450073 Summary: System tray applets mispositioned Product: plasmashell Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: philipp.reichm...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY On my two-monitor configuration, where the primary screen on the right contains a panel with the system tray, system tray applets and tooltips appear mispositioned. Applets appear on the left edge of the screen (when the system tray is on the right), tooltips appear either on the left edge, or on the right side of the screen adjacent to it on the left. This is a 5.24 regression; on 5.23.x placement was fine. STEPS TO REPRODUCE 1. Set screen panel configuration as follows: two screens, primary screen on the right, panel with systray on the right screen. 2. Hover over a system tray icon, or click on an icon to open a system tray applet. OBSERVED RESULT See screenshots: System tray applets open on the left edge of the primary screen; hover tooltips open either on the left edge of the primary screen, or on the right edge of the screen left to it. EXPECTED RESULT System tray applets and tooltips should open where the respective system tray icon is. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220207 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 phrxmd changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #10 from phrxmd --- (In reply to Nate Graham from comment #7) > Was there any more? I see this, which is quite helpful: > > Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault. > KWin::Workspace::clientArea (this=0x557a5b0fcfd0, opt=KWin::PlacementArea, > output=, desktop=) at > /usr/src/debug/kwin5-5.24.0-1.1.x86_64/src/workspace.cpp:2288 > 2288 screenArea = effectiveOutput->geometry(); > > ...However the attachment does not include the rest of thread 1. Could you > see if that was truncated, and attach it? Unfortunately that's all the `kwin_wayland.gdb` file contains. Attaching a debugger to KWin Wayland seems to be tricky. I'll try getting another laptop ready to ssh into my machine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 phrxmd changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #14 from phrxmd --- (In reply to Nate Graham from comment #13) > Reminds me of Bug 449212. Some questions: > > 1. When your system is in this state, does it get fixed if you restart > plasmashell with `plasmashell --replace`? I just tried it. `plasmashell --replace` seems to the issue mostly. After `plasmashell --replace` I end up in a state where the wallpaper is shown correctly initially until I either click on it or move the mouse to another screen, then it is displayed "scaled twice" again. This persists until I change virtual desktops at least once, then the wallpaper remains displayed correctly. > 2. What kind of GPU do you have? Intel 620 in the laptop, plus the Thunderbolt dock the external monitor is attached to. > 3. Is this a regression from Plasma 5.23? No. I first reported this with 5.23.2, it's persisted since then. See comment 4 for the original system information, back then I had forgotten to put it in the original post. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450036] KWin effect animations and desktop switcher flicker and appear pixelated instead of blurred on screen attached to Thunderbolt dock (Wayland)
https://bugs.kde.org/show_bug.cgi?id=450036 --- Comment #2 from phrxmd --- Applies to the Overview effect as well. I had reported earlier as bug 449961, without realizing that the behaviour there is monitor-specific. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450036] KWin effect animations and desktop switcher flicker and appear pixelated instead of blurred on screen attached to Thunderbolt dock (Wayland)
https://bugs.kde.org/show_bug.cgi?id=450036 --- Comment #1 from phrxmd --- *** Bug 449961 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449961] Overview flickers whenever window or content changes
https://bugs.kde.org/show_bug.cgi?id=449961 phrxmd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from phrxmd --- Sorry, that's bug 450036, not 449961 (which is this one). *** This bug has been marked as a duplicate of bug 450036 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449961] Overview flickers whenever window or content changes
https://bugs.kde.org/show_bug.cgi?id=449961 --- Comment #1 from phrxmd --- It appears this is specific to the monitor - on one screen which is attached to a Thunderbolt dock it flickers, on the internal screen of my laptop it does not. The effect behaves similar to bug 449961, so I'm marking this as a duplicate since 449961 is the more general description. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 --- Comment #14 from phrxmd --- I reported the "no local menubar in GTK3 application windows" issue separately as bug 450038. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450038] No menubar at all in Wayland with GTK3 applications (neither global nor in app window)
https://bugs.kde.org/show_bug.cgi?id=450038 phrxmd changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450038] New: No menubar at all in Wayland with GTK3 applications (neither global nor in app window)
https://bugs.kde.org/show_bug.cgi?id=450038 Bug ID: 450038 Summary: No menubar at all in Wayland with GTK3 applications (neither global nor in app window) Product: plasmashell Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: philipp.reichm...@gmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 146599 --> https://bugs.kde.org/attachment.cgi?id=146599=edit Screenshot of Inkscape, with no global menu, and no application menubar either SUMMARY I use the Global Menu applet and have appmenu-gtk2-module and appmenu-gtk3-module installed. In Wayland, whenever I start a GTK3 application, it shows no menu at all: the menu does not get exported to the Global Menu, but the application window does not show a menu bar either - see attached screenshot. I tested this with Inkscape, GLabels and Electron-based apps (signal-desktop in my case). It looks as if the Global Menu does not detect the menu (bug 424485), but the application is expecting its menu to be drawn by somebody else anyway. It would be good if the apps could at least draw their own menu in their window. Currently for me the only workaround to access menu-based functionality is to launch the application in XWayland, with the associated problems regarding scaling etc. STEPS TO REPRODUCE 1. With the global menu applet enabled, and appmenu-gtk-module installed, launch a GTK3 app (tested with Inkscape, GLabels and signal-desktop) OBSERVED RESULT The application's menu does not appear in the global menu, but the window contains no menu bar either. All menu functions are inaccessible. EXPECTED RESULT The global menu should show the application's menu; or, barring that, at least the application's window should show a menu bar. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220207 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 phrxmd changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #18 from phrxmd --- I can't reproduce it on 5.24.0 anymore. Closing this for now, will reopen if it happens again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450036] New: KWin effect animations and desktop switcher flicker and appear pixelated instead of blurred on screen attached to Thunderbolt dock (Wayland)
https://bugs.kde.org/show_bug.cgi?id=450036 Bug ID: 450036 Summary: KWin effect animations and desktop switcher flicker and appear pixelated instead of blurred on screen attached to Thunderbolt dock (Wayland) Product: kwin Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- SUMMARY KWin effects that involve blur and animated transitions flicker and appear grainy and pixelated on a screen that is attached to a Thunderbolt 3 dock. On the built-in screen of my laptop, they appear smooth and blurred as they should. It's hard to take videos or screenshots of KWin effects with Spectacle or OBS, but a phone video showing the effect on both monitors is here: https://youtu.be/ELo-a4dDKh0 The laptop is a Thinkpad X1 Yoga, the dock in question is a Lenovo Thunderbolt 3 dock. The bug appears only on Wayland. It has been around for a while, it's not a 5.24 regression. STEPS TO REPRODUCE 1. Place the mouse on the screen attached to the Thunderbolt dock 2. Invoke the virtual desktop switcher OR a KWin effect that involves animated transitions (tested with Cover Switch and Flip Switch) OBSERVED RESULT Animations and transitions flicker and appear grainy and pixelated, instead of smooth and blurred. EXPECTED RESULT The effects should look smooth and blurred everywhere. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220207 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash when turning off or unplugging monitor
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #6 from phrxmd --- In addition, when KWin comes back up again from the crash, the Plasma wallpaper is scaled incorrectly on a HiDPI display - as if it has the scaling factor for that monitor applied twice. It's as if before the crash there was a cached version of the wallpaper with the HiDPI scaling, and after the crash, when KWin comes up again, it reads the cached wallpaper and applies the HiDPI scaling to it again. See bug 445160 for photos of the desktop arrangement before and after the crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #12 from phrxmd --- Created attachment 146594 --> https://bugs.kde.org/attachment.cgi?id=146594=edit Wallpaper setup after KWin crash and restart (National Geographic POTD with KWin scaling applied twice) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #11 from phrxmd --- Created attachment 146593 --> https://bugs.kde.org/attachment.cgi?id=146593=edit Wallpaper setup before KWin crash (National Geographic POTD scaled correctly) -- You are receiving this mail because: You are watching all bug changes.
