[02:02] <xtalmath> s it possible to make my application generate a prompt dialog, that is system wide? so it can say block me from using the browser? is it a specific system call?
[04:20] <pitti> Good morning
[04:59] <didrocks> good morning!
[05:00] <pitti> bonjour didrocks, ça va ?
[05:00] <pitti> didrocks: comment est le plastique ?
[05:01] <didrocks> pitti: le plastique était bien, mais fini hier soir :(
[05:01] <didrocks> pitti: je travaille un peu avant d'aller à l'aéroport (mon vol est à 11h45)
[05:02] <pitti> didrocks: ah, es-tu déjà rentrè ?
[05:02] <didrocks> pitti: non, tout à l'heure
[05:02] <pitti> ah
[05:02] <didrocks> pitti: et toi, comment ça va ?
[05:02] <pitti> didrocks: ça va bien ! j'ai dormi très bien à nouveau \o/
[05:03] <didrocks> ah, super ! :-)
[06:25] <larsu> good morning!
[06:26] <didrocks> hey larsu!
[06:26] <larsu> Laney, attente: congrats! https://www.bassi.io/articles/2015/09/15/who-wrote-gtk-3-18/
[06:27] <seb128> good morning desktopers
[06:27] <larsu> didrocks: bonjour! ça va?
[06:27] <larsu> oh aussi seb128! How are you?
[06:27] <seb128> hey larsu, I'm good thanks, how are you?
[06:27] <didrocks> larsu: ça va bien :)
[06:27] <didrocks> et toi ?
[06:27] <larsu> seb128: great! Fixed gnome-logs boot menu for the 99.999% case late last night
[06:28] <larsu> boot menu showed 0 entries when there's only one boot
[06:28] <larsu> instead of ... you know ... 1
[06:28] <larsu> didrocks: nickel! merci
[06:29] <larsu> pitti: morning :) Do you know if we can get the journal to keep the most recent N logs?
[06:29] <larsu> I see the point of not storing all of them, but having the last after a crash is probably useful
[06:29] <pitti> hey larsu
[06:30] <pitti> larsu: sure, just enable persistent journal, see /usr/share/doc/systemd/README.Debian
[06:30] <larsu> I think I did this with `mkdir /var/log/journal`
[06:30] <larsu> but according to its man page, it now stores everything, no?
[06:30] <pitti> larsu: or just look at syslog, if you have that installed (I enabled persistant journal and uninstalled rsyslog)
[06:31] <pitti> well, everything up to the size limits
[06:31] <larsu> ah
[06:31] <larsu> cool
[06:31] <larsu> that makes sense
[06:31] <larsu> thanks :)
[06:31] <seb128> hey pitti
[06:31] <pitti> ça va seb128 !
[06:31] <seb128> pitti, bien! et toi ?
[06:31]  * larsu removes rsyslog as well - no need to keep *that* many logs
[06:31] <pitti> seb128: je vais bien aussi, merci ! j'ai dormi bien à nouveau
[06:32] <seb128> ah, bonne nouvelle
[06:32] <pitti> larsu: if you already have a persistant journal, then you should already see the previous boot -- try "journalctl -b -1"
[06:32] <larsu> I do now, yes
[06:32]  * larsu only noticed because gnome-logs is buggy in that case
[07:24] <larsu> didrocks: so.... I'm actually eating a croissant with chocolate inside right now (sorry)
[07:24] <larsu> (not claiming it's french, but it is very tasty)
[07:25]  * didrocks cries
[07:26] <didrocks> ok, going to checkout and then, train to the airport, I'll see if I can connect from there
[07:26] <didrocks> later guys!
[07:26] <larsu> later!
[07:51] <willcooke> hi didrocks, bye didrocks
[07:51] <willcooke> morning all
[07:52] <larsu> hi willcooke. sup?
[07:52] <willcooke> larsu, word
[08:03] <Laney> hey!
[08:04] <seb128> hey Laney!
[08:04] <seb128> wie gehts?
[08:05] <larsu> morning Laney!
[08:05] <larsu> and congrats again :P
[08:07] <larsu> Trevinho: new scrollbars break on web views :/
[08:07] <Laney> told him that yesterday
[08:08] <larsu> ah, thanks
[08:09] <Laney> something messed up my keyboard then, it was like alt was held down all the time
[08:09]  * Laney blames synergy
[08:09] <Laney> oh i still can't use shift, wtf
[08:09] <larsu> shift is OVERRATED
[08:10] <darkxst> hey desktopers
[08:10] <Laney> thanks for the congrats!
[08:10] <davmor2> larsu: DOES THAT MAKE NO SHIFT underrated?
[08:10] <Laney> oh It WoRkS aGaIn
[08:12] <seb128> hey darkxst
[08:14] <seb128> willcooke, so you posted the compiz/unity blog? now any plan to run the bot to close bugs before people waste effort on triaging those manually? ;-)
[08:16] <willcooke> seb128, yeah, didrocks said he has some bots which can help
[08:17] <seb128> willcooke, that was not prepared before sending the post? :-/
[08:20] <willcooke> seb128, I want to allow time for people to find out that a robot is going to start closing their bugs so we don't get a sudden influx of "Hey, why did you close my bug" questions.
[08:20] <larsu> willcooke: you'll get that either way, sadly
[08:20] <willcooke> I dont think a gap of some days/a week is going to be a huge problem
[08:20] <willcooke> larsu, yeah, probably true
[08:20] <larsu> it helps if the closing comment contains "feel free to reopen if this is still an issue"
[08:20] <willcooke> but if I can point to some public information that was published before we actioned it
[08:21] <larsu> indeed
[08:21] <willcooke> then we have a robust defence
[08:21] <darkxst> you don't need a robot to close bugs, just 10 lines of python ;)
[08:21] <larsu> I agree that this way around is better
[08:21] <larsu> darkxst: that's what we call robots these days
[08:21] <larsu> or ... you know .... "bots"
[08:21] <willcooke> you kids, and your slang
[08:21] <darkxst> larsu, its ok, I have a bot
[08:22] <larsu> heh
[08:24] <seb128> willcooke, right, it doesn't mean we couldn't have got the solution ready before posting :-)
[08:25] <seb128> it just put us under pressure now because we started the process while we didn't figure out all the details yet
[08:25] <seb128> but oh well, minor problem
[08:25] <willcooke> yes, minor
[08:27] <darkxst> I have a script somewhere to close of eol bugs, or are you want to close off more than that
[08:31] <willcooke> darkxst, that will be useful, can you share?
[08:32] <darkxst> willcooke, will dig it out after dinner
[08:32] <willcooke> thanks
[08:32] <seb128> willcooke, I'm going to help triaging a bit, let's see where we can get ;-)
[08:33] <willcooke> seb128, I'm closing the apport ones now
[08:33] <seb128> great
[08:33] <seb128> manually?
[08:33] <willcooke> maybe :)
[08:34] <willcooke> depends on how many there are, vs how long it would take me to write a script
[08:34] <seb128> some people probably have scripts for that
[08:35]  * didrocks is now waiting for his plane (boarding in 40 minutes)
[08:36] <seb128> hey didrocks
[08:36] <mpt> larsu, because “UTC” is something that (a) geeks may want to use and (b) has only one meaning. We couldn’t cover all abbreviations because many of them are ambiguous: to cover just the ones starting with “A”, ADT, AMST, AMT, and AST each refer to two different time zones.
[08:36] <seb128> enjoying Schripold?
[08:37] <didrocks> seb128: yeah, always liked this airport :)
[08:37] <didrocks> enjoying the weather as well :p
[08:37] <seb128> lol
[08:37] <didrocks> so typical!
[08:37] <didrocks> :)
[08:37] <seb128> yesterday evening was fine!
[08:37] <seb128> I went to play tennis from 8 to 10
[08:37] <seb128> great weather
[08:37] <didrocks> yeah… in 3 days, it was the only time which was fine :p
[08:37] <seb128> when I wouldn't have bet on in the afternoon...
[08:38] <didrocks> indeed…
[08:38] <didrocks> seems like there are high wind in Lyon (~110km/h)
[08:38] <seb128> Trevinho, andyrock, bug #1496294 seems to be new in wily and high ranked on e.u.c
[08:38] <didrocks> I hope the arrival won't be jumpy
[08:38] <seb128> didrocks, urg, good luck
[08:38] <larsu> mpt: fair enough, but being able to type this in "Location" still feels wrong to me
[08:41] <mpt> larsu, it’s a hidden treasure. I wouldn’t want to add extra UI for it.
[08:41] <mpt> (Or distract people by labelling it “Location or UTC:”.)
[08:42] <larsu> people that live in a city that starts with "utc" will see it ...
[08:42] <larsu> *cough*
[08:42] <larsu> well, at least people in cities starting with u and ut
[08:45] <flexiondotorg> Morning.
[08:45] <flexiondotorg> I was just smoke testing the daily isos.
[08:46] <flexiondotorg> Ubiquity crashes on start up on both Ubuntu MATE and Xubuntu.
[08:46] <flexiondotorg> Are you aware?
[08:47] <Laney> Is it the network-manager thing?
[08:47] <flexiondotorg> Yep.
[08:47] <larsu> Laney is aware
[08:47] <Laney> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1495017/comments/16
[08:48] <flexiondotorg> Laney, Just saw nm has been updated :-)
[08:49] <darkxst> I think that was fixed today
[08:50] <seb128> it's still in proposed
[08:50] <seb128> oh, just moved to release
[08:59] <seb128> darkxst, bug #1496298 is due to new nautilus in the GNOME ppa, yet another case of GNOME dropping a key from a schemas...
[09:00] <larsu> sigh
[09:00] <larsu> when will people realize that these are public API
[09:15] <seb128> larsu, Laney, do you have youtube showing as a source in totem?
[09:16] <seb128> I don't, I wonder if that's a local issue
[09:16] <larsu> nope
[09:16] <larsu> rai.tv, blib.tv, and apple trailers
[09:16] <seb128> same here
[09:17] <Laney> yeah same
[09:17] <Laney> is it meant to?
[09:20] <seb128> I thought it was
[09:20] <seb128> I expect youtube to be more popular than the other ones
[09:20]  * larsu vaguely remembers some legal issue
[09:23] <seb128> well, I guess it's supposed to work
[09:23] <seb128> https://git.gnome.org/browse/totem/commit/?id=8121563b4fb276a984ed6fcd8d4d27f83b3aaa16
[09:23] <seb128> recent key update
[09:24] <seb128> ok, so I don't know how to test that, but everything else works, so let's upload the bugfix version
[09:30] <seb128> mpt, your libusermetrics landed by error (validated the wrong line), I would rather keep it than revert and push through with the other part of the fix ... could you comment on the mp on what would be the right behaviour (having no text on first boot, or just the standard "no text sent today", etc)
[09:34] <mpt> seb128, sure, do you have the link handy?
[09:34] <willcooke> Trevinho, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1197872
[09:34] <popey> seb128: on that subject, blip.tv should be removed from totem, they were bought out and shut down recently
[09:34] <willcooke> Trevinho, Do you think we should keep this open and work on it?
[09:37] <seb128> mpt, https://code.launchpad.net/~mpt/libusermetrics/1286276-no-data-sources/+merge/268042 see mterry's comment
[09:38] <seb128> popey, thanks
[09:38]  * seb128 is away for some bt in car testing and some errands
[09:38] <seb128> bbiab
[09:38] <mpt> thanks
[09:45] <darkxst> seb128, will take a look after dinner
[11:15] <andyrock> willcooke: i think it's safe to close it
[11:15] <willcooke> andyrock, thank you
[11:16] <andyrock> willcooke: btw I finally managed to get a fix for the resize problem
[11:16] <andyrock> \o/
[11:16] <willcooke> andyrock, yay!
[11:16] <andyrock> turned up to be a 1 line fix
[11:16] <andyrock> 2 weeks for a lne
[11:16] <andyrock> *line
[11:16] <willcooke> andyrock, ha!  Well, good work!
[11:16] <darkxst> willcooke, this seems to be the script I had, no idea where it came from though http://pastebin.com/f58wNZGd
[11:17] <darkxst> though I do recall writing one also, can't find that though
[11:17] <willcooke> thanks
[11:17] <willcooke> I've got my own simple script pretty much ready to go
[11:18] <willcooke> just working out how to add comments
[11:18] <willcooke> and that script you showed has that functionality, so I'll steal that
[11:20] <darkxst> comments are about the easiest bit of the LP api
[11:21] <willcooke> I was somewhat surprised I had to slice a string to get the bug ID
[11:21] <willcooke> then I found the bug object
[11:21] <willcooke> :)
[11:22] <darkxst> yup finding the data, is usually the harder bit
[11:23] <darkxst> and in some cases, it just plain doesnt exist ;(
[11:24] <willcooke> ok, so my script can now find and comment on the bugs I want and set the staus
[11:24] <willcooke> status
[11:25] <willcooke> But I need it to be able to set the status on both the upstream project and the Ubuntu package
[11:25] <willcooke> back to dir(bug)
[11:29] <darkxst> don't think I have ever tried to extract upstream project, from an ubuntu package, but surely it is there
[12:45] <didrocks> phew, that was… interesting
[12:45] <didrocks> I didn't think I ordered any roller coaster topping in addition to the flight
[12:47] <willcooke> :D
[12:48] <didrocks> at least, home and safe ;)
[12:49] <larsu> welcome home didrocks :)
[12:51] <didrocks> thx larsu!
[12:51]  * larsu curses at gtkentrycompletion
[12:52] <larsu> srsly, I'm very close to reimplmenting it, but sanely
[12:52] <larsu> it's like, oh, you have 50 matches? Let's show a VERY LARGE window
[12:54]  * popey wonders where to file a bug where ALT+PRSCR _always_ messes up the menu/titlebar in screenshots http://imgur.com/2HWwQL1
[12:55] <popey> I think it's because of our menus, but not sure where that goes? Unity?
[12:55] <popey> willcooke: ^
[12:55] <larsu> does turning of locally integrated menus help?
[12:56]  * popey looks for that option
[12:57] <popey> larsu: yes
[12:57] <larsu> blame Trevinho, then ;)
[12:57] <popey> \o/
[12:57] <didrocks> larsu: it's a little bit more complicated than that
[12:57] <didrocks> larsu: so, you press alt, you have the locally integrated menu appearing
[12:58] <larsu> oh!
[12:58] <larsu> haha
[12:58] <Trevinho> larsu: yeah... that would be also without LIM in geneeral
[12:58] <didrocks> then, you press Print Screen
[12:58] <larsu> this is gold :D
[12:58] <didrocks> you have the effect of fading to the menu again
[12:58] <didrocks> and gnome-screenshot starts
[12:58] <Trevinho> by pressing Alt in general unity shows the menus (also global ones)
[12:58] <didrocks> yep
[12:59] <didrocks> interesting, gnome-screenshot only execute when you release alt
[12:59] <didrocks> so, if you press alt + print screen, keep alt pressed
[12:59] <didrocks> gnome-screenshot is only executed when alt is released
[13:00] <didrocks> so, can't easily avoid that, or the screenshotting need to be in unity to control the rendering
[13:05] <larsu> didrocks: clearly that's where it belongs
[13:12] <mdeslaur_> mpt: hi! do you have any opinion on https://code.launchpad.net/~mdeslaur/indicator-power/fix-priorities/+merge/260903
[13:22] <seb128> Trevinho, could you review https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446081?
[13:22] <seb128> Trevinho, there is a patch on there
[13:24] <seb128> larsu, there is a small css patch to https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1448272 do you think you could have a look?
[13:25] <larsu> seb128: err, I don't have this line
[13:26] <seb128> larsu, yeah, me neither, but seems some user do, unsure why
[13:26] <mpt> mdeslaur_, looking
[13:27] <larsu> seb128: also, what's this patch for? rhythmbox itself?
[13:28] <larsu> seb128: this already fixed it: http://bazaar.launchpad.net/~jjardon/rhythmbox/trunk/revision/8892
[13:28] <larsu> I'll make a note on the bug
[13:29] <seb128> larsu, great, thanks
[13:30] <seb128> larsu, sorry, I didn't look much, going through https://launchpad.net/ubuntu/+patches and subscribing sponsors/pinging some people on the way to get some reviewing action ;-)
[13:30] <larsu> seb128: no worries. No need for you to do all the work. happy to help out
[13:30] <seb128> thanks!
[13:31] <Newww> Developers! Please add the following item. On windows there is a convenient option to specify a file for download in the form http links. Example https://pp.vk.me/c629117/v629117790/eee0/LRcvOplaV8I.jpg I want to upload the file to the file sharing. This file is located on another server. On windows I can provide a link to a file that is dialog box itself will load the file into a temporary folder, and select it.
[13:31] <Newww> On Unity, I have to first download the file to, and then specify the file.
[13:32] <larsu> Newww: to upload, you can use nautilus' "Connect to server" feature. You can then select that server from the sidebar
[13:34] <Newww> larsu: No, I just want to dialog supported http links, not just local files.
[13:35] <larsu> not sure I understand. Do you want to open http links in an app or upload files to some http server while saving?
[13:37] <Newww> I want to open http links in an app, Some apps such links, and some do not, like the chrome or firefox.
[13:37] <larsu> all apps using gvfs should support this just fine
[13:37] <larsu> gedit works, for example
[13:38]  * larsu opens google.com in gedit and feels awesome
[13:39] <Newww> More specifically, I want to choose the file to something from another server directly to the dialog box itself elected him, loaded into a temporary folder. So much faster than most.
[13:41] <Newww> Yes, it works to open, but not selected. Chrome or firefox not support this, but windows I often use it, it is convenient and reduces time.
[13:42] <Newww> Little such detail that really need :)
[13:43] <larsu> ah, so you do want it the other way around. I don't think that works unless you add a server in nautilus
[13:44] <didrocks> bye unity-panel-service, you didn't need to take 98% of my CPU IMHO
[13:45] <larsu> didrocks: probably it's doing something important
[13:45] <larsu> don't interrupt it!
[13:45] <didrocks> larsu: ofc!
[13:45] <qengho> Newww: is this only in web browsers that you can paste a location of a remote resource? Is it a place you normally type a local file name?
[13:46] <larsu> it started displaying very small fonts for me recently
[13:46] <Newww> Adding a server is not necessary, there are so many different servers, each adding it's inconvenient. It seems to me that you do not understand me a little bit.
[13:47] <Newww> qengho: Exactly!
[13:49] <qengho> I'm guessing that the file selector on Windows is less strict. A web page asks for a file to upload. You don't pick a file, but instead paste a URL. Windows' browser sends that text string to the remote end, which processes it magically. Ubuntu's file selector makes sure you are sending a file.
[13:50] <mdeslaur_> mpt: excellent comment, I didn't properly handle that. I've proposed a new order, could you take another look? https://code.launchpad.net/~mdeslaur/indicator-power/fix-priorities/+merge/260903
[13:53] <Newww> qengho: On windows dialog box downloads the file on this link -> saves it to a temporary folder -> select the downloaded file.
[13:53] <qengho> Oh. Weird.
[13:55] <Newww> But it is logical and very comfortable. Other programs like Krita allow you to select a file link, but do the same thing, first download, and then inserted into the program.
[13:56] <larsu> hm? Now we're talking about downloading again?
[13:58] <Newww> I mean, Krita itself downloading a file link.
[13:59] <Newww> Although I'm not sure, maybe it makes the dialog box. Then why does not he do it for the web browser?
[14:05] <andyrock> seb128: do you know where I can find the source code of the privacy panel in ucc?
[14:05] <seb128> andyrock, https://code.launchpad.net/activity-log-manager
[14:06] <andyrock> thanks :D
[14:06] <seb128> iirc
[14:10] <popey> willcooke: hey, please add bug 1496414 to your super important list of bugs which must be fixed for 16.04, kthx :)
[14:10] <seb128> lol
[14:11] <seb128> popey, unsure that's easy to solve/worth the effort
[14:11] <seb128> you can use the gnome-screenshot UI instead of the keybinding to workaround it
[14:11] <willcooke> popey, done.  Please leave the money in the usual place.
[14:11] <popey> its a regression introduced with LIM
[14:11] <willcooke> seb128, I've added the rls-w-incoming tag ;)
[14:11] <popey> it _should_ have been fixed releases ago
[14:11] <seb128> willcooke, fair enough, I'm just saying that I bet some money that it's not fixed for the LTS ;-)
[14:12] <popey> working around a default keyboard shortcut because the default keyboard shortcut we ship is broken seems.. broken
[14:12] <seb128> popey, not sure we can call that regression, it was always there with LIM, you disable LIM you are back to what we had
[14:12] <seb128> note that LIM is not default
[14:13] <popey> true, so not a regression, but LIM breaks screenshots, and LIM is on the CD by default
[14:13] <popey> anyway, lets see if someone steps up to fix it
[14:13] <seb128> I doubt it
[14:13] <seb128> but let's see
[14:13] <popey> :(
[14:13] <seb128> out of changing the default keybinding to be e.g shift+printscreen
[14:13] <seb128> but that's a workaround
[14:13] <seb128> if you set to alt it's going to have the issue again
[14:13] <popey> indeed, all workarounds
[14:14] <popey> I suspect it can be fixed by changing the timing for how quickly the titlebar fades back
[14:14] <popey> maybe a few ms difference could fix it
[14:15] <mpt> mdeslaur_, this terminology predates your change, but I can’t judge your proposal because I don’t understand the distinction between “1. discharging items…” “5. batteries” and “7. non-line power”
[14:15] <mpt> Should “batteries” be “fully-charged batteries”?
[14:16] <mpt> And is “non-line power” just a UPS, or does it cover batteries in some situations too?
[14:16] <seb128> popey, changing the animation might mean compromising on what we think is the best visual experience just for a screenshoter bug easy to workaround, doesn't seem a good deal
[14:16] <seb128> we could also delay the screenshot
[14:17] <seb128> but at the price of making it less reactive, which would bug users would want to take a screenshot of a state of something changing
[14:17] <charles> mpt, hello
[14:18]  * charles reads the new comments in the MR
[14:20] <popey> I have zero confidence in a fix to gnome screenshot after I filed gnome bug 684662 3 years ago. :)
[14:22] <sethj> Is there a reason this bug is still set to "new" for the Unity package? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/940603 No comments since 2012, unity projected has it marked as fixed
[14:22] <sethj> s/projected/project. Doesn't seem reproducible either.
[14:22] <seb128> sethj, likely good to be closed
[14:23] <larsu> this blog post worked...
[14:23] <charles> mpt, 'non-line power' is a bad term that mdeslaur_ seems to have gotten from a comment I wrote, it's my fault :)
[14:24] <charles> mpt, iirc, and from looking at the code, it's shorthand for upower 'kinds' that aren't battery or line power, e.g.
[14:24] <seb128> larsu, what blog post?
[14:24] <charles> mpt, keyboard, mouse
[14:25] <larsu> seb128: willcooke's
[14:25] <seb128> larsu, oh :-)
[14:25] <larsu> seems like more bug activity today
[14:25] <seb128> right
[14:26] <charles> mpt, so it mean "everything else after batteries and line power", maybe mdeslaur_ will be kind enough to tweak my comment when he pushes the revision you suggested :-)
[14:26] <mpt> sethj, it’s a side-effect of bug 76416. Basically Unity has some bug reports filed against the project, some against the package, some against both at once. That one was filed against both, and marked fixed for one, never marked fixed for the other.
[14:27] <sethj> mpt, so if I can't reproduce it should I mark it invalid or fix released?
[14:28] <mdeslaur_> charles, mpt: ok, so it looks like "batteries" means "fully charged batteries", and non-line power is "all other devices"
[14:28] <mpt> sethj, so it’s good to look at both bug lists: <https://bugs.launchpad.net/ubuntu/+source/unity> and <https://bugs.launchpad.net/unity>
[14:29] <mpt> If it’s marked fixed for one, it’s almost certainly fixed for the other too, especially if it happened years ago. :-)
[14:29] <mdeslaur_> charles, mpt: actually, "non-line power" would mean "fully charged other devices"
[14:29] <mdeslaur_> I assume if something isn't charging or discharging it's fully-charged...but perhaps that assumption is wropng
[14:31] <sethj> mpt, cool. Thanks for the lists tip, I hadn't thought of that xD
[14:32] <willcooke> sethj, you good to mark that bug as Fix Released?
[14:32] <mdeslaur_> right, it can be "unknown" too
[14:32] <sethj> willcooke, yup, I can't reproduce it, and I have never experienced it either.
[14:33] <willcooke> thanks sethj
[14:33] <sethj> looks like this bug is in the same position: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/977984
[14:34] <mdeslaur_> charles, mpt: "5- batteries that are neither charging nor discharging", "7- all other devices that are neither charging no discharging", "8- Line power"
[14:34] <mpt> sethj, yep. Maybe willcooke can get those bug reports with conflicting states cleaned up as a batch.
[14:35] <sethj> that seems like it would be a good idea.
[14:35] <charles> mdeslaur_, mpt, in meeting, but ^ 5 7 8 sound good (but typo 's/no/not/' on 7)
[14:35] <willcooke> mpt, sethj - good plan
[14:35] <willcooke> I'll add it to my script
[14:36] <willcooke> should be easy enough, once I've worked out why I keep getting " Resource is not bound to any representation, and no media media type was specified."
[14:38] <larsu> that's because the resource is not bound to any representation! duh!!
[14:38] <mpt> willcooke, at my suggestion unity8 switched to tracking bugs on just the package (bug 1364477). Maybe Unity 7 can do the same, unless there’s some SRU-related reason to keep them separate.
[14:39] <willcooke> mpt, I'll look in to it, thanks
[14:41] <mpt> charles, so should it be “7. fully-charged keyboard/mouse”?
[14:42] <mpt> charles, and “8. UPS”?
[14:42] <mdeslaur_> mpt: 7 is unknown, ups, monitor, mouse, keyboard, pda, phone, edia player, tablet and computer
[14:42] <mpt> So what is “line power” then? :-)
[14:42] <mdeslaur_> "line power" means a power supply
[14:43] <mdeslaur_> AC
[14:43] <mdeslaur_> Which I have no idea why we would want to display
[14:45] <mdeslaur_> oh, we don't display it, it's special-case elsewhere
[15:19] <desrt> cute: mount -o bind /home /mnt; mount -o bind /home/desrt /mnt
[15:19] <desrt> what do you think this does?
[15:19] <desrt> the correct answer, of course is "replace the contents of /home with /home/desrt"
[15:20] <desrt> ie: /home/desrt stops existing and /home now contains my homedir, directly
[15:21] <desrt> this is not how i thought bind mounts worked.....
[15:29] <larsu> desrt: what did you expect?
[15:33] <didrocks> I guess he expected to have /mnt containg /home/desrt and having the /home bindmount "shadowed"
[15:33] <didrocks> interesting behavior btw :)
[15:38] <desrt> i didn't expect that playing around with bindmounts instead of /mnt might impact the world outside /mnt ...
[15:38] <desrt> *inside of
[15:38] <pitti> desrt: welcome to the world of having mounts "shared" by default :/
[15:41] <desrt> ya.  this is really strange.
[15:42] <desrt> is this some recent change?
[15:42] <pitti> desrt: with systemd; it was a huge debate back then
[15:42] <desrt> how does systemd have any control over this?
[15:43] <pitti> desrt: it's a kernel default (whether mounts are private or public by default)
[15:43] <desrt> ah
[15:43] <pitti> some sysctl thingy
[15:43] <pitti> and systemd changes it
[15:43] <desrt> this is ... weird
[15:43] <pitti> it broke quite a lot of things back then
[15:44] <pitti> I mean, those fixes were correct in the sense that anyone else could also have flipped that sysctl, but it was still weird
[15:44] <pitti> I had preferred if nspawn or whatever would have configured its mounts public when needed
[15:44] <pitti> but oh well, water under the bridge
[15:44]  * pitti toddles off for making dinner
[15:44] <desrt> pitti: do you know the name of the sysctl?
[15:45] <desrt> not containing 'mount' nor 'bind' as one may expect
[15:45] <pitti> http://cgit.freedesktop.org/systemd/systemd/commit/?id=b3ac5f8cb98757416d8660023d6564a7c411f0a0
[15:45] <pitti> desrt: ^
[15:45] <desrt> thanks
[15:46] <desrt> ah
[15:46] <desrt> mount flag
[15:46] <pitti> one of the most debated changes ever
[15:46] <desrt> ya
[15:46] <desrt> this is a really bad change, imho
[15:46] <desrt> _totally_ unexpected behaviour
[15:46] <pitti> http://lists.freedesktop.org/archives/systemd-devel/2013-February/008558.html
[15:46] <desrt> and specific to the root filesystem only, is _really_ weird
[15:46] <pitti> no, I think it propagates
[15:47] <pitti> to undo it you need --make-rprivate
[15:47] <desrt> ugh
[16:03] <mdeslaur_> mpt, charles: ok, I'm going to put this on hold for a while. Reading the upower source, it looks like the _only_ devices it calculates time remaining for is laptop batteries, and that is likely going away soon.
[16:04] <mpt> mdeslaur_, really? Yay bizarre upstreams
[16:05] <mdeslaur_> mpt: it's calculating the time remaining based on the "energy discharge rate", and since windows doesn't use that value, more and more hardware is coming out with bogus values there
[16:07] <mpt> mdeslaur_, why is that a thing anyway? There’s probably something I don’t understand, but I’d just measure the percentage remaining at time T, and then at time T+n, and calculate the rate from that
[16:07] <mpt> (“just” <http://c2.com/cgi/wiki?JustIsaDangerousWord>)
[16:09] <mdeslaur_> mpt: that may work for a laptop battery, but my mouse for example only has something like three percentages: 92%, 48%, 5%
[16:09] <mpt> haha
[16:09] <mdeslaur_> yeah, yay for hardware
[16:10] <mpt> Yay operating systems that try to work on hardware made by vendors who don’t care
[16:10] <mdeslaur_> hehe, yeah
[16:30] <Laney> I seem to have lost my Firefox launcher icon
[16:31] <Laney> did the .desktop file get renamed or something?
[16:45] <larsu> I lost terminal one recently
[16:46] <Laney> hm, it's happened on both machines
[16:53] <willcooke> hey robert_ancell - how's the travel?
[16:56] <robert_ancell> willcooke, made it to Toronto so must be all good!
[16:56] <willcooke> :)
[16:58] <robert_ancell> willcooke, how is the bug squashing response going?
[16:58] <willcooke> robert_ancell, we had a response
[16:58] <willcooke> :)
[16:58] <willcooke> the first of many, I'm surre
[16:59] <willcooke> *sure
[16:59] <willcooke> robert_ancell, sethj wins the prize
[16:59] <robert_ancell> Most bugs closed?
[16:59] <willcooke> not quite
[17:00] <willcooke> we'll have closed a couple of hundred by the end of the day
[17:00] <willcooke> but mostly old apport crashes
[17:01] <sethj> if I win the prize that's pretty sad as I've only processed 4/5 bugs so far :(
[17:01] <willcooke> sethj, early days
[17:01] <sethj> speaking of that however, I don't see how this is actually a Unity bug: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/971018
[17:01]  * willcooke <- eternal optimist 
[17:01] <sethj> Turning off mouse mouse pointer integration and it all works 100%
[17:02] <sethj> willcooke, lol. Optimism is good :)
[17:03] <willcooke> sethj, right so they're saying that once the mouse leaves the vbox screen then you can't open the launcher
[17:03] <willcooke> I don't think we can do much about that
[17:03]  * willcooke fires up vbox
[17:03] <sethj> willcooke, yeah, basically. It's on Vbox to decide when the pointer is in the VM and when it's in the host, and it chooses host.
[17:04] <sethj> I dunno if that makes it invalid or what though.
[17:05] <willcooke> sethj, go with "Won't Fix"
[17:06] <sethj> kk, thanks.
[17:06] <willcooke> we wont ever get around to improving it, and there are a couple of work-arounds, don't hide the launcher, or use super key or alt-f1
[17:07] <willcooke> sethj, fyi - there is some suggested text on the wiki page:  https://wiki.ubuntu.com/BigDesktopBugScrub
[17:08] <willcooke> I'll add one for "Won't Fix"
[17:09] <didrocks> see you guys!
[17:10] <willcooke> see ya didrocks
[17:10] <Laney> hmm there's no relevant difference in files between the two firefoxen
[17:11] <willcooke> actually sethj - I wonder if Opinion is a better choice.  That way its there to be picked up by anyone else if they want to work on it.
[17:11] <sethj> willcooke, yup! Been using those when applicable. I don't have "won't fix" privs though. Do you want me to add a tag or do you want to do it.?
[17:12] <willcooke> sethj, I'll do it now
[17:12] <sethj> willcooke, oh that's a good idea. I'm sure there are a few things that can be done to optimize it, but it is such an edge case (no pun intended haha) I doubt anything will happen.
[17:12] <willcooke> sethj, yeah
[17:21] <sethj> willcooke, you might want to update the section on apport bugs on the wiki page too, as "won't fix" isn't a priv most users have. Potential ideas are use a tag for that too, or leave those for privileged folks.
[17:22] <willcooke> sethj, all apport bugs should be gone very soon
[17:22] <willcooke> sethj, just running my script against them now
[17:22] <sethj> oh cool. nbd then
[18:11] <willcooke> A.B.C.
[18:11] <willcooke> Always. Be. Closing.
[18:11] <willcooke> Bugs
[18:29] <sethj> hmm, anyone else think this is more of a feature than a bug?
[18:29] <sethj> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1213834
[18:33] <willcooke> hrm
[18:33] <willcooke> Trevinho, what do you think about that one ^^
[18:33] <willcooke> The calc scope isn't installed by default
[18:33] <willcooke> oh, maybe it is
[18:34] <willcooke> could be that searches starting "=" coudl do that
[18:40] <sethj> the scope is installed by default
[18:40] <sethj> = is a good idea
[18:41] <willcooke> I'll mark it as opionon and use another tag to make sure it gets considered
[18:45] <doko> fyi, gdk-pixbuf is broken, and things are uninstallable where it built. see https://launchpad.net/ubuntu/+source/gdk-pixbuf/2.31.7-1
[18:45] <doko> e.g. no openjdk installable
[18:46] <willcooke> thx for the heads up doko
[19:41] <doko> willcooke, I pinged robert_ancell too. anybody looking at this?
[19:41] <willcooke> doko, robert_ancell is at a conference.  I will hook up with seb128 in the morning
[19:41] <robert_ancell> doko, this the gdk-pixbuf issue?
[19:42] <doko> yes, then maybe better to remove the built binaries
[19:47] <doko> willcooke, robert_ancell: now removed. please don't sync and run in the future ;)
[19:54] <charles> mpt, another blow for making 'time remaining' meaningful in indicator-power then :P
[19:55] <robert_ancell> tjaalton, were you thinking of having Xorg 1.19 in 16.04?
[20:40] <Laney> doko: remove it
[20:40] <Laney> and check debian buildds next time :P
[20:41] <doko> Laney, I didn't sync ...
[20:43] <Laney> ok, note to whoever did
[21:36] <tjaalton> robert_ancell: depends on the release schedule, but yeah if doable
[21:36] <robert_ancell> tjaalton, we were discussing it here and end of march is the release date. So that would work out pretty good for us.
[21:36] <tjaalton> actually that's pretty late
[21:37] <tjaalton> because of fglrx
[21:37] <robert_ancell> ?
[21:38] <tjaalton> it takes time for fglrx to catch up
[21:38] <tjaalton> with the video abi
[21:38] <robert_ancell> they release after the X release?
[21:38] <tjaalton> they still don't support 1.18rc
[21:38] <tjaalton> for instance
[21:38] <robert_ancell> tjaalton, would they be motivated to hit 16.04 and be more ready for 1.19?
[21:39] <tjaalton> we've always asked, but it still slips to the last week before release, every time :)
[21:39] <tjaalton> ubuntu release
[21:39] <robert_ancell> right
[21:40] <robert_ancell> That's a bit tight for an LTS...
[21:40] <robert_ancell> We'll have to lie to them and say it's 16.03
[21:41] <tjaalton> of course, if the video abi doesn't change..
[21:41] <tjaalton> then it's a non-issue. but I think it has changed every release
[21:41] <robert_ancell> No-one talked about video changes (mostly glamor and input and general cleanups)
[21:42] <robert_ancell> I guess we hope it doesn't change / ask fglrx nicely and see if that works out.
[21:42] <tjaalton> as long as the abi is set early enough
[21:43] <tjaalton> if it is changed. so first rc by mid-january or so, then put it in a ppa and ask them to fix their shit
[21:44] <tjaalton> leaning towards not bumping mesa to 11.0.x in wily, since it can't use llvm-3.7 so no proper amdgpu support anyway
[21:46] <robert_ancell> tjaalton, oh, it requires an newer llvm?
[21:46] <tjaalton> amdgpu does
[21:46] <robert_ancell> what else requires llvm in Ubuntu, i.e. what stops us bumping that?
[21:47] <tjaalton> llvm-3.7 not building on i386
[21:47] <robert_ancell> :(
[21:47] <tjaalton> and that it's in universe, 3.5 3.6 already in main
[21:47] <tjaalton> so would have to get rid of one
[21:47] <robert_ancell> Problem for next cycle then...
[21:48] <tjaalton> hm, though if mesa switched to 3.7 it would allow dropping 3.6 it seems