 No problem. How are you?
[08:22] <seb128> I'm good, I went to bed early yesterday, was good to have a longer night :)
[08:23] <seb128> duflu, I'm going to try to build a list of bugs that would be nice to fix tor the LTS, like papercut/polish kind of things, if you have some of those on your list or cross some when trying feel free to tag them/note them down and send them in my direction
[08:24] <seb128> then I'm going to try to argue at the product sprint that we need part of the cycle allocated to work on those
[08:28] <duflu> seb128, use rls-ff-incoming or something else?
[08:28] <seb128> something else, incoming are team reviewed in the perspective of being release blockers and then tracked
[08:29] <seb128> those would rather be a wishlist/papercut project
[08:29] <seb128> like things that would make a difference in polish level for the LTS but are not release critical
[08:29] <duflu> How about "bugs I can find in the first 5 seconds after logging in"
[08:30] <seb128> those are probably good candidate for polish fixing :)
[08:30] <duflu> seb128, I will use a tag of your choosing
[08:30] <seb128> duflu, desktop-lts-wishlist ?
[08:30] <duflu> Sure, whatever it is it only needs to be unique
[08:30] <seb128> k, let's use that then
[08:30] <seb128> thx :)
[08:32] <duflu> seb128, just remembered I had used 'visual-quality' for that for a few years. Already a long list
[08:33] <seb128> k, I will review that list as well
[08:33] <seb128> don't bother re-tagging those
[08:34] <seb128> wooot, that's quite a list indeed
[08:34] <duflu> Lots of Unity stuff in there so mostly ignorable
[08:36] <seb128> I will review it and tag some with the new tag
[08:38] <seb128> jamesh, tkamppeter, (Cc Laney FYI), rls bugs on discourse update reminder
[08:38] <seb128> jamesh, weekly summary also :)
[08:38] <jamesh> will do.
[08:39] <seb128> thx
[08:42] <duflu> seb128, https://bugs.launchpad.net/ubuntu/+bugs?field.tag=desktop-lts-wishlist
[08:42] <seb128> duflu, that looks like a nice list, thanks!
[09:00] <ricotz> godd morning desktopers!
[09:00] <oSoMoN> good morning ricotz
[09:01] <Laney> hi
[09:01] <ricotz> oSoMoN, hey, looks like one the few cycles where firefox doesn't require a unity patch update
[09:01] <ricotz> Laney, hey
[09:02] <ricotz> seb128, hi, is there further action required on https://bugs.launchpad.net/ubuntu/+source/vala/+bug/1803136 ?
[09:02] <ricotz> like reassigning to release-team?
[09:03] <ricotz> I am hoping the package won't be stuck in the queue for weeks
[09:07] <seb128> hey ricotz Laney, how are you?
[09:07] <seb128> ricotz, try pinging the SRU reviewer of the day? (shifts are listed on the wikipage)
[09:07] <seb128> lut oSoMoN, en forme ?
[09:11] <oSoMoN> hey Laney
[09:11] <oSoMoN> salut seb128, la forme, et toi?
[09:11] <oSoMoN> ricotz, that's very good news, more time for me to focus on backporting thunderbird 68 to stable releases :)
[09:12] <seb128> oSoMoN, ca va bien !
[09:12] <ricotz> seb128, thanks!
[09:13] <Wimpress> Morning desktoppers
[09:15] <seb128> hey Wimpress, how is u.k today?
[09:15] <Wimpress> Well, best described as grey. And cold.
[09:15] <Wimpress> How about you?
[09:17] <seb128> nice and sunny
[09:18] <oSoMoN> good morning Wimpress
[09:19] <didrocks> RAOF: hey, also if you have a minute to look at zsys on eoan (the fix is in -proposed in focal). Currently installing it will prevent you to log in on next reboot, so quite a high one :)
[09:19] <Laney> hi ricotz seb128 oSoMoN Wimpress
[09:19] <Laney> sunny and nice here
[09:20] <didrocks> hey Laney, Wimpress
[09:23] <Laney> \o didrocks o/
[09:25] <duflu> Morning ricotz, Wimpress and Laney
[09:25] <Laney> ahoy duflu!
[09:34] <clobrano> good morning all 0/
[09:35] <seb128> hey clobrano, how are you?
[09:35] <clobrano> hey seb128, I'm good thanks
[09:35] <seb128> clobrano, sorry I didn't really have time to investigate that deb upgrade issue
[09:35] <seb128> did you figure it out?
[09:35] <didrocks> hey clobrano
[09:36] <clobrano> hey didrocks :)
[09:36] <clobrano> seb128, kind of, but I was reviewing deb packages to test it locally
[09:37] <clobrano> basically, the PR to allow User Themes switch install gnome-shell in a yaru-gtk created folder
[09:38] <clobrano> I think I need to either change something in debian/gnome-shell.install or revert the change, installing gnome-shell again in /usr/share/gnome-shell and symlink it to /usr/share/themes
[09:44] <seb128> what's the issue? the file seemed to be on disk no?
[09:52] <seb128> or is update-alternative not liking the destination to be a symlink?
[09:52] <seb128> Laney, do you know if https://github.com/ubuntu/yaru/blob/master/debian/yaru-theme-gnome-shell.postinst#L7 would have an issue with the file being a symlink?
[09:52] <seb128> Laney, context is https://github.com/ubuntu/yaru/blob/master/debian/yaru-theme-gnome-shell.postinst#L7
[09:53] <seb128> update-alternatives: error: alternative path /usr/share/gnome-shell/theme/Yaru/gnome-shell.css doesn't exist
[09:53] <seb128> but the target should be there (it's provided by -gtk which is installed first)
[09:53] <seb128> didrocks, ^
[09:54] <Laney> don't think so
[09:54] <marcustomlinson> morning desktoppers
[09:54] <Laney> how do you reproduce this issue?
[09:55] <Laney> hey marcustomlinson
[09:55] <didrocks> I doubt update-alternatives have any issues with the file type as well
[09:55] <didrocks> hey marcustomlinson
[10:04] <duflu> Hi marcustomlinson
[10:33] <Laney> TFW you can't understand your own code
[10:33] <Laney> who wrote this and what was I thinking?
[12:26] <seb128> question of the day...when is the meeting? still in 2 hours from now? or is DST going to confuse again? ;-)
[12:27] <Laney> calendar says 2 hours
[12:27] <Laney> trust the calendar
[12:29] <Laney> although this one http://ubuntu-news.org/calendars/fridge says 18:30 WTF
[12:30] <seb128> :/
[12:30] <seb128> kenvandine and other USers, if it's in 2 hours it probably means shifted by one hour for you guys this week since you didn't have DST yet
[12:36] <kenvandine> It does say in 2 hours
[12:36] <Laney> seb128: dunno if you missed the message but how do you reproduce that yaru problem?
[12:37] <seb128> kenvandine, that's one hour off compared to your normal local time then right? anyway, as long as you are aware it's all good :)
[12:38] <seb128> Laney, I didn't try to reproduce yet, I just have the urls I shared earlier. but I think it's using this ppa https://launchpad.net/~communitheme/+archive/ubuntu/ppa and upgrading
[12:38] <seb128> Laney, let me try in a bionic chroot see if I hit the issue
[12:39] <Laney> ok cheers
[12:47] <diddledan> Morning, oSoMoN 😊 auto defeat ftw!
[12:48] <oSoMoN> :)
[12:52] <seb128> Laney, clobrano, I can't trigger the bug with dpkg, but I don't have the previous ppa version to try the update scenario
[12:52] <seb128> clobrano, Laney, in any case the -theme-gnome-shell should depends on -gtk if it symlinks to content from there
[12:53] <clobrano> seb128, sorry I missed the replies, reading now
[12:53] <seb128> that should also hep ensuring the content of -gtk is unpacked first
[12:53] <seb128> (or is Pre-Depends needed for that?)
[12:53] <Laney> nah, postinst -> depends
[12:55] <clobrano> seb128, as far as I understood, https://github.com/ubuntu/yaru/blob/master/debian/yaru-theme-gnome-shell.postinst#L7 triggers the error message, but I think the problem is before
[12:56] <seb128> clobrano, how before?
[12:56] <clobrano> meson build script installs gnome-shel under `/usr/share/themes/Yaru/gnome-shell`, but the folder `/usr/share/themes/Yaru` is created by yaru-gtk
[12:57] <clobrano> so if ones install gnome-shell first, or it only wants to install gnome-shell, that folder does not exists
[12:58] <seb128> right, which is why I said you need a Depends added to -theme-gnome-shell
[12:58] <clobrano> and if `/usr/share/themes/Yaru/gnome-shell` does not exist, nor its symlink under `/usr/share/gnome-shell` does
[12:58] <clobrano> right, but this means one cannot install Yaru gnome-shell without the gtk part, is that a problem?
[12:59] <seb128> well, they can't anyway
[12:59] <clobrano> why?
[12:59] <seb128> since you installed the actual shell css in a directory shipped by -gtk
[12:59] <seb128> and make the gnome-shell binary only ship a symlink
[13:00] <seb128> if you remove gtk then your shell css is a broken symlink no?
[13:00] <clobrano> oh yes, sure. That's why the other solution. Install gnome-shell under `/usr/share/gnome-shell` as we did before, and symlink into the gtk path
[13:01] <seb128> I don't understand enough of how the theme work / what you are doing to comment on that
[13:01] <clobrano> but that wouldn't work either... since at that point the would be the gtk folder that doesn't exist :(
[13:01] <seb128> e.g why do you have that new approach/need to symlink in between directories?
[13:02] <didrocks> I really don't think it's sane to ship the g-s css in the gtk directory
[13:02] <clobrano> that was to support User Themes gnome-shell extension
[13:02] <clobrano> didrocks, I see
[13:02] <seb128> right, which is where it's getting over my theme knowledge
[13:03] <seb128> like I don't know why technically that's the solution to that problem or if that's the right way to do it
[13:03] <clobrano> I read some people complaining that `/usr/share/gnome-shell` path is not the place, but I don't really know why
[13:04] <didrocks> it's clearly the place, you have /usr/share/gnome-shell/theme created upstream in the past
[13:04] <didrocks> it will fetch them there first
[13:04] <didrocks> and for themes, then, extensions needs to have a <theme>.css or something like that
[13:04] <didrocks> in the extension path
[13:04] <didrocks> (which is the weird part, but meh)
[13:05] <didrocks> actually, for the extension, it's the mode name
[13:05] <seb128> marcustomlinson, did you get any success with the libreoffice/focal autopkgtest issue? unsure how you ranked it on your priority list, it's blocking a stack of desktop components in focal-proposed atm, so would be nice to have it looked at in medium-to-high priority if possible
[13:05] <seb128> (unsure if the context was clear from my ping yesterday)
[13:05] <didrocks> hence the empty file we ship, like<EMAIL_ADDRESS>to allow the theme to override it
[13:06] <clobrano> didrocks, what about shipping more than one default? Like the light and the dark variant? Both shall be installed in `/usr/share/gnome-shell`
[13:06] <clobrano> ?
[13:07] <didrocks> yeah, under /usr/share/gnome-shell/theme
[13:07] <didrocks> then, for switching them, this needs the extension though
[13:07] <marcustomlinson> seb128: will be fixed this week when I upload the new version, tomorrow or Thursday
[13:07] <seb128> marcustomlinson, excellent, thx
[13:08] <clobrano> didrocks, I see. I didn't try that first, because according to https://github.com/ubuntu/yaru/issues/1483 it seemed that, using /usr/share/gnome-shell, changing session one cannot use Yaru anymore
[13:09] <clobrano> but it would be a lot easier to install both themes under /usr/share/gnome-shell/ and not using any symlink
[13:10] <didrocks> just seeing the start of the discussion, I doubt the reporter has a deep understanding that there are 2 themes completely separated (gtk and shell)
[13:11] <clobrano> installing from source, it actually works with this configuration
[13:11] <clobrano> but it creates some issue with the debs
[13:11] <didrocks> yeah, I doubt though that once the assets (like imgs) are different, this will work with the alternative
[13:12] <didrocks> as you need an alternative on the directory symlink directly
[13:15] <clobrano> okay, I'll try with the old installation directory
[13:25] <clobrano> didrocks, an unrelated question, we still need the gtk-3.0 and gtk-3.20 folders?
[13:26] <didrocks> clobrano: that's more a question for seb128/Laney, I don't think we have apps built with pre-gtk3.20, but better to check with them
[13:26] <Laney> that's xenial basically
[13:26] <Laney> so if you have to work with xenial's gtk
[13:27] <Laney> (or older)
[13:27] <didrocks> so as we don't support it, I would say fine for cleaning it up
[13:27] <clobrano> Laney, but isn't yaru supported on >bionic?
[13:27] <didrocks> (we started pre-bionic, remember? ;))
[13:28] <clobrano> okay, I can use 3.0 only then, right?
[13:28] <didrocks> but the release is EOL for quite a long time :)
[13:28] <Laney> I dunno, any snap reasons?
[13:28] <clobrano> didrocks, yes sure, I was saying right now we support from bionic
[13:29] <didrocks> yeah, snaps, good point. It will be interesting to know if any are using an older gtk version
[13:29] <didrocks> (as we build the theme snap from the same source)
[13:29] <seb128> didn't jamesh spent weeks working on making the theme work on xenial's gtk for snap reasons?
[13:29] <seb128> kenvandine, ^
[13:29] <Laney> that'd be what a 3.0 is good for
[13:30] <kenvandine> seb128: yes
[13:30] <kenvandine> seb128: is there an issue?
[13:31] <Laney> just answering a question from Carlo
[13:31] <seb128> kenvandine, if I understood the discussion correctly, I think clobrano was wondering if they could drop the 3.20 folder/support now
[13:32] <kenvandine> yes, we need that for snaps on xenial
[13:32] <clobrano> seb128, exactly. This comes from a complain on yaru flatpak version and I just wanted to have a valid reply for keep/remove the folder
[13:32] <clobrano> kenvandine, perfect
[13:33] <seb128> kenvandine, but xenial users are on unity with ambiance so why do they need yaru?
[13:33] <Laney> current users running a snap with xenial's gtk in it
[13:33] <seb128> oh, that was it of course
[13:33] <seb128> thx Laney :)
[13:34] <kenvandine> yup
[13:34] <Laney> np
[13:34] <Laney> lunch, laterz
[13:34] <seb128> enjoy!
[13:34] <hellsworth> isn't it meeting time?
[13:34] <seb128> DST kicked in, it's in one hour
[13:34] <clobrano> alright, thanks all :)
[13:34] <seb128> well it did for UK/Europe
[13:34] <seb128> not US yet
[13:34] <seb128> always a fun time for calendars/meetings
[13:34] <hellsworth> oh that's right. stupid daylight savings :)
[13:35] <hellsworth> ok well good morning folks
[13:36] <didrocks> good morning hellsworth
[13:36] <didrocks> the calendar should be up to date though for meeting time, doesn't it translate it correctly?
[13:37] <hellsworth> yes it did but i didnt' look at the calendar
[13:37] <hellsworth> i was going off memory
[13:37] <didrocks> :)
[13:38] <hellsworth> that'll teach me :)
[13:41] <seb128> kenvandine, you should have a clicky url for the snapcraft PRs you are mentioning, I'm curious :)
[13:41] <seb128> kenvandine, also do you need help with the segfault issue?
[13:42] <seb128> jamesh, weekly summary post?
[13:42] <kenvandine> seb128: oh, i'll add them :)
[13:42] <jamesh> seb128: just finishing it up.  Thanks for the reminder
[13:42] <kenvandine> seb128: maybe, marcustomlinson ^^ want to get some help from seb128?
[13:42] <seb128> jamesh, thx, sorry for being naggy :)
[13:43] <kenvandine> jamesh: make sure you include any release bugs :)
[13:49] <marcustomlinson> seb128: let me at it for another day then I'll ping you if I'm jammed, thanks for offering
[13:49] <kenvandine> seb128: link added to the status report
[13:49] <seb128> marcustomlinson, np
[13:49] <seb128> kenvandine, thx
[13:49] <kenvandine> seb128: the snapcraft PR includes a link to a PR against gtk-common-themes
[13:50] <kenvandine> I think both look good, but wanted jamesh to look at them
[13:51] <seb128> right, nice numbers in the description, I like it :-)
[14:31] <seb128> Wimpress, team meeting?
[14:32] <seb128> k, I'm going to assume you don't have it yet in your calendar or got delayed and start it
[14:32] <seb128> #startmeeting Desktop Team Weekly Meeting - 2019-10-29
[14:32] <meetingology> Meeting started Tue Oct 29 14:32:51 2019 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:32] <meetingology> Available commands: action commands idea info link nick
[14:33] <seb128> Roll call:  didrocks, duflu (out), hellsworth, jamesh (out), jibel, kenvandine, laney, marcustomlinson, oSoMoN, seb128 , tkamppeter, trevinho, robert_ancell (out)
[14:33] <oSoMoN> o/
[14:33] <hellsworth> 0/
[14:33] <marcustomlinson> \o
[14:33] <Trevinho> o/
[14:33] <kenvandine> seb128: I just invited Wimpress on the calendar event :)
[14:33] <seb128> kenvandine, that might be useful :)
[14:34] <seb128> k, half the team at least seems around let's get started
[14:34] <seb128> #topic rls-bb-bugs
[14:34] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[14:34] <seb128> no desktop one
[14:34] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[14:35] <seb128> that looks in shape, unassigned ones are fix commited
[14:35] <seb128> #topic rls-dd-bugs
[14:35] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
[14:35] <seb128> no desktop one
[14:35] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-tracking-bug-tasks.html
[14:35] <seb128> no unassigned ones
[14:35] <seb128> #topic rls-ee-bugs
[14:36] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
[14:36] <seb128> still no desktop
[14:36] <seb128> bug #1848969 is border desktop but community side now so I don't think we need to handle it here
[14:37] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html
[14:37] <seb128> bug #1845801
[14:37] <seb128> Laney commented on it that he couldn't reproduce
[14:37] <Laney> it's assigned
[14:38] <Laney> just not all of the tasks
[14:38] <seb128> do you know if Alberto noticed it was?
[14:38] <Laney> yes, as we talked on irc before
[14:38] <seb128> tseliot, ^ please confirm you saw the emails and just didn't /dev/null filter those :)
[14:38] <seb128> k
[14:38] <seb128> so I'm assigning to the other lines
[14:39] <Laney> I wouldn't usually just assign a bug to someone and expect them to notice that
[14:39] <seb128> ack
[14:39] <didrocks> as long as we don't know which component is impacted…
[14:39] <didrocks> Laney: you can with me, filter power ;)
[14:39] <seb128> bug #1847551
[14:39] <seb128> Trevinho, that's part of your pending SRU right?
[14:39] <Laney> yes
[14:39] <Laney> assign it
[14:40] <seb128> k
[14:40] <Trevinho> seb128: yes
[14:40] <Trevinho> already in queue
[14:40] <seb128> bug #1850052
[14:40] <didrocks> waiting in unapproved
[14:40] <seb128> didrocks, assigning that one to you
[14:41] <didrocks> doing, even if "fixed" and waiting from the SRU team to act on it (+ Laney to unblock focal, pretty please ;))
[14:41] <Laney> one thing at a time
[14:41] <seb128> I assigned the rygel one to me
[14:41] <seb128> and that's it
[14:42] <seb128> #topic rls-ff-bugs
[14:42] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[14:42] <seb128> bug #1848766
[14:43] <seb128> it's assigned to xubuntu, the other lines seem buggy
[14:43] <seb128> but I've https://code.launchpad.net/~jbicha/libappindicator/drop-python-appindicator/+merge/335606 on my review queue which is related from our side of things
[14:43] <seb128> bug #1849773
[14:44] <seb128> it's an evince segfault on text selection on some specific documents
[14:44] <seb128> jibel could find only one private document example
[14:44] <jibel> it seems related to the font used in the doc
[14:44] <seb128> I think it's too specific to qualify as a rls bug, we should probably fix it but as normal business
[14:44] <jibel> +1
[14:44] <seb128> jibel, if you can add the font info to the bug that might be useful
[14:44] <tseliot> seb128, I got the bug mail, I remember Laney telling me about it too. I remember systemd complaining about things in the log. I haven't really got time to look into it. I am not sure if NVIDIA is the cause of the problem yet (it could just trigger it)
[14:45] <seb128> tseliot, k, thx
[14:45] <Wimpress> o/
[14:45] <seb128> unless someone objects I will notfixing the evince one
[14:45] <kenvandine> hey Wimpress!
[14:45] <Laney> can we also notfix the indicator-datetime thing pls
[14:45] <Laney> or else we will keep coming back to it
[14:46] <seb128> hey Wimpress
[14:46] <seb128> Laney, good point, done
[14:47] <seb128> bug #1848217
[14:47] <seb128> that's fix commited, probably not rls material though
[14:47] <Laney> seems handled so I don't think it particularly matters either way
[14:47] <seb128> ah, it's in the installer context
[14:48] <seb128> so yeah, tag is fine, it's fix commited
[14:48] <seb128> right
[14:48] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-tracking-bug-tasks.html
[14:48] <seb128> desktop clean
[14:48] <seb128> #topic update_excuses_by_team.html#desktop-packages
[14:49] <seb128> Laney, yours
[14:49] <seb128> (in the measure we are ready to look at it/should maybe wait for the initial sync churn to settle down)
[14:49] <Laney> forget it
[14:49] <Laney> it's ruined for this week at least
[14:49] <seb128> just libreoffice is obvious but marcus is on it
[14:49] <Laney> apart from some things like libreoffice which are known separately
[14:50] <seb128> thx Laney :)
[14:50] <seb128> #topic AOB
[14:50] <seb128> any other topic?
[14:51] <seb128> seems not, it's a wrap then
[14:51] <seb128> thanks team!
[14:51] <seb128> #endmeeting
[14:51] <meetingology> Meeting ended Tue Oct 29 14:51:55 2019 UTC.
[14:51] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-10-29-14.32.moin.txt
[14:52] <kenvandine> thanks!
[14:52] <marcustomlinson> thanks
[14:52] <Trevinho> ta
[14:52] <Wimpress> seb128 kenvandine Thanks for running things. I'll be here on time next week now I have the calendar entry :-)
[14:52] <didrocks> thx!
[14:53] <seb128> Wimpress, no worry :)
[14:54] <kenvandine> Wimpress: let's hope that's the only think willcooke neglected to hand off :)
[15:17] <clobrano> didrocks, sorry to bother again :), but looking at user themes code, it seems to look for gnome-shell css installed under `/usr/share/themes/<theme>/gnome-shell` folder https://gitlab.gnome.org/GNOME/gnome-shell-extensions/blob/master/extensions/user-theme/extension.js#L42
[15:19] <didrocks> clobrano: interesting, this has changed as it as looking at the other places before
[15:19] <didrocks> I based the location on where the mode/theme for G-S was looking before we moving to an internal css in the compiled gressources
[15:19] <clobrano> didrocks, uhm let me check git history then
[15:19] <didrocks> so yeah, sounds like then moving the whole theme will be necessary. It means updating the Shell css
[15:20] <didrocks> clobrano: well, if upstream thinks now we should put them there, no need to dig more
[15:22] <clobrano> didrocks, yeah I guess
[15:22] <didrocks> clobrano: upstream disagrees with itself though: https://gitlab.gnome.org/GNOME/gnome-shell/blob/master/js/ui/main.js#L298
[15:22] <clobrano> so both gtk and gnome-shell goes into the same dir
[15:23] <didrocks> look here, in G-S, they are looking at the place we are using
[15:23] <didrocks> so I guess it's something for you to discuss with Trevinho, but the extension made by usptream and the G-S code should align at least
[15:24] <clobrano> eh, a bit messy indeed
[15:26] <didrocks> not that crazy… I was sure when I did the extension mode 2.5 years ago I didn't invent it from nothing ;)
[15:27] <clobrano> I'm sure you didn't :D
[15:27] <Trevinho> clobrano: probably upstream wants to keep both, like if the shell theme is the same of gtk then it goes with it otherwise it can use a local time
[15:27] <Trevinho> question of prioritizing one or the other
[15:27] <Trevinho> clobrano: I'd suggest you to ask in #gnome-shell to fmueller when he's around
[15:28] <Trevinho> or open an issue so we can discuss there the proper strategy
[15:32] <clobrano> Trevinho, yes, this could make sense
[16:07] <clobrano> Trevinho, didrocks, reply from #gnome-shell was that `/usr/share/gnome-shell/theme` is for session default and the other for 3rd party theme. Reconsidering the problem, we have Yaru(light) as default and Yaru-dark as selectable, so I can simply install the first under gnome-shell and the latter under themes
[16:07] <clobrano> as I was actually doing at the beginning
[16:08] <clobrano> to have yaru light available under gnome-session, the only option is the symlink
[16:23] <didrocks> yeah, it sounds weird to me, but ack
[16:39] <didrocks> Laney: I think you typoed the hint on https://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/4024: ss390x
[16:39] <Laney> k
[16:40] <Laney> merge proposals are accepted for reference for the future ;-)
[16:40] <didrocks> thx ;)
[17:30] <kenvandine> hellsworth: marcustomlinson found the crasher.  It's cairo 1.17.  Try downgrading it to 1.16
[17:33] <hellsworth> hmmmm
[17:34] <hellsworth> then it must be different from the librsvg issue of updating the build snap to librsvg-2.46
[17:35] <hellsworth> while the librsvg commit does change cairo versions, it updates librsvg to require 1.16.0 instead of cairo 1.15.12
[17:37] <hellsworth> still.. i'm build ing gnome-3-34-1804-sdk with cairo branch 1.16, rebuilt the platform snap, and rebuilt evince to test
[17:42] <kenvandine> hellsworth: i cherry-picked the fix into gnome-3-34-1804-sdk and pushed it to get a build in LP
[17:42] <hellsworth> oh nice!
[17:43] <hellsworth> can you launch a build? looks like the last lp build of the build snap was a week ago
[17:48] <kenvandine> waiting for the git mirror to sync
[18:04] <hellsworth> is there a way to tell the platform snap to use the gnome-3-34-1804-sdk that is installed locally rather than pulling from the snapstore?
[18:06] <marcustomlinson> hellsworth: doubtful, you could ask on #snapcraft
[18:08] <hellsworth> ah yes good idea
[18:13] <marcustomlinson> hellsworth: it's not that much work to just snapcraft push your local snap to edge
[18:13] <marcustomlinson> but I guess you're using edge at the moment as your release I guess
[18:13] <hellsworth> oh right i can do that from my lp build, i think
[18:13] <marcustomlinson> lots of guessing going on :P
[18:14] <marcustomlinson> hellsworth: doesn't your LP build push to edge already?
[18:15] <marcustomlinson> oh you mean you just need to trigger one
[18:15] <marcustomlinson> yeah that was why I suggested you have a personal one, for times like this where you want to bypass all the import waiting
[18:15] <hellsworth> i tend to just build locally because lp is confusing
[18:15] <hellsworth> yes you're right
[18:15] <hellsworth> and i think i have one
[18:15] <hellsworth> need to find it
[18:16] <marcustomlinson> that's fine, you can do: "snapcraft push <path to local snap>.snap --release edge"
[18:17] <marcustomlinson> hellsworth: ^
[18:17] <hellsworth> wat! i didn't know that
[18:17] <marcustomlinson> :)
[18:18] <hellsworth> i thought the only way to get to the store was to go through lp
[18:18] <marcustomlinson> hellsworth: for a snap to be seeded it needs to, but otherwise no. If I'm remembering correctly kenvandine?
[18:19] <kenvandine> right
[18:19] <kenvandine> there is a policy for seeded snaps
[18:19] <kenvandine> we also utilize LP for automated builds
[18:22] <hellsworth> well since my local build is still going, i just launched a new LP build on ~hellsworth/gnome-3-34-1804-sdk
[18:22] <hellsworth> and that should publish to the store
[18:23] <hellsworth> but my build will be finished first. oh well. lp can publish it for me.
[18:24] <kenvandine> hellsworth: is your snap built from the git mirror?
[18:24] <kenvandine> if so that mirror isn't updating
[18:25] <hellsworth> well my lp build builds from ~ubuntu-desktop/gnome-sdk/+git/gnome-sdk
[18:25] <marcustomlinson> hellsworth: what you've done with gnome-3-34-1804, do with gnome-3-34-1804-sdk
[18:25] <hellsworth> and doesn't that just point to the git repo
[18:25] <marcustomlinson> Source: https://gitlab.gnome.org/Community/Ubuntu/gnome-sdk.git gnome-3-34-1804-sdk
[18:26] <hellsworth> oh yeah marcustomlinson your'e right
[18:32] <hellsworth> isn't gnome-3-34-1804-sdk a seeded snap?
[18:32] <hellsworth> so i should go through lp for this snap to get in the store?
[18:33] <hellsworth> well i'll push it anyways. you wouldn't have told me to if i shouldnt' :)
[18:33] <hellsworth> sometimes i overanalyze things...
[18:36] <kenvandine> nope
[18:37] <hellsworth> out of curiosity, where is the list of seeded snaps?
[18:42] <hellsworth> ok updated build snap in edge. rebuilding the platform snap now.
[19:08] <Trevinho> clobrano: nice, I read on #g-s as well, so.. Yeah somewhat similar to what I was guessing, but nice that we've a definition now
[19:14] <marcustomlinson> hellsworth: if you have time, you think you could give this suggestion a try today? https://gitlab.freedesktop.org/cairo/cairo/issues/382#note_278108
[19:16] <marcustomlinson> kenvandine: got a reply on that bug that looks promising ^
[19:18] <kenvandine> yeah, a build of gnome-3-34-1804-sdk with cairo 1.17 plus that patch shouldn't be too hard
[19:18] <kenvandine> or even just update the cairo part to use the git branch in that PR
[19:19] <hellsworth> well but how do we do that in the build snap? can i have the cairo portion in the build snap checkout a merge request?
[19:19] <marcustomlinson> hellsworth: https://gitlab.freedesktop.org/psychon/cairo/tree/invalid-free-crash
[19:19] <hellsworth> yeah ok i can use this persons branch
[19:24] <marcustomlinson> kenvandine: all 5 of my test apps are working now, I've promoted 3-32 build and platform snaps to stable
[19:25] <marcustomlinson> you can rebuild drawing and let that guy know the good news on forum.snapcraft.io :)
[19:25] <hellsworth> rebuilting gnome-3-34-1804-sdk with the invalid-free-crash branch of ciaro now
[19:25] <marcustomlinson> hellsworth: thanks!
[19:28] <hellsworth> i also had already built the build snap with cairo branch 1.16, pushed it to edge, rebuilt the gnome-3-34-1804 platform snap, pushed it to edge, moved it to stable and am rebuilding evince
[19:47] <hellsworth> evince still crashes for me when i have the build snap using cairo source-branch: 1.16. evince started ok, i went to open a pdf and when i selected a pdf and clicked open, i got a segfault
[19:48] <hellsworth> https://paste.ubuntu.com/p/43yg8JPWHT/
[19:48] <hellsworth> my build of the buildsnap with the invalid-free-crash branch is still going
[19:48] <marcustomlinson> hellsworth: you connected to the right platform snap?
[19:49] <marcustomlinson> You’ll need to connect to a platform snap that is also built from the new build snap
[19:51] <hellsworth> yep and i did that
[19:51] <marcustomlinson> hellsworth: also, the 1.16 branch may be broken as it’s WIP, I meant use the 1.16.0 tag
[19:51] <hellsworth> ah ok
[19:52] <marcustomlinson> The branch I believe has some 1.16.1 work in it
[19:52] <hellsworth> maybe that's the problem then.
[19:53] <marcustomlinson> hellsworth: but good to know that 1.16.1 is broken too. Could you leave a comment on that bug about that
[19:53] <hellsworth> i need to run in a little bit to pick up my daughter from daycare (closing early today because of snow) but i should at least be able to launch a build of the platform snap with the invalid-free-crash build snap first
[20:01] <marcustomlinson> Thanks hellsworth, appreciate it!
[20:05] <hellsworth> my pleasure :)
[20:19] <hellsworth> for some reason, my laptop can't build any snaps: https://paste.ubuntu.com/p/yRdDRvWJw3/
[20:19] <hellsworth> does anyone know how to fix this?
[20:19] <hellsworth> there is no /var/lib/dpkg/lock*
[20:20] <hellsworth> i can do other things like apt update (which wouldn't work if there was already a lock in place)
[20:20] <hellsworth> and my snapcraft version is the stable one (not one of my local builds)
[20:21] <marcustomlinson> hellsworth: that error is coming from the multipass vm not your host
[20:21] <hellsworth> hmm ok maybe i'll reinstall multipass
[20:22] <marcustomlinson> hellsworth: you could try ‘multipass delete snapcraft-evince’
[20:22] <marcustomlinson> Then ‘multipass purge’
[20:22] <hellsworth> ok i will try that
[20:25] <hellsworth> yep that worked!
[20:25] <hellsworth> thanks marcustomlinson
[20:25] <marcustomlinson> np, yeah those VMs can sometimes get into a funky state
[20:25] <hellsworth> ok i need to run and finish up the invalid-free-crash testing later tonight
[20:26] <kenvandine> later
[22:51] <ricotz> kenvandine, hi, https://launchpad.net/~ubuntu-desktop/+snap/gnome-calculator-master -- is this actually using vala 0.40.8 to build gnome-calculator from latest git master? :(


[19:32] <highvoltage> stgraber: another thing that we lost via ubuntu seeds was gnome-games. (which lead to us losing things like glchess, gnibbles, etc)
[19:32] <highvoltage> stgraber: I suggest that we add gnome-games back
[19:32] <highvoltage> stgraber: and I think since we can't ship stellarium on arm and since we want consistant packages across architectures, it's probably best to remove it
[19:34] <stgraber> highvoltage: ok, I'll remove stellarium. For gnome-games, can you check what dependencies that'd bring? for example I don't really want us to become the clutter maintainers ;)
[19:35] <stgraber> stellarium dropped
[19:35] <highvoltage> stgraber: I installed it on the livecd, no clutter, and in total it's around 10MB of .deb downloads
[19:36] <highvoltage> stgraber: ah, I lied
[19:36] <highvoltage> stgraber: there's libclutter :-/
[19:36]  * highvoltage checks what needs it
[19:36] <stgraber> k, no thanks then :) maybe the desktop team will start getting clutter stuff this cycle and we'll get it for free then
[19:37] <stgraber> also clutter performance on arm sucks apparently, I want any package we add to the seeds to be tested on armhf or we'll just end up having to remove them later on...
[19:37] <highvoltage> ok, so if I remove libclutter, then gnibbles, gnome-games, lightsoff, quadrapassel and swell-foop are emoved
[19:37] <highvoltage> *removed
[19:38] <highvoltage> so perhaps we should just ship the ones that doesn't depend on clutter (which at least still gives us a chess game)
[19:39] <stgraber> assuming the non-clutter ones are usable on arm
[19:40] <stgraber> highvoltage: did you end up getting a pandaboard @RLNX or are you still using the beagles?
[19:40] <highvoltage> stgraber: I think the pandaboard I have here is technically supposed to go back to the client, but they haven't collected it yet
[19:42] <stgraber> highvoltage: k, I think it'd be best to get Ubuntu 12.04 installed on a panda, install the video driver, then install edubuntu-desktop and check what works/what doesn't
[19:42] <stgraber> maybe try to upgrade to 12.10 but I'm not sure if that works yet
[19:42] <stgraber> ogra_: ^
[19:44] <highvoltage> stgraber, alkisg, mgariepy: btw we have an edubuntu meeting tomorrow
[19:44] <alkisg> highvoltage: ah nice, what time?
[19:44] <highvoltage> alkisg: 19:00 UTC
[19:45] <alkisg> Hmmm I'm not sure if I can make it, I'll try though
[19:45] <highvoltage> ok, we'll run through recent changes and work items and post the results to the list
[19:45] <highvoltage> I'd like to talk to the EC as well about sponsorship for Edubuntu, but we could perhaps do that by mail instead
[20:36] <jbicha> the Ubuntu Desktop Team plans to ship clutter on the 12.10 CD...
[20:37] <jbicha> totem will depend on it, gnome-sushi (a quick-previewer for nautilus) needs it...
[20:37] <highvoltage> http://tranzistors.wordpress.com/2012/05/29/progress-on-gnome-lockdown-2-mockups/
[20:38] <highvoltage> jbicha: thanks for the info


[03:37] <ahoneybun> the heck is going on with this "Flames_in_Paradise" mparillo ?
[04:45] <bshah> yofel: removed patch from kubuntu_unstable as that doesn't apply anymore after mck182's change got in. you will probably want new release for xenial (tar is already redone)
[06:53] <soee> hmm, right click on desktop not working, right click in other apps seems to be a bit laggy
[06:54] <soee> krunner can't find anything so as application lanuncher
[06:55] <valorie> in wily, or xenial?
[06:55] <soee> valorie: xenial
[06:55] <valorie> ok, I've not updated that laptop yet
[06:55] <soee> :)
[06:56] <soee> Plasma 5.5 is pretty cool, except some small issues
[06:56] <soee> but i see some randomness here
[06:58] <valorie> I saw you in #plasma, helping out
[06:58] <valorie> thank you for that
[07:02] <soee> yup devs helped and we found faulty code :) and Philip removed it from Frameworks 5.18 so it looks pretty stable now
[07:03] <soee> i'm happy looking at what is done now = new plasma, new frameworks and apps are wip
[07:04] <soee> and from what i see Plasma 5.6 is scheduled on 17 March so it should get into Xenial before release in april
[07:05] <soee> so to sum it up, 16.04 schould be damn cool release :)
[07:05] <valorie> have we done enough streamlining to make that possible?
[07:05] <soee> what exactly ?
[07:06] <valorie> getting this all done has been a pretty heavy life
[07:06] <valorie> lift
[07:07] <rww> If I want to poke around the new hotness in Kubuntu and don't mind stuff breaking, where would I be looking? xenial's repositories or add a PPA on top of that?
[07:07] <rww> (and if I have bugs with your answer, do you want them tagged/filed a special way?)
[07:08] <valorie> rww: we don't have plasma 5.4.3 backported to wily yet
[07:08] <valorie> and not sure we'll get it
[07:08] <soee> valorie: it is for Wily :)
[07:08] <soee> http://kubuntu.org/news/plasma-5-4-3-and-applications-15-08-3-for-kubuntu-15-10/
[07:09] <soee> Plasma 5.5 is no backported though
[07:09] <rww> So xenial?
[07:09] <soee> rww: i'm using xenial on my laptop like few weeks already
[07:10] <valorie> soee: have you been filing bugs in launchpad for xenial?
[07:10] <valorie> I've not been
[07:10] <valorie> oops, I meant 5.5.3 sheesh
[07:10] <valorie> I honestly saw very few differences with 5.4.3
[07:10] <soee> if you want to help testing new stuff use Xenial
[07:10] <rww> Just file bugs the usual-way using ubuntu-bug?
[07:10] <soee> valorie: not yet, i was waiting for Plasma 5.5 and new Frameworks
[07:10] <valorie> rww: my travel laptop is xenial
[07:10] <valorie> haven't upgraded for a few weeks though
[07:11] <valorie> rww: i always advise that
[07:11] <soee> i usually try to find someone here who can confirm some bugs and than i'm reporting them
[07:11] <valorie> it's the best
[07:12] <soee> but there are bugs in Plasma, Applications that are not our job
[07:12] <rww> sounds good. any mailing list in particular I should be on? kubuntu-devel?
[07:12] <soee> so then best to consult with Plasma devs
[07:13] <rww> for doing that on IRC, #kde-devel or somewhere better?
[07:13] <rww> sorry for all the questions, it's been a while
[07:13] <soee> rww: yes, on this list often some stuff to test is announced etc.
[07:13] <soee> rww: also #plasma
[07:13] <soee> plasma is for desktop environment - panel, widgets, kcms etc.
[07:14] <soee> kde-devel for applications
[07:15] <valorie> rww: I usually default to here first
[07:15] <rww> *nod*
[07:16] <valorie> those other chans second, and an ML next -- sometimes even when I get a good answer
[07:16] <valorie> everybody's on the list, and not everybody uses IRC
[08:18] <soee> i have fixed the right click
[09:10] <soee> yofel: ping me when you have 2 min
[10:32] <mparillo> ahoneybun: You talking about the bug reporter who originally reported https://bugs.launchpad.net/kubuntu-website/+bug/1532157 with two separate bugs in two separate components, who split out the second (more of a request actually) into Launchpad bug 1532372
[10:32] <mparillo> I fixed the first, and was asking for website permissions to fix the second
[11:00] <yofel> soee: ping
[11:04] <soee> yofel: i had problems with right click on desktop today. After some checks o noticed that not all Frameworks packages were updated to 5.18. Now i wonder why: yesterday i'v downgraded all to 5.17 than some packages where upgraded to 5.18 (when i was testing them). But after we wound faulty package i run upgrade with frameworks staging ppa enabled, so i thought all packages should be updates to 5.18 but they were not. Any idea why ?
[11:05] <yofel> not without knowing what exactly you told apt to do..
[11:06] <soee> :/
[11:06] <yofel> I did the same, but for me a dist-upgrade upgraded everything
[11:07]  * yofel uploads new kwallet
[11:09] <soee> again ?
[11:09] <yofel> the new tarball
[11:09] <soee> ah so mck182 fixed it ?
[11:10] <yofel> yep, and devid did a respin
[11:10] <yofel> *david
[11:10] <soee> cool
[11:15] <yofel> and let me rename discover again
[11:17] <yofel> Riddell: with https://git.reviewboard.kde.org/r/126680/ - would you also name the source plasma-discover please? We already have a 'discover' in the archive so we need to rename anyway
[11:19] <BluesKaj> Hi folks
[11:20] <yofel> hey
[11:21] <BluesKaj> hi yofel , how goes the battle ?  :-)
[11:22] <yofel> making progress, after I'm done renaming discover again I can start testing plasma 5.5 on wily
[11:22] <BluesKaj> right
[11:22] <yofel> apps OTOH, will probably take another week or so
[11:22] <yofel> (including the merges)
[11:24] <yofel> why do we have an amarok beta release in wily backports ppa o.O?
[11:24] <BluesKaj> ok yofel , good to know
[11:28] <soee> yofel: do you have machine with Xenial maybe ?
[11:28] <yofel> soee: yes?
[11:29] <soee> with 5.5.3 and 5.18 ?
[11:29] <yofel> yes
[11:30] <soee> please take a look how clipboard icon is rendered for me after reboot: https://www.youtube.com/watch?v=fN69H_HpSzQ
[11:30] <yofel> clivejo: I committed your amarok beta packaging to bzr, but that needs cleanup before it can be uploaded to xenial
[11:30] <soee> it was ok again when i moved back to 5.17 yesterday
[11:30] <mparillo> After upgrading to Plasma 5.5.3 on Xenial, Muon Update Manager seems to list updates available, but does nothing when I click on apply updates. Maybe I caught some things in progress. Using apt now and will report back next time updates are available.
[11:30] <soee> but after upgrading to 5.18 it happens again
[11:31] <yofel> my icon is fine here, but I have some other item that's completely invisible
[11:31] <soee> so it looks like it starts rendering - scaling up - but hangs in some moment
[11:31] <yofel> hm, could be panel size dependent then
[11:32] <soee> there are also some rendering problems when moving panel
[11:32] <soee> task manager items get strange size, loose spaces
[11:32] <soee> etc.
[11:33] <soee> so i'm sure that in 5.18 there was some other change that has influance on rendering
[11:33] <yofel> that's upstream bugs IMO
[11:34] <soee> yup, just wanted to find someone who can confirm them
[11:40] <clivejo> I did amarok beta packaging?
[11:41] <yofel> sometime in august it looks like
[11:41] <clivejo> :/
[11:41] <clivejo> maybe just practising
[11:41] <yofel> possibly, but it ended up in the stable backports ppa, so now we kind of have to support it
[11:42] <clivejo> is amarok on alioth?
[11:42] <yofel> no
[11:42] <yofel> and I wouldn't bother moving the qt4 version
[11:43] <yofel> or moving anything until we've decided what to do with our git stuff
[11:43] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/kde-extras/amarok.git/
[11:43] <clivejo> cant use that then?
[11:43] <yofel> no
[11:43] <clivejo> :(
[11:43] <clivejo> can we convert the bzr to a git archive?
[11:44] <yofel> well, you can on LP if you want to. But if we keep our own repo then preferably migrate the history
[11:44] <yofel> there was some bzr-git-import plugin IIRC
[11:44] <clivejo> as you know Im not fan of bzr
[11:45] <yofel> I'm not particulary a fan of it either, but for simply packaging branches it does the job just fine
[11:45] <yofel> *simple
[11:45] <yofel> but as I said, feel free to migrate the repo to git
[11:45] <clivejo> so why dont we use debian got?
[11:46] <clivejo> git
[11:46] <yofel> we talked about moving our stuff away, didn't we? So for now I wouldn't use alioth for stuff where we have our own repo
[11:47] <clivejo> ok :(
[11:47] <yofel> LP can do git just fine now. So use that if you really can't work with bzr
[11:49] <yofel> amarok looks so unmaintained that I really wouldn't bother investing much time in it anyway..
[11:49] <clivejo> I have a bad memory, its hard enough learning one batch of commands, but my brain just refuses to work with certain things
[11:49] <yofel> did you never use svn?
[11:49] <clivejo> nope
[11:50] <yofel> ah ok
[11:50] <yofel> then bzr and git will feel very different indeed
[11:51] <clivejo> I learned to program in Minux while at uni.  It put me off programming and I ended up in building management
[11:51] <clivejo> I havent really looked into programming since
[11:51] <clivejo> I have on and off days
[11:52] <clivejo> some days I can read and write code like it is second nature, other days its like some kind of alien language
[11:53] <yofel> even professionals have that, there it's called developaralysis
[11:53] <yofel> http://techcrunch.com/2014/10/18/you-too-may-be-a-victim-of-developaralysis/
[11:54] <clivejo> I prefer physical challeges now, plumbing, electrical, anything involving hands I guess
[11:55] <yofel> get yourself a raspi and start automating your house, then you get both sides :P
[11:55] <clivejo> I do :P
[11:55] <yofel> :D
[11:55] <yofel> come to think of it, our l10n stuff would benefit a lot from a git migration..
[11:55] <yofel> that uses a bazillion branches
[11:57] <clivejo> grrr my pup is possessed
[11:57] <yofel> what?!
[11:58] <clivejo> he ripped his bed apart this morning, I took him for a walk and stopped at my mothers house for breakfast.  Left him outside for 10mins and he ripped out all my motthers pot plants
[11:58] <yofel> . . .
[11:58] <clivejo> hes eating my welly at the moment
[12:00] <clivejo> while trying to sweep up the soil and clean the mess up he was trying to bite and run away with the brush
[12:03] <clivejo> I need to run into town for some supplies.  Need some flux ASAP
[12:05] <clivejo> has kwallet been fixed now?
[12:05] <bshah> aye
[12:05] <clivejo> uploaded?
[12:06] <bshah> no idea..
[12:06] <bshah> <- not a ~kubuntu-dev
[12:06] <yofel> yes
[12:06] <soee> clivejo: yofet tooked care of it
[12:06] <clivejo> is it in landing?
[12:07] <clivejo> ah yes
[12:07] <clivejo> kwallet-kf5 - 5.18.0a-0ubuntu1~ubuntu16.04~ppa1
[12:08] <yofel> bah, my epoch hackery isn't working
[12:08] <clivejo> has anyone tested this version ?
[12:09] <clivejo> only 44mins old
[12:10] <lordievader> Besides 16.04 are there other versions of Kubuntu that frequently require testing?
[12:11] <clivejo> lordievader: backports to wily?
[12:11] <clivejo> hi sick_rimmit, are you still sick?
[12:11] <yofel> what do you mean with frequently?
[12:12] <lordievader> Well, I can image that there are times to test something on 14.04 but not frequently anymore. Basically I am trying to figure out which installs I should have on my test box.
[12:12] <sick_rimmit> Yes :-(
[12:12] <clivejo> yofel: with kwallet fixed is Plasma5.5 ready for wily?
[12:13] <sick_rimmit> I am improving, but it really given me a hard time
[12:13] <yofel> clivejo: not until I'm done with discover - where I'm a bit stuck right now
[12:13] <clivejo> stuck?
[12:13] <clivejo> isnt it just a rename?
[12:14]  * clivejo says "just" like he knows the process of renaming a package
[12:14] <yofel> lordievader: generally, we "support" last LTS, current stable and dev. As we're currently developing the next LTS, the last one doesn't really recieve any attention anymore
[12:15] <yofel> clivejo: there's epochs involved...
[12:15] <yofel> I would like to drop those with the rename, but I didn't really want to rename the binaries *right now*, as the app itself only gets renamed for 5.6
[12:16] <lordievader> yofel: So, it is best for testing to have 15.10 (with backports) and 16.04 installed?
[12:16] <yofel> but the libdiscover is new and should not carry an epoch, but e.g. muon-discover depends on libdiscover (= ${binary:Version}) which needs an epoch that libdiscover doesn't have
[12:16] <yofel> -> boom
[12:16] <yofel> so I might go and rename the binaries after all :/
[12:17] <yofel> and just leave the epoch on the transitional packages with loose deps
[12:17] <yofel> lordievader: yes
[12:17] <lordievader> Check, thanks :)
[12:18] <BluesKaj> I have muon on xenial by installing libmuon first then muon itself
[12:19] <yofel> talking about that..
[12:19] <BluesKaj> bbl
[12:19] <yofel> sick_rimmit: how's muon maintenance working out?
[12:23] <mparillo> I applied the updates to Xenial with Plasma 5.5.3, and after rebooting, I no longer needed to enter my WEP password, but now I have to enter my kwallet password to connect to WiFi.
[12:24] <yofel> mparillo: did you remove pam_kwallet.so from the pam config?
[12:24] <yofel> *kwallet5
[12:28] <mparillo> No, is that they way we will eventually ship 16.04?
[12:28] <ovidiu-florin> mparillo: hello
[12:29] <ovidiu-florin> can that card be closed?
[12:29] <yofel> mparillo: no, I just remembered us talking about it. But that really should work..
[12:29] <yofel> I'll test it in a bit
[12:30] <mparillo> In general, I prefer to remain pretty vanilla, (not to mention I do not know how to change my pam config), but I would be happy to test with you.
[12:30] <mparillo> ovidiu-florin: Which card, the Wikipeadia card?
[12:33] <mparillo> sudo nano /etc/pam.conf ?
[12:33] <mparillo> Mine is all comments.
[12:34] <yofel>  /etc/pam.d/sddm should have 2 lines with pam_kwallet5.so
[12:36] <mparillo> So I comment out by: # -auth   optional        pam_kwallet5.so
[12:37] <yofel> that shouldn't be commented out
[12:37] <mparillo> # -session optional       pam_kwallet5.so auto_start
[12:37] <ovidiu-florin> mparillo: yes the wikipedia card
[12:39] <mparillo> So, after editing, cat  /etc/pam.d/sddm | grep pam_kwallet5.so shows both lines as commented out
[12:40] <mparillo> ovidiu-florin: I am content with the wikipedia card being closed, assuming nobody else has any suggestions. After 16.04, I would want to update Wikipedia again, but that can be a new card if you prefer.
[12:40] <mparillo> re-booting to test the kwallet for wifi password.
[12:42] <yofel> mparillo: they should NOT be commented out
[12:44] <yofel> ok, discover building, let me try out kwallet
[12:48] <ovidiu-florin> yofel: what heppend to the Trello->IRC bot?
[12:48] <yofel> that was implemented in kubotu, whose server seems to be dead
[12:50] <yofel> mparillo: kwallet works fine for me now
[12:56] <mparillo> OK, that was way too painful
[12:57] <mparillo> I removed the comments and reverted
[12:59] <yofel> discover rework finished, my last couple commits could do with a review if someone wants to (sgclark, clivejo ?)
[12:59] <yofel> plasma 5.5 users might have to force-downgrade libdiscover
[13:01] <bshah> oopsie.. yet another version downgrade..
[13:01] <bshah> hmmm
[13:02] <yofel> sorry about that
[13:05] <yofel> ovidiu-florin: something I just realized for the packaging docs, I strongly recommend every packager to have a ~/.dput.cf with this content:
[13:05] <yofel> [DEFAULT]
[13:05] <yofel> default_host_main = ppa
[13:05] <yofel> this isn't that important for beginners, but really important for every person with primary archive upload permissions
[13:06] <yofel> and by that time, you can easily forget to add that
[13:35] <yofel> hm, kwallet-pam is missing transitional packages
[13:36] <yofel> or updating the recommends in plasma-desktop should work as well
[13:47] <clivejo> testing from landing?
[13:48] <yofel> that's what I'm doing
[13:48] <yofel> still finding stuff to fix, but slowly running out
[13:49] <sgclark> just woke up, need at least a cup of coffee lol
[13:49] <clivejo> you say that like its a bad thing!
[13:49] <yofel> well, the first part is the bad thing
[13:49] <yofel> but I think we can do a public tester call this evening
[13:50] <sgclark> sorry whats going on?
[13:50]  * clivejo cheers and does happy dance
[13:50] <yofel> sgclark: talking about plasma
[13:50]  * sgclark scrolls
[13:53] <sgclark> mm bouncer did not keep enough to be useful. I will look at the notes.
[13:54] <clivejo> sgclark: mailing list might be more helpful, basically KDE have respun a tarball for kwallet
[13:54] <sgclark> ahhh
[13:54] <yofel> sgclark: I would appreciate it if you could review my discover rename
[13:54] <yofel> the rest we pretty much took care of
[13:55] <clivejo> yofel: how do I review?
[13:55] <yofel> just look at the last 5 commits in kubuntu_xenial_archive
[13:56] <yofel> the idea was to rename to the coming 5.6 name, drop the epoch and only add the epoch for the transitional packages
[13:56] <clivejo> does the debian git branch get renamed too?
[13:56] <yofel> no, git matches the upstream source name
[13:57] <yofel> thinking about it, my changes probably screwed up the CI
[13:57] <yofel> oh well
[13:57] <clivejo> yofel:  in rules $(overridden_command) --dbg-package=muon-discover-dbg
[13:58] <sgclark> lots of broken merges I see, I can work on those today
[13:58] <clivejo> rename there too or no?
[13:58] <yofel> clivejo: that's fixed in some other commit
[13:58] <clivejo> is it?
[13:58] <clivejo> I thought I was current
[13:58] <yofel> It's fixed here and I have no diff and nothing to push..
[13:59] <clivejo> ah I see it now
[13:59] <clivejo> what does muon.postinst do?
[14:00] <yofel> nothing useful, delete
[14:00] <yofel> I forgot to do that
[14:00] <sgclark> I cant seem to find the repo
[14:00]  * sgclark needs more coffee
[14:00] <yofel> plasma/discover.git
[14:00] <sgclark> ah
[14:00] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/plasma/discover.git
[14:01] <clivejo> the language files arent installed?
[14:02] <clivejo> oh muon-exporter, what ever that is
[14:02] <yofel> I have no idea what muon-exporter is supposed to be
[14:02] <clivejo> will upstream rename too?
[14:03] <yofel> clivejo: https://git.reviewboard.kde.org/r/126680/
[14:03] <yofel> that's where I got the names from
[14:04] <clivejo> I see
[14:06] <clivejo> if you have custom wallpaper does plasma change it back to default?
[14:06] <yofel> it shouldn't
[14:06] <clivejo> only if you use the default already?
[14:07] <yofel> yep
[14:08] <clivejo> where is the updated kwallet tarball?
[14:08] <clivejo> depot?
[14:08] <yofel> yes
[14:10] <sgclark> yofel: the lintain-overrides still contain conent for muon, is that on purpose?
[14:10] <clivejo> whats the tool that scans for orphaned files?
[14:10] <yofel> sgclark: the binaries are still called muon-* for now, so I just fixed the package names in the lintian-override files
[14:10] <yofel> clivejo: orphaned files?
[14:11] <sgclark> ok
[14:11] <clivejo> files that apt may have left behind?
[14:11] <sgclark> there is a tool for that?!
[14:11] <yofel> apt never leaves stuff behind, except config files
[14:11] <clivejo> or I installed manually
[14:11] <clivejo> there was a tool for it
[14:11] <clivejo> compared the physical files to apt
[14:11] <yofel> and if config files are left then the package is still in the dpkg DB as uninstalled/configured or so
[14:12] <yofel> there is debsums, but that's checksum checking for installed packages
[14:12] <clivejo> I had a problem with kde theme for sddm
[14:13] <clivejo> I used a tool before called fluff or lint or something like that
[14:14] <yofel>  /lib/x86_64-linux-gnu/security/libpam_kwallet5.so
[14:15] <yofel> that probably won't work if our sddm profile says "pam_kwallet5.so" which was the lib name in the old package
[14:15] <yofel> and as all other files in there are called pam_*, I wonder why kwallet is suddenly called libpam_*
[14:15] <yofel> anyway
[14:15]  * yofel out shopping, bbl
[14:16] <soee> yofel: http://pastebin.com/uJRLKugs
[14:16] <soee> are you working on discover and it causes some problems ?
[14:17] <sgclark> yofel: looks good to me.
[14:22] <clivejo> I think I prefered the old plasma icons for shutdown/reboot etc :/
[14:23] <vishalrao> clivejo: you mean the colourful ones or the monochromatic ones?
[14:23] <clivejo> mono ones
[14:24] <clivejo> eakk
[14:24] <vishalrao> me too, the mono ones seem to be there on the default app launcher, but the ugly colourful ones on the menu launcher (this is on plasma 5.4.3 sorry, seem to be same for plasma 5.5.3 IINM)
[14:25] <clivejo> just switch the them
[14:25] <clivejo> theme
[14:25] <clivejo> I no likey!
[14:25] <vishalrao> theme to what?
[14:25] <soee> can someone test one thing: if you create new user account and login there, it will use old oxygen icons
[14:25] <clivejo> dark breeze
[14:26] <clivejo> yuck yuck yuck
[14:28] <sgclark> I liked the old ones too, new ones dont seem to fit
[14:30] <vishalrao> soee: seem to be regular breeze icons in new account for me
[14:30] <clivejo> hmmmm
[14:30] <vishalrao> soee: oh wait, yeah, the right click menu seems to be old oxygen icons, same on buttons etc
[14:31] <clivejo> Im gonna have to look for a new theme
[14:31] <clivejo> any suggestions?
[14:31] <vishalrao> can't the breeze theme be modified to use the old mono icons (if the mono icons are still in there) ?
[14:32] <soee> iconset or desktop theme ?
[14:32] <soee> vishalrao: ok thanks for checking
[14:35] <clivejo> I like the dark breeze kickoff menu and taskbar, but the light breeze for windows and rest of system
[14:36] <sgclark> ok, I am confused, I still see alot of red, but we are ready for testing?
[14:37] <clivejo> red for what?
[14:38] <sgclark> apps
[14:38] <soee> plasma and frameworks shoudl be ready
[14:38] <soee> apps are not
[14:38] <sgclark> oh
[14:38] <sgclark> ok
[14:38] <soee> yofel: said 1 week is needed for finieh the, :)
[14:38] <clivejo> plasma 5.5.3 is ready for testing
[14:39] <sgclark> cool ok
[14:39] <clivejo> apps 15.12.0 still needs work
[14:39] <mparillo> It seems as if the muon changes (muon-discover muon-notifier muon-updater) are held back
[14:39] <sgclark> got it, I am clear now thanks
[14:39] <clivejo> ovidiu-florin: you still want to finish okular?
[14:40] <soee> mparillo: confirmed here
[14:44] <clivejo> BTW does kubuntu not brand the kickoff menu icon?
[14:44] <soee> yofel: http://paste.ubuntu.com/14447156/
[14:45] <ovidiu-florin> clivejo: yes, but I'm still kind of tired
[14:45] <ovidiu-florin> and it's hard for me to focus on reading the symbols documentation for packaging
[14:46] <ovidiu-florin> and my keyboard looks backwards
[14:47] <ovidiu-florin> if you can explain it to me in a few simple words, I might get it faster
[14:47] <sgclark> kubuntu does not brand much of anything.
[14:48] <sgclark> ovidiu-florin: as you probably know there is nothing simple about symbols. But you can run that command in the README I pointed out yesterday for a quick start.
[14:55] <ovidiu-florin> sgclark: but I'm not sure I understand the prboblem yet
[14:56] <sgclark> ovidiu-florin: sorry I don't understand
[14:58] <yofel> soee: sudo apt install libdiscover=5.5.3a-0ubuntu1~ubuntu16.04~ppa1
[14:58] <yofel> the rest should figure itself out after that
[15:01] <yofel> mparillo: for you too: sudo apt install libdiscover=5.5.3a-0ubuntu1~ubuntu16.04~ppa1
[15:01] <yofel> BluesKaj: ^
[15:03] <BluesKaj> yofel:  but i don't want muon discover, I'll stick with plain muon, but thanks anyway :-)
[15:03] <yofel> ah right
[15:04] <yofel> hm, I really don't get why our kwallet modules are called libpam suddenly
[15:05] <ovidiu-florin> sgclark: I'm not sure I understand the symbols problem with the okular package
[15:06] <yofel> ovidiu-florin: did you kind of get the point of having symbol files yet?
[15:06] <ovidiu-florin> I understand teh point of having them
[15:07] <yofel> ok, so the problem right now with okular is that the symbol table in the packaging doesn't match with the one generated at build time from the built binary
[15:07] <soee> yofel: worked
[15:07] <ovidiu-florin> https://paste.kde.org/pvgywrux2
[15:08] <ovidiu-florin> yofel: that seems pretty obvious, that they would not match, since it's a newer version of the software.
[15:08] <ovidiu-florin> Why are the symbol files stored in the packaging?
[15:09] <yofel> if you look into the file, you will see that every symbol has the okular version that it appeared in appended to it
[15:10] <yofel> that information is used by dpkg-shlibdeps to generate properly versioned library dependencies for packages that use libokularcore
[15:11] <yofel> it is also used to make sure that no symbols disappear between releases without upstream updating the so version of the library
[15:12] <yofel> that would be an ABI break and would cause applications to fail to run like this: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5: undefined symbol: _ZTIN7Akonadi8Protocol7CommandE
[15:13] <yofel> that's why the package actually fails to build when a symbol goes missing
[15:13] <yofel> (for C++, that's not sufficient actually and you need abi-compliance-checker, but that's a different topic)
[15:14] <yofel> now okular did change the soversion from 6 to 7, and clive updated the packaging to reflect this, he just didn't get to update the symbol files
[15:14] <yofel> so you now need to update the symbol files in the packaging, remove any #MISSING# lines from them and you're done
[15:15] <ovidiu-florin> ok
[15:15] <ovidiu-florin> I understand what needs to be done
[15:16] <ovidiu-florin> but still I don't understand why it is the package's responsibility to make sure backwards compatibility is not broken?
[15:16] <yofel> because the software authors cannot be trusted
[15:17] <yofel> so this is a very basic saftey measure, as well as information for dpkg-shlibdeps to generate proper deps
[15:17] <yofel> latter was what the file was really meant for when it was introduced for C applications
[15:22] <ovidiu-florin> "<yofel> because the software authors cannot be trusted" - This seems like a very big issue to me
[15:22] <yofel> well, C++ ABI rules are so mental, that most developers don't even know all of them and end up breaking them by accident
[15:22] <yofel> and KDE CI still has no ABI check AFAIK
[15:23] <sgclark> still has no what?
[15:23] <yofel> sgclark: does build.kde.org run abi-compliance-checker yet?
[15:23] <sgclark> yet? I have heard nothing about this requirement
[15:24] <yofel> I'm pretty sure that was talked about a while ago, but ben either didn't seem interested or didn't have time as usual
[15:24] <yofel> but without kde upstream validating ABI, we have to
[15:24] <sgclark> well no one told me... it is my ci now
[15:25] <sgclark> I will add a workitem for it, now that I am aware..
[15:25] <yofel> it's not a requirement. It's just a good-to-have thing for the kde parts that guarantee a stable ABI
[15:25] <sgclark> yep, agreed, I will work on it
[15:26] <yofel> ovidiu-florin: regarding the c++ rules, enjoy the read: https://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B
[15:26]  * yofel -> lunch
[16:02] <yofel> wtf
[16:02] <yofel> if I compile kwallet-pam by hand I get pam_kwallet5.so
[16:04] <yofel> eeeeeeeeeeehm
[16:04] <yofel> debian/patches/fix_install_location.diff
[16:04] <yofel> -set_target_properties (${library_name} PROPERTIES PREFIX "")
[16:10]  * yofel talks to maxy..
[17:21] <clivejo> anyone using activites?
[17:27] <clivejo> On Plasma 5.5.3 I have a few activities for different tasks.  I have one for Kubuntu and I added an icon.  I want to add an icon for OSM but the select file dialogue box wont work.  Can anyone confirm?
[17:50] <acher88> Hmmm.. The file picker comes up below the preceding 2 dialogue boxes here, and so is unusable
[17:50] <clivejo> same here acher88
[17:50] <clivejo> I guess that makes it a bug
[17:52] <acher88> I can close the other 2 as well, but not the file picker.
[17:52] <acher88> Have to kill that window which nukes plasmashell as well
[17:54] <acher88> Hmm. on 2nd try it's now at least closeable. odd
[17:55] <clivejo> hummmm now I cant get logged on to bugs.kde.org
[17:56] <clivejo> fancy reporting it acher88?
[17:57] <acher88> https://bugs.kde.org/show_bug.cgi?id=357533
[17:58] <clivejo> acher88: your on fedora?
[17:58] <clivejo> oh no, thats not you
[17:59] <acher88> Nope. Thought best to do a quick search first
[18:00] <clivejo> is my KDE ID not the same one I use for KDE Etherpad?
[18:00] <acher88> not a clue
[18:00] <clivejo> weird
[18:02] <clivejo> will you add a me too on that bug?
[18:03] <acher88> can't just this sec, and I think I'm going to have to re-register if I want to anyway
[18:04] <clivejo> hi Rick_Timmis
[18:07] <clivejo> Anyone know if and how can I setup two Quassel windows, each in a different activity and save/lock them to those activities?
[18:08] <clivejo> I want one on my Kubuntu activity and one on my OSM
[18:15] <sgclark> clivejo: no bugs.kde.org is seperate login
[18:17] <sgclark> I can change icons for activities, or am I mis understadning thee issue?
[18:19] <clivejo> I can change it, but I want a custom one
[18:19] <clivejo> not one already on the system
[18:19] <mparillo> acher88: For bugs.kde.org, you use an e-mail.
[18:20] <mparillo> It is public, so I use an ancient hotmail one, because I was afraid of spam, but I do not seem to get any.
[18:20] <clivejo> if I select "Other Icons:" and click the "Browse.." button, the window to select the file on local filesystem wont let me pick a file
[18:21] <clivejo> thankyou mparillo!!
[18:27] <acher88> Like: http://i.imgur.com/tuLbO1Z.png
[18:28] <clivejo> yup
[18:28] <mparillo> clivejo: You are welcome, but for what? Adding a me-too on the bug?
[18:29] <clivejo> to use my email to log in
[18:29] <clivejo> Ive been trying to get logged onto bugs.kde.org for about 20mins now!
[18:29] <clivejo> I was about to reset my password
[18:29] <clivejo> thats why I thanked you!
[18:30] <sgclark> ahh yes, confirmed
[18:31] <clivejo> not only does it appear behind the other windows, when you do drag it in front, it doesnt work7
[18:31] <sgclark> I marked the bug as confirmed. thanks all
[18:33] <mparillo> clivejo: My pleasure. I have lobbed plenty of bugs there (but not enough karma to allow me to mark a bug as confirmed, so thank you sgclark), so logging in with an e-mail is fresh in my mind.
[18:33] <acher88> I shall check in Arch/Chakra
[18:34] <acher88> ditto. the same
[18:34] <acher88> not that I doubted it would be after all that....
[18:35] <clivejo> interestingly, if you add the icon via the Kickoff menu customise, it shows up to add to add it as an activities icon
[18:37] <acher88> by the way, if you switch kickoff to an application dashboard and then r-click to edit settings, I had an error on both real machine and VM
[18:38] <acher88> had to install a couple of extra kf5/qml packages to make that work
[18:38] <acher88> seemed to not get pulled in by default on the plasma install/upgrade
[18:39] <clivejo> the dropbox icon in dark breeze theme isnt very nice :/
[18:41] <acher88> qml-module-qt-labs-folderlistmodel and qml-module-qt-labs-settings
[18:58] <sgclark> yofel: artikulate lintain errors are directly related to some changes you made. I made a note in the notepad if you would go ahead take a look when you have time.
[18:59] <clivejo> sgclark: how are pim packages coming along?
[19:00] <yofel> looking
[19:00] <sgclark> ok, but I doubt it will be done today. I plan to have some saturday to relax
[19:02] <yofel> actually clive did that, and it looks like he added some files that were in not-installed so far
[19:02] <yofel> those symlinks really shouldn't get installed
[19:02] <clivejo> what did I do?
[19:03] <yofel> look at linitian
[19:03] <clivejo> non-dev-pkg-with-shlib-symlink ?
[19:04] <yofel> all errors
[19:05] <clivejo> Im seeing 6 warnings?
[19:05] <yofel> yes, and the bold ones need fixing
[19:06] <clivejo> --> https://paste.kde.org/p8noudmfm
[19:06] <yofel> look at the status page, not the build log
[19:07] <clivejo> what status page?
[19:07] <yofel> http://qa.kubuntu.co.uk/ppa-status/applications/build_status_15.12.0_xenial.html
[19:07] <clivejo> its orange?
[19:07] <clivejo> or yellow :P
[19:07] <yofel> click at show/hide for artikulate
[19:08] <clivejo> wow, I didnt know it did that!#
[19:08] <clivejo> is that new?!?
[19:08] <yofel> that was there since script version one...
[19:09] <clivejo> ok, so what did I do wrong?
[19:09] <yofel> read up on what non-dev-pkg-with-shlib-symlink means
[19:10] <yofel> regarding package-name-doesnt-match-sonames, you simply didn't update the artikulate.lintian-errors file
[19:11] <clivejo> Shared libraries are supposed to place such symbolic links in their respective "-dev" packages, so it is a bug to include it with the main library package.  However, if this is a small package which includes the runtime and the development libraries, this is not a bug. In the latter case, please override this warning.
[19:11] <clivejo> there is no -dev package
[19:12] <yofel> right, why is that?
[19:12] <clivejo> private lib?
[19:12] <yofel> yes, no headers shipped for it
[19:12] <clivejo> so it should be in not installed?
[19:12] <yofel> yes
[19:13] <clivejo> ah
[19:15] <clivejo> so all the libs, sym links and all, go in not-installed?
[19:15] <yofel> no, only the symlinks
[19:15] <yofel> look at not-installed, they're already in there, just with the old, now broken syntax
[19:16] <yofel> if you put the libs in not-installed instead of shipping them artikulate would hardly work, would it ^^
[19:17] <clivejo> it might, by magic
[19:23] <clivejo> ok uploaded and commited
[19:33] <clivejo> yofel: does digikam provide KF5KipiConfig.cmake ?
[19:33] <sgclark> clivejo: new framework I believe
[19:34] <clivejo> sgclark: do you know what provides it?
[19:34] <clivejo> its a built dep of gwenview
[19:34] <sgclark> nope. googling..
[19:35] <yofel> kipi was libkipi in the past
[19:35] <yofel> no idea if that's ported yet
[19:35] <yofel> libkipi qt4 edition was part of apps
[19:36] <sgclark> oh libkipi and it is red
[19:36] <clivejo> oh its part of apps 15.12?
[19:36] <sgclark> yeah
[19:36] <clivejo> ah
[19:36] <sgclark> it is there and red
[19:36] <clivejo> explains a lot!
[19:47] <Riddell> clivejo: I don't think kf5kipi exists yte
[19:47] <Riddell> if gwenview or something is asking for it you can just ignore that
[19:56] <sgclark> hi Riddell!
[20:17] <Riddell> hola sgclark
[21:16] <murthy> Riddell: hi
[21:18] <murthy> Will i be given permission to post a fsf survery article link on the kubuntu channel?
[21:20] <murthy> yofel: ^
[21:30] <murthy>  valorie ?
[21:39] <valorie> go for it
[21:41] <murthy> thanks
[21:43] <claydoh> Is muon package manager broken, or is it dead?
[21:43] <claydoh> in 16.04
[21:45] <valorie> sick_rimmit: ^^^
[21:45] <valorie> how's it coming along?
[21:45]  * valorie hopes that muon is alive and well
[21:46] <valorie> and sick_rimmit too
[21:46] <valorie> <3
[21:46] <mparillo> Did sick_rimmit volunteer to keep muon package manager going? https://lists.ubuntu.com/archives/kubuntu-devel/2015-November/010137.html
[21:46] <mparillo> Ahh, valorie is sooooo fast.
[21:47]  * claydoh agrees with valorie, hopes both sick_rimmit and muon are ok
[21:48] <valorie> I'm pretty sure he would welcome patches to fix bugs.....
[22:08] <murthy> valorie: Did we get a new muon maintainer ?
[22:10] <valorie> yes, Rick Timmis
[22:10] <valorie> but whether he's taken over officially I don't know
[22:11] <valorie> and there
[22:11] <valorie> s the man in question
[22:12] <valorie> Rick_Timmis: do you need a paste of the conversation about you and muon?
[22:12] <murthy> super
[22:12] <murthy> finally muon will get some love
[22:14] <valorie> I like it so much better than synaptic, or any "software store"
[22:14] <murthy> +1
[22:19] <DarinMiller> BTW, if anyone is fighting the 16.04 daily download install bug,  unsquashfs'd the /casper/filesystem.squahfs file from 16.04 live usb.
[22:20] <DarinMiller> Replace /usr/lib/ubiquity/plugins/ubi-prepare.py with the same file from 15.10,  and mksquashfs squashfs-root filesystem.squashfs -b 1024k -comp xz -Xbcj x86 -e boot
[22:21] <DarinMiller> copy the filesystem.squahfs back to the live usb /casper directory and Bob's your uncle....
[22:24] <valorie> DarinMiller: please write to the kubuntu-devel list about that
[22:24] <valorie> sounds like a packaging issue
[22:24]  * valorie heads off to Star Wars
[22:25] <valorie> finally
[22:25] <yofel> enjoy :)
[22:26] <DarinMiller> The ubi-prepare.py a bug has been reported and triaged, but it has not landed in the daily downloads.  Someone posted here the other day that they could not install via the daily  dowload.
[22:27] <DarinMiller> Side note, the resulting install seem incomplete... debugging now.
[22:32] <DarinMiller> Nevermind.  Looks like the install did not go well.  Permissions were transferred to my username when I unsquahed.  Need to check if unsquash can preserve owership of files.
[23:42] <clivejo> is ricktimmis internet connection sick too?


[13:50] <ficol> hello, it's not working when I wanna switch between tabs on firefox with ctr+1, ctrl+2 and so on
[13:50] <ficol> what can I do about it?
[14:30] <ficol> lads?
[14:32] <g4z_> can you use alt+1 and alt+2 instead?
[14:33] <ficol> oh yes
[14:33] <ficol> but I don't want that
[14:34] <g4z_> i don't know how to customise it. i use the defaults
[15:20] <dust> ubuntu-drivers-common:i386:
[15:20] <dust>  Depends: python3-apt but it is not going to be installed
[15:20] <dust>  Depends: python3-xkit  but it is not installable
[15:20] <dust>   Conflicts: ubuntu-drivers-common  but 1:0.4.22 is to be installed
[15:36] <vaba> i remove xfce4 power manager and light locker works very well!
[15:37] <vaba> in lubuntu
[15:37] <vaba> from lubuntu
[15:37] <vaba> i was removed xfce4 power manager and light locker works very well!
[15:43] <vaba> !info xfce4-power-manager
[19:45] <fishcooker> is channel lubuntu-devel private?
[19:48] <krytarik> fishcooker: No, but keep in mind that it's for development purposes.
[19:52] <fishcooker> i've joined, krytarik can't wait about the lxqt dev for next lubuntu-dev
[19:53] <tsimonq2> fishcooker: Any specific questions? I'm the guy working on that. ;)
[19:55] <fishcooker> ic your name on the https://wiki.ubuntu.com/Lubuntu/ReleaseSchedules, i just checking the mailinglist first
[19:55] <fishcooker> tsimonq2:


[01:41] <NyanCat> Lubuntu does not like being awoken from suspension on Aspire One 725-0826
[01:42] <NyanCat> latest 64-bit
[01:42] <NyanCat> Just an illuminated black screen
[01:42] <NyanCat> Suspension method was lid close
[01:42] <ianorlin> does control alt f1 do anything?
[01:42] <NyanCat> no
[01:51] <phillw> NyanCat: all suspension bugs have a really low priority. it boots so quickly, that the efforts of the devs are to keep that up. As different kit can handle acpi suspend differently - they've stopped worrying about it.
[01:52] <phillw> I think that happened at about 13.10
[01:57] <phillw> NyanCat: that is not to say a well reported bug will not be actioned, just that a generic "It wont start from hibernation / suspension" type of bug is going no where.
[01:58] <NyanCat> phillw, I don't want to go back to regular ubuntu either, but i guess we all have to make decisions that we dont like sometimes\
[02:01] <phillw> NyanCat: hibernation is ubuntu core, so if you find a difference - please let lubuntu know.
[02:02] <NyanCat> phillw, i'm telling you right now
[02:02] <NyanCat> there is a difference
[02:02] <phillw> this early in the cycle is good, as it allows our devs to go hunting.
[02:02] <NyanCat> because suspension on ubuntu works fine
[02:02] <phillw> NyanCat: then raise a bug
[02:03] <phillw> you raise a bug, give me the number and I'll pass it up the line faster than is normally done. Do we have a deal?
[02:07] <NyanCat> phillw, i cannot do that right now though
[02:07] <NyanCat> lol
[02:07] <phillw> NyanCat: open a terminal and issue the command
[02:07] <phillw> ubuntu-bug
[02:07] <phillw> once you decide what you think it might be, that system will hold your hand and help file a bug that the devs can act upon.
[02:10] <phillw> NyanCat: at least you now have the instructions, it is from the session after mine at http://irclogs.ubuntu.com/2013/06/24/%23ubuntu-classroom.html#t21:00
[02:11] <phillw> Brian explained how useful the ubuntu-bug was
[16:49] <Exilie> hi
[16:50] <Exilie> are there any italian for helpme?
[16:50] <Exilie> my english is not very good :)
[16:50] <holstein> !it
[16:51] <Exilie> thx
[17:23] <dust> !de
[17:23] <dust> !uk
[17:23] <dust> !us
[17:23] <dust> !ca
[17:23] <dust> cool :D
[17:24] <dust> !cn
[18:20] <Garbonzo> !el
[18:20] <Garbonzo> awesomes
[18:20] <wxl> btw rather than filling the channel up, you can msg ubottu Garbonzo
[18:24] <dust> !kernel
[18:25] <dust> so no actual info about what is used now
[18:25] <holstein> dust: everything is open.. what are you wanting to know?
[18:25] <dust> what the bot is able to do
[18:26] <holstein> !bot
[18:31] <dust> nice
[19:53] <jean_> Hi there, I need help to configure the sound on my lubuntu : there is no sound, neither in Firefox, nor in Gnome MPlayer...
[19:55] <jean_> What should I do ?
[19:55] <wxl> jean_: open alsamixer in terminal
[19:56] <jean_> wxl : ok, done
[19:57] <wxl> jean_: 1s
[19:57] <jean_> With F6, I can choose between : C-Medi CMI8737, C-Medi CMI8738 and Intel ICH7
[19:58] <jean_> C-Media instead of C-Medi
[19:58] <jean_> I retry : With F6, I can choose between : C-Media CMI8738, C-Media CMI8738 and Intel ICH7...
[20:01] <wxl> jean_: is anything muted?
[20:01] <wxl> it would show [00] instead of [MM] if it is
[20:03] <jean_> 3D Contr is MM, PCM is 00, synth is 00, Line is MM, Phone is MM
[20:03] <wxl> you might want to turn on your pcm
[20:03] <jean_> beep is 00 Aux is MM ans Four Cha is 00
[20:04] <jean_> wxl : How can I turn it on ?
[20:04] <wxl> m
[20:06] <jean_> ok, using m, I can swith between 00 and MM, but no sound again
[20:06] <wxl> do you have pulseaudio installed?
[20:06] <wxl> how are you testing sound? you should use aplay with some wav file in cli
[20:06] <jean_> I don't know
[20:07] <jean_> using gnome mplayer to test
[20:10] <wxl> jean_: pastebin the results of lspci -vvnn please
[20:12] <jean_> wxl : http://pastebin.com/0G0MuhT8
[20:14] <wxl> well you're using drivers, so that's a good sign :)
[20:14] <jean_> wxl : cool :-)
[20:18] <wxl> jean_: do you have a Master, or Speaker?
[20:19] <wxl> jean_: this is old bvut may provide some insight http://ubuntuforums.org/showthread.php?t=1272837
[20:20] <jean_> Yes Master... Volume is 100<>100 (but no swith between 00 and MM on it)
[20:20] <wxl> if you google the device id (13f6:0111) and ubuntu or linux there's a lot of "no sound" thingys :)
[20:22] <jean_> this is my aplay -L result : http://pastebin.com/J5DSDzYA
[20:23] <jean_> yes, I see...
[20:27] <jean_> wxl : there is this thread : https://bbs.archlinux.org/viewtopic.php?id=43564 but /etc/modprob.conf doesn't exists in Lubuntu...
[20:27] <wxl> modprobe.conf jean_
[20:28] <jean_> yes modprobe.conf isn't in /etc...
[20:29] <wxl> jean_: you could probably add it and/or add it to /etc/modprobe.d/alsa-base.conf
[20:30] <jean_> I try it, and after, is there a command to restart the daemon ?
[20:31] <wxl> well it's a matter of reloading kernel modules i believe
[20:31] <wxl> you could use modprobe to do that
[20:31] <wxl> it'd probably be easier to just restart :)
[20:35] <jean_> Restarting...
[20:35]  * wxl crosses his fingers
[20:40] <jean_> wxl : working ! I added  : "options    snd-intel8x0 ac97_quirk=1" in /etc/modprobe.d/alsaèbase.conf, and restarted the computer ! Cool ! Thanx
[20:40] <wxl> jean_: no problem!
[20:41] <wxl> jean_: if you have any further hardware problems, i encourage you to get the device id from lspci and then google it with "linux" or "ubuntu" and you'll usually figure out your own problem :)
[20:41] <wxl> jean_: are you already on the mailing list?
[20:42] <jean_> wxl : I'm not on the mailing list...
[20:42] <wxl> jean_: you should join!
[20:42] <jean_> where ?
[20:43] <wxl> jean_: i'd suggest blogging about this topic and sharing with the mailing list. if you don't have a blog, just post to the list for others
[20:43] <wxl> jean_: http://lists.ubuntu.com/lubuntu-users
[20:44] <jean_> ok
[20:44] <wxl> there's plenty of ways to contribute to the team, too, if you're interested in helping the project!
[20:47] <wxl> jean_: https://wiki.ubuntu.com/Lubuntu/GettingInvolved
[20:47] <wxl> you are from france, jean_ ?
[20:47] <jean_> wxl : oui
[20:47] <jean_> yes
[20:48] <wxl> jean_: we started a new "Global" team as part of our "Translations" team. if you can help with translations to french, that would be super cool. just one example!
[20:48] <wxl> we have other french speakers helping but the more we have the less work each person has to do
[20:48] <wxl> rafaellaguna is the head there. you might want to chat with him
[20:49] <jean_> ok, I'll try to help Lubuntu team as much as I could !
[20:49] <wxl> we'd love to have you jean!
[20:50] <wxl> if you have any questions about how to help, any ideas, anything, feel free to ask here or on the mailing list
[20:52] <wxl> and know jean_ you can always email me personally at<EMAIL_ADDRESS>or ping me here on irc. i'm always here, though sometimes i'm away from the keyboard. i'll pick up on msgs or hilights (say my nick) when i'm back
[20:54] <jean_> ok wxl, with pleasure !
[20:55] <jean_> I'll wait for rafaellaguna
[20:55] <wxl> jean_: i don't think he's in this channel. feel free to message him
[20:56] <jean_> wxl : is he on a different channel ?
[20:56] <wxl> jean_: yeah. i can invite you there


[12:03] <fij0> hello
[12:03] <fij0> there is a form to change the output power via ssh  ?
[14:23] <CIA-12> ubiquity: stgraber * r5507 ubiquity/ (bin/ubiquity-bluetooth-agent debian/changelog): Port ubiquity-bluetooth-agent to using the gi.repository version of gobject
[14:28] <CIA-12> ubiquity: stgraber * r5508 ubiquity/bin/ubiquity-bluetooth-agent: No need for the 'as gobject' part, just change the two calls to use GObject instead.
[14:35] <xnox> stgraber: looks good =) does this mean python-gobject has been dropped from the cd's now?
[14:35] <stgraber> xnox: I don't believe so, but that script was using #!/usr/bin/python3 and non-gi gobject doesn't exist for python3
[14:36] <xnox> stgraber: ok. Needs checking, cause dropping that can gain us space.
[14:36] <xnox> and spot what is missing from python3 port ;-)
[14:47] <cjwatson> xnox: http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.quantal/rdepends/ALL/python-gobject-2
[14:48] <xnox> cjwatson: =((((((
[23:36] <Chocky> hi kids.
[23:39] <Chocky> it's been a long time, I did work on boot-floppies back in the day and made custom Debian images about 4 years ago, and now I want to do the same.  That is, command-line configured Ubuntu install generator with a minimal selection of packages and my own stuff.  what's the best thing I should be using?
[23:43] <Chocky> might go debootstrap route.


[01:01] <smoser> mgagne, sorry. bzr
[01:01] <smoser> lp:cloud-init
[01:01] <mgagne> yea, I figured. thanks!
[01:24] <harlowja> mgagne  ya, were working on fixing that
[01:24] <harlowja> i mean smoser is gonna save us all
[01:40] <smoser> harlowja, right after you get the rhel networking sorted
[01:40] <smoser> :)
[01:40] <harlowja> lol
[01:40] <harlowja> oh ya, i'll try to do something there this week
[01:40] <smoser> :)
[01:40] <smoser> found / hit this today: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1571761
[01:40] <smoser> :-(
[01:40] <smoser> and with that  /me disapears
[01:40] <smoser> later gator.
[01:41] <harlowja> hmmmm, interesting, later
[07:57] <ReSam> good morning!
[07:57] <ReSam> I'
[07:58] <ReSam> I'm running MAAS and want to change my curtin_userdata preseed to install a few more things - but unfortunatley something always errors and then the exit code causes my deployment to fail
[07:58] <ReSam> what is the best way to "ignore the exit code" completely?
[07:59] <ReSam> I'm have lines like this in /etc/maas/preseeds/curtin_userdata:  puppet_02: curtin in-target -- sh -c 'dpkg -i /tmp/puppetlabs-release-pc1.deb'
[09:31] <Odd_Bloke> smoser: Is the expected behaviour of the 'fallback' networking to present network interfaces as eth{0,1,...} rather than the systemd names?
[09:36] <Odd_Bloke> rharper: ^
[09:36] <Odd_Bloke> If it isn't that's fine, I just got the impression that maybe that's what's meant to happen.
[09:36] <Odd_Bloke> And therefore want to know if I should be reporting if it isn't. :)
[09:44] <Odd_Bloke> (Oh, actually, maybe I'm being thrown off by a red herring: systemd leaves Hyper-V interfaces named eth* and I looked at Azure first; confirmation of the above would still be appreciated :)
[12:32] <rharper> Odd_Bloke: smoser  can confirm, but I don't think fallback does any renaming, so if you're booted without net.ifnames=0, and you have systemd, and fallback happens, you should see whatever systemd named the nic in the interfaces.d/50-cloud-init.cfg file
[12:33] <Odd_Bloke> OK, cool.
[12:34] <Odd_Bloke> smoser: rharper: So (assuming that to be true), do you have any suggestions for handling clouds that are sending network_config over in the meta_data.json, where content/0000 hard-codes eth0 as the expected network interface?
[12:34] <rharper> if
[12:34] <Odd_Bloke> (Other than going to the cloud and telling them to change what they're doing, of course ;)
[12:34] <Odd_Bloke> (Though we will try that)
[12:34] <rharper> if they are sending network_config via metadata service, we respect and use that
[12:34] <rharper> including naming
[12:35] <rharper> that's not fallback
[12:35] <rharper> we convert network_data.json into internal network_config.yaml which is then parsed and applied as if you had passed in a network_config.yaml in user-data
[12:35] <rharper> this is the configdrive stuff
[12:35] <Odd_Bloke> Yeah.
[12:35] <Odd_Bloke> Let me paste some things so we're on the same page.
[12:41] <Odd_Bloke> rharper: http://paste.ubuntu.com/15929016/
[12:41] <Odd_Bloke> So the cloud are just specifying an ENI file via meta_data.json and content/
[12:41] <Odd_Bloke> 0000
[12:41] <rharper> oh, this is network_config
[12:41] <rharper> unfortunate naming collision smoser and I discussed
[12:42] <rharper> Odd_Bloke: so, IIUC, cloud is providing an eni as-is;  however, it may not be aware of how nics will be named, right ?
[12:42] <Odd_Bloke> Right.
[12:42] <rharper> if they're sending ethX naming, and not also supplying an udev rule mapping file (70-persistent-net)
[12:42] <rharper> or network_config.yaml; then it's a bit of a shot in the dark
[12:43] <rharper> for Xenial (and wily), ensuring you boot with net.ifnames=0 will prevent nic naming to systemd style
[12:43] <rharper> which should match what they send; but the cloud itself should transition to using network_config.yaml
[12:44] <Odd_Bloke> rharper: Right; we're trying to get away from net.ifnames=0 as far as we can (because I suspect we will strongly regret having that delta in place for the next five years).
[12:44] <rharper> agreed
[12:44] <rharper> and the requirement is to specify what you want in network_config.yaml
[12:44] <rharper> alternatively, they can emit the ConfigDrive format that OpenStack uses
[12:44] <rharper> which cloud-init can convert to network_config.yaml
[12:45] <rharper> which emits the rules files needed to do name mapping
[12:45] <Odd_Bloke> rharper: Is there documentation that I can read/point them at?
[12:45] <rharper> y
[12:45] <rharper> one sec
[12:46] <rharper> https://blueprints.launchpad.net/nova/+spec/metadata-service-network-info
[12:46] <rharper> http://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/metadata-service-network-info.html
[12:48] <Odd_Bloke> rharper: So that's what they would put in /openstack/.../network_data.json, right?  How does network_config.yaml work?
[12:49] <rharper> it goes in the ConfigDrive at openstack/<date>/network_data.json
[12:49] <rharper> for network_config.yaml, lemme find the details
[12:51] <Odd_Bloke> rharper: Thanks. :)
[13:06] <smoser> Odd_Bloke, well, we need them to send the macs
[13:07] <smoser> and openstack does.
[13:13] <Odd_Bloke> smoser: From Liberty onward, right?
[13:14] <Odd_Bloke> (Can I tell what version of OpenStack I'm running on easily?)
[13:17] <smoser> the easiest way to do so is to look at the config drive.
[13:17] <smoser> or metadata service.
[13:17] <smoser> the version of the openstack isn't really exposed to the guest.
[13:18] <smoser> to further make it painful you actually have to have this fix applied to your liberty cloud : https://bugs.launchpad.net/nova/+bug/1513267
[13:18] <Odd_Bloke> So the most recent metadata version is 2013-10-17.
[13:20] <smoser> Odd_Bloke, https://github.com/openstack/nova/blob/master/nova/api/metadata/base.py#L72
[13:21] <smoser> so they're ssomewhere between Havana and Liberty (Icehouse, Juno, or Kilo)
[13:21] <Odd_Bloke> smoser: So one of Hava, Icehouse, Juno or Kilo?
[13:21] <Odd_Bloke> Hah.
[13:21] <smoser> its not unreasonabel to request the newer metadata really...
[13:22] <smoser> if they want to provide network data to the guest, then that is how it is done, and any thing previous is just kind of crap.
[13:22] <smoser> we could maybe support the path where they made a /etc/network/interfaces style file available to the guest
[13:27] <Odd_Bloke> smoser: Assuming they aren't able to do network_config.json, is there any good path forward that might mean we can get something working on GA day?
[13:27] <Odd_Bloke> (I'm assuming cloud-init changes are out of scope for Thursday :p)
[13:27] <smoser> well, ga is almost certainly no.
[13:27] <smoser> right.
[13:28] <smoser> this is dreamhost ?
[13:28] <Odd_Bloke> Yep.
[13:28] <Odd_Bloke> Only their new region though.
[13:28] <smoser> and each instance has static ip configuration expected ?
[13:28] <Odd_Bloke> Their old region has a DHCP server.
[13:28] <smoser> how did they think this is supposed to work?
[13:28] <smoser> ie, if its static config, how does the host tell the guest what config to use
[13:29] <Odd_Bloke> Did you see http://paste.ubuntu.com/15929016/ ?
[13:36] <smoser> no sorry
[13:37] <smoser> Odd_Bloke, ok. so yeah, thats the old way of declaring it and we could prbosbaly without too much effort make that work
[13:37] <smoser> but not without some chagnes to cloud-init
[13:37] <Odd_Bloke> smoser: No need to be sorry. :)
[13:38] <Odd_Bloke> smoser: What would you envision those changes being, roughly?
[13:39] <smoser> the config drive datasource would just have to look in that path for config information and the parse the ENI format
[13:39] <smoser> and then apply it as networking.
[13:39] <smoser> we do have an ENI parser in cloud-init
[13:39] <smoser> and then a writer. so the pieces are mostly there.
[13:40] <smoser> the hwaddress bit is actually *wrong* in openstack's use.
[13:40] <smoser> ie, they're saying "eth0 is the nic with this mac address"
[13:40] <Odd_Bloke> How would it infer that the config for eth0 should actually be applied to network_interfaces[0]?
[13:40] <smoser> when ifupdown says "i shoudl change the nic named eth0 to use this mac address"
[13:40] <smoser> how would it infer ?
[13:42] <Odd_Bloke> Ohhh, I'd missed that they specified the MAC address.
[13:44] <Odd_Bloke> So cloud-init would rename the NIC with the MAC address specified there to eth0 and then apply that ENI config in ENI.d/50-cloud-init.cfg (or whatever that file is called)?
[13:44] <smoser> yeah.


[14:24] <thinkjson> Anyone looking for a sysadmin job? http://www.lifechurch.tv/jobs/81-linux-systems-administrator
[14:24] <thinkjson> work from home, good pay, awesome team :-)
[14:29] <mhall119> hey there thinkjson
[14:34] <thinkjson> mhall119: hi!
[14:34] <mhall119> thinkjson: haven't seen you 'round here in a while, how's the new job going?
[14:34] <thinkjson> super awesome
[14:35] <thinkjson> I'm so busy they approved my proposal to hire my own staff. :-D
[14:35] <mhall119> nice
[14:35] <thinkjson> that particular position isn't one of them
[14:35] <thinkjson> I have a Node.js dev position opening up
[14:35] <mhall119> heh, that was my next question
[14:35] <thinkjson> and a little bit of freelance Pentaho work
[14:36] <mhall119> you still in tough with the Pentago guys?
[14:36] <mhall119> Pentago
[14:36] <mhall119> gah, twice
[14:36] <mhall119> Pentaho
[14:36] <mhall119> stupid fingers
[14:37] <mhall119> missed you at UDS/LoCo Party last month
[14:37] <thinkjson> yeah
[14:37] <thinkjson> been soooooo busy
[14:37] <thinkjson> things should free up after the first of the year
[14:37] <thinkjson> we're doing our big year-end push for Christmas
[14:37] <mhall119> I know, you think working from home would give you more time, right?
[14:37] <thinkjson> because lots of people buy smart phones for Christmas
[14:38] <thinkjson> haha. time.
[14:38] <thinkjson> I've tossed around the idea of hiring a PA
[14:38] <mhall119> how's the family? everyone doing well I hope
[14:38] <thinkjson> well
[14:38] <thinkjson> found out we're having a boy
[14:38] <mhall119> yay!
[14:38] <mhall119> nice balance
[14:39] <thinkjson> yeah
[14:39] <thinkjson> then we'll have a third child and throw it all off :-P
[14:39] <mhall119> heh, quit while you're ahead
[14:39] <thinkjson> lol
[14:39] <thinkjson> maybe we'll have 4 to balance it out again
[14:39] <mhall119> kids are algorithmic
[14:39] <thinkjson> we have 5 seats in the van, so that's the absolute maximum :-)
[14:39] <mhall119> two kids is 4x as hard as 1
[14:40] <thinkjson> O(n^2) ?
[14:40] <thinkjson> lol
[14:40] <mhall119> yup
[14:41] <mhall119> and they don't take kindly to optimization efforts either
[14:42] <mhall119> I think resource consumption is algorithmic too
[14:42] <mhall119> but maybe that just grows with age
[14:43] <mhall119> all I know is that 1 large pizza used to feed us all, but not anymore
[14:43] <thinkjson> mhall119: did you delete your twitter account?
[14:44] <mhall119> no
[14:44] <mhall119> just haven't used it much
[14:44] <thinkjson> you're completely missing now. what's your username?
[14:50] <mhall119> mhall119
[14:50] <mhall119> http://twitter.com/#!/mhall119
[14:59] <thinkjson> mhall119: https://twitter.com/#!/thinkjson/status/145155476911423489
[15:01] <mhall119> heh
[15:31] <zoopster> mhall119: funny comment about resource consumption...and it's not just food either!
[15:53] <thinkjson> well I'm off to save the world. ttyl.


[02:43] <ypwong> smartboyhw, ping
[02:43] <smartboyhw> ypwong, pong
[02:44] <ypwong> smartboyhw, out of curiosity, is there any freeze dates for points releases like 12.04.3/.4, similar to those freeze dates for regular releases, like 12.10/13.04
[02:44] <ypwong> ?
[02:44] <ypwong> coz I don't see them at https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule?action=show&redirect=PreciseReleaseSchedule
[02:45] <smartboyhw> ypwong, probably not.
[02:45] <ypwong> smartboyhw, ok, so just got what's available at the regular releases and then build?
[02:45] <smartboyhw> ypwong, ?
[02:46] <ypwong> 12.04.3 is just combination of what's available from 12.04 and 13.04 (kernel + xorg stacks)
[02:46] <smartboyhw> ypwong, technicallly
[02:47] <smartboyhw> Except a few flavours (Studio for example)
[02:47] <ypwong> smartboyhw, what's the difference?
[02:47] <smartboyhw> ypwong, for Ubuntu Studio, we are still using a 3.2 kernel (we might have such a new kernel for 12.04.4)
[02:48] <ypwong> smartboyhw, I see
[03:57] <FJKong> In file included from main.cpp:24:0:
[03:57] <FJKong> qmlaudio.h:19:18: fatal error: phonon: No such file or directory
[03:58] <FJKong> I have some trouble when make youker-assistant
[06:12] <maclin> smartboyhw,ping
[10:13] <smartboyhw> Damn, maclin left
[10:40] <ypwong> smartboyhw, what's up
[10:46] <smartboyhw> ypwong, he pinged me...
[10:48] <ypwong> smartboyhw, oh yes, about a very important thing
[10:48] <smartboyhw> ypwong, oh?
[10:48] <smartboyhw> How important?
[10:48] <ypwong> just kidding :)
[10:48] <smartboyhw> ypwong, LOL
[10:48] <ypwong> dunno why he pinged you
[10:49] <smartboyhw> OK...
[11:29] <smartboyhw> maclin, did you ping me?
[11:29] <smartboyhw> And obviously JackYu and maclin are at the same place:P
[11:30] <JackYu> yes, he is beside me:)
[11:32] <smartboyhw> JackYu, maclin plz make sure you do hide your IPs:P
[11:32] <ypwong> smartboyhw, they are actually the same person
[11:32] <ypwong> you found it
[11:32] <smartboyhw> ypwong, :O
[11:32] <smartboyhw> JackYu = maclin!!?!?!?!?!?!
[11:32] <JackYu> no...
[11:33] <smartboyhw> ypwong, good jk
[11:33] <maclin> smartboyhw, my network has some problem
[11:33] <smartboyhw> maclin, so you pinged me for network problems? :O
[11:33] <maclin> It is ok now
[11:34] <smartboyhw> maclin, ^
[11:34] <maclin> I have some questions about upgrade on QAtracker
[11:34] <smartboyhw> maclin, uh huh
[11:34] <smartboyhw> Do ask
[11:35] <maclin> What is the upgrade tests for?
[11:36] <smartboyhw> maclin, they are for upgrade from one release to another,
[11:36] <smartboyhw> For example, in your case, 13.04 -> 13.10
[11:36] <smartboyhw> Two methods:
[11:36] <smartboyhw> Image-based upgrade
[11:36] <smartboyhw> Or using the software updater
[11:37] <maclin> so we should do the tests on 13.04?
[11:38] <smartboyhw> maclin, yes
[11:38] <smartboyhw> In a 13.04 system, upgrade to 13.10
[11:48] <maclin> ok i got it. tks
[11:54] <maclin> smartboyhw, sorry that we have a meeting now and i am doing records, can we continue the discussion later or tomorrow?


[01:41] <mase_wk> hi guys, i need to add a module to the initramfs but i would like to make it so that whenever a new kernel is installed , when it runs update-initramfs it also adds in this module. Which file do i need to alter in order for this to occur ?
[01:41] <mase_wk> does it use /etc/modules.conf?
[01:41] <dtchen_> /etc/initramfs-tools/modules
[01:42] <mase_wk> thank you
[11:48] <_ruben> is it known/expected/whatever that hardy doesnt like newer kernels .. like 2.6.28 mainline builds, or backports from jaunty/karmic .. lvm fails to come up at boot .. it detects the disks, and then drops to shell
[13:33] <asabil> hi all
[21:18] <manjo_> dinh, u still around?
[21:27] <amitk> manjo_: he left


[06:40] <RAOF> ♪ You're one microscopic cog in his catastrophic plan / designed and directed by his red right hand ♫
[09:00] <mlankhorst> hey
[09:03] <RAOF> Ho!
[09:03] <RAOF> What can I do you for?+
[09:27] <makara> Hi. What's the story with adoption of Mir?
[09:27] <makara> will it be available in Ubuntu 14.04 desktop
[09:28] <RAOF> Depends on what you mean by “available”, really :)
[09:28] <RAOF> There's a unity8-desktop-session package available in trusty-proposed; I don't know if that's migrated yet, after beta freeze.
[09:41] <RAOF> And the Mir libraries are available, of course.
[10:58] <alan_g> alf_: are you happy with response on https://code.launchpad.net/~alan-griffiths/mir/add-some-intelligence-to-scheduling-compositing/+merge/208633?
[16:21] <kgunn> mterry: so we're talking about ripping out setting of MIR_SERVER_STANDALONE  currently in usc...within mir, this looks like it doesn't do squat (and is likely buggy)
[16:21] <kgunn> seems like an artifact....curious if you had an opinion
[16:22] <mterry> kgunn, no it is now an artifact I believe
[16:22] <kgunn> mterry: ok...its going bye bye
[16:23] <mterry> kgunn, as long as Mir keeps defaulting to nested when MIR_SOCKET is defined, we should be fine
[16:23] <kgunn> alan_g: ^ can you confirm the approach ?
[16:24] <alan_g> kgunn: I don't intend to change that.
[16:58] <evstevemd> any documetation on how to support mir to new toolkit (wxWidgets)
[17:03] <evstevemd> any documetation on how to support mir to new toolkit (wxWidgets)
[20:28] <Captain_Crow> does mir prevent apps from stealing the keyboard?
[21:05] <kdub> shells choice