[00:03] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm just became unstable after failing: https://ci.lubuntu.me/job/groovy_stable_sddm/385/
[00:04] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/628/
[00:04] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/132/
[00:20] <wxl> i just heard yet another complaint about the fact that we don't have a simple option for a full dark experience. if i remember correctly the steps to make that happen are on discourse somewhere. maybe we could make some simple program to twiddle it?
[00:40] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_screengrab just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_screengrab/353/
[00:40] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-session just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_lxqt-session/346/
[00:54] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_compton-conf FAILURE: https://ci.lubuntu.me/job/groovy_stable_compton-conf/319/
[00:54] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/370/
[00:54] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/218/
[00:54] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/120/
[00:54] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/604/
[00:54] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/366/
[00:55] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/566/
[01:10] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libsysstat just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_libsysstat/104/
[01:14] <kc2bez[m]> wxl: I don't know if it meets the easy threshold or not but this is in LXQt 0.16 https://share.riseup.net/#Zdrwl6Robn27DLnvnhmLKA
[01:15] <wxl> oh well it's not 100% easy cuz there's still GTK
[01:15] <kc2bez[m]> Understood
[01:15] <wxl> i hear lots of folks fixed it with kvantum
[01:16] <wxl> maybe we could ship that with two configs, standard and dark?
[01:16] <kc2bez[m]> I used kvantum which works fine if you don't twiddle too many things.
[01:17] <wxl> i've never used it and don't care too much but clearly other people do
[01:18] <kc2bez[m]> We should probably have 2 options I guess.
[01:18] <wxl> i mean there's dark mode everything these days so i think people kind of expect it
[01:18] <kc2bez[m]> I agree
[01:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-openssh-askpass just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-openssh-askpass/580/
[01:25] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-powermanagement just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_lxqt-powermanagement/337/
[01:25] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/628/
[01:25] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/132/
[01:26] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm just became unstable after failing: https://ci.lubuntu.me/job/groovy_stable_sddm/385/
[01:26] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_obconf-qt just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_obconf-qt/351/
[01:27] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/121/
[01:27] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/605/
[01:27] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/367/
[01:35] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_obconf-qt just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_obconf-qt/587/
[01:35] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/367/
[01:36] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/219/
[01:37] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/567/
[01:40] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/628/
[01:41] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/132/
[01:41] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm just became unstable after failing: https://ci.lubuntu.me/job/groovy_stable_sddm/385/
[01:51] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_compton-conf just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_compton-conf/320/
 @HMollerCl  has a script to put a dark mode, which seems to work also in 0.16
 Or it seems to do it correctly on debian
 I tend not to do too much themeing as then to update screenshots for the manual I would have to change back
 we actually have that in phab I think. (re @N0um3n0: @HMollerCl  has a script to put a dark mode, which seems to work also in 0.16)
 Yes (re @kc2bez: we actually have that in phab I think.)
[02:26] -lugito:#lubuntu-devel- [rMANUALd73edb954197: Fix styling on resume playback] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALd73edb954197
[02:26] -lugito:#lubuntu-devel- [rMANUALfdf10f7e6f48: Add more descrpition on custom skins] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALfdf10f7e6f48
[02:39] -lugito:#lubuntu-devel- [rMANUAL10581fb36e39: Add last.fm tracking option] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL10581fb36e39
[02:45] -lugito:#lubuntu-devel- [rMANUAL4b40a01df2b9: Fix order of fullscreen and window decorations in vlc prefrences] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL4b40a01df2b9
[02:47] -lugito:#lubuntu-devel- [rMANUALe6b152052152: Update wording on which fullscreen monitor] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALe6b152052152
[02:55] -lugito:#lubuntu-devel- [rMANUAL6970ea4249b3: Add note on snapshot section] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL6970ea4249b3
[03:29] -lugito:#lubuntu-devel- [rMANUAL2926fbddf1e0: Add fast seek option] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL2926fbddf1e0
[04:31] <wxl> there's an old screenshot here to show how much i care about looks https://soundcloud.com/djxen23/juno-vi
[04:33] <wxl> @lynorian do you not theme because of the screenshots or because you don't really care anyways?
[04:34] <lynorian> both why not both
[04:34] <wxl> aw heck
[04:34] <wxl> wait i meant or not xor, so we're good XD
[05:25] <RyuKurisu[m]> <lubot "[telegram] <N0um3n0> @HMollerCl "> Do you know where that script went? 🙂
[05:51] -lugito:#lubuntu-devel- [T185: deal with merges] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T185#4231
[06:12] -lugito:#lubuntu-devel- [T185: deal with merges] The_LoudSpeaker (Raman Sarda) commented on the task: https://phab.lubuntu.me/T185#4233
[06:27] -lugito:#lubuntu-devel- [Lubuntu CI] merger_libqtxdg FAILURE: https://ci.lubuntu.me/job/merger_libqtxdg/715/
[06:28] -lugito:#lubuntu-devel- [Lubuntu CI] merger_libfm-qt FAILURE: https://ci.lubuntu.me/job/merger_libfm-qt/746/
[06:49] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_nm-tray just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_nm-tray/557/
[06:49] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_nm-tray just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_nm-tray/557/
[06:59] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-qtplugin just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-qtplugin/360/
[06:59] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-qtplugin just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-qtplugin/360/
[06:59] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/105/
[06:59] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/105/
[08:47] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/594/
[08:58] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/371/
[08:58] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/595/
[08:58] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/595/
[08:58] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/102/
[08:58] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/371/
[08:58] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/102/
[09:24] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_compton-conf just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_compton-conf/321/
[09:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/682/
[09:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/682/
[09:55] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/682/
[10:10] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libsysstat just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_libsysstat/105/
[11:02] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/360/
[11:02] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/219/
[11:06] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/568/
[11:06] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/220/
[11:07] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver just failed after being unstable: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/361/
 Here it is https://phab.lubuntu.me/source/lubuntu-breeze-config/repository/master/ but I remember I tried in 0.16 and it didn't work, but I compiled myself over 20.04 for testing. (re @lubuntu_bot: (irc) <RyuKurisu[m]> <lubot "[telegram] <N0um3n0> @HMollerCl "> Do you know where that script went? 🙂)
[11:17] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/568/
[11:17] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/534/
[11:17] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-build-tools/311/
[11:26] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-build-tools/97/
[11:27] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-build-tools/98/
[11:31] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/534/
[11:42] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-build-tools/312/
[11:42] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/535/
[11:43] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-globalkeys just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-globalkeys/101/
[11:43] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-globalkeys just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-globalkeys/101/
[12:46] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-powermanagement just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-powermanagement/593/
[13:37] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_calamares just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_calamares/654/
[13:58] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-runner just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-runner/102/
[15:04] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/606/
[15:04] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/122/
[15:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/606/
[15:24] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/368/
[15:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/606/
[15:25] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/122/
[15:44] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/368/
[15:45] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_qterminal/425/
[16:10] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/628/
[16:10] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/132/
[16:11] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/385/
[16:31] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qps just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_qps/393/
[16:52] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/629/
[16:52] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qps just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_qps/393/
[16:52] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/386/
[16:56] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_nm-tray just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_nm-tray/558/
[17:21] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/133/
[17:22] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_nm-tray just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_nm-tray/558/
[17:22] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-qtplugin/360/
[17:23] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-qtplugin just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_lxqt-qtplugin/361/
[17:41] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/106/
[17:42] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/106/
[18:05]  * The_LoudSpeaker is here. @wxl around?
[18:05] <wxl> yep
[18:07]  * The_LoudSpeaker boots up the ontainers
[18:07] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-config/683/
[18:07] <The_LoudSpeaker> *containers
[18:07] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_compton-conf just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_compton-conf/322/
[18:08] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/595/
[18:11] <The_LoudSpeaker> https://launchpadlibrarian.net/521180878/buildlog_ubuntu-hirsute-s390x.liblxqt_0.16.0-1ubuntu1_BUILDING.txt.gz
[18:11] <The_LoudSpeaker> about this, so I try deleting all those problematic lines form s390x symbols file?
[18:11] <The_LoudSpeaker> *should I try?
[18:12] <wxl> oh we're still on that
[18:12] <The_LoudSpeaker> yeah. i didn't have time before.
[18:12] <wxl> np
[18:13] <The_LoudSpeaker> college stuff. and today I was filing taxes for dad
[18:13] <wxl> so it looks like you just need to do what i did before
[18:13] <wxl> did we really not get libqtxdg done? i thought we did
[18:14] <The_LoudSpeaker> wait a sec
[18:14] <The_LoudSpeaker> i pasted wrong link
[18:14] <kc2bez[m]> I don't think we did xdg no
[18:14] <kc2bez[m]> I synced it from the archive but that was it
[18:14] <wxl> cuz that's first
[18:15] <kc2bez[m]> Yeah we need to watch that
[18:15] <The_LoudSpeaker> https://launchpadlibrarian.net/521797169/buildlog_ubuntu-hirsute-s390x.libfm-qt_0.16.0-3ubuntu1_BUILDING.txt.gz
[18:15] <The_LoudSpeaker> this is the correct one which is giving us trouble.
[18:16] <wxl> https://phab.lubuntu.me/rLIBLXQTPACKAGINGc87bb9a68e4af79e41f1ae65d2f50f8a854e172b
[18:18] <wxl> ^ did you see that raman? i already fixed it
[18:18] <The_LoudSpeaker> have exatly that opned in my browser rn.
[18:18] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/568/
[18:18] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libsysstat FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libsysstat/106/
[18:18] <The_LoudSpeaker> yeah as i said wxl, i pasted wrong link first time, pasted the one you had solved.
[18:18] <wxl> so debian is 3.6 on libqtxdg and we're on 3.5 so we need to do that
[18:18] <wxl> dude they're the same link XD
[18:19] <wxl> err wait
[18:19] <wxl> ok they're not XD
[18:19] <The_LoudSpeaker> bruh, i pasted earlier liblxqt related and now libfm related open both you will see
[18:19] <The_LoudSpeaker> XD
[18:19] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/569/
[18:20] <wxl> so this goes back to the conversation we had the other day. i'd make an arch specific file that resolves all the issues
[18:21] <The_LoudSpeaker> there is already. this error is in arch specific file only. we have to modify that file. delete lines from that.
[18:22] <wxl> yep
[18:22] <The_LoudSpeaker> will do this now. brb in 5mins.
[18:22]  * The_LoudSpeaker goes to fairyland
[18:22] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/221/
[18:22] <wxl> but we really should get qtxdg done first
[18:30] <The_LoudSpeaker> oh okay then
[18:32] <The_LoudSpeaker> is there a possiblity that the error which we are getting in libfm-qt is due t libqtxdg not present first?
[18:32] <wxl> it's remotely possible
[18:33] <wxl> however with it affecting s390x specifically, unlikely
[18:33] <The_LoudSpeaker> that's what i thought
[18:33] <The_LoudSpeaker> also, since this came from debian, where can I find s390x build logs of debian?
[18:33] <wxl> ehhhhhh
[18:34] <The_LoudSpeaker> they don't build?
[18:34] <wxl> i mean they have to right but i don't know where
[18:35] <The_LoudSpeaker> okay. i will ask in their channels lite.
[18:35] <kc2bez[m]> Debian buildd system is different
[18:35] <kc2bez[m]> It isn't weird to have something succeed there and not on Ubuntu
[18:36] <wxl> https://buildd.debian.org/status/package.php?p=libfm-qt&suite=sid
[18:36] <The_LoudSpeaker> what kind of action is "giveback"
[18:37] <wxl> looks like there were only warnings that there were new symbols, not any missing ones https://buildd.debian.org/status/fetch.php?pkg=libfm-qt&arch=s390x&ver=0.16.0-3&stamp=1610135380&raw=0
[18:38] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver just became unstable after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/362/
[18:38] <wxl> no clue XD
[18:38] <The_LoudSpeaker> also, who write build result as "maybe successful" ?
[18:38] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-powermanagement FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-powermanagement/594/
[18:38] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-powermanagement FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-powermanagement/594/
[18:39] <kc2bez[m]> I think all that is needed is to add the missing ones from the Ubuntu build log to the s390 architecture 🤷♂
[18:39]  * wxl shrugs
[18:39] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/607/
[18:39] <wxl> right added ones are a warning. missing ones are a problem.
[18:39] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/123/
[18:39] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-globalkeys just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_lxqt-globalkeys/102/
[18:39] <The_LoudSpeaker> kc2bez[m]: that was case with liblxqt too and wxl had removed them from symbols file.
[18:44]  * theloudspeaker sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/vRvkBzDQYOxduxtBafFVtWvA/message.txt >
[18:44] <kc2bez[m]> whoa
[18:44] <theloudspeaker> i have a bad feeling about these new symbols
[18:44] <kc2bez[m]> wrong spot
[18:45] <theloudspeaker> <kc2bez[m] "wrong spot"> it shows on irc like "posted a long message so..:P)
[18:45] <kc2bez[m]> I thought you were pasting it here instead of the symbols file ;)
[18:45] <theloudspeaker> XD
[18:46] <theloudspeaker> nah. these are on different desktops and I don't paste stuff like that into files.
[18:48] <theloudspeaker> also, about stuff I just pasted above, I am not sure if we should keep the ubuntu side line along with debian one.
[18:48] <theloudspeaker> that line was never there in debian sides
[18:48]  * theloudspeaker check ubuntu commit history
[18:49] <kc2bez[m]> follow debian
[18:49] <kc2bez[m]> add the missing symbols where you have MISSING: 0.16.0-3ubuntu1
[18:49] <theloudspeaker> looks like that line was added by tsimonq2
[18:50] <theloudspeaker> https://phab.lubuntu.me/rLIBQTXDGPACKAGING3941df2165af98dd6501ddb26160f86592285578
[18:50] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/369/
[18:50] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-runner just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_lxqt-runner/103/
[18:50] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_calamares just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_calamares/655/
[18:50] <kc2bez[m]> <kc2bez[m] "add the missing symbols where yo"> for the individual architecture
[18:51] <theloudspeaker> tsimonq2: tsimonq2 tsimonq2 ABI BREAK!! ABI BREAK!!
[18:51] <kc2bez[m]> then put it in a ppa and see if it builds
[18:51] <theloudspeaker> ▶
[18:51] <theloudspeaker> <kc2bez[m] "then put it in a ppa and see if "> yes. doing that.
[18:53] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-runner just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_lxqt-runner/103/
[18:57] <theloudspeaker> also, should I bump debhelper-compat? like debian didn't bump it. it's still on 12 for libqtxdg ?
[18:57] <theloudspeaker> wxl:
[18:57] <kc2bez[m]> you can, you just need to note it in the changelog
[18:57] <wxl> it's a good practice in general
[18:58] <theloudspeaker> so debhelper gets a bump.
[19:10] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/607/
[19:24] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/123/
[19:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/629/
[19:24] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal FAILURE: https://ci.lubuntu.me/job/groovy_stable_qterminal/425/
[19:24] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/133/
[19:25] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/386/
[19:36] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/607/
[19:36] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_qterminal/426/
[19:37] -lugito:#lubuntu-devel- [rLIBQTXDGPACKAGING5bee571317d1: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLIBQTXDGPACKAGING5bee571317d1
[19:52] <The_LoudSpeaker> ^ cc: wxl
[19:55] <wxl[m]> I probably would have commented about the symbol charges in the changelog
[19:57] <The_LoudSpeaker> arrey s390x failed again. it hadn't failed in my ppa.
[19:57] <The_LoudSpeaker> ooof! my ppa h=doesn't have all archs.
[19:57]  * The_LoudSpeaker facepalms
[19:58] <The_LoudSpeaker> wxl[m]: yes. will add that.
[20:05] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qps just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_qps/394/
[20:06] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/107/
[20:06] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/107/
[20:06] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/570/
[20:06] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/608/
[20:06] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/124/
[20:07] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/370/
[20:21] <The_LoudSpeaker> wxl[m]: how do I go about this: https://launchpadlibrarian.net/522525810/buildlog_ubuntu-hirsute-s390x.libqtxdg_3.6.0-1ubuntu1_BUILDING.txt.gz
[20:21] <The_LoudSpeaker> so I add that missing one right?
[20:22] <kc2bez> yup
[20:22] <kc2bez> Looks like only one there
[20:23]  * The_LoudSpeaker is super confused about this whole symbols thing.
[20:25] <The_LoudSpeaker> actually I have that line in the symbols file
[20:25] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-config/684/
[20:25] <The_LoudSpeaker> https://phab.lubuntu.me/source/libqtxdg/browse/ubuntu%252Fhirsute/debian/libqt5xdg3.symbols$152
[20:25] <The_LoudSpeaker> ^ kc2bez[m] wxl[m]
[20:25] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/570/
[20:26]  * The_LoudSpeaker tries to remove it an test.
[20:26] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/629/
[20:26] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/222/
[20:26] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/133/
[20:26] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/386/
[20:26] <wxl> yeah this is confusing
[20:27] <wxl> you want to disable it for s390x
[20:27] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libsysstat just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_libsysstat/107/
[20:27] <wxl> going back to what i did look here https://launchpadlibrarian.net/521180878/buildlog_ubuntu-hirsute-s390x.liblxqt_0.16.0-1ubuntu1_BUILDING.txt.gz
[20:27] <kc2bez> I don't see the missing one
[20:27] -lugito:#lubuntu-devel- [Lubuntu CI] merger_libqtxdg FAILURE: https://ci.lubuntu.me/job/merger_libqtxdg/716/
[20:27] <wxl> - (c++)"void std::vector<int, std::allocator<int> >::_M_realloc_insert<int>(__gnu_cxx::__normal_iterator<int*, std::vector<int, std::allocator<int> > >, int&&)@Base" 0.12.0
[20:27] <wxl> +#MISSING: 0.16.0-1ubuntu1# (c++)"void std::vector<int, std::allocator<int> >::_M_realloc_insert<int>(__gnu_cxx::__normal_iterator<int*, std::vector<int, std::allocator<int> > >, int&&)@Base" 0.12.0
[20:27] <wxl> if you ignore the #MISSING…# stuff you'll notice they're the same
[20:28] <wxl> and here's how i fixed it: https://phab.lubuntu.me/rLIBLXQTPACKAGINGc87bb9a68e4af79e41f1ae65d2f50f8a854e172b
[20:28] <wxl>  (arch=!s390x|c++)"void std::vector<int, std::allocator<int> >::_M_realloc_insert<int>(__gnu_cxx::__normal_iterator<int*, std::vector<int, std::allocator<int> > >, int&&)@Base" 0.12.0
[20:28] <wxl> so what you need is:
[20:28] <The_LoudSpeaker> i am doing exactly that rn
[20:29] <wxl>  (arch=!s390x)_ZNSt6vectorISt10unique_ptrI14XdgDesktopFileSt14default_deleteIS1_EESaIS4_EE17_M_realloc_insertIJS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base 3.6.0
[20:30] <kc2bez> The changelog should probably be fixed too even though it has been committed
[20:31] <wxl> …like my fix
[20:31] <wxl> tl;dr every change should be tracked in the changelog (duh)
[20:31] <kc2bez> If you look on phab aptghetto raised a concern
[20:31] <The_LoudSpeaker> yeah i will add that changelog entry with the s390x fix.
[20:32] <The_LoudSpeaker> apt-ghetto one is for old commit, i did not even touch that part. check my reply there. linked his commit
[20:33] <The_LoudSpeaker> kc2bez[m]: see this commit: https://phab.lubuntu.me/rLIBQTXDGPACKAGING66431d649f43dedc67633880999ae48df4c93331
[20:33] <kc2bez> I see what you mean but I think it wrong.
[20:34] <The_LoudSpeaker> eh?
[20:34] <The_LoudSpeaker> i don't think I understand what you are saying here.
[20:35] <wxl> i don't think i understand either of you XD
[20:36] <The_LoudSpeaker> basically, apt-ghetto raised a concern on my recent commit about his name in the changelog.
[20:36] <kc2bez> I think this commit https://phab.lubuntu.me/rLIBQTXDGPACKAGING66431d649f43dedc67633880999ae48df4c93331
[20:36] <kc2bez> got pushed to the wrong branch and committed to the archive
[20:36] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-powermanagement FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-powermanagement/594/
[20:38] <wxl> oy vey
[20:38] <The_LoudSpeaker> backports/focal is not correct ah?
[20:39] <kc2bez> ubuntu/groovy and ubuntu/hirsute are not correct
[20:39] <The_LoudSpeaker> ah.
[20:40] <The_LoudSpeaker> but not my fault right? my commit only has that symbols changelog entry missing. which i am fixing in next commit alongside the symbols file itself.
[20:41] <kc2bez> no it wasn't you Raman
[20:41] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_qterminal/426/
[20:41] <The_LoudSpeaker> :)
[20:42] <wxl> it would be nice to fix that, though
[20:43] <wxl> it could be as simple as just copying and pasting in the individual debian entry and then marking the error on the changelog
[20:43] <The_LoudSpeaker> send instructions
[20:43] <wxl> um
[20:43] <wxl>  1. vi debian/changelog
[20:43] <wxl>  2. done
[20:44] <The_LoudSpeaker> hahahaha
[20:44] <The_LoudSpeaker> on which branches and what to do in vi?
[20:44]  * The_LoudSpeaker cannot exit vi
[20:44] <kc2bez> look at the debian source for that chanelog entry
[20:44] <kc2bez> `:wq`
[20:45] <kc2bez> only worry about ubuntu/hirsute
[20:46] <wxl> https://stackoverflow.blog/2017/05/23/stack-overflow-helping-one-million-developers-exit-vim/
[20:47] <wxl> also ESC `ZZ`
[20:47] <kc2bez> ^
[20:48] <wxl> " escape is too far to reach…
[20:48] <wxl> imap jk <Esc>
[20:48] <wxl> " \ is dumb, too
[20:48] <wxl> let mapleader = ","
[20:48] <wxl> " ,, instead of ZZ
[20:48] <wxl> nnoremap <leader><leader> :xa<cr>
[20:48] <wxl> inoremap <leader><leader> <esc>:xa<cr>
[20:48] <wxl> ^ from my .vimrc
[20:49] <kc2bez> I get used to the defaults. I'm on too many boxes to remap anything.
[20:49] <The_LoudSpeaker> i totally understood each and every line of what you wrote here. ^ wxl
[20:49] <The_LoudSpeaker> :)
[20:49] <wxl> i use ,, with no escape
[20:50] <The_LoudSpeaker> finally!! https://launchpad.net/~theloudspeaker/+archive/ubuntu/devel-packages/+build/21013893
[20:50] <kc2bez> Many folks remap to caps lock too
[20:51] <wxl> good job raman
[20:51] <kc2bez> LGTM
[20:52] <wxl> i wonder if we don't need to do a no change rebuild on liblxqt
[20:52] <The_LoudSpeaker> now about that changelog thing, how do I fix it? just remove those entries from changelog?
[20:52] <wxl> yeah
[20:52] <The_LoudSpeaker> that it?
[20:52] <wxl> or maybe we should review that more later
[20:53] <The_LoudSpeaker> okay that seems good. apt-ghetto isn't around now so..
[20:55] <wxl> so now get going on libsysstat
[20:55] <wxl> :)
[20:55] <The_LoudSpeaker> should I bump the version number? or do a force push on this commit?
[20:56] <The_LoudSpeaker> bump right? but people in debian prefer force pushes. they are like helps keep history clean.
[20:56] <kc2bez> You should bump the ubuntu version and note the adjustments you made
[20:57] <kc2bez> versions are cheap
[20:57] <The_LoudSpeaker> i am like what you are gonna do of a clean history on a forked repo. clean it while merging with main na.
[20:58] <The_LoudSpeaker> kc2bez: aye. did exactly that but thought if a force push would be okay.
[20:58] <kc2bez> I think it is discouraged
[20:59] <The_LoudSpeaker> wxl you are talking about this symbols file only right? https://phab.lubuntu.me/rLIBQTXDGPACKAGING5bee571317d1276c0c776e4f4a7d469eff9d50de#change-bZfPbO6MrVIO
[20:59] <The_LoudSpeaker> which i missed in dchangelog?
[21:00] <The_LoudSpeaker> this one came from debian so i thought new upstream version covers it?
[21:00] <kc2bez> Yeah but you added something right?
[21:00] <kc2bez> Like "Updated symbols." is good
[21:01] <kc2bez> If you add or remove any
[21:01] <The_LoudSpeaker> okay.
[21:01] <kc2bez> If it is a straight merge it should be noted upstream
[21:01] <kc2bez> It is only necessary to document your changes whatever they are.
[21:02] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-powermanagement just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-powermanagement/595/
[21:02] <kc2bez> Time for the meeting.
[21:02] <KGIII> I am here.
[21:02] <kc2bez> !standup
 Here
[21:03] <lynorian> \o
[21:03] <The_LoudSpeaker> o/
[21:05] <kc2bez> ack KGIII @Leokolb lynorian The_LoudSpeaker
[21:05] <KGIII> I might get interrupted so I've gotta go early.
[21:05] -lugito:#lubuntu-devel- [rLIBQTXDGPACKAGING15fb18d36992: Fixed s390x errors and previous changelog entry] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLIBQTXDGPACKAGING15fb18d36992
[21:05] <kc2bez> ok
[21:05] <KGIII> This week, I've been able to continue daily testing and had some time to do a little support. I'm still monitoring the triage process and reading everything in sight. Because 21.04 is soon to be released, I've been making it a point to actually use the OS after doing the testing. My longest test was about 3 hours of normal use and it's looking pretty solid. I'll preemptively thank everyone and I am done.
[21:05] <kc2bez> Thanks KGIII
[21:05]  * guiverc present now too
[21:05] <The_LoudSpeaker> Thanks! KGIII
 thanks KGIII
[21:06] <kc2bez> ack guiverc
[21:06] <The_LoudSpeaker> hola guiverc!
[21:06] <kc2bez> ok, @Leokolb over to you
 Tested Hirsute dailies & also tested T58 minimum install - no major issues - done
[21:07] <kc2bez> Thanks for the testing.
[21:07] <kc2bez> lynorian: is next
[21:09] <lynorian> I edited the prefrences of vlc in the manual and also edited the prefrences for lxqt-runner and htop
[21:10] <lynorian> found a few features in vlc I had not docuemnted
[21:10] <lynorian> that is what I did
[21:11] <kc2bez> Nice, thanks lynorian !
[21:11] <kc2bez> The_LoudSpeaker: over to you
[21:12] <theloudspeaker> o/
[21:12] <theloudspeaker> since last week:
[21:12] <theloudspeaker> updated libqtxdg
[21:13] <theloudspeaker> working on libfm-qt's s390x and libsysstat rn
[21:13] <kc2bez> cool
[21:13] <theloudspeaker> that's it.
[21:13] <kc2bez> Thanks for working on those!
[21:14] <kc2bez> guiverc: What is new?
[21:14]  * theloudspeaker is waiting for my younger brother to send back my old laptop so that I can help with testing.
[21:14] <guiverc> - usual support, some testing (no issues with 'force append' 1864787 or really 1914521 on hirsute, but will continue testing; esp. on 755-5 as I've mainly used 755-8 thus far)
[21:14] <guiverc> - minor discussion on lxqt with yan12125 re: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1905947 or display.config not surviving logout/reboot who noted it's Qt that crashes (not LXQt) ..  I'm unsure what to do with this, but any clues most welcome  (do we cross fingers & hope it's resolved, or how to further explore?)
[21:14] <guiverc> nothing else I remember
[21:15] <kc2bez> We might want to wait until we get things merged for 1905947
[21:15] <kc2bez> It might be resolved
[21:15]  * guiverc has fingers crossed
[21:15] <kc2bez> same
[21:16] <kc2bez> At the very least the package will see a rebuild and compile
[21:16] <kc2bez> Thanks for working on that guiverc
[21:17] <kc2bez> I guess that leaves me.
[21:17] <kc2bez> worked on getting https://discourse.lubuntu.me/t/development-for-the-week-of-february-5-11-2021/2167?u=kc2bez setup
[21:17] <kc2bez> hopefully we can use that for a template and add to it for future meetings.
[21:18] <kc2bez> worked with wxl to ceeate rQLIPPER repository.
[21:18] <kc2bez> i finished out some final release tasks for 20.04.2
[21:18] <guiverc> development for week looks great kc2bez
 +1
[21:18] <kc2bez> We should be filling that in as we go.
[21:18] <kc2bez> !itsawiki
[21:18] <kc2bez> :D
[21:19] <guiverc> yep & ack.
[21:19] <kc2bez> of note: main Ubuntu and any flavor using ubiquity had to do a respin. There was an issue with OEM installs.
[21:19] <kc2bez> synced rLIBQTXDGPACKAGING with the archive in preparation for the Debian merge
[21:19] <kc2bez> We will want to make sure that is done on every package before we begin the merge process.
[21:20] <kc2bez> Lubuntu Council nomination period is set to end this week. I hope to get emails to the Members this weekend.
[21:20] <kc2bez> That is all I have for this week.
 thanks everyone
[21:21] <kc2bez> Anyone else, anywhere else? Questions?
[21:22] <theloudspeaker> yup
[21:22] <kc2bez> go ahead
[21:22] <theloudspeaker> should I update debian/.gitignore too?
[21:22] <guiverc> thanks Dan..   Your effort is appreciated, as is everyones.
[21:22] <theloudspeaker> many times it is updated.
[21:23] <kc2bez> which package?
[21:23] <The_LoudSpeaker> almost every one which we have merged.
[21:23] <The_LoudSpeaker> tehy havea  debian/.gitignore
[21:23] <The_LoudSpeaker> we don't
[21:23] <The_LoudSpeaker> ** they have a
[21:23] <kc2bez> then no
[21:23] <The_LoudSpeaker> okay.
[21:24] <KGIII> There, caught up. You're welcome all and, again, thanks everyone. Y'all make Lubuntu awesome.
[21:24] <kc2bez> Thanks everyone for meeting!
[21:24] <wxl> oh hey
[21:24] <kc2bez> Oh hey
[21:24] <wxl> sorry chaos over here
[21:24] <kc2bez> to the front of the line you go
[21:24] <kc2bez> XD
[21:24] <wxl> here's my paste; not a lot done really https://paste.ubuntu.com/p/26V64jJ7qJ/
[21:25] <kc2bez> ummm
[21:25] <wxl> basically i went down a big qlipper rabbit hole
[21:25] <kc2bez> it was fun in a sleep deprived sort of way
[21:25] <wxl> hehehe
[21:26] <kc2bez> wxl: at some point we need to get a handle on github syncing
[21:26] <wxl> yeah i know
[21:26] <kc2bez> ok
[21:26] -lugito:#lubuntu-devel- [Lubuntu CI] merger_libqtxdg FAILURE: https://ci.lubuntu.me/job/merger_libqtxdg/717/
[21:26] <kc2bez> Just didn't want to lose sight of it
[21:26] <wxl> we also have to make sure phab and the archive are synced
[21:27] <wxl> it is possible for things to end up on the archive that don't end up in phab
[21:27] <kc2bez> Yes
[21:27] <wxl> i mean i guess the opposite is possible too
[21:27] <kc2bez> I don't know how we avoid that without some notification for all the packages we have
[21:28] <kc2bez> It could be a daily check of some sort I suppose
[21:28] <wxl> though phab is a mirror of launchpad repos, neither of them are actual archives which are not actually git repos
[21:28] <kc2bez> right
[21:28] <wxl> i think we could automate
[21:28] <wxl> in any case looking into the near future we really really really really really need to get these merges done
[21:28] <kc2bez> noted
[21:29] <wxl> it might not be a good idea to create a best practices doc for merging to perhaps allow others to help out
[21:29] <The_LoudSpeaker> libsysstat_0.4.4-1ubuntu1_source.changes in a ppa now
[21:30] <kc2bez> Yeah, like the one we did for adding a repo
[21:30] <wxl> yep
[21:30] <wxl> so let's put our heads together on that
[21:30] <kc2bez> yup, theloudspeaker too since he has done a bunch
[21:30] <wxl> +1
[21:31] <wxl> like everything in packaging there are different approaches so having an SOP that people can deviate from is a good idea
[21:31] <The_LoudSpeaker> i will prepare a notes.lubuntu.me paste which has my steps for merges.
[21:31] <kc2bez> Nice
[21:32] <wxl> great! thank you
[21:32] <kc2bez> Throw a link to it in the task
[21:32] <The_LoudSpeaker> https://launchpad.net/~theloudspeaker/+archive/ubuntu/devel-packages/+build/21014032
[21:32] <The_LoudSpeaker> pushing now
[21:32] <wxl> i'd aim for an overview like the packaging tutorial rather than an enormous document
[21:33] <wxl> wow raman is our new s390x expert XD
[21:33] <The_LoudSpeaker> XD
[21:33] <kc2bez> We need to get him a s390 for the house
[21:33] <The_LoudSpeaker> if anyone asks me what to do about s390x I am gonna point then to a paste that has only one line: Follow what wxl did.
[21:34] <kc2bez> Anything else wxl ?
[21:34] <The_LoudSpeaker> kc2bez: yeah please. that would be awesome. I have never used s390x. would be fun. used all arm achitecures and 32/64 bit ones but s390x is something else only.
[21:35] <wxl> hahah no
[21:35] <kc2bez> ok
[21:35] <wxl> one other thing: does anyone else need any help?
[21:35] <kc2bez> It would be cool to have someone run through T58 test. I can get that uploaded if we are ok with it.
[21:36] <wxl> i'll get to that relatively soon
[21:36] <kc2bez> I know Leo did but another might be nice
[21:36] <kc2bez> sounds good
[21:36] <wxl> that's a good task for anyone really, though
[21:36] <kc2bez> yes
[21:37]  * guiverc reading t58
[21:37] -lugito:#lubuntu-devel- [rLIBSYSSTATPACKAGING11e1b104a5f4: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLIBSYSSTATPACKAGING11e1b104a5f4
[21:37] <kc2bez> It actually takes longer to install because we remove a slew of packages that we copy over
 i have done several further tests on T58 as well
[21:37] <kc2bez> cool
[21:38] <kc2bez> Once done it is snappy to boot though
 very fast..
[21:38] <guiverc> I'll endeavour to test it.. but currently worried I'll not get around to it, so feel free to remind me
[21:38] <kc2bez> no worries
[21:38] <wxl> @KGIII: ^ that might be a good one for you, too
[21:39] <wxl> keep going raman!
[21:39] <KGIII> Got a direct link to this T58 critter? That's the one where you start the live ISO, add a repo, and then do a minimum installation?
[21:39] <wxl> isn't libfm-qt done?
[21:39] <guiverc> https://phab.lubuntu.me/T58 KGIII
[21:39] -lugito:#lubuntu-devel- [Medium, Open] consider minimal install: https://phab.lubuntu.me/T58
[21:40] <guiverc> & yep KGIII
[21:40] <kc2bez> did it build wxl
[21:40] <The_LoudSpeaker> i will take leave now. pretty much satisfied with the work we got in today. 2 merges. Although I ended up scrolling fb for an hour when I was booting my pc and was late to start. :P
[21:40] <wxl> add the repo and update the package :)
[21:40] <KGIII> I may be quiet, but that doesn't mean I'm not paying attention. ;-)
[21:40] <wxl> good job raman! let's do it without social media next time!
[21:41] <KGIII> I'll see if I can get a test done this evening. Will someone be around if I have questions?
[21:41] <kc2bez> LoL
[21:41] <kc2bez> sure will
[21:41] <KGIII> Alright. I'll check it out after dinner.
[21:41] <wxl> i'm generally around and if you ping me i'll pick it up on the phone if not
[21:41] <kc2bez> same here
[21:41] <The_LoudSpeaker> i already uninstalled fb. such occurences have been increasing lately.
[21:42] <wxl> there's an fb appliccation???
[21:42] <kc2bez> for the phone, yeah
[21:42] <The_LoudSpeaker> yes you old potato
[21:42] <wxl> i deleted facebook so long ago i don't even remember
[21:43] <kc2bez> First app I removed on my phone XD
[21:43] <wxl> alright well good meet all and thanks for the hard work
[21:44] <kc2bez> thanks to you as well wxl
[21:44] <wxl> np
[21:45] <KGIII> This is the correct PPA: https://launchpad.net/~kc2bez/+archive/ubuntu/testing
[21:45] <kc2bez> yes
[21:45] <KGIII> So, add that, update, and then install and pick minimal install?
[21:45] <kc2bez> yup, that should do it
[21:46] <KGIII> That won't be a problem. I'll do a test tonight.
[21:46] <kc2bez> A regular install might be good too just for sanity
[21:46] <KGIII> I can do both. I will have time.
[21:46] <kc2bez> Fantastic
[21:47] <KGIII> Where do I report my findings?
[21:47] <wxl> on the task
[21:47] <wxl> like leo did
[21:47] <KGIII> Excellent. Just making sure.
[21:47] -lugito:#lubuntu-devel- [T187: Lubuntu 20.04.2] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T187#4239
[21:47] <guiverc> thank you KGIII (and thank you @Leokolb for already testing it!)
[21:48] <KGIII> No problem.
[21:49] <KGIII> When I started, I agreed to test *just* 21.04 for the duration of the testing process. Methinks I'll stick around a while longer. I am learning a lot and it's kinda fun.
[21:49] <guiverc> :)
[21:49] <wxl> glad you're enjoying yourself KGIII :)
[21:49] <KGIII> I enjoy learning new things and trying new things. So, it's all good.
[21:50] <kc2bez> That is great, it is good to have you here. It really does help.
[21:52] <KGIII> You don't need to butter me up, I already said I'd test it! ;-)
[21:52] <kc2bez> hahaha
[21:53] <kc2bez> I wasn't :D
[21:53] <KGIII> LOL I'll get to it after dinner. It'll give me something to do. The wife is used to me poking buttons for long hours. Speaking of dinner, I should probably start making it.
[22:08] -lugito:#lubuntu-devel- [Lubuntu CI] merger_libqtxdg FAILURE: https://ci.lubuntu.me/job/merger_libqtxdg/718/
[22:09] <KGIII> So far so good. Meaning I got the missus to make dinner. I do the overwhelming majority of cooking. I enjoy it.
[22:12] <KGIII> Silly question... Would this minimal install work for 20.04?
[22:13] <kc2bez> I think so, maybe.
[22:13] <KGIII> I may have to test that on bare metal. I am still not upgraded beyond 18.04 on my two main systems. Yes, I know my shame...
[22:14] <kc2bez> Well, it would have to be repackaged for focal
[22:14] <KGIII> Hmm... Well, if it works and you ever get time... Though I should probably do full installs so that I can support people better, now that I think about it.
[22:15] <kc2bez> but the basics just remove a list of packages it could be done on a first boot too
[22:15] <kc2bez> It actually purges them and does an autoremove
[22:15] <KGIII> I'm doing the first reboot after the minimal install.
[22:16] <kc2bez> cool
[22:16] <KGIII> Ah, that's one way of doing it.
[22:16] <kc2bez> Nukes it from orbit so to speak
[22:16] <kc2bez> XD
[22:17] <KGIII> So far so good.
[22:17] <kc2bez> nice that sounds promising
[22:18] <KGIII> You want a full install test done as well?
[22:19] <kc2bez> It might be good, just to make sure I didn't botch something there.
[22:19] <KGIII> Gotcha... Gimme a few minutes.
[22:19] <kc2bez> It should be fine but...
[22:22] <kc2bez> wxl: do we want a new post for the new development week? I think yes but I want to see what you think.
[22:23] <wxl> yeah we should
[22:23] <kc2bez> Perfect, I will get on it
[22:24] <wxl> thx
[22:24] <KGIII> It is a little unclear. To do a full install - just do NOT select minimum install?
[22:25] <kc2bez> Ok, i was wondering how we felt about that. Yes, to answer your question.
[22:26] <kc2bez> I shall endeavor to find a more concise way to get through that
[22:27] <KGIII> It's a little unclear. I guessed right, but that was a guess. Some text saying, "Make no selection to do a full install" might work.
[22:27] <kc2bez> Yup, I will see where I can add something like that.
[22:27] <KGIII> It's zooming right along doing the full install as we speak.
[22:28] <wxl> wow that surfacego problem worked out THANK GOD XD
[22:28] <kc2bez> Amazing, those are a pain in Linux.
[22:29] <wxl> i'm shocked, amazed and delighted that a total linux noob (i had to explain case sensitivity) was able to figure that out
[22:30] <kc2bez> It is the sort of experience that will keep them around though.
[22:30] <wxl> thing is what is killernetworking.com?????
[22:31] <wxl> oh it's actually the manufacturer? bizarre
[22:31] <kc2bez> Interesting
[22:32] <wxl> i guess it's just some fancy branding on top of a qualcomm atheros chip
[22:32] <wxl> or something
[22:32] <wxl> cuz lspci doesn't report anything odd
[22:33] <kc2bez> I wonder if it is USB
[22:34] -lugito:#lubuntu-devel- [T58: consider minimal install] KGIII (David G) commented on the task: https://phab.lubuntu.me/T58#4241
[22:34] <KGIII> It's an 80/20 split. 80% of the time I know what you're talking about. 20% of the time I'm pretty sure you're speaking gibberish! Anyhow, both test were successful with satisfactory results.
[22:35] <KGIII> Now that I know how to do it, feel free to ping me again if you need more testing.
[22:35] <kc2bez> Thanks KGIII
[22:36] <KGIII> 'Snot a problem. It doesn't take too long to test them both, much less time than to do the daily live testing. With the live testing, I open everything and check everything. That can eat up some time. This isn't so time consuming.
[22:36] <wxl> KGIII: i think we want to be as user-friendly as possible so if you feel like you don't understand something, that may be an indication of something we need to fix, so please point it out!
[22:37] <kc2bez> Absolutely, I will make some adjustments based on your feedback. That really helps.
[22:38] <KGIII> Will do, though I try to not interrupt. I'm here far more often than you might think - I just don't say anything. Or at least i flip over here and catch up with what was said.
[22:38] <KGIII> I think next week I'm going to learn more about packaging. I even have a project in mind.
[22:47] <wxl> nice!
[22:48] <wxl> the best thing to do is start with some little test package and put it in a ppa.
[22:48] <wxl> that way you don't need any special access to upload and you can't screw anything up
[22:48] <wxl> plus if you start simple, the better
[22:49] <wxl> there's a couple packages that are good examples here, like hello-world or anarchism
[22:49] <wxl> !info anarchism
[22:49] <wxl> ^ it's just text, really
[22:51] <KGIII> Hmm... Thanks, I'll probably have a ton of questions. I figure I'll *try* to package and maintain a package for Midori. Though I'd double check. The last time I looked there wasn't one being maintained. I don't even use the browser, but it's always simple to build and seemed like a helpful thing to package.
[22:51] <KGIII> Should I ask the devs if they care if I package it?
[22:52] <KGIII> It's opensource, after all. I figure I can do that if I want to.
[23:01] <wxl> they won't care if you do
[23:01] <wxl> i'm sure you already know midori is in the repos and that you just want something to cut your teeth on
[23:04] <KGIII> Yup, though the one in the repo is pretty much never the current version - or historically hasn't been.
[23:04] <KGIII> I figure it's a simple project, plus it's never the right version. They sporadically (or someone sporadically) will update it and keep it updated for a little while and then it gets forgotten again.
[23:06] <wxl> i can't quite figure it out
[23:07] <wxl> oh nevermind i think i got it
[23:07] <wxl> they're on 9
[23:07] <wxl> we're on 7
[23:07] <wxl> and so is debian
[23:07] <KGIII> Yeah, it's never/seldom the most updated version. It's also sporadic, like they care for a little while and then just forget about it.
[23:08] <KGIII> So, it'll make a nice little PPA for me to practice with.
[23:08] <wxl> the last upload was from someone who wasn't the maintainer about a year after the maintainer  did a version
[23:09] <wxl> i will say you will likely run into some challenges
[23:09] <wxl> you really might want to start simple first
[23:09] <KGIII> LOL More simple than that?
[23:09] <wxl> like i said, going with something that doesn't even need to be compiled would give you a really good idea of the basics of packaging
[23:10] <wxl> and then you can do an actual piece of software and run into all the other caveats :)
[23:10] <KGIII> Ah, alright. Well, I'll try the anarchism first and see how that goes.
[23:10] <wxl> it's important to remember that packages are a lot of things but one of the things they are is automated compilation instructions and if you've done any sort of compiling you know you can run into all sorts of fun stuff
[23:11] <KGIII> That's why I picked Midori - it compiles easily and I've never had an issue compiling it.
[23:11] <wxl> luckily you don't need to make a brand new package from scratch. that's a lot harder. but still
[23:11] <wxl> the debian policy manual is your friend. you can find the answer to (most) questions there
[23:12] <KGIII> Oh, man... That's a lot of reading.
[23:12] <KGIII> I still haven't finished the freedesktop stuff. :/
[23:12] <kc2bez[m]> policy manual is good reading, tough to put it down
[23:13] <KGIII> LOL I'll add it to my to-read list.
[23:13]  * KGIII sighs
[23:13] <kc2bez[m]> Lol
[23:13] <KGIII> It's a good thing I bought a giant external drive for Lubuntu stuff.
[23:14] <wxl> hehehe
[23:15] <KGIII> Alright, it's time to eat. I'll probably return.
[23:15] <wxl> i would look at the debian policy manual like the constitution. you can do pretty well with a general understanding, but every now and then you really need to read the fine print and think carefully.
[23:15] <wxl> and, of course, it's ALWAYS better if you know it inside and out, but that may be asking a lot.
[23:18] <kc2bez[m]> It is like most "reference" material. After you get the hang of it you know where to find what you are looking for.
[23:53] <guiverc> thanks KGIII for all your thorough testing !


[06:38] <mihir> Good Morning guys :)
[07:15] <dholbach> good morning
[07:17] <chrisp> I'm working on a qml app for Ubuntu Touch with a C++ backend relying on gcrypt. It works well on the desktop but won't compile using the device kits due to the missing gcrypt.h header file (a shared object gcrypt library is available in the device kits but the header file is missing). Is there a way to add the header files needed for compilation to the kits on my machine or is the preferred way shipping my own version of gcrypt
[09:07] <JamesTait> Good morning all; happy Monday, and happy Emma M Nutt Day! :-D
[09:50] <justCarakas> good morning JamesTait
[09:52] <JamesTait> justCarakas, o/
[10:18] <dholbach> popey, is stock ticker still being updated?
[10:18] <dholbach> popey, it needs to use a newer framework to be accepted
[10:19] <popey> dholbach: no, its not in the image any longer.
[10:19] <dholbach> ah ok
[12:32] <nik90_> popey: [12:33] <popey> kk
[13:00] <popey> nik90_: left a comment
[13:01]  * nik90_ looks
[13:05] <nik90_> rpadovani: if you have time, can you review https://code.launchpad.net/~nik90/ubuntu-clock-app/onetime-alarms/+merge/232519
[13:05]  * nik90_ goes for lunch, brb
[13:19] <popey> zbenjamin: dunno if you're aware but when installing clicks to device the log gets spammed by the animations done in pkcon... http://paste.ubuntu.com/8206179/
[13:19] <popey> any way we can make pkcon be a bit less animated?
[13:19] <popey> zbenjamin: looks like you already do -p, but it's still a bit shouty
[13:22] <zbenjamin> popey: yeah we can do that
[13:25] <rpadovani> nik90_, until dinner I'll do :-(
[13:25] <rpadovani> *:-)
[13:50] <dholbach> davidcalle, salut mon ami - comment ça va?
[13:51] <davidcalle> dholbach, bien et toi?
[13:51] <dholbach> très bien - merci!
[13:51] <dholbach> qu'est-ce qui se passe en France? :)
[13:53] <davidcalle> dholbach, emulators are being launched and destroyed :)
[13:53] <dholbach> haha, great :)
[14:00] <nik90_> rpadovani: cool
[14:16] <ogra_> DanChapman, hmm, not sure if you actually wnated to send two mails ? (i got a private reply with onyl my original mail as quote in it)
[14:18] <DanChapman> ogra_, yeah I've just seen that :-/ Sorry about that. Hmmm that shouldn't have happened
[14:19] <ogra_> DanChapman, no worries, happy to be a guineapig ... go on if you need to :)
[14:19] <DanChapman> ogra_, :-) thanks
[14:19] <dholbach> beuno, thanks for the review - did you check the prerequisite branch too? (mostly just wrapping all the functions into a class)
[14:20] <beuno> dholbach, have it open, didn't quite get that they were linked
[14:20] <beuno> will get to it soon
[14:20]  * dholbach hugs beuno
[14:21] <t1mp> nik90_: wow, the startup animation for the clock-app is very cool :)
[14:21] <dholbach> zbenjamin, or https://code.launchpad.net/~dholbach/click-reviewers-tools/1363857/+merge/232864 I requested a review from you too, just so you can check if the output format generally makes sense to you
[14:22] <nik90_> t1mp: thnx, it is a bit laggy atm when the alarm model is loaded, but I have a fix for it in a branch waiting to land.
[14:23] <dholbach> zbenjamin, sorry, meant to say "for https://code...... I requested..."
[14:30] <nik90_> renatu: hey, I need your help with bug 1362081
[14:31] <nik90_> renatu: Looking through the bottom edge component, you basically load the page in a sequential animation once the bottomEdge.y has reached its target value.
[14:31] <nik90_> renatu: would I able to do this when it reach 0.75% of the page height instead?
[14:32] <renatu> nik90_, yes you can change the code
[14:32] <zbenjamin> dholbach: sure
[14:33] <nik90_> renatu: so would calling page._pushPage() at 0.75 % of the page height suffice? Or would it appear out of nowhere?
[14:33] <zbenjamin> dholbach: can i run the script without installing the package?
[14:33] <t1mp> artmello__: I like the updates to gallery-app. I only get a lot of these warnings: file:///home/tim/dev/gallery-app/gallery-app-new_header/rc/qml/MediaViewer/GalleryPhotoComponent.qml:111:21: Unable to assign double to QSize
[14:33] <dholbach> zbenjamin, yes, just branch it, run ./bin/click-review <.click file>
[14:34] <renatu> nik90_, I do not known what this will cause, the SDK Page stack is very sensible , you will need to try
[14:34] <renatu> nik90_, we have several problems on bottom edge due the way that pagestack works
[14:34] <nik90_> renatu: ah :/
[14:35] <zbenjamin> dholbach: is there some sort of seperator between the objects?
[14:36] <zbenjamin> dholbach: or do i need to write a incremental parser for that , i guess i will just receive a stream of text
[14:36] <renatu> nik90_, the only way to test is trying :D
[14:36] <dholbach> zbenjamin, the output doesn't need to be json if that doesn't suit you - I can use something else as well
[14:36] <dholbach> zbenjamin, we can make the output format whatever you like it to be
[14:36] <renatu> nik90_, I think this will cause a very strange visual
[14:36] <nik90_> renatu: yeah since the page will be pushed on top of the bottom edge rectangle
[14:37] <nik90_> renatu: so it will have a rather abrupt transition
[14:37] <renatu> yes
[14:37] <renatu> the header will appear without any animation
[14:37] <renatu> we can not control that
[14:37] <renatu> this is how pagestack works
[14:37] <t1mp> renatu, nik90_ that page._pushPage() function is not in the UITK PageStack. To the pagestack you either push a page or you don't
[14:37] <nik90_> renatu: well that we can control atm by changing the page title from " " to "somevalue"
[14:38] <renatu> nik90_, yes but this will make the header to appear
[14:38] <zbenjamin> dholbach: ok, well we could reuse the old format where this would show the start of a new section:   = click-check-scope =
[14:38] <zbenjamin> dholbach: i will use the text between = =  as the heading for the test element
[14:38] <renatu> t1mp, this function only does some preparation to call the pageStack.push
[14:38] <dholbach> zbenjamin, sure, let me add that
[14:39] <renatu> nik90_, you need to set the title at the same time that you push the page
[14:39] <renatu> nik90_, the problem is that they are different pages, and contains different headers
[14:40] <nik90_> renatu: welll for me the clock page doesn't have a header which is the root cause of the bug
[14:40] <dholbach> zbenjamin, if you pull again, let me know if that works
[14:41] <renatu> nik90_, yes but at the moment you call the pagestack.push(new_page) the new header should appears
[14:41] <nik90_> renatu: so I was thinking when bottom edge is at 75% page height -> push page with title which will cause the header to slide down and meet the bottom edge
[14:41] <renatu> yes
[14:41] <renatu> does htat
[14:41] <renatu> does that
[14:41] <renatu> but the header will not slide down
[14:41] <renatu> it will appear
[14:42] <nik90_> true
[14:42] <nik90_> no animations
[14:43] <renatu> nik90_, and I do not know how this will look like you need to try to see
[14:43] <renatu> I think this will be very ugly
[14:43] <nik90_> yeah I am trying although I am not optimistic
[14:43] <zbenjamin> dholbach: looks good, only question i have is if it makes sense to have the header 2 times in the output, for example functional is in the header and in the object
[14:43] <nik90_> I think the bug will be post-rtm in that case
[14:43] <artmello__> t1mp: yep, those warning were there before but seems to be more frequent with the new header
[14:43] <dholbach> zbenjamin, ah ok, let me see
[14:43] <zbenjamin> dholbach: or could a top level object have mutliple atrributes
[14:44] <dholbach> sure sure
[14:46] <dholbach> zbenjamin, try again?
[14:47] <zbenjamin> dholbach: perfect, looks like we basically have the same output now
[14:48] <dholbach> it doesn't show stuff like "click-show-files", etc
[14:48] <zbenjamin> exactly we just need the tests
[14:48] <dholbach> so just actual test results of the individual modules of clickreviews
[14:48] <dholbach> ok
[14:48] <dholbach> so I guess you're all set? :)
[14:48] <dholbach> zbenjamin, not sure if you checked the return codes before?
[14:49] <dholbach> in any case you should have 0 (pass) and 1 (FAIL) as ret codes now
[14:49] <zbenjamin> let me see
[14:52] <zbenjamin> dholbach: doesn't look like it
[14:52] <dholbach> ok
[14:52] <zbenjamin> dholbach: are you exiting with != 0 when there was a error?
[14:52] <dholbach> yes
[14:52] <zbenjamin> dholbach: that should be enough
[14:52] <dholbach> ok
[14:53] <zbenjamin> dholbach: approved
[14:53] <dholbach> zbenjamin, awesome
[14:54] <dholbach> now I just need somebody to review the prerequisite branch: https://code.launchpad.net/~dholbach/click-reviewers-tools/click-review-refactor/+merge/232861 :)
[15:00] <nik90_> t1mp: Do you know where I find the header divider that you implemented? I am going to create a fake header.
[15:00] <nik90_> t1mp: the fake header will slide in from the top with the bottom edge component. Once the bottom edge component is fully expanded, I will hide the fake header and show the normal page header
[15:01] <t1mp> nik90_: the code for that is part of PageHeadStyle.qml (there are two files named that, check them both) in lp:ubuntu-ui-toolkit
[15:01] <nik90_> t1mp: ack. thnx
[15:03] <t1mp> nik90_: I have an item at the bottom of my TODO list, that says to replace the current divider visuals by a 5% opacity black rectangle
[15:03] <t1mp> nik90_: I won't get to that todo item very soon, but eventually the divider code may be simplified a bit
[15:03] <nik90_> t1mp: before or post rtm?
[15:03] <t1mp> just fyi :)
[15:04] <nik90_> t1mp: if it is post rtm, I will use the current implementation
[15:04] <t1mp> nik90_: post. But what I tried to say is that maybe with some simple code it is possible to create something better-looking than what we have right now
[15:04] <t1mp> nik90_: sure
[15:04] <nik90_> ah ok :)
[15:04] <t1mp> nik90_: actually.. unity8 uses the PageHeadStyle to get the UITK header contents inside a custom header of which they control the show/hide
[15:05] <t1mp> nik90_: I don't know any details, but it is somewhere in the unity8 project
[15:05] <t1mp> nik90_: you can use a StyledItem with style: Theme.createStyleComponent("PageHeadStyle.qml", header)
[15:05] <t1mp> mzanetti ^ knows more about that
[15:06] <t1mp> nik90_: when you have an app with custom header, let me know and I can review the code and double-check that I don't break the app when changing the header style :)
[15:06]  * mzanetti looks into the blue^Cgrey sky
[15:07] <nik90_> t1mp: it is for the clock app :/ will do so
[15:07] <t1mp> mzanetti: I just pointed nik90_ to unity8 for custom header with UITK styling
[15:09] <mzanetti> t1mp: hah. speaking of which, using a Page with it's header, how can I make it slide in/out?
[15:09] <mzanetti> wanted to do that yesterday and failed
[15:10] <nik90_> mzanetti: you can't. that's the issue I am facing due to which i need to create a fake header
[15:10] <nik90_> mzanetti: you need to set title to "" to hide it. But it appears without any slide in animation
[15:12] <mzanetti> ah... ok
[15:12] <mzanetti> wah! why is the terminal all pink?
[15:12] <davmor2> mzanetti: so you like it more
[15:13] <mzanetti> :D
[15:13] <davmor2> mzanetti: settings and flick of the retro terminal option and then it is back to black iirc
[15:14] <mzanetti> seems to be caused by the "Enable effects:" setting
[15:14] <mzanetti> what's that supposed to do?
[15:14] <davmor2> mzanetti: blame popey (tm)
[15:14] <ogra_> "did you blame your popey today ?"
[15:15]  * mzanetti blames popey
[15:15] <popey> mzanetti: https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1363414
[15:15] <mzanetti> aha!
[15:15] <mzanetti> thanks popey :)
[15:15] <popey> np
[15:15] <popey> its being worked on
[15:15] <t1mp> mzanetti, nik90_ can you report a bug for the sliding in/out of the header?
[15:15] <popey> difficult because the developer doesn't have that device
[15:15] <popey> </record type=broken>
[15:16] <ogra_> and the approver didnt either when it landed ;)
[15:16] <popey> indeed
[15:16] <popey> fixed that bug
[15:16] <popey> in fact the devloper has no device at all, is using the emulator
[15:16] <mzanetti> lol
[15:17]  * mzanetti sees the effects for the first time
[15:17] <popey> that one is in progress
[15:17] <ogra_> they look shiny on first sight but i find them annoying after a while
[15:18] <mzanetti> ogra_: I guess I agree
[15:19] <popey> yeah, its a bit of fun
[15:19] <popey> might default off in the future
[15:20] <mzanetti> popey: the settings page is borked too
[15:20] <popey> how so?
[15:21] <popey> it doesn't save between sessions?
[15:21] <mzanetti> popey: when the color schema option is collapsed, there's empty space at the end of the list
[15:21] <mzanetti> when its expanded the page doesn't fit
[15:21] <popey> mzanetti: https://bugs.launchpad.net/ubuntu-terminal-app/+filebug ☻
[15:22]  * mzanetti is busy flying his AR.Drone using the Ubuntu phone
[15:22] <popey> "busy"
[15:22] <mzanetti> :D
[15:22] <mzanetti> popey: will file the bug :)
[15:23] <davmor2> wow did mzanetti just create a popey bug bot when I wasn't looking?
[15:24] <mzanetti> I wish
[15:25] <dholbach> beuno, zbenjamin: thanks for the reviews - changes pushed to bzr
[15:25] <zbenjamin> dholbach: awesome :)
[15:29] <nik90_> t1mp: fake header -> https://imgur.com/GjjQxNd
[15:29] <nik90_> t1mp: just cant get the color and icon size correct
[15:32] <zeta> hi all!!
[15:33] <zeta> can i create chat app for android?
[15:34] <zeta> with qt creator, of corse...
[15:46] <nik90_> zbenjamin: when you fix the console output logs being cut of in qtcreator when running on emulator or phone, please do give me a heads up.
[15:46] <nik90_> zbenjamin: it makes debugging on emulators pretty much impossible since it doesn't return all the errors in the code (if any)
[15:46] <zbenjamin> nik90_: next big release should be much better, but i'm blocked from releasing it atm
[15:47] <zbenjamin> nik90_: adb shell into the phone and tail the log file for your app
[15:47] <nik90_> zbenjamin: hmm yes I could do that...
[15:47]  * nik90_ tries
[15:47] <zbenjamin> nik90_: /home/phablet/.cache/upstart
[15:48] <nik90_> yup got it
[15:48] <nik90_> :)
[15:51] <davmor2> nik90_: 11 minutes for the 10 minutes alarm you are off by 1
[15:52] <nik90_> davmor2: where? :D
[15:52] <nik90_> davmor2: you mean it rings after 11 minutes instead of 10?
[15:52] <davmor2> nik90_: Yeap
[15:52] <davmor2> nik90_: no it rings for 11 minutes instead of 10
[15:52] <nik90_> davmor2: platform bug I am afraid :/ since it is indicator-datetime that rings the alarm and not clock app.
[15:53] <nik90_> davmor2: clock app only allows you to create alarms and list them. Actual ringing is done by a platform service
[15:53] <davmor2> nik90_: I'm still blaming you, it's your app that lets me set stop alarm automatically after 10 minutes :P
[15:54] <nik90_> davmor2: lol
[15:54] <davmor2> nik90_: this is the auto shut of it rang on time it just didn't stop in time
[15:54] <davmor2> shut off even
[15:55] <davmor2> nik90_: so who owns the setting for that is that in the clock app or the platform?
[15:55] <nik90_> davmor2: not sure I follow the autoshut of part
[15:56] <davmor2> nik90_: ie in clock settings change the auto shut off for alarms to 10 minutes,  Let the alarm ring until it stops,  It stops after 11 minutes not 10
[15:57] <nik90_> davmor2: that would be indicator-datetime
[15:57] <nik90_> davmor2: please ping me the bug number when you report it. I am tracking a huge list of alarm bugs in a blueprint at https://blueprints.launchpad.net/ubuntu-clock-app/+spec/alarms-rtm
[15:58] <davmor2> nik90_: will do
[16:44] <nik90_> renatu: you got a few minutes? I fixed the issue with the slide in header (by creating a fake header) at lp:~nik90/ubuntu-clock-app/fix-jarring-alarm-header
[16:45] <nik90_> renatu: however there is one last tiny issue when you drag the bottom edge all the way to the top which I am unable to fix
[16:45] <nik90_> renatu: can you help me fix it pls
[16:53] <davmor2> nik90_: https://bugs.launchpad.net/indicator-datetime/+bug/1364088
[16:57] <nik90_> davmor2: thnx
[16:58] <ahayzen> nik90_, were there really no docs for the usermetrics?
[16:58] <davmor2> nik90_: you know I'm going to keep blaming you till it's fixed though right ;)
[16:58] <nik90_> davmor2: ofc
[16:58] <nik90_> ahayzen: yup no docs
[16:59] <ahayzen> nik90_, i thought i saw something somewhere....but maybe i'm thinking ur blog post was the doc aha
[16:59] <nik90_> lol
[17:00] <ahayzen> nik90_, but as i stated probably the bigger issue is that usermetrics don't work since #200
[17:00] <nik90_> ahayzen: yup
[17:00] <ahayzen> :(
[17:00] <nik90_> ahayzen: but tbh we still don't know if 3rd party app devs can even use that api in the first place
[17:00] <nik90_> ahayzen: need to track the usermetric info dev for both these issues
[17:00] <ahayzen> nik90_, i think they can? just put the apparmor group in?
[17:01] <nik90_> ahayzen: well the decision for restricting/opening the apparmor group
[17:01] <ahayzen> popey, any progress on bug 1363314 ?
[17:01] <nik90_> ahayzen: atm yes any body can use it though it may not be intended
[17:02] <popey> sadly not ahayzen. I poked the landing team this morning but it seems everyone who can do anything on it is on vacation today (US Holiday)
[17:02] <popey> will poke again tomorrow
[17:03] <ahayzen> popey, :( my mps are stacking up! lol
[17:04] <ahayzen> nik90_, yeah i guess we need clarification
[17:08] <nik90_> ahayzen: music app is unconfined! How?
[17:09] <ahayzen> nik90_, magic :)
[17:09] <ahayzen> nik90_, and it has a lifecycle exception \o/
[17:09] <nik90_> ahayzen: not fair :P
[17:09]  * nik90_ wants one
[17:09] <ahayzen> nik90_, basically we rule the device
[17:09] <nik90_> lol
[17:14] <ahayzen> nik90_, we did get really close to being confined and having no lifecycle exception at one point...but yeah we had to revert...
[17:22] <t1mp> nik90_: font (weight) and colors are all in PageHeadStyle
[17:23] <t1mp> nik90_: PageHeadStyle that is in uitk staging has some animations already when switching Page (but the icon colors broke, so I need to fix that)
[17:24] <nik90_> t1mp: I fixed all of it. It is not indistinguishable from the real header :P
[17:24] <nik90_> t1mp: although I am now worries if the uitk staging animations might break it
[17:24] <t1mp> nik90_: -in I guess :)
[17:24] <t1mp> or -not
[17:24] <nik90_> s/worries/worried
[17:24] <nik90_> t1mp: you cannot tell the fake header from the real one..they are very similar :D
[17:25] <t1mp> nik90_: bzr branch lp:ubuntu-ui-toolkit/staging && cd staging && qmake && make && source export_modules_dir.sh && test your app :)
[17:25] <nik90_> t1mp: yup will try now
[17:25] <t1mp> ^to see if staging breaks it
[17:25] <t1mp> :)
[17:25]  * t1mp will cook a chicken now, bbl
[17:28] <ahayzen> nik90_, surely bug 1359022 should be on the blocker list?
[17:29] <nik90_> ahayzen: well as a low priority bug I suppose
[17:29] <ahayzen> nik90_, yep who do we ping to do that?
[17:29] <nik90_> ahayzen: I suppose sil2100 in ubuntu-ci-eng
[17:29] <ahayzen> nik90_, cool i'll try
[17:31] <nik90_> t1mp: it breaks the continuity :/
[17:32] <popey> pretty sure i filed a bug for that already
[17:32] <nik90_> t1mp: in the current UITK, my fake header slides in and when the page is pushed, the page header nicely appears over the top but the user won't notice anything.
[17:33] <nik90_> t1mp: but now, after my fake header is in place, when the real page header loads it blinks and then the header contents slides in from the sides
[17:39] <popey> ahayzen: to confuse things further, usermetrics are broken on mako, working on krillin
[17:39] <ahayzen> popey, wtf lol
[17:39] <popey> commented on bug
[17:39] <ahayzen> popey, thanks
[17:39] <popey> -> lasagne
[17:40] <ahayzen> nom
[18:08] <t1mp> nik90_: ohh :(
[18:08] <t1mp> nik90_: I didn't have many apps to test it with. Can you report a bug with sample code?
[18:10] <t1mp> nik90_: assign it to me
[18:14] <nik90_> t1mp: well its a corner case since it only happens with the bottom edge component
[18:14] <nik90_> t1mp: so not the sdk's fault
[18:14] <nik90_> t1mp: checkout lp:~nik90/ubuntu-clock-app/fix-jarring-alarm-header to see what I mean with & without the sdk staging
[18:17] <t1mp> nik90_: how do I run it on desktop?
[18:17] <nik90_> t1mp: trusty or utopic?
[18:17] <t1mp> ah, tim@trusty:~/dev/fix-jarring-alarm-header/app$ qmlscene -I ../backend/ ubuntu-clock-app.qml
[18:18] <t1mp> uh.. on utopic, although my hostname suggests otherwise
[18:18] <nik90_> t1mp: http://paste.ubuntu.com/8208418/
[18:18] <t1mp> nik90_: works. looks cool :)
[18:18]  * t1mp eating now. I'll try later with the uitk header animations branch.
[18:19] <nik90_> t1mp: oh .. enjoy your dinner :)
[18:41] <renatu> nik90_, hi, sorry I only saw your messages now
[18:41] <renatu> nik90_, do you still need help?
[18:46] <nik90_> renatu: yes
[18:46] <nik90_> renatu: it is all working except for that one issue
[18:47] <renatu> nik90_, can you explain the problem?
[18:47] <renatu> Do you want block the user for drag the page until the top?
[18:47] <nik90_> yes
[18:47] <nik90_> I already set the StartY property to the fake header height
[18:48] <nik90_> however it stops like 1 gu units before when dragging the bottom edge
[18:50] <renatu> nik90_, well there is a BIG WORKAROUND in the end of the file related with problems with page and headers
[18:50] <renatu> this is very trick to change
[18:50] <renatu> can cause a lot of stuff to stop to work
[18:50] <renatu> but you can play with that
[18:51] <renatu> maybe this soulve your problem
[18:51] <renatu> look for that
[18:51] <renatu>   //WORKAROUND: The SDK move the page contents down to allocate space for the header we need to avoid that during the page dragging
[18:51] <renatu>                 Binding {
[18:51] <renatu>                     target: edgeLoader.status [18:51] <renatu>                     property: "anchors.topMargin"
[18:51] <renatu>                     value:  edgeLoader.item && edgeLoader.item.flickable ? edgeLoader.item.flickable.contentY : 0
[18:51] <renatu>                     when: !page.isReady
[18:51] <renatu>                 }
[18:51] <nik90_> ok
[18:52] <renatu> and since you have already change the startY value
[18:52] <renatu> this should works fine
[18:52] <renatu>  minimumY: bottomEdge.pageStartY
[18:52] <renatu> but yeah in fact the hole pageStack stuff was not done to work this way
[18:52] <renatu> we have to do a lot of workarounds to get this working
[18:53] <renatu> and still a lot of problem is happening
[18:53] <nik90_> did you try out my branch, may be that might explain the issue better to you?
[18:53] <renatu> maybe in the future we should not handle the edge page as a "Page"
[18:53] <t1mp> nik90_: I see the problem. After opening the new page the new header animates again after it already appeared
[18:53] <nik90_> renatu: the issue i face happens before the page is pushed
[18:53] <nik90_> t1mp: yup
[18:53] <renatu> nik90_, humm we do not have control over the header
[18:54] <nik90_> renatu: I created a fake header
[18:54] <nik90_> renatu: https://code.launchpad.net/~nik90/ubuntu-clock-app/fix-jarring-alarm-header/+merge/232913
[18:54] <nik90_> renatu: fakeHeader.qml
[18:54] <nik90_> t1mp: I was able to workaround the issue by removing the contents defined in my fake header
[18:54] <nik90_> t1mp: so it shows the empty fake header slide and then once the page is loaded, your page header animates in the from the side
[18:55] <nik90_> t1mp: so I think that is acceptable for now
[18:56] <renatu> nik90_, maybe you should not use pagestack then. If you are not using the header
[18:56] <renatu> this will make your life easy
[18:56] <nik90_> t1mp: http://paste.ubuntu.com/8208750/
[18:56] <renatu> the header is the only reason to use pagestack
[18:56] <nik90_> renatu: what do you mean?
[18:56] <nik90_> If I remove pageStack how do I show the alarms page?
[18:57] <t1mp> nik90_: ok
[18:57] <renatu> you can use stackView
[18:57] <renatu> viewStack
[18:57] <renatu> http://qt-project.org/doc/qt-5/qml-qtquick-controls-stackview.html
[18:57] <nik90_> renatu: I do use the header. When the bottom edge animation is complete, the real page loader just appears over the top of the fake header. The user doesnt really notice it.
[18:57] <renatu> humm
[18:58] <renatu> ok I will take a look later
[18:58] <t1mp> renatu: the header shows the back button, and actions of the Page
[18:58] <renatu> I need to run to a meeting right now
[18:58] <t1mp> renatu: that won't work with viewStack (from QtQuick.Controls I guess?)
[18:58] <nik90_> renatu: ok, no worries
[18:58] <renatu> yeah if you are using headers you can not use the ViewStack
[18:59] <renatu> you should use the PageStack
[19:04] <nik90_> t1mp: btw was the header content animation requested by design?
[19:05] <t1mp> nik90_: yes
[19:05] <t1mp> nik90_: I implemented it a few weeks ago when I was in London with the designers
[19:05] <nik90_> ok
[19:05] <t1mp> nik90_: but it took until last week to get all the tests updated to pass with the animations
[19:06] <t1mp> nik90_: more types of animations and more control over the animations are planned, but only after a while since there are more important things to finish first
[19:06] <nik90_> t1mp: ok I think my workaround results in something better than what we have now. So I think for now I am just going to accept what I have implemented.
[19:54] <Akiva-Thinkpad> hey all
[19:56] <popey> yo
[20:30] <Akiva-Thinkpad> popey is there a global variable for the current time in the calender app?
[20:30] <Akiva-Thinkpad> I need to grab the hour to do an if statement
[20:31] <Akiva-Thinkpad> better question; is there a way in the sdk to view all the currently defined globals
[20:36] <ahayzen> Akiva-Thinkpad, if in qtcreator you can press Ctrl+Space and that usually shows you which vars are in scope
[20:37] <ahayzen> Akiva-Thinkpad, although there are issues when your a cmake project and a few random places it doesn't quite work perfectly
[20:37] <Akiva-Thinkpad> ahayzen, yah ; usually globals have some underscors in fron tof it?
[20:38] <ahayzen> Akiva-Thinkpad, depends who has been writing the app :) and which style they have used
[20:38] <Akiva-Thinkpad> hummdinger
[20:38]  * Akiva-Thinkpad starts scrolling through the list
[20:39] <ahayzen> haha
[20:39] <ahayzen> Akiva-Thinkpad, it then depends where they've been put, eg in music app we have alot of things under mainView.abc or player.abc or tabs.abc
[20:40] <ahayzen> i see calendar has tabs.currentDay
[20:40] <Akiva-Thinkpad> hmmm
[20:40] <ahayzen> Akiva-Thinkpad, but if u just want the current time can u not get that straight from Date ?
[20:40] <Akiva-Thinkpad> wwhat is the syntax for defining a global in qml?
[20:41] <Akiva-Thinkpad> okay I'll check
[20:41] <Akiva-Thinkpad> for some reason I thought they stored it in a global
[20:41] <ahayzen> there is a DateExt ?
[20:41]  * ahayzen is just scanning over the calendar code
[20:44] <Akiva-Thinkpad> Yah I just need a conditional, "if (index == Date.getHour){do magic}
[20:45] <ahayzen> \o/
[20:47] <Akiva-Thinkpad> looks like I will have to write it in dateExt...
[20:55] <Akiva-Thinkpad> hmmm. there is Date.now, but that is a raw number
[21:01] <Akiva-Thinkpad> okay
[21:01] <Akiva-Thinkpad> new Date().getHours()
[21:01] <Akiva-Thinkpad> thats how you do it. not sure if I need new
[21:10] <Akiva-Thinkpad> ahayzen, popey I notice a lot of the imports in these projects are ubuntu.components 0.1; should I report this as a bug to make sure they are current?
[21:10] <Akiva-Thinkpad> would updating the .components maybe have any speed improvements ? (I am not sure how the library devs are making tweaks like this)
[21:11] <ahayzen> Akiva-Thinkpad, probably...i just bumped music-app to be all 1.1 but it depends if the app really needs the later stuff as well
[21:11] <Akiva-Thinkpad> ahayzen, it would take longer to import I gather.
[21:11] <ahayzen> Akiva-Thinkpad, i'm not sure if there is any requirement to move onto later versions, eg the old being removed?
[21:12] <Akiva-Thinkpad> ahayzen, is there a library freeze on it at the moment?
[21:12] <Akiva-Thinkpad> or are they working on new versions
[21:12] <ahayzen> Akiva-Thinkpad, idk probably best to ask one of the SDK guys
[21:16] <Akiva-Thinkpad> sure
[21:19] <Akiva-Thinkpad> http://askubuntu.com/questions/518912/should-we-be-upgrading-away-from-ubuntu-components-0-1
[21:19] <Akiva-Thinkpad> Guess its time to play the waiting game
[21:20] <Akiva-Thinkpad> :)
[21:23] <ahayzen> Akiva-Thinkpad, hehe :) and now we wait...
[21:37] <Akiva-Thinkpad> brb
[23:45] <nik90_> Akiva-Thinkpad: the SDK API has been frozen for RTM. So what we have for 1.1 is final
[23:45] <Akiva-Thinkpad> nik90_, oh great
[23:45] <nik90_> Akiva-Thinkpad: It is supposed to maintain backwards compatibility with 0.1.
[23:46] <Akiva-Thinkpad> nik90_, any performance tweaks?
[23:46] <nik90_> Akiva-Thinkpad: If it is a core app, it is highly recommended to upgrade to 1.1 since core apps are supposed to be pioneers of using the latest SDK.
[23:46] <Akiva-Thinkpad> okay
[23:46] <nik90_> Akiva-Thinkpad: I believe there were performance tweaks to ubuntu shape.
[23:46] <nik90_> Akiva-Thinkpad: not sure if that benefited 0.1 as well
[23:46] <Akiva-Thinkpad> nik90_, if you want to answer the question then, i'll accept it as the answer
[23:47] <nik90_> Akiva-Thinkpad: sure, give me a min
[23:54] <Akiva-Thinkpad> Ubuntu.Components.Popups" version 1.1 not installed
[23:54] <Akiva-Thinkpad> nik90_,
[23:55] <Akiva-Thinkpad> for those; what do we do?
[23:55] <nik90_> Akiva-Thinkpad: for those import 1.0
[23:55] <nik90_> Akiva-Thinkpad: same applies for ListItems as well
[23:57] <Akiva-Thinkpad> cool


[01:06] <micahg> chrisccoulson: I think we need --disable-elf-hack still armel and powerpc failed
[01:07] <chrisccoulson> micahg - maybe not, i spoke to glandium about that earlier
[01:07] <micahg> chrisccoulson: ok
[01:08] <chrisccoulson> i'll probably do that tonight, but i guess it will get fixed quite quickly
[01:08] <micahg> chrisccoulson: I'm still trying to get my VMs set up :)
[01:08] <chrisccoulson> heh :)
[09:20] <fta2> dpm, hi, seems the strings are back: http://people.ubuntu.com/~fta/chromium/translations/trunk/converter-output.html (in blue)
[09:21] <dpm> fta, \o/
[09:25] <fta2> dpm, i hope they are the right ones. someone should check (i unfortunately can't)
[10:15] <dpm> fta2, I think the best thing to do would be to send an e-mail to the launchpad-translators list, to simply tell translators to double-check them
[10:16] <dpm> hi chrisccoulson, is the panorama thing gone from firefox? I can't see the little icon anymore next to the tabs
[11:30] <chrisccoulson> dpm - oh, i only just noticed the icon isn't there too
[11:31] <chrisccoulson> panorama is still there though
[11:31] <dpm> chrisccoulson, not that it bothers me much tough, but the one time I wanted to use it, it suddenly wasn't there :)
[12:04] <dpm> chrisccoulson, could you configure https://launchpad.net/po2xpi for bugs? I'd like to open a bug for the problems we're currently having for the Lucid language packs, and I can't, since it's not configured
[12:04] <dpm> (sorry if you got an additional ping. I just got disconnected and I want to make sure you got it)
[12:16] <chrisccoulson> dpm - ok, that's done
[12:17] <dpm> brilliant, thanks chrisccoulson
[12:22] <chrisccoulson> dpm - https://bugzilla.mozilla.org/show_bug.cgi?id=626500
[12:22] <ubot2> Mozilla bug 626500 in Toolbars "Don't put the Panorama button on the tab bar by default" [Normal,Resolved: fixed]
[12:23] <chrisccoulson> and also https://bugzilla.mozilla.org/show_bug.cgi?id=626791
[12:23] <ubot2> Mozilla bug 626791 in Toolbars "Add the Panorama button to the toolbar automatically after the user has entered Panorama for the first time" [Normal,Assigned]
[12:24] <dpm> chrisccoulson, aaahh that was it then, thanks :)
[15:35] <jeward> Anyone know how to set what the first hour displayed is in Mozilla Sunbird?
[18:45] <micahg> jdstrand: apparently both my machines don't support the VT-x extension, so I'll have to wait for my new machine to use kvm, in the mean time, I'll get some Virtualbox VMs set up
[18:46] <jeward> Anyone know how to set what the first hour displayed is in Mozilla Sunbird?
[19:00] <chrisccoulson> micahg - virtualbox is broken in natty ;)
[19:00] <chrisccoulson> (or, at least it was when i last tried)
[19:01] <micahg> chrisccoulson: not on natty yet ;) still using Maverick
[19:02] <chrisccoulson> heh ;)
[19:02] <chrisccoulson> maverick is oooooolllllllllllddddddd
[19:02] <chrisccoulson> that was sooooooooo last year
[19:02] <micahg> chrisccoulson: I might try to set up the 32 bit VMs on the desktop I have set up here, but it only has 1GB RAM
[19:07]  * micahg wonders what's better P3 1Ghz 2GB RAM vs P4 2Ghz 1GB RAM
[19:28] <micahg> chrisccoulson: I've got a crazy suggestion for you, what about Firefox building mozjs?
[19:28] <chrisccoulson> micahg - it can't ;)
[19:29] <micahg> oh well
[19:29] <chrisccoulson> micahg - libmozjs is statically linked in to libxul now
[19:29] <chrisccoulson> we only get libmozjs in xulrunner because we explicitly build with --enable-shared-js
[19:29] <chrisccoulson> we don't want to do that in firefox ;)
[19:32] <micahg> indeed
[19:45] <jdstrand> micahg: no worries. virtualbox is more than able to do what you need :)
[19:46] <jdstrand> micahg: 1G with virtualization is a bit tight, but should be doable. later versions of ubuntu you'll likely want 384M in the guest so it isn't horrible (karmic+ iirc)
[19:47] <micahg> jdstrand: I'm assuming I'm better off with the faster processor and dealing with the lower memory?
[19:52] <jdstrand> micahg: tbh, I'd prefer more memory, but I haven't benchmarked it
[19:53] <micahg> jdstrand: really? I guess I can swap the drives out of the systems, is the assumption that the GUI should perform the tests just as well on teh slower machine?
[19:55] <jdstrand> I would think so
[21:11] <chrisccoulson> right, the nightlies should work again now
[21:46] <fta> jdstrand, any idea why the build died?
[21:47] <fta> i'm not getting any email regarding those builds, weird
[21:49] <jdstrand> fta: yes. it has to do with armel and how build-master works
[21:49] <fta> ?
[21:49] <jdstrand> fta: it isn't a ftbfs, it is the thing that sees if a build stalled/died isn't smart enough
[21:49] <fta> doh, i guess it's always at link time then
[21:50] <jdstrand> fta: in essence, the build-master tries to 'ping' the builder using some pythong twisted method, then if it doesn't hear back in time, it stops the build and starts another
[21:50] <jdstrand> I went ahead and pushed maverick
[21:51] <fta> jdstrand, how come it works sometimes then? it's always very slow to link, and even slower on armel, it should always die
[21:53] <jdstrand> no idea
[21:54] <jdstrand> I'm just passing along what I was told
[21:54] <jdstrand> it seems more ram would help. I think they are looking at that. they are also trying to figure out how to fix build-master
[21:54] <jdstrand> it happens on more than just chromium
[21:57] <BUGabundo> anyone think they can help me? https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/716136
[21:57] <ubot2> Launchpad bug 716136 in notify-osd "getting old ballons for notifications" [Undecided,New]
[23:09] <jcastro> fta: ping
[23:13] <fta> BUGabundo, i see the same at work, with xchat and evo (x64). but not at home (32bit)
[23:13] <fta> jcastro, pong
[23:14] <jcastro> http://castrojo.tumblr.com/post/3202209062/progress-meters-quicklists-and-number-count-for-the
[23:14] <BUGabundo> fta: seb128 fixed it to me
[23:14] <jcastro> you think upstream chromium might be interested in that?
[23:24] <chrisccoulson> m_conley_away, ^^
[23:24] <chrisccoulson> you might be interested in that too ;)
[23:30] <fta> reading..
[23:30] <fta> BUGabundo, how?
[23:32] <BUGabundo> fta: purge notification-daemon and then stop it or restart session
[23:32] <BUGabundo> if you are like me, you are using Classic desktop
[23:32] <BUGabundo> $ export  | grep GDMSESSION
[23:34] <fta> chrisccoulson, fyi, my problem with lp's translations: http://ftagada.wordpress.com/2011/02/10/chromium-translations-explained-part-2b/
[23:37] <fta> jcastro, most probably, i can spread it if you want, but i also accept dist patches ;)
[23:37] <fta> jcastro, i hope it won't break the classic desktop users
[23:37] <jcastro> nope, it's purely additive
[23:37] <fta> BUGabundo, ok, thanks, i'll try that tomorrow
[23:37] <jcastro> fta: I think just spreading for now will do the trick
[23:38] <jcastro> fta: he mentioned something specifically for making it easier for browser users
[23:38] <jcastro> fta: or we can just make chrisccoulson do it ... *grin*
[23:38] <chrisccoulson> fta - thanks for the link
[23:39] <chrisccoulson> jcastro, are you assigning work to me? ;)
[23:52] <fta> jcastro, well, it seems the macos build already have that, and much more
[23:52] <fta> buildS
[23:53] <jcastro> fta: ah ok, handy. What would I search for if I wanted to find a screenshot?
[23:53] <jcastro> what do they call that on osx?
[23:55] <fta> jcastro, i don't know. i read "the equiv osx api lets you put arbitrary graphics in the icon" "on os x we actually show download progress in the icon"
[23:55] <jcastro> k