kde-sig
LOGS
15:07:28 <rdieter> #startmeeting kde-sig
15:07:28 <zodbot> Meeting started Tue May 21 15:07:28 2013 UTC.  The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:07:28 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:07:33 <rdieter> #meetingname kde-sig
15:07:33 <zodbot> The meeting name has been set to 'kde-sig'
15:07:37 <rdieter> #topic roll call
15:07:42 <Kevin_Kofler> Present.
15:07:49 <rdieter> hola all, who's round today?
15:07:51 <jgrulich> present
15:08:01 * mbriza 's here :)
15:08:32 <rdieter> than: ping
15:08:50 <than> rdieter: present
15:09:14 <rdieter> #info rdieter Kevin_Kofler jgrulich mbriza than present
15:09:19 <rdieter> #chair Kevin_Kofler jgrulich mbriza than
15:09:20 <zodbot> Current chairs: Kevin_Kofler jgrulich mbriza rdieter than
15:09:36 <rdieter> #topic agenda
15:09:54 <rdieter> okie dokie, what to discuss today?  f19 beta issues... I suppose
15:12:05 * rdieter can't think of anything else
15:12:13 <rdieter> #topic f19 beta
15:12:20 <mbriza> well, thb, i just came to listen, nothing from my side
15:12:59 <rdieter> I believe f19 kde theming was touched on last week, someone mentioned trying to use a brighter (less dark) wallpaper?
15:13:20 <mbriza> yes, nucleo did and i reassigned the bug to schroedinger-cat-backgrounds
15:13:34 <rdieter> got the bug handy?
15:13:35 <mbriza> i'll find the bug
15:13:40 <nucleo> .bug 962952
15:13:47 <zodbot> nucleo: Bug 962952 wallpaper too dark - https://bugzilla.redhat.com/show_bug.cgi?id=962952
15:13:50 <rdieter> excellent, any news/progress?
15:13:50 <Kevin_Kofler> And now it's in a superposition of getting fixed and not getting fixed? ;-)
15:13:55 <Kevin_Kofler> Or do we have any updates?
15:14:39 <mbriza> no updates i think
15:15:23 <rdieter> let's decide which we like best, https://fedoraproject.org/wiki/F19_Artwork#Alpha_Release_Wallpaper
15:15:39 <mbriza> to be honest, i'd be much happier if the change was done in the backgrounds package than in our themes
15:15:40 <rdieter> the current one used now is what?  night?
15:15:50 <mbriza> yes, night
15:16:06 <rdieter> ok, I can barely tell any difference between dawn/day, so either is fine with me.
15:16:09 <mbriza> i like dawn the best, it's similar color to the f18 one
15:16:11 <rdieter> anyone else with a preference?
15:16:19 <rdieter> ok, dawn gets +1.
15:16:45 <jgrulich> dawn +1
15:17:00 * rdieter tenatively +1's dawn too
15:18:07 <rdieter> any objections, comments?  if not, we can followup in the bug with our official preference for dawn
15:18:12 <jgrulich> Dusk and Night are too dark
15:18:17 * Kevin_Kofler has a look at the images…
15:18:58 <rdieter> than: do you have any preference?
15:19:36 <rdieter> nucleo: ^^ ? you seems to imply you'd prefer the "most light" one in the bug... day ?
15:19:38 <Kevin_Kofler> Dawn looks best standalone, but I'm not sure the bottom is not (still) too dark for transparent panels.
15:20:00 <than> none from ,my side
15:20:18 <Kevin_Kofler> Day is very light.
15:20:33 * rdieter thinks dawn is probably the best compromise, agrees day may be too light
15:21:15 <Kevin_Kofler> The current default (Night) is way too dark.
15:21:17 <rdieter> another approach is we could tweak the plasma clock settings to use some darker/bold text perhaps
15:21:37 <Kevin_Kofler> I think we'd need lighter text, not darker. :-)
15:21:40 <rdieter> (well, s/another/another parallel/)
15:22:00 <rdieter> I meant do both, but bolding should help either way
15:22:19 <nucleo> I need to try Dawn (still have F16 wallpaper that was the best)
15:22:49 <rdieter> regardless, dawn is an incremental improvement over the status quo
15:23:26 <mbriza> the funny thing in this is, changing the background in schroedinger-cat-backgrounds changes it for other spins, too
15:23:47 <mbriza> because schroedinger-cat-backgrounds-base contains only the night one
15:24:37 <rdieter> mbriza: true, we'll have to see how it goes
15:24:47 <Kevin_Kofler> I think the ultra-dark Night image is a poor default for all spins.
15:24:48 <nucleo> text on panel with Down looks fine
15:25:03 <rdieter> Kevin_Kofler: I would tend to agree
15:25:28 <mbriza> me too, as i mentioned, it's similar to the spherical cow background
15:25:28 <rdieter> ok, dawn it is.
15:25:40 <rdieter> any other f19 related issues or comments?
15:26:00 * rdieter saw some anaconda-on-kde issue(s) raised on irc last night... something about icons?
15:26:20 <rdieter> .bug 964019
15:26:26 <zodbot> rdieter: Bug 964019 Ugly icons when running from KDE live images - https://bugzilla.redhat.com/show_bug.cgi?id=964019
15:26:41 <rdieter> apparently it uses some of the gnome symbolic fonts (not present in oxygen)
15:27:07 <rdieter> it's in anaconda hands for now, dont think theres anything for us to do here (yet)
15:27:37 <Kevin_Kofler> It uses the stock harddisk image from GTK+ instead of the fd.o drive-harddisk themed icon.
15:27:49 <rdieter> Kevin_Kofler: I recall you checking xsettings-kde, what does it set/use for the fallback icons?
15:28:09 <Kevin_Kofler> We haven't figured out yet why, because running anaconda directly instead of liveinst appears not to be affected.
15:28:22 <Kevin_Kofler> The fallback to the GNOME theme works in KDE.
15:28:29 <rdieter> ok
15:28:32 <Kevin_Kofler> adamw only asked me about that because it doesn't work on MATE.
15:28:44 <Kevin_Kofler> The issue we have now is the one with the harddisk icon.
15:29:01 <rdieter> may be another one of those 'anaconda running as root, without any settings daemon theming wierdness'
15:29:06 <Kevin_Kofler> And there we don't know why we end up with the unthemed stock icon getting used (which is not available in large enough sizes).
15:29:21 <Kevin_Kofler> XSettings should apply to all apps, even root ones.
15:29:39 <Kevin_Kofler> (anything displaying on the X server)
15:29:55 <rdieter> oh, I didn't think that worked?  if it does, great
15:30:22 <rdieter> isn't that we we have all those /root gtk hacks on the live image?
15:31:38 <Kevin_Kofler> The root hacks are for firstboot/initial-setup.
15:31:56 <rdieter> ah, right!  knew was confusing myself
15:32:02 <Kevin_Kofler> They used to be for liveinst too, but they're not needed for that now that xsettings-kde sets the theme through XSettings.
15:33:02 <rdieter> quick status update on other f19 stuff:  the packagekit problem seems resolved
15:33:20 <rdieter> both pk-yum backend crasher, and apper/kded, should be fixed now
15:33:25 <rdieter> with latest stuff in updates-testing
15:33:41 <Kevin_Kofler> Great,
15:33:47 <rdieter> i've prepped f18 updates for pk-qt-0.8.8+apper-0.8.1 too
15:34:06 <rdieter> since f18-updates-testing has pk-0.8.9 now too
15:34:56 <nucleo> night screenshot http://nucleo.fedorapeople.org/night.png
15:35:04 <nucleo> dusk http://nucleo.fedorapeople.org/dusk.png
15:35:12 <nucleo> dawn http://nucleo.fedorapeople.org/dawn.png
15:35:19 <nucleo> day http://nucleo.fedorapeople.org/day.png
15:35:53 <rdieter> wow, didnt realize the diff between dawn/day was so big
15:36:24 <rdieter> wait, I think I just confused dawn and dusk
15:36:26 * rdieter reloads
15:36:44 <rdieter> ok, i still like dawn best :)
15:36:46 <rdieter> nucleo: thanks
15:38:43 <Kevin_Kofler> +1 for dawn.
15:40:58 <rdieter> #topic open discussion
15:41:02 <rdieter> so, anything else for today?
15:41:38 <nucleo> .bug 963502
15:41:44 <zodbot> nucleo: Bug 963502 Droid sans fonts not applied in GTK applications - https://bugzilla.redhat.com/show_bug.cgi?id=963502
15:42:52 <rdieter> that one works for me... if I choose the "right" droid sans, which seems to get listed twice for me
15:43:20 <rdieter> in systemsettings fonts I see both:  Droid Sans [monotype] and Droid Sans [unknown]
15:43:22 <nucleo> looks like Sns used if Doid sans [unknown] or [monotype] selected
15:43:36 <rdieter> I think only [unknown] works right for me
15:43:56 <rdieter> though, i've since switched to using arimo :)
15:44:08 <rdieter> which doesnt have that problem
15:45:24 <nucleo> works in GTK apps?
15:45:29 <nucleo> firefox
15:45:30 <rdieter> yeah
15:46:09 <nucleo> for me only Droid Serif changes fonts in firefox
15:46:30 <nucleo> [unknown] and [monotype] the same as default fonts
15:46:38 <rdieter> hrm, on my f19 box now, I can't get ff to use anything
15:46:52 <rdieter> the window flickers when I change the menu font, but it doesnt actually change. :-/
15:47:03 <rdieter> sigh
15:47:57 <nucleo> I also on F19
15:48:00 <rdieter> heh, when I mouse-over menu items, it switches to what I want.  wierd
15:48:26 <nucleo> I see firefox preferences window
15:48:37 <rdieter> something wierd is going on there alright
15:49:42 <nucleo> only one Droid Sans was when Droid fonts was added to repo
15:49:50 <nucleo> without [..]
15:50:10 <rdieter> yeah, the [] is new, not sure when it showed up
15:50:24 <nucleo> this was 3 years ago http://nucleo.fedorapeople.org/droid.png
15:50:44 <nucleo> but  I don't remember how it was in GTK apps
15:50:45 <rdieter> the fact that it's not present in arimo variant, makes me think it's a droid'ism
15:51:05 <rdieter> hard to say
15:51:56 <nucleo> so this bug in xsettings-kde, gtk or in droid fonts?
15:52:50 <rdieter> dont know, need more debugging/evidence
15:53:28 <rdieter> need to look @ oxygen-gtk/xsettings-kde and try older droid fonts (least likely is a gtk issue, but you never know)
15:54:00 <nucleo> bug reporter tried both oxygen-gtk and qtcurve
15:54:45 <rdieter> could even be firefox specific
15:55:00 <rdieter> looks like even chrome worked here, in a quick test
15:55:38 <Kevin_Kofler> I'd say Firefox bug.
15:56:28 <rdieter> if other gtk apps work, that would be more likely
15:56:38 <nucleo> for me Droid font not appliedalso  in chroium
15:56:45 <nucleo> chromium
15:57:04 <rdieter> nucleo: so we're testing 2 slightly different things
15:57:18 <rdieter> for me, *nothing* I set for menu font gets applied to firefox
15:57:27 <rdieter> it's not specific to droid
15:59:38 <rdieter> gimp works
15:59:51 <nucleo> Liberation, Droid Sserif appeared in firefox menus, only Droid Sans looks as Sans Serif
16:00:58 <rdieter> gnome-disks does not work
16:01:12 <nucleo> it uses gtk3
16:01:39 <rdieter> i know, just testing different things
16:01:47 <rdieter> boo, this used to work
16:02:30 <rdieter> anyway, let's followup in the bug
16:02:45 <rdieter> any final thoughts before I close the meeting?  we're pretty much out of time
16:04:27 <rdieter> ok, thanks everyone!
16:04:28 <rdieter> #endmeeting