[07:46] -ChanServ(ChanServ@services.)- [#ubuntu]  Welcome to #ubuntu! Please read the channel topic and consider spending some time on the FAQ mentioned there
[07:47] -ChanServ(ChanServ@services.)- You do not have channel operator access to [#ubuntu-freshers]
[02:14] -ChanServ(ChanServ@services.)- [#ubuntu-ops]  Welcome to #ubuntu-ops - Home of the operators for official K/X/Ed/Ubuntu channels. Questions, requests and complaints about Ubuntu related channels and their people can be filed here"
[02:14] -ChanServ(ChanServ@services.)- [#ubuntu]  Welcome to #ubuntu! Please read the channel topic and consider spending some time on the FAQ mentioned there
[02:14] -ChanServ(ChanServ@services.)- [#ubuntu-server]  Ubuntu Server Discussions (development and support)
[02:29] -RichiH(i=richih@freenode/staff/richih)- Hi all. As you surely noticed, we just had a largish split. A sponsor had a route flap which took a part of freenode from the net. Sorry for the inconvenience and thank you for flying freenode air!


[04:36] <thismamacooks200> fresh jaunty upgrade, cheese doesn't find my webcam, camorama doesn't find /dev/video0 (I have no /dev/vid* anything). lsbusb reports a "Bus 002 Device 002: ID 0545:800c Xirlink, Inc. Veo StingRay"
[15:05] <LaserJock> nubae: ping
[21:52] <zerothis> how often has this happened? <http://digg.com/linux_unix/Proprietary_Software_Can_Kill_You?FC=PRCK4>
[21:57] <Lns> zerothis: the more people depend on software, the more it will be in control (rather, the ones who create/distribute it)
[21:57] <Lns> so choose your license / vendor wisely.


[07:51] <Kaya> Hello, I'm quite new with ubuntu and I'm having some troubles with skype. And I'm not able to solve it myself. Is there someone who would like to help me?
[07:56] <Kaya> Till yesterday it was working fine. However, now it is not connecting anymore. Then I'm trying to solve it, but I cant find the error. All what has happend is that now even the program doesn't even start when I click on the button
[07:56] <Kaya> Till yesterday it was working fine. However, now it is not connecting anymore. Then I'm trying to solve it, but I cant find the error. All what has happend is that now even the program doesn't even start when I click on the button.
[18:13] <mahi_> How ca I delete Temp, Cookies and Prefetch?
[18:15] <mahi_> How can I delete Temp, Cookies and Prefetch? Sorry, miss-spelled 1st time....


[00:52] <LinuxGuy2009> What would be a proper response to a bug report that is questionable about if its an actual bug or an intentional program feature?
[00:53] <LinuxGuy2009> Just state that as a responce and just leave it?
[01:00] <LinuxGuy2009> Bug #579682 is questionable if its a feature request or if the 'bug' observed was actually an intentional programmed action. Other than stating that as the response I don't know what else to do with it. Otherwise the report is just gonna sit there probably with no solution.
[01:00] <ubot4> Launchpad bug 579682 in software-center (Ubuntu) "Ubuntu Software Center scrolls after package removal (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/579682
[01:11] <LinuxGuy2009> Ok maybe I wont help triage bugs.
[01:15] <mrand> LinuxGuy2009: sorry... this week is kinda bad...
[01:15] <mrand> a number of people are at UDS.
[01:16] <LinuxGuy2009> Oh I see. I understand
[09:04] <pedro_> folks, we're having the discussion of the Bugsquad Roadmap now at UDS in case you want to join us
[09:04] <pedro_> join #ubuntu-uds-jatoba for make comments
[09:06] <BUGabundo_remote> m@rnlng cowboys&girls
[09:06] <pedro_> vish, qense bugsquad roadmap session at jatoba
[09:07] <vish> pedro_: right now?
[09:07] <ddecator> vish: yup
[09:07]  * vish  in a theme session now  :(
[09:08] <qense> pedro_: I really wanted to attend, but I'm in the AppInd session now and I am necessary here.
[09:08] <qense> pedro_: sorry
[09:08] <qense> I will propose to get rid of the distinction between Adopt-a-Package and Adopt-an-Upstream and integrate the efforts during the AdoptUpstream session that has yet to be scheduled.
[09:09] <pedro_> qense, ok. I've talked to marjo about it in the roundtable it will be scheduled
[09:10] <qense> pedro_: What will be?
[09:14] <pedro_> qense, adopt an upstream, i'll let you know as soon as i see it scheduled
[09:16] <qense> pedro_: Thanks
[09:57] <ddecator> For anyone interested, there will be a meeting about BugSquad Mentorship at 1300 UTC in one of the UDS channels (room unknown at this time)
[10:09] <pedro_> Folks, the Mentoring Program Review session is at 1500 at the Ginko room
[10:09] <pedro_> http://summit.ubuntu.com/uds-m/2010-05-13/
[10:09] <ddecator> pedro_: ha, i was just going to put that up
[10:09] <pedro_> hggdh, the session was scheduled for 1500  at the Ginko room
[10:09] <hggdh> pedro_: thank you
[10:10] <ddecator> pedro_: i'll be there (even though it's at the same time as the discussion for default applications in maverick =\)
[10:11] <ddecator> BTW, 1500 is CEST, so 1300 UTC is the time of the meeting
[10:13] <bdmurray> pedro_: updated bugsquad roadmap gobby document
[10:14] <pedro_> bdmurray, you rock!
[10:15] <ddecator> thanks bdmurray for adding that stuff
[11:03] <Tyriel> Hi, to whom may I report the bugs?
[11:03] <BUGabundo_remote> Tyriel: usually to a bug tracker
[11:03] <BUGabundo_remote> in our case, launchpad
[11:04] <BUGabundo_remote> !lanchpad > Tyriel
[11:04] <ubot4> Factoid 'lanchpad' not found
[11:04] <yofel> !bugs
[11:04] <ubot4> If you find a bug in Ubuntu or any of its derivatives, please file a bug using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs - Bugs in/wishes for the IRC bots (not Ubuntu) can be filed at http://bugs.launchpad.net/ubuntu-bots
[11:04] <BUGabundo_remote> !launchpad > Tyriel
[11:04] <ubot4> Tyriel, please see my private message
[11:04] <BUGabundo_remote> yofel: that one was next!!!
[11:04] <BUGabundo_remote> :)
[11:04] <yofel> heh
[11:04] <yofel> Tyriel: what's the problem?
[11:04] <Tyriel> The Calendar has 8 days per week
[11:04] <Tyriel> hahahahaha
[11:04] <Tyriel> this is really something serious
[11:05] <Tyriel> lol
[11:05] <yofel> wth?
[11:05] <BUGabundo_remote> LOL
[11:05] <yofel> Tyriel: which calender? (which application?)
[11:05] <BUGabundo_remote> what he said
[11:05] <Tyriel> The calendar if you click on the icon to check the calendar on the desktop you will see it 8 days weeek
[11:07] <Tyriel> At least here on my version 10.04LTS is like this
[11:07] <yofel> Tyriel: using gnome?
[11:07] <Tyriel> I don know others, if you guys want I can send an ss
[11:07] <Tyriel> yes gnome
[11:07] <yofel> BUGabundo_remote: can you reproduce that?
[11:07] <yofel> Tyriel: sure (especially as I don't use gnome myself)
[11:08] <Tyriel> did you receive the dcc?
[11:08] <yofel> Tyriel: I'm using quassel which doesn't support dcc, please use imagebin.ca
[11:08] <Tyriel> ok

[11:10] <Tyriel> There is also another bug fort the wireless tool, sometimes when i restart the icon disappear
[11:10] <yofel> Tyriel: I only see 7 days there
[11:10] <yofel> Sun - Sat
[11:11] <Tyriel> You see the days 17, 18, 19, 20, 21, 22 are off the week days
[11:11] <Tyriel> so it causes a wrong
[11:11] <yofel> yes, as that's the, '17th... week this year'
[11:11] <Tyriel> haaaaaaaaaa
[11:11] <Tyriel> lol
[11:11] <Tyriel> i'm nooober
[11:11] <Tyriel> :D
[11:11] <yofel> so no bug ;)
[11:11] <Tyriel> tks god :P
[11:12] <Tyriel> but still the wireless thingi s a pitty
[11:12] <Tyriel> haha
[11:12] <Tyriel> another question, Do you have any knowledge of when the Ubuntu One contacts will start working again? I have some many contacts there...
[11:13] <yofel> I'm not sure where the NM icon belongs to, either network-manager-gnome or some indicator package
[11:13] <Tyriel> is the network-manager-gnome
[11:13] <yofel> Tyriel: #ubuntuone might be able to help you more then
[11:13] <BUGabundo_remote> yofel: Tyriel: looks fine for me in maverick
[11:14] <yofel> BUGabundo_remote: he mistook the week numbers for another weekday :P
[11:14] <Tyriel> yes i'm sorry
[11:14] <Tyriel> it was the weeks of the year
[11:14] <Tyriel> i though it was days
[11:14] <Tyriel> :P
[11:14] <BUGabundo_remote> I saw
[13:17] <b_> hello
[13:17] <b_> my ubuntu is starting many times with no image on display
[13:18] <b_> i have a intel video card on a laptop and a 10.4 version of ubuntu
[13:19] <b_> anybody some help please
[13:20] <astraljava> b_: #ubuntu is the official support channel, this is for bug triaging and other bug work.
[13:21] <b_> where should i ask for help ?
[13:22] <astraljava> b_: On IRC, /join #ubuntu, then there are ubuntuforums.org, and you can also browse already reported bugs on https://launchpad.net
[13:22] <astraljava> b_: Try also<EMAIL_ADDRESS>[13:23] <b_> thank you
[13:23] <astraljava> b_: No problem, happy to help. :)
[13:57] <ddecator> For those interested, the BugSquad Mentoring Program Review UDS session will be starting in 5-10 minutes in #ubuntu-uds-ginko
[14:10] <pedro_> guys we're having the mentoring program discussion at #ubuntu-uds-ginko
[14:10] <pedro_> in case you want to join us
[14:31] <optix> I believe bug #578834 should be updated to wishlist, can someone here agree and change it?
[14:31] <ubot4> Launchpad bug 578834 in language-selector (Ubuntu) "Sort languages by display name, not locale code (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/578834
[15:49] <LinuxGuy2009> When a launchpad bug is looked at and I ask for more info or for the reporter to post back to answer a question or whatever, is it proper to set the status to incomplete? Then after the 60 days expire without a response, then it would be considered invalid? This correct? I'm trying to learn proper procedure.
[15:55] <ddecator> set to incomplete yet. then we usually send them a comment if they don't respond in 4 weeks. if no response for two more weeks then it's invalid
[15:55] <ddecator> https://wiki.ubuntu.com/Bugs/Responses#Incomplete%20bugs%20without%20a%20response%20from%20submitter
[16:08] <LinuxGuy2009> cool
[16:09] <ddecator> s/yet/yes
[16:14] <LinuxGuy2009> https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/579682 This appears to be an intentional programmed occurance and is basically agreed upon by myself and another person there. Would it be proper to set it to invalid yet or let it sit for a while?
[16:14] <ubot4> Launchpad bug 579682 in software-center (Ubuntu) "Ubuntu Software Center scrolls after package removal (affects: 1) (heat: 6)" [Undecided,New]
[16:16] <LinuxGuy2009> Seems more a wishlist type of thing than a bug.
[16:16] <ddecator> oh i've had it do that...it's annoying, haha
[16:17] <ddecator> if you're unsure whether it's supposed to do that, it'd be good to contact one of the developers to see what the intended behavior is
[18:26] <mrand> optix: done
[18:38] <optix> mrand: thank you
[19:33] <resno> ive got a bug i would to report. but im i dont think i can repeat it with a level of certainty.
[19:33] <resno> i would like*
[19:43] <astraljava> resno: Which distribution?
[19:44] <resno> astraljava: ubuntu server and ubuntu desktop 9.10 and also 10.04
[19:44] <astraljava> resno: Okay, can't help you there, don't have either of those.
[19:45] <resno> astraljava: its the same machine, that has had a recurring problem
[19:45] <resno> kacpi-notify runs up to 100% if i do something thats heavy
[19:46] <astraljava> resno: If you don't get attention here, I suggest you post steps to reproduce somewhere, like ubuntuforums.org or<EMAIL_ADDRESS>and wait for confirmation from other users. Then you can decide whether to file a bug or not.
[19:47] <resno> ok, i wont worry about it then.
[19:48] <astraljava> resno: Does that happen often, or repeatedly?
[19:50] <resno> astraljava: only when im doing something heavy... not often anymore. its my server at the moment. if i pull up webmin, it will happen.
[19:50] <resno> but when i used it as a desktop, it happended more then it should
[19:58] <resno> at that time, i didnt know anything about submitting bugs
[19:59] <astraljava> resno: There are a couple of similar bugs filed in LP, but they don't really show any foolproof solutions. I don't know how to help you, sorry. Hope you get someone assisting you in this problem.
[20:00] <resno> astraljava: thanks for your assitance
[20:01] <jf1976> is there anyway i can help with rtl development as a non coder ?
[20:15] <psusi> how do you file a bug report to request a merge from upstream again?
[20:31] <mrand> psusi: https://wiki.ubuntu.com/SyncRequestProcess In short, if the package isn't automatically synced, you can create a launchpad ticket for that package and subscribe ubuntu-sponsors. Example preferred title format (i.e., include the upstream version number): Sync xmltv 0.5.56+cvs20100328-1 (universe) from Debian testing (main)
[20:31] <psusi> ahh there we go...
[20:31] <micahg> mrand: psusi: it's preferable to use the requestsync tool
[20:32] <psusi> I'm actually trying to convert an existing bug to the proper format
[20:32] <micahg> psusi: ah
[20:33] <psusi> also it seems that debian unstable still hasn't updated to the latest upstream version from a few weeks ago either, which fixes a bug in the version currently in testing that this bug has requested we update to for the new lvm --merge feature
[20:34] <psusi> ohh wait, that's a sync.. we have ubuntu changes that need merged
[20:34] <mrand> psusi: if the debian package is actively maintained, I'd push for them to update first.  Keep diff's as small as possible.
[20:35] <psusi> true
[20:44] <David-T><PHONE_NUMBER>55555555555555555555555555555555]]]]]
[20:45] <David-T> er, oops
[22:33] <trinikrono> hey any mentors
[22:34] <trinikrono> if a guy has a bug 379723, and a packages has the wrong version in the universe, how do we get it updated to the new one, a request to package?
[22:34] <ubot4> Launchpad bug 379723 in partitionmanager (Ubuntu Jaunty) (and 1 other project) "partitionmanager 1.0.0~beta1a doesn't work (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/379723
[22:39] <astraljava> trinikrono: Like Colin said in the bug comments, it requires an SRU. File such a bug, and if you can prepare the package for such an update. If not, try to get someone else doing it.
[22:43] <trinikrono> so what should we do with the bug to make it happen?
[22:47] <astraljava> trinikrono: Read up here: https://wiki.ubuntu.com/StableReleaseUpdates
[22:49] <trinikrono> wow, i think i will go work on another package lol
[22:50] <thekorn> trinikrono, do you know which version of the package fixes this bug?
[22:52] <trinikrono> well its beta1 in the repo, but from beta apparently works for the guy
[22:53] <trinikrono> the newer ubuntu releases use the stable versions
[22:54] <thekorn> IMHO, this bug is not worth the hard work of a SRU
[22:55] <trinikrono> yea i thought so
[22:55] <trinikrono> :\
[22:56] <trinikrono> okie next one, Bug #579703   what do i need to do again to get this triaged
[22:56] <ubot4> Launchpad bug 579703 in gparted (Ubuntu) "gparted wrongly reports partition "mounted" when uuid and label are duplicates (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/579703
[23:03] <thekorn> trinikrono, how can a uuid of two partitions be the same?
[23:10] <trinikrono> well thats why i want some ideas as what to ask the reporter


[17:56] <hank__> just loaded 15.04 having a great time
[17:56] <holstein> cheers
[17:57] <hank__> trying to get TV tuner to work.  Already rebuilt whole media.  Keep working on it
[17:58] <holstein> yup.. if they (they = the creators of the hardware) dont support linux, it can be challenging
[17:58] <holstein> you can go upstream for support, to #ubuntu or one of the communities that use capture cards like that
[17:58] <holstein> !mythbuntu
[17:59] <holstein> you can look for, and purchase hardware with linux support in mind
[17:59] <holstein> otherwise, i say, grab different live iso's and see how things are supported. note kernel versions and drivers..
[17:59] <hank__> have Happhaghue dongle supposed to work,  wiki has bunch mumbo-jumbo.  I'll get it . Gotta compile,  arggggg.  gotta go I'm joined.  cheers
[18:00] <holstein> "supposed to" is the issue
[18:00] <holstein> if "they" dont promise linux support.. just keep in mind, nothing about linux/ubuntu is preventing it from working
[18:00] <holstein> we *want* it to work for you :)
[18:01] <hank__> uh-huh!  Their site has some linux help.  the 'ol wiki.  I'll get it.   Later
[18:01] <holstein> hank__: sure. let them know if its not working for you
[18:02] <holstein> if "some linux help" on the "ol wiki" ='d "official linux support for that particular device, hank would be in business :)
[21:56] <redac38> hello


[00:47] <josharenson> If you have a snap installed from the stable channel, is there an easy way to get a newer channel without uninstalling/reinstalling?
[00:48] <nacc> josharenson: snap refresh foo --<channel>
[00:48] <nacc> josharenson: i think?
[00:49] <nacc> josharenson: i mean, that will change what is installed, of course, not sure how you expect to avoid that?
[00:49] <josharenson> nacc: its downloading... thanks
[00:49] <nacc> josharenson: unless you just meant the two steps :)
[00:49] <josharenson> nacc: yeah this is what I was looking for
[00:51] <nacc> josharenson: great!
[01:32] <sergiusens> jdstrand are you using master?
[02:16] <mup> PR snapcraft#895 closed: Release changelog for 2.22 <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/895>
[08:00] <foxmask> bonjello
[08:11] <dholbach> hey hey
[08:25] <didrocks> good morning dholbach!
[08:41] <abeato> $ sudo snap connect modem-manager:mmcli modem-manager:service
[08:41] <abeato> error: cannot perform the following tasks:
[08:41] <abeato> - Connect modem-manager:mmcli to modem-manager:service (connection denied by slot rule of interface "modem-manager")
[08:42] <abeato> morphis_, zyga any idea on why this might be happening? ^^
[08:42] <morphis_> abeato: did you sideload a modem-manager snap?
[08:42] <abeato> moyes
[08:43] <abeato> morphis_, yes
[08:43] <morphis_> then I guess the base_declaration.go denies slot connection for unasserted snaps :-)
[08:43] <morphis_> which doesn't sound right to me
[08:43] <abeato> hmpf
[08:44] <morphis_> abeato: need to check with jdstrand what the rational behind this is
[08:44] <abeato> morphis_, agreed, will try to reach him later
[08:44] <morphis_> thanks
[08:46] <dholbach> salut didrocks
[08:48] <tsdgeos> is there a way to tell snapcraft "reload the .deb files that may be old since the last run"?
[08:49] <tsdgeos> or do i need to clean and run it again?
[08:52] <didrocks> tsdgeos: you can clean a part if needed
[08:53] <didrocks> to not clea all parts of your builds
[08:56] <tsdgeos>  that doesn't help much
[08:56] <tsdgeos> since all the debs are in the same part
[08:56] <tsdgeos> given the big amount of debs in the unity8 snap
[08:56] <didrocks> tsdgeos: not other way AFAIK than redownloading all of them
[08:57] <tsdgeos> would be good not having to refetch several MB of data just because 1 .deb changed
[08:57] <didrocks> please open a bug for this
[08:57] <tsdgeos> otoh not sure if we can actaully know only 1 deb changed
[08:57] <tsdgeos> i guess we can (since apt-get update knows)
[08:57] <didrocks> could, from the checksum
[08:57] <didrocks> or if we don't want to compute them, opening the ar, there is a checksum inside
[08:58] <didrocks> tsdgeos: please refer here the opened bug
[08:58] <tsdgeos> sure
[09:07] <tsdgeos> didrocks: https://bugs.launchpad.net/snapcraft/+bug/1640721
[09:07] <mup> Bug #1640721: Feature Request: Would be nice to have a way to refresh .deb files <Snapcraft:New> <https://launchpad.net/bugs/1640721>
[09:07] <tsdgeos> not sure i worded it correctly
[09:17] <didrocks> tsdgeos: just added a small precision, but yeah, looks good!
[10:16] <ppisati> ogra_: i suspect you have a white list of modules that end up in the pc-kernel snap
[10:17] <ppisati> ogra_: e.g. initramfs-tools-ubuntu-core
[10:17] <ppisati> ogra_: that's where you select which kernel modules endup in the pc-kernel snap initrd
[11:02] <didrocks> Mirv: I'm unsure to understand your PR
[11:02] <didrocks> Mirv: I guess you didn't push the second commit with the override, correct?
[11:02] <Mirv> didrocks: sorry, I was just thinking I might have explained it better. so the platform qt5 sets QTCOMPOSE, but if the "general" QTCOMPOSE is set after that block the platform qt5 setting is never taking effect
[11:03] <didrocks> oh, you already overrde it
[11:03] <didrocks> let me check :)
[11:03] <Mirv> yes, but currently the override is before it's generally set, so the override never works
[11:03] <didrocks> ah indeed :)
[11:04] <didrocks> what is QTCOMPOSE for btw?
[11:04] <didrocks> looking for locales? but the name doesn't help…
[11:04] <didrocks> (I guess it's for input keyboards…)
[11:04] <didrocks> (merged)
[11:07] <Mirv> yeah the location of compose.dir
[11:09] <didrocks> good, thanks!
[11:18] <ogra_> ppisati, yup
[11:19] <ogra_> ppisati, that is what we use today, correct ... i need a way to have a modules file per arch though, i dont want all the VM drivers in arm kernels for example
[12:34] <tsdgeos> what was the command to get a shell inside the snap ?
[12:34] <ogra_> snap run --shell $yourcommand
[12:36] <tsdgeos> tx
[13:02] <Elleo> jdstrand: ping?
[13:04] <renato__> Mirv, hey, just tested the platform plugin from here: https://code.launchpad.net/~timo-jyrinki/+snap/ubuntu-app-platform/, but the app still not starting on unity8
[13:04] <renato__> Mirv, if I add the "mir-graphics-drivers-desktop" it works. Probably some files still missing
[13:06] <Mirv> renato__: or environment variable ;)
[13:07] <Mirv> renato__: weird though, since you only added that same package that's being staged
[13:07] <renato__> Mirv, no, I am not using any wrapper
[13:07] <renato__> Mirv, could be some dir that you are not exporting?
[13:07] <Mirv> renato__: yeah I just started looking at that actually, the same thing occurred to me
[13:08] <renato__> Mirv, nice, let me know if you fix it.
[13:09] <popey> jdstrand: http://people.canonical.com/~alan/wine/32bitbuild/wine_1.6-git_amd64.snap - 32 bit build for you
[13:19] <Mirv> renato__: not finding anything not exported in the new packages which were libmirplatform13 mir-client-platform-mesa5 mir-platform-graphics-mesa-x10 mir-platform-graphics-mesa-kms10 mir-graphics-drivers-desktop
[13:19] <Mirv> renato__: so it might be something that was already installed by previous staged packages, but not exported, which was not needed until now... or something completely different
[13:20] <davmor2> pitti, mwhudson: In console conf, if you have ethernet and wifi you see options to configure the wifi but also on the main page there is what looks to be some global set ipv4/ipv6.  Are they actually global or are they only controlling ethernet?
[13:21] <renato__> Mirv, cLet me try to make a list of all files intalled with my package
[13:27] <Mirv> renato__: I'll make list of files that are staged by the platform snap but not exported
[13:28] <renato__> Mirv, i will do a diff btw the version with ""mir-graphics-drivers-desktop"" and without it
[13:30] <Mirv> doh, what's up with pastebin.ubuntu.com
[13:31] <Mirv> renato__: ok here goes, I don't find anything suspicious "mir" http://pastebin.com/vfi0vPGf
[13:32] <Mirv> also directly rm -rf :d usr/share/doc and usr/share/man from the list, in addition to move /lib, /lib64 and /usr/include to that canbeprobablysafelyignored
[13:35] <Mirv> renato__: logically thinking if mir-graphics-driver-desktop was the only thing you have in staged-packages now, and I added it in platform snap, and it works with your included-in-app but not with included-in-platform, the missing file(s) should be in that pastebin.com output, am I thinking correctly?
[13:35] <Mirv> there's surely bunch of /usr/bin that's not being exported, but nothing obvious
[13:36] <renato__> Mirv, I am getting the diff now
[13:40] <renato__> Mirv, page 2: https://docs.google.com/spreadsheets/d/1IKlbILX1S-k2w2Pba5-ZlBoYsBVcOIglmAEUjv8uOcY/edit#gid=144700900
[13:43] <renato__> Mirv, is "$plataform/usr/lib/x86_64-linux-gnu/mir/" part of LD_LIBRARY_PATH?
[13:43] <renato__> Mirv, and usr/lib/x86_64-linux-gnu/mir/client-platform
[13:49] <Mirv> renato__: yeah, so missing env var indeed (you said "no, I am not using any wrapper" so I wasn't sure if you meant it can't be any env var), that's probably it. adding.
[13:49] <renato__> Mirv, did you confirm that? Is the missing var?
[13:49] <Mirv> renato__: well it's not set, I'm not sure if it's something that helps
[13:50] <jdstrand> sergiusens: re master> no. I was using 2.21 with https://github.com/snapcore/snapcraft/pull/876/files
[13:50] <mup> PR snapcraft#876: repo: allow for architecture-specific stage-packages <Created by stgraber> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/876>
[13:50] <jdstrand> popey: thanks!
[13:50] <Mirv> renato__: you could try it in your local snapcraft-desktop-helpers first of course
[13:50] <jdstrand> Elleo: hey
[13:50] <renato__> Mirv, ok let me try first I am not sure if it is necessary
[13:51] <renato__> Mirv, are you able to check if that is exported for QT5 or gtk launcher?
[13:52] <Mirv> renato__: it's not, but I'm wondering if Mir could confused that it's not under the standard path /usr/lib/.../mir but /ubuntu-app-platform/usr/lib/.../mir
[13:52] <Mirv> renato__: oh, actually now I found it!
[13:52] <Mirv> renato__: export MIR_CLIENT_PLATFORM_PATH=$SNAP/usr/lib/$ARCH/mir/client-platform in desktop-exports, not launcher-specific
[13:53] <Mirv> so we need to override that common env
[13:53] <renato__> Mirv, let me try
[13:53] <Mirv> renato__: http://pastebin.com/mZNLx7j8 - the diff
[13:53] <jdstrand> popey: fyi:
[13:53] <jdstrand> $ /snap/bin/wine notepad.exe
[13:53] <jdstrand> /snap/wine/x1/wine: 15: /snap/wine/x1/wine: /snap/wine/x1/bin/wine64: not found
[13:53] <Mirv> renato__: if you're on up-to-date snapcraft-desktop-helpers locally
[13:57] <Elleo> jdstrand: heya, got a couple of questions about app armor rules for snaps; is there any equivalent of @{APP_PKGNAME}? At the moment I'm faking it with "snap.@{SNAP_NAME}.@{SNAP_NAME}", but I'm not sure if that covers all cases correctly? and what about @{APP_ID_DBUS}? I saw in the old click stuff it uses libnih-dbus to get a dbus friendly name, but I couldn't find anything similar in snapd?
[13:58] <Elleo> jdstrand: I had wondered whether I should write a bit of go code in my interface to make a dbus friendly ID instead?
[13:58] <Elleo> jdstrand: like some of the ###TEMPLATE### style replace stuff done in other interfaces
[13:59] <popey> jdstrand: balls
[13:59] <popey> jdstrand: ok, will rebuild and actually test it this time
[13:59] <popey> sorry
[14:01] <jdstrand> Elleo: all of the variables are in interfaces/apparmor/template_vars.go
[14:02] <jdstrand> Elleo: snap.@{SNAP_NAME}.@{SNAP_NAME} is only going to sometimes be correct
[14:03] <renato__> Mirv, did not solve the problem, let me try more Vars
[14:04] <Elleo> jdstrand: okay, neither of those are in template_vars.go, so what would be the correct way of forming an equivelant of APP_PKGNAME and should I rewrite it to be dbus friendly in my interface or add something to snapd to make it available for all snaps?
[14:04] <jdstrand> Elleo: but snippets has different ways of creating the label. eg, plugAppLabelExpr(plug) and slotAppLabelExpr(slot)
[14:05] <jdstrand> Elleo: see for example udisks2.go and how it expands ###PLUG_SECURITY_TAGS###
[14:07] <jdstrand> popey: np. I'm not blocked on it atm since I have a simpler reproducer, but would like to test with wine before claiming to have fixed it
[14:07] <jdstrand> popey: and yes, I think I will be able to make this work
[14:08] <Elleo> jdstrand: ah, okay, looks like I can use that for the replacement of APP_PKGNAME and then I guess just write some go code to do what libnih-dbus does to make it dbus friendly for APP_ID_DBUS then?
[14:08] <popey> jdstrand: that's awesome news, thanks.
[14:08] <jdstrand> Elleo: there is already go code for that
[14:08] <Elleo> jdstrand: oh?
[14:08] <jdstrand> Elleo: that is what plugAppLabelExpr and slotAppLabelExpr do
[14:09] <jdstrand> Elleo: they expand out the plugged commands into what you need. just copy the udisks2.go methodology and you'll get what you need
[14:10] <Elleo> jdstrand: okay, thanks :)
[14:10] <jdstrand> Elleo: (notice that ###PLUG_SECURITY_TAGS### in udisks2ConnectedSlotAppArmor expands to dbus labels)
[14:12] <jdstrand> Elleo: it works pretty neat because it will expand to snap.<snap>.* if using a toplevel plugs, snap.<snap>.<command> if only one command is connected or 'snap.<snap>.<command1>,snap.<snap>.<command2>,snap.<snap>.<commandN>' if multiple commands are connected
[14:13] <jdstrand> Elleo: so all you need to worry about is peer=(label=###PLUG_SECURITY_TAGS###)
[14:14] <Elleo> jdstrand: okay, separate but related questions; where should I be allowing download manager and the apps to write data? currently it's: @{HOME}/.local/share/ubuntu-download-manager/@{APP_PKGNAME}/ (which is where the non-dbus version of PKGNAME was being used), should we be shifting that somewhere else for snaps? and should it be on a per snap basis or a per command basis (I'd guess per snap so all commands within a snap can access downloads from other
[14:14] <jdstrand> Elleo: (note, you use ###PLUG_SECURITY_TAGS### on the slot side policy and ###SLOT_SECURITY_TAGS### on the plug side policy (they are opposite since you are specifying the peer)
[14:15] <jdstrand> Elleo: per snap. a tenant of snappy is that all commands can access each other's data
[14:16] <jdstrand> Elleo: @{HOME}/.local/share/ubuntu-download-manager/ is trickier cause there are a couple of things to keep in mind
[14:18] <renato__> Mirv, I can not find the problem :(. Do you know some Mir guy that could help us?
[14:18] <jdstrand> Elleo: the @{HOME} apparmor variable (be default) expands to '/root/' and /home/*/'. the $HOME *environment* variable is set to $HOME/snap/$SNAP_NAME/$SNAP_REVISION
[14:18] <renato__> Mirv, at least get more info about the problem
[14:18] <jdstrand> s/be default/by default/
[14:19] <jdstrand> Elleo: and the template policy allows writes to @{HOME}snap/$SNAP_NAME/$SNAP_REVISION/**
[14:19] <Mirv> renato__: I think they are all more in your time zone, maybe ask Kevin to give a person to give ideas.
[14:19] <Mirv> renato__: I can't also find any further variables to set at this point that could have an effect
[14:19] <jdstrand> Elleo: so from a snap's perspective, you don't have to do anything if udm puts stuff in $HOME/snap/$SNAP_NAME/$SNAP_REVISION/.local/share/ubuntu-download-manager/
[14:20] <renato__> Mirv, do you have a small app that they could easily test?
[14:21] <jdstrand> Elleo: (note there is also $SNAP_USER_COMMON env variable, which is set to $HOME/snap/$SNAP_NAME/common
[14:21] <jdstrand> )
[14:21] <Elleo> jdstrand: is there a way in which the UDM service can find out the SNAP_REVISION of what it's talking to? or can I have it write to $HOME/snap/$SNAP_NAME/$SNAP_REVISION/current/<blah>?
[14:22] <Elleo> jdstrand: ah, thought there was a current symlink there, but seems thats only for snap packages in /snap/ not user directories
[14:22] <jdstrand> Elleo: so you have a choice-- you can adjust udm to figure out where to put the downloads or you can store them where you do now and make your clients figure out where it is (which is tricky cause they don't know the user's home)
[14:22] <renato__> Mirv, this is printing on unity8 log while trying to run the app: http://paste.ubuntu.com/23456384/
[14:22] <renato__> Mirv, check if you see anything that could cause the problem
[14:23] <jdstrand> Elleo: SNAP_USER_DATA doesn't have the current symlink
[14:23] <jdstrand> Elleo: but this is data that really isn't revision specific, I suspect SNAP_USER_COMMON is a better fit (and easier to implement for you)
[14:23] <Elleo> jdstrand: udm sends the path to the client as part of the finished signal, can that be used unmodified if the interface provides access to the current location? then the apps don't need to do any work to find it
[14:25] <jdstrand> Elleo: yes, that is possible from a policy perspective. it is a bit weird with the way snap data dirs are setup though. to me SNAP_USER_COMMON seems the way to go unless there is a compelling reason not to (this will come up in the PR review as well)
[14:26] <Elleo> jdstrand: for udm to work in a snap it'll need write access to all other snap's common areas though; with the current mechanism it just has access to $HOME/.local/share/ubuntu-download-manager/** and apps get .local/share/ubuntu-download-manager/snap.@{SNAP_NAME}/ or similar
[14:26] <Elleo> jdstrand: which would seem to keep things much more isolated
[14:27] <jdstrand> Elleo: click had a different way of doing things-- it had data sprinkled throughout the HOME dir by having data in xdg data dirs. snappy consolidates when application data is and sets HOME for the snap so it can put it wherever. ngoi
[14:28] <Elleo> jdstrand: is there a way I can find out SNAP_USER_COMMON's value for a snap I'm communicating with over dbus?
[14:28] <jdstrand> Elleo: udm is a trusted slot though-- its the connecting snaps that are untrusted. you can still limit it to<EMAIL_ADDRESS>rwk,'
[14:29] <jdstrand> (or something-- point is, limited within the snap's dir)
[14:30] <Elleo> jdstrand: okay, when udm decides where to write if I can't get the actual SNAP_USER_COMMON can I assume that<EMAIL_ADDRESS>will be correct?
[14:30] <jdstrand> Elleo: you can use libapparmor to figure out the connecting process' security label and then derive the $SNAP_NAME from that
[14:30] <Elleo> jdstrand: okay, so SNAP_USER_COMMON will always be of that form then?
[14:31] <jdstrand> Elleo: you can assume @{HOME}/snap/@{SNAP_NAME}/common/ is correct for series 16, yes. I doubt it will change for series 18, but it is conceivable
[14:31] <jdstrand> Elleo: yes
[14:31] <Elleo> jdstrand: okay, cool; thanks :)
[14:31] <Elleo> jdstrand: will see about making those changes now, I expect I'll be back with more questions soon :P
[14:31] <jdstrand> ok
[14:39] <Mirv> renato__: please try / give them https://code.launchpad.net/~timo-jyrinki/+snap/uitk-gallery/+build/9673/+files/uitk-gallery_0.1_amd64.snap - anyway, I'm EOD now but just managed to create that snap
[14:40] <Mirv> not tested under U8, starts under U7
[14:40] <renato__> Mirv, yes my app starts on u7 too
[14:40] <renato__> Mirv, the problem is only on unit8
[14:43] <Mirv> renato__: yeah, I just mean that there's nothing fundamentally wrong with that snap (that I just created on LP for the first time), so it should be good for testing
[14:43] <Mirv> uses the platform snap
[14:44] <mup> PR snapcraft#896 opened: indicators: work with Content-Encoding set <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/896>
[14:59] <renato__> Mirv, did you push the changes on the launcher? With the MIR client evn var?
[15:20] <mup> PR snapcraft#897 opened: Don't organize in the install dir <Created by josepht> <https://github.com/snapcore/snapcraft/pull/897>
[15:23] <mup> PR snapcraft#856 closed: Call organize() after building <Created by josepht> <Closed by josepht> <https://github.com/snapcore/snapcraft/pull/856>
[15:35] <kalikiana_> jdstrand: Would you have another look at https://github.com/snapcore/snapd/pull/2225 ?
[15:35] <mup> PR snapd#2225: Implement lxd-client interface exposing the lxd snap <Created by kalikiana> <https://github.com/snapcore/snapd/pull/2225>
[15:44] <jdstrand> kalikiana_: yes
[15:52] <kalikiana_> Thanks
[15:54] <lewciie> hi there! trying to register a snap and getting registration failed but no reason is given
[15:55] <didrocks> hey lewciie! What's your specific error message output?
[15:55] <lewciie> 'Registration failed.'
[15:56] <didrocks> hum, nothing more with --debug?
[15:56] <lewciie> let me check
[15:56] <didrocks> (just if it gets you more info by any chance)
[15:57] <didrocks> also, have you tried with a different name? (the one you are using may be taken?)
[15:57] <didrocks> lewciie: just pastebin the output please
[15:57] <lewciie> I tried 3 different names, including my full name, lastname, and 'gangsta', none of them worked
[15:57] <lewciie> http://pastebin.ubuntu.com/23456703/
[15:58] <didrocks> yeah, no real clue there. "snapcraft login" worked, right?
[15:58] <lewciie> yes, log in was successful
[15:58] <didrocks> do you mind running snapcraft logout and snapcraft login again?
[15:58] <lewciie> sure
[15:59] <didrocks> (maybe pastebin the result of login as well)
[15:59] <sergiusens> lewciie mind getting this branch https://github.com/snapcore/snapcraft/pull/866 run from source (./bin/snapcraft register) and while you are at it comment on the PR?
[15:59] <mup> PR snapcraft#866: Login with option to agree to terms of service and human friendly errors <Created by psivaa> <https://github.com/snapcore/snapcraft/pull/866>
[15:59] <sergiusens> didrocks ^
[16:00] <sergiusens> it is most likely developer namespace or ToS signing missing
[16:00] <sergiusens> using that branch should give you the correct hint
[16:00] <didrocks> ah, graceful store message finally :)
[16:00] <didrocks> that wil help, indeed
[16:01] <didrocks> lewciie: mind trying what sergiusens did? (do oyu know how to run from a git branch?)
[16:01] <lewciie> let me check :)
[16:01] <didrocks> sergiusens: we don't have snapcraft CLI for ToS signing or such, correct?
[16:02] <sergiusens> didrocks nope, link to webpage is returned
[16:02] <didrocks> sergiusens: it's a start at least :)
[16:02] <sergiusens> didrocks ToS will always be a webpage though
[16:02] <didrocks> ah, you can't grab it, have people type "I accept" or so?
[16:02] <cjwatson> There's an upcoming project to improve terms handling
[16:02] <lewciie> alright I need further support
[16:03] <cjwatson> (store-side)
[16:08] <kgunn> ogra_: have you noticed on dragon board... it's like the terminal just goes for a walk sometimes....
[16:09] <ogra_> for a walk ?
[16:10] <kgunn> ogra_: like keyboard input into my ssh console just doesn't respond for many seconds
[16:12] <ogra_> hmm, no, i dont have that
[16:12] <ogra_> checked dmesg for possible wlan errors ?
[16:14] <kgunn>  nothing there
[16:14] <kgunn> just regular init stuff for wlan
[16:15] <lewciie> sergiusens: not sure how to run that branch, can  get help? :D
[16:15] <ogra_> well, thats the only thing i could imagine
[16:16] <kgunn> ogra_: are you on dragonboard much?
[16:16] <kgunn> just curious
[16:16] <kgunn> wonder who's using it with ubuntu-core besides me
[16:16] <ogra_> not really, but i tend to log in a few times a day and have constantly a ssh windo with htop running on it
[16:16] <ogra_> but nothing where i would actually notice such delays
[16:27] <lewciie> hello? can anyone help? :D
[16:28] <lewciie> please?
[16:28] <lewciie> :)
[16:28] <ogra_> !ask | lewciie
[16:28] <ogra_> :)
[16:28] <lewciie> ahhaa
[16:28] <lewciie> I asked the questions long ago but thanks, I'm not familiarised with this, will follow the rules
[16:29] <ogra_> (all i see above is "i need further support" ... but no question after that)
[16:29] <didrocks> ogra_: I guess there a ping on how to run that branch
[16:29] <didrocks> ok, so lewciie, let's try
[16:29] <lewciie> you're right, I was in private chat, I'm just impatient, apologies, dont want to spam anyone with this!
[16:30] <didrocks> you need to git clone https://github.com/psivaa/snapcraft.git
[16:30] <ogra_> lewciie, better spam ... the channel is logged and google will find the discussion when someone looks for the same issue in a year ;)
[16:30] <didrocks> then, cd snapcraft
[16:30] <lewciie> ogra_: thank :)
[16:30] <lewciie> didrocks: let me do it
[16:30] <didrocks> git checkout bug/1619193
[16:31] <mup> Bug #1619193: Registering a snap without agreeing to terms and conditions fails opaquely <store> <Snapcraft:In Progress by psivaa> <Software Center Agent:Fix Released by fgallina> <https://launchpad.net/bugs/1619193>
[16:31] <didrocks> and replace your snapcraft command with bin/snapcraft (retry doing the registration without --debug)
[16:39] <lewciie> thanks didrocks!
[16:41] <lewciie> it worked :)
[16:41] <didrocks> lewciie: did it?
[16:41] <didrocks> you didn't get an error detail?
[16:41] <lewciie> no, not sure what happened... magic?
[16:41] <didrocks> (without loging out/in again?)
[16:41] <lewciie> I had done that bit already
[16:41] <didrocks> hum… sergiusens doesn't sound great, could that be another bug fixed in master? ^
[16:55] <abeato> jdstrand, hey, thanks for the reviews, I've addressed all the issues
[16:56] <abeato> jdstrand, there is something that I need to solve though: connection of interfaces, like mmcli connected to modemanager daemon, shows an error
[16:56] <abeato> jdstrand, I changed basedeclaration to allow that, but probably the real solution is using snap-declaration. How can I do that?
[16:57] <jdstrand> abeato: let me look at what you changed in the base declaration
[16:58] <abeato> jdstrand, I had to remove "deny-connection: true"
[16:58] <jdstrand> abeato: yes, you need to revert that change to for it to be acceptable to commit
[16:58] <jdstrand> abeato: and then we would add a snap declaration
[16:58] <abeato> jdstrand, I suspected that, but how can I do that?
[16:59] <abeato> I want to connect mmcli to modemmanager daemon, which are in the same snap
[16:59] <jdstrand> abeato: so, this is a rough edge for slot implementation interface developers since the base declaration may prevent install or connection for snaps that don't have a store signed snap declaration
[16:59] <abeato> jdstrand, we need to be able to do this locally for testing
[17:00] <jdstrand> abeato: (this includes installing snaps with --dangerous)
[17:00] <jdstrand> abeato: I understand. today you simply fudge the base declaration like you did, then in the PR you revert that
[17:01] <abeato> jdstrand, alright, will do that for the PR
[17:01] <jdstrand> abeato: I brought this up with Gustavo. how to make this easier for developers needs to be discussed. maybe it will remain as fudging the base declaration but to document that
[17:02] <abeato> jdstrand, that should not be the only way imho, this can get very painful
[17:02] <jdstrand> abeato: so, today, modem-manager already has a snap declaration
[17:02] <jdstrand> abeato: but it isn't used with a locally installed snap where you use --dangerous
[17:02] <abeato> jdstrand, as you would need a hacked snapd for whatever small change you have to do to a snap
[17:02] <jdstrand> abeato: again, I understand, that is why I brought it up with Gustavo
[17:03] <abeato> jdstrand, noted, and thanks, just want to make sure you all know this is not a minor issue for snappers :)
[17:08] <jdstrand> abeato: it probably makes sense to file a bug against snappy
[17:08] <abeato> jdstrand, ack
[17:09] <jdstrand> abeato: simply mentioning that the security of the base declaration requiring a snap declaration from the store is a pain point for local testing before you are ready to upload even to edge
[17:10] <jdstrand> roadmr: https://myapps.developer.ubuntu.com/dev/click-apps/4874/rev/12/ is your test snap?
[17:13] <jdstrand> roadmr: I ask cause choosing lxd-support as your plugs for the snap declaration test makes me twitchy (that is a super-powerful interface) ;)
[17:15] <jdstrand> popey: you may want to subscribe to bug #1592022. I know what the fix is and am working on it
[17:15] <mup> Bug #1592022: 32 bit applications on 64 bit system fail due to seccomp <snapd-interface> <Snappy:In Progress by jdstrand> <https://launchpad.net/bugs/1592022>
[17:17] <roadmr> jdstrand: yes, it is. I'm happy to use another one (but it has to be one that would not normally pass automated review). Any suggestions?
[17:18] <popey> jdstrand: yay
[17:19] <roadmr> jdstrand: I'd prefer not deleting the package but I can if you feel it's safer. I updated the payloads to remove lxd-support, so at least the package will be uninstallable (as the just-updated snap-declaration doesn't allow it)
[17:19] <jdstrand> roadmr: well, it is the correct one for testing 'installation'. 'mir' slot implementation would be good for 'connection'
[17:20] <jdstrand> roadmr: no, it is fine. perhaps removing the snap declaration on prod after you are done would make sense (you could leave it in staging if snapd can point to staging)
[17:20] <ogra_> cjwatson, hmm, shouldnt it be possible to pull stuff via wget from github during an LP snap build ? https://launchpadlibrarian.net/292935958/buildlog_snap_ubuntu_xenial_armhf_kodi-pi_BUILDING.txt.gz
[17:21] <roadmr> jdstrand: it can, yes (SNAPPY_USE_STAGING_STORE=1)
[17:21] <jdstrand> nice! :)
[17:21] <roadmr> jdstrand: ok, I'll be extra careful when using lxd-support for testing
[17:21] <abeato> jdstrand, https://bugs.launchpad.net/snappy/+bug/1640874
[17:22] <mup> Bug #1640874: It is not possible to inter-connect locally installed snaps <Snappy:New> <https://launchpad.net/bugs/1640874>
[17:22] <jdstrand> roadmr: I mean, you're fine. it is just that there is a snap in the store that if modified could be bad. I just like to reduce those kind of things :)
[17:22] <mup> Bug #1640874 opened: It is not possible to inter-connect locally installed snaps <Snappy:New> <https://launchpad.net/bugs/1640874>
[17:24] <roadmr> jdstrand: I made it private, so at least only I can get it
[17:25] <cjwatson> ogra_: Currently only during the pull phase.  This will change in a bit
[17:25] <ogra_> ah, k
[17:25] <abeato> jdstrand, besides this issue, which is your opinion on whether the policy for plugs in classic should include just unconfined or unconfined+label? I answered your comment on the ofono PR, whatever you prefer should be the same for both mm and ofono interfaces I guess
[17:25] <cjwatson> ogra_: Still good practice to fetch remote stuff in the pull phase though, I'd say
[17:25] <jdstrand> abeato: thanks! I updated the description for some clarifying remarks and marked confirmed
[17:25] <jdstrand> roadmr: ah, even better. thanks!
[17:25] <abeato> awesome!
[17:25] <ogra_> cjwatson, yeah, but then i cant get it to build
[17:26] <roadmr> jdstrand: np, and do let me know if you think I should delete it alright. It's a test package so it'd be no big deal
[17:26] <roadmr> s/alright/altogether/
[17:26] <cjwatson> ogra_: https://code.launchpad.net/~cjwatson/launchpad-buildd/snap-proxy-allow-build/+merge/310050 anyway
[17:26] <jdstrand> abeato: it should be the same. I have a todo to look at that pr today and will comment there
[17:27] <ogra_> cjwatson, ah, perfect !
[17:27] <abeato> jdstrand, great, thanks
[17:27] <jdstrand> roadmr: if it is helpful to you, leaving it private seems fine
[17:29] <roadmr> it is, I use it to test c-r-t updates :) I'll leave it there for now.
[18:29] <mwhudson> davmor2: i don't understand, can you take screenshots (or photos, or something) and point out what you mean?
[18:30] <ogra_> paintings !
[18:33] <davmor2> mwhudson: I filed a bug https://bugs.launchpad.net/bugs/1640843
[18:33] <mup> Bug #1640843: Networking fails if you touch the default route <subiquity (Ubuntu):New> <https://launchpad.net/bugs/1640843>
[18:34] <mwhudson> davmor2: are you testing stable?
[18:34] <davmor2> mwhudson: yeap
[18:34] <mwhudson> davmor2: i think that's fixed in edge by hiding that bit of the ui
[18:34] <mwhudson> yeah
[18:35] <mwhudson> in fact pitti and i realized last night that that we didn't understand what that ui was trying to achieve at all...
[18:35] <davmor2> mwhudson: okay I'll have a look at edge after then, we are just writing the manual steps for everything currently
[18:36] <mwhudson> davmor2: yeah, quite a bit has changed in edge, would definitely like your attention on that :)
[18:36] <davmor2> mwhudson: yeah it threw me as well as it look like it was only specific to eth0 as it don't remember seeing it on wlan0 on db so was getting more and more confused with it
[18:37] <davmor2> mwhudson: right I need to finish up the initial round of steps and then I can modify the cases as needs be.
[19:06] <Guest56474> Hello, I was wondering if anyone would be able to help me. Running 16.04 64 bit, all up to date. Installed ubuntu-sdk and am running it as root. When I try to create a project (specifically creating a kit), I get the following error: error: Registering root is not possible. Any ideas would be greatly appreciated!
[19:07] <ogra_> Guest56474, try the #ubuntu-app-devel channel instead ...
[19:07] <Guest56474> Gah, apologies. Thank you!
[19:45]  * davmor2 shakes his fist at mwhudson this loops on hitting enter on the second page back to the start again :(
[19:45] <davmor2> mwhudson: you baypassed network config and user setup but hiding them all together ;)
[19:48] <mwhudson> davmor2: eh?
[19:48] <mwhudson> sounds like it might crashing, can you dig out the logs?
[19:49] <davmor2> mwhudson: give me a minute
[19:54] <davmor2> mwhudson: is it likely to be syslog or else where?
[19:55] <davmor2> mwhudson: never mind found the subiquity log
[19:57] <dpb1> hey, I was trying to use this gist to publish to edge from travis:  https://gist.github.com/evandandrea/c754964bfdfb176844f26f605ebbb8db
[19:57] <dpb1> it uses a docker image 'snapcore/snapcraft', and I got this error when running it:
[19:57] <dpb1> Status: Downloaded newer image for snapcore/snapcraft:latest
[19:57] <dpb1> Issues while validating snapcraft.yaml: Additional properties are not allowed ('grade' was unexpected)
[19:57] <dpb1> is it out of date?
[20:02] <davmor2> mwhudson: see pm, I'm about to knock off for the night so if there is anything else let me know in an email and I can get it to you tomorrow
[20:13] <sergiusens> dpb1 what does snapcraft --version give you?
[20:25] <sergiusens> dpb1 can you pull again?
[20:37] <dpb1> sergiusens: awesome, that fixed it
[20:38] <dpb1> tyvm
[21:28] <dpb1> is there a way to search for snaps in the edge channel?
[21:51] <mup> Bug #1592022 changed: 32 bit applications on 64 bit system fail due to seccomp <snapd-interface> <Snappy Launcher:In Progress by jdstrand> <https://launchpad.net/bugs/1592022>
[22:49] <bschaefer> hmm not sure why i keep getting this on yakkety? Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/g/gcc-6/gcc-6-base_6.2.0-5ubuntu11_amd64.deb 404  Not Found [IP: <IP_ADDRESS> 80]
[22:50] <bschaefer> checking... snapcraft is using the wrong version then the policy i have on the machine (not sure where its pulling the wrong path from)
[22:50] <bschaefer> is my policy: 6.2.0-5ubuntu12 500


[02:26] <countman> hello?
[02:28] <__dan__> hi
[02:28] <countman> haha whats up man.  Hope its okay
[02:29] <__dan__> nps
[02:30] <__dan__> or you can use the channel list function of whatever irc client you're using
[02:30] <countman> how do i look up channels though...
[02:30] <__dan__> depends on what software you're using, but there should be a channel list function somewhere
[02:31] <__dan__> for example using konversation, under the window menu, there is a channel list option
[02:31] <countman> what a coincidince... im using konversation
[02:31] <__dan__> from there you may have to click refresh channels, then it should just be a case of double clicking the channel you want to join
[02:32] <__dan__> in that case it should be easy enough :)
[02:32] <countman> thanks a lot man. Its all gucci now
[02:33] <__dan__> glad to hear it :)
[11:17] <Rienst> hello?
[11:19] <Rienst> Is there somebody?
[11:45] <Walex2> where?
[11:52] <BluesKaj> 'Morning folks
[13:34] <tobiasBora__> Hello !
[13:34] <tobiasBora__> I would like to move with GParted a FAT32 partition (20 Mo) whose goal is obscur for me (I just think it's related to UEFI) but when I move it I have the error "File system doesn't have expected sizes for windows to like it". Do you know how to move this partition ?
[14:50] <Other> Hi, could someone help? I'm using Kubuntu 14.04 on netbook and "alt+F2" doesn't work.
[15:26] <anonuser> hi
[15:26] <anonuser> how can i hide the system messagem from quassel
[15:26] <anonuser> messages
[15:28] <anonuser> right click buffer and hide
[15:28] <anonuser> for who want that also
[17:07] <abaday> hi, how do I choose boot-options when installing ubuntu 14.04 with a usb-stick? There is no os installed on the harddisk
[17:11] <BluesKaj> abaday, kubuntu will install the grub bootloader and the end of the install procedure.
[17:12] <abaday> BluesKaj: I want to autoinstall with preseed
[17:13] <abaday> i dont know how to point at that file when installing with usb stick and having the preseed.cfg on another usbstick
[17:14] <BluesKaj> abaday, preseed? never used that
[17:15] <BluesKaj> abaday, best to pre-partition with gparted then just install to / and /home partitions
[17:16] <abaday> BluesKaj: it is important that the installation uses the preseed.cfg..
[17:18] <BluesKaj> https://help.ubuntu.com/10.04/installation-guide/i386/preseed-using.html
[17:18] <BluesKaj> abaday,^
[17:20] <abaday> BluesKaj: Ive gone through that, but I dont understand this
[17:20] <abaday> "If you are using initrd preseeding, you only have to make sure a file named preseed.cfg is included in the root directory of the initrd. The installer will automatically check if this file is present and load it. "
[17:20] <abaday> root directory of the initrd of my usb-stick?
[17:22] <BluesKaj> dunno abaday sorry , I have no experience with that, but it looks like 14.04 has a problem with preseeding
[17:23] <abaday> BluesKaj: np, where did u hear that 14.04 has problem?
[17:25] <BluesKaj> abaday, http://askubuntu.com/questions/467804/preseeding-does-not-work-properly-in-ubuntu-14-04
[17:26] <abaday> thanks
[17:26] <abaday> " In principle the installer recognizes the preseed file." I dont even know how to get to that step..
[17:27] <abaday> If someone just could tell me where to place it.. :(
[17:32] <BluesKaj> abaday, perhaps asking in #ubuntu will help there are a lot more users and helpers there
[17:32] <abaday> Ive asked for 2 days there, noone is answering..
[17:33] <abaday> ill figure this out somehow, thanks for your time :p
[17:35] <BluesKaj> abaday, probly in the root file, aka /
[20:42] <Walex> abaday: preseeding and installation are explained in the Debian documentation
[20:42] <Walex> abaday: the Ubuntu/Kubuntu package and installation logic is the same as for Debian.
[20:44] <Walex> abaday: as to the 'initrd', the only case where the 'initrd' matteris the 'initrd' when booting, whichever 'initrd' is being used by the boot loader (RGUB or other). The boot 'initrd' is the one you explicitly give as a parameter to the boot loader.
[23:04] <rcnn> sup


[00:12] <lynorian> that exists?
[00:12] <wxl> doubtful.. but it did a long time ago XD
 @HMollerCl The presentation you sent is in Spanish. I don't know Spanish. :(
 @The_LoudSpeaker [@HMollerCl The presentation you sent is in Spanish. I don't know Spanish. :(], I will translate it and send it again
[01:48] <guiverc> fyi: I've never used anything but english with installer, but this user (https://ubuntuforums.org/showthread.php?t=2425318) has issues with it..   If you'd like to comment, or I've missed anything please yell (i'm having issues with pain so concentration is near pointless)
 @The_LoudSpeaker [@HMollerCl The presentation you sent is in Spanish. I don't know Spanish. :(], The one team member that doesn't know even a little Spanish 😂
 🤐
 I will start learning today itself.
 I'm joking with you, but learning a new language is absolutely a great experience :)
 I know enough Spanish to be conversational, if I'm caffeinated :P
 @tsimonq2 [I'm joking with you, but learning a new language is absolutely a great experienc …], I know. Also, I was thinking about learning either Spanish or French. Need it for something else. Now I have one more reason for learning Spanish.
[03:21] <lynorian> I more can only read Spanish I have forgotten most of the vocabulary but the grammar is supringly more logical than English
 Proper English used precisely is an art form though
[04:48] <wxl> oh english doesn't make a darn bit of sense.
[04:48] <wxl> https://en.wikipedia.org/wiki/The_Mother_Tongue
 I would be interested to hear the results in 19.10 ^^. There has been some work in the language selection and locale so the issue may have been resolved.
[06:15] -lugito:#lubuntu-devel- [rMANUAL6e90a92495c8: Add test memory to installation] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL6e90a92495c8
 If I am not mistaken, Spanish is the mother tongue of Hans and mine, if anyone has problems with it, please ask the global team
[11:50] <guiverc> Request help, installed system with two languages (russian) but english(us) keyboard, okay once logged in but RU available at sddm/login (and password is english so can't login I gather) -- https://ubuntuforums.org/showthread.php?t=2425318 if anyone has ideas :)
 Wow! No one in trojita responded yet.
 Shifting to geary.
 Or slypheed
 Why did we stop shipping slypheed?
 As far as I have searched around last night, trojita can only read encrypted mails. Can't sign or encrypt.
 We should be providing a full featured client na?
 Also, trojita doesn't support pop3.
 How to solve lubuntu black screen?
 @The_LoudSpeaker [Wow! No one in trojita responded yet.], Trojita is a lot of silence most of the time.
 @The_LoudSpeaker [Why did we stop shipping slypheed?], ^ @kc2bez
 sylpheed is gtk. it might even be gtk2 and not 3. I haven't looked.
 https://discourse.lubuntu.me/t/19-04-megathread/24/81 … I can confirm this. Can anyone else?
[18:03] <kc2bez> @The_LoudSpeaker https://bugs.kde.org/show_bug.cgi?id=321503
[19:08] -lugito:#lubuntu-devel- [rMANUAL8d2eed9d1d8c: Fix layout in 1.1] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL8d2eed9d1d8c
[19:17]  * lynorian just upgraded to eaon and and now the new version of featherpad has spell checking but we do not include hunspell in our seed nor is it even a suggest of the new featherpad
[19:26] <lynorian> Ok it is just missing hunspell as a dependency
[19:26] <lynorian> but works great once that is installed
[19:29] <lynorian> dang I really should make a bug or task to get this fixed
[19:39] <kc2bez> according to the changelog lynorian there should be a dependency on libhunspell-dev
[19:40] <lynorian> kc2bez: I am not sure that is enough as hunspell not libhunspell fixes it
[19:41] <kc2bez> It is actually a debian bug.
[19:41] <lynorian> ok I have to go now
[19:41] <kc2bez> Ok
[19:42] <kc2bez> I'll keep looking at it.
 3rd computer I upgrade in eoan and have same issue with shortcuts, should I file a bug? Is to write down all the findings I have made
 I think it needs a bug.
[20:39] -lugito:#lubuntu-devel- [rUPDATENOTIFIER7a39232c3c0e: chnage license from GPL2 to GPL3] Hans P Möller<EMAIL_ADDRESS>committed: https://phab.lubuntu.me/rUPDATENOTIFIER7a39232c3c0e
 Chilean national TV about ubuconla, you can practice your Spanish
 Fwd from hbkfabio: https://www.24horas.cl/regiones/maule/conozca-que-son-los-software-libres-3544983
[21:12] <kc2bez> lynorian: It looks like you need the appropriate dictionary on top of just hunspell.
[22:37] <The_LoudSpeaker> @kc2bez, thanks for the link
[22:39] <The_LoudSpeaker> @HMollerCl can you describe the problem briefly? also, describe it in long in the bug. tag me.
[22:56] <The_LoudSpeaker> @kc2bez, for zsync, which iso do I use? normal iso or iso.zsync ?
 @The_LoudSpeaker  iso.zsync
[23:09] <The_LoudSpeaker> thanks
 yw
 @The_LoudSpeaker [<The_LoudSpeaker> @HMollerCl can you describe the problem briefly? also, describ …], what's your lp user?
[23:44] <The_LoudSpeaker> theloudspeaker


[07:18] <dAskreeCh> Jucato: Grats on 100
[08:09] <Tonio_> hi there
[08:40] <maltedik> hi. i compiled kopete from trunk but it doesnt allow connecting to jabber via ssl because qca-tls is missing. isnt that part of qt-copy?
[09:53] <Xand3r> hi
[09:54] <Xand3r> does an german-english english-german dictionary for python, ruby or c++ exist?
[09:55] <Xand3r> if where i can find it and is it licensed under GPL or comparabel licens?
[09:56] <Xand3r> apachelogger: maybe you know something about it ^
[09:56] <apachelogger> sudo apt-get install ding
[09:56] <apachelogger> !info ding
[10:00] <Xand3r> apachelogger: thx a lot
[10:15] <Xand3r> apachelogger: hmm i dont need the things arround i only need a db wich i can use
[10:35] <apachelogger> Xand3r: then only install the db
[10:35] <Xand3r> hmm
[10:36] <Xand3r> to much in there not what i want
[10:36] <Xand3r> i am searching
[10:39] <Xand3r> hmm
[11:56] <Xand3r> apachelogger: i could cry, why i could not compile gtk-qt-engine?!
[12:41] <vorian> morning
[13:36] <Xand3r> hi vorian
[13:36] <vorian> heya Xand3r :)
[13:36] <vorian> sorry i havent had time to revu your package yet
[13:36] <Xand3r> nevermind
[13:36] <vorian> nevermina?
[13:36] <vorian> grr
[13:37] <vorian> nevermind, rather?
[13:37] <Xand3r> mom
[13:38] <Xand3r> i wanted to say: "Never mind"
[13:39] <Xand3r> so what did you get wrong?
[13:39] <vorian> do you not want the package reviewed?
[13:40] <vorian> or do you mean, "no problem" or "i can wait as long as it takes" :)
[13:40] <Xand3r> yea
[13:40] <vorian> oh! OK!
[13:40] <vorian> :)
[13:40] <Xand3r> you see my english is not the best
[13:41] <vorian> mine english is terrible, don't worry about it
[13:41] <vorian> the sad thing is, I only speak english :o
[13:42] <Xand3r> vorian i want to create an shell emulator like yakuake only as plasmoid, what knowleg i need for it
[13:42] <sebas> Xand3r: Why a plasmoid?
[13:42] <Xand3r> then i have it on the desktop or dashboard
[13:43] <Xand3r> or later i only have the button for it on the panel and than it comes from the left or so
[13:43] <Xand3r> sebas: is plasmoid not a good idea?
[13:44] <sebas> Depends on what you actually want :)
[13:44] <sebas> That's why I asked
[13:44] <sebas> Usually, you go "I want something that does this", then you decide how it's implemented
[13:45] <sebas> Not "I want to do a plasmoid, dunno what it should do" :)
[13:45] <sebas> (The latter can be useful for learning, of course)
[13:45] <Xand3r> i know that i want a shell emulator as plasmoid
[13:45] <Xand3r> so how i do that
[13:45] <Xand3r> easyest way
[13:46] <sebas> You drop konsole into the window plasmoid :)
[13:46] <Xand3r> sebas: i have to say that i never programmed
[13:46] <sebas> You can also put a KPart from konsole into a plasma applet of course, and then do the interaction bits
[13:47] <sebas> Then you want to learn programming first I guess
[13:47] <Xand3r> but i have theproblem everytime i started i stoped cause it began to be boring
[13:47] <Xand3r> i need somthing where i cann see what i learnd
[13:48] <Xand3r> so i want to learn with the project
[13:48] <sebas> C++ is probably not a good language to start with though
[13:49] <Xand3r> i have started with python
[13:50] <sebas> Good call :)
[13:51] <Xand3r> ^^
[13:51] <Xand3r> but i have forgotten the most^^
[13:51]  * Jucato hugs C++... the underdog :)
[13:51] <vorian> haha
[13:51]  * sebas likes C++, too
[13:53] <Xand3r> i love plasmoids, for me one of the best things in kde4, so i want to practice my knowleg, programming an plasmoid
[13:53] <Xand3r> some times i have good ideas what is needed but no clue how to do it
[13:54] <Jucato> yeah... I know the feeling... :/
[13:55] <Xand3r> sebas: may be you can teache me how to implement the konsole to a plasmoid
[13:55] <Xand3r> with python
[13:56]  * Jucato was about to say "wasn't there something like that already".. but then saw the "with python" :P
[13:57] <Xand3r> Jucato: using something what is already there is quit useles if you whant to know how it works
[13:59] <Xand3r> i have to go, was nice to talk to you folks, c ya
[15:14] <vorian> smarter: i'm getting a failed build with kvpm
[15:14] <vorian> http://paste.ubuntu.com/26211/
[15:15] <nixternal> hola
[15:15] <nixternal> como estas
[15:15]  * vorian runs
[15:15] <nixternal> you better run!
[15:15] <vorian> ITS NIXTERNAL!!!
[15:15] <nixternal> ;)
[15:16] <vorian> haha
[15:16] <vorian> thanks :)
[15:19] <Xand3r> hi
[15:19] <vorian> howdy Xand3r
[15:20] <Xand3r> howdy vorian
[15:21] <Xand3r> hey apachelogger
[15:22] <apachelogger> howdy Nightrose
[15:22] <apachelogger> hey vorian
[15:22] <apachelogger> yo Xand3r
[15:22] <apachelogger> hi nixternal
[15:22] <vorian> aloha apachelogger
[15:23] <Xand3r> hi Nightrose
[15:23] <vorian> haha
[15:23]  * Nightrose hugs apachelogger
[15:23]  * apachelogger is listening to Rocko Schamoni & Jogging Mystique - Der Mond
[15:24] <Xand3r> apachelogger: please look in the querry
[15:26]  * apachelogger takes Nightrose for a dance
[15:26] <Nightrose> yay
[15:27] <apachelogger> Nightrose: you know that song, right?
[15:27] <nixternal> howdy apachelogger and Nightrose and Xand3r and Jucato and Hobbsee and Riddell and vorian and anyone else who is trolling right now :P
[15:27] <Xand3r> hi nixternal
[15:27]  * Hobbsee beats nixternal
[15:28]  * apachelogger hands Hobbsee a cookie
[15:28] <nixternal> hahhaa, why?
[15:28] <nixternal> no love
[15:28] <Hobbsee> evil highlights
[15:28] <Hobbsee> apachelogger: thanks!
[15:28] <nixternal> hob b see
[15:28] <vorian> hahaha
[15:28] <Nightrose> apachelogger: don't think so :(
[15:29] <Nightrose> heya nixternal :)
[15:29] <apachelogger> Nightrose: you shoudl check it out
[15:29] <Nightrose> k
[15:29] <apachelogger> <3 rocko schamoni
[15:29] <Nightrose> ;-)
[15:31]  * Hobbsee is pondering changing phone carrier.
[15:31] <Hobbsee> which is...not fun.
[15:31] <Jucato> lol hi Nightrose!
[15:31] <Jucato> er.. hi nixternal!
[15:31] <vorian> Hobbsee: it's like going to the dentist!
[15:31] <jjesse> morning
[15:31] <Hobbsee> vorian: a bit.  and i should do that next week.
[15:31]  * Hobbsee also has to get stabbed today :(
[15:32] <Hobbsee> for more not fun things.
[15:32] <apachelogger> bonjour jjesse
[15:32] <apachelogger> Nightrose: did tagging work, btw?
[15:32] <jjesse> bonjour apachelogger
[15:32] <Nightrose> apachelogger: yes and no - tagged it as beta1 first... doh!
[15:32] <Nightrose> fixing now
[15:32] <Nightrose> alpha is tagged
[15:32] <apachelogger> Oo
[15:32] <vorian> no stabbing :/
[15:32] <Nightrose> apachelogger: that 2.0-beta3 in the dialog is evil ;-)
[15:33] <apachelogger> oh
[15:33] <apachelogger> well
[15:33] <apachelogger> Nightrose: you should have used 1.85 anyway :P
[15:33] <Hobbsee> vorian: damn injections.
[15:33] <apachelogger> status tags as part of the release version is pretty stupid IMO
[15:34] <Nightrose> *shrug*
[15:34] <apachelogger> Nightrose: a package manager doesn't care whether it is alpha or beta or rc, it cares whether the version is higher than the installed one ;-)
[15:35] <apachelogger> humans always think everything has to think like them :S
[15:35] <Nightrose> ;-)
[15:35] <apachelogger> but well
[15:35] <vorian> Xand3r: what's your package again?
[15:35] <apachelogger> you are the release manager :P
[15:35]  * vorian is blind today
[15:35] <apachelogger> vorian: mailody-kde4
[15:36] <vorian> ah, there it is
[15:36] <vorian> ta
[15:37] <vorian> any reason it's -kde4?
[15:38] <Nightrose> apachelogger: anything else i need to do besides delete the folder in /tags/amarok/?
[15:38] <apachelogger> Nightrose: nope
[15:38] <Nightrose> *deleting
[15:38] <Nightrose> ok thx
[15:38] <apachelogger> vorian: it's alpha
[15:38] <apachelogger> therefore shouldn't replace the KDE 3 version yet
[15:38] <vorian> groovie
[15:51] <apachelogger> so
[15:51] <apachelogger> who deleted the amarok2 package from the -kde4 ppa?
[15:52] <Hobbsee> me!  muhahahaha!
[15:52] <jjesse> i did cause i don't like you
[15:52] <apachelogger> -.-
[15:52] <apachelogger> that looks like I have to redo the packging a 3rd time
[15:52] <apachelogger> yay
[15:52] <apachelogger> bah
[15:53] <Hobbsee> you can access the old ones
[15:55] <apachelogger> Hobbsee: where?
[15:55] <Hobbsee> on +archive - there's a filter that you can show all statuses, not just published
[15:57] <apachelogger> omg
[15:57]  * apachelogger hugs Hobbsee
[15:58] <Hobbsee> :D
[16:05] <Xand3r> i start to hate my system, i can bet, if i overwrite the hole system nothing changed
[16:05] <Xand3r> why ervertime me?
[16:07] <vorian> Xand3r: manpage problem
[16:07] <vorian> this line
[16:07] <Xand3r> vorian: what is with the man?
[16:07] <vorian> sets the client geometry of the main widget - see man X for the argument format
[16:07] <vorian> sets the client geometry of the main widget \- see man X for the argument format
[16:07] <Xand3r> aha
[16:07] <Xand3r> ok
[16:08] <vorian> :)
[16:09] <apachelogger> Nightrose: you could update the AUTHORS file :P
[16:10] <Nightrose> apachelogger: i did
[16:10] <Nightrose> yesterday night
[16:10] <Xand3r> vorian: that you see such litle mistakes
[16:10] <apachelogger> Nightrose: Alexandre Oliveira<EMAIL_ADDRESS>[16:11] <apachelogger> alex is not around for >1 year now
[16:11] <vorian> Xand3r: hmm?
[16:11] <Nightrose> apachelogger: ye i was asked to leave him in
[16:11] <apachelogger> why?!
[16:11] <Nightrose> substantial contributions to amarok
[16:11] <apachelogger> yeah
[16:11] <Nightrose> don't ask me...
[16:11] <apachelogger> like a life time ago
[16:11] <Nightrose> :P
[16:11] <apachelogger> he is certainly not coming back because his name is in the authors file :P
[16:11] <Nightrose> true true
[16:12] <Nightrose> will kick him after 2.0
[16:12] <Xand3r> vorian: thx for review
[16:17] <apachelogger> Nightrose: libvisual still didn't get dropped?
[16:17] <Nightrose> don't think so no
[16:20] <apachelogger> ah
[16:21] <apachelogger> Nightrose: appears strange to me
[16:24] <apachelogger> d'oh
[16:25] <apachelogger> amarok crashed
[16:26] <apachelogger> hm
[16:26] <apachelogger> Nightrose: I would suggest you activate some kind of crash manager
[16:26]  * apachelogger doesn't have a bt now
[16:27] <Nightrose> apachelogger: how?
[16:27] <apachelogger> Nightrose: use the KDE crash thingy
[16:29] <apachelogger> having an alpha without simple way to obtain a bt seems rather useless IMHO
[16:31] <Nightrose> apachelogger: that doesn't really answer the "how?"  :P
[16:55] <apachelogger> uh
[16:55] <apachelogger> :(
[16:56] <apachelogger> hm
[16:57] <apachelogger> what do you people think
[16:57] <apachelogger> amarok-kde4 OR amarok2?
[16:57] <apachelogger> Nightrose: ?
[16:57] <apachelogger> Xand3r: ?
[16:57] <apachelogger> everyone: ?
[16:57] <Nightrose> amarok2
[16:57] <Nightrose> hmmm otoh
[16:58] <Nightrose> you might want to go for amarok at one point
[16:58] <Nightrose> intepid+1 likely
[16:58] <apachelogger> yes
[16:58] <apachelogger> that's why I think -kde4 is more appropriate
[16:58] <Nightrose> yea
[16:58] <apachelogger> because we will have to provide a transitional package
[16:58] <Nightrose> yea
[16:58] <apachelogger> which means that amarok2 package is gonna stick around for some time
[17:12] <Xand3r> apachelogger: i upload digikam right now on revu, maybe in 40 min you can review it
[17:12] <apachelogger> :D
[17:24] <Xand3r> apachelogger: 1/3 of the orig.tar.gz is up
[17:24] <daSkreech> hi Xand3r
[17:24] <Xand3r> hi daSkreech
[17:49] <smarter> [16:14:01] <vorian> smarter: i'm getting a failed build with kvpm
[17:49] <smarter> strange, I just pbuilt it and no problem
[17:50] <apachelogger> maybe it is the include error that occurs on my system as well?
[17:50]  * apachelogger notes that some things in intrepid are very strange
[17:50] <smarter> [16:14:17] <vorian> http://paste.ubuntu.com/26211/
[17:51] <smarter> I don't understand the error, it looks like some parts of libqt4-dev are missing
[17:53] <apachelogger> hm
[17:53] <apachelogger> black magic
[17:53] <\sh> there is an include statement missing
[17:54] <apachelogger> \#include <KProcess>
[17:54] <apachelogger> \sh: ^
[17:54] <\sh> it wants qprocess
[17:54] <\sh> not kprocess
[17:54] <apachelogger> kprocess probably inherts from qprocess
[17:54] <\sh> therefore you need to include qprocess as well
[17:54] <Xand3r> apachelogger: now it is up
[17:54] <\sh> apachelogger: sure...but I don't trust it ;)
[17:54] <apachelogger> http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKProcess.html
[17:54] <apachelogger> well
[17:55] <apachelogger> the thing is
[17:55] <apachelogger> it build some days ago for me and smarter
[17:55] <apachelogger> *built even
[17:55] <smarter> and it stills build for me
[17:55] <smarter> (I update my pbuilder #two hours ago)
[17:55]  * apachelogger doesn't even wanna try
[17:55] <smarter> s/#/~/
[17:55] <\sh> hae=
[17:56] <\sh> is there any full build log?
[17:56] <smarter> working build or failed build?
[17:57] <\sh> pbuilder --logfile <foo> ?
[17:57] <\sh> failed build
[17:57] <\sh> the other one makes no sense ;)
[17:57]  * smarter uploads the package to his PPA to see what happens
[17:59] <smarter> Maybe the universe will collapse on itself
[18:00] <apachelogger> my universe ain't gonna collapse!
[18:00] <smarter> multiverse then? ;)
[18:01] <apachelogger> hm
[18:01] <apachelogger> fair enough
[18:01] <apachelogger> that thing could easily collapse with all the dangerous software in
[18:01] <smarter> Estimated build start:
[18:01] <smarter> in 22 minutes
[18:02] <apachelogger> -.-
[18:02]  * apachelogger gets beer and popcorn for tonight's build show
[18:02] <smarter> that's approximately one South Park episode
[18:03]  * smarter /away for 20 minutes
[18:07] <Nightrose> apachelogger: *strike* I finally deleted the tag
[18:08] <Nightrose> release notes and upload next
[18:09] <Xand3r> apachelogger: here the damn digikam package http://revu.ubuntuwire.com/details.py?package=digikam-kde4
[18:10] <Xand3r> please review it
[18:10] <Xand3r> i need the knowleg building it in the right way
[18:12] <apachelogger> Xand3r: first, dinner
[18:13] <Xand3r> apachelogger: ok thx, your the best
[18:29] <smarter> hmm, it FTBFS on Launchpad with the same error than vorian
[18:30]  * smarter is confused
[18:33] <Xand3r> i whant to compile a plasmoid but i could not find plasma/widgets/widget.h
[18:33] <Xand3r> has the place moved or what?
[18:33] <Xand3r> cause i have the dev package
[18:34] <smarter> do you have libplasmaX-dev?
[18:35] <Xand3r> smarter: aptitude cant find it, i have hrady btw
[18:36] <apachelogger> smarter: well include process
[18:36]  * apachelogger suspects that the cmake thingy is just b0rked somehow
[18:37] <apachelogger> s/process/qprocess
[18:40] <apachelogger> hm
[18:40] <apachelogger> smarter: go write your motu-contribution-wiki-page-thingy
[18:41] <daSkreech> the cmake is a lie!
[18:42] <apachelogger> Xand3r: does showfoto really depend digikam?
[18:42] <Xand3r> apachelogger: yea i asket in the digikam channel
[18:42] <apachelogger> k
[18:43] <apachelogger> Xand3r: COPYING.LIB is missing
[18:43] <Xand3r> apachelogger: ?
[18:44] <apachelogger> a complete copy of the LGPL
[18:45] <apachelogger> Xand3r: please tell upstream to add such a thingy
[18:46] <Xand3r> why i could not copy one in the debian?
[18:46] <Xand3r> apachelogger: ^
[18:47] <apachelogger> because the upstream stuff contains lgpl licensed stuff
[18:47] <apachelogger> not the debian dir
[18:47] <Xand3r> ok
[18:49] <Xand3r> apachelogger: is that the only mistake :D
[18:49] <apachelogger> Xand3r: dunno
[18:49] <Xand3r> -.-
[18:49] <apachelogger> we don't need a new tarball I guess
[18:49] <apachelogger> but the file should be in SVN
[18:50] <Xand3r> look in #digikam
[18:50] <apachelogger> Xand3r: poke someone
[18:52] <Xand3r> ok
[18:53] <apachelogger> Xand3r: the manpage copyright is wrong
[18:54] <Xand3r> ?
[18:54] <apachelogger> well
[18:54] <apachelogger> look at the manpage
[18:54] <apachelogger> you also forgot to add the showfoto.manpage to debian/copyright
[18:54] <apachelogger> only digikam.manpage listed
[18:56] <apachelogger> Xand3r: the xpm icons for the debian/*.menu files are missing
[18:58] <Xand3r> urg
[18:59] <Xand3r> working
[19:01] <apachelogger> Nightrose: you should work together with digikam
[19:02] <apachelogger> analyze pictures and assign them a certain mood
[19:02] <Nightrose> apachelogger: ?
[19:02] <Nightrose> ah
[19:02] <Nightrose> hehe
[19:02] <apachelogger> anazlye tracks and assign them a certain mood
[19:02] <Nightrose> yea
[19:02] <Nightrose> sounds good
[19:02] <apachelogger> create slideshows with music fitting the pictures
[19:16] <Xand3r> apachelogger: i have two digikam pics, the 16x16 i have to name digikam-16.png how i make that via *.install?
[19:16] <apachelogger> huh?!
[19:16] <apachelogger> for debian/menu files you need xpm icons
[19:17] <apachelogger> see debian policy about that
[19:18] <Xand3r> kk
[19:41] <Xand3r> apachelogger: xpm added, copyright for the manpages setted
[19:58] <vorian> jpds: did you get irssi-plugin-otr uploaded?
[19:58] <JontheEchidna> Here are some quick stats for yesterday's bug efforts:
[19:58] <JontheEchidna> 13% Confirmed bugs closed/changed
[19:58] <JontheEchidna> 4% New bugs closed/changed
[19:58] <JontheEchidna> 3% more Incomplete bugs
[19:58] <JontheEchidna> 21% more triaged bugs
[19:58] <vorian> \o/
[19:58] <vorian> triage ftw
[19:59] <JontheEchidna> The graphs look nice though, lawl: https://wiki.kubuntu.org/UbuntuBugDay/20080708#head-da542d40dfa39fd2edcce72d674b3c8bd5da2ed9
[19:59] <JontheEchidna> probably because they only show the top portion of the graph <.<
[20:00] <JontheEchidna> Anyway, good job everyone!
[20:52] <Xand3r> apachelogger: are there more mistakes?
[20:52] <apachelogger> dunno
[20:52] <apachelogger> busy with helping NickNak
[20:52] <apachelogger> Nightrose even
[20:52] <apachelogger> NickNak: can help you as well, if you want, though ;-)
[20:54] <gnomefreak> apachelogger: are kdesu and kdesudo not linked like gtksu and gtksudo?
[20:54] <vorian> haha
[20:55] <Xand3r> NickNak: ? what is he doing?
[20:57] <vorian> he's comming over for the party
[20:57] <vorian> Xand3r: did you get that lgpl doc yet?
[20:58] <Xand3r> vorian: nop
[20:58] <vorian> :/
[20:59] <Xand3r> i ask again
[20:59] <smarter> gnomefreak: kdesudo links to kdesu
[21:00] <gnomefreak> smarter: why am i hearing one doesnt work
[21:00] <Xand3r> vorian: apachelogger loded it in the svn
[21:00] <smarter> KDE's stock kdesu has been renamed to /usr/bin/kdesu.distrib
[21:00] <smarter> and it caused some problem in the paste, but nobody use it anymore on kubuntu
[21:00] <vorian> excellent
[21:00] <gnomefreak> double checking
[21:06] <gnomefreak> smarter: user is stating neither kdesu or kdesudo works for him (command not found)
[21:07] <smarter> gnomefreak: if he has kubuntu-desktop, kdesudo is installed
[21:07] <smarter> if not, sudo aptitude install kdesudo
[21:09] <gnomefreak> hes on kde4 so im assuming its kubuntukde4-desktop
[21:13] <apachelogger> sebas: Nightrose needs a quicky
[21:13] <apachelogger> ....news
[21:13] <gnomefreak> s/gnomefreak/smarter 16:12 <            jb__ > gnomefreak: GENIUS!
[21:14]  * gnomefreak though smarter deserved that instead of the messenger ;)
[21:14] <smarter> glad I could helped ;)
[21:16] <apachelogger> question is - why don't we build kdesu with sudo support as well
[21:17] <gnomefreak> smarter: what to gparted on the kubuntu disk :( j/k he asked not me
[21:17] <gnomefreak> apachelogger: linking it was good enough (atleast for gk*
[21:17] <apachelogger> well
[21:17] <smarter> apachelogger: asks Tonio_ ;)
[21:17] <apachelogger> but since only kubuntu-desktop depends on kdesudo
[21:18] <apachelogger> either we make kdelibs depend kdesudo
[21:18] <apachelogger> or build kdesu with sudo support
[21:18] <smarter> kdesu sudo support sucks
[21:18]  * gnomefreak gone, them people are crazy in #kubuntu
[21:18] <smarter> (hey, that looks like a poem or something)
[21:19] <apachelogger> smarter: suckish support > no support
[21:20] <smarter> I think it's a config option, not a build option
[21:22] <apachelogger> smarter: in kde4 it's build
[21:23] <smarter> oh, ok
[21:48] <ScottK> mhb: Is there any hope of getting that klamav change from you soon?  I'm otherwise ready to upload to Debian ....
[21:48] <Xand3r> apachelogger: btw you have loaded the lpg doc in the svn, what have i to fo with it?
[21:49] <Xand3r> apachelogger: and i had done a mistkae in screenie-qt
[21:50] <Xand3r> it is libqt4-dev (>=4.4) needed, i only said libqt4-dev
[21:50] <Xand3r> how i can repair that mistake?
[21:53] <Xand3r> ScottK: is it possible the the change is mad only in the backport version
[21:54] <ScottK> Xand3r: It is, but it's equally needed in the Intrepid version.  We strongly prefer to do no change backports, so it would strongly be preferred to fix it in Intrepid first and then backport that package unchanged.
[21:55] <Xand3r> ScottK: i am new in the stuff, but is qt4 in íntrepid only 4.4?
[21:56] <ScottK> True, but the idea is to get the versioned dependencies correct in the main package (in intrepid) so it will not try to build on something that doesn't have 4.4.
[21:56] <ScottK> You should have the versioned depends until 4.3 is no longer in any supported release.
[21:58] <Xand3r> hmm
[21:58] <apachelogger> Xand3r: create an ubuntu2
[21:58] <apachelogger> make the change
[21:58] <apachelogger> upload to revu
[21:58] <apachelogger> find a sponsor
[21:58] <Xand3r> hmm
[21:59] <Xand3r> i mail the upstream asking for an icon of screenie, so i can do both together tomorrow
[21:59] <Xand3r> if i dont get tomorrow an email with the icon i do it without
[22:00] <Xand3r> apachelogger: btw what i have to do with the LGPL doc?
[22:00] <Xand3r> have i build a new orig.tar?
[22:02] <apachelogger> you can
[22:03] <apachelogger> but note in the changelog that you did so and that the copying.lib was added in upstream svn
[22:05] <Xand3r> kk
[22:05] <Xand3r> apachelogger: end of the week i get the new upstream cversion of rubberband
[22:11] <Xand3r> apachelogger: where is get the nice LGPL doc?
[22:11]  * ScottK notes  KDE 3.5.10 in August and wonders about hardy-updates ...
[22:12] <JontheEchidna> http://digg.com/software/First_alpha_release_of_Amarok_2_0_Malina
[22:12] <apachelogger> Xand3r: websvn.kde.org
[22:12] <apachelogger> trunk
[22:12] <apachelogger> extragear
[22:12] <apachelogger> graphics
[22:12] <apachelogger> digikam
[22:12] <Xand3r> kk
[22:12] <Xand3r> danke
[22:12] <apachelogger> de rien
[22:12] <Xand3r> ^^
[22:13] <apachelogger> omg
[22:13] <apachelogger> JontheEchidna: who is gonna package that?! :O
[22:13] <apachelogger> oh right
[22:13] <apachelogger> I already did :S
[22:13] <JontheEchidna> lol
[22:17] <Xand3r> apachelogger: have i any where to refer to the COPYING.LIB ?
[22:22] <apachelogger> Xand3r: no, just state that it was added to SVN
[22:23] <Xand3r> no i mean in the copyright
[22:31] <apachelogger> stdin: the kde4 ppa doesn't have taglib 1.5, so I can't package amarok2 :(
[22:31] <apachelogger> Xand3r: no
[22:31] <Xand3r> apachelogger: alright
[22:35] <Xand3r> so the thing is done
[22:42]  * gnomefreak buys apachelogger a drink
[22:42] <apachelogger> uh thank you :)
[22:42]  * gnomefreak can yell at him now for amarok2+taglibs ;)
[22:42]  * apachelogger is fine with that
[22:42] <gnomefreak> is that all it needs is taglib 1.5?
[22:43] <apachelogger> well, it breaks at taglib dep
[22:43] <gnomefreak> with the rest of kde4
[22:43] <gnomefreak> oh
[22:43] <gnomefreak> taglib is going to need everything else respun on it if changed (or atleast most of kde4)
[22:45] <apachelogger> I think we could throw taglib into usr/lib/kde4
[22:45] <apachelogger> thus avoid abi breakage
[22:49] <gnomefreak> but we dont use kde4 anymomre?
[22:49] <gnomefreak> its /usr/lib/kde now isnt it?
[22:50] <apachelogger> gnomefreak: not in hardy
[22:50] <apachelogger> and hardy is the problem
[22:50] <gnomefreak> true
[22:50] <apachelogger> intrepid already got 1.5
[22:50] <gnomefreak> ;)
[22:50]  * gnomefreak off to bed for tonight
[22:50] <dasKREech> NIght
[22:51] <Xand3r> night
[22:53] <gnomefreak> night


[00:56] <knome> Mapley, hold your... ponies
[00:57] <knome> bbl ->
[04:41] <Unit193> The ISOs are getting awefully large...
[04:42] <Noskcaj> Unit193, current size?
[04:43] <Unit193> ~900MB.
[04:43] <Noskcaj> that's shot up quick
[04:45] <Noskcaj> I wonder what could be used to reduce it
[04:46] <Unit193> http://paste.openstack.org/show/K6vzagtj8MuyXd3TFyUU/
[04:48] <Noskcaj> nothing shows up for the paste
[04:48] <Unit193> Weirdly nothing does unless you hit raw: http://paste.openstack.org/raw/dFvG9B7pMueL843yqKWX/
[04:50] <Unit193> gnome-settings-*, gnome-session*, gnome-control*, and gnome-desktop* should be able to, if we can change what's pulling them. :/
[04:50] <Unit193> Biggest part is, we have 3 python versions, right?
[04:51] <Unit193> Yep.
[04:52] <Noskcaj> i think so
[04:52] <Noskcaj> What do we have to do to drop 3.3 or 3.4 for the final iso?
[04:52] <Noskcaj> also a lot of new cups stuff seems to be in
[04:52] <Unit193> Don't know offhand.
[04:53] <Unit193> Nice part of do-release-upgrade, you get the full list of things being installed (a lot of which gets purged. :P )
[04:54] <Noskcaj> gdisk seems to be a new recommend of udisks2
[04:55] <Unit193> Recommends are killers. :/
[04:56] <Noskcaj> I wonder how much smaller our iso would be with --no-recommends
[04:56] <Unit193> On the bright side, we're about to bump them up with menulibre, mugshot, and xubuntu-community-wallpapers! :P
[04:57] <Noskcaj> :)
[04:57] <micahg> well, we should only end up with 2 versions of python by fonal
[04:57] <micahg> fina
[04:57] <micahg> final
[04:57] <Unit193> Nice.
[04:58] <Unit193> indicator-sound now has an alt dep on pavucontrol, so that shouldn't pull in one of the control centers...
[07:31] <elfy> knome: ok - I'll look later
[08:49] <elfy> knome: looked now - mucked about with it a bit
[08:51] <elfy> zequence: many of our testcases are - open it, start a new <whatever>, save it, close it, does saved <whatever> open, does help work
[08:52] <elfy> really basic stuff
[08:53] <elfy> if you want someone to start running through them - I can find some time for it
[08:58] <elfy> once the basic test is written it's not as bad to flesh them out - where it's required, the worst bit is actually getting them on the tracker - wasn't a great deal of fun last cycle, but it was worth it in the end
[09:30] <zequence> elfy: Simple is best :). I think cub would be a good candidate to work on testing, if he can find some time for it
[09:31] <zequence> It has happened that we released, and there have been some pretty serious, yet fixable bugs
[09:31] <elfy> zequence: well I can start working on writing them today, I'll just work from the testcase bugs for your stuff
[09:31] <zequence> That's mainly what I would like to prevent with testing
[09:32] <zequence> elfy: We only need testcased for our multimedia applications, though
[09:32] <elfy> yep - ok
[09:42] <slickymaster-job> morning all
[09:42] <elfy> hi slickymaster-job
[09:44] <slickymaster-job> hi elfy. Did you have a good weekeend?
[09:44] <elfy> pretty good thanks :)
[09:45] <slickymaster-job> he had a pretty heavy storm here, yesterday
[09:52] <elfy> zequence: I'll work with the 5 'menu' groups you have - Audio Production etc
[10:42] <elfy> knome: somethings up with whatever package deals with keyboard settings, not sure which package it would be - but updates set keyboard layout to US - which can play havoc with passwords
[10:42] <elfy> ochosi - maybe you know which it is
[11:12] <ali1234> it's a issue with ubuntu in general
[11:13] <elfy> ok ali1234 thanks
[12:54] <slickymaster-job> bbl ->
[14:15] <jjfrv8> knome, slickymaster-job, my first cut of the MenuLibre section in the Settings & Preferences chapter: http://imagebin.org/292590
[14:15] <jjfrv8> subject to change pending the decision on whiskermenu
[14:16] <jjfrv8> if I'm going to work on the upstream version, I'm going to need a tutorial from bluesabre :)
[14:17] <ochosi> jjfrv8: we're planning on taking a decision in this week's meeting to finalize the panel stuff
[14:17] <jjfrv8> cool
[14:18] <elfy> let's hope enough people turn up then :)
[14:18] <slickymaster-job> jjfrv8: it looks great, so far
[14:19] <slickymaster-job> but we really do need a tuto on it
[14:21] <ochosi> elfy: yeah, sorry for not being there for the last few meetings, it wasn't that i didn't want to attend
[14:22] <elfy> ochosi: lol - I didn't mean anyone in particular, just if there's not many about it won't help with the whisker menu thing :)
[14:22] <ochosi> well depends, we've voted on it once before
[14:23] <elfy> the general idea yea
[14:23] <ochosi> the proposed panel layout would work without it as well
[14:23] <ochosi> just not as nicely
[14:23] <elfy> and not whisker - but the proposed layout is what I was meaning too
[14:23] <elfy> ochosi: which looks fine to me :)
[14:24] <ochosi> yeah, it's not a real departure imo
[14:24] <ochosi> so there's no need to make a huge fuss about it
[14:24] <elfy> I agree
[14:24] <ochosi> it's just a reduction of the current layout
[14:24] <elfy> yea
[14:24] <ochosi> since it's easy enough for ppl to customize it, i think that makes sense
[14:25] <elfy> exactly - I'd love the default to be exactly like mine - but no-one else is likely to :)
[14:30] <ochosi> :)
[14:30] <ochosi> everyone would like the default to be like theirs i guess
[14:30] <elfy> I'd guess so - being human and inherently bone idle :)
[17:09] <slickymaster-job> knome: ping
[17:09] <knome> slickymaster-job, pong
[17:10] <slickymaster-job> lol, i chased you on -off
[17:10] <knome> heh
[17:10] <knome> slickymaster-job, so yeah, i'll look at that
[17:10] <knome> thanks :)
[21:04] <knome> pleia2, did you have something done re: the website updates?
[21:05] <knome> we should really look into getting a new docs upload for beta 1
[21:06] <knome> that would also close a lot of the -docs blueprint work items, so it would be more accurate
[21:10] <Unit193> Some are pending, like shipping translations. :P
[21:10] <knome> yep.
[21:10] <knome> a lot of stuff is
[21:11] <Unit193> Also did that http://paste.openstack.org/show/iPSpyiAk8MSRAog8pQR3
[21:11] <knome> :)
[21:12] <Unit193> I'm trying to make it so people don't try rm -r for fun, thus used rm -ir
[22:25] <pleia2> knome: no, I was missing all weekend
[22:26] <ochosi> ali1234: have you bothered tedg about indicators lately?
[22:29] <ali1234> not this week no
[22:31] <brainwash> can you link the bug report pls?
[22:31] <brainwash> we could bump it a bit
[22:31] <knome> pleia2, great to hear you've been found
[22:31] <pleia2> :)
[22:33] <ochosi> ali1234: feel like launching a combined "attack" on him now that he's around?
[22:34] <ali1234> is he around?
[22:34]  * knome ponders: hmm, pink wallpaper for trusty
[22:35] <ochosi> yeah, he just was on #ubuntu-desktop
[22:35] <pleia2> I LIEK PINK
[22:37] <ochosi> ali1234: do you know what he has to fix technically speaking?
[22:37] <ali1234> sure, i sent a MR
[22:38] <ochosi> oh, i didn't know that
[22:38] <ochosi> sry, seems i don't know the full backstory
[22:39] <ali1234> i thought i mentioned it
[22:39] <ochosi> you probably did, i wasn't at a few of the last meetings though
[22:50] <slickymaster> hey knome, you still around?
[22:50] <slickymaster> hey knome, you still around?
[22:52] <knome> slickymaster, flooding the channel, aye?
[22:52] <knome> :)
[22:53] <slickymaster> nah, I hardly can feel my fingers
[22:53] <slickymaster> got get myself some gloves :P
[22:53] <knome> yep
[22:53] <slickymaster> did you manage to browse through the wallpaper section?
[22:54] <knome> nope, not yet
[22:54] <knome> though you can poke jjfrv8 with them now
[22:54] <knome> he's able to merge as well
[22:54] <knome> and you don't need my ack for everything really :)
[22:54] <slickymaster> yeah, good idea
[22:54] <slickymaster> well, just playing on the safe side, even know you got a ton of issues between hands
[22:55] <slickymaster> I'll try not to overload you so much
[22:55] <knome> i did look really quickly at it, and what i saw looked fine
[22:55] <slickymaster> I'll ping jjfrv8 on it
[22:56] <slickymaster> if he's also ok with it, I'll make a MP for review
[22:58] <slickymaster> jjfrv8: here's my proposal for the xfdestop of the settings-preferences chapter: http://paste.ubuntu.com/6911856/
[22:58] <slickymaster> jjfrv8: please ping on your opinion
[23:04] <ochosi> Noskcaj: ping
[23:04] <ochosi> micahg: ping
[23:09] <ochosi> knome: just to give you a quick heads up, since ali1234 and i just talked to tedg about gtk3 indicators in #ubuntu-desktop
[23:09] <knome> okay
[23:09] <ochosi> there's no clear ETA on fixing the indicators on the ubuntu side
[23:09] <knome> but i guess it
[23:09] <ochosi> they just pushed the half-borked stuff to get more time
[23:09]  * bluesabre starts working on menulibre upstream documentation
[23:09] <knome> ...it's happening before T?
[23:09] <knome> bluesabre, :)
[23:10] <ochosi> because FF doesn't apply to this "bugfix"
[23:10] <ali1234> i don't think they did it on purpose
[23:10] <ochosi> i think it's a bit nasty, but we should do the same
[23:10] <knome> ochosi, yep.
[23:10] <ochosi> yeah, ali1234 is right i guess, and i didn't mean to make it sound like they did it on purpose
[23:10] <ali1234> it was pushed months ago
[23:10] <ochosi> just unhappy phrasing
[23:11] <ochosi> i'm pretty sure this will get fixed in time
[23:11] <ochosi> for T
[23:11] <ochosi> but not for FF
[23:11] <knome> ACK, i'm fine with that
[23:11] <ochosi> and i also think there'll be no panel-release on the xfce-side before FF
[23:11] <ochosi> so we should push what we have
[23:11] <ali1234> it has to get fixed really, otherwise unity will be broken, as previously stated
[23:11] <ochosi> (is my conclusion)
[23:12] <knome> ochosi, as long as it doesn't render anything completely unusable, sure
[23:12] <ali1234> if we're pushing a git snapshot anyway, i recommend somehow putting in the workaround if possible
[23:12] <brainwash> ali1234: is unity really broken too? indicators seem to work fine like they always did
[23:12] <knome> ali1234, that means more work though
[23:13] <ali1234> brainwash: it's a race condition
[23:13] <knome> ali1234, we've just concluded that we shouldn't do workarounds
[23:13] <ochosi> bluesabre: ?
[23:13] <ali1234> the workaround = putting a variable in the environment
[23:13] <brainwash> ali1234: oh, never encountered it :)
[23:13] <ochosi> bluesabre: whoopsie, that wasn't intended like that :)
[23:13] <bluesabre> ?
[23:14] <ali1234> at the very least we should tell testers to apply the workaround manually
[23:14] <ali1234> and then add it to the release notes if it's still not fixed by then
[23:14] <ochosi> +1
[23:16] <ali1234> the workaround is "echo INDICATOR_ALLOW_NO_WATCHERS=yes | sudo tee -a /etc/environment"
[23:17] <brainwash> it should check for the current session
[23:17] <ali1234> no, it shouldn't, because it is broken on all sessions
[23:17] <ali1234> including unity
[23:17] <ochosi> ali1234: session restart needed after that i presume?
[23:17] <ali1234> right
[23:19] <ochosi> ali1234: indicator-application still doesn't want to start
[23:19] <ochosi> or do i have to reboot?
[23:20] <ali1234> hmm. yeah you might have to reboot
[23:20] <ali1234> check env?
[23:20] <ochosi> yup, need reboot
[23:20] <ali1234> check the /etc/environment is okay too
[23:21] <ali1234> it might have put it on the same line or something
[23:21] <ochosi> PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:INDICATOR_ALLOW_NO_WATCHERS=yes"
[23:22] <ali1234> yeah that's wrong
[23:22] <ochosi> should be in a separate line?
[23:22] <ali1234> yes
[23:22] <ali1234> also it shouldn't be inside the quotes like that
[23:22] <ali1234> you did it manually?
[23:22] <ochosi> no, used your suggested command
[23:22] <ali1234> where did the extra : come from? ;)
[23:23] <ochosi> oh, hm
[23:23] <ochosi> might've added that manually some other time then :)
[23:23] <ali1234> i don't know if /etc/environment has a trailing newline by default, but it should do
[23:24] <ochosi> yup, that worked