[plasmashell] [Bug 445461] New: Task manager shows empty thumbnails
https://bugs.kde.org/show_bug.cgi?id=445461 Bug ID: 445461 Summary: Task manager shows empty thumbnails Product: plasmashell Version: 5.23.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: oii...@yahoo.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When I hover the mouse over a taskbar icon, the thumbnails are often empty or garbled. Wayland-session.log shows the following lines every time this happens: https://pastebin.com/42VsUDin "无效的参数" means "invalid argument" in Chinese. This issue first happened when pipewire was upgraded from 0.3.33 to 0.3.39 and pipewire-media-session replaced by wireplumber. However, rolling back that upgrade does not fix the issue. STEPS TO REPRODUCE Identical to Bug 444107. OBSERVED RESULT Empty or garbled thumbnails. EXPECTED RESULT Thumbnails correctly shown and no error logged. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Bookworm (testing) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.0-2-amd64 (using amdgpu driver) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 445460] New: [kded5] Systemd-coredump
https://bugs.kde.org/show_bug.cgi?id=445460 Bug ID: 445460 Summary: [kded5] Systemd-coredump Product: frameworks-kded Version: 5.87.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: fa...@kde.org Reporter: yelmusa...@vusra.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 143531 --> https://bugs.kde.org/attachment.cgi?id=143531&action=edit Coredump_Logfile SUMMARY *** I was monitoring Journalctl and noticed Systemd was core dumping kded5. I haven't noticed any issues (performance or graphical) using the desktop and only reported due to Systemd's recommendation, "This usually indicates a programming error in the crashing program and should be reported to its vendor as a bug" *** STEPS TO REPRODUCE OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux x86_64 / 5.23.3-1 (available in About System) KDE Plasma Version: plasma-desktop 5.23.3-1 KDE Frameworks Version: plasma-framework 5.87.0-1 Qt Version: qt5-base 5.15.2+kde+r254-1 ADDITIONAL INFORMATION More than happy to supply with more information, ask away. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445422] digikam not compliant with pipewire jack library
https://bugs.kde.org/show_bug.cgi?id=445422 --- Comment #11 from Philippe ROUBACH --- Created attachment 143530 --> https://bugs.kde.org/attachment.cgi?id=143530&action=edit digikam verbose result of export QT_LOGGING_RULES="digikam*=true" digikam -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445459] SelectableLabel.qml:36:5: QML TextArea: Binding loop detected for property "implicitHeight"
https://bugs.kde.org/show_bug.cgi?id=445459 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/380 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 445429] KPA Viewer crashes on arrow-key up
https://bugs.kde.org/show_bug.cgi?id=445429 --- Comment #4 from Tobias Leupold --- Ah, I forgot we have multiple backends by now. My bad … -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445459] New: SelectableLabel.qml:36:5: QML TextArea: Binding loop detected for property "implicitHeight"
https://bugs.kde.org/show_bug.cgi?id=445459 Bug ID: 445459 Summary: SelectableLabel.qml:36:5: QML TextArea: Binding loop detected for property "implicitHeight" Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: qydwhotm...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When a notification with icon appears, a binding loop will be detected. file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/SelectableLabel.qml:36:5: QML TextArea: Binding loop detected for property "implicitHeight" Example: Element new message notification Operating System: openSUSE Tumbleweed 2020 KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 444407] Phonon audio notification leaks file descriptors
https://bugs.kde.org/show_bug.cgi?id=07 --- Comment #1 from Jasem Mutlaq --- We keep getting more reports from users where KStars using Phonon notifications is breaking their system: https://indilib.org/forum/ekos/10705-kstars-ekos-freezing-on-large-image-sequences-astroberry.html#77529 Is this some packaging issue? Phonon issue? upstream? downstream? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445432] started system setting: crash
https://bugs.kde.org/show_bug.cgi?id=445432 philipp.kn...@web.de changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from philipp.kn...@web.de --- Seems to be caused by incomplete update/upgrade files/packages: https://www.preining.info/blog/2021/10/kde-plasma-5-23-25th-anniversary-edition-for-debian/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445430] kinfocenter crash after app start
https://bugs.kde.org/show_bug.cgi?id=445430 philipp.kn...@web.de changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from philipp.kn...@web.de --- Seems to be caused by incomplete update/upgrade files/packages: https://www.preining.info/blog/2021/10/kde-plasma-5-23-25th-anniversary-edition-for-debian/ -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 296526] Dolphin is too slow when upload a file on a SSH server
https://bugs.kde.org/show_bug.cgi?id=296526 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 339830] Slow file transfer (fish, sshfs)
https://bugs.kde.org/show_bug.cgi?id=339830 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 147948] copying via fish stalls
https://bugs.kde.org/show_bug.cgi?id=147948 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 394744] Dolphin cannot browse archives that are not named with the appropriate extension
https://bugs.kde.org/show_bug.cgi?id=394744 --- Comment #3 from Kishore Gopalakrishnan --- The behaviour has changed (but still does not work as expected). Now, instead of showing 'invalid protocol', it just appears to enter the zip archive (that is named without an appropriate extension) and says 'the folder is empty' (even if the archive is not empty). The 'Extract' option appears correctly (and works as expected) in the right-click menu. Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 21.5 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 154469] composing mail and settings: redesign default identity behaviour (default identity per recipent)
https://bugs.kde.org/show_bug.cgi?id=154469 Prajna Sariputra changed: What|Removed |Added Component|general |general Resolution|WAITINGFORINFO |--- Status|RESOLVED|REOPENED Platform|openSUSE RPMs |Archlinux Packages Product|kmail |kmail2 CC||putr...@gmail.com Ever confirmed|0 |1 --- Comment #3 from Prajna Sariputra --- > Instead of creating a new feature request, please confirm here if the > wishlist is still valid for kmail2. This feature is not present in KMail 5.18.3, so I believe it is still valid. I found myself almost sending emails with the wrong identity a few times recently, so having this option would be quite helpful to prevent that, especially in my case since I only ever use one of my identities to send emails to people in two specific domains anyway. Alternatively, simply having an option to not have a default identity (and thus have KMail ask which one to use every time) would also work for me personally. P.S. Bugzilla's similar/related bugs feature when adding a new bug is what led me here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 s1994...@yahoo.com.tw changed: What|Removed |Added Version|5.21.90 |5.23.3 --- Comment #10 from s1994...@yahoo.com.tw --- Still happened on 5.23.3 If application starts in maximized state, after dragging window, it is still in maximized state but "Restore" button has became "Maximize" button. And, click "Maximize" button, it doesn't work in the most time. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 312003] meta information displays old information
https://bugs.kde.org/show_bug.cgi?id=312003 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441569] Freehand Selection Tool produces severe artifacts when holding Ctrl to draw polygonal outline
https://bugs.kde.org/show_bug.cgi?id=441569 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444634] dbus-daemon spamming about full message queue from kwin_x11 a few hours after startup
https://bugs.kde.org/show_bug.cgi?id=444634 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 444444] Drop down menu for drives is shoving snaps
https://bugs.kde.org/show_bug.cgi?id=44 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 441666] Operations on a Skrooge file with many movements take some time to complete
https://bugs.kde.org/show_bug.cgi?id=441666 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 437864] Template search and edit changes non-relevant entries
https://bugs.kde.org/show_bug.cgi?id=437864 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 445458] New: Investment Cap Gains by Account (Customized) crashes with my dataset. Changing the date of one ledger entry fixes the crash.
https://bugs.kde.org/show_bug.cgi?id=445458 Bug ID: 445458 Summary: Investment Cap Gains by Account (Customized) crashes with my dataset. Changing the date of one ledger entry fixes the crash. Product: kmymoney Version: 5.1.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: patr...@lestrade.com Target Milestone: --- Created attachment 143529 --> https://bugs.kde.org/attachment.cgi?id=143529&action=edit Kmymoney file for client Walter White. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Load my file KM1.kmy 2. Go to Reports and choose Inv. Cap Gains by Account (Custom) (N.B. I did not create that custom report) 3. Crash. Restart 4. Go into ledger for "MethProfits". Change the date of the 737.85 ADDED Shares from 10/10/17 to 10/10/10 (mm/dd/yy) 5. Repeat step 3 above. This time it does not crash. OBSERVED RESULT Wife leaves me. etc EXPECTED RESULT SOFTWARE/OS VERSIONS Ubuntu/Gnome ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 358713] Cannot copy text in package descriptions
https://bugs.kde.org/show_bug.cgi?id=358713 --- Comment #2 from Martin Thomas --- The problem still persists. I - and maybe many other people - now use Synaptic instead of apper as it has a far better interface, so fixing the problem is probably not very important. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 440663] Ark opens a new instance of Dolphin after compression/extraction via Dolphin
https://bugs.kde.org/show_bug.cgi?id=440663 burster changed: What|Removed |Added CC||burs...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445444] wrong window size for alacritty terminal emulator
https://bugs.kde.org/show_bug.cgi?id=445444 --- Comment #2 from Chang Liu --- Typo. Downgrading to kwin 5.23.2 can solve this issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445444] wrong window size for alacritty terminal emulator
https://bugs.kde.org/show_bug.cgi?id=445444 --- Comment #1 from Chang Liu --- I got the same issue for kwin-5.23.3. Downgrading kwin to 5.22 can solve this issue temporarily. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 440663] Ark opens a new instance of Dolphin after compression/extraction via Dolphin
https://bugs.kde.org/show_bug.cgi?id=440663 --- Comment #30 from Patrick Silva --- I get the same results on both X11 and Wayland sessions of my neon unstable. The bug no longer occurs if 'Open new folders in tabs' option is checked in Dolphin settings. If said option is unchecked, both "Extract archive here' and 'Extract archive here, autodetect subfolder' options from conttext menu open a new instance of Dolphin after extraction. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445457] Showing a window before disabling resizing (GTK4 dialogs) results in incorrect title bar buttons
https://bugs.kde.org/show_bug.cgi?id=445457 --- Comment #1 from nyanpasu64 --- Created attachment 143528 --> https://bugs.kde.org/attachment.cgi?id=143528&action=edit The bug in a Qt Widgets app -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445457] New: Showing a window before disabling resizing (GTK4 dialogs) results in incorrect title bar buttons
https://bugs.kde.org/show_bug.cgi?id=445457 Bug ID: 445457 Summary: Showing a window before disabling resizing (GTK4 dialogs) results in incorrect title bar buttons Product: kwin Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: nyanpas...@tuta.io Target Milestone: --- Created attachment 143527 --> https://bugs.kde.org/attachment.cgi?id=143527&action=edit The bug in gtk4-demo SUMMARY In X11 apps which first map a window, *then* call XSetWMNormalHints or send WM_NORMAL_HINTS to disable resizing (which hides kwin_x11's Maximize button), KWin fails to recompute the title bar layout and right-align the buttons. STEPS TO REPRODUCE 1. Run gtk4-demo. 2. Scroll down to Dialogs and click Run. OBSERVED RESULT The title bar contains a minimize button, close button, and a blank space to the right (where the close button would be, if a maximize button was present). EXPECTED RESULT The title bar is properly right-aligned. I don't know if GTK4 is wrong for mapping a window before disabling resize, or if KWin is wrong for rendering the title bar incorrectly when resizability is toggled after a window is mapped, or both. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GT 730/PCIe/SSE2 ADDITIONAL INFORMATION First reported in https://bugs.kde.org/show_bug.cgi?id=439137#c1. I investigated the root cause at https://gitlab.gnome.org/GNOME/gtk/-/issues/4090#note_1309466. I decided to split it out since it's a different issue. This happens by default in GTK4 dialogs, but I was also able to reproduce this effect in a Qt app by calling `dialog->layout()->setSizeConstraint(QLayout::SetFixedSize)` (which disables resizing) after the dialog is shown. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445456] New: Multiple GPU hangs upon display of notifications or hovering-over a panel
https://bugs.kde.org/show_bug.cgi?id=445456 Bug ID: 445456 Summary: Multiple GPU hangs upon display of notifications or hovering-over a panel Product: plasmashell Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: carterisonl...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 143526 --> https://bugs.kde.org/attachment.cgi?id=143526&action=edit Logs from journalctl from when I was testing the bug SUMMARY When receiving a notification, hovering-over a panel, or clicking on/hovering over a panel item, the GPU will hang for 5-10 seconds. After the effect, the GPU will stop hanging, but will cause widgets to stop appearing when clicked on if they're on a panel. Hovering over panel items, even in edit mode, will not show labels or context options like they're supposed to after the effect. Despite this, right-clicking on widgets or the panel still works as intended. STEPS TO REPRODUCE 1. Use Mesa with Intel's integrated graphics (Xe/Tiger Lake) as the primary graphics card 2. Have the below versions of software 3. Start KDE Plasma using startplasma-x11 4. Recieve a notification or hover over/interact with a panel 5. The GPU will hang for 5-10 seconds 6. After the effect, certain displays described above will stop appearing. OBSERVED RESULT The GPU hangs for 5-10 seconds, often multiple times, and causes certain displays to stop appearing. EXPECTED RESULT Notifications and hover-over actions correctly render. SOFTWARE/OS VERSIONS Linux: 5.15.2-zen1-1-zen (x86_64) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION GPU: Intel Tigerlake Xe Graphics (Gen12) Graphics Platform: X11 Logs attached below =-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441074] windows with "keep above others" option don't stay above windows in "windowed fullscreen" mode.
https://bugs.kde.org/show_bug.cgi?id=441074 --- Comment #9 from Nate Graham --- You can do it at the user level today with KWin window rules. This bug report is about us shipping such a window rule for everyone by default. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445095] Touchpad Applet is missing
https://bugs.kde.org/show_bug.cgi?id=445095 --- Comment #4 from Nate Graham --- See https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/690 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441569] Freehand Selection Tool produces severe artifacts when holding Ctrl to draw polygonal outline
https://bugs.kde.org/show_bug.cgi?id=441569 --- Comment #3 from Tyson Tan --- Thanks Dmitry, although it still produces slight artifacts as the traces of the straight line, it's much less obvious now. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 440663] Ark opens a new instance of Dolphin after compression/extraction via Dolphin
https://bugs.kde.org/show_bug.cgi?id=440663 --- Comment #29 from Andrey --- (In reply to Steve Vialle from comment #27) > (In reply to Andrey from comment #10) > > This was fixed in master: > > https://invent.kde.org/system/dolphin/-/merge_requests/261, > > maybe need to backport to some "release" branch. > > While this does apply cleanly to the dolphin 21.08.3 release branch, it does > _not_ fix the problem, at least not on X11. Sorry for the confusion, this probably were two different bugs with similar symptoms, which results they both have been tracked here in one issue. So this was original fix: https://invent.kde.org/system/dolphin/-/merge_requests/258 And these are mostly tested on Wayland: https://invent.kde.org/system/dolphin/-/merge_requests/261 https://invent.kde.org/frameworks/kio/-/merge_requests/554 The latter two were not backported to stable but solved the issue on Wayland for me, it would be good if someone confirm on Neon unstable in VM e.g -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444569] Keyboard layout shortcuts activate wrong language [regression]
https://bugs.kde.org/show_bug.cgi?id=444569 --- Comment #7 from Andrey --- In 5.21.4 we had old layouts widget maybe? They look a bit different, if you trouble to compare I can check for sure. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445451] some screen geometry detection critically buggy
https://bugs.kde.org/show_bug.cgi?id=445451 --- Comment #1 from David Chmelik --- My top screen is 1600x1200--I hope you still take such case (4:3 shape screens including some resolutions lower than this) into consideration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445455] New: If the main tabbox switcher fails to load, the alternative switcher will also fail to load
https://bugs.kde.org/show_bug.cgi?id=445455 Bug ID: 445455 Summary: If the main tabbox switcher fails to load, the alternative switcher will also fail to load Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: isma...@gmail.com Target Milestone: --- SUMMARY When the main tabbox switcher fails to load, an alternative working switcher will also fail to load (or viceversa). To be able to load the working switcher, it has to be reloaded or kwin restarted STEPS TO REPRODUCE 1. Set a failing window switcher as the main switcher, and a working one as the alternative 2. Try to launch the failing switcher: It will fail to load and notify the error 3. Now try to launch the alternative (working) switcher OBSERVED RESULT The alternative working switcher also fails to load EXPECTED RESULT Every switcher should only be held accountable by there own merits :) SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-21-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445454] New: programs usually open on a different screen
https://bugs.kde.org/show_bug.cgi?id=445454 Bug ID: 445454 Summary: programs usually open on a different screen Product: plasmashell Version: 5.23.2 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dchme...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY If you have two or (like I have) three or more screens, programs usually open on a different screen. STEPS TO REPRODUCE 1. Select a screen with the left mouse button. 2. Use that screen's menu to open a program. 3. Probably see it open on a random screen. OBSERVED RESULT Program often open on a screen other than I selected/started it on, not always even the primary display (which might be expected) but a totally random screen. KDE programs are particularly bad at this. Other programs like non-KDE IRC, web browsers, text editors, usually opened on the primary display, don't tend to do this. It's usually that I open konsole on the right-hand screen and dolphin on the upper screen but they usually open on a random screen, sometimes my main/left-hand one or the top one. EXPECTED RESULT Open programs on the same screen as beforehand selected and as the menu that opened them. If someone moves the mouse to another screen before it starts, I don't know if that must change it or if people could be given an option. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.23.2 KDE Plasma Version: Slackware64-current / 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445453] New: system settings crash
https://bugs.kde.org/show_bug.cgi?id=445453 Bug ID: 445453 Summary: system settings crash Product: systemsettings Version: 5.23.3 Platform: Debian unstable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: d...@dccathome.com Target Milestone: --- Application: systemsettings5 (5.23.3) Qt Version: 5.15.2 Frameworks Version: 5.88.0 Operating System: Linux 5.14.0-4-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux bookworm/sid DrKonqi: 5.23.3 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: opening system settings - Custom settings of the application: using sid I just updated the system and that is when the crash happened. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7f73d5b337c2 in QV4::QQmlTypeWrapper::virtualInstanceOf(QV4::Object const*, QV4::Value const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7f73d5a212b7 in QV4::Runtime::Instanceof::call(QV4::ExecutionEngine*, QV4::Value const&, QV4::Value const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f73d5a0d295 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f73d5a11cf7 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f73d59ad56d in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f73d5b243c5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7f73d5b294c4 in QQmlBinding::evaluate(bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7f73d5b2d367 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7f73d5b2b144 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7f73d5b377e3 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7f73d5acc86c in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7f73d5aceafe in QQmlComponentPrivate::completeCreate() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7f73d5acfbf0 in QQmlComponent::createObject(QQmlV4Function*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7f73d5ad0693 in QQmlComponent::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x7f73d5b086fd in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #19 0x7f73d59f3ba6 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x7f73d5a0f1cf in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7f73d5a11cf7 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7f73d59ad56d in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7f73d5b243c5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7f73d5ad858b in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7f73d5ad8a70 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7f73d5b081ad in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #27 0x7f73d6c6a4dd in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f73d5b7fcf3 in QQmlTimer::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7f73d5b086fd in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #30 0x7f73d59f13ce in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #31 0x7f73d59f395a in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #32 0x7f73d5a0f1cf in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #33 0x7f73d5a11cf7 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #34 0x7f73d59ad56d in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #35 0x7f73d5b243c5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #36 0x7f73d5ad858b in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #37 0x7f73d5ad8a70 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #38 0x7f73d5b081ad in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #39 0x0
[plasma-pa] [Bug 445452] New: Swap the "Configure Audio Volume" Button with "Configure Audio Devices.." when right clicking tray icon
https://bugs.kde.org/show_bug.cgi?id=445452 Bug ID: 445452 Summary: Swap the "Configure Audio Volume" Button with "Configure Audio Devices.." when right clicking tray icon Product: plasma-pa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: jess...@jessicamaybe.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 143525 --> https://bugs.kde.org/attachment.cgi?id=143525&action=edit Picture highlighting the button I am talking about The button shown in the attachment "volume_1.png" should open the audio system settings panel rather than the settings menu for the applet. The applet settings button should instead be in the hamburger menu. When I'm trying to configure my audio devices, my first instinct on what to click is the settings button in the volume mixer that has the hover text "Configure Audio Volume". It doesn't actually open the System Settings audio tab. It's rather confusing because the same button in other tray icons do open their respective System Settings menu. For example, see the Networking, Bluetooth, Notifications, or Disks and Devices tray icons. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445438] If plasmashell has been restarted in a session, the widget explorer does not open at all
https://bugs.kde.org/show_bug.cgi?id=445438 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 439159 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439159] "Add widgets..." and "Show alternatives..." options from context menu stop working after manually restarting plasmashell process
https://bugs.kde.org/show_bug.cgi?id=439159 Patrick Silva changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #15 from Patrick Silva --- *** Bug 445438 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 443958] Kmail/Akregator/Kleopatra etc crash/segmentation fault when quitting the applications
https://bugs.kde.org/show_bug.cgi?id=443958 James Beddek changed: What|Removed |Added Summary|Kmail crash/segmentation|Kmail/Akregator/Kleopatra |fault when quitting the |etc crash/segmentation |application |fault when quitting the ||applications --- Comment #2 from James Beddek --- This turns out to be due to UB in qtspeech when compiled with Clang 13.0.0. I have opened a relevant Qt bug report here: https://bugreports.qt.io/projects/QTBUG/issues/QTBUG-98321 I was not able to fix it myself, though perhaps someone from KDE might be able to :-). Below is the ubsan report: telans@desktop ~ $ LD_PRELOAD=/usr/lib/clang/13.0.0/lib/linux/libclang_rt.ubsan_standalone-x86_64.so kmail Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls") FolderCollectionMonitor::~FolderCollectionMonitor() MailCommon::FolderCollectionMonitor(0x55c6c95d9cd0) /var/tmp/portage/dev-qt/qtspeech-5.15.2-r1/work/qtspeech-everywhere-src-5.15.2/src/tts/qtexttospeech.cpp:87:15: runtime error: member call on address 0x55c6c9c535f0 which does not point to an object of type 'QTextToSpeech' 0x55c6c9c535f0: note: object is of type 'QObject' 00 00 00 00 48 c6 79 2b d2 7f 00 00 d0 27 c5 c9 c6 55 00 00 6e 66 69 67 00 00 00 00 41 00 00 00 ^~~ vptr for 'QObject' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /var/tmp/portage/dev-qt/qtspeech-5.15.2-r1/work/qtspeech-everywhere-src-5.15.2/src/tts/qtexttospeech.cpp:87:15 in /var/tmp/portage/dev-qt/qtspeech-5.15.2-r1/work/qtspeech-everywhere-src-5.15.2/src/tts/qtexttospeech.cpp:263:5: runtime error: member call on address 0x55c6c9c535f0 which does not point to an object of type 'QTextToSpeech' 0x55c6c9c535f0: note: object is of type 'QObject' 00 00 00 00 48 c6 79 2b d2 7f 00 00 d0 27 c5 c9 c6 55 00 00 6e 66 69 67 00 00 00 00 41 00 00 00 ^~~ vptr for 'QObject' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /var/tmp/portage/dev-qt/qtspeech-5.15.2-r1/work/qtspeech-everywhere-src-5.15.2/src/tts/qtexttospeech.cpp:263:5 in -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445451] New: some screen geometry detection critically buggy
https://bugs.kde.org/show_bug.cgi?id=445451 Bug ID: 445451 Summary: some screen geometry detection critically buggy Product: plasmashell Version: 5.23.0 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dchme...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Sometimes when I open, for example, dolphin, from the upper screen menu, but it opens on my lower screen, I move it to my upper screen, but unless I keep it partially past the left or right edge (though I don't think it should be possible to go past the edge) it will jump back down to the lower screen. If I want it on the upper screen I'm forced to maximize it (which I normally wan to anyway but prefer to do after fitting it into the screen manually, which if I try to do, it jumps back down.) STEPS TO REPRODUCE 1. Open a program intended for the upper screen, but might open on a lower screen. 2. Try to size it to the upper screen. 3. See it jump back down. OBSERVED RESULT Depending how you move a program from the lower to upper screen and start moving/sizing it there, it may jump back down to the lower screen, because some of the geometry calculations are off. EXPECTED RESULT Once you have a program on the upper screen, don't force it back down onto the lower one just from moving/sizing it without going below the upper one. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64-current / 5.23.2 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I wish I could make a video for you but don't think I'm going to be able to. Let me know if I need to describe more. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444516] Crash while painting
https://bugs.kde.org/show_bug.cgi?id=444516 Tiar changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com --- Comment #18 from Tiar --- @David, to get a more useful console output, please create a file called `.gdbinit` in your home directory with this line: `set print thread-events off` It will remove all those annoying `[New Thread 0x7fff2a37a700 (LWP 284671)]` and leave just things either Krita or Qt print out, mostly warnings or some config info. It also shows all asserts and safe asserts. Safe asserts might also appear in Help -> Show Krita log for bug reports, can you please check it? You probably should scroll to the very bottom. --- `Still unsignalled after processed 129 tiles` that actually sounds worrying, maybe @Dmitry will know what's up with that. That line was added only recently, two months ago, in this commit: https://invent.kde.org/graphics/krita/-/commit/191e0da9d2a4770f996b89f8e657eef90a79e207 > Proof of concept implementation of multibuffered tile uploading --- Since it's related to OpenGL, @David does the crash happen every time you paint, or maybe so often that you'd notice if it doesn't crash? If so, can you please try 1) without "Use Texture Buffer" in Display -> Canvas Acceleration; and 2) without Graphics Acceleration altogether, and see if it crashes then as well? I'm assigning Dmitry, thoush maybe someone else, like Amyspark or Ivanyossi, could help too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445450] New: KDE uses language at end of list for messages/errors
https://bugs.kde.org/show_bug.cgi?id=445450 Bug ID: 445450 Summary: KDE uses language at end of list for messages/errors Product: plasmashell Version: 5.23.0 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dchme...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY KDE seems to often/usually use languages from the end of the regional settings list. I had in order British English, American English, Greek. I was usually getting popup/error/etc. messages in Greek. I removed it (just kept the alternative keyboard layout) but it's still happening. STEPS TO REPRODUCE 1. Add languages in regional settings. 2. Do something to get a message. 3. See that it uses last, not first language on the list. OBSERVED RESULT Uses last language on your list for messages. Konsole errors, also various non-KDE program tool-tips, and others did this. EXPECTED RESULT Use first language on your list for messages. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64-current / 5.23.2 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 445429] KPA Viewer crashes on arrow-key up
https://bugs.kde.org/show_bug.cgi?id=445429 Johannes Zarl-Zierl changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/commit/9b6 ||67402baa764ba04304e5325cf75 ||fff0de0c7e --- Comment #3 from Johannes Zarl-Zierl --- Git commit 9b667402baa764ba04304e5325cf75fff0de0c7e by Johannes Zarl-Zierl. Committed on 14/11/2021 at 00:55. Pushed by johanneszarl into branch 'master'. Fix crash when PhononDisplay is not yet initialized M +3-3Viewer/PhononDisplay.cpp https://invent.kde.org/graphics/kphotoalbum/commit/9b667402baa764ba04304e5325cf75fff0de0c7e -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #26 from Sebastian E. --- KSysGuard and KDE System Monitor are system utilities, and as such should first and foremost display system information as it is. Any processing that helps to better dig through and display that information is a nice-to-have option, but should only be that - an option. * This is not macOS running exclusively on a limited, well-known set of Apple hardware. Any attempt to properly clean up a raw list of sensors is futile. * There's the kernel, lm_sensors, and systemd-sensorsd suddenly popping up wouldn't surprise me. That's the layer were cleanup should happen. Doing it at the application layer is conceptually wrong (but of course still a nice-to-have option, especially when the layers below leave something to be desired). * There's a reason why people choose a particular OS and desktop environment. And sometimes that choice changes when beginners become experts. Don't look to macOS or Windows as if the grass was greener there, just because it's more polished. KDE is the side with the greenest grass. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425385] Desktop freezes after taking a screenshot
https://bugs.kde.org/show_bug.cgi?id=425385 --- Comment #52 from Nick Stefanov --- Thank you! Let's hope they'll fix it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 --- Comment #1 from Jon Voss --- Created attachment 143524 --> https://bugs.kde.org/attachment.cgi?id=143524&action=edit tail of journal where issue occurred -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] New: Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 Bug ID: 445449 Summary: Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM Product: kwin Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jonv...@outlook.com Target Milestone: --- Created attachment 143523 --> https://bugs.kde.org/attachment.cgi?id=143523&action=edit picture of issue SUMMARY When issuing a shutdown or restart from within a Plasma Wayland session, there is a 1 min. 30 sec. delay while waiting for systemd to stop Simple Desktop Display Manager. This times out and forces a SIGKILL to sddm and associated processes. If I log out of my session and shutdown/reboot directly from sddm, this issue does not occur. Shutdown is instantaneous. I cannot reproduce in the X11 session. It only occurs in Wayland. It also did not occur prior to 5.23.3. A relevant portion of my shutdown log is attached. Not much to see, unfortunately. Let me know if I can help in any way. STEPS TO REPRODUCE 1. Log in to Plasma Wayland 2. Applcation Launcher -> Shutdown (or Restart) OBSERVED RESULT Shutdown hangs on SDDM. EXPECTED RESULT Shutdown should be instantaneous. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT ADDITIONAL INFORMATION Does this fix? https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1177 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445444] wrong window size for alacritty terminal emulator
https://bugs.kde.org/show_bug.cgi?id=445444 Chang Liu changed: What|Removed |Added CC||goduck...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 445429] KPA Viewer crashes on arrow-key up
https://bugs.kde.org/show_bug.cgi?id=445429 Johannes Zarl-Zierl changed: What|Removed |Added Ever confirmed|0 |1 CC||johan...@zarl-zierl.at Status|REPORTED|CONFIRMED --- Comment #2 from Johannes Zarl-Zierl --- I can reproduce this using the phonon video backend, but not the VLC one (which fits the backtrace that you sent). Interestingly enough, the crash is triggered with images not just videos. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445448] New: [Wayland] Jagged cursor in Firefox, but MOZ_ENABLED_WAYLAND is enabled
https://bugs.kde.org/show_bug.cgi?id=445448 Bug ID: 445448 Summary: [Wayland] Jagged cursor in Firefox, but MOZ_ENABLED_WAYLAND is enabled Product: kwin Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: poperi...@mailbox.org Target Milestone: --- Flags: Wayland+ Created attachment 143522 --> https://bugs.kde.org/attachment.cgi?id=143522&action=edit A screenshot of a cursor with jagged edges, while hovering over Firefox SUMMARY The edges of my cursor are jagged when ever I mouse over Firefox, but the `MOZ_ENABLED_WAYLAND` environment variable is set to 1, and I can verify Firefox is using Wayland in about:support, as `Window Protocol` says `wayland`. This also happens in Thunderbird, so I'm assuming it's a Gecko thing. STEPS TO REPRODUCE 1. Login to a Wayland session 2. Mouse over Firefox OBSERVED RESULT The edges of the cursor are jagged when hovering over Firefox EXPECTED RESULT The edges of the cursor are smooth when hovering over Firefox SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425385] Desktop freezes after taking a screenshot
https://bugs.kde.org/show_bug.cgi?id=425385 --- Comment #51 from Antonio Prcela --- (In reply to Nick Stefanov from comment #50) > I see :) So this line is causing the issue. If you comment it, the desktop doesn't freeze. https://invent.kde.org/graphics/spectacle/-/blob/master/src/ExportManager.cpp#L543 Leaving this here and doing some further analyzing. Tho I doubt that my knowledge of C++ will be enough to fix this :( -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445422] digikam not compliant with pipewire jack library
https://bugs.kde.org/show_bug.cgi?id=445422 --- Comment #10 from caulier.gil...@gmail.com --- To Philippe from comment #7: Look explanations from this page : https://www.digikam.org/contribute/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444646] After an upgrade to 5.23.2, all Window Rules lost their Virtual Desktop property
https://bugs.kde.org/show_bug.cgi?id=444646 Andrei Rybak changed: What|Removed |Added Attachment #143418|redacted kwin |redacted kwinrulesrc description|| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442269] Clicking on a Plasma notification from some app doesn't bring that app forward
https://bugs.kde.org/show_bug.cgi?id=442269 gobo...@gmail.com changed: What|Removed |Added CC||gobo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #25 from Shmerl --- (In reply to Ilia Kats from comment #24) > I'm all for making KDE beginner-friendly, but it shouldn't be at the cost of > advanced users. Perhaps there can be an option, off by default, to show all > the sensors under "Hardware sensors" in addition to the filtered ones in CPU > or something. Yes, good point. I'm using ksysguard because it allows selecting any available sensors exactly this way and you can see the sensor name. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445447] New: Window Placement Centered Appears not to be Working on Wayland
https://bugs.kde.org/show_bug.cgi?id=445447 Bug ID: 445447 Summary: Window Placement Centered Appears not to be Working on Wayland Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com Target Milestone: --- Thought my system settings is set to "centered" for window placement, windows are still appearing in corners of the screen. I am using neon git unstable with updates from today. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444394] Rejected face suggestions reappear for the same person the next time recognition is run
https://bugs.kde.org/show_bug.cgi?id=444394 Frieder Schrempf changed: What|Removed |Added CC||frie...@fris.de -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432643] kdeconnect slowing down system shutdown
https://bugs.kde.org/show_bug.cgi?id=432643 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444280] Opening Sony raw file (arw) in image editor crashes digiKam V7.3.0 (Windows OS)
https://bugs.kde.org/show_bug.cgi?id=444280 --- Comment #18 from fri...@bluemail.ch --- (In reply to R Ramina from comment #14) > Same issue here, using windos 64 bit version of DK 7.3 and Canon R6 and M6 > cameras, CR2 and CR3 files. I also tried open CR2 files from Canon G12 and > it also crashed. Note that previous versions of DK opened the CR2 files OK. Can you try to open the image https://www.imaging-resource.com/PRODS/sony-a7r-iii/Y-35MM-DSC01650.ARW.HTM Just to be sure we talk about the same cause. Thanks FRizzo -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444280] Opening Sony raw file (arw) in image editor crashes digiKam V7.3.0 (Windows OS)
https://bugs.kde.org/show_bug.cgi?id=444280 --- Comment #17 from fri...@bluemail.ch --- I tried digiKam-7.4.0-2023T144931-Win64. Unfortunately it crashes too. I am still using the test image Y-35MM-DSC01650.ARW. The stack trace also looks the same. Running on: Processor Intel(R) Core(TM) i7-6950X CPU @ 3.00GHz 3.00 GHz Installed RAM 32.0 GB System type 64-bit operating system, x64-based processor Pen and touch Pen support Microsoft Windows [Version 10.0.19043.1348] Edition Windows 10 Pro Version 21H1 Installed on27.02.2021 OS build19043.1348 Experience Windows Feature Experience Pack 120.2212.3920.0 Regarding the lack of reproducibility I can't offer any clues. If you tell me what additional HW/SW config items you need to know I will post them. FRizzo -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445446] New: Allow for Custom Bluetooth Device Names
https://bugs.kde.org/show_bug.cgi?id=445446 Bug ID: 445446 Summary: Allow for Custom Bluetooth Device Names Product: systemsettings Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_bluetooth Assignee: now...@gmail.com Reporter: anditosan1...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- I think it would be very useful if users had the ability to rename their connected bluetooth devices. Sometimes bluetooth device names are very unpredictable, they are not indicative of the product you are using and can be hard to recognize in a setup with a lot of them connected. I was thinking the system can store the original name while the user gets a chance to edit the name however they want. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445445] New: Truncated Audio Port list cannot be used to distinguish outputs
https://bugs.kde.org/show_bug.cgi?id=445445 Bug ID: 445445 Summary: Truncated Audio Port list cannot be used to distinguish outputs Product: systemsettings Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: carl.er...@gmail.com Target Milestone: --- Created attachment 143521 --> https://bugs.kde.org/attachment.cgi?id=143521&action=edit screenshot of system settings audio section SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Run an application playing some audio (firefox + youtube for example) 2. Run kde system settings au go to Audio section 3. Select a different audio port for the firefox application OBSERVED RESULT The audio port list shows truncated entries: "Tiger Lake-LP Smart Sound Technology Audio Controller HDMI / Displ..." "Tiger Lake-LP Smart Sound Technology Audio Controller HDMI / Displ..." "Tiger Lake-LP Smart Sound Technology Audio Controller HDMI / Displ..." "Tiger Lake-LP Smart Sound Technology Audio Controller Speaker + H..." EXPECTED RESULT The menu should use all the space available to allow long strings: "Tiger Lake-LP Smart Sound Technology Audio Controller HDMI / DisplayPort 3 Output" "Tiger Lake-LP Smart Sound Technology Audio Controller HDMI / DisplayPort 2 Output" "Tiger Lake-LP Smart Sound Technology Audio Controller HDMI / DisplayPort 1 Output" "Tiger Lake-LP Smart Sound Technology Audio Controller Speaker + Headphones" SOFTWARE/OS VERSIONS Linux: openSUSE Tumbleweed (Release: 2021) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Audio system based on Intel Corporation Tiger Lake-LP Smart Sound Technology Audio -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444516] Crash while painting
https://bugs.kde.org/show_bug.cgi?id=444516
--- Comment #17 from David REVOY ---
I got a crash with a command line only session (no gdb), here is what the full
session prints:
===
~/sources/krita »»» ./krita-5.0.0-beta2-188e619-x86_64.appimage
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
QObject::startTimer: Timers cannot have negative intervals
[RESOURCE] Name: "1. Foreground to Transparent" Version: 0 Filename:
"Foreground to Transparent.svg" MD5: "dd40e1119cf9940cac147d1c07bf69ef" Type:
QPair("gradients","stop_gradients") Valid: true Storage: "memory"
/tmp/.mount_krita-ppP0RH/usr/lib/krita-python-libs/krita added to PYTHONPATH
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
Shortcut for action "isolate_active_layer" "&Isolate Active Layer" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Still unsignalled after processed 17 tiles
increased number of buffers to 32
Still unsignalled after processed 33 tiles
increased number of buffers to 64
Still unsignalled after processed 17 tiles
increased number of buffers to 32
Still unsignalled after processed 33 tiles
increased number of buffers to 64
Still unsignalled after processed 65 tiles
increased number of buffers to 128
Still unsignalled after processed 129 tiles
increased number of buffers to 256
Still unsignalled after processed 17 tiles
increased number of buffers to 32
Still unsignalled after processed 33 tiles
increased number of buffers to 64
Still unsignalled after processed 65 tiles
increased number of buffers to 128
Still unsignalled after processed 129 tiles
increased number of buffers to 256
[gmic_krita-plugin_qt]./error/ ~GmicProcessor(): There are 1 unfinished filter
threads.
Still unsignalled after processed 17 tiles
increased number of buffers to 32
Still unsignalled after processed 33 tiles
increased number of buffers to 64
Still unsignalled after processed 65 tiles
increased number of buffers to 128
Still unsignalled after processed 129 tiles
increased number of buffers to 256
Still unsignalled after processed 17 tiles
increased number of buffers to 32
Still unsignalled after processed 33 tiles
increased number of buffers to 64
Still unsignalled after processed 65 tiles
increased number of buffers to 128
Still unsignalled after processed 129 tiles
increased number of buffers to 256
Still unsignalled after processed 17 tiles
increased number of buffers to 32
Still unsignalled after processed 33 tiles
increased number of buffers to 64
Still unsignalled after processed 65 tiles
increased number of buffers to 128
Still unsignalled after processed 129 tiles
increased number of buffers to 256
Still unsignalled after processed 17 tiles
increased number of buffers to 32
Still unsignalled after processed 33 tiles
increased number of buffers to 64
Still unsignalled after processed 65 tiles
increased number of buffers to 128
Still unsignalled after processed 129 tiles
increased number of buffers to 256
[gmic_krita-plugin_qt]./error/ ~GmicProcessor(): There are 1 unfinished filter
threads.
Still unsignalled after processed 17 tiles
increased number of buffers to 32
Still unsignalled after processed 33 tiles
increased number of buffers to 64
Still unsignalled after processed 65 tiles
increased number of buffers to 128
Still unsignalled after processed 129 tiles
increased number of buffers to 256
Still unsignalled after processed 17 tiles
increased number of buffers to 32
Still unsignalled after processed 33 tiles
increased number of buffers to 64
Still unsignalled after processed 65 tiles
increased number of buffers to 128
Still unsignalled after proce
[kwin] [Bug 445444] New: wrong window size for alacritty terminal emulator
https://bugs.kde.org/show_bug.cgi?id=445444 Bug ID: 445444 Summary: wrong window size for alacritty terminal emulator Product: kwin Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: co...@matthewbriancohen.com Target Milestone: --- SUMMARY A recent Plasma upgrade made it so terminal emulator alacritty gets incorrectly resized to a 2x1 window when opened. I opened a bug report with alacritty and they said this is a KDE issue, so I'm reporting it here. I have not seen this resize bug effect other programs outside of alacritty. Github issue - https://github.com/alacritty/alacritty/issues/5603 STEPS TO REPRODUCE 1. open alacritty OBSERVED RESULT alacritty window is tiny (2x1) EXPECTED RESULT alacritty window is size specified in config file (behavior even occurs if config file is deleted and default setting is used) SOFTWARE/OS VERSIONS Linux/KDE Plasma KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445443] New: Wayland: Issues with the display switcher widget or popup (Meta+P) - I dare you to play with it until it breaks
https://bugs.kde.org/show_bug.cgi?id=445443 Bug ID: 445443 Summary: Wayland: Issues with the display switcher widget or popup (Meta+P) - I dare you to play with it until it breaks Product: KScreen Version: git Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasma Applet Assignee: kscreen-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY On Wayland I'm experiencing issues with the quick display switcher thingy that pops up with Meta+P, as well as its system tray applet counterpart. If you have a laptop and an external display I encourage you to try switching between all the options for a minute (on Wayland), you are guaranteed to run into various bugs. Among the issues I personally found are: - If you first set only the internal display to be active and then switch to only the external display or vice versa, nothing happens. You have to choose "extend to the left/right" first and then choose to switch to the external (/internal) display only in order for it to work - Sometimes when switching to the internal display, the wallpaper is cut off (likely because the external screen has a different aspect ratio) - Sometimes when switching around, one of the monitors will have a black background (no wallpaper) - When choosing any option at all from the quick display switcher, there seems to be a ~25% chance that it will freeze the session completely except for the mouse cursor, and you can't do anything but restart the PC or switch to a TTY SOFTWARE/OS VERSIONS Operating System: KDE Neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445422] digikam not compliant with pipewire jack library
https://bugs.kde.org/show_bug.cgi?id=445422 --- Comment #9 from Maik Qualmann --- https://www.digikam.org/contribute/ Debug log in terminal: export QT_LOGGING_RULES="digikam*=true" digikam Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445422] digikam not compliant with pipewire jack library
https://bugs.kde.org/show_bug.cgi?id=445422 --- Comment #8 from Maik Qualmann --- Git commit d8213d853db4c3664a6ca549ebc6e4dcd4d77d33 by Maik Qualmann. Committed on 13/11/2021 at 21:04. Pushed by mqualmann into branch 'master'. try to force platform dependent audio output plugin Related: bug 382582 M +21 -1core/libs/video/player/mediaplayerview.cpp https://invent.kde.org/graphics/digikam/commit/d8213d853db4c3664a6ca549ebc6e4dcd4d77d33 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382582] Video stutters when played with MP3 audio track
https://bugs.kde.org/show_bug.cgi?id=382582 --- Comment #42 from Maik Qualmann --- Git commit d8213d853db4c3664a6ca549ebc6e4dcd4d77d33 by Maik Qualmann. Committed on 13/11/2021 at 21:04. Pushed by mqualmann into branch 'master'. try to force platform dependent audio output plugin Related: bug 445422 M +21 -1core/libs/video/player/mediaplayerview.cpp https://invent.kde.org/graphics/digikam/commit/d8213d853db4c3664a6ca549ebc6e4dcd4d77d33 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445422] digikam not compliant with pipewire jack library
https://bugs.kde.org/show_bug.cgi?id=445422 --- Comment #7 from Philippe ROUBACH --- >> Please post a log from the terminal with an active debug environment >> variable from the start >> of digiKam How ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445422] digikam not compliant with pipewire jack library
https://bugs.kde.org/show_bug.cgi?id=445422 --- Comment #6 from Maik Qualmann --- A test here with the Pulse Audio backend from QtAV cannot be used here under openSUSE Tumbleweed, a video only plays a few frames per second. Please post a log from the terminal with an active debug environment variable from the start of digiKam. I want to see which audio backends are available under openSUSE Leap in QtAV. I no longer see messages under openSUSE Tumbleweed that QtAV is looking for a Jack Audio Server, possibly this has already been deactivated under Tumbleweed in the QtAV package. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444569] Keyboard layout shortcuts activate wrong language [regression]
https://bugs.kde.org/show_bug.cgi?id=444569 --- Comment #6 from Roman Odaisky --- (In reply to Andrey from comment #5) > I can guess what's happening - if we use spare layout first time, we change > theirs order. > But the shortcuts do know nothing about it, and continue behave as if the > order was the same. > Here you got the swapping. > Does it look possible? Well spotted. If I have English, Russian, Ukrainian, in that order, then activating Ukrainian switches the order to EN—UK—RU and, if the shortcuts are tied to the position of the layout on the list instead of the layout itself, that would cause the problem. What changed since 5.21.4, where things worked well? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444280] Opening Sony raw file (arw) in image editor crashes digiKam V7.3.0 (Windows OS)
https://bugs.kde.org/show_bug.cgi?id=444280 --- Comment #16 from Maik Qualmann --- The last digiKam function in the trace is from LibRaw::convert_to_rgb(). Just why can't I reproduce it? Processor dependent? If you make a backup of your database, you are welcome to test the pre-release of digiKam-7.4.0, whether the problem is reproducible. https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445440] Add Dimensions information to mwg-rs
https://bugs.kde.org/show_bug.cgi?id=445440 --- Comment #2 from Maik Qualmann --- I cannot imagine that the mwg-rs:AppliedToDimensions tag is the reason why no name is recognized. It would actually be a Lightroom bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429219] MWG "Applied To" state (mwg-rs:AppliedToDimensions XMP tag) is not included when writing Face metadata to file - Use ExifTool
https://bugs.kde.org/show_bug.cgi?id=429219 Maik Qualmann changed: What|Removed |Added CC||ertym...@gmail.com --- Comment #8 from Maik Qualmann --- *** Bug 445440 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445440] Add Dimensions information to mwg-rs
https://bugs.kde.org/show_bug.cgi?id=445440 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 429219 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440983] crash after ejecting storage device
https://bugs.kde.org/show_bug.cgi?id=440983 k...@trummer.xyz changed: What|Removed |Added Resolution|WORKSFORME |WAITINGFORINFO --- Comment #5 from k...@trummer.xyz --- It happened again today, but DrKonqi was killed before the backtrace had finished. coredumpctl also has nothing, probably because plasmashell was sigkilled. Operating System: openSUSE Tumbleweed 20211107 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440983] crash after ejecting storage device
https://bugs.kde.org/show_bug.cgi?id=440983 --- Comment #4 from k...@trummer.xyz --- Created attachment 143520 --> https://bugs.kde.org/attachment.cgi?id=143520&action=edit "journalctl --user" output -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445442] New: Holding F2 while creating a selection freezes the rubber band
https://bugs.kde.org/show_bug.cgi?id=445442 Bug ID: 445442 Summary: Holding F2 while creating a selection freezes the rubber band Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: christ.de...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 143519 --> https://bugs.kde.org/attachment.cgi?id=143519&action=edit Video of the issue SUMMARY Holding F2 while creating a selection freezes the rubber band. Please see my attached video. STEPS TO REPRODUCE 1. Hold F2 2. Make a selection with the mouse 3. The rubber band will freeze in place Operating System: openSUSE Tumbleweed 2020 KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443735] Thumbnails for .cbz files does not support .webp, .avif etc
https://bugs.kde.org/show_bug.cgi?id=443735 Magnus Boman changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Magnus Boman --- Fixed with KDE Frameworks 5.88.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 391661] KDialog's Open File dialog hangs if an automount NFS share is unavailable
https://bugs.kde.org/show_bug.cgi?id=391661 --- Comment #5 from Lars Bischoff --- meanwhile I found that my issue was addressed here: https://bugs.kde.org/show_bug.cgi?id=442106 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 361036] No support for 30bpp X11 display
https://bugs.kde.org/show_bug.cgi?id=361036 Mia Herkt changed: What|Removed |Added Resolution|FIXED |--- CC||mia+...@0x0.st Status|RESOLVED|REOPENED --- Comment #10 from Mia Herkt --- Looks like it’s regressed as of Spectacle 21.08.3. More precisely it looks like the color channels are swapped. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 442106] "UUID" or "LABEL" fstab entries cause file browsing slowdown (kio commit 7de9c2e3)
https://bugs.kde.org/show_bug.cgi?id=442106 Lars Bischoff changed: What|Removed |Added CC||lbisch...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425368] widgets change size slightly after reboot
https://bugs.kde.org/show_bug.cgi?id=425368 Drew changed: What|Removed |Added CC||dreame...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445441] New: Dropping multiple files on the desktop only positions one file at the mouse position
https://bugs.kde.org/show_bug.cgi?id=445441 Bug ID: 445441 Summary: Dropping multiple files on the desktop only positions one file at the mouse position Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: christ.de...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When dropping multiple files onto the desktop, only one will be actually dropped at the mouse position. The other items will just fill up at the top left corner. STEPS TO REPRODUCE 1. Drag multiple files from Dolphin onto the desktop 2. See that only one item will be at the mouse position EXPECTED RESULT All files dropped at mouse position. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 2020 KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445440] New: Add Dimensions information to mwg-rs
https://bugs.kde.org/show_bug.cgi?id=445440 Bug ID: 445440 Summary: Add Dimensions information to mwg-rs Product: digikam Version: 7.3.0 Platform: unspecified OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Engine Assignee: digikam-bugs-n...@kde.org Reporter: ertym...@gmail.com Target Milestone: --- SUMMARY digiKam does not store Dimensions information when saving Face Tags in xmp:mwg-rs. Why is this important? Because Lightroom can't import the digiKam photo collection properly. It does not recognize all Face Tags and treats them as "Unnamed people". This may prevent many people from using digiKam, fearing that they will lose the entire collection of Faces tags if they switch to Lightroom in the future. STEPS TO REPRODUCE 1. Recognize any person in the photo 2. Import this photo into Lightroom 3. Try to see named Face Tag of this person in the imported photo OBSERVED RESULT You can see only "Unnamed people" EXPECTED RESULT All people recognized properly as "Person's name" ADDITIONAL INFORMATION I compared the xmp tags between the photos that were imported correctly and the digiKam photos and found only one important difference, it is Dimensions block inside of mwg-rs section. It contained height and width size of the picture and format (pixel), that's all. If you export xmp tags with "exiftool -tagsfromfile SRC.EXT -xmp:all DST.xmp" That block looks like this: 1920 pixel 2560 ... digiKam never write this block and that is the only reason that prevents the correct import Face tagged photos into Lightroom. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 445439] New: In the latest level of the activity to learn to pay, there may not be enough money to do so, as in the attached screenshot.
https://bugs.kde.org/show_bug.cgi?id=445439 Bug ID: 445439 Summary: In the latest level of the activity to learn to pay, there may not be enough money to do so, as in the attached screenshot. Product: gcompris Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: lc...@april.org Target Milestone: --- Created attachment 143518 --> https://bugs.kde.org/attachment.cgi?id=143518&action=edit Unpayable total price (screenshot) STEPS TO REPRODUCE 1. Launch the activity to learn to pay. 2. Go to the last level, for instance using the left arrow. OBSERVED RESULT The total price of the items exceeds the sum of the values of all coins and notes. EXPECTED RESULT The total price should always be payable with the provided coins and notes. SOFTWARE/OS VERSIONS GCompris 1.1 downloaded from https://gcompris.net/download/qt/linux/gcompris-qt-1.1-Linux64.sh and running on Trisquel 9 (based on Ubuntu 18.04). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445438] New: If plasmashell has been restarted in a session, the widget explorer does not open at all
https://bugs.kde.org/show_bug.cgi?id=445438 Bug ID: 445438 Summary: If plasmashell has been restarted in a session, the widget explorer does not open at all Product: plasmashell Version: 5.23.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: 1.0 SUMMARY The widget explorer sidebar simply will not open if you have restarted plasmashell with plasmashell --replace. Clicking "Add widgets" in a panel's or desktop's right click menu or using the keyboard shortcut does nothing at all in that case. You have to log out and log back in again to be able to open it again. STEPS TO REPRODUCE 1. In a fresh Plasma session, open the widget explorer sidebar: It works as expected 2. Now run "plasmashell --replace" in KRunner or the terminal 3. Try to open the widget explorer again OBSERVED RESULT The widget explorer won't open after restarting plasmashell until you log out and log back in again or reboot EXPECTED RESULT The widget explorer should open normally even after plasmashell has been restarted SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-zen1-1-zen (64-bit) Graphics Platform: Both X11 and Wayland -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445408] Krita 4 resources bundle is broken and causes conflict with Quiralta's brushes set
https://bugs.kde.org/show_bug.cgi?id=445408 --- Comment #5 from Tiar --- I, uhh, respectfully disagree with the notion that it's a "workaround" because it is a fix for a real issue. Here we have two issues: 1) deactivating all resources when you have duplicates (probably caused by the fact that the first one is disabled because it comes from a disabled bundle, then the next one is disabled because it's a second one... etc.) 2) not finding the appropriate resource in the model just because it's disabled or comes from a disabled model. Note that or this to happen you don't need issue (1); it's enough if you make a preset with some brush tip and then deactivate that brush tip (note that right now, all presets embed their dependant resources so you might need to create a preset in earlier versions of Krita for it, though I think the bundle still puts them alongside presets anyway...). Hence, issue (2) is a separate issue from issue (1), and a fix that fixes (2) is still a fix, and not a "workaround for issue (1)". Btw. regarding issue (1), yeah, but see bug 439703. I noted the same issue (1) but Halla closed it. There is a general idea that newly coming resources with the same md5 should be disabled by default, and I guess maybe Halla focused on that part when closing that bug report. I think the fact that this automatic system makes *all* of the resources disabled, if the first one come from a disabled bundle, might not exactly be expected or at least, I wouldn't expect it as a user. But in any case, for that you'd need to talk with her. -- Also about issue 2), you might need to also use: resModel.setStorageFilter(KisResourceModel::ShowAllStorages) to be sure to find the resource that comes from the disabled bundle as well. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 433597] Closing Kdenlive leaves orphaned "dbus-daemon.exe"
https://bugs.kde.org/show_bug.cgi?id=433597 Julius Künzel changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #3 from Julius Künzel --- This is should be fixed with newer versions of Kdenlive (if I remember right since 21.08.0?) since we don't use DBus on Windows anymore -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426861] Indicate if a clip is used in Timeline or not
https://bugs.kde.org/show_bug.cgi?id=426861 Julius Künzel changed: What|Removed |Added Version Fixed In||21.12 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Julius Künzel --- With version 21.12 (release in December) there are now blue audio/video icons to highlight better whether the clip is used in the timeline or not. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 445437] New: QML errors and crashing when removing processes with search open in tree view
https://bugs.kde.org/show_bug.cgi?id=445437
Bug ID: 445437
Summary: QML errors and crashing when removing processes with
search open in tree view
Product: plasma-systemmonitor
Version: 5.23.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ksysguard-b...@kde.org
Reporter: nyanpas...@tuta.io
CC: ahiems...@heimr.nl, plasma-b...@kde.org
Target Milestone: ---
Created attachment 143517
--> https://bugs.kde.org/attachment.cgi?id=143517&action=edit
Backtrace of this crash, missing many symbols.
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
When I run System Monitor, type a process name filter, and close a large number
of processes matching the filter, switching to tree view produces QML errors
and sometimes segfaults.
STEPS TO REPRODUCE
1. Open plasma-systemmonitor to the Processes tab.
2. Optionally switch to tree view.
3. Type bash into the search bar.
4. Open a Konsole tab, open Bash if you're using a different shell, and run
`for i in {1..200}; do bash & done`.
5. Once the 200 bash processes show up in plasma-systemmonitor, close the
Konsole tab, and wait for the processes to disappear.
6. Switch to tree view if you're not already in it. Warnings will not appear
unless/until you're in tree view.
Without a search query open, I don't get instability (fixed in Bug 437862).
If you run a different child process (like perl), you can encounter this bug by
searching for perl instead of bash. And if you start out in list view and later
switch to tree view, you can *only* reproduce the bug by searching for perl
(not the parent process bash).
OBSERVED RESULT
```
TableView::forceLayout(): Cannot do an immediate re-layout during an ongoing
layout!
Model size of -1 is less than 0
Model size of -1 is less than 0
Model size of -1 is less than 0
...
file:///usr/lib/qt/qml/org/kde/ksysguard/table/TreeDecoration.qml:49:
TypeError: Value is undefined and could not be converted to an object
file:///usr/lib/qt/qml/org/kde/ksysguard/table/FirstCellDelegate.qml:57:42:
Unable to assign [undefined] to bool
file:///usr/lib/qt/qml/org/kde/ksysguard/table/FirstCellDelegate.qml:56:44:
Unable to assign [undefined] to bool
file:///usr/lib/qt/qml/org/kde/ksysguard/table/FirstCellDelegate.qml:55:39:
Unable to assign [undefined] to int
file:///usr/lib/qt/qml/org/kde/ksysguard/table/TreeDecoration.qml:49:
TypeError: Value is undefined and could not be converted to an object
file:///usr/lib/qt/qml/org/kde/ksysguard/table/FirstCellDelegate.qml:57:42:
Unable to assign [undefined] to bool
file:///usr/lib/qt/qml/org/kde/ksysguard/table/FirstCellDelegate.qml:56:44:
Unable to assign [undefined] to bool
file:///usr/lib/qt/qml/org/kde/ksysguard/table/FirstCellDelegate.qml:55:39:
Unable to assign [undefined] to int
,,,
```
In some rare cases I get a crash as well. For example, when filtering in
plasma-systemmonitor, I got a crash "in the wild" a few days ago with a
non-symboled backtrace (attached), but it's missing the actual coredump. Since
then, I've only been able to replicate this crash in synthetic conditions using
non-symboled Arch Linux plasma-systemmonitor in painfully-slow Valgrind (my
(!strip debug) builds don't crash).
EXPECTED RESULT
plasma-systemmonitor doesn't crash and doesn't use invalid object indexes.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.16-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 730/PCIe/SSE2
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 445436] New: [Wayland] On multi screen setups, moving a window to a different workspace makes it flicker and also stay visible on the current workspace
https://bugs.kde.org/show_bug.cgi?id=445436 Bug ID: 445436 Summary: [Wayland] On multi screen setups, moving a window to a different workspace makes it flicker and also stay visible on the current workspace Product: kwin Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY On Wayland, when I use a keyboard shortcut to move a window to a different workspace / virtual desktop on a system with two monitors, the window flickers a lot, but stays visible on the current workspace. Clicking it makes it disappear, though while it is still visible you can use a keyboard shortcut again to move it to yet another workspace (or back to the current one). This issue does NOT occur with just one monitor (but I think it used to). It also does NOT occur if instead of a keyboard shortcut, the Alt+F3 menu is used to move the window to a different workspace STEPS TO REPRODUCE 1. Be on Wayland and have more than one monitor 2. Have >1 workspace and set KWin keyboard shortcuts for moving a window to a specific workspace 3. Use the shortcut to move a window to a different workspace OBSERVED RESULT The window flickers and stays visible on the current workspace even though it was moved to a different one EXPECTED RESULT The window should simply disappear since it is no longer supposed to be on that workspace. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-zen1-1-zen (64-bit) Graphics Platform: Wayland ... and also on KDE Neon unstable -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 445425] Battery and screen brightness applet should be a bit brighter itself
https://bugs.kde.org/show_bug.cgi?id=445425 Paul Worrall changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 445435] New: kdesrc-build doesn't respect HTTPS_PROXY
https://bugs.kde.org/show_bug.cgi?id=445435 Bug ID: 445435 Summary: kdesrc-build doesn't respect HTTPS_PROXY Product: kdesrc-build Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: hanyo...@protonmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. export HTTPS_PROXY=https:// 2. kdesrc-build ktexteditor 3. waiting OBSERVED RESULT extremely slow on Third World country's internet EXPECTED RESULT Use the HTTPS_PROXY to git clone the source, it's much faster SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 445434] New: Gwenview crash when clicking "crop" button
https://bugs.kde.org/show_bug.cgi?id=445434
Bug ID: 445434
Summary: Gwenview crash when clicking "crop" button
Product: gwenview
Version: 21.08.3
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: gwenview-bugs-n...@kde.org
Reporter: philipp.reichm...@gmail.com
Target Milestone: ---
Application: gwenview (21.08.3)
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.14-2-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.2 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Opened an image, selected the Crop tool from the toolbar on the left.
Gwenview reproducibly crashes for me when cropping any image.
The crash can be reproduced every time.
-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6 QScreen::geometry (this=0x0) at kernel/qscreen.cpp:413
#7 0x7f0f0f3319b5 in Gwenview::CropWidgetPrivate::initRatioComboBox
(this=0x56366c4e9eb0) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/lib/crop/cropwidget.cpp:203
#8 Gwenview::CropWidget::CropWidget (this=, parent=, imageView=, cropTool=, this=, parent=, imageView=, cropTool=) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/lib/crop/cropwidget.cpp:396
#9 0x7f0f0f332f70 in Gwenview::CropToolPrivate::setupWidget
(this=0x56366c4ff7d0) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/lib/crop/croptool.cpp:203
#10 Gwenview::CropTool::CropTool (this=, view=,
this=, view=) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/lib/crop/croptool.cpp:234
#11 0x56366aab02cc in Gwenview::ImageOpsContextManagerItem::crop
(this=0x56366c28b670) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/app/imageopscontextmanageritem.cpp:264
#12 Gwenview::ImageOpsContextManagerItem::qt_static_metacall
(_o=0x56366c28b670, _id=, _a=, _c=) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/build/app/gwenview_autogen/EWIEGA46WW/moc_imageopscontextmanageritem.cpp:115
#13 0x7f0f0d713078 in doActivate (sender=0x56366c19ddc0,
signal_index=4, argv=0x7fff03a218d0) at kernel/qobject.cpp:3898
#14 0x7f0f0d70c50f in QMetaObject::activate
(sender=sender@entry=0x56366c19ddc0, m=m@entry=0x7f0f0ea0c0a0,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff03a218d0)
at kernel/qobject.cpp:3946
#15 0x7f0f0e4ed182 in QAction::triggered (this=this@entry=0x56366c19ddc0,
_t1=) at .moc/moc_qaction.cpp:376
#16 0x7f0f0e4efdb4 in QAction::activate (this=0x56366c19ddc0,
event=) at kernel/qaction.cpp:1161
#17 0x7f0f0e5e8a0a in QAbstractButtonPrivate::click (this=0x563672befd90)
at widgets/qabstractbutton.cpp:398
#18 0x7f0f0e5e8b63 in QAbstractButton::mouseReleaseEvent
(this=0x563672bee010, e=0x7fff03a21e70) at widgets/qabstractbutton.cpp:1044
#19 0x7f0f0e6e139a in QToolButton::mouseReleaseEvent (this=,
e=) at widgets/qtoolbutton.cpp:622
#20 0x7f0f0e53576e in QWidget::event (this=0x563672bee010,
event=0x7fff03a21e70) at kernel/qwidget.cpp:9020
#21 0x7f0f0e4f3a7f in QApplicationPrivate::notify_helper
(this=this@entry=0x56366bccdb30, receiver=receiver@entry=0x563672bee010,
e=e@entry=0x7fff03a21e70) at kernel/qapplication.cpp:3632
#22 0x7f0f0e4fb584 in QApplication::notify (this=0x7fff03a21b90,
receiver=0x563672bee010, e=0x7fff03a21e70) at kernel/qapplication.cpp:3076
#23 0x7f0f0d6dc9fa in QCoreApplication::notifyInternal2
(receiver=0x563672bee010, event=0x7fff03a21e70) at
kernel/qcoreapplication.cpp:1064
#24 0x7f0f0e4fa093 in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x563672bee010, event=event@entry=0x7fff03a21e70,
alienWidget=alienWidget@entry=0x563672bee010, nativeWidget=0x56366bd33120,
buttonDown=, lastMouseReceiver=..., spontaneous=true,
onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614
#25 0x7f0f0e54e83c in QWidgetWindow::handleMouseEvent (this=0x56366c2d6e40,
event=0x7fff03a22140) at kernel/qwidgetwindow.cpp:683
#26 0x7f0f0e551c55 in QWidgetWindow::event (this=0x56366c2d6e40,
event=0x7fff03a22140) at kernel/qwidgetwindow.cpp:300
#27 0x7f0f0e4f3a7f in QApplicationPrivate::notify_helper (this=, receiver=0x56366c2d6e40, e=0x7fff03a22140) at
kernel/qapplication.cpp:3632
#28 0x7f0f0d6dc9fa in QCoreApplication::notifyInternal2
(receiver=0x56366c2d6e40, event=0x7fff03a22140) at
kernel/qcoreapplication.cpp:1064
#29 0x7f0f0dda15c7 in QGuiApplicationPrivate::processMouseEvent
(e=0x56366c50b3c0) at kernel/qguiapplication.cpp:2282
#30 0x7f0f0dd7778c in QWindowSystemInterface::sendWindowSystemEvents
(flags=...) at kernel/qwindowsysteminterface.cpp:1169
#31 0x7f0f0b906a80 in userEventSourceDispatch
(source=source@entry=0x56366bd07fe0) at qeventdispatcher_glib.cpp:74
#32 0x
[plasma-nm] [Bug 445433] New: QR code for network partially obstructed by applet (wayland)
https://bugs.kde.org/show_bug.cgi?id=445433 Bug ID: 445433 Summary: QR code for network partially obstructed by applet (wayland) Product: plasma-nm Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: 31...@tuta.io Target Milestone: --- SUMMARY When trying to share my wifi password to other devices via QR code, the QR code I can display by opening the applet, right clicking the network and clicking "Show network's QR code", is partially obstructed by the applet and cannot be scanned. This only happens on wayland. STEPS TO REPRODUCE 1. Open network applet 2. Right click network 3. Show newtork's QR code OBSERVED RESULT QR code is obstructed by applet EXPECTED RESULT QR code is not obstructed by applet SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 35 (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87 Qt Version: 5.15.2 ADDITIONAL INFORMATION Aspect ratio 16:10 Screen resolution 1280x800 Scale 100% -- You are receiving this mail because: You are watching all bug changes.
