Not found the easy way to do this yet. Probably possible with some scripting, but meh!

@acrouthamel good point; done.

@valorie Should this be named 18.04 point release based on @rikmills suggestion?

Is there a written declaration somewhere of :

the market direction of Kubuntu

My feeling is that we might look at enabling backends by default for an LTS point release? If integration issues receive some fixes and updates to that LTS for them.

By all acounnts from the reading I have done so far - Plasma Mycroft requires

Testing Kubuntu 18.04 beta ISOs when you have a minute, basically.

So Peruse, Cutelyst, kio-stash, systemdgenie, Plasma Mycroft and kube remain unpackaged or not uploaded.

Uh oh :)

I was working on trying to MyCroft Plasmoid installed on 17.10 today, but I ran into a dep issue with zlib.so.1 zlib1g:amd64

I haven't started on the QA part yet, but I have some technically-proficient Kubuntu-using contacts and leads who I may be able to tap. @acrouthamel and @sharvey spring to mind!

Do you have any thoughts on this apsect of the role

Thanks, I already feel well-supported! Really all the credit goes not to me but to the folks doing the work! This is an amazing team of people.

Right.. Just a bit behind the curve as always. But Welcome Nate, and thanks for stepping up to the role of Product Manager

This has already been in the iso and in desktop full recommends for a long time

Works perfect with ppa enabled. Love it.

Should be on iso tomorrow.

In T7854#135886, @darinmiller wrote:

I had to manually set the wallpaper type to "image" and the default image was available. It's looked great as a lock screen.

I had to manually set the wallpaper type to "image" and the default image was available. It's looked great as a lock screen.

Anyone tested?

In T8377#135845, @stikonas wrote:

But that would break theming in other desktops.

In T8377#135841, @ngraham wrote:

In T8377#135812, @ragreen wrote:

@ngraham It's important for root apps to be visually consistent with the rest of the desktop but a different color scheme is advisable. Re-open at will.

Agreed. The question is... should we fix this in Kubuntu by setting XDG_CURRENT_DESKTOP="KDE", or upstream in KSystemLog itself?

What exactly is this task tracking? Very general suggestions ("make it better") aren't very actionable. Do you have specific action items in mind for how to improve the installer slideshow?

In T8377#135812, @ragreen wrote:

@ngraham It's important for root apps to be visually consistent with the rest of the desktop but a different color scheme is advisable. Re-open at will.

Not sure this is really appropriate for a Phabricator task. Feel free to go and do it though!

The targeted user has no notion of up or downstream. For them it's just Kubuntu. I'll load Kubuntu again, then I should be able to elaborate properly.

@ngraham It's important for root apps to be visually consistent with the rest of the desktop but a different color scheme is advisable. Re-open at will.

In T8377#135810, @jackyalcine wrote:

That video confirms what he mentioned - but it does provide a notion for a potential fix.

It seems like XDG_CURRENT_ENVIRONMENT is _not_ being set by or being used by kdesu and the launched application.

That video confirms what he mentioned - but it does provide a notion for a potential fix.

In T8377#135797, @ngraham wrote:

Bugzilla tickets aren't necessary to commence work, in fact! The real issue is that KSysLog currently has to run as root: apps run as root don't inherit user themes. The correct solution is to make it not need to run as root, and then make it request elevated privileges using PolicyKit only when necessary. You might talk to @stikonas, who recently did this work for KDE Partition Manager.

apps run as root don't inherit user themes :)

Are you saying that Kubuntu should disable the behavior of apps that minimize to the system tray when closed, and that instead they should always quit instead?

The funny thing is: when I tested Artful, it looked the same as in the upcoming Bionic, but I saw a picture illustrating a breezified KSysLog in Help.

Are you referring to it minimizing to the system tray?

Bugzilla tickets aren't necessary to commence work, in fact! The real issue is that KSysLog currently has to run as root: apps run as root don't inherit user themes. The correct solution is to make it not need to run as root, and then make it request elevated privileges using PolicyKit only when necessary. You might talk to @stikonas, who recently did this work for KDE Partition Manager.

In T8377#135794, @ngraham wrote:

This isn't really something that we can feasibly fix in Kubuntu. I would say, "please report upstream," but KDE folks are well aware of the issue already. What's needed is not more bug reports, but rather someone to actually put in the time to improve it. Would you like to have a go at it?

https://community.kde.org/Get_Involved/development

This isn't really something that we can feasibly fix in Kubuntu. I would say, "please report upstream," but KDE folks are well aware of the issue already. What's needed is not more bug reports, but rather someone to actually put in the time to improve it. Would you like to have a go at it?

@ngraham Michael is great but you can't expect unbiased opinions from a declared Plasma fan.

Some people prefer vintage! 😜

Purpose: we need more opinions to make Bionic even better.

You mean like @michaeltunnell? 😉

Please try:

Integration is good but too much integration is bad.

Say Akregator. I open it. I close it. It gets pined to Notifications. And it remains pinned to Notifications even after reboot. Closing it does not mean you quite it.

Please explain what you mean by that.

Neon's selling point is it's a slim build. Several legacy apps shouldn't be included into the iso, but made readily available in the repo. I'll refer to them soon. At any rate, it's pretty annoying when some of those get pinned to Notifications by default.

Okay, I need to wrap this up nicely for them. Will do.

And for best results, please remember https://community.kde.org/Get_Involved/Bug_Reporting#Bug_tracker_etiquette

You should! :) Please head over to http://bugs.kde.org/ and file individual bugs against the Breeze product for these separate issues.

What's the deeper issue here that's motivating this change request?

I'm not sure it makes sense to have just Dolphin's main window forced to centered. It feels like working around another issue that we should fix instead. What's the deeper issue here that's motivating this change request?

@ngraham Whatever you see fit. I'm done.

A quadrant's width is probably okay. I'm not sure about the hight.

However, I would reject this as a default, as it is very non-obvious how to turn such a thing off for a new or even moderately experienced user.

In T8354#135382, @ngraham wrote:

Then they must use the "Centered" KWin positioning behavior by default.

This request was about Dolphin, not all windows. We could investigate using the "Centered" KWin window positioning behavior for all windows, but not just Dolphin.

I need rest. Made it a mess.

I guess you are suggesting that it should be installed by default?

Then they must use the "Centered" KWin positioning behavior by default.

@ngraham But Nathan, look into Neptune. Every window opens in the middle.

Is this something we can actually do? KWin takes care of window positioning, and I'm not sure there's anything we can to do adjust this. Bugs in window positioning should be reported upstream to KWin

Applied

64 px tested.

Latest Yakuake 3.0.5 is there in bionic to install if desired.

Done, uploaded, and now in today's daily iso.

Personally, the blue has grown on me, and my retinas are just fine. :P

That they do demonstrate. With this Plasma wallpaper it does look good, since it's colours are darker and there's no overlapping elements in the background. But this changes if the next release's wallpaper have more "stuff" and brighter, more vibrant colours, unsless this taken into account when designing it.