[kcolorchooser] [Bug 415927] Impossible to pick a screen color on Wayland
https://bugs.kde.org/show_bug.cgi?id=415927 Hugo Parente Lima changed: What|Removed |Added Assignee|hugo...@gmail.com |unassigned-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 415927] Impossible to pick a screen color on Wayland
https://bugs.kde.org/show_bug.cgi?id=415927 Hugo Parente Lima changed: What|Removed |Added CC||hugo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 413691] Color picker picks color from the wrong place when monitors are configured using xrandr (using --scale, --pos and --panning parameters)
https://bugs.kde.org/show_bug.cgi?id=413691 --- Comment #1 from Hugo Parente Lima --- Hi, KColorchooser is just a QColorDialog with extra buttons injected, so you must file this bust to Qt5[1], since there's not much we can do on KDE side. Thanks! [1] https://bugreports.qt.io/ -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.
https://bugs.kde.org/show_bug.cgi?id=356853 --- Comment #35 from Hugo Parente Lima --- This bug was (is) a blocker to me, in fact it was the root cause that make me move away from my KDE/yakuake working env. :-(. At least I learned tmux :-) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 357861] yakuake KF5 git (2016-01-11): fokus problems, no active terminal
https://bugs.kde.org/show_bug.cgi?id=357861 Hugo Parente Lima changed: What|Removed |Added CC||hugo...@gmail.com --- Comment #9 from Hugo Parente Lima --- I can reproduce this with version 3.0.2, other issue I have is, if my terminal is split in two, every time I press F12 to show the terminals the focus (when it works) changes from one terminal to the other. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.
https://bugs.kde.org/show_bug.cgi?id=356853 Hugo Parente Lima changed: What|Removed |Added CC||hugo...@gmail.com --- Comment #9 from Hugo Parente Lima --- Created attachment 97836 --> https://bugs.kde.org/attachment.cgi?id=97836&action=edit A fix, works for me. I fixed it with this patch, however I'm not sure if this is the right fix. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.
https://bugs.kde.org/show_bug.cgi?id=356853 --- Comment #12 from Hugo Parente Lima --- Yes, this is why I said I was not sure if this was the right fix :-) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 357861] yakuake KF5 git (2016-01-11): fokus problems, no active terminal
https://bugs.kde.org/show_bug.cgi?id=357861 --- Comment #12 from Hugo Parente Lima --- Another interesting thing is that when the bug is triggered, i.e. the cursor is not filled, and you retract yakuake, you can see the terminal getting the focus, i.e. having the cursor filled way before the terminal get retracted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 337079] sddm theme doesn't focus password field
https://bugs.kde.org/show_bug.cgi?id=337079 Hugo Parente Lima changed: What|Removed |Added CC|hugo...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 337079] sddm theme doesn't focus password field
https://bugs.kde.org/show_bug.cgi?id=337079 Hugo Parente Lima changed: What|Removed |Added CC||hugo...@gmail.com --- Comment #17 from Hugo Parente Lima --- No focus to me too on start-up. sddm 0.13.0-2 plasma 5.5.4 notebook + monitor -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 357861] yakuake KF5 git (2016-01-11): fokus problems, no active terminal
https://bugs.kde.org/show_bug.cgi?id=357861 --- Comment #13 from Hugo Parente Lima --- Another info, on my machine the bug is only triggered if my settings has 0ms animation time, with 100ms animation time it works. -- You are receiving this mail because: You are watching all bug changes.
