[09:57] <Unit193> mitya57: Howdy.  So I'll flat out ask.  What's the current method in a GTK desktop to set Qt to not look 2002 (basic theme)?  It's starting to change more than the GTK3 for themes. :/
[09:58] <mitya57> Unit193, are you on Yakkety or Zesty?
[09:59] <Unit193> QT_STYLE_OVERRIDE=gtk was the way last cycle, there are indicators the styleplugin is the method but that just changes the application to black.  Another hint was that package plus an ENV var of one of a few choices, but again that either didn't change much or just flat out crashed.  This would be Zesty, I'm asking on behalf of myself and also a bit on Xubuntu's.
[09:59] <mitya57> Then try installing qt5-style-plugins package, and exporting QT_QPA_PLATFORMTHEME=gtk2
[10:02] <mitya57> (This will use GTK+ 2 for both style and native dialogs. If you specify QT_STYLE_OVERRIDE=gtk2 then you can get crashes because style will be GTK+ 2 and dialogs will be GTK+ 3.)
[10:02] <Unit193> mitya57: Right, that's the one that got me the partially black application.
[10:03] <Unit193> mitya57: That seemed to have been the issue then, having both.
[10:04] <Unit193> (/etc/X11/Xsession.d/56xubuntu-session sets QT_STYLE_OVERRIDE=gtk)
[10:04] <Unit193> Thanks.
[10:04] <mitya57> Unit193, then just replace it with QT_QPA_PLATFORMTHEME=gtk2 and add the qt5-style-plugins dependency to some meta package
[10:05] <mitya57> That used to be in qtbase, but has been split out into a separate source.
[10:06] <Unit193> Right, really stinks the env var has changed, but oh well.  I had looked into it (and saw you did commits!) and saw it was split out, seems it's going to go away too..
[10:24] <ilmaisin> some kind of outage on launchpad?
[10:24] <ilmaisin> as i get "timeout error" when trying to change tags
[10:25] <ilmaisin> but however, there: https://bugs.launchpad.net/ubuntu/zesty/+source/cups/+bug/1642966 xnox has submitted ppa patches, they now need a sponsor, right?
[10:59] <cjwatson> ilmaisin: That happens every so often and goes away within 10 minutes or so.  We're hoping that upgrading from PostgreSQL 9.3 to 9.6 will either fix it or at least make it easier to debug.