[kmail2] [Bug 420433] New: Clone identity
https://bugs.kde.org/show_bug.cgi?id=420433 Bug ID: 420433 Summary: Clone identity Product: kmail2 Version: Git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sotadic_rest...@simplelogin.co Target Milestone: --- Kmail already offers some options like modify, delete and rename, but it's still not possible to clone an existing identity. That would be very helpful. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 5.6.6 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420433] Clone identity
https://bugs.kde.org/show_bug.cgi?id=420433 --- Comment #1 from Parker --- A screenshot of the current options https://i.imgur.com/ReTcDUc.png -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416181] Allow selecting different locale for each identity / account
https://bugs.kde.org/show_bug.cgi?id=416181 Parker changed: What|Removed |Added CC||sotadic_restage@simplelogin ||.co --- Comment #1 from Parker --- up -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420433] Clone identity
https://bugs.kde.org/show_bug.cgi?id=420433 Parker changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Parker --- I just realized that this option appears when creating a new identity. sorry -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381579] add and handle Openpgp header
https://bugs.kde.org/show_bug.cgi?id=381579 Parker changed: What|Removed |Added CC||sotadic_restage@simplelogin ||.co --- Comment #1 from Parker --- Autocrypt does that. It hasn't been implemented in kmail yet. https://bugs.kde.org/show_bug.cgi?id=388036 Maybe this is a duplicate bug? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420434] New: Change only body font size
https://bugs.kde.org/show_bug.cgi?id=420434 Bug ID: 420434 Summary: Change only body font size Product: kmail2 Version: Git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: sotadic_rest...@simplelogin.co Target Milestone: --- SUMMARY Changing the font size of the mail body also changes the header font. OBSERVED RESULT I changed the default font size of kmail because I think the default size is too small (at least on my monitor) but I would like this change to only apply to the message body and not the header. As some email addresses can be very large, or there can be a lot of recipients, this becomes a mess and takes up almost every piece of screen available See this screenshot: https://i.imgur.com/djDh9nt.png EXPECTED RESULT Ideally, it would be possible to edit the font size individually for each of the two separately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 5.6.6 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420436] New: Modify header section
https://bugs.kde.org/show_bug.cgi?id=420436 Bug ID: 420436 Summary: Modify header section Product: kmail2 Version: Git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: sotadic_rest...@simplelogin.co Target Milestone: --- SUMMARY Kmail already has many options to customize the interface and that's amazing! But there's almost nothing to customize the part where the basic headers of an email are displayed, like sender, recipient, subject, etc. Options to change which items should be displayed, list all headers, see the source of the email, would be very useful. Another necessary modification would be the possibility to move the reply buttons, forward, and other useful ones to that same place. In my opinion it makes more sense that these buttons stay in the header. Currently, they only stay on the top menu and you can move it to one of the sides or keep it "floating". Something like what I tried to do in this image: https://i.imgur.com/etvJlxE.png SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 5.6.6 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 Parker changed: What|Removed |Added CC||sotadic_restage@simplelogin ||.co --- Comment #26 from Parker --- @Laurent Montel, you seem to keep developing kmail as a karma you've acquired. Why don't you give it up and get on with your life? Let someone else who really has an interest and passion for what you do take care of it. You treat people as inferior and disagree with all your opinions. I don't think the KDE community can be contaminated with toxic people like you. Btw, I've never seen any KDE application have so many bugs and not work like KMail. KDE really needs an e-mail client. I don't understand how this is not prioritized. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 --- Comment #28 from Parker --- Do that. Kick me out for telling the truth. It's good to know how things work around here. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 --- Comment #32 from Parker --- "[...] that are maintained by a single developer 365 days each year." Did you realize you just agreed with what I said earlier? He works alone because the people who try to help him can't. If you want everything to be done your way, you don't have patience with those who are learning and you think you're right about everything, so there's no surprise if you work alone. This isn't just about lines of code, it's also about the person you are. Treating people who come here to make a suggestion or report a bug well is essential and necessary. KMail has a lot of bugs and a lot of things don't work, but that doesn't mean it's dead. It just needs to be more open to contributions. If that's done, other people will contribute. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 417895] New: Current music on radio
https://bugs.kde.org/show_bug.cgi?id=417895 Bug ID: 417895 Summary: Current music on radio Product: elisa Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: bugs-...@comunidadelinux.com Target Milestone: --- I listen to a lot of radios and some of them tell me the name of the song and the band that is playing at the moment, but Elisa doesn't recognize this. See these two screenshots of Elisa (1) and Yarock (2) on the same radio: 1. https://i.imgur.com/YrYmt6k.png 2. https://i.imgur.com/vyfcAVg.png -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 417895] Current music on radio
https://bugs.kde.org/show_bug.cgi?id=417895 --- Comment #2 from Parker --- (In reply to Alexander Stippich from comment #1) > Is this with git master? This one https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/elisa -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 417945] New: Audio problem
https://bugs.kde.org/show_bug.cgi?id=417945 Bug ID: 417945 Summary: Audio problem Product: elisa Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: bugs-...@comunidadelinux.com Target Milestone: --- SUMMARY What happens is that the audio played from a live link of a radio transmitted via HLS is "cutting". I don't know the correct word for it, so I uploaded a video showing the bug. https://cloud.disroot.org/s/NizX72iyBoRypne In the video, I used mpv to play the same radio to show that the link works without problems in another program Another thing that happens is that the play/pause button stops working and I can't get to the radio, I have to close the program. STEPS TO REPRODUCE 1. Add a radio with an url like this: https://medias.sgr.globo.com/hls/aRGloboRJ/aRGloboRJ.m3u8 2. Play This also happens with other links from other radios, like this one http://server01.ouvir.radio.br:8050/stream?1582044253100 SOFTWARE/OS VERSIONS Linux: 5.5.4-arch1-1 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 417945] Audio problem
https://bugs.kde.org/show_bug.cgi?id=417945 --- Comment #1 from Parker --- The older link seems have no audio, use this one: https://cloud.disroot.org/s/awcNELgcXW9oMbG While trying to record another video showing the error I realized that sometimes it reproduces without any problem. But most of the time the problem still remains. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416403] During account wizard using @protonmail.com, get "Kmail could not convert value of setting 'Authentication' to required type"
https://bugs.kde.org/show_bug.cgi?id=416403 --- Comment #12 from Parker --- so, that's it? is the end of kmail? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416403] During account wizard using @protonmail.com, get "Kmail could not convert value of setting 'Authentication' to required type"
https://bugs.kde.org/show_bug.cgi?id=416403 --- Comment #19 from Parker --- The current workaround is add the account manually. It's finally worked for me. Settings -> Configure the Kmail In accounts, add an identity, configure your IMAP/POP3/other server in the receiving tab (press "Add" button and choose "Another account") and then configure SMTP on the sending tab. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 54212] freeze and export items
https://bugs.kde.org/show_bug.cgi?id=54212 Parker changed: What|Removed |Added CC||bugs-...@comunidadelinux.co ||m --- Comment #37 from Parker --- wow! a 2002 bug and no progress -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419551] New: pop up audio notifications
https://bugs.kde.org/show_bug.cgi?id=419551 Bug ID: 419551 Summary: pop up audio notifications Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: sotadic_rest...@simplelogin.co CC: plasma-b...@kde.org Target Milestone: 1.0 The pop up that is displayed when the volume is changed should be less intrusive. It appears in the middle of the screen and is very large. https://upload.vaa.red/2a7VCB#8Uqi3kasG0TOETevKtBuMoVc8kbK2ti0 Changing the audio output also generates another pop up in the same place and of the same size. To change these two settings more often, this is very disturbing, especially when watching a movie or series. Why is it not displayed as a native plasma notification or as a smaller and more discreet pop up, like on the edge of the screen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 504879] Colors have weird horizontal bands.
https://bugs.kde.org/show_bug.cgi?id=504879 --- Comment #3 from parker --- (In reply to animtim from comment #2) > I see the file you attached uses the color model XYZ/Alpha, instead of the > default RGB/Alpha. This is the cause of your problem. > In the "Create new document" dialog, select color model RGB/Alpha, with the > default depth 8-bit integer/channel, and the default profile > sRGB-elle-V2-srgbtrc.icc, and press create. The last setting used there is > saved for next new documents, until you change it. this fixed it, thank you! apologies for bothering -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 504879] Colors have weird horizontal bands.
https://bugs.kde.org/show_bug.cgi?id=504879 --- Comment #1 from parker --- Created attachment 181788 --> https://bugs.kde.org/attachment.cgi?id=181788&action=edit Krita file with the problem of the color gradient -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 504879] New: Colors have weird horizontal bands.
https://bugs.kde.org/show_bug.cgi?id=504879 Bug ID: 504879 Summary: Colors have weird horizontal bands. Classification: Applications Product: krita Version First 5.2.9 Reported In: Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: beetlear...@gmail.com Target Milestone: --- SUMMARY I opened my program like always but the color selector has this weird horizontal bands, I tried deleting and reinstalling the program but nothing changed. I also tried searching for help and I can't seem to find an answer or a replica of this problem. STEPS TO REPRODUCE 1. There are weird horizontal bands in the color selector 2. I expected to close and open program for the colors to be back to normal 3. The only result I could do was delete and reinstall and expect the problem to fix itself OBSERVED RESULT The color it picks has nothing to do with the ones i choose EXPECTED RESULT I expected the color selector to have the normal gradient. SOFTWARE/OS VERSIONS Windows: 11 ADDITIONAL INFORMATION I opened a file from a drawing I made before the problem started and the selector works like normal, it only happens when I open new files -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466633] Black lines or bands flickered horizontally when using Plasma 5.27.1 on Wayland with nomodeset on the kernel command line in VMs
https://bugs.kde.org/show_bug.cgi?id=466633 parker changed: What|Removed |Added CC||beetlear...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466203] New: [Android] Crash upon launch
https://bugs.kde.org/show_bug.cgi?id=466203 Bug ID: 466203 Summary: [Android] Crash upon launch Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- Created attachment 156575 --> https://bugs.kde.org/attachment.cgi?id=156575&action=edit logcat SUMMARY Nightly commit 3aeb18b37e2a619448972ae4d0e481200349c51f Crashes on Android 13 shortly after splash appears STEPS TO REPRODUCE 1. Install nightly 2. Launch OBSERVED RESULT EXPECTED RESULT 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.
[krita] [Bug 466203] [Android] Crash upon launch
https://bugs.kde.org/show_bug.cgi?id=466203 --- Comment #1 from Parker Reed --- Created attachment 156576 --> https://bugs.kde.org/attachment.cgi?id=156576&action=edit Tombstone Tombstone from the crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466203] [Android] Crash upon launch
https://bugs.kde.org/show_bug.cgi?id=466203 --- Comment #2 from Parker Reed --- Created attachment 156577 --> https://bugs.kde.org/attachment.cgi?id=156577&action=edit Extra Tombstone PB -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 455692] ** Removed for violation of community policy **
https://bugs.kde.org/show_bug.cgi?id=455692 Amily Parker changed: What|Removed |Added URL|https://myassignmenthelp.co |https://myassignmenthelp.co |m/page-calculator.php |m/uk/english-homework-help. ||html CC||amilyparke...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 455692] ** Removed for violation of community policy **
https://bugs.kde.org/show_bug.cgi?id=455692 --- Comment #2 from Amily Parker --- 6 Hints to Compose Selective Data Innovation Tasks Frequently, understudies recruit data innovation task assist administrations with completing their tasks on time and securing passing marks. However, do you have any idea that you can compose it all alone, assuming you follow a couple of straightforward tips? We have assembled a few experiences from the specialists who offer data cheap dissertation help administrations around the world. Today, this blog will share a couple of tips to form a great data innovation task. In this way, here are the tips. We should see - 1.Understand the inquiry Remember that data innovation is a specialized subject, so ensure you are in the right temper to have the option to reasonably tackle the inquiry before you start dealing with the undertaking. Specialists who proposition top zara case study swot analysis solution administrations online concur with this. 2.Start early Beginning your occupation promptly is an incredible methodology for composing a business report writing. Since the majority of these tasks have due dates, you ought to begin working rapidly. Besides the fact that missing a cutoff time result in can horrible scores, yet it will likewise show an absence of subject skill. 3.Do your examination For your data innovation task, accumulate an adequate number of information and sources to assist you with understanding the substance that should be given. To be completely ready and appreciate the inquiry, read books, and peruse existing arrangements, papers, and diaries on the data innovation issue. You can likewise recruit proficient IT task assist administrations with completing your responsibility rapidly. 4.Keep it basic Hold your reaction to the data innovation task brief. Rather than utilizing muddled jargon, write in plain, conceivable English liberated from language. Moreover, join hypothesis and applications so the educator can see that you can put speculations to use in a true setting. At long last, work on an answer that fittingly fulfills the data innovation task since your point depends on a true situation. 5.Provide bit by bit arrangement You should move toward a data innovation task with a sensible and scientific mentality. Since this is a specialized subject, your task ought to likewise be founded on rationale. Your data innovation task ought to incorporate coherent clarifications and bit by bit replies. The task ought to be logical on the grounds that the subject is one science. 6.Edit and edited Continuously audit your English homework help prior to submitting it and make the required alterations to forestall blunders. Last Considerations, Presently you are set to make a faultless data innovation task. In this way, execute the tips referenced above and go for it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470531] New: [Android] SDLAudioManager crash
https://bugs.kde.org/show_bug.cgi?id=470531 Bug ID: 470531 Summary: [Android] SDLAudioManager crash Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- SUMMARY Latest nightly crashing on Android 13 STEPS TO REPRODUCE 1. Install update 2. Application crash upon launch OBSERVED RESULT Applications crashes EXPECTED RESULT Application no crashes SOFTWARE/OS VERSIONS Android 13 Samsung Tab S8+ ADDITIONAL INFORMATION 06-01 12:54:03.216 9738 9738 E org.krita.next: - class 'Lorg/libsdl/app/SDLAudioManager;' cl=0x12c77468 - 06-01 12:54:03.216 9738 9738 E org.krita.next: objectSize=228 (224 from super) 06-01 12:54:03.216 9738 9738 E org.krita.next: access=0x.0001 06-01 12:54:03.216 9738 9738 E org.krita.next: super='java.lang.Class' (cl=0x0) 06-01 12:54:03.216 9738 9738 E org.krita.next: vtable (0 entries, 11 in super): 06-01 12:54:03.216 9738 9738 E org.krita.next: direct methods (4 entries): 06-01 12:54:03.216 9738 9738 E org.krita.next: 0: void org.libsdl.app.SDLAudioManager.() 06-01 12:54:03.216 9738 9738 E org.krita.next: 1: void org.libsdl.app.SDLAudioManager.addAudioDevice(boolean, int) 06-01 12:54:03.216 9738 9738 E org.krita.next: 2: int org.libsdl.app.SDLAudioManager.nativeSetupJNI() 06-01 12:54:03.216 9738 9738 E org.krita.next: 3: void org.libsdl.app.SDLAudioManager.removeAudioDevice(boolean, int) 06-01 12:54:03.216 9738 9738 E org.krita.next: static fields (1 entries): 06-01 12:54:03.216 9738 9738 E org.krita.next: 0: org.libsdl.app.SDLAudioManager$1 org.libsdl.app.SDLAudioManager.mAudioDeviceCallback 06-01 12:54:03.216 9738 9738 E org.krita.next: Failed to register native method org.libsdl.app.SDLAudioManager.nativePermissionResult(IZ)V in base.apk 06-01 12:54:03.216 9738 9738 E SDL : Failed to register methods of org/libsdl/app/SDLAudioManager -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470531] [Android] SDLAudioManager crash
https://bugs.kde.org/show_bug.cgi?id=470531 --- Comment #1 from Parker Reed --- Likely related to the commit adding audio for animations bfc5402d8798cf37c5941633fbfdad3a960dfb57 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470531] [Android] SDLAudioManager crash
https://bugs.kde.org/show_bug.cgi?id=470531 Parker Reed changed: What|Removed |Added Latest Commit||2ceec081587284d7d5eae5d5039 ||4084a111a21ff -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] New: [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 Bug ID: 470761 Summary: [Android] Crash upon opening canvas Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- Created attachment 159525 --> https://bugs.kde.org/attachment.cgi?id=159525&action=edit WindowManager lines from logcat SUMMARY Application crashes any time the canvas is brought up (new file or opening existing) STEPS TO REPRODUCE 1. Load Krita Nightly 2. New file 3. Create OBSERVED RESULT Application crashes upon creating canvas EXPECTED RESULT Canvas to be created SOFTWARE/OS VERSIONS Samsung Tab S8+ Android 13 ADDITIONAL INFORMATION Log attached -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 Parker Reed changed: What|Removed |Added Latest Commit||e7bf1f0d299c4f7c6529438059d ||14e7a99907066 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 --- Comment #2 from Parker Reed --- (In reply to Halla Rempt from comment #1) > Sharaf, the android maintainer, is having exams, so this'll take some time. > The attached log doesn't show anything happening inside Krita, though. After taking another look I was able to get better logcat output and found the tombstone that was created. Attaching files -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 --- Comment #3 from Parker Reed --- Created attachment 159545 --> https://bugs.kde.org/attachment.cgi?id=159545&action=edit logcat of application dump -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 --- Comment #4 from Parker Reed --- Created attachment 159546 --> https://bugs.kde.org/attachment.cgi?id=159546&action=edit tombstone -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 --- Comment #5 from Parker Reed --- Created attachment 159547 --> https://bugs.kde.org/attachment.cgi?id=159547&action=edit tombstone pb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 --- Comment #7 from Parker Reed --- Look like this was fixed as of the past handful of commits! Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488813] New: Shake cursor inoperable with animation speed set to instant
https://bugs.kde.org/show_bug.cgi?id=488813 Bug ID: 488813 Summary: Shake cursor inoperable with animation speed set to instant Classification: Plasma Product: kwin Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY With animation speed set to instant, shake cursor does not work. STEPS TO REPRODUCE 1. Set animations to instant 2. Enable Shake Cursor under accessibility 3. Try to shake cursor OBSERVED RESULT Cursor stays the same size EXPECTED RESULT Cursor to inflate when shaken SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.8.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488813] Shake cursor inoperable with animation speed set to instant
https://bugs.kde.org/show_bug.cgi?id=488813 --- Comment #1 from Parker Reed --- Subsequently the cursor size changing is entirely dependent on animation speed. If you have it set really low, it takes a long time to inflate and deflate. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481979] No audio and video play in information panel (After upgrade to qt6 and plasma6)
https://bugs.kde.org/show_bug.cgi?id=481979 --- Comment #6 from Alex Parker --- (In reply to Nicolas Fella from comment #3) > Please update KDE Neon and test again. There was an issue with some phonon > backend packages missing that should be fixed now Update one hour ago my kde neon and now all play-preview on info panel in Dolphin works as expected (as before this bug introduced). Thanks very much to developers! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 481967] Activating Calculator with a global shortcut fails to pass focus to it (only works when clicking on it to activate it)
https://bugs.kde.org/show_bug.cgi?id=481967 --- Comment #3 from Alex Parker --- (In reply to Nate Graham from comment #2) > Ah, it looks like we only fixed it for when the Calculator is clicked on, > not when it's activated with a keyboard shortcut. Strange that those have > different codepaths. Thank you for widget, Nate. Using it every day. Before this feature would be released, if somebody has same trouble — I've found temporary workaround. After activating calculator widget with hotkey, user can simply press Tab key — so widget getting focus on "C" button, and user can input any data. So, in my case, I use combo "Win+K, Tab" and widget works as I'm expecting. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 482341] New: Error when open Discover: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)
https://bugs.kde.org/show_bug.cgi?id=482341 Bug ID: 482341 Summary: Error when open Discover: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg) Classification: Applications Product: Discover Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: someanonymousema...@mail.ru CC: aleix...@kde.org Target Milestone: --- SUMMARY "W: file:/var/lib/preinstalled-pool/dists/jammy/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details." Such window raising every time I've open Discover. That's started after last update today. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 482341] Error when open Discover: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)
https://bugs.kde.org/show_bug.cgi?id=482341 --- Comment #1 from Alex Parker --- (In reply to Alex Parker from comment #0) One note: On Ubuntu Jammy I've resolved such issue when I've moved all software gpg keys into /etc/apt/keyrings (and have edited corresponding .list files). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 Alex Parker changed: What|Removed |Added CC||someanonymousema...@mail.ru --- Comment #11 from Alex Parker --- (In reply to Rich Johnson from comment #10) > https://bugs.kde.org/show_bug.cgi?id=481940#c2 <-- this will fix krunner > for you too. Thanks to Duha on discuss.kde.org for helping! Yeah, it works now after applying actions you've recommended. Thanks to Duha and you! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481979] New: No audio and video play in information panel (After upgrade to qt6 and plasma6)
https://bugs.kde.org/show_bug.cgi?id=481979 Bug ID: 481979 Summary: No audio and video play in information panel (After upgrade to qt6 and plasma6) Classification: Applications Product: dolphin Version: 24.02.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: someanonymousema...@mail.ru CC: kfm-de...@kde.org Target Milestone: --- SUMMARY After yesterday big update to plasma6 there is no more audio and video play preview at information panel. STEPS TO REPRODUCE 1. Update to latest kde neon 2. Choose mp3 or mp4 file in Dolphin and try to click play button at info side-panel 3. Nothing happens, and timeline control in preview area are grayed (like «function inaccessible for now») EXPECTED RESULT Play of audio/video file in small preview area in info panel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon Latest KDE Plasma Version: 6 KDE Frameworks Version: 6 Qt Version: 6 ADDITIONAL INFORMATION When start Dolphin from Konsole, I've got many lines of warnings like this: ``` kf.kio.core: An error occurred during write. The worker terminates now. WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to EmbeddedVideoPlayer ( no objectName ). WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::AudioOutput ( no objectName ). ``` Those messages generated when I've clicked on audio or video files in directory. Before yesterday big update all worked fine. Maybe, during update, when Discover audo-deleted 2-3 dozens of packages — it didn't install package or plugin for this function of media-preview? Maybe I need to install something else? I've installed manually `pkcon install phonon-backend-gstreamer` but nothing changed, it didn't help. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 486127] New: Unable to drag scrollbar with mouse
https://bugs.kde.org/show_bug.cgi?id=486127 Bug ID: 486127 Summary: Unable to drag scrollbar with mouse Classification: Applications Product: NeoChat Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: parker.l.r...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Scrollbar handle pops to the left when scrolling, seemingly so you can drag it. As soon as you mouse over it, it collapses to the right making it impossible to drag. STEPS TO REPRODUCE 1. Go to any chat list 2. Try dragging the scrollbar OBSERVED RESULT Handle avoids the mouse making it impossible to drag EXPECTED RESULT Being able to drag the scrollbar handle SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484492] New: Plasma Wayland fails to initialize Display Stream Compression
https://bugs.kde.org/show_bug.cgi?id=484492 Bug ID: 484492 Summary: Plasma Wayland fails to initialize Display Stream Compression Classification: Plasma Product: kwin Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- SUMMARY Hardware: Steam Deck/ROG Ally Dock : Dell WD-19S Monitors: 3 Lenovo Q27q-10 1440p 75 Hz With all three monitors connected (MST and Display Stream Compression) Plasma X11 can output to all three at their native 1440p 75 Hz. When running Plasma Wayland, it's either * 2 1440 75 Hz and the third monitor never initializes video (Does however show up to KScreen) * 1 1440 75 Hz and 2 1080 60 Hz (As if Display Stream Compression wasn't even working to begin with) I have confirmed on Gnome Wayland Mutter that all three monitors do work at their native resolution for Wayland. STEPS TO REPRODUCE 1. Plug in monitors 2. Go to Display Settings 3. Try to configure all three at native reosolution OBSERVED RESULT Acts like DSC isn't available and either 2 work or 3 work at reduced resolution. EXPECTED RESULT All three to work at native resolution (As they do in Gnome) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 24.0.2 Qt Version: 6.6.2 ADDITIONAL INFORMATION Dmesg from ROG Ally https://gist.github.com/parkerlreed/10da3f1ff55340c5b1f317948ee8f7ac Journalctl (kernel + plasma) from Steam Deck https://gist.github.com/parkerlreed/0b153848d2513d0ad7d8d8696aeffe2f amdgpu thread https://gitlab.freedesktop.org/drm/amd/-/issues/3278 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484492] Plasma Wayland fails to initialize Display Stream Compression
https://bugs.kde.org/show_bug.cgi?id=484492 --- Comment #1 from Parker Reed --- Additional note: Inoperability with Wayland was present on 5.27 as well going back quite a ways. So this isn't new to Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484492] Plasma Wayland fails to initialize Display Stream Compression
https://bugs.kde.org/show_bug.cgi?id=484492 --- Comment #2 from Parker Reed --- Just tried enabling 2 1440 75 and 1 1080 60 and got this on kernel messages [ 717.144654] amdgpu :09:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:264 [ 717.351967] [drm] Send DSC enable to synaptics Waiting for the monitor and it's just slow enough to be past the timeout? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484492] Plasma Wayland fails to initialize Display Stream Compression
https://bugs.kde.org/show_bug.cgi?id=484492 --- Comment #4 from Parker Reed --- Oh my. Thank you! Is there an existing bug triage for this I can follow? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 484200] New: Segfault when closing child color picker dialog with no parents
https://bugs.kde.org/show_bug.cgi?id=484200 Bug ID: 484200 Summary: Segfault when closing child color picker dialog with no parents Classification: Applications Product: konsole Version: 24.02.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- Created attachment 167584 --> https://bugs.kde.org/attachment.cgi?id=167584&action=edit backtrace SUMMARY Editing any of the current profile's colors, closing the parent windows, and then closing the color picker causes a crash STEPS TO REPRODUCE 1. Edit Current Profile 2. Appearance 3. Edit 4. Click a color 5. Close Edit Color Scheme and Edit Profile via the titlebar (Window buttons are properly blocked) 6. Close the child Color Picker dialog OBSERVED RESULT Konsole crashes EXPECTED RESULT Color Picker closing (or the Edit Color Scheme/Edit Profile titlebar exit buttons being blocked if the Color Picker is open) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Attached backtrace -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 484200] Segfault when closing child color picker dialog with no parents
https://bugs.kde.org/show_bug.cgi?id=484200 --- Comment #2 from Parker Reed --- The steps as I posted them should replicate it. When you go into the edit color scheme dialog and click on any of the colors like foreground or background and leave that resulting color picker dialog open and close the schemes and profile, proceeding to close the color picker will crash the entire application. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475574] [Wayland] Unable to bind keys with keycodes above 255
https://bugs.kde.org/show_bug.cgi?id=475574 Parker Reed changed: What|Removed |Added CC||parker.l.r...@gmail.com --- Comment #1 from Parker Reed --- Seeing same thing here with Chromecast remote. Half of the buttons are way above 255 and won't map in KWin. Event: time 1706641635.753398, -- SYN_REPORT Event: time 1706641641.873435, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0089 Event: time 1706641641.873435, type 1 (EV_KEY), code 377 (KEY_TV), value 1 Event: time 1706641641.873435, -- SYN_REPORT Event: time 1706641642.013353, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0089 Event: time 1706641642.013353, type 1 (EV_KEY), code 377 (KEY_TV), value 0 Event: time 1706641642.013353, -- SYN_REPORT Event: time 1706641643.873390, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0078 Event: time 1706641643.873390, type 1 (EV_KEY), code 589 (?), value 1 Event: time 1706641643.873390, -- SYN_REPORT Event: time 1706641643.973367, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0078 Event: time 1706641643.973367, type 1 (EV_KEY), code 589 (?), value 0 Event: time 1706641643.973367, -- SYN_REPORT Event: time 1706641644.453419, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0077 Event: time 1706641644.453419, type 1 (EV_KEY), code 588 (?), value 1 Event: time 1706641644.453419, -- SYN_REPORT Event: time 1706641644.533424, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0077 Event: time 1706641644.533424, type 1 (EV_KEY), code 588 (?), value 0 Event: time 1706641644.533424, -- SYN_REPORT Event: time 1706641645.313474, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0041 Event: time 1706641645.313474, type 1 (EV_KEY), code 353 (KEY_SELECT), value 1 Event: time 1706641645.313474, -- SYN_REPORT Event: time 1706641645.453442, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0041 Event: time 1706641645.453442, type 1 (EV_KEY), code 353 (KEY_SELECT), value 0 Event: time 1706641645.453442, -- SYN_REPORT -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475574] [Wayland] Unable to bind keys with keycodes above 255
https://bugs.kde.org/show_bug.cgi?id=475574 --- Comment #4 from Parker Reed --- These keys are defined in evdev and I can use them perfectly remapping them to other keys so this shouldn't be an issue. https://github.com/philipl/evdevremapkeys/commit/e5f251720c470f047549b59acff16ef701e28120 devices: - input_name: 'Chromecast Remote' output_name: remap-kbd remappings: KEY_SELECT: - KEY_ENTER 588: - KEY_PHONE KEY_SCREENLOCK: - KEY_POWER KEY_TV: - KEY_LEFTALT - KEY_F4 589: - KEY_MEDIA KEY_BACK: - KEY_BACKSPACE KEY_HOMEPAGE: - KEY_LEFTMETA -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451591] New: [kwin/display configuration] Multiple monitors with same name cause unintentional behavior
https://bugs.kde.org/show_bug.cgi?id=451591 Bug ID: 451591 Summary: [kwin/display configuration] Multiple monitors with same name cause unintentional behavior Product: kwin Version: 5.24.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: xrandr Assignee: kwin-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- Created attachment 147533 --> https://bugs.kde.org/attachment.cgi?id=147533&action=edit Screenshot of fixed result 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 using more than one display with the same EDID name and multiple different rotations, display configuration will apply your changes but instantly think a change was made so there are TWO apply steps. Due to a hardware issue, sometimes my displays reconnect and the portrait rotation from the right monitor is applied to the left making the left upside down. I have to go in each time and reapply the rotation, apply twice, and then close out. Confirmed on two different AMD GPU systems with the same monitor layout (One HDMI and two Displayport) My fix was to create a specific EDID for each of the portrait monitors with their own name. Image attached showing the result of the fix. STEPS TO REPRODUCE 1. Have three monitors 2. Arrange in one landscape, one portrait, and one reverse portrait 3. Rotation applied incorrectly to one of the portrait montiors OBSERVED RESULT On display reconnect/resume, the wrong rotation is applied to one of the portrait monitors due to the naming of the display being the same between all. EXPECTED RESULT Displays to be treated separately (possibly by serial/unique identifier based on connection name) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3+kde+r134-1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451591] [kwin/display configuration] Multiple monitors with same name cause unintentional behavior
https://bugs.kde.org/show_bug.cgi?id=451591 --- Comment #1 from Parker Reed --- Forgot to mention session type X11. I think the connector based layout is working but there's possibly a bug with two of the same name in portrait rotation. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451591] [kwin/display configuration] Multiple monitors with same name cause unintentional behavior
https://bugs.kde.org/show_bug.cgi?id=451591 --- Comment #2 from Parker Reed --- Thanks to a wonderful contributor over on Reddit, finally realized what exposed this issue. My custom EDID setup was already in place when this started. The DisplayPort dock that I have will not drive to monitors at the full refresh rate. So I already had a custom EDID with a single mode single refresh rate set for both of those. Guess which two those were, both portrait. I used a basic EDID generator for the mode and refresh rate which doesn't set a serial number. On top of that I used the same file for both of them in the kernel command line, so to the system they were essentially the same monitor with an nulled out serial. My "solution" of creating to EDID with different names worked because Plasma then have something to differentiate them by even with a blank serial. Wayland with the same EDID works as it already names them as "unknown " programmatically. For the X11 issue at hand, I get that it was my EDID with the same nulled serial causing the issue. I know those get used a lot so probably not the first to run into it. Will be interesting to see if there's anything that can be done there. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439563] KMail completely breaks when running on Wayland
https://bugs.kde.org/show_bug.cgi?id=439563 --- Comment #2 from Amy Parker --- (In reply to Andrew Bota from comment #1) > You can get the Qt version by opening "System Information". I don't use Plasma and don't have Plasma Settings installed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439563] KMail completely breaks when running on Wayland
https://bugs.kde.org/show_bug.cgi?id=439563 --- Comment #4 from Amy Parker --- The help menu is rendered inaccessible by this bug. Amy Parker, she/her On Tue, Jul 13, 2021, 6:59 AM Alois Wohlschlager wrote: > https://bugs.kde.org/show_bug.cgi?id=439563 > > Alois Wohlschlager changed: > >What|Removed |Added > > > CC||alo...@gmx-topmail.de > > --- Comment #3 from Alois Wohlschlager --- > You can use Help>About KMail>Libraries to get KMail, Frameworks and Qt > versions. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439563] New: KMail completely breaks when running on Wayland
https://bugs.kde.org/show_bug.cgi?id=439563 Bug ID: 439563 Summary: KMail completely breaks when running on Wayland Product: kmail2 Version: 5.16.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: enby...@gmail.com Target Milestone: --- Created attachment 139904 --> https://bugs.kde.org/attachment.cgi?id=139904&action=edit Shows KMail being broken SUMMARY On Wayland, KMail's UI just completely breaks. STEPS TO REPRODUCE 1. Install KMail on Fedora 34 w/ Wayland 2. Run KMail 3. Observe OBSERVED RESULT See attachment EXPECTED RESULT KMail operating properly SOFTWARE/OS VERSIONS Linux: 5.12.8 Qt Version: Unsure ADDITIONAL INFORMATION N/A -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 428921] New: error: ‘class KWayland::Client::DataOffer’ has no member named ‘accept’
https://bugs.kde.org/show_bug.cgi?id=428921 Bug ID: 428921 Summary: error: ‘class KWayland::Client::DataOffer’ has no member named ‘accept’ Product: frameworks-kwayland Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: mgraess...@kde.org Reporter: parker.l.r...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- Created attachment 133191 --> https://bugs.kde.org/attachment.cgi?id=133191&action=edit Build log Fails to build on latest master Arch Linux gcc 10.2.0-3 STEPS TO REPRODUCE 1. Clone kwayland-server from git 2. Build OBSERVED RESULT Errors out at a missing member EXPECTED RESULT Build successful Log attached -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 428921] error: ‘class KWayland::Client::DataOffer’ has no member named ‘accept’
https://bugs.kde.org/show_bug.cgi?id=428921 --- Comment #2 from Parker Reed --- plasma-framework-git r15640.8b7b4f74c-1 https://invent.kde.org/frameworks/plasma-framework/-/commit/8b7b4f74c6bdfd51fe9247fec28e71c377004045 Only does it if I leave the default cmake BUILD_TESTS enabled. Disabling tests lets it compile successfully. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 428921] error: ‘class KWayland::Client::DataOffer’ has no member named ‘accept’
https://bugs.kde.org/show_bug.cgi?id=428921 Parker Reed changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Parker Reed --- This appears to be working now. Built fine on the same install with the default options. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 170072] Toolbar doesn't hide when moving cursor from fullscreen window to a different screen on a multihead setup
https://bugs.kde.org/show_bug.cgi?id=170072 Parker Coates changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Parker Coates --- I no longer use Dragon Player, but I just installed it to confirm that this problem no longer occurs for me. Resolving as WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 451591] [kwin/display configuration] Multiple monitors with same name cause unintentional behavior
https://bugs.kde.org/show_bug.cgi?id=451591 --- Comment #7 from Parker Reed --- I have been on 5.26 with the same setup without any modified EDID and it appears to be working as expected. I believe I changed the bottom option in display settings to remember it per monitor setup if that helps. I was on 5.23 shortly before this (Steam Deck) and I was experiencing the same rotation issue on the left hand monitor. After Steam Deck Main branch updated to 5.26, smooth sailing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #1 from Parker Reed --- Seemingly all the Framework laptops have their battery labeled as BAT1 which is where I noticed this (Framework 16) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #3 from Parker Reed --- Checked with a few friends and it looks like even with BAT1 they are only seeing the "Battery" label So this might be a bug that was introduced in the testing Plasma updates. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] New: Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 Bug ID: 492480 Summary: Battery monitor labels only battery as Battery 2 Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: plasma-b...@kde.org Reporter: parker.l.r...@gmail.com CC: k...@privat.broulik.de, natalie_clar...@yahoo.de Target Milestone: 1.0 Created attachment 173188 --> https://bugs.kde.org/attachment.cgi?id=173188&action=edit Screenshot SUMMARY Tray applet shows single battery at /sys/class/power_supply/BAT1 as "Battery 2" STEPS TO REPRODUCE 1. Have a single battery available to the system labeled as BAT1 OBSERVED RESULT Label shows "Battery 2" EXPECTED RESULT Only show "Battery" if BAT1 is the only one available. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.8.0 Kernel Version: 6.10.6-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Attached screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #2 from Parker Reed --- So this may be a recent kernel change to avoid using BAT0. All of my machines on 6.10 are BAT1 and show "Battery 2" in the applet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #5 from Parker Reed --- I only show one battery but it is labeled as BAT1, hence getting the "Battery 2" label ACAD BAT1 ucsi-source-psy-USBC000:001 ucsi-source-psy-USBC000:002 ucsi-source-psy-USBC000:003 ucsi-source-psy-USBC000:004 All of my AMD machines show as BAT1 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 409973] New: Need dual screen support
https://bugs.kde.org/show_bug.cgi?id=409973 Bug ID: 409973 Summary: Need dual screen support Product: yakuake Version: 2.9.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: mpar...@ilm.com Target Milestone: --- SUMMARY Hello! I use Yakuake every day at ILM and really like it! I have a rather large number of terminals to manage and would really appreciate it if Yakuake could work with dual screen setups, allowing more terminals to be shown on the second monitor. Currently the options for screen are: "screen 1, screen 2 or at mouse location". Ideally there would be an option like "Unique sessions on all screens". Thanks so much for your consideration! STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364662] Opening URLs is very slow or aborted completely
https://bugs.kde.org/show_bug.cgi?id=364662 Parker Reed changed: What|Removed |Added CC||parker.l.r...@gmail.com --- Comment #15 from Parker Reed --- Running into this on plasma-framework 5.61 With the default applications URL handler set to "in an application based on the contents of the URL" it takes 1:16 to open http://google.com with kde-open5 Attached log -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364662] Opening URLs is very slow or aborted completely
https://bugs.kde.org/show_bug.cgi?id=364662 --- Comment #16 from Parker Reed --- Created attachment 122495 --> https://bugs.kde.org/attachment.cgi?id=122495&action=edit kde-open5 strace with timestamps -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364662] Opening URLs is very slow or aborted completely
https://bugs.kde.org/show_bug.cgi?id=364662 --- Comment #17 from Parker Reed --- Created attachment 122496 --> https://bugs.kde.org/attachment.cgi?id=122496&action=edit Malformed kioslaverc Figured out the culprit. My ~/.config/kioslaverc had some old malformed proxy entries. Nuking the rc and running without properly opens URL based on mimetype instantly. Uploading the bad kioslaverc as an example -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384066] Auto-rotate screen not working for Accelerometer sensors
https://bugs.kde.org/show_bug.cgi?id=384066 Parker Reed changed: What|Removed |Added CC||parker.l.r...@gmail.com --- Comment #13 from Parker Reed --- Since this didn't make it due to X11 freeze, will this be available for X11 in the hotfix after release? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 396882] Freecell: Can move from foundation with double click
https://bugs.kde.org/show_bug.cgi?id=396882 Parker Coates changed: What|Removed |Added CC||coa...@kde.org --- Comment #2 from Parker Coates --- Created attachment 114153 --> https://bugs.kde.org/attachment.cgi?id=114153&action=edit Potential fix I no longer have a kde-games development enviroment set up, so I can't actually test that this compiles and works, but I believe the fix should be as simple as this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403071] New: The KWin scripting API provides no way to maximize or unmaximize a window
https://bugs.kde.org/show_bug.cgi?id=403071 Bug ID: 403071 Summary: The KWin scripting API provides no way to maximize or unmaximize a window Product: kwin Version: 5.14.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: coa...@kde.org Target Milestone: --- According to d_ed, the relevant function just hasn't been made invokable and exposed to the Javascript API. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 Parker Reed changed: What|Removed |Added CC||parker.l.r...@gmail.com --- Comment #3 from Parker Reed --- Found a workaround: open any KDE file dialog (I used Ctrl O in Chrome) and sort the entries there. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 290061] pie elf always loaded at 0x108000
https://bugs.kde.org/show_bug.cgi?id=290061 Stephen Parker changed: What|Removed |Added CC||stephen.j.par...@gmail.com --- Comment #4 from Stephen Parker --- This is a bit of a necrobump (almost 5 years later to the date!), but I ran into a similar problem trying to run memcheck on android/arm64 with an executable >600mb (Unreal game) and Amir's patch solved the problem. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 485534] Another slider appears after muting/unmuting notification sounds
https://bugs.kde.org/show_bug.cgi?id=485534 Parker Reed changed: What|Removed |Added CC||parker.l.r...@gmail.com --- Comment #2 from Parker Reed --- Created attachment 174875 --> https://bugs.kde.org/attachment.cgi?id=174875&action=edit Screenshot I am seeing this still happening Operating System: Arch Linux KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 485534] Another slider appears after muting/unmuting notification sounds
https://bugs.kde.org/show_bug.cgi?id=485534 Parker Reed changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 495188] New: KDE >=6.2 Crashes after Displayport Hotplug
https://bugs.kde.org/show_bug.cgi?id=495188 Bug ID: 495188 Summary: KDE >=6.2 Crashes after Displayport Hotplug Classification: Plasma Product: plasmashell Version: 6.2.1 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: atericpar...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.2.1) ApplicationNotResponding [ANR]: false Qt Version: 6.8.0 Frameworks Version: 6.7.0 Operating System: Linux 6.11.3-arch1-1-rdtsc x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 6.2.1 [CoredumpBackend] -- Information about the crash: When my monitors turn off and come back on, I get this plasmashell has crashed message every time now (Monitors: lg 5k 2k 34 inch and 2 AOC 4k monitors), the system automatically restarts them and it works fine afterwards. This happened after the 6.2 update, 6.1 was flawless. The crash does not seem to be reproducible. -- Backtrace (Reduced): #5 QWeakPointer::internalData (this=0x60) at /usr/include/qt6/QtCore/qsharedpointer_impl.h:750 #6 QPointer::data (this=0x60) at /usr/include/qt6/QtCore/qpointer.h:75 #7 QPointer::operator QScreen* (this=0x60) at /usr/include/qt6/QtCore/qpointer.h:83 #8 DesktopView::screenToFollow (this=0x0) at /usr/src/debug/plasma-workspace/plasma-workspace-6.2.1.1/shell/desktopview.cpp:144 #9 ShellCorona::screenInvariants (this=) at /usr/src/debug/plasma-workspace/plasma-workspace-6.2.1.1/shell/shellcorona.cpp:874 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 495188] KDE >=6.2 Crashes after Displayport Hotplug
https://bugs.kde.org/show_bug.cgi?id=495188 --- Comment #1 from Eric Parker --- Created attachment 175113 --> https://bugs.kde.org/attachment.cgi?id=175113&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #15 from Parker Reed --- Even stranger, I just booted the Ally on 6.10.10 and it's showing BAT0, but the applet still says battery 2. I could have sworn this was reading BAT1 earlier. There's a second fake PS controller battery, but that's correctly labeled in the power widget. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 493612] New: Night Light fails to activate when displayport monitors go to sleep triggering hotplug
https://bugs.kde.org/show_bug.cgi?id=493612 Bug ID: 493612 Summary: Night Light fails to activate when displayport monitors go to sleep triggering hotplug Classification: Applications Product: systemsettings Version: git-stable-Plasma/6.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: atericpar...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY If the monitors turn off for any reason, night light will fail to activate. This is because of Displayport "hotplug", where sleeping displayport monitors are treated as unplugged. STEPS TO REPRODUCE 1. Turn off a displayport monitor before Night Light's activation time. 2. Turn it on after activation, it doesn't activate. OBSERVED RESULT Night Light never triggers EXPECTED RESULT Night light should work normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.10 KDE Plasma Version: 6.15 KDE Frameworks Version: 6.6 Qt Version: 6.7.2 ADDITIONAL INFORMATION This can probably be fixed by checking night light status whenever a monitor is plugged or unplugged. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 493612] Night Light fails to activate when displayport monitors go to sleep triggering hotplug
https://bugs.kde.org/show_bug.cgi?id=493612 Eric Parker changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 493612] Night Light fails to activate when displayport monitors go to sleep triggering hotplug
https://bugs.kde.org/show_bug.cgi?id=493612 --- Comment #1 from Eric Parker --- >From looking at the codebase, this could probably be fixed by adding a check for monitor plug similar to how the suspend check works? https://invent.kde.org/plasma/kwin/-/blob/master/src/plugins/nightlight/nightlightmanager.cpp -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #20 from Parker Reed --- I recompiled upower to return nothing on creating the DisplayDevice node. Had no affect on Plasma. Still reporting "Battery 2" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #16 from Parker Reed --- Created attachment 173815 --> https://bugs.kde.org/attachment.cgi?id=173815&action=edit upower I'm hitting this condition without having more than one battery https://invent.kde.org/plasma/plasma-workspace/-/blob/master/dataengines/powermanagement/powermanagementengine.cpp#L476 For reference here's my Framework upower output -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #23 from Parker Reed --- I was mistaken in my first assumption of it being powermanagementengine Turns out what handles this for the powerdevil applet is components/batterycontrol/batteriesnamesmonitor_p.cpp Working through some debug messages to try and see why first start of power devil iterates over two batteries but the restart works fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #21 from Parker Reed --- Created attachment 173817 --> https://bugs.kde.org/attachment.cgi?id=173817&action=edit plasmawindowed If I run org.kde.plasma.battery with plasmawindowed within the same session it shows the correct "Battery" label Attached screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #22 from Parker Reed --- Created attachment 173818 --> https://bugs.kde.org/attachment.cgi?id=173818&action=edit powerdevil If I kill and restart org_kde_powerdevil it shows up correctly -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #12 from Parker Reed --- I guess this doesn't rule out a kernel bug or configuration issue. The only commonality between my devices is using Arch Linux. Recently switched to Linux Zen on the framework and its BAT1 as well. I'll ask around on the framework discussion to see what their devices show. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #10 from Parker Reed --- The behavior is seemingly entirely dependent on whether your /sys/class/power_supply folder has a BAT0 or BAT1. None of my devices have any capabilities for multiple batteries, but they are all labeled as BAT1, which would be 2. What is your battery labeled as under sysfs? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #13 from Parker Reed --- I'm seeing a bunch of mentions of this being handled with quirks in the kernel https://github.com/torvalds/linux/commit/c986a7024916c92a775fc8d853fba3cae1d5fde4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #14 from Parker Reed --- Okay, so just realized I do have more AMD hardware. Steam Deck is also BAT1 but 5.27 but power widget correctly labels it as "Battery". Ally, FW 16, T495 all on 6.1/6.2 are BAT1 and have the "Battery 2" label. So, if you need a testing device to triage against, Steam Deck would be a good bet with an up-to-date operating system installed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #8 from Parker Reed --- (In reply to Nate Graham from comment #7) > So you're only seeing this on Framework hardware? Or elsewhere too? I am seeing this on all of my AMD hardware currently, so Framework 16 and a T495. Using up-to-date kernels on Arch Linux. Currently have 6.2 beta on the Framework and it is still showing the same behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #17 from Parker Reed --- I figured it out finally. DisplayDevice has battery stats but no vendor info. This increments unnamedBattery by 1. The real battery comes along and trips it over to 2. [parker@parker-framework powerdevil]$ upower -i /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Wed 18 Sep 2024 02:40:00 AM EDT (7 seconds ago) has history: no has statistics: no battery present: yes state: discharging warning-level: none energy: 21.9971 Wh energy-full: 84.01 Wh energy-rate: 18.7308 W charge-cycles: N/A time to empty: 1.2 hours percentage: 26% icon-name: 'battery-low-symbolic' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #18 from Parker Reed --- Same on the Ally [parker@rogally ~]$ upower -i /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Wed 18 Sep 2024 02:48:00 AM EDT (27 seconds ago) has history: no has statistics: no battery present: yes state: discharging warning-level: none energy: 26.211 Wh energy-full: 33.957 Wh energy-rate: 6.568 W charge-cycles: N/A time to empty: 4.0 hours percentage: 77% icon-name: 'battery-full-symbolic' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #19 from Parker Reed --- Is DisplayDevice not monitor in UPower's world? Now I'm not so sure if that's what's tripping the counter. -- You are receiving this mail because: You are watching all bug changes.
