[plasma-pa] [Bug 480493] Associate an audio output with a display configuration
https://bugs.kde.org/show_bug.cgi?id=480493 --- Comment #2 from Martin Collins --- Looking into that I find that just getting the name of the connected monitor is rather involved. Is there a simple way? How does kscreen do it? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 480493] Associate an audio output with a display configuration.
https://bugs.kde.org/show_bug.cgi?id=480493 Martin Collins changed: What|Removed |Added CC||kdeb...@mkcollins.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 480493] New: Associate an audio output with a display configuration.
https://bugs.kde.org/show_bug.cgi?id=480493 Bug ID: 480493 Summary: Associate an audio output with a display configuration. Classification: Plasma Product: KScreen Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kdeb...@mkcollins.org Target Milestone: --- I carry my laptop between home and work, and plug it into USB-C docks with all the peripherals attached, with different monitors in each place. I have recently upgraded my home setup with an AV receiver so video and sound now both go out via HDMI. At work sound still goes out via the analog port. Now when I plug in I have to manually change the audio output every time. So I wonder if an audio output could be associated with a display configuration so the switch is automatic. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 Martin Collins changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #16 from Martin Collins --- I got some improvement by removing the TERM entry in the profile's environment settings. Now I have replaced my laptop and did a new install. It all works correctly so I will close this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385607] Panel drawn badly after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=385607 --- Comment #9 from Martin Collins --- I am on 5.24.5 now, but have not seen this happen in a long time. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 --- Comment #15 from Martin Collins --- After a reboot I still have all three problems. I may have confused myself with the XFree4/Linux Console binding thing. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 --- Comment #14 from Martin Collins --- (In reply to Ahmad Samir from comment #13) > did you try a new konsole profile? No change. > - ~/.local/share/konsole/ this is where the profiles live There is also konsoleui.rc here which the new user does not have. I renamed it and ran a new konsole. That seems to have fixed the keys, even though a new one got created that diff says is the same as the old one !? Likewise New Colour Scheme.colorscheme, though renaming it had no effect on the colors. > - ~/.config/konsolerc this is the app general settings Not seeing anything suspicious in there. Tried renaming it anyway but it didn't fix the colors. Hmm, there was a sizeable update this morning. I'm wondering if that is why the new user works and the keys were fixed. I think I'll try rebooting. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 --- Comment #12 from Martin Collins --- (In reply to Ahmad Samir from comment #6) > Also it might be useful to try with a new user account, just in case > something in your current one is interfering. Well now. I created a new user and the keys, the colors, and even the Chinese characters work as they should. I guess that means something in my config files disagrees with some update. I haven't done much configging lately but I do have 20 years worth of accumulated . files hanging around. Any suggestions where I should focus my attention? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 --- Comment #10 from Martin Collins --- (In reply to Ahmad Samir from comment #9) > When you select XFree4 in the config dialog, the "Defaults" (i.e. reset) > button is disabled? Yes, and also when I select Linux Console. I guess that only enables when you have edited a binding? I haven't messed with that at all. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 --- Comment #8 from Martin Collins --- I wonder if the default key bindings changed. If it used to be Linux Console and got changed to XFree 4 that would make sense. Incidentally, the broken Chinese character rendering also happens in UXTerm so I guess that is not a Konsole problem. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 --- Comment #7 from Martin Collins --- (In reply to Ahmad Samir from comment #4) > Check what the characters the key codes are sending, e.g.: F1 F2 F3 F4 F5 Home End Xfree4 ^[OP ^[OQ ^[OR ^[OS ^[[15~ ^[[H ^[[F Linux^[[[A ^[[[B ^[[[C ^[[[D ^[[[E ^[[1~ ^[[4~ -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 --- Comment #5 from Martin Collins --- (In reply to Duncan from comment #3) > FWIW I believe the color thing was now-fixed bug #435309. I don't think so. That bug is all about text selection and was fixed in 21.08. This problem is not only selection but colors in general in mc (ncurses?) and I'm running 21.08.2 so presumably have that fix. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 --- Comment #2 from Martin Collins --- It is Default (XFree 4). I tried Linux Console and that works much better. I changed back to Default (XFree 4) and it is still faulty. Maybe I'll stick with Linux Console. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 Martin Collins changed: What|Removed |Added CC||kdeb...@mkcollins.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] New: Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 Bug ID: 445616 Summary: Update broke keys and colors in Midnight Commander. Product: konsole Version: 21.08.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: kdeb...@mkcollins.org Target Milestone: --- SUMMARY In Midnight Commander a number of important keys either no longer work or do something wrong. Also some of its colors have changed, hampering usability. STEPS TO REPRODUCE 1. Run mc in a konsole. 2. Try pressing F1-F4, home, end, numpad operators, probably more. 3. Look at the colors! OBSERVED RESULT Some of the keys no longer work or do the wrong thing. eg. F3 should view a file, instead it selects all files. And they go brown instead of yellow. Oh, probably unrelated but Chinese characters are still broken too. That was from an earlier update. EXPECTED RESULT No surprise changes to my precious mc. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Sparky Linux 6.1 (Debian Testing) kernel 5.14.0-4-amd64 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I tried running mc in a UXTerm. Still normal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431440] Plasma fails to start
https://bugs.kde.org/show_bug.cgi?id=431440 Martin Collins changed: What|Removed |Added CC||kdeb...@mkcollins.org --- Comment #8 from Martin Collins --- I have the same issue. After entering my password the K banner comes down but the progress bar stalls about 2/3 way along. I discovered by accident that Alt-F2 will open a Krunner and if I type plasmashell in it I get a desktop. It is missing some of my settings and it does not restore my session but it is usable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385607] Panel drawn badly after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=385607 --- Comment #6 from Martin Collins --- This was fixed for a while but it is broken again in 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385607] Panel drawn badly after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=385607 --- Comment #5 from Martin Collins --- Wiping ~/.cache didn't work. I noticed this in my syslog: [399172.702445] nouveau :01:00.0: fifo: CACHE_ERROR - ch 8 [plasmashell[13676]] subc 0 mthd 0060 data beef0201 [399414.688342] nouveau :01:00.0: fifo: CACHE_ERROR - ch 8 [plasmashell[13676]] subc 0 mthd 0060 data beef0201 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385607] Panel drawn badly after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=385607 --- Comment #3 from Martin Collins --- Still does it with plasmashell 5.10.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385607] Panel drawn badly after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=385607 --- Comment #2 from Martin Collins --- Created attachment 108311 --> https://bugs.kde.org/attachment.cgi?id=108311&action=edit Screenshot The black bar runs all along the bottom of the screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385607] New: Panel drawn badly after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=385607 Bug ID: 385607 Summary: Panel drawn badly after resume from suspend Product: plasmashell Version: 5.8.7 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: kdeb...@mkcollins.org Target Milestone: 1.0 Flags: Wayland-, X11-, VisualDesign- New bug in plasmashell 5.8.7 After resuming from suspend the bottom few pixels of the panel are black and also a small rectangle in the bottom right of the screen which obscures the last digit of the clock. Restarting plasmashell fixes it. I am running nouveau graphics driver. -- You are receiving this mail because: You are watching all bug changes.
