[neon] [Bug 370358] GIve sddm user home folder and .face.icon ACL rights in order to load the avatar

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370358

Jens Reuterberg  changed:

   What|Removed |Added

 CC||jens...@kolabnow.com

--- Comment #4 from Jens Reuterberg  ---
Can confirm that it's the same on a newly installed Arch machine here.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 369671] Tone down transparency of kicker/kickoff menu

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369671

Jens Reuterberg  changed:

   What|Removed |Added

 CC||jens...@kolabnow.com

--- Comment #4 from Jens Reuterberg  ---
One way to solve this would be too turn off transparency completely when
Blur/Background Contrast isn't enabled (for applauncher as well as panel etc) -
but then again there are a few people who use it simply as is and I have no
idea how tricky it is to create such a solution.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360333

Jens Reuterberg  changed:

   What|Removed |Added

 CC||jens...@kolabnow.com

--- Comment #18 from Jens Reuterberg  ---
(In reply to Marco Martin from comment #6)
> this bug is pretty much mutually exclusive with
> https://bugs.kde.org/show_bug.cgi?id=353834
> I fear icons are either going to be too big for some people or too small for
> some other people (and i don't want to add a configure icon size ui)

I guess that any variant will rub some people wrong. We simply can't account
for all tastes and any change will make one group or another angry. The
question is: which group do we want to piss off, or do we accept the problems
that come with such a configuration UI. 
Also if Guillame is correct above, that HiDPI screens make the icons stick to
16x16, that's the main issue since that would make them close to unusable. 

One solution would be to create a third size of 32x32 icons and simply skip to
that size when the panel is resized to something that could accomade them. But
that means recreating the icon theme (so its pixel aligned) and that will take
a while (IIRC only a few of the panel icons exists in 32x32)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 358578] Active window taskbar entry background too bright in Breeze Dark theme

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358578

Jens Reuterberg  changed:

   What|Removed |Added

 CC||jens...@kolabnow.com

--- Comment #7 from Jens Reuterberg  ---
I can't reproduce this now as in Breeze Dark the window decorations are both
dark.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 365318] KRDC is unreadable under breeze dark theme

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365318

Jens Reuterberg  changed:

   What|Removed |Added

 CC||ohy...@gmail.com

--- Comment #12 from Jens Reuterberg  ---
Neither Okular, k3b or ktorrent are affected by what gtk theme you use
though... unless you have set the KDE themes to pick up the GTK theme - which
looking at it seems unlikely. 

With the GTK theme there is a generation shift that happened quite recently
(and may not have picked up) where GTK3 apps suddenly didn't work with the old
GTK3 theme. But that seems like it's not whats happening at all (that glitch
just messed with rightclick menu's being white-on-white). 

What happens when you set the entire destop via Look n Feel to "Breeze Dark"
and then go to GTK theme, set that in turn to Breeze Dark (and Breeze Dark
Icons) - then do the log-in-log-out dance?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365267] Kwin crashes after adding a new system tray and moving it, displays wrong dialogue

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365267

--- Comment #4 from Jens Reuterberg  ---
(In reply to Thomas Lübking from comment #3)
> Sounds much more like a plasmashell issue - shell and compositor seem to be
> running on the screenshots.

Ah cheers Thomas (it was five in the morning and I had slept two hours when I
did this bugreport so a bit saucy in the head)

Also the same applies to my desktop, tested it there to, will test it on
another distro as well later to see if it exists there.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365270] New: Alignment in digital clock/calendar popup wrong

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365270

Bug ID: 365270
   Summary: Alignment in digital clock/calendar popup wrong
   Product: plasmashell
   Version: 5.7.0
  Platform: Archlinux Packages
   URL: https://imgur.com/eH6oPt4
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Digital Clock
  Assignee: mklape...@kde.org
  Reporter: ohy...@gmail.com
CC: plasma-b...@kde.org

The digital clock calendar is awesome but it is also very very misaligned due
to width changes between the letter/numbers practical width and font width.
This causes the effect that it looks extremely misaligned even though the two
parts of the calendar are perfectly aligned.
(Saturday - compared to July for example appear to be on entirely different top
lines but the "saturday" is connected to the "09" which due to the size of the
font has a rather massive padding and pushes "saturday" down)

Similarly the "no events today" sign is based on the initial size and placement
of the date number which makes it in turn misaligned with the right hand part
of the calendar

[screenshot in link]

Reproducible: Always

Steps to Reproduce:
1. Open Calendar

Actual Results:  
Alignment appear wrong

Expected Results:  
Alignment should not appear wrong - one method to achieve this is to base the
placement of "july" in the actual calendar bit on the right to be linked to the
top edge of the 09 as well, which in this case would sadly create a rather
large padding on top. 
But by decreasing the font size of the "09" this could be minimized.

The "no events today" should be placed centred in the open area of the calendar
daily planner from bottom row of date to bottom of widget. Or if possible
centered horisontally, but aligned with middle bar of the actual calendar on
the right.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 364329] System forgets custom login screen background image

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364329

--- Comment #2 from Jens Reuterberg  ---
For me this is using Arch based distro so it is distro independent

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 364329] System forgets custom login screen background image

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364329

Jens Reuterberg  changed:

   What|Removed |Added

 CC||ohy...@gmail.com

--- Comment #1 from Jens Reuterberg  ---
I have the same issues on 5.6 and 5.7 - the reason I think is because when you
select an image from your own home filesystem SDDM can't reach it, picking a
file in /usr/shr and it happily accept the change. 

The best way for me have always been renaming the image you want to use and
moving it manually to the SDDM theme you select and renaming it background.png
(thereby removing the standard background.png)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365269] New: Widget Explorer lacking icons

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365269

Bug ID: 365269
   Summary: Widget Explorer lacking icons
   Product: plasmashell
   Version: 5.7.0
  Platform: Archlinux Packages
   URL: https://imgur.com/NFrzT9f
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Widget Explorer
  Assignee: plasma-b...@kde.org
  Reporter: ohy...@gmail.com

Icons for several widgets in the Widget Explorer are blank and display the
"no-icon" icon.

Reproducible: Always

Steps to Reproduce:
1. Rightclick Desktop
2. Click Add new widget


Actual Results:  
Widget icons are removed for several widgets

Expected Results:  
Visible icons for all widgets. 

The icons for the widgets are available in cuttlefish as for as I can tell.
Activity Pager, Media Frame and KDE connect for example

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365267] Kwin crashes after adding a new system tray and moving it, displays wrong dialogue

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365267

--- Comment #2 from Jens Reuterberg  ---
More fiddling - this only affects the system tray widget and when its on the
desktop

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365267] Kwin crashes after adding a new system tray and moving it, displays wrong dialogue

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365267

--- Comment #1 from Jens Reuterberg  ---
After doing it over and over I realize the only thing that it removes is the
wallpaper, all other features like opening new apps. yakuake, krunner etc are
all there. There simply isnt a desktop to rightclick on or interact with in any
way

Rightclicking on the system tray on the desktop still brings up the desktop
settings and not just clicking the settings on the panel

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365267] New: Kwin crashes after adding a new system tray and moving it, displays wrong dialogue

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365267

Bug ID: 365267
   Summary: Kwin crashes after adding a new system tray and moving
it, displays wrong dialogue
   Product: kwin
   Version: 5.7.0
  Platform: Archlinux Packages
   URL: https://imgur.com/a/D0bfY
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ohy...@gmail.com

I had a panel on one side with a system tray, launcher and clock. Added a new
system tray to desktop and when clicking the settings button, I get the desktop
settings instead of system tray settings.
When trying to drag the system tray widget using the handle, kwin crashes,
screen goes black but still display mouse, and dialogues like desktop number
when moving from desktop to desktop.

Reproducible: Always

Steps to Reproduce:
1. Add system tray to desktop
2. Click on settings for the applet (not rightclick on system tray)
3. Move system tray

Actual Results:  
Displays the desktop settings instead of widget settings. When moved Kwin
crashes

Expected Results:  
Display widget settings, able to move the widget when dragging the handle.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365158] option to change font color in task manager

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365158

--- Comment #8 from Jens Reuterberg  ---
(In reply to Jens Reuterberg from comment #7)
> So after digging around I found that MX theme DO have a colour file, so it
> sets its own colours. Now in the colour file you can edit [colors:window]
> and ForegroundNormal to change colour theme of the taskmanager. With that
> parts of the theme change as well like the clock - but that you can change
> back by defining it in [colors:view]

Sry that doesnt set clock colour so I guess you have to use the same for all
those.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365158] option to change font color in task manager

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365158

--- Comment #7 from Jens Reuterberg  ---
So after digging around I found that MX theme DO have a colour file, so it sets
its own colours. Now in the colour file you can edit [colors:window] and
ForegroundNormal to change colour theme of the taskmanager. With that parts of
the theme change as well like the clock - but that you can change back by
defining it in [colors:view]

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365158] option to change font color in task manager

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365158

--- Comment #6 from Jens Reuterberg  ---
> Even if the choice to follow the text color was made by MX Themes creator I
> don't want to be dependent on it. I want to be able to download a theme from
> kde-look and be able to modify to my preference.

Chances are this will not happen though. There are plans for a theme creator
but this is currently on ice as plans to ensure Plasma 5.8 as an LTS are
underfoot - and stability/polish, instead of features, are more relevant to
work on. Such a thing would be something packaged within the Plasma-sdk package
and allow for an easier way to sort SVG's etc to ensure simplicity (sort of
like Theme Explorer in the Plasma-sdk package which I implore you to check out)
Essentially if you make a theme which says "Make all backgrounds in widgets
bright pink", someone downloads your theme and use it - its very tricky for us
to "fix problem with all this bright pink" except suggest that that person
contact the theme creator.

> This is not the same as set color for task manager text independent from
> theme, widget color or whatever. What if I change this theme so that it
> doesn't follow the color of text set by color theme. What color  would task
> manager follow then and why it is not clearly explained in techbase
> guidelines?

It follows the Window theme colour. Edit the Window Text Colour in Colour
settings. This will affect ALL text in the window theme though so the solution
isn't optimal.

> What if I want to use other themes that are made the same? Well, that's 
> hypothetical question, I have not checked every theme.
Then you wont be able to see the text as well as you would prefer.

> I don't understand what you mean by elegant solution. 
A way where the solution for a fringe issue isn't impeding more common use
cases. A solution where simplicity is part of it. If you can't marry these two
into a solution, the solution isn't elegant and as the choice then is "hurt the
majority" or "hurt the minority" the choice is obvious. ("The need of the many
outweigh the need of the few" to quote Mr Spock)

> What I request is options in configuration file and an easy to understand
> description in techbase so that every user can download theme from kde-look
> and adjust it to his/her preference or even mix different elements from
> different themes (for example to mix icons).
That is impossible to do. Theming in Plasma is extremely flexible from a theme
creators POV and the attempt to have a mix-and-match setting was underwhelming
and buggy. Hence it was removed - if a theme editor is created in the future,
hopefully that will work to cover your needs too. 
Until then, you have to either 
1) edit the theme yourself using for example "Theme Explorer", 
2) ask the creator to make a theme with hardcoded text colours for different
elements,
3) change wallpaper, 
4) change the colour of the Window Text, 
5) Change font to something more readable 
6) Swap to a different theme
7) Hang in there and hope for some dev to create a theme editor from scratch
that covers your needs.

Now I am not the end decider, but I was asked in here as someone representing
the VDG - and from our POV unless an elegant solution presents itself, with a
dev attached that can create this solution, there simply isn't anything that
CAN be done except suggest the above fixes to your issue.
As for an easier to understand techbase documentation (or more extensive) and
easier to understand RC files - I can only agree and I wish I could say "a
theme creator coming right up" - but that would just be lying to you. We want
to create a better theming system for the future, sketches exist, but so far
thats as far as we can get. The dev for the taskmanager has stated that he
can't add this new feature to the taskmanager so that avenue is closed too
leaving you with the seven options above to fix your issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 364472] show holidays also as text in main view

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364472

Jens Reuterberg  changed:

   What|Removed |Added

 CC||ohy...@gmail.com

--- Comment #9 from Jens Reuterberg  ---
What we need is better communication to theme creators that certain changes are
happening and they need to add bits to their themes like in this case a tiny
marker with the correct naming.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365158] option to change font color in task manager

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365158

Jens Reuterberg  changed:

   What|Removed |Added

 CC||ohy...@gmail.com

--- Comment #4 from Jens Reuterberg  ---
The text colour should always (or per default) follow the colour theme in
Breeze and themes that want this. Since there already exists an option in
desktop theme to follow or NOT follow the colour of text set by colour theme,
this is a non issue. (Change theme to Oxygen, change to some coloured text for
the colour theme and observe that the theme does NOT change colour of text). So
the choice to follow the text colour was made by MX Themes creator. 

In the above screenshot I notice the text in the taskmanager is far more
readable than the icons and clock text in the chosen colour theme. To be honest
testing it on my own using Gimp to change colours of text I notice that "white"
(or #FCFCFC) is probably the best option there and I am slightly curious to
know what colour you think would fit better and be more readable? Trying
Magenta for example just hides it. 

My suggestion for fix would be to 1) edit the theme and hardcode the colour of
the widget text. 2) change colour of "Window Text" slightly to better fit your
needs 3) Change the font used for Taskmanager to something bigger and bolder to
make it more readable no matter what colour 4) Change wallpaper 5) Change the
theme to not allow transparent widgets in certain cases, like the taskmanager.

I simply dont see an elegant solution which only goal is, in practice, to fix
one broken theme.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 364953] Breeze and Breeze Light themes are the same but listed twice

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364953

--- Comment #4 from Jens Reuterberg  ---
Created attachment 99798
  --> https://bugs.kde.org/attachment.cgi?id=99798=edit
example for new Breeze multicolour image

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 364953] Breeze and Breeze Light themes are the same but listed twice

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364953

Jens Reuterberg  changed:

   What|Removed |Added

 CC||ohy...@gmail.com

--- Comment #3 from Jens Reuterberg  ---
"Breeze Light", "Breeze Dark" and "Breeze" should be the naming. As for image
to represent each differently I think it wont be that difficult - we could add
the 5.4 wallpaper or something in the background instead of just light grey
colour to represent "any colour you like"?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 364931] Regression: Status icon for "not available" (presence) seems to be lacking

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364931

Jens Reuterberg  changed:

   What|Removed |Added

 CC||ohy...@gmail.com

--- Comment #2 from Jens Reuterberg  ---
Worst possible answer: "it works here" ... can you check if the icon is present
at all and the issue is somewhere on that end? Just install cuttlefish (its in
the plasma-sdk bundle) and search for "user-away-extended" or go to
/usr/share/icons/status and check through all the variable sizes?

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 363206] either install all of oxygen or nothing

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363206

Jens Reuterberg  changed:

   What|Removed |Added

 CC||ohy...@gmail.com

--- Comment #1 from Jens Reuterberg  ---
Nothing then. The main issue here, which I was drawn upon when talking to one
of the neon users is that there is no safe way to install bundles (like
"everything for complete Oxygen" or "Every addon for Application X to ensure
its usability"), but with Oxygen installing it after the fact isn't a big
issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 359127] Desktop theme KCM 'details' and editing tab no longer present/functional

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359127

Jens Reuterberg  changed:

   What|Removed |Added

 CC||ohy...@gmail.com

--- Comment #29 from Jens Reuterberg  ---

> Why not just give a little love to that feature rather then removing it? It
> was very useful! This was one of the biggest features I loved about kde, I
> could customize it in the inside (how it works) and outside (how it looks).
> Now it's like the half of it was gone. My feeling is, we're going in the
> direction of gnome. What is the point of KDE existing if not being extremely
> customable and a complete opposite to gnome philosophy? People love KDE for
> it and now KDE seems to loose its identity. I'm sad because of that.

It simply is one of math - we have a very very limited amount of devs, very few
people from the community helping out meaning that even smaller issues becomes
things that soak up time for everyone.

The theme editor didn't work well enough to be included with a good conscience
and currently the best method is one where you use the Plasma-SDK package to
check, blend and test themes (the Theme Explorer specifically) - granted I too
want a better situation where perhaps we could have a "theme creator" as an
application or something. But that has to be a future choice and one based on
whether there are people enough to do it. Having a Plasma desktop starting,
working as expected, systemtray etc is more relevant than the theme editor
which is harsh but the truth. 

Love sadly is no match against "manpower", "time" and "developer fatigue"

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 360733] screen scaling window does not let you scale below 100%

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360733

Jens Reuterberg  changed:

   What|Removed |Added

 CC||ohy...@gmail.com

--- Comment #2 from Jens Reuterberg  ---
I think this is mostly visual in nature since it's (reading from your reddit
post OP) more about making the widget parts smaller. You should in my opinion
pick a slimmer widget theme (check out the different Qtcurve themes available)
and make your fonts smaller.

Enforcing a downwards resize seems like a hassle in comparison to the gain when
workarounds are available.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 294778] unlock screen should show system name

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=294778

--- Comment #1 from Jens Reuterberg  ---
My suggestion would be to switch wallpapers in the lockscreen - on the one hand
there are ways to include a name from a design perspective without any issue to
the Breeze theme but at the same time the same thing can be acquired by the
user changing wallpapers on one of his/her identical laptops. (You can even add
your computer Name to the lockscreen wallpaper in gimp and use that?)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 351393] support Ctrl+W in password field

[Jens Reuterberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=351393

--- Comment #1 from Jens Reuterberg  ---
I know it would be cool to add more shortcut methods for lockscreen but in this
very specific use case I think that its one of those "it will cause way more
problems implementing than its worth" - its easier to force you to retrain
muscle memory/hold in backspace only than adding the choice to set shortcuts
for off-key lockscreen actions.

At least for the time being.

-- 
You are receiving this mail because:
You are watching all bug changes.