[00:48] <robert_ancell> bregma, I'm trying to get the convergence demo set up - do you happen to know what version of Ubuntu touch that is based on?
[01:01] <bregma> robert_ancell, no idea, you'll need to ask Will I think
[05:00] <pitti> Good morrning
[06:00] <didrocks> good morning
[06:07] <seb128> hey didrocks & desktopers
[06:08] <didrocks> hey seb128
[06:23] <larsu> morning!
[06:29] <seb128> hey larsu
[06:30] <pitti> hey didrocks, seb128, and larsu! wie gehtsZ?
[06:30] <seb128> hey pitti
[06:30] <seb128> zzehr gut, danke! und dir?
[06:30] <didrocks> hey pitti, larsu!
[06:31] <larsu> I'm great, thanks!
[06:31] <larsu> how are yo guys?
[07:01] <pitti> larsu: ... apparently not paying enough attention to IRC :) quite well, thanks!
[07:01]  * pitti enjoys working on non-emergency things for a change
[07:03] <larsu> pitti: haha enjoy ;)
[07:12] <willcooke> morning
[07:17] <willcooke> didrocks, you know all that packet loss I was telling you about.... and how once it had arp'd again pings would work for a little while before stopping....
[07:17] <willcooke> duplicate IP address
[07:17] <seb128> hey willcooke
[07:17] <willcooke> hey seb128
[07:17] <willcooke> seb128, I've signed you up to a few UOS sessions
[07:18] <willcooke> seb128, I'll just go for blanket coverage and then we can work out what is really needed once all the sessions are there
[07:18] <willcooke> we should try and spread the load a bit
[07:18] <willcooke> I think I will have to be at all of them, but we should spread the others around
[07:18] <willcooke> I dont think robert_ancell will be able to cover any of them though :(
[07:19] <larsu> morninf willcooke!
[07:19] <larsu> *g
[07:19] <willcooke> g'day larsu
[07:19] <seb128> willcooke, I saw, thanks
[07:19] <willcooke> In other news....
[07:19] <willcooke> I am very concerned that it's nearly May already
[07:19] <didrocks> willcooke: ahah, nice one on duplicated IP address… We always think about firewalling banning, and iptables rules before thinking about the easy guilty one :)
[07:20] <willcooke> What happened to the rest of the year !?!
[07:20] <didrocks> willcooke: I hope you blame your dhcp now!
[07:20] <willcooke> didrocks, worse - I configured it wrong, plain and simple.  What an idiot! :)
[07:20] <didrocks> ahah ;)
[07:21] <willcooke> So I'm now running a load-balanced set up which seems to be working.
[07:21] <willcooke> More testing today, and then I'll write it up
[07:32]  * willcooke -> school run
[07:32] <hikiko> hello :)
[07:34] <hikiko> didrocks, do you think it's safe to temporarily uninstall systemd and use init in vivid? I have troubles each time I restart services and when I restart lightdm I have to reboot (and even reboot doesn't work, I need to press the button after running reboot)
[07:34] <hikiko> I ve uninstalled it successfully on debian unstable
[07:35] <hikiko> but I didn't take the risk in ubuntu yet.. :)
[07:37] <hikiko> (+I had several other minor problems)
[07:42] <didrocks> hikiko: what do you mean by init? like sysvinit?
[07:44] <hikiko> yes
[07:45] <hikiko> and install systemd-shim for the services
[07:45] <didrocks> it's been years that sysvinit isn't supported, I doubt it will even boot, upstart should still work though, but unsupported for the ubuntu desktop image
[07:45] <didrocks> hikiko: what would be more interested is to debug your issues
[07:45] <didrocks> as most of people don't seem to have this
[07:45] <didrocks> I'm sure pitti or I will be pleased to help you
[07:47] <hikiko> I think other people have this lightdm issue too +I'm sure debugging is better I was just wondering because it happens to have 2 vivid installations so, maybe it's faster to work in the non-systemd one while we debug the systemd
[07:48] <seb128> hikiko, what do you do exactly and what is happening?
[07:48] <didrocks> hikiko: well, I guess you will be the "we" as there is no other bug report (AFAIK) about such issues
[07:48] <didrocks> so better to debug it with you, (now ideally)
[07:48] <hikiko> sure :)
[07:49] <didrocks> so let's start with this "I have troubles each time I restart services"
[07:49] <hikiko> :s/services/desktop services!
[07:49] <didrocks> what command are you running, what are you trying to restart and what happens?
[07:49] <hikiko> i try to restart with sudo daemon restart
[07:49] <hikiko> is this correct?
[07:49] <hikiko> eg:
[07:49] <didrocks> which service, for instance?
[07:49] <hikiko> sudo lightdm restart
[07:49] <didrocks> no
[07:49] <didrocks> this isn't supported
[07:49] <hikiko> :D
[07:49] <didrocks> (and never was)
[07:50] <didrocks> sudo systemctl restart lightdm
[07:50] <hikiko> ok :)
[07:50] <hikiko> pebcak
[07:50] <hikiko> let me try :)
[07:50] <didrocks> sure :)
[07:51] <hikiko> ok now I ve run this it worked (so, apologies the restart was a pebcak) but I got another problem
[07:51] <hikiko> maybe it's another pebcak... :D
[07:52] <hikiko> when i start unity and compiz crashes (because for example I ve done a bug in the code or sth)
[07:52] <hikiko> I return to the lightdm login screen
[07:53] <hikiko> and if I re-login successfully
[07:53] <hikiko> the previous session is gone and lightdm starts a new one
[07:54] <didrocks> when you say "when I start unity", it means:
[07:54] <hikiko> +this happens every time i try to run unity --replace ...
[07:54] <didrocks> 1. you are in your session
[07:54] <didrocks> 2. hack hack hack, build…
[07:54] <willcooke> seb128, did you see on the snappy mailing list, sergiusens said they're working on an insaller for Snappy this cycle \o/
[07:54] <didrocks> 3. unity --restart
[07:54] <didrocks> right?
[07:54] <hikiko> yes or ./unity --restart
[07:54] <didrocks> (meaning, restarting unity… actually compiz from inside the session)
[07:54] <hikiko> exactly
[07:54] <didrocks> interesting that this crashes the session
[07:54] <didrocks> so, first, this has nothing to do with systemd (it's still upstart managing the session)
[07:55] <didrocks> I doubt anything change, I'm looking at the unity7 upstart script, it doesn't seem to have any magic to kill the session if compiz fails
[07:55] <hikiko> I know for sure that other people get this too
[07:55] <didrocks> seb128: do you know if we still have this "RequiredComponents" or if any change in gnome-session for this?
[07:55] <hikiko> chris townsend for example got it yesterday
[07:55] <hikiko> didrocks, also, I don't know if that helps
[07:55] <hikiko> when I ran
[07:55] <didrocks> hikiko: do you have any other .crash in /var/crash than compiz? (like a gnome-session one or whatsover)
[07:56] <hikiko> sudo restart lightdm
[07:56] <hikiko> I got an upstart error
[07:56] <didrocks> yeah
[07:56] <didrocks> those commands are upstart ones
[07:56] <hikiko> yes
[07:56] <hikiko> so it's normal
[07:56] <hikiko> to get the errors
[07:56] <hikiko> right?
[07:56] <didrocks> so, basically until lightdm (included) everything is managemed by systemd
[07:56] <didrocks> and there is no lightdm upstart script
[07:56] <seb128> didrocks, gnome-session still has required component, but some jobs got moved from being gnome-session spawned to be upstart services
[07:56] <didrocks> after that, it's upstart
[07:56] <didrocks> seb128: yeah, unity7 is one of them
[07:57] <didrocks> I wonder why compiz crashing trash the session though…
[07:57] <hikiko> in var/crash i have the compiz crashes
[07:57] <didrocks> nothing else?
[07:57] <seb128> didrocks, pitti, I think I mentioned it before, but could be make "restart" being a wrapper and make it call "systemctl restart" under systemd?
[07:57] <hikiko> and some very old from
[07:57] <hikiko> guvcview (a broken camera app)
[07:57] <didrocks> seb128: restart is still used for session job as well
[07:57] <hikiko> skype, chromium
[07:57] <didrocks> seb128: so you need to know which kind of job are used
[07:57] <hikiko> vbox
[07:57] <hikiko> mmm
[07:57] <seb128> willcooke, just saw for the installer, that's great!
[07:58] <hikiko> I have a usr_bin_signon-ui
[07:58] <didrocks> yeah, nothing that's related to the session-components itself :/
[07:58] <seb128> didrocks, well, check the uid?
[07:58] <didrocks> seb128: that can work, sure
[07:58] <willcooke> seb128, I've poked them in #snappy to see if they need any input from us - I might follow up with an email to the ML as well
[07:59] <seb128> willcooke, good, I should probably be on that channel, joined
[07:59] <didrocks> seb128: btw, taping "restart" only close the current g-t window
[07:59] <didrocks> (actually all)
[07:59] <seb128> Try `restart --help' for more information.
[07:59] <seb128> it does here
[07:59] <didrocks> hikiko: let's wait for Laney (he should be around soon), if he heared about such behaviors)
[08:00] <didrocks> seb128: tried 3 times, it closes the g-t window here
[08:00] <seb128> didrocks, weird
[08:00] <didrocks> and I can't ctrl+alt+t now :/
[08:00] <didrocks> grumph
[08:00] <seb128> didrocks, do you have the binary installed?
[08:00] <didrocks> "the binary"?
[08:00] <seb128> "restart"
[08:00] <didrocks> yeah
[08:00] <seb128> "which restart"
[08:00] <hikiko> also didrocks I don't know if I made this clear: unity --replace always sends me to the login screen not only when compiz crashes, +compiz crashes send me to the login screen too (2 different cases)
[08:01] <didrocks> and it's the upstart one, of course, I checked it
[08:01] <didrocks> hikiko: interesting, I guess it's something for Laney
[08:01] <seb128> hikiko, didrocks, could be that restarting unity this week screws the job state and makes other job act in response
[08:01] <hikiko> +also: didrocks  thanks for the help :) +sure, I ll wait for Laney :)
[08:02] <didrocks> seb128: quite a lot of things in the session restarted
[08:02] <didrocks> hikiko: yw!
[08:02] <didrocks> seb128: u-s-d, and so on
[08:02] <seb128> didrocks, weird...
[08:02] <didrocks> weird you don't have the same "restart" behavior
[08:02] <seb128> $ restart
[08:02] <seb128> restart : nom de la tâche manquant
[08:02] <seb128> Try `restart --help' for more information.
[08:02] <seb128> $
[08:02] <seb128> $ which restart
[08:02] <seb128> /sbin/restart
[08:03] <didrocks> and no crash either, it really restarted some session services
[08:03] <Laney> WHAT
[08:03] <didrocks> hey Laney!
[08:03] <seb128> howdy mr Lane
[08:03] <Laney> greetings!
[08:04] <hikiko> hahaha
[08:04] <hikiko> hi Laney :)
[08:05] <hikiko> Laney, I've got an issue after I upgraded to vivid I don't know if it's something in my settings or my use of systemd or a bug in the setup
[08:06] <hikiko> but I remember that chris had it too yesterday when I first got it
[08:07] <hikiko> when I run ./unity --replace ... (for a unity I ve built) I see the lightdm login screen and if I login, I login to a new session
[08:08] <hikiko> +sometimes this happens when compiz crashes and I try to restart it
[08:19] <darkxst> Laney, late pong, we don't ship overlay-scrollbars, so no problems there. how it gtk 3.16 looking for update?
[08:19] <Laney> darkxst: try the ppa
[08:20] <Laney> you had some problems last time i remember
[08:20] <Laney> hikiko: is this new?
[08:20] <darkxst> Laney, problems mixing gtk 3.16 with gnome-shell 3.14
[08:20] <darkxst> but we won't do that
[08:23] <hikiko> Laney, this started at the time I upgraded to vivid (a few days ago)
[08:26] <darkxst> Laney, there doesnt seem to be any easy way around the theming issues, so will just upload core 3.16 along with gtk
[08:28] <ricotz> Laney, darkxst, please take a look at the gtk packaging, iirc there are several manpages missing
[08:30] <Laney> we should get this running --fail-missing
[08:31] <Laney> ricotz: I can merge your branch, bzr is up to date
[08:32] <ricotz> Laney, no bzr branch here yet, this just came into my mind, I stumbled over it while merging 3.14.13
[08:34] <ricotz> Laney, I think the location of gtk-encode-symbolic-svg was weird too which should be in libgtk-3-bin
[08:34] <ricotz> sorry, g2g
[08:35] <seb128> Laney, --fail-missing doesn't work well with multi-builds
[08:51] <Laney> seb128: just tried, the results seem sane here
[08:51] <Laney> shows that there are some .desktop files, icons and manpages missing
[08:52] <Laney> hikiko: Got it, somehow compiz got back into RequiredComponents in /usr/share/gnome-session/sessions/ubuntu.session
[08:52] <Laney> that is a bug
[08:52] <seb128> Laney, is that standard debhelper or do we still have a custom hack script?
[08:52] <Laney> cdbs
[08:52] <Laney> but using the dh tools
[08:53] <Laney> I guess it understands --sourcedirectory or whatever, maybe didn't do that right in the past?
[08:53] <seb128> so the debian/dh_listmissing.pl is deprecated?
[08:53] <Laney> man
[08:53] <Laney> I don't even know what that is
[08:53]  * Laney shows his youth
[08:53] <seb128> that's the script we used to have for --list-missing in gtk
[08:53] <seb128> because the cdbs/dh tools didn't understand the multiple builddirs
[08:53] <Laney> ah
[08:54] <seb128> e.G debian/build/shared debian/build/static
[08:54] <popey> is there any way to "reset" compiz back to defaults?
[08:54] <popey> (other than creating a new user or deleting all dot files)
[08:54] <seb128> popey, there is a reset button in ccsm
[08:54] <popey> problem I have is my GUI freaks out when I add/remove a display. A new clean user doesn't have this problem.
[08:54] <Laney> it could be that if I fix these fail-missing files then it breaks later on
[08:54] <popey> oh!
[08:55] <seb128> popey, "dconf reset -f /org/compiz" should work as well
[08:55] <Laney> this fails at the first dh_install call for the normal lib
[08:55]  * popey presses "reset to defaults" button
[08:55] <popey> unity disappears.
[08:55] <Laney> will try after ricotz gives me his patch :-)
[08:55] <seb128> Laney, k :-)
[08:55] <seb128> let me know how it works!
[08:56] <Laney> ricotz: I want to keep that tool out of the main -bin package, it's not for normal users
[08:56] <Laney> not an "example" but didn't feel like making a new binary for it
[08:56] <popey> seb128: yeah, the dconf reset didn't fix it, will reboot and see if the reset to defaults did, thanks!
[08:56] <seb128> popey, shouldn't need to reboot
[08:56] <popey> my unity died
[08:56] <Laney> hikiko: try removing that "compiz;" and see if it works for you?
[08:56] <popey> I'm unable to alt-tab anymore
[08:56] <seb128> "great"
[08:57] <Laney> this is a darkxst bug btw!
[08:57] <darkxst> Laney, what is a darkxst bug?
[08:58] <Laney> you changed RequiredComponents for ubuntu.session when updating gnome-session to 3.15
[08:58] <Laney> 3.14
[08:59]  * Laney tried to blame systemd at first
[08:59] <Laney> annoyed that it wasn't that :P
[08:59] <popey> bah, not unity wont start at all :(
[08:59] <popey> *now
[09:01] <darkxst> Laney, did I?
[09:04] <popey> seb128: any other ideas for debugging unity not starting :(
[09:04] <seb128> popey, type "unity" on a command line and see what is printed?
[09:05] <hikiko> Laney, what do you mean remove compiz?
[09:05] <Laney> darkxst: probably an accident, but the diff says so - curl -s https://launchpadlibrarian.net/188763536/gnome-session_3.9.90-0ubuntu16_3.14.0-2ubuntu1.diff.gz | zcat | filterdiff -i "*50_ubuntu*"
[09:05] <Laney> hikiko: e.g. sudo sed -i 's/compiz;//' /usr/share/gnome-session/sessions/ubuntu.session
[09:06] <popey> seb128: http://paste.ubuntu.com/10937467/
[09:07] <seb128> popey, "Loading plugin: ccp"
[09:07] <seb128> popey, in ccsm change the settings backend to gsettings
[09:07] <seb128> ups
[09:07] <seb128> "Info: Backend     : gsettings"
[09:07] <seb128> hum
[09:07] <seb128> popey, nothing more than that?
[09:07] <popey> thats everything
[09:07] <popey> display flickers and I end up with an empty desktop
[09:07] <seb128> in unity enabled in ccsm?
[09:08] <popey> hah! no
[09:08] <seb128> popey, "gsettings get org.compiz.core:/org/compiz/profiles/unity/plugins/core/ active-plugins"
[09:08] <popey> the reset must have disabled it
[09:08] <popey> just ticked the box and my launcher appears
[09:08]  * popey hugs seb128 
[09:08]  * seb128 hugs popey back
[09:08] <seb128> weird, that plugin should be in the default
[09:09] <seb128> popey, try to "gsettings reset org.compiz.core:/org/compiz/profiles/unity/plugins/core/ active-plugins"
[09:09] <popey> done
[09:09] <popey> hmm, no window decorations
[09:10] <popey> is /usr/bin/gtk-window-decorator the right thing for window decorator command?
[09:12] <darkxst> Laney, I see, really don't know how that could happen though, the merge would have been based off the vcs-bzr branch
[09:13] <popey> seb128: restarted lightdm, all back to normal. big hugs! Thank you!
[09:13] <seb128> popey, yw!
[09:15] <ricotz> Laney, https://paste.debian.net/plain/169847
[09:17] <Laney> why do you want that program in -bin?
[09:18] <Laney> this diff isn't based on the ppa or bzr
[09:18] <Laney> bleh
[09:18] <ricotz> Laney, I kind of consider this a dev tool and hiding it in example makes less sense
[09:18] <ricotz> Laney, the diff is based on bzr+ssh://bazaar.launchpad.net/~ubuntu-desktop/gtk/ubuntugtk3/
[09:20] <ricotz> Laney, so lp:~ubuntu-desktop/gtk/ubuntugtk3 isn't the current one for 3.16?
[09:21] <Laney> it is, lemme look in a bit, thanks
[09:22] <hikiko>  Laney
[09:22] <hikiko> without compiz;
[09:22] <hikiko> lightdm restarts all the time
[09:23] <hikiko> mmm and with compiz it restarts once
[09:23] <hikiko> wait
[09:23] <hikiko> maybe there's something wrong in compiz
[09:24] <hikiko> ok it was not compiz I reinstalled it :s
[09:25] <hikiko> i ll replace the dconf user as well to have the default unity settings
[09:26] <hikiko> still
[09:32] <hikiko> Laney, didrocks for the record: reboot doesnt work when you have nfs entries in fstab just found out
[09:41] <didrocks> pitti: any idea? we have some tested together IIRC nfs entries in fstab successfully
[09:42] <pitti> hikiko: not known, works fine here; can you please file a bug with a journal, using the "debug shutdown problems" steps in /usr/share/doc/systemd/README.Debian?
[09:43] <willcooke> could it be that nfs it starting before the NIC is up?
[09:43] <willcooke> *is
[09:43] <hikiko> sure pitti :)
[09:53] <pitti> didrocks: yippie! (bug 1423811)
[09:54] <Laney> accidental fix?
[09:56] <pitti> Laney: seems so, about as accidental as it got broken in the first place :)
[09:56]  * pitti lets his computer cool down now, after some 500 VM reboots and 30 git builds
[10:00] <didrocks> pitti: interesting
[10:01] <didrocks> again a proof that coverity can be useful :)
[10:03] <Laney> hikiko: did you file a bug for this --replace issue?
[10:05] <hikiko> no Laney
[10:05] <pitti> didrocks: yeah, and Murphy's law (the commit said "Should Not Fail™")
[10:06] <hikiko> Laney and pitti where should i file both bug reports?
[10:06] <Laney> hikiko: gnome-session for me please
[10:06]  * Laney will upload a SRU for this
[10:06] <hikiko> ok Laney, thank you :)
[10:06] <Laney> an*
[10:06] <pitti> hikiko: nfs-utils for now, we can reassign as appropriate
[10:07] <pitti> hikiko: please tag it "systemd-boot"
[10:07] <didrocks> pitti: of course! I bet it's fsckd's fault :p
[10:07] <hikiko> ok! thanks!
[10:08] <pitti> didrocks: yes, it has its filthy fingers aaaaaaall the way to shutdown!
[10:08] <hikiko> Laney,
[10:08] <hikiko> gnome-session must be configured in order for Launchpad to forward bugs to the project's developers.
[10:08] <pitti> didrocks: and for sure it's also responsible for the world's hunger and raining next Saturday
[10:09] <Laney> hikiko: from a terminal run ubuntu-bug gnome-session
[10:09] <pitti> didrocks: speaking of which, seems we need to change this a last time to read from that new socket that s-fsck now writes to?
[10:09] <didrocks> pitti: I didn't follow what they changed upstream
[10:10] <hikiko> ha! Laney the package gnome-session is not installed...
[10:10] <hikiko> could that be the problem?
[10:10] <didrocks> I think we shouldn't do anything until next systemd release anyway
[10:10] <hikiko> it's not a unity dependency
[10:11] <Laney> hikiko: oh right, no, unity-session then
[10:11] <Laney> or ubuntu-session?
[10:11] <Laney> I forget the exact name
[10:11] <pitti> didrocks: right, but for v220 we need to port it
[10:12] <didrocks> yeah
[10:13] <hikiko> Laney, ubuntu-session maybe?
[10:13] <Laney> if that works, sure
[10:22] <ricotz> Sweet5hark, hi, is there a chance that 4.4.3.2 is hitting a ppa today?
[10:23] <Sweet5hark> ricotz: nope, will be a bit delayed
[10:23] <ricotz> Sweet5hark, alright, let me know when it happens
[10:24] <Sweet5hark> ricotz: willdo.
[11:33] <hikiko> pitti, there's no package nfs-utils in my repos + here: https://launchpad.net/nfs-utils the report a bug link is disabled for me, could I report it somewhere else?
[11:38] <larsu> Laney: if you have a 14.04 vm around, can you please test the patch I just posted to bug #1448969? Resizing columns in nautilus' list view is impossibe if the horizontal scrollbar is visible (possible SRU)
[11:38] <larsu> (bbiab)
[12:00] <pitti> hikiko: ah, it's ubuntu-bug nfs-common, sorry; nfs-utils is the source package
[12:00] <hikiko> ok :)
[12:05] <Laney> larsu: not sure, but I can get one easy enough, thanks!
[12:26] <larsu> Laney: cool thanks. Let me know if it works for you so that I can SRUify
[12:28] <hikiko> pitti, when i use ubuntu-bug nfs-common it's different than with other packages it doesn't ask me to fill the bug details etc it generates an automated bug report I think
[12:28] <pitti> hikiko: right, and it opens a LP page with the bug reporting, as usual
[12:28] <hikiko> no
[12:28] <hikiko> that's the weird
[12:29] <pitti> hikiko: it's pretty much like +filebug, except that it automatically attaches extra info
[12:29] <hikiko> yes pitti i used it a while ago for the other bug
[12:29] <hikiko> just in nfs-common
[12:29] <hikiko> it doesnt open that win
[12:29] <hikiko> and doesn't ask me to login
[12:29] <hikiko> I don't know why
[12:29] <pitti> hm, works here; it collects info for a few secs, then shows the collected data, I press "Send" and get directed to LP
[12:30] <hikiko> do i have to be root? I guess that's not the problem
[12:30] <pitti> hikiko: if anything else fails, you can also use https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+filebug, but it's really supposed to work with ubuntu-bug too
[12:30] <pitti> hikiko: no, you don't
[12:31] <hikiko> ok ok pitti it worked the 4th time just the page needs some time
[12:31] <hikiko> sorry :)
[12:31] <pitti> hikiko: right, it does
[12:32] <pitti> no worries :)
[14:07] <xclaesse> seb128, upgraded to vivid today, (14.04->15.04 went fine with a simple dist-upgrade). Was still wondering what's the plan to integrate GtkHeaderBar with unity?
[14:07] <xclaesse> seb128, here is how I see gedit (build from source), same with devhelp (as packaged in vivid): http://people.collabora.com/~xclaesse/tmp/gedit.png
[14:08] <seb128> xclaesse, we integrate them better now, like decorations are on the right side and looks like our theme, but it's only so much we can do
[14:09] <seb128> not sure about the issue in your particular screenshot, larsu or Laney probably know about the gedit situation better
[14:09] <xclaesse> seb128, I guess it's impossible to move the GtkHeaderBar inside the unity panel like you guys do with the menu ?
[14:09] <seb128> not really no
[14:09] <xclaesse> seb128, problem is that maximised we get 2 bars...
[14:09] <seb128> yeah, that's the app design, talk to the gedit upstreams...
[14:16] <larsu> xclaesse: ya, this is the #1 reason we don't use header bars. I have a patch for gedit upstream that makes it use a traditional title bar
[14:17] <larsu> but it's a bit weird without a tool bar
[14:17] <xclaesse> larsu, seb128: sooner or later all GNOME apps are going to have the same thing
[14:17] <larsu> xclaesse: we know
[14:17] <xclaesse> IMO their design is ridiculous, but unity will have to deal with it I guess :(
[14:18] <larsu> their design is pretty good actually
[14:18] <larsu> it just doesn't fit well with unity
[14:18] <larsu> patch is at https://bugzilla.gnome.org/show_bug.cgi?id=741904 if you're interested
[14:20] <seb128> xclaesse, yeah, well as an user you can decide to user other apps that the GNOME ones ;-)
[14:21] <larsu> seb128: that's true, but we should strive for a good experience for the default apps
[14:23] <xclaesse> larsu, hm, I build gedit with the patch from bugzilla, didn't change anything. Probably did something wrong :/
[14:24] <larsu> xclaesse: hm, weird. I wanted to update that patch a bit anyway. I'll have a look later today or tomorrow
[14:24] <seb128> larsu, right, I'm just saying that there is only so much we can do if designs conflict
[14:25] <larsu> seb128: indeed
[14:25] <xclaesse> larsu, ah forget me, there were conflict when apply the patch that I didn't resolve :p
[14:25] <larsu> hehe :)
[14:45] <qengho> Hi all. I'm trying to make chromium-browser do two new things. I would like your help in trying the new chromium packages in Stage PPA. ppa:canonical-chromium-builds/stage
[14:46] <qengho> Who's interested in yesterday's Cr release? New hot v42! Anyone?
[14:49] <willcooke> qengho, o/  (i'm on 14.04 still though)
[14:50] <qengho> willcooke: Oh, I have to support that too. It's in there.
[14:50] <willcooke> woot
[14:50] <willcooke> I'll add the PPA tomorrow morning then so I dont lose where I am today
[14:53] <kenvandine> willcooke, 14.04?  you're so old school
[14:53] <willcooke> word
[14:53] <willcooke> I've got a dog food VM
[14:53]  * kenvandine waves to desktop :)
[14:54] <willcooke> and I will update this machine, but I want a fresh install
[14:54] <willcooke> so, ya know, backups
[14:54] <kenvandine> :)
[14:54] <kenvandine> seb128, i copied code from unity-scope-click that should fix that bad framework bug, working on getting a build to test now
[14:55] <seb128> kenvandine, hey, \o/
[14:55] <kenvandine> more duplicated code... grrr
[14:55] <seb128> yeah :-/
[14:55] <kenvandine> the good news is there is a spec being worked on this week to fix that problem :)
[14:55] <seb128> great
[14:56] <kenvandine> but in the mean time we need to keep the updates plugin working
[14:56] <seb128> yeah
[14:57] <seb128> dobey mentioned previously that we should use the scope service to install or something
[14:57] <seb128> or the wrapper they have
[14:57] <seb128> rather than manually deal with it
[14:59] <Laney> click got an API
[16:07] <xclaesse> outch, google map on firefox with ubuntu vivid is utra slow
[16:07] <xclaesse> with chrome it's perfect
[16:21] <Laney> larsu: I get a segfault in the testsuite with your backport
[16:21] <Laney> on 3.10
[16:22] <seb128> xclaesse, yeah, google streetview is un-usable in firefox for me for over a cycle, dunno why
[16:22] <seb128> it takes like 30s to display one frame
[16:22] <seb128> webgl or something not working there I guess?
[16:23] <xclaesse> seb128, it's not only street view, it's also panning the map
[16:23] <xclaesse> seb128, was working fine on 14.04 afaik
[16:23] <seb128> well, maybe same issue
[16:23] <xclaesse> looks like unaccelerated webgl
[16:23] <seb128> I'm sure maps requires a lot less rendering
[16:24] <seb128> streetview is just the same issue pushed further
[16:24] <xclaesse> yeah
[16:27] <Laney> larsu: looks like b4282e5ef, trying that
[16:28] <larsu> Laney: thanks
[16:28]  * larsu didn't run it (sorry)
[16:28] <Laney> that's what packagers are for
[16:29] <larsu> :)
[16:30] <davmor2> seb128: it's the if "ua=firefox: run_speed=dead_slow" at the top of all google code right ;)
[16:30] <seb128> right
[16:30] <Laney> looks good
[16:30]  * Laney builds it properly with this
[16:32] <xclaesse> seb128, fishgl.com is ultra slow as well
[16:34] <xclaesse> seb128, on fedora with same firefox version, it works perfectly
[16:35] <seb128> xclaesse, same version = binary from upstream, or same version but distro builds?
[16:35] <seb128> chrisccoulson, is there any known issue with firefox/webgl on Ubuntu?
[16:35] <xclaesse> seb128, I mean the about dialog says "37.0.2"
[16:36] <xclaesse> distro rebuild it I guess
[16:37] <seb128> xclaesse, what if you go in about:config and set webgl.force-enabled  to true?
[16:37] <chrisccoulson> seb128, no idea - about:support says it's blacklisted with my drivers
[16:38] <chrisccoulson> I'd ask upstream if I were the Firefox maintainer :)
[16:38] <seb128> chrisccoulson, you still are the defacto one :-)
[16:38] <chrisccoulson> heh
[16:39] <xclaesse> seb128, it's much better, but still slow
[16:39] <xclaesse> seb128, I get 25fps with the force-enabled
[16:40] <xclaesse> in chrome I get 60fps
[16:40] <seb128> xclaesse, how about firefox on fedora?
[16:40] <seb128> is that on the same box?
[16:40] <chrisccoulson> webgl has always been slow with Firefox because it's using a software compositor
[16:40] <xclaesse> it's on my collegue's laptop, will ask to test again when he has time
[16:40] <seb128> k
[16:40] <chrisccoulson> which means it uses glReadPixels for webgl
[16:41] <seb128> xclaesse, I assume you get the normal firefox speed now, chrome(ium) is probably just more performant
[16:41] <seb128> chrisccoulson, thanks
[16:41] <chrisccoulson> our phone browser runs webgl better than firefox btw
[16:41] <seb128> :-)
[16:41] <chrisccoulson> just thought I'd get that in there
[16:41] <seb128> good to know!
[16:42] <seb128> we should pay some free beer to whoever is working on that :p
[16:43] <chrisccoulson> Yeah, that's a good idea :)
[17:42]  * willcooke -> EOD