[xdg-desktop-portal-kde] [Bug 490715] New: Feature request: Permissions management for xdg-desktop-portal
https://bugs.kde.org/show_bug.cgi?id=490715 Bug ID: 490715 Summary: Feature request: Permissions management for xdg-desktop-portal Classification: Plasma Product: xdg-desktop-portal-kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: the.real.samuel.jime...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- The user is shown a dialog requesting permissions (e.g. Input Capture) for certain applications. Currently there is no centralized location to view or revoke permissions granted. To improve usability, could an entry for xdg-desktop-portal be added to the Application Permissions menu to display and manage permissions by application? -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 490509] Annoying popup appearing every time that i connect a bluetooth controller
https://bugs.kde.org/show_bug.cgi?id=490509 Samuel Jimenez changed: What|Removed |Added CC||the.real.samuel.jimenez@gma ||il.com -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480235] Persistence in the remote desktop portal does not work across reboots
https://bugs.kde.org/show_bug.cgi?id=480235 --- Comment #20 from Samuel Jimenez --- (In reply to orangestar from comment #19) > > Deleting those files did the trick! Thank you! Hopefully that wont happen > too often. > Did this resolve your problem with Steam as well? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488225] After waking from a sleep of a few hours, the desktop session shows a black screen with a cursor
https://bugs.kde.org/show_bug.cgi?id=488225 Samuel Meenzen changed: What|Removed |Added CC||sam...@meenzen.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484999] [Overview] MMB-clicking on added Virtual Desktop should not remove it
https://bugs.kde.org/show_bug.cgi?id=484999 --- Comment #5 from Samuel M. --- > By deleting them that easily with MMB, "Window Rules" set for them are being > destroyed as well, which are a pain to set up again. Did not read properly. Yeah, thats destructive. Still, for my workflow removing this is a considerable regression. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484999] [Overview] MMB-clicking on added Virtual Desktop should not remove it
https://bugs.kde.org/show_bug.cgi?id=484999 --- Comment #4 from Samuel M. --- Sorry to come in at a late hour like this. I just learned of this yesterday from Brodies video. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484999] [Overview] MMB-clicking on added Virtual Desktop should not remove it
https://bugs.kde.org/show_bug.cgi?id=484999 Samuel M. changed: What|Removed |Added Status|RESOLVED|REOPENED CC||samuel.maier2+bugs.kde.org@ ||hotmail.de Resolution|FIXED |--- --- Comment #3 from Samuel M. --- I guess I'm the famous spacebar-heater guy... but I extensively use this behavior. Before plasma 6 I had an array of first 4, then 6 desktops in a grid, these were fixed. When plasma 6 came out I wondered why my overview did not look like the clips I had seen, and eventually I figured out it was the grid layout, which seems incompatible. So I had to rethink my virtual desktop handling. Before that I had already had the situation that I ran out of virtual desktops in specific tasks, while most of the time most desktops were empty anyways and just taking up space. When I saw that you got a remove icon in the overview, and then tried the MMB to remove a desktop - which also works for most other things tabs in broswers or dolphin, windows in the overview, ... - I thought this was intended and adjusted my virtual desktop management to regularely add and remove desktop in a linear layout. So honestly removing this for me feature is not amazing. Closing desktops with the close button is much more effort than roughly aiming at the desktop and clicking the MMB - which shares muscle memory with closing windows and by now has trained specific muscle memory too - and opening new desktops is appropriately easy, just drag a window to the plus desktop button. And removing desktops is IMO not really destructive at all, unless you had a BUNCH of windows on that desktop. All Apps that were opened just go to another desktop, keeping their shape and their monitor assignment. So if you made a mistake just drag the few windows back over to a new desktop. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 487094] Nextcloud Sync Client (Flatpak) asks for credentials every relaunch when KDE wallet subsystem disabled
https://bugs.kde.org/show_bug.cgi?id=487094 --- Comment #7 from Samuel Sanchez --- Just to clarify, my issue and the issues reported at https://invent.kde.org/frameworks/kwallet/-/merge_requests/67#note_944107 are all with KWallet enabled. I'll split these issues to a new bug report if necessary. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 487094] Nextcloud Sync Client (Flatpak) asks for credentials every relaunch when KDE wallet subsystem disabled
https://bugs.kde.org/show_bug.cgi?id=487094 --- Comment #5 from Samuel Sanchez --- (In reply to Daniel Rusek from comment #4) > Did you try reinstalling the Flatpak and removing its existing config files > and other data? Yes, I have tried that for both the Bitwarden and the Standard Notes flatpaks, but this did not resolve the issue. Successful workarounds for the issue include switching to the Bitwarden and Standard Notes AppImages, or switching the desktop environment to GNOME Shell 46.1, or rolling back KDE Frameworks to version 6.1.0. It is the combination of KDE Wallet 6.2.0 and the Bitwarden and Standard Notes flatpaks that cause the issue on my end. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336990] Chromium and Firefox does not remember their virtual desktops on session restore
https://bugs.kde.org/show_bug.cgi?id=336990 Samuel Jimenez changed: What|Removed |Added CC||the.real.samuel.jimenez@gma ||il.com -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480235] Persistence in the remote desktop portal does not work across reboots
https://bugs.kde.org/show_bug.cgi?id=480235 Samuel Jimenez changed: What|Removed |Added CC||the.real.samuel.jimenez@gma ||il.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 445598] Dynamic word wrapping in Kile stopped working in Ubuntu 21.10
https://bugs.kde.org/show_bug.cgi?id=445598 Samuel Jimenez changed: What|Removed |Added Product|kile|frameworks-ktexteditor Component|editor |general Assignee|michel.lud...@gmail.com |kwrite-bugs-n...@kde.org Version|2.9.93 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 445598] Dynamic word wrapping in Kile stopped working in Ubuntu 21.10
https://bugs.kde.org/show_bug.cgi?id=445598 --- Comment #7 from Samuel Jimenez --- (In reply to Kishore Gopalakrishnan from comment #6) > (In reply to Samuel Jimenez from comment #5) > > (In reply to Kishore Gopalakrishnan from comment #4) > > > (In reply to Samuel Jimenez from comment #3) > > > > This happens sporadically on 2.9.95 > > > > Operating System: Arch Linux > > > > KDE Plasma Version: 6.0.4 > > > > KDE Frameworks Version: 6.1.0 > > > > Qt Version: 6.7.0 > > > > > > > > If an entry for the file is created in kilerc, it remains persistent. > > > > (This > > > > corresponds to View >Word Wrap > Dynamic Word Wrap) > > > > [View-Settings,View=0,URL=file://:@/path/to/file.tex] > > > > Dynamic Word Wrap=true > > > > > > > > However, until this is saved per-file, the setting inherited from > > > > KTextEditor is not consistently respected. > > > > (Settings > Configure > Kile > Editor > Appearance > Dynamic Word Wrap) > > > > [KTextEditor View] > > > > Dynamic Word Wrap=true > > > > > > Are you sure this is not a ktexteditor bug? I seem to be seeing similar > > > behaviour in Kate too. > > > > In which version of Kate do you see this? > > I cannot reproduce in Kate version 24.02.2. > > > > While I don't claim to be sure, I see it around 50% in Kile. > > I also have kate 24.02.2, and dynamic word wrapping occasionally gets > disabled in some new windows (the same happens for me in Kile). If you are seeing it in kate, that would indicate it is in ktexteditor or some other unit of katepart shared between the two. Has an upstream bug been opened for this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432291] Hide mouse cursor after some timout on the lock and login screens
https://bugs.kde.org/show_bug.cgi?id=432291 --- Comment #6 from Samuel Gilbert --- It looks like it's fixed in kscreenlocker 6.0.4 (I'm testing with Arch Linux with Wayland). -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 484452] Documentation is unavailable
https://bugs.kde.org/show_bug.cgi?id=484452 Samuel Jimenez changed: What|Removed |Added CC||the.real.samuel.jimenez@gma ||il.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 445598] Dynamic word wrapping in Kile stopped working in Ubuntu 21.10
https://bugs.kde.org/show_bug.cgi?id=445598 --- Comment #5 from Samuel Jimenez --- (In reply to Kishore Gopalakrishnan from comment #4) > (In reply to Samuel Jimenez from comment #3) > > This happens sporadically on 2.9.95 > > Operating System: Arch Linux > > KDE Plasma Version: 6.0.4 > > KDE Frameworks Version: 6.1.0 > > Qt Version: 6.7.0 > > > > If an entry for the file is created in kilerc, it remains persistent. (This > > corresponds to View >Word Wrap > Dynamic Word Wrap) > > [View-Settings,View=0,URL=file://:@/path/to/file.tex] > > Dynamic Word Wrap=true > > > > However, until this is saved per-file, the setting inherited from > > KTextEditor is not consistently respected. > > (Settings > Configure > Kile > Editor > Appearance > Dynamic Word Wrap) > > [KTextEditor View] > > Dynamic Word Wrap=true > > Are you sure this is not a ktexteditor bug? I seem to be seeing similar > behaviour in Kate too. In which version of Kate do you see this? I cannot reproduce in Kate version 24.02.2. While I don't claim to be sure, I see it around 50% in Kile. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482811] On X11 with NVIDIA GPU panel always moves moved from one screen to another one after screen unlock
https://bugs.kde.org/show_bug.cgi?id=482811 --- Comment #15 from Samuel --- (In reply to Nate Graham from comment #12) > Ok great. One final question: > > Do you see the issue when: > - You manually lock the screen with Meta+L and then unlock? > - When you disable the lock screen and let the monitor go into power save > mode automatically? > - Only when the monitor goes into power save while the screen is locked? Sorry for the delay, and the answer is yes to all, it happens when I lock screen via META + L, I disabled the screen lock in all the accounts and, when the monitor goes power save, it happens again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482811] On X11, After upgrading from Plasma 5, panel always moves moved from one screen to another one after screen unlock
https://bugs.kde.org/show_bug.cgi?id=482811 --- Comment #11 from Samuel --- I have updated the system to the latest KDE packages available in Arch repos, the bug it's still happening in the original user and the new non privileged one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482811] On X11, After upgrading from Plasma 5, panel always moves moved from one screen to another one after screen unlock
https://bugs.kde.org/show_bug.cgi?id=482811 --- Comment #10 from Samuel --- (In reply to Nate Graham from comment #8) > Oh I have one more question, if you don't mind: > > When this happens, can you make the issue go away by restarting plasmashell > with `systemctl restart --user plasma-plasmashell.service` (assuming you're > using the systemd boot; if not, try `plasmashell --replace`)? Got back and test it, used systemctl restart --user plasma-plasmashell.service when it happened, and totally worked, also, when the bug appeared again, entering in edit mode got the taskbar back too. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483944] Mx master's scroll wheel slows down after a while since upgrading to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483944 --- Comment #4 from Samuel García --- (In reply to Jonathan from comment #3) > Using Solaar, I cannot trigger this by locking the screen, but by restarting > the mouse or letting it go into standby mode. The issue seems to be not > exactly with the scroll speed configuration (which determines how far a > scroll event moves) but the disabled hires scrolling mode, which causes > scroll events to be emitted only about twice per revolution, True! I just tested this, and the fact that it went to standby around the same time my screen was set to lock was a coincidence. I just let the mouse idle while using the computer and indeed I was able to replicate it this way. There is nothing relevant in journalctl around the time it went on standby, although when I moved the mouse again I could only see the following in journalctl (the mouse is connected via bluetooth): Mar 19 11:40:12 mostriyo bluetoothd[1788]: Device is already marked as connected Also: In my case, I don't use Solaar/logiops at all -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483944] Mx master's scroll wheel slows down after a while since upgrading to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483944 --- Comment #2 from Samuel García --- This is on the Wayland session, I haven't tested it on X but I will try to see if it happens there too -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483944] Mx master's scroll wheel slows down after a while since upgrading to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483944 Samuel García changed: What|Removed |Added CC||k...@samueldgv.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483944] New: Mx master's scroll wheel slows down after a while since upgrading to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483944 Bug ID: 483944 Summary: Mx master's scroll wheel slows down after a while since upgrading to Plasma 6 Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@samueldgv.com Target Milestone: --- SUMMARY Ever since upgrading to Plasma 6 (now currently on 6.0.2), my Mx master 3's scroll wheel has started to slow down to a crawl and slighly erratically on every application after a limited period of usage, most notably after a screen lock. This is fixed after a reboot, but the issue will consistently reappear again. This issue previously happened very rarely (maybe once a month) on Plasma 5, and I attributed it to the mouse itself. In these past cases, switching off and on the mouse fixed it, but now it doesn't. STEPS TO REPRODUCE 1. Have a Mx master 3 (not sure if any other mouse with a free/unlocked scrollwheel is affected) 2. Let the computer idle and automatically screen lock 3. Go back in: now the scrollwheel will be unusably slow Relevant external reports, all also mentioning that it started to happen after the Plasma 6 release: https://github.com/pwr-Solaar/Solaar/issues/2404 https://www.reddit.com/r/archlinux/comments/1bekbon/arch_kde/ I have been trying to catch something in journalctl, but I haven't found anything around the time before & after the issue happens. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482811] On X11, After upgrading from Plasma 5, panel always moves moved from one screen to another one after screen unlock
https://bugs.kde.org/show_bug.cgi?id=482811 --- Comment #9 from Samuel --- (In reply to Nate Graham from comment #8) > Oh I have one more question, if you don't mind: > > When this happens, can you make the issue go away by restarting plasmashell > with `systemctl restart --user plasma-plasmashell.service` (assuming you're > using the systemd boot; if not, try `plasmashell --replace`)? Gonna test that, as soon as I get back. Just give me a cuple of days -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482811] On X11, Panel has moved from one screen to another one after screen lock
https://bugs.kde.org/show_bug.cgi?id=482811 --- Comment #6 from Samuel --- (In reply to Nate Graham from comment #5) > Thanks. Can I ask you to set up a new user account and replicate your panel > setup, and see if it's still happening there? Basically I want to see if it > was caused by an issue upgrading old configs from Plasma 5 to Plasma 6. I did the following tests: Created a 2 users via KDE Settings, a standard and an administrator. Updated and restarted the machine, then logged into the new ones and set the second monitor as primary. In the standard one the bug happened again, and in addition, the second output was not recognized after second screen lock, so suddenly only one monitor was available in that account. In the administrator one all worked without issues, bug did not happen. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483142] [wayland] Pressing Enter on Application Dashboard does not open an Application in List
https://bugs.kde.org/show_bug.cgi?id=483142 --- Comment #4 from Samuel M. --- It seems I can edit the title, so I focused on the issue, and made it a bit vague. Since there's a separate issue for selecting an item (https://bugs.kde.org/show_bug.cgi?id=477348) , and in my interpretation enter should open the selected item, I would suggest waiting for a fix for that to test this. Frankly perhaps these issues should be unified. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483142] [wayland] Pressing Enter on Application Dashboard does not open an Application in List
https://bugs.kde.org/show_bug.cgi?id=483142 Samuel M. changed: What|Removed |Added Summary|[wayland] Pressing Enter on |[wayland] Pressing Enter on |Application Dashboard Takes |Application Dashboard does |Newline Instead of Opening |not open an Application in |First Application in List |List -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 477348] Application Dashboard: Can't select items via keyboard after searching
https://bugs.kde.org/show_bug.cgi?id=477348 Samuel M. changed: What|Removed |Added Version|5.27.80 |6.0.1 --- Comment #5 from Samuel M. --- It seems I need to submit changes to the plasma version with a comment... -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 477348] Application Dashboard: Can't select items via keyboard after searching
https://bugs.kde.org/show_bug.cgi?id=477348 Samuel M. changed: What|Removed |Added CC||samuel.maier2+bugs.kde.org@ ||hotmail.de --- Comment #4 from Samuel M. --- Note that the aspect of what happens if you press enter is or was handled in other issues, this issues remains with a strict focus on selecting an item with arrow down and tab. I will also be so free and adjust the plasma version. While the original issue was observed in plasma 5, and just concerned the plasma 6 version of the applet, this has been observed multiple times in plasma 6 now. The solution to the issue of opening an application with enter (https://bugs.kde.org/show_bug.cgi?id=483142) should probably be tested with a fix for this issue, so I'd recommend handling this first. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 483463] New: Help opened by ktouch has wrong link
https://bugs.kde.org/show_bug.cgi?id=483463 Bug ID: 483463 Summary: Help opened by ktouch has wrong link Classification: Applications Product: ktouch Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sebastian.gottfr...@posteo.de Reporter: samuel.fied...@proton.me Target Milestone: --- SUMMARY *** The help page opened by ktouch has a slightly wrong link. STEPS TO REPRODUCE 1. Open ktouch 2. Open menu on upper right corner => Help => Typewriting Trainer Handbook 3. Click on any link that references a sub-page OBSERVED RESULT Help shows me a "not found" when clicking on, for example, "Introduction". EXPECTED RESULT I expected Help to show me the correct page. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Using Konqueror I found out that the page opened by ktouch is "help:/ktouch". This causes the main help page of ktouch to open "help:/learning.html" instead of "help:/ktouch/learning.html". So we could easily fix this if we replaced "help:/ktouch" with "help:/ktouch/index.html", because then "learning.html" is relative to "help:/ktouch/" and not relative to "help:/". -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483142] [wayland] Pressing Enter on Application Dashboard Takes Newline Instead of Opening First Application in List
https://bugs.kde.org/show_bug.cgi?id=483142 Samuel M. changed: What|Removed |Added CC||samuel.maier2+bugs.kde.org@ ||hotmail.de Resolution|DUPLICATE |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from Samuel M. --- I'll be so free and reopen this. The 'Duplikate' mentioned the possibility to enter newline specifically, and was closed when that issue was resolved. But enter still does not open any application. We're supposed to have separate issues for each aspect. The title of this issue is a bit confused, but the issue description mostly concerns opening applications with enter, and also mentions potential issues I did not notice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482811] On X11, Panel has moved from one screen to another one after screen lock
https://bugs.kde.org/show_bug.cgi?id=482811 --- Comment #4 from Samuel --- (In reply to Nate Graham from comment #3) > Thanks. Is this consistent? Does it happen every time you do it? Or did it > just happen once? It's happening constantly, specially after first login of the day, if I reset primary mon few times, it stops. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482811] Taskbar changes position after screen lock.
https://bugs.kde.org/show_bug.cgi?id=482811 --- Comment #2 from Samuel --- (In reply to Nate Graham from comment #1) > Does it happen on Wayland too, or only X11? > > Is the actual primary screen changing, or is the panel the only thing that's > moving? > > Are the wallpapers or any desktop icons on the screens also changing, or are > they remaining the same? This happens on X11 only, wayland does not work for me, black screen is the only output. I found the solution for this wayland issue, haven't tweaked my system yet. Only the panel is changing, background images and desktop icons stay in place. I checked the screen configs after the bug, all screen configs did not changed, primary one was the same, but taskbar was in the non primary one. -- You are receiving this mail because: You are watching all bug changes.
[plasma-simplemenu] [Bug 482811] Taskbar changes position after screen lock.
https://bugs.kde.org/show_bug.cgi?id=482811 Samuel changed: What|Removed |Added CC||samuel.per@gmail.com Keywords||multiscreen, qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasma-simplemenu] [Bug 482811] New: Taskbar changes position after screen lock.
https://bugs.kde.org/show_bug.cgi?id=482811 Bug ID: 482811 Summary: Taskbar changes position after screen lock. Classification: Plasma Product: plasma-simplemenu Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: samuel.per@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I have dual monitor setup, when I lock the screen and login STEPS TO REPRODUCE 1. Set monitor 2 as primary 2. Lock screen with Super + L 3. Unlock and login again OBSERVED RESULT Task manager bar that was set in the monitor 2, is now on monitor 1, besides that in the Screen configuration, the primary one has not changed. EXPECTED RESULT Task manager should stay in monitor 2, as it was configured. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. ADDITIONAL INFORMATION kde-accessibility-meta 24.02-2 kde-cli-tools 6.0.1-1 kde-graphics-meta 24.02-2 kde-gtk-config 6.0.1-1 kde-system-meta 24.02-2 kde-utilities-meta 24.02-2 kdebugsettings 24.02.0-1 kdeclarative 6.0.0-1 kdeclarative5 5.115.0-1 kdecoration 6.0.1-1 kded 6.0.0-1 kded5 5.115.0-1 kdegraphics-mobipocket 24.02.0-1 kdegraphics-thumbnailers 24.02.0-1 kdelibs4support 5.115.0-1 kdepim-addons 24.02.0-1 kdepim-runtime 24.02.0-1 kdeplasma-addons 6.0.1-1 kdesu 6.0.0-1 kdesu5 5.115.0-1 plasma-activities 6.0.1-1 plasma-activities-stats 6.0.1-1 plasma-desktop 6.0.1-1 plasma-framework5 5.115.0-3 plasma-integration 6.0.1-2 plasma-nm 6.0.1-1 plasma-pa 6.0.1-1 plasma-sdk 6.0.1-1 plasma-thunderbolt 6.0.1-1 plasma-workspace 6.0.1-1 plasma5support 6.0.1-1 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 482123] Application Dashboard add new lines in search field
https://bugs.kde.org/show_bug.cgi?id=482123 Samuel M. changed: What|Removed |Added CC||samuel.maier2+bugs.kde.org@ ||hotmail.de --- Comment #6 from Samuel M. --- Also happens to me on Arch Linux. Isn't this a duplicate of https://bugs.kde.org/show_bug.cgi?id=477348 ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482062] IDEA OR FEATURE for ISSUE as User of KDE.
https://bugs.kde.org/show_bug.cgi?id=482062 --- Comment #4 from Samuel Robins --- Ok, Thank you for the response. From: David Edmundson Sent: Thursday, February 29, 2024 5:30 PM To: windsi...@hotmail.com Subject: [kwin] [Bug 482062] IDEA OR FEATURE for ISSUE as User of KDE. https://bugs.kde.org/show_bug.cgi?id=482062 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |INTENTIONAL --- Comment #3 from David Edmundson --- The feature does not exist in KDE. It's an interesting ideal, unfortunately only the application knows where the text cursor is if you're selecting by keyboard so it's difficult to do well for a niche feature. Lets follow it on the forum rather than in a bug tracker. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482063] New: FEATURE OR IDEA for KDE to resolve social media issue in task used daily.
https://bugs.kde.org/show_bug.cgi?id=482063 Bug ID: 482063 Summary: FEATURE OR IDEA for KDE to resolve social media issue in task used daily. Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: windsi...@hotmail.com Target Milestone: --- I will start by saying I am posting this as I cannot find feature in KDE that has this ability and how I come to posting idea. In social media all things has a buffer for posting, from twitter to chatbox in Youtube, have a character count limit can post at 1 time. My issue that brought me to posting is, I wish to post a cut and paste but have no clue live how many characters i am highlighting before the cut. This feature may exist in KDE and I may have missed it. which if I did hopefully I find ability at best. On with IDEA…WHILE HOLDING DOWN ONE BUTTON(hotkey) on the keyboard and clicking mouse to cut some text to paste to a social media platform with limited buffer: A TOOL TIP pops up showing the character amount as you highlight the text. That way you can know exactly how many characters your are highlighting to be posted to social media platform you are using at the time and if it will fit that social media platforms buffer size. PS: not to be redundant but hot key allow you only invoke it when need count without changing cut and paste so not annoying when do not need a count. Best Regards -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 482062] New: IDEA OR FEATURE for ISSUE as User of KDE.
https://bugs.kde.org/show_bug.cgi?id=482062 Bug ID: 482062 Summary: IDEA OR FEATURE for ISSUE as User of KDE. Classification: Frameworks and Libraries Product: frameworks-kded Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: windsi...@hotmail.com CC: kdelibs-b...@kde.org Target Milestone: --- I will start by saying I am posting this as I cannot find feature in KDE that has this ability and how I come to posting idea. In social media all things has a buffer for posting, from twitter to chatbox in Youtube, have a character count limit can post at 1 time. My issue that brought me to posting is, I wish to post a cut and paste but have no clue live how many characters i am highlighting before the cut. This feature may exist in KDE and I may have missed it. which if I did hopefully I find ability at best. On with IDEA…WHILE HOLDING DOWN ONE BUTTON(hotkey) on the keyboard and clicking mouse to cut some text to paste to a social media platform with limited buffer: A TOOL TIP pops up showing the character amount as you highlight the text. That way you can know exactly how many characters your are highlighting to be posted to social media platform you are using at the time and if it will fit that social media platforms buffer size. PS: not to be redundant but hot key allow you only invoke it when need count without changing cut and paste so not annoying when do not need a count. Best Regards -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 481891] Can't open images by click, just from within gwenview "File-Menu"
https://bugs.kde.org/show_bug.cgi?id=481891 Samuel Suther changed: What|Removed |Added Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 481891] New: Can't open images by click, just from within gwenview "File-Menu"
https://bugs.kde.org/show_bug.cgi?id=481891 Bug ID: 481891 Summary: Can't open images by click, just from within gwenview "File-Menu" Classification: Applications Product: gwenview Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: s.sut...@gmx.de Target Milestone: --- SUMMARY Open an Image by clicking on it (e.g. from dolphin) shows only an error-message, that this image couldn't be found. But if I open Gwenview > Files > Open and go to the exact same file, it work! STEPS TO REPRODUCE See Video: https://somup.com/cZntlhpgRI During recording this video I've seen that going to `/tmp/+++Screenshots` via `Gwenview > File open` , it result in another path as directly type in /tmp/... which will be used if just clicked from "Dolphin". >From Gwenview it's: `/run/user/1000/doc/61c3d954/` So it might be an issue with the way /tmp is used? Operating System: Manjaro Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.1.77-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 20 × 13th Gen Intel® Core™ i5-13600K Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7D98 System Version: 3.0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 478214] New: Lock screen wallpaper selector missing
https://bugs.kde.org/show_bug.cgi?id=478214 Bug ID: 478214 Summary: Lock screen wallpaper selector missing Classification: Plasma Product: kscreenlocker Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: samuelquesn...@gmail.com Target Milestone: --- SUMMERY The lock screen wallpaper selector under Screen Locking > configure appearance is missing STEPS TO REPRODUCE 1. Open systemsettings 2. Select Screen Locking 3. Click configure appearance OBSERVED RESULT The wallpaper select is missing EXPECTED RESULT The wallpaper selector should appear under the wallpaper type. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux kernel 6.6.4 (available in About System) KDE Plasma Version: 6.0 Beta 1 (5.90.0) KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemdgenie] [Bug 427902] Ability to create systemd timers and services
https://bugs.kde.org/show_bug.cgi?id=427902 Samuel Suther changed: What|Removed |Added CC||s.sut...@gmx.de --- Comment #1 from Samuel Suther --- Would also love this, as `cron` is kind of outdated. Please add a GUI in the KDE-Settings for it (e.g. as replacement for cron. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438903] KWin sometimes looses some effects when the compositor resumes after system suspend. [NVIDIA]
https://bugs.kde.org/show_bug.cgi?id=438903 Samuel changed: What|Removed |Added Resolution|UNMAINTAINED|FIXED --- Comment #2 from Samuel --- Yeah sorry, I forgot about this report that I made. This issue was fixed in one of the subsequent Plasma releases. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473738] New: kreminder crash.
https://bugs.kde.org/show_bug.cgi?id=473738 Bug ID: 473738 Summary: kreminder crash. Classification: I don't know Product: kde Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: aviumtechnol...@gmail.com Target Milestone: --- Application: kalendarac (5.23.3) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.11-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: It just happened out of no where. I was really doing nothing. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Reminders (kalendarac), signal: Segmentation fault PID: 2631 (kalendarac) UID: 1000 (ghost) GID: 1000 (ghost) Signal: 11 (SEGV) Timestamp: Thu 2023-08-24 23:21:34 CDT (1min 4s ago) Command Line: /usr/bin/kalendarac Executable: /usr/bin/kalendarac Control Group: /user.slice/user-1000.slice/session-3.scope Unit: session-3.scope Slice: user-1000.slice Session: 3 Owner UID: 1000 (ghost) Boot ID: dd92e729aa814479b16f44847eb69fe2 Machine ID: 9d2061b3812e41e887d29cd090e1fa2a Hostname: DELL-OS11-3060 Storage: /var/lib/systemd/coredump/core.kalendarac.1000.dd92e729aa814479b16f44847eb69fe2.2631.169293729400.zst (present) Size on Disk: 1.4M Message: Process 2631 (kalendarac) of user 1000 dumped core. Stack trace of thread 2631: #0 0x7f9d69c91e4c __pthread_kill_implementation (libc.so.6 + 0x91e4c) #1 0x7f9d69c3f126 raise (libc.so.6 + 0x3f126) #2 0x7f9d68763d9a _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d9a) #3 0x7f9d69c3f1f0 __restore_rt (libc.so.6 + 0x3f1f0) #4 0x7f9d691a8115 _ZNK9QListData5beginEv (libQt5Widgets.so.5 + 0x1a8115) #5 0x7f9d658ec06a _ZN17LXQtPlatformTheme12loadSettingsEv (libqtlxqt.so + 0x1106a) #6 0x7f9d658ec7ba _ZN17LXQtPlatformTheme17onSettingsChangedEv (libqtlxqt.so + 0x117ba) #7 0x7f9d6a725812 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x325812) #8 0x7f9d6a650cdf _ZN18QFileSystemWatcher11fileChangedERK7QStringNS_14QPrivateSignalE (libQt5Core.so.5 + 0x250cdf) #9 0x7f9d6a7257b3 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x3257b3) #10 0x7f9d6a650da3 _ZN24QFileSystemWatcherEngine11fileChangedERK7QStringb (libQt5Core.so.5 + 0x250da3) #11 0x7f9d6a656390 _ZN31QInotifyFileSystemWatcherEngine15readFromInotifyEv (libQt5Core.so.5 + 0x256390) #12 0x7f9d6a7257b3 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x3257b3) #13 0x7f9d6a728b0f _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x328b0f) #14 0x7f9d6a729315 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x329315) #15 0x7f9d6a6ed568 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ed568) #16 0x7f9d6a746f7d socketNotifierSourceDispatch (libQt5Core.so.5 + 0x346f7d) #17 0x7f9d67f169b8 g_main_context_dispatch (libglib-2.0.so.0 + 0x5d9b8) #18 0x7f9d67f16dc8 n/a (libglib-2.0.so.0 + 0x5ddc8) #19 0x7f9d67f16e5c g_main_context_iteration (libglib-2.0.so.0 + 0x5de5c) #20 0x7f9d6a7464a6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3464a6) #21 0x7f9d6a6ebffb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2ebffb) #22 0x7f9d6a6f4490 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2f4490) #23 0x561cbe076d65 n/a (kalendarac + 0x9d65) #24 0x7f9d69c281f0 __libc_start_call_main (libc.so.6 + 0x281f0) #25 0x7f9d69c282b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x282b9) #26 0x561cbe077385 n/a (kalendarac + 0xa385) Stack trace of thread 2843: #0 0x7f9d69d0a0af __poll (libc.so.6 + 0x10a0af) #1 0x7f9d67f16d3e n/a (libglib-2.0.so.0 + 0x5dd3e) #2 0x7f9d67f16e5c g_main_context_iteration (libglib-2.0.so.0 + 0x5de5c) #3 0x7f9d6a7464be _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3464be) #4 0x7f9d6a6ebffb
[Discover] [Bug 473518] Crash when checking system upgrade checkbox
https://bugs.kde.org/show_bug.cgi?id=473518 --- Comment #1 from Samuel Q --- Created attachment 161052 --> https://bugs.kde.org/attachment.cgi?id=161052=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 473518] New: Crash when checking system upgrade checkbox
https://bugs.kde.org/show_bug.cgi?id=473518 Bug ID: 473518 Summary: Crash when checking system upgrade checkbox Classification: Applications Product: Discover Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: samuelquesn...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.80) Qt Version: 6.6.0 Frameworks Version: 5.240.0 Operating System: Linux 5.15.0-60-generic x86_64 Windowing System: X11 Distribution: KDE neon Unstable Edition DrKonqi: 5.27.80 [CoredumpBackend] -- Information about the crash: When checking for updates in KDE Neon and it finds syetm package updates clicking update all doesn't do anything. When clicking refresh the system packages updates become unchecked. Checking them usally crashes Discover but this time it didn't happen right away so it might be seperate crash The crash can be reproduced every time. -- Backtrace (Reduced): #6 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140012518724032) at ./nptl/pthread_kill.c:44 #7 __pthread_kill_internal (signo=6, threadid=140012518724032) at ./nptl/pthread_kill.c:78 #8 __GI___pthread_kill (threadid=140012518724032, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #9 0x7f57391f2476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #10 0x7f57391d87f3 in __GI_abort () at ./stdlib/abort.c:79 The reporter indicates this bug may be a duplicate of or related to bug 472295, bug 469554, bug 472045. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 472222] New: Kickoff search crashes plasmashell (qt6)
https://bugs.kde.org/show_bug.cgi?id=47 Bug ID: 47 Summary: Kickoff search crashes plasmashell (qt6) Classification: Plasma Product: krunner Version: master Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: samuelquesn...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY Plasma Shell crashes and automatically restarts itself when searching for anything in kickoff. STEPS TO REPRODUCE 1. Open Kickoff 2. Start typing OBSERVED RESULT Plasma Shell crashes and automatically restarts itself EXPECTED RESULT Plasma should not crash and kickoff should give me search results SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 ADDITIONAL INFORMATION Stack trace of thread 1226: #0 0x7fb985096a7c __pthread_kill_implementation (libc.so.6 + 0x96a7c) #1 0x7fb985042476 __GI_raise (libc.so.6 + 0x42476) #2 0x7fb987f8270f _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x870f) #3 0x7fb985042520 __restore_rt (libc.so.6 + 0x42520) #4 0x7fb985921d94 _ZNK4QUrl7isEmptyEv (libQt6Core.so.6 + 0x121d94) #5 0x7fb985921ded _ZNK4QUrl7isValidEv (libQt6Core.so.6 + 0x121ded) #6 0x7fb98534da51 n/a (libKF6KIOCore.so.6 + 0x114a51) #7 0x7fb98598369f _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18369f) #8 0x7fb9869875f6 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1875f6) #9 0x7fb985937378 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x137378) #10 0x7fb98593aec7 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x13aec7) #11 0x7fb985b97fa7 n/a (libQt6Core.so.6 + 0x397fa7) #12 0x7fb9845ebd3b g_main_context_dispatch (libglib-2.0.so.0 + 0x55d3b) #13 0x7fb984641258 n/a (libglib-2.0.so.0 + 0xab258) #14 0x7fb9845e93e3 g_main_context_iteration (libglib-2.0.so.0 + 0x533e3) #15 0x7fb985b9780e _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x39780e) #16 0x7fb985943dcb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x143dcb) #17 0x7fb98593fc56 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x13fc56) #18 0x559aee2a2d71 n/a (plasmashell + 0x3ad71) #19 0x7fb985029d90 __libc_start_call_main (libc.so.6 + 0x29d90) #20 0x7fb985029e40 __libc_start_main_impl (libc.so.6 + 0x29e40) #21 0x559aee2a2ed5 n/a (plasmashell + 0x3aed5) Stack trace of thread 1252: #0 0x7fb985118d7f __GI___poll (libc.so.6 + 0x118d7f) #1 0x7fb9846411f6 n/a (libglib-2.0.so.0 + 0xab1f6) #2 0x7fb9845e93e3 g_main_context_iteration (libglib-2.0.so.0 + 0x533e3) #3 0x7fb985b97891 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x397891) #4 0x7fb985943dcb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x143dcb) #5 0x7fb985a38214 _ZN7QThread4execEv (libQt6Core.so.6 + 0x238214) #6 0x7fb98668e58e n/a (libQt6DBus.so.6 + 0x3558e) #7 0x7fb985aae86f n/a (libQt6Core.so.6 + 0x2ae86f) #8 0x7fb985094b43 start_thread (libc.so.6 + 0x94b43) #9 0x7fb985126a00 __clone3 (libc.so.6 + 0x126a00) Stack trace of thread 1539: #0 0x7fb985091197 __futex_abstimed_wait_common64 (libc.so.6 + 0x91197) #1 0x7fb985093f1b __pthread_cond_wait_common (libc.so.6 + 0x93f1b) #2 0x7fb985ab69e4 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2b69e4) #3 0x7fb985ab35cd n/a (libQt6Core.so.6 + 0x2b35cd) #4 0x7fb985aae86f n/a (libQt6Core.so.6 + 0x2ae86f) #5 0x7fb985094b43 start_thread (libc.so.6 + 0x94b43) #6 0x7fb985126a00 __clone3 (libc.so.6 + 0x126a00) Stack trace of thread 1547: #0 0x7fb985091197 __futex_abstimed_wait_common64 (libc.so.6 + 0x91197) #1 0x7fb985093ac1 __pthread_cond_wait_common (libc.so.6 + 0x93ac1) #2 0x7fb985ab6a8b
[xdg-desktop-portal-kde] [Bug 472078] xdg-desktop-portal-kde crashes on Plasma 6 startup
https://bugs.kde.org/show_bug.cgi?id=472078 --- Comment #4 from Samuel Q --- I can't reproduce after doing a full update. If I run coredumpctl the last xdg-desktop-portal-kde crash shows up as inaccessible and the rest are labeled missing. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 472078] xdg-desktop-portal-kde crashes on Plasma 6 startup
https://bugs.kde.org/show_bug.cgi?id=472078 --- Comment #1 from Samuel Q --- Created attachment 160200 --> https://bugs.kde.org/attachment.cgi?id=160200=edit Acual log -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 472078] New: xdg-desktop-portal-kde crashes on Plasma 6 startup
https://bugs.kde.org/show_bug.cgi?id=472078 Bug ID: 472078 Summary: xdg-desktop-portal-kde crashes on Plasma 6 startup Classification: Plasma Product: xdg-desktop-portal-kde Version: git-master Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: samuelquesn...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- Created attachment 160199 --> https://bugs.kde.org/attachment.cgi?id=160199=edit The log from Crashed Processes Viewer SUMMARY xdg-desktop-portal-kde silently crashes when logging into a Plasma 6 session. STEPS TO REPRODUCE 1. Log into a new Plasma 6 session OBSERVED RESULT Nothing unual seems to happen but when opening the crashed process viewer xdg-desktop-portal-kde shows up every time a session is started EXPECTED RESULT xdg-desktop-portal-kde should not crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon Unstable (Updated a few days ago) (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 470474] new nvidia beta driver (535 series) not showing statistics
https://bugs.kde.org/show_bug.cgi?id=470474 Samuel changed: What|Removed |Added CC||samping...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 464869] Installing updates corrupts Grub 2 ( unbootable system)
https://bugs.kde.org/show_bug.cgi?id=464869 --- Comment #9 from Samuel Q --- (In reply to Lassi Väätämöinen from comment #8) > Did you run an upgrade before rebooting? No, I booted the Neon unstable ISO through Ventoy and shrunk an partition to install it. Grub froze on the first boot after that. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 464869] Installing updates corrupts Grub 2 ( unbootable system)
https://bugs.kde.org/show_bug.cgi?id=464869 --- Comment #7 from Samuel Q --- This happened to me again, but this time when first reboot after dualbooting on real legacy BIOS system. That makes me think this is a problem with GRUB on KDE Neon, and not pkcon one. I haven't tested on a UEFI system yet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia
https://bugs.kde.org/show_bug.cgi?id=469016 --- Comment #26 from Samuel --- (In reply to Rafael Linux User from comment #25) > (In reply to rushmash from comment #24) > Your workaround seems to "work"!!! There is also another method to workaround this issue: Click on show desktop button to hide all open windows > Right click on panel > Edit panel > Move the panel from horizontal edge to vertical edge of screen (or vice-versa) > Move back to original position Now panel starts working again. Changing the panel alignment seems to make the problem go away for some reason. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 463636] After sleep, KDE Connect complains about dBus service files
https://bugs.kde.org/show_bug.cgi?id=463636 Samuel changed: What|Removed |Added CC||nagrap...@gmail.com --- Comment #1 from Samuel --- *** Bug 470660 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 470660] KDEconnect disconnects on mac
https://bugs.kde.org/show_bug.cgi?id=470660 Samuel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Samuel --- *** This bug has been marked as a duplicate of bug 463636 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 470660] KDEconnect disconnects on mac
https://bugs.kde.org/show_bug.cgi?id=470660 Samuel changed: What|Removed |Added CC||flightman...@me.com --- Comment #1 from Samuel --- I also have this problem, and have experienced it for a few years. Where can we start digging to figure out the bug? I am using kdeconnect-indicator version 23.7.70 on MacOS 13.3.1 (a) (22E772610a). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450914] Wayland, games on Nvidia are force vsynced
https://bugs.kde.org/show_bug.cgi?id=450914 --- Comment #37 from Samuel --- Update: This issue will be fixed in the upcoming NVIDIA 545 Driver (https://forums.developer.nvidia.com/t/nvidia-bug-kde-wayland-games-are-force-vsynced/237880/21). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 470273] New: KDE connect daemon crashed while sending files from android device
https://bugs.kde.org/show_bug.cgi?id=470273
Bug ID: 470273
Summary: KDE connect daemon crashed while sending files from
android device
Classification: Applications
Product: kdeconnect
Version: 23.04.1
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: thepixelc...@duck.com
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
Application: kdeconnectd (23.04.1)
Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.3-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: EndeavourOS
DrKonqi: 5.27.5 [KCrashBackend]
-- Information about the crash:
I was sending three pdfs from my android to my computer, when crashed after one
file was sended, I don't know if it is usefull but my computer is connected via
ethernet cable and while I was using kdeconnect the computer was receiving
files via samba
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Demonio de KDE Connect (kdeconnectd), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x41)
at /usr/include/c++/13.1.1/bits/atomic_base.h:837
#7 std::atomic::load(std::memory_order) const [clone .constprop.0]
(this=0x41, __m=std::memory_order_relaxed) at
/usr/include/c++/13.1.1/atomic:577
#8 0x7f158dccf966 in QAtomicOps::loadRelaxed (_q_value=...,
_q_value=...) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#9 QBasicAtomicPointer::loadRelaxed (this=,
this=) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248
#10 doActivate (sender=0x55a639a1a5f0, signal_index=4,
argv=0x7ffd756c9c50) at kernel/qobject.cpp:3850
#11 0x7f158dbf2df6 in QIODevice::channelReadyRead
(this=this@entry=0x55a639a1a5f0, _t1=, _t1@entry=0) at
.moc/moc_qiodevice.cpp:197
#12 0x7f158d9890ae in QSslSocketBackendPrivate::transmit
(this=0x55a639a41a30) at ssl/qsslsocket_openssl.cpp:1202
#13 0x7f158dcd01a3 in doActivate (sender=0x55a639a74810,
signal_index=3, argv=0x7ffd756cada0) at kernel/qobject.cpp:3935
#14 0x7f158d951180 in QAbstractSocketPrivate::emitReadyRead (channel=0,
this=0x55a639b49460) at socket/qabstractsocket.cpp:1323
#15 QAbstractSocketPrivate::canReadNotification (this=0x55a639b49460) at
socket/qabstractsocket.cpp:748
#16 0x7f158d96828a in QAbstractSocketEngine::readNotification
(this=) at socket/qabstractsocketengine.cpp:160
#17 QReadNotifier::event (this=, e=) at
socket/qnativesocketengine.cpp:1274
#18 0x7f158e97893f in QApplicationPrivate::notify_helper (this=, receiver=0x55a6399f0cd0, e=0x7ffd756caeb0) at
kernel/qapplication.cpp:3640
#19 0x7f158dc9ab18 in QCoreApplication::notifyInternal2
(receiver=0x55a6399f0cd0, event=0x7ffd756caeb0) at
kernel/qcoreapplication.cpp:1064
#20 0x7f158dce8c76 in socketNotifierSourceDispatch (source=0x55a63954e420)
at kernel/qeventdispatcher_glib.cpp:107
#21 0x7f158c10f53b in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#22 0x7f158c16c219 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0x7f158c10e1a2 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#24 0x7f158dce9f0c in QEventDispatcherGlib::processEvents
(this=0x55a63954a9b0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#25 0x7f158dc99824 in QEventLoop::exec (this=this@entry=0x7ffd756cb130,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#26 0x7f158dc9acc3 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#27 0x7f158e13b7c2 in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1870
#28 0x7f158e976cda in QApplication::exec () at kernel/qapplication.cpp:2832
#29 0x55a638c02597 in main (argc=, argv=) at
/usr/src/debug/kdeconnect/kdeconnect-kde-23.04.1/daemon/kdeconnectd.cpp:185
[Inferior 1 (process 751) detached]
The reporter indicates this bug may be a duplicate of or related to bug 467015.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 429211] [X11] Digital clock/whole panel sometimes stops updating until there is user interaction with Plasma
https://bugs.kde.org/show_bug.cgi?id=429211 Samuel changed: What|Removed |Added CC|samping...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469894] [NVIDIA+WAYLAND] Plasmashell crashes when dragging a file/image from notifications applet
https://bugs.kde.org/show_bug.cgi?id=469894 Samuel changed: What|Removed |Added Assignee|samping...@gmail.com|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469894] [NVIDIA+WAYLAND] Plasmashell crashes when dragging a file/image from notifications applet
https://bugs.kde.org/show_bug.cgi?id=469894 --- Comment #3 from Samuel --- Created attachment 159058 --> https://bugs.kde.org/attachment.cgi?id=159058=edit Journal log of plasmashell when the crash occured -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469894] [NVIDIA+WAYLAND] Plasmashell crashes when dragging a file/image from notifications applet
https://bugs.kde.org/show_bug.cgi?id=469894 Samuel changed: What|Removed |Added Assignee|plasma-b...@kde.org |samping...@gmail.com Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Samuel --- Created attachment 159057 --> https://bugs.kde.org/attachment.cgi?id=159057=edit GDB Log of reproduced bug in plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469894] New: [NVIDIA+WAYLAND] Plasmashell crashes when dragging a file/image from notifications applet
https://bugs.kde.org/show_bug.cgi?id=469894 Bug ID: 469894 Summary: [NVIDIA+WAYLAND] Plasmashell crashes when dragging a file/image from notifications applet Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: samping...@gmail.com Target Milestone: 1.0 SUMMARY In Plasma Wayland session, when a file/image is dragged from system tray notifications applet, the entire shell crashes. STEPS TO REPRODUCE 1. Log into Plasma Wayland session and take a screenshot or download/move/copy a file. 2. Let the notification timer run-out and get stored in notifications applet in system tray. 3. Open the notifications applet and drag the screenshot/file from here -> Plasmashell crashes and gets replaced immediately. OBSERVED RESULT Plasmashell crashes when dragging a file from notifications applet and gets replaced immediately. EXPECTED RESULT Dragging a file from notification stored inside notification applet not resulting a crash. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION using NVIDIA GeForce GTX 1060 with the NVIDIA proprietary 525.89 driver. Here is the video showcasing this bug: https://www.youtube.com/watch?v=6SQyGM9K1p4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia
https://bugs.kde.org/show_bug.cgi?id=469016 --- Comment #11 from Samuel --- Can confirm that this has been happening when I hover back and forth between applications (until the tooltip shows) in icon-only task manager or when I open the pinned Firefox from task manager and place the cursor on the icon until Firefox opens. `plasmashell --replace` fixes this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia
https://bugs.kde.org/show_bug.cgi?id=469016 Samuel changed: What|Removed |Added CC||samping...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467835] On login, containment for left-most screen is placed on right-most screen overlapping its containment, and left-most screen gets a black background
https://bugs.kde.org/show_bug.cgi?id=467835 Samuel Suther changed: What|Removed |Added CC||s.sut...@gmx.de Platform|Archlinux |Manjaro Version|5.27.3 |5.27.4 Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #12 from Samuel Suther --- plasmashell 5.27.4 Same here since some weeks. After startup left screen is black. Right-Mouseclick on it, don't show any context... seems plasmashell is fully broken for it. I've made a little script to reload it... after running it, it work. But that is only an unsatisfying workaround. Hope it will be fixed soon. ``` #!/bin/bash killall plasmashell plasmashell > /dev/null 2>&1 & disown ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467536] [WAYLAND] Task Switcher window appears dim (unfocused)
https://bugs.kde.org/show_bug.cgi?id=467536 --- Comment #1 from Samuel --- Created attachment 157398 --> https://bugs.kde.org/attachment.cgi?id=157398=edit Task switcher in Plasma X11 session Note: See the brightness difference in Task Switcher window between Wayland and X11 sessions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467536] New: [WAYLAND] Task Switcher window appears dim (unfocused)
https://bugs.kde.org/show_bug.cgi?id=467536 Bug ID: 467536 Summary: [WAYLAND] Task Switcher window appears dim (unfocused) Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: samping...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 157396 --> https://bugs.kde.org/attachment.cgi?id=157396=edit Task switcher appearance in Wayland session SUMMARY The task switcher in Plasma Wayland session appears dim and dull as compared to Plasma X11 session. STEPS TO REPRODUCE 1. Log-in to Plasma Wayland session 2. Press and hold Alt+tab. 3. The task switcher appears dim and dull as compared to X11 session. OBSERVED RESULT In Plasma Wayland session, the task switcher window that shows up when you alt+tab to switch windows appear very dull and appears to be "unfocused". EXPECTED RESULT The task switcher window work as it already does in X11 session - focused and bright. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103 Qt Version: 5.15.8 ADDITIONAL INFORMATION I have tested the various task switchers - Breeze, Thumbnail Grid, Cover/Flip Switch etc. They all appear dim in Wayland session as compared to X11 session. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466806] [Flatpak Permissions KCM] Clicking on app doesn't show permission settings
https://bugs.kde.org/show_bug.cgi?id=466806 --- Comment #5 from Samuel Reddy --- (In reply to Samuel Reddy from comment #4) > Issue still exists on Plasma 5.27.3 with the same error. Tested on Kubuntu > with Backports ppa. Nevermind, it has been fixed on the upcoming Kubuntu 23.04 Lunar Lobster. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467181] No screen output shown when resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=467181 --- Comment #4 from Samuel Reddy --- It appears that on the upcoming Kubuntu 23.04, the issue seems to be fixed. I tested using the daily images of Lunar Lobster. This suggests that it is either an old kernel causing the issue or a distro issue that has been fixed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466806] [Flatpak Permissions KCM] Clicking on app doesn't show permission settings
https://bugs.kde.org/show_bug.cgi?id=466806 --- Comment #4 from Samuel Reddy --- Issue still exists on Plasma 5.27.3 with the same error. Tested on Kubuntu with Backports ppa. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467181] No screen output shown when resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=467181 --- Comment #3 from Samuel Reddy --- Created attachment 157198 --> https://bugs.kde.org/attachment.cgi?id=157198=edit systemd log Contains log from systemd-journald -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467181] No screen output shown when resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=467181 --- Comment #2 from Samuel Reddy --- Created attachment 157197 --> https://bugs.kde.org/attachment.cgi?id=157197=edit Kernel dmesg log Contains log from dmesg -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467181] No screen output shown when resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=467181 Samuel Reddy changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467181] New: No screen output shown when resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=467181 Bug ID: 467181 Summary: No screen output shown when resuming from sleep Classification: Plasma Product: kwin Version: 5.27.2 Platform: Kubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: samuelsumukhre...@gmail.com Target Milestone: --- Created attachment 157180 --> https://bugs.kde.org/attachment.cgi?id=157180=edit log SUMMARY On Plasma Wayland, when I resume from sleep mode, I get no output on my monitor and the only way to workaround the problem is to kill kwin or restart the computer. STEPS TO REPRODUCE 1. Use Plasma Wayland 2. Put system into sleep mode, not hibernate 3. Resume from sleep mode 4. No output is shown OBSERVED RESULT When resuming from sleep, I have nothing on my screen and my monitor says their is no output EXPECTED RESULT The lock screen should show up like normal when resuming from sleep mode SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 (With backports ppa) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NAVI22 Manufacturer: ASUS ADDITIONAL INFORMATION I am using a hdmi monitor that is connected to a custom built pc with an amd graphics card -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466806] [Flatpak Permissions KCM] Clicking on app doesn't show permission settings
https://bugs.kde.org/show_bug.cgi?id=466806 --- Comment #2 from Samuel Reddy --- I get this weird error saying something is not defined when clicking an app: (process:57626): GLib-CRITICAL **: 15:40:15.885: g_atomic_ref_count_dec: assertion 'old_value > 0' failed Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion file:///usr/share/kpackage/kcms/kcm_flatpak/contents/ui/main.qml:28: ReferenceError: FlatpakReferencesModel is not defined file:///usr/share/kpackage/kcms/kcm_flatpak/contents/ui/main.qml:28: ReferenceError: FlatpakReferencesModel is not defined file:///usr/share/kpackage/kcms/kcm_flatpak/contents/ui/main.qml:28: ReferenceError: FlatpakReferencesModel is not defined file:///usr/share/kpackage/kcms/kcm_flatpak/contents/ui/main.qml:28: ReferenceError: FlatpakReferencesModel is not defined file:///usr/share/kpackage/kcms/kcm_flatpak/contents/ui/main.qml:28: ReferenceError: FlatpakReferencesModel is not defined file:///usr/share/kpackage/kcms/kcm_flatpak/contents/ui/main.qml:28: ReferenceError: FlatpakReferencesModel is not defined -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466932] New: [Wayland] Desktop icons disappear after locking screen for a while
https://bugs.kde.org/show_bug.cgi?id=466932 Bug ID: 466932 Summary: [Wayland] Desktop icons disappear after locking screen for a while Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: samuelsumukhre...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 157033 --> https://bugs.kde.org/attachment.cgi?id=157033=edit Picture of issue SUMMARY When I lock my screen for a while, then unlock my computer, the desktop icons disappear! The only way to show the desktop icons is to restart plasmashell. STEPS TO REPRODUCE 1. Lock the screen (don't use sleep mode, just lock) for a while 2. Unlock the screen 3. Desktop icons are missing OBSERVED RESULT Desktop icons are missing after unlocking EXPECTED RESULT Desktop icons should still show even after leaving it for a while, then unlocking SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 (With backports ppa) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NAVI22 Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466806] New: [Flatpak Permissions KCM] Clicking on app doesn't show permission settings
https://bugs.kde.org/show_bug.cgi?id=466806 Bug ID: 466806 Summary: [Flatpak Permissions KCM] Clicking on app doesn't show permission settings Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_flatpak Assignee: plasma-b...@kde.org Reporter: samuelsumukhre...@gmail.com CC: joshiesuha...@gmail.com Target Milestone: --- SUMMARY When using the flatpak permission settings in system settings, clicking on a app does not show the permissions or allow you to change the settings. STEPS TO REPRODUCE 1. Open system settings 2. Click applications 3. Click on flatpak permission settings 4. Click on an app you want to change the permissions of 5. No page is shown to change the permission or view the permission of the app OBSERVED RESULT The page in the kcm to change the permissions does not show up when I click an app EXPECTED RESULT The page to show the permissions and change the permissions should show up when I click on an app SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 (With backports PPA) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NAVI22 Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442826] After cold boot one of multiple monitors stays black with no wallpaper and no context menu, but windows can be dragged to it
https://bugs.kde.org/show_bug.cgi?id=442826 Samuel Suther changed: What|Removed |Added Resolution|DUPLICATE |UNMAINTAINED Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442826] After cold boot one of multiple monitors stays black with no wallpaper and no context menu, but windows can be dragged to it
https://bugs.kde.org/show_bug.cgi?id=442826 Samuel Suther changed: What|Removed |Added CC||s.sut...@gmx.de --- Comment #8 from Samuel Suther --- (In reply to Corentin Girard from comment #3) > (In reply to Nate Graham from comment #1) > > > > *** This bug has been marked as a duplicate of bug 427861 *** > > I think this is **not** a duplicate. > > Bug 427861 is "just" a reset of settings. Your settings go back to default > but at least, the desktop works, it has a (default) wallpaper and you can > have a context menu when you right-click. > > Here in this bug, what we call a "zombie" desktop screen is a desktop where > the wallpaper is unset (black), without any trace of Plasma Desktop. You > can't even right click on the desktop. You can just drag windows on the > "zombie" desktop. > > I'm not even sure the "zombie" desktop loses its settings, we would have to > investigate. But it seems to be a temporary glitch because it does that one > out of 5 startups. > > Also, for me it only does that on my second monitor. Have the same issue since 1 week. ``` Operating System: Manjaro Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 5.15.91-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3610QM CPU @ 2.30GHz Memory: 15.1 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 Manufacturer: ASUSTeK COMPUTER INC. Product Name: N76VZ System Version: 1.0 ``` After logout and re-login as same user, it appears without an issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463987] Mouse was cause of the issue. Cancel BUG
https://bugs.kde.org/show_bug.cgi?id=463987 Samuel Robins changed: What|Removed |Added Summary|kubuntu 22.04, kubuntu |Mouse was cause of the |22.10, when i install |issue. Cancel BUG |cheerful phantasy theme,| |even after I remove it I| |can not drag as it random | |stops | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463987] kubuntu 22.04, kubuntu 22.10, when i install cheerful phantasy theme, even after I remove it I can not drag as it random stops
https://bugs.kde.org/show_bug.cgi?id=463987 --- Comment #1 from Samuel Robins --- Also when you install cheeful phantasy theme, unlike the others there is no small icon on picture to click uninstall it, I tried and removed it manually but the bug stays. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463987] New: kubuntu 22.04, kubuntu 22.10, when i install cheerful phantasy theme, even after I remove it I can not drag as it random stops
https://bugs.kde.org/show_bug.cgi?id=463987 Bug ID: 463987 Summary: kubuntu 22.04, kubuntu 22.10, when i install cheerful phantasy theme, even after I remove it I can not drag as it random stops Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: windsi...@hotmail.com CC: plasma-b...@kde.org 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. installed 2 different versions of Kubuntu 22.04 and 22.10 2. when I load in desktop on fresh install, then install theme cheerful phantasy. 3. then no matter what program, or window or software i am in(filemanager, pycharm, so on) when hold to drag highlight it random just stops or skips say pasting rearranges what try cut and paste with a drag. if i try to drag a file on doplin split view from one window to next, it random just quit during the drag. affects every single application i tried to use. I get random garbage when cutting and pasting to the terminal as well in front of what cut paste and after. OBSERVED RESULT describe above EXPECTED RESULT to remove whatever is doing it from my system , after testing, I thought it was pycharm, but i believe its the cheeful phantasy theme. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.10 (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION its almost impossible to even drag a window on the screen. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 327548] false positive while destroying mutex
https://bugs.kde.org/show_bug.cgi?id=327548 --- Comment #19 from Samuel Thibault --- (ran it for an hour) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 327548] false positive while destroying mutex
https://bugs.kde.org/show_bug.cgi?id=327548 --- Comment #18 from Samuel Thibault --- I have run the reproducer on all the various systems previously mentioned, with no issue so far, so it seems we're good with that fix. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 327548] false positive while destroying mutex
https://bugs.kde.org/show_bug.cgi?id=327548 --- Comment #17 from Samuel Thibault --- Ah, configure.ac already detects which case that is. So we need a valgrind built against the proper glibc, that's why I hadn't the proper name. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 327548] false positive while destroying mutex
https://bugs.kde.org/show_bug.cgi?id=327548
--- Comment #16 from Samuel Thibault ---
> I would expect these to be covered by the default suppressions:
> {
>helgrind-glibc2X-004
>Helgrind:Race
>obj:*/lib*/libc-2.*so*
> }
Ah, but glibc renamed libc-2.*so* into just libc.so.6, so that suppression
won't take effect. Duplicating the entry with libc.so.* does indeed seem to
avoid the warnings. I'll try to test on more machines and archs.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 327548] false positive while destroying mutex
https://bugs.kde.org/show_bug.cgi?id=327548 --- Comment #14 from Samuel Thibault --- FYI, it's glibc 2.36: - pthread_mutex_lock.c:94 is when it checks assert (mutex->__data.__owner == 0); after obtaining the lock - pthread_mutex_lock.c:182 is when it sets mutex->__data.__owner after obtaining the lock - pthread_mutex_unlock.c:62 is when it clears mutex->__data.__owner before releasing the lock - pthread_mutex_unlock.c:65 is when it --mutex->__data.__nusers; before releasing the lock The other cond-related lines are more complex to describe, but they'll probably get fixed the same way as mutex would get fixed. I guess the disabling of checking somehow perturbates helgrind's history record (I guess that's part of the "This puts it in the same state as new memory allocated by this thread -- that is, basically owned exclusively by this thread." comment for the VALGRIND_HG_ENABLE_CHECKING macro) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 327548] false positive while destroying mutex
https://bugs.kde.org/show_bug.cgi?id=327548 --- Comment #12 from Samuel Thibault --- Yes that avoids that exact issue, but then a flurry of new ones pop up, I was not getting them before: ==2511392== Possible data race during read of size 4 at 0x10C128 by thread #2 ==2511392== Locks held: none ==2511392==at 0x48F31A2: pthread_mutex_lock@@GLIBC_2.2.5 (pthread_mutex_lock.c:94) ==2511392==by 0x48487F8: mutex_lock_WRK (hg_intercepts.c:937) ==2511392==by 0x109272: f (in /net/inria/home/sthibault/test) ==2511392==by 0x484B966: mythread_wrapper (hg_intercepts.c:406) ==2511392==by 0x48EFFD3: start_thread (pthread_create.c:442) ==2511392==by 0x496F8CF: clone (clone.S:100) ==2511392== ==2511392== This conflicts with a previous write of size 4 by thread #1 ==2511392== Locks held: none ==2511392==at 0x48F4A47: __pthread_mutex_unlock_usercnt (pthread_mutex_unlock.c:62) ==2511392==by 0x48EF26D: __pthread_cond_wait_common (pthread_cond_wait.c:419) ==2511392==by 0x48EF26D: pthread_cond_wait@@GLIBC_2.3.2 (pthread_cond_wait.c:618) ==2511392==by 0x484BB03: pthread_cond_wait_WRK (hg_intercepts.c:1291) ==2511392==by 0x10933B: main (in /net/inria/home/sthibault/test) ==2511392== Address 0x10c128 is 8 bytes inside data symbol "mutex" ==2511392== ==2511392== ==2511392== ==2511392== Possible data race during write of size 4 at 0x10C128 by thread #2 ==2511392== Locks held: none ==2511392==at 0x48F31B9: pthread_mutex_lock@@GLIBC_2.2.5 (pthread_mutex_lock.c:182) ==2511392==by 0x48487F8: mutex_lock_WRK (hg_intercepts.c:937) ==2511392==by 0x109272: f (in /net/inria/home/sthibault/test) ==2511392==by 0x484B966: mythread_wrapper (hg_intercepts.c:406) ==2511392==by 0x48EFFD3: start_thread (pthread_create.c:442) ==2511392==by 0x496F8CF: clone (clone.S:100) ==2511392== ==2511392== This conflicts with a previous write of size 4 by thread #1 ==2511392== Locks held: none ==2511392==at 0x48F4A47: __pthread_mutex_unlock_usercnt (pthread_mutex_unlock.c:62) ==2511392==by 0x48EF26D: __pthread_cond_wait_common (pthread_cond_wait.c:419) ==2511392==by 0x48EF26D: pthread_cond_wait@@GLIBC_2.3.2 (pthread_cond_wait.c:618) ==2511392==by 0x484BB03: pthread_cond_wait_WRK (hg_intercepts.c:1291) ==2511392==by 0x10933B: main (in /net/inria/home/sthibault/test) ==2511392== Address 0x10c128 is 8 bytes inside data symbol "mutex" ==2511392== ==2511392== ==2511392== ==2511392== Lock at 0x10C120 was first observed ==2511392==at 0x484CFE9: pthread_mutex_init (hg_intercepts.c:818) ==2511392==by 0x1092EE: main (in /net/inria/home/sthibault/test) ==2511392== Address 0x10c120 is 0 bytes inside data symbol "mutex" ==2511392== ==2511392== Possible data race during write of size 8 at 0x10C0E8 by thread #2 ==2511392== Locks held: 1, at address 0x10C120 ==2511392==at 0x48EEE29: __atomic_wide_counter_add_relaxed (atomic_wide_counter.h:57) ==2511392==by 0x48EEE29: __condvar_add_g1_start_relaxed (pthread_cond_common.c:52) ==2511392==by 0x48EEE29: __condvar_quiesce_and_switch_g1 (pthread_cond_common.c:294) ==2511392==by 0x48EEE29: pthread_cond_signal@@GLIBC_2.3.2 (pthread_cond_signal.c:77) ==2511392==by 0x4848FB8: pthread_cond_signal_WRK (hg_intercepts.c:1570) ==2511392==by 0x10928B: f (in /net/inria/home/sthibault/test) ==2511392==by 0x484B966: mythread_wrapper (hg_intercepts.c:406) ==2511392==by 0x48EFFD3: start_thread (pthread_create.c:442) ==2511392==by 0x496F8CF: clone (clone.S:100) ==2511392== ==2511392== This conflicts with a previous read of size 8 by thread #1 ==2511392== Locks held: none ==2511392==at 0x48EF39E: __atomic_wide_counter_load_relaxed (atomic_wide_counter.h:30) ==2511392==by 0x48EF39E: __condvar_load_g1_start_relaxed (pthread_cond_common.c:46) ==2511392==by 0x48EF39E: __pthread_cond_wait_common (pthread_cond_wait.c:486) ==2511392==by 0x48EF39E: pthread_cond_wait@@GLIBC_2.3.2 (pthread_cond_wait.c:618) ==2511392==by 0x484BB03: pthread_cond_wait_WRK (hg_intercepts.c:1291) ==2511392==by 0x10933B: main (in /net/inria/home/sthibault/test) ==2511392== Address 0x10c0e8 is 8 bytes inside data symbol "cond" ==2511392== ==2511392== ==2511392== ==2511392== Possible data race during write of size 4 at 0x10C128 by thread #2 ==2511392== Locks held: none ==2511392==at 0x48F4A47: __pthread_mutex_unlock_usercnt (pthread_mutex_unlock.c:62) ==2511392==by 0x4848DD8: mutex_unlock_WRK (hg_intercepts.c:1184) ==2511392==by 0x10929A: f (in /net/inria/home/sthibault/test) ==2511392==by 0x484B966: mythread_wrapper (hg_intercepts.c:406) ==2511392==by 0x48EFFD3: start_thread (pthread_create.c:442) ==2511392==by 0x496F8CF: clone (clone.S:100) ==2511392== ==251139
[valgrind] [Bug 327548] false positive while destroying mutex
https://bugs.kde.org/show_bug.cgi?id=327548 --- Comment #8 from Samuel Thibault --- (with the various versions of valgrind between 3.9 and 3.19) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 327548] false positive while destroying mutex
https://bugs.kde.org/show_bug.cgi?id=327548 Samuel Thibault changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #7 from Samuel Thibault --- To provide various datapoints, I have tried it valgrind --tool=helgrind ./test on: - Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz - Intel(R) Xeon(R) Gold 6140 CPU @ 2.30GHz - Intel(R) Xeon(R) CPU E5-2650L v4 @ 1.70GHz - AMD EPYC 7352 24-Core Processor - AMD EPYC 7502 32-Core Processor with glibc 2.35 I got the hit ==420467== Helgrind, a thread error detector ==420467== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al. ==420467== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info ==420467== Command: ./test ==420467== ==420467== ---Thread-Announcement-- ==420467== ==420467== Thread #1 is the program's root thread ==420467== ==420467== ---Thread-Announcement-- ==420467== ==420467== Thread #2 was created ==420467==at 0x49792FF: clone (clone.S:76) ==420467==by 0x497A146: __clone_internal (clone-internal.c:83) ==420467==by 0x48F6484: create_thread (pthread_create.c:295) ==420467==by 0x48F6F78: pthread_create@@GLIBC_2.34 (pthread_create.c:828) ==420467==by 0x484E5D7: ??? (in /usr/libexec/valgrind/vgpreload_helgrind-amd64-linux.so) ==420467==by 0x1092DA: main (in /net/inria/home/sthibault/test) ==420467== ==420467== ==420467== ==420467== Possible data race during read of size 1 at 0x10C128 by thread #1 ==420467== Locks held: none ==420467==at 0x484B225: ??? (in /usr/libexec/valgrind/vgpreload_helgrind-amd64-linux.so) ==420467==by 0x484B4CA: ??? (in /usr/libexec/valgrind/vgpreload_helgrind-amd64-linux.so) ==420467==by 0x10937C: main (in /net/inria/home/sthibault/test) ==420467== ==420467== This conflicts with a previous write of size 4 by thread #2 ==420467== Locks held: none ==420467==at 0x48FB4D8: __pthread_mutex_unlock_usercnt (pthread_mutex_unlock.c:62) ==420467==by 0x484BCE8: ??? (in /usr/libexec/valgrind/vgpreload_helgrind-amd64-linux.so) ==420467==by 0x10929A: f (in /net/inria/home/sthibault/test) ==420467==by 0x484E7D6: ??? (in /usr/libexec/valgrind/vgpreload_helgrind-amd64-linux.so) ==420467==by 0x48F6849: start_thread (pthread_create.c:442) ==420467==by 0x497930F: clone (clone.S:100) ==420467== Address 0x10c128 is 8 bytes inside data symbol "mutex" ==420467== immediately on almost all of them, only AMD EPYC 7352 24-Core Processor took 1m to reproduce. On an AMD Opteron(tm) Processor 6174 with glibc 2.28 I couldn't reproduce it within an hour. On a Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz, I tried with various glibcs: 2.19, 2.24, 2.28, 2.31, 2.36, with all versions it happens within half an hour, sometimes within a minute. On an arm64 with glibc 2.36 it appeared immediately On a mips64el Cavium Octeon III V0.2 FPU V0.0 with glibc 2.36 it appeared immediately On a ppc64el POWER8 with glibc 2.36 it appeared within a minute. On an s390x it appeared in 8 minutes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450914] Wayland, games on Nvidia are force vsynced
https://bugs.kde.org/show_bug.cgi?id=450914 --- Comment #35 from Samuel --- Here is the NVIDIA Developer forum link for this bug : https://forums.developer.nvidia.com/t/nvidia-bug-kde-wayland-games-are-force-vsynced/237880 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450914] Wayland, games on Nvidia are force vsynced
https://bugs.kde.org/show_bug.cgi?id=450914 --- Comment #34 from Samuel --- Here is the latest news on this bug:- "Hi, I’m currently working on a driver-side change that should resolve the forced vsync issue, as well as enable direct scan-out for eligible Xwayland applications. Work on Gamma LUT support is also in progress. The implementation is currently under internal code-review." - Erik Kurzinger -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450914] Wayland, games on Nvidia are force vsynced
https://bugs.kde.org/show_bug.cgi?id=450914 --- Comment #32 from Samuel --- (In reply to Erik Kurzinger from comment #25) > It should be pretty easy to fix, but that will need to be in an > upcoming driver release. I updated to latest stable NVIDIA proprietary driver version - 525.60.11 and the VSync is still forced in games in fullscreen and borderless modes in Plasma. Any fix for this in future? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 463027] New: broken check for MPX instruction support in assembler
https://bugs.kde.org/show_bug.cgi?id=463027 Bug ID: 463027 Summary: broken check for MPX instruction support in assembler Classification: Developer tools Product: valgrind Version: 3.21 GIT Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: naes...@gmail.com Target Milestone: --- SUMMARY There is a syntax error in the "if amd64 assembler knows the MPX instructions" check. The assembler never gets to see it. STEPS TO REPRODUCE 1. On amd64, follow the build instructions from README, up through step 4 OBSERVED RESULT The configure output includes the line: checking if amd64 assembler knows the MPX instructions... no EXPECTED RESULT With a sufficiently-new assembler, it should instead be: checking if amd64 assembler knows the MPX instructions... yes SOFTWARE/OS VERSIONS gcc (Debian 10.2.1-6) 10.2.1 20210110 GNU assembler (GNU Binutils for Debian) 2.35.2 ADDITIONAL INFORMATION The relevant portion of config.log is: configure:12750: checking if amd64 assembler knows the MPX instructions configure:12773: gcc -c conftest.c >&5 conftest.c: In function 'main': conftest.c:51:11: error: expected ':' or ')' before 'bnd' 51 | bnd jmp end\n" | ^~~ conftest.c:51:23: error: stray '\' in program 51 | bnd jmp end\n" | ^ conftest.c:51:25: warning: missing terminating " character 51 | bnd jmp end\n" | ^ conftest.c:51:25: error: missing terminating " character conftest.c:52:23: error: stray '\' in program 52 | foo: bnd ret\n" | ^ conftest.c:52:25: warning: missing terminating " character 52 | foo: bnd ret\n" | ^ conftest.c:52:25: error: missing terminating " character conftest.c:53:19: warning: missing terminating " character 53 | end: nop"); | ^ conftest.c:53:19: error: missing terminating " character 53 | end: nop"); | ^~~ configure:12773: $? = 1 However, it's actually just missing some starting " characters. See attached patch. The test even passes! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462343] Don't show runtimes in the UI
https://bugs.kde.org/show_bug.cgi?id=462343 --- Comment #6 from Samuel Reddy --- Discover has a way of sorting programs by apps, system or addons in the updates category. Would it be possible to do the same with the installed category? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462343] Discover should show only appstream programs
https://bugs.kde.org/show_bug.cgi?id=462343 --- Comment #4 from Samuel Reddy --- Also steam-devices -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462343] Discover should show only appstream programs
https://bugs.kde.org/show_bug.cgi?id=462343 --- Comment #3 from Samuel Reddy --- (In reply to Aleix Pol from comment #2) > can you be more specific about which packages you think they don't fit? An example is Gstreamer Multimedia Codecs for native packages I think that "system" programs like KDE Plasma Desktop packages, flatpak runtimes and snap runtimes should be sorted into a system category like GNOME Software, which would be a good compromise between user friendliness and being powerful when needed -- You are receiving this mail because: You are watching all bug changes.
