[00:07] <asac> ccheney: so the class and main struct seem compatible
[00:08] <asac> so we can do this:
[00:08]  * ccheney looks to see where the problem laid
[00:08] <asac> ccheney: no i see
[00:08] <ccheney> oh ok
[00:08] <asac> one second ;)
[00:08] <asac> the icon stuff needs Private struct
[00:08] <asac> which you cannot break/change
[00:08] <asac> whati think we should do is because Class and main struct are compatible
[00:09] <asac> we just copy the full gtkentry.c and gtkentry.h and name it gtkentryBackported
[00:09] <asac> define a new type gtkentrybackported etc.
[00:09] <asac> and use that in epiphany
[00:09] <asac> that type would just inherit from gtkentry
[00:09] <ccheney> iirc it uses some other newer types along with it might need to do that for those two i guess?
[00:10] <ccheney> i'm not sure what you mean wrt inherit with C :)
[00:10] <ccheney> i'm still pretty new with using glib/gtk so its probably something that they do with macros i suppose?
[00:11] <asac> ccheney: right. the G_DEFINE_YPE Macro specifies a supertype
[00:11] <asac> also you derive the structs like this:
[00:11] <asac> struct _GtkEntryBackport {
[00:11] <asac> GtkEntry parent;
[00:11] <asac> };
[00:11] <asac> and GtkEntryBackportClass {
[00:11] <asac> GtkEntryClass parent_klass;
[00:11] <asac> }
[00:11] <asac> ;
[00:11] <ccheney> ah ok
[00:11] <asac> then you basically put the G_DEFINE_TYPE macro there that says that GTK_TYPE_ENTRY is supertype
[00:12] <asac> and in _init and _class_init you dont do anything
[00:12] <ccheney> i'm going to copy this into the epiphany wiki page so i don't forget anything while working on it tomorrow
[00:12] <asac> err
[00:12] <ccheney> if that is ok?
[00:12] <asac> in _class_init you basically copy what you currently have there
[00:12] <ccheney> rather i just copy it locally
[00:12] <asac> no wiki is fine
[00:12] <ccheney> ok
[00:13] <asac> so _class_init you keep as it is in the copy you created from the new gtkentry
[00:13] <ccheney> ok
[00:14] <asac> ccheney: look at the class_init
[00:14] <asac> function
[00:14] <asac> thats where they bind the functions to the static impls
[00:14] <ccheney> yea i remember seeing that when working on it before
[00:15] <ccheney> i'll try to get it at least partially done tonight after i get something to eat, if i am lucky maybe done by meeting tomorrow :)
[00:16] <asac> ccheney: maybe we can even just first try to copy that entry over
[00:16] <asac> as it is ... rename all the funcs and types
[00:16] <asac> and see if that is enough ... if all uses of that are redirected in epiphany
[00:17] <asac> for the other symbols:
[00:17] <asac> gtk_show_uri -> shouldnt be a problem
[00:17] <asac> gtk_status_icon_set_tooltip_text -> we can survive without that?
[00:17] <asac> gtk_activatable_get_type -> guess we need this type backported
[00:17] <ccheney> ok
[00:18] <asac> gdk_app_launch_context_* -> feels like thats confined and can be backported or even added to gtk
[00:18] <asac> if its imliar to the thread thing
[00:18] <asac> from glib
[00:18] <ccheney> yea probably so
[00:18] <asac> let me check something
[00:18] <asac> ok for gtk_entry we have icon and progress
[00:18] <ccheney> from what i remember the context stuff seemed pretty easy
[00:19] <asac> lib/widgets/ephy-location-entry.c lib/widgets/ephy-search-entry.c:
[00:19] <asac> those are the places for icon
[00:19] <ccheney> yea
[00:19] <ccheney> iirc there is one other place but i forgot the filename
[00:20] <ccheney> maybe was src/ephy-location-action.c
[00:21] <ccheney> yea it refers to GtkEntry at least, not sure if it used the new functions though
[00:22] <ccheney> oh no i think it wasn't that but src/ephy-window.c
[00:22] <ccheney> i see where i commented out the +// #include "../lib/gtk-gtkentry.h"
[00:22] <asac> hmm. problem is you did abunch of stuff
[00:22] <ccheney> which i had done when trying to do the initial func backport
[00:22] <asac> so i dont even see the original ;)
[00:22] <asac> let me revert everything in that tree
[00:22] <ccheney> oh :-\
[00:23] <ccheney> ok
[00:27] <asac> ccheney: so yeah. simple approach would be to copy GtkEntry as EphyGtkEntry ... rename all gtk_entry to ephy_gtk_entry and all GtkEntry to EphyGtkEntry and GTK_ENTRY to EPHY_GTK_ENTRY etc.
[00:27] <asac> in the copied source files
[00:27] <asac> and then fix the few places where they say: gtk_entry_new() -> ephy_gtk_entry_new()
[00:27] <asac> and of course all the other gtk_entry.* func
[00:27] <asac> s
[00:28] <ccheney> ok
[00:29] <asac> feels like a plan
[00:29] <asac> i dont think it passes gtk entries to different libs etc.
[00:29] <asac> so should be fine
[00:29] <ccheney> ok will try to implement it tonight and let you know how it goes tomorrow :)
[00:30] <asac> yeah. just copy over ... and sed ;)
[00:30] <asac> well. first see if it builds ;)
[00:30] <asac> who knows what that thing pulls in
[00:30] <ccheney> heh yea
[00:31] <ccheney> iirc it pulls a few other bits in but not too much
[00:31] <asac> the gtkentry.c file?
[00:31] <ccheney> i can probably get away by doing something similar with the other bits if they have problems
[00:31] <ccheney> yea
[00:32] <asac> would be fun if gtk code is more portable than ephy ;)
[00:32] <ccheney> i think there is a glib icon thing as well it messes with but i can remember for certain
[00:32] <ccheney> er can't
[00:35] <BUGabundo> I totally forgot what was that FF about:config entry to turn off process separation
[00:35]  * ccheney bbl, will check backlog when i get back :)
[00:35] <BUGabundo> can anyone recall me ?
[00:38] <asac> BUGabundo: i remember you. yes.
[00:39] <BUGabundo> duh
[00:39] <asac> BUGabundo: searhc for dom.ipc
[00:39] <asac> or something
[00:39] <asac> or ipc
[00:39] <BUGabundo> help me out :D
[00:39] <asac> plugins
[00:39] <BUGabundo> thanks
[00:39] <BUGabundo> its already false :(
[00:39] <BUGabundo> so why is this crashing!!
[00:39] <BUGabundo> grrr
[00:39] <BUGabundo> [NoScript] document is null while processing JS redirects
[00:39] <BUGabundo> ** (firefox-3.7:8620): WARNING **: Serious fd usage error 14
[00:39] <BUGabundo> ** (firefox-3.7:8620): WARNING **: Serious fd usage error 12
[00:40] <asac> noscript ;)?
[00:40] <BUGabundo> maybe
[00:40] <BUGabundo> ff 3.7
[00:47] <asac> bug<PHONE_NUMBER>41 522254
[00:47] <asac> bug<PHONE_NUMBER>54
[00:47] <asac> bug 522254
[00:54] <bdrung_> asac: FF in lucid failed to start. rm -rf ~/.mozilla will let it start once.
[00:55] <asac> bdrung_: global extensions cause this (some)
[00:55] <asac> if you can figure out whats it, i would be grateful
[00:55] <asac> e.g. waht extension
[00:56] <bdrung_> asac: "firefox -g" does not work: "/usr/lib/firefox-3.6/firefox": not in executable format: file format not recognised
[00:56] <asac> i also suspect it has to do with the plenty of levels of links we have or with the new /usr/lib/mozilla location
[00:56] <asac> hmm
[00:56] <asac> thats a bug
[00:56] <asac> run /usr/lib/firefox-*/run-mozilla.sh /usr/bin/gdm /usr/lib/firefox-*/firefox-bin
[00:56] <asac> err gdb ;)
[00:58] <bdrung_> asac: i have these packages installed: xul-ext-adblock-plus, xul-ext-notify, xul-ext-pwdhash, xul-ext-mozgest
[00:58] <asac> yes. one of those is it
[00:58] <asac> try -safe-mode
[00:58] <asac> and then enable one by one
[00:59] <asac> i would suspect mozgest
[00:59] <asac> it has something to do with xpt
[00:59] <asac> so if an extension defines its own interfaces
[00:59] <bdrung_> asac: running with gdb, it gives me: "Program exited with code 01."
[00:59] <asac> if an extension without a .xpt file causes this, it would invalidate my theory
[00:59] <asac> bdrung_: yeah
[01:00] <asac> it just ends ;)
[01:00] <asac> needs some serious debugging ;)
[01:01] <bdrung_> asac: i used -safe-mode and enabled them step-by-step. but it still restarts without problems.
[01:02] <asac> bdrung_: try twice ;)
[01:02] <asac> you need to restart twice for this to kick in
[01:02] <asac> first time enable will work
[01:02] <bdrung_> there must be a difference between restarting FF and closing+reopen it
[01:02] <asac> no
[01:02] <asac> its just about updating extension cache
[01:02] <asac> in the run where that is updated it works. in the next it doesnt
[01:03] <asac> at least the bug i saw showed that behaviour
[01:05] <bdrung_> asac: i checked it twice and your guess was correct: it is mozgest
[01:07] <bdrung_> asac: mozgest contains /usr/share/xul-ext-mozgest/components/mglMouseService.xpt
[01:10] <asac>  so yeah... we should check whether its the new locatoin
[01:10] <asac> maybe by copying the bits to FIREFOX/extensions
[01:10] <asac> moving rather
[01:10] <asac> if its not the new location ... upstream bug i guess
[01:10] <asac> unless i find to debug it
[01:10] <asac> which probably has to happen to fix this for lucid :(
[01:13] <chrisccoulson> asac - so, do you have some thoughts about issues like bug 531583? (it seems to be similar to the issue you're talking about)
[01:13] <chrisccoulson> bryce asked me if i could take a look at that
[01:14] <asac> chrisccoulson: thats the issue
[01:14] <asac> no ideas besides from what i said above
[01:14] <asac> needs debugging ... if reproducible with upstream builds we might get help from there
[01:14] <chrisccoulson> what i found is that firefox seems to have an issue specifically with the sym-links (but you might have already figured that out)
[01:15] <asac> chrisccoulson: thats what i asked bdrung to test
[01:15] <asac> e.g. unpack directly in FIREFOX/extensions
[01:15] <asac> rather than having the links in /usr/lib/mozilla/...
[01:15] <asac> so its the symlinks?
[01:15] <chrisccoulson> yeah, if i unpack directly, then it works fine
[01:15] <chrisccoulson> if i symlink, then it breaks
[01:15] <asac> chrisccoulson: bug still not writable?
[01:15] <chrisccoulson> and that applies in my home folder too
[01:15] <asac> hmm
[01:16] <asac> let me check something
[01:16] <chrisccoulson> but, other than that, i'm a little bit stuck ;)
[01:16] <bdrung_> asac: xpt files are made from what?
[01:17] <bdrung_> what does they contain?
[01:17] <asac> bdrung_: do you have a broken profile?
[01:17] <asac> can you paste compreg.dat?
[01:17] <asac> (from a profile that doesnt start)
[01:17] <asac> bdrung_: its xpcom interface description
[01:17] <asac> produced from an .idl
[01:17] <asac> or more than one etc.
[01:18] <asac> bdrung_: also please verify what chrisccoulson said ... e.g. that not using symlinks works
[01:18] <asac> but get me a compreg.dat first ;))
[01:19] <bdrung_> asac: i have the solution: the xpt file is non-free and needs to be removed from the source. ;)
[01:20] <asac> thats indeed a bug
[01:20] <asac> usually it should be produced during build
[01:20] <asac> but that wont help here i think
[01:20] <bdrung_> asac: removing this file works, because we removed the .so files (no source for them)
[01:21] <asac> in this case yes.
[01:21] <asac> get me a compreg.dat please of broken ;)
[01:21] <bdrung_> i'll downgrade the package and create the file for you.
[01:21] <asac> cool
[01:23] <asac> also the absent of a .so doesnt necessarily mean the .xpt is useless. might also be a .js implementing the interface that then can be called through xpcom (from js or C++)
[01:24] <bdrung_> pastebinit is buggy
[01:25] <bdrung_> asac: http://pastebin.com/2F9uLM6S
[01:26] <asac> bdrung_: and xpti.dat
[01:26] <bdrung_> asac: http://pastebin.com/KXSXcCWs
[01:27] <asac> {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
[01:27] <asac> thats mozgest?
[01:27] <asac> bdrung_: ?
[01:28] <asac> adblock it seems
[01:28] <bdrung_> that's adblock-plus
[01:29] <asac> so my guess is that it does a stupid abspath somewhere
[01:30] <asac> (or not) then doesnt see the file in the the xpti.dat and gives up
[01:31] <bdrung_> asac: btw, what's the status of getting the font rendering fixed?
[01:53] <asac> in xpcom/reflect/xptinfo/src/xptiInterfaceInfoManager.cpp
[01:53] <asac> drop
[01:53] <asac> +            // nsIFile::Equals basically compares path strings so normalize
[01:53] <asac>      4.8 +            // before the comparison.
[01:53] <asac>      4.9 +            parent->Normalize();
[01:53] <asac>     4.10 +            current->Normalize();
[01:53] <asac> those lines
[01:53] <asac> and see if that helps
[01:53] <asac> for the xpt thing
[01:54] <asac> otherwise we might want to try to Normalize in FindDirectory in xptiWorkingSet.cpp
[01:55] <asac> font rendenering ::: needs debugging
[01:55] <asac> upstream seems not to care. didnt get a confirm whether its a problem on redhat too with upstream builds
[01:55] <asac> if fedora has the same, we can escalate
[01:55] <asac> otherwise we need to do it on our own
[01:56] <asac> bdrung_: chrisccoulson: ^^
[01:56] <asac> (thats a blind guess)
[01:56] <asac> (the de-normalizing)
[01:58] <masterme120> Hello, there's something I've always wondered about the linux version of firefox:
[01:58] <masterme120> why doe the open with alternate program dialog make you find the actual binary instead of just having a custom command
[01:59] <bdrung_> asac: i will try this, but compiling may take a while
[02:01] <asac> masterme120: gtk doesnt offer a app chooser
[02:01] <asac> so either firefox has to reinvent its own
[02:02] <asac> the one from nautilus looks promissing but would need to get promoted to gtk in some what
[02:02] <asac> way
[02:02] <masterme120> oh
[02:03] <asac> even if firefox would be willing to use gnome stuff ... nautilus chooser is not exposed in any API
[02:03] <asac> so someone would need to rip that out
[02:04] <bdrung_> asac: igitt; a tarball in tarball. can you give me a debdiff for testing?
[02:04] <bdrung_> i will test it then tomorrow
[02:04]  * bdrung_ will go to bed now.
[02:06] <asac> extract tarball ... create diff, dump in debian/patches and series
[02:06] <asac> build
[02:07] <bdrung_> i am too tired for that
[02:07] <asac> i am not less tired. <5h till wake up ;)
[02:07] <asac> off
[02:07] <asac> 'night
[08:54] <BUGabundo_remote> \0
[10:12] <asac> hi
[10:38] <stefanlsd> heys
[10:38] <stefanlsd> is xulrunner-dev 1.9.2 still expected in lucid?
[10:39] <directhex> stefanlsd, sure, at some point within the next 18 months...
[10:40] <stefanlsd> so not at release i take it
[10:49] <directhex> stefanlsd, good question. i've been told "imminently" for over a month now afaik
[10:51] <asac> directhex: xul 1.9.2?
[10:51] <asac> or fonts?
[11:01] <directhex> asac, xulrunner-dev 1.9.2.
[11:03] <asac> hmm
[11:03] <asac> i think i saw the new button order for the first time now
[11:03] <asac> thats really odd ;)
[11:03]  * asac tries to get used to it
[11:04] <asac> chrisccoulson: can you check with micahg on the xul 1.9.2 stuff and help getting that in the archive?
[11:04] <chrisccoulson> asac - no worries. last time i asked, he had a build issue with fennec
[11:05] <chrisccoulson> do you know if he got that sorted?
[11:05] <asac> i had hoped for a few more ports first, but we shouldnt stress the good will of release team too much ;)
[11:05] <chrisccoulson> (most of my day yesterday was taken up by openjdk)
[11:05] <asac> chrisccoulson: i think he sorted the prism problem ... which might also have been the fennec problem
[11:05] <asac> chrisccoulson: openjdk now working?
[11:06] <asac> not sure if he committed the stuff yet though
[11:06] <chrisccoulson> asac - it would be good to get all the stuff which is seeded done before the beta freeze
[11:06] <asac> yes
[11:06] <asac> thats why i think we should upload _now_ ;)
[11:07] <asac> so i think the build system fix is still missing
[11:07] <chrisccoulson> asac - do you know what time micahg is around?
[11:07] <asac> he is more around than not ;)
[11:07] <chrisccoulson> openjdk is not working yet btw, but that's not a xulrunner issue
[11:07] <chrisccoulson> it's due to a change in llvm
[11:08] <asac> hmm. so openjdk doesnt ubild at all atm?
[11:08] <asac> even in archive? didnt you say doko uploaded something?
[11:08] <chrisccoulson> asac - yeah, doko uploaded openjdk, and then a new version of llvm
[11:08] <chrisccoulson> but the current openjdk version built against the old llvm
[11:08] <chrisccoulson> it doesn't build with the new one
[11:09] <asac> sigh
[11:09] <asac> i assume he knows/deals with it?
[11:09] <chrisccoulson> i spent quite a few hours yesterday trying to track that down, i could probably do with some help from doko
[11:09] <asac> i wouldnt bother. he will fix it
[11:09] <chrisccoulson> he seemed to be quite confused about the error message when i mentioned it to him yesterday
[11:09] <asac> go for the other fruits ;)
[11:10] <chrisccoulson> yeah, will do :)
[11:10] <asac> just ensure he is on it ;)
[11:10] <asac> ... file a RC bug if there is none yet
[11:10] <chrisccoulson> did you get any where with the firefox failing to start issue since last night?
[11:10] <asac> chrisccoulson: i suggested a patch
[11:10] <asac> asked you or bdrung to test ;)
[11:10] <directhex> i already uploaded monodevelop-moonlight, so that's uninstallable right now
[11:10] <asac> 02:53 < asac> in xpcom/reflect/xptinfo/src/xptiInterfaceInfoManager.cpp
[11:10] <chrisccoulson> ah, i probably should check the scrollback
[11:11] <asac> 02:53 < asac> drop
[11:11] <asac> 02:53 < asac> +            // nsIFile::Equals basically compares path strings so normalize
[11:11] <asac> 02:53 < asac>      4.8 +            // before the comparison.
[11:11] <asac> 02:53 < asac>      4.9 +            parent->Normalize();
[11:11] <asac> 02:53 < asac>     4.10 +            current->Normalize();
[11:11] <asac> 02:53 < asac> those lines
[11:11] <asac> 02:53 < asac> and see if that helps
[11:11] <asac> 02:53 < asac> for the xpt thing
[11:11] <asac> was easy enough for me to repaste
[11:11] <asac> 02:54 < asac> otherwise we might want to try to Normalize in FindDirectory in xptiWorkingSet.cpp
[11:11] <asac> directhex: good
[11:11] <asac> chrisccoulson: no its fine ;)
[11:11] <asac> so two approaches i can imagine
[11:11] <chrisccoulson> awesome, i will try that shortly
[11:11] <asac> dropping Normalize there or adding Normalize in WorkingSet FindDirectofry (or maybe some other places)
[11:12] <asac> makes somewhat sense, because that was landed in Jul 2009 ... probably after the 1.9.1 cut off
[11:12] <asac> but let me double check ;)
[11:12] <asac> so a good way to check source and cross reference is: http://mxr.mozilla.org/
[11:12] <asac> chrisccoulson: ^^
[11:12] <asac> there you can also find blame if you in a source file etc.
[11:12] <directhex> good thing there's months before release, otherwise the window for testing & bug-fixing all the 1.9.2 rdeps might be considered really short.
[11:12] <chrisccoulson> asac - thanks
[11:13] <asac> directhex: right. plan is to kick stuff that doesnt make the cut out of the archive
[11:13] <asac> kind of evolutionary cleanup
[11:13] <asac> in the future we need to be able to do such porting swiftly
[11:13] <asac> as we need to upgrade to .3 .4 etc. every 6 month or so
[11:13] <asac> as a security/stability update
[11:14] <asac> chrisccoulson: good ;)
[11:14] <asac> http://mxr.mozilla.org/mozilla1.9.1/source/xpcom/reflect/xptinfo/src/xptiInterfaceInfoManager.cpp
[11:14] <asac> that suggests that that code wasnt on the 1.9.1 branch ;)
[11:14] <asac> so probably is a good lead ;)
[11:16] <chrisccoulson> asac - i've also been assigned a work item for looking at extensions to clean from the archive
[11:16] <asac> right
[11:16] <asac> important task
[11:16] <chrisccoulson> i'm not sure if you've got any special requirements for any that you would like to remain
[11:17] <asac> chrisccoulson: check popcon as a first
[11:17] <asac> chrisccoulson: also extensions with native components should stay
[11:17] <chrisccoulson> i compiled a list of source packages providing extensions at https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel/extension-list yesterday
[11:17] <asac> as those are not available for all archs in addons.mozilla.org (amo)
[11:17] <chrisccoulson> yeah, i didn't think of checking popcon actually, that's quite a good idea
[11:18] <asac> so out of head i would guess: all in main ;)
[11:18] <asac> adblock-plus
[11:18] <asac> all-in-one-sidebar
[11:18] <asac> bindwood
[11:18] <asac> bugmail-extension
[11:18] <asac> firebug
[11:18] <asac> firefox-launchpad-plugin
[11:18] <asac> flashblock
[11:18] <asac> flashgot
[11:18] <asac> gears
[11:18] <asac> greasemonkey
[11:18] <asac> mozgest
[11:19] <asac> notify-extension
[11:19] <asac> mozilla-noscript
[11:19] <directhex> i thought gears was EOL
[11:19] <asac> if it still works its good stuff
[11:19] <asac> its EOL in chromium ... where they dropped it without replacement ;)
[11:20] <chrisccoulson> cool, i will try and spend some time going through this list today anyway
[11:20] <asac> yeah
[11:20] <asac> cross check that with popularity
[11:20] <asac> chrisccoulson: btw, there have been quite a few coming
[11:20] <asac> from debian in lucid named xul-ext-*
[11:20] <asac> those seem to be not in your list ... not sure why
[11:20] <asac> (maybe they us that prefix for binaries only)
[11:24] <bdrung> chrisccoulson: can you make this scriptable?
[11:25] <chrisccoulson> asac - yeah, those names are binary only (the list only has source packages providing extensions)
[11:26] <chrisccoulson> bdrung - i don't see why i couldn't make it scriptable :-)
[11:26] <chrisccoulson> if there are any that i've missed off the list, please feel free to add them
[11:27] <bdrung> chrisccoulson: it would be nice, if the list can be updated via a script - otherwise it will get outdated very soon.
[11:27] <chrisccoulson> yeah, that's a good point
[11:31] <asac> the new policy permits that
[11:31] <asac> because we have special headers
[11:31] <asac> and even xul-ext* prefix
[11:31] <asac> for now we have to maintain it through pain
[11:31] <asac> and maybe we should write a pool/ grep
[11:32] <asac> checking for install.rdf or something
[13:16] <bdrung> asac: grabbing all packages build depending on mozilla-devscripts will catch most of them
[13:17] <asac> right, but not all
[13:17] <bdrung> yes
[13:17] <bdrung> asac: pool grep would be a good idea.
[13:36] <chrisccoulson> asac - so, if we want to start the xulrunner 1.9.2 transition today, would you mind doing the 1.9.1 upload to not ship xulrunner-dev any more?
[13:36] <chrisccoulson> i think i can do the initial 1.9.2 upload
[13:39] <asac> chrisccoulson: yes. we should do that
[13:40] <asac> chrisccoulson: we have to set replaces anyway, so we can remove the file in a later upload
[13:40] <asac> err ;)
[13:40] <asac> scratch that
[13:40] <asac> we just have to remember to upload ;)
[13:40] <asac> next upload would fail to upload
[13:41] <asac> but yes, we should drop it from bzr right away
[13:43] <chrisccoulson> asac - it's already dropped in bzr (http://bazaar.launchpad.net/~mozillateam/xulrunner/xulrunner-1.9.1.head/revision/528)
[13:52] <asac> good ;)
[13:52] <asac> so just an upload. but that can wait till next update round
[13:52] <asac> if thats before the releaes ;)
[14:55] <bdrung> asac: my kvm instance went out of space. 10 GB was not enough.
[14:55] <asac> lol
[14:55] <directhex> moz needs 10 gig?
[14:55] <asac> for ffox  you need 4 or more ,)
[14:55] <asac> havent checked current space recently
[14:55] <bdrung> directhex: my kvm has 10 gig.
[14:57] <mahfouz> did I hear somebody say that thunder gets its own repo?
[14:57] <bdrung_> directhex: i had 2.5 gig free before compiling
[14:57] <bdrung_> asac: that's even more that eclipse needs.
[14:57] <directhex> bdrung_, tried OOo?
[14:57] <bdrung_> directhex: nope. i compiled eclipse often enough
[16:30] <chrisccoulson> asac - xulrunner-1.9.2 is in NEW now
[16:31] <micahg> ?
[16:31] <micahg> what did I miss?
[16:31] <chrisccoulson> hey micahg
[16:32] <chrisccoulson> we're going to start the transition in the archive quite soon
[16:32] <micahg> chrisccoulson: it doesn't have my latest changes
[16:32] <chrisccoulson> ah, where are those?
[16:33]  * micahg wonders why no one asked...
[16:33] <micahg> chrisccoulson: I was finishing up locally waiting for the last piece to be approved by asac before pushing to branch
[16:34] <asac> chrisccoulson: did you commit stuff?
[16:34] <asac> merge request?
[16:34] <micahg> asac: he proposed a merge...
[16:34] <asac> ok
[16:35] <chrisccoulson> yeah, i just did that a few moments ago
[16:35] <micahg> asac: should I make my last few fixes ubuntu2 and have him respin or do you want to delete from NEW and try ubuntu1 again?
[16:35] <micahg> asac: it's not even tagged
[16:36] <directhex> (please pull latest moon update from https://launchpad.net/~moonlight-team/+archive/skunkworks/+packages into staging PPA)
[16:36] <asac> ok.
[16:36] <micahg> directhex: I'll take care of that
[16:36] <micahg> directhex: after it builds ;)
[16:36] <asac> micahg: lets make ubuntu2
[16:37] <asac> we can upload once its in
[16:37] <asac> micahg: please review his merge and merge it
[16:37] <asac> for release
[16:37] <directhex> micahg, it'll build. it's the same thing as last time, but with something we were carrying as a patch merged
[16:37] <micahg> asac: should I just tag his change as release?
[16:37] <BUGabundo_remote> [reed]: ping
[16:37] <asac> chrisccoulson: usually you should wait for a merge approved before uploading ;) ... otherwise review doesnt make sense :)
[16:37] <asac> but ok as its now
[16:37] <BUGabundo_remote> [reed]: watchi this page: https://www.paraescolar.pt/registo/
[16:37] <BUGabundo_remote> firefox shows NOTHING
[16:37] <micahg> chrisccoulson: you should also ask whoever's working on it if there are any last changes ;)
[16:37] <BUGabundo_remote> not even a single error
[16:38] <asac> micahg: i think you can just push (not merge) what he did if he used proper changelog format
[16:38] <BUGabundo_remote> chromium loads it fine
[16:38] <chrisccoulson> yeah, sorry ;)
[16:38] <BUGabundo_remote> and IE shows cert error and allows user to load content
[16:38] <chrisccoulson> i thought it was tagged though (it's tagged with 1.9.2+nobinonly-0ubuntu1 isn't it?)
[16:38] <asac> right. thats why we should push rather than merge
[16:38] <asac> so the tag is on a top level commit
[16:39] <micahg> asac: so pull his branch than push to ,head?
[16:39] <chrisccoulson> oh, do the tags not show on the top-level commit?
[16:39] <micahg> tags don't show up in diffs I guess
[16:40] <micahg> yes, I see the tag
[16:41] <micahg> k
[16:41] <micahg> pushing
[16:41] <asac> micahg: yes
[16:41] <micahg> done
[16:41] <asac> chrisccoulson: if you merge, then not
[16:42] <asac> chrisccoulson: so usually releases get tagged by whoever does the release
[16:42] <asac> merge
[16:42] <chrisccoulson> yeah, that's normally how i do it
[16:42] <asac> ok now we need to get someone getting this through new
[16:42]  * asac thinks we should have filed a FFe
[16:43]  * micahg looks who is archive admin du jour
[16:43] <chrisccoulson> do we need a FFe? this has been planned for some time now hasn't it?
[16:43] <asac> yeah
[16:43] <asac> but i think planned doesnt replace it
[16:43] <asac> but lets see how well it goes
[16:43] <asac> probably depends on the archive admin
[16:43] <micahg> asac: riddell is the archive admin du jour
[16:43] <chrisccoulson> ok, no problem
[16:43] <asac> most likely he will process it today
[16:43] <asac> anymore
[16:43] <chrisccoulson> Riddell is in a team meeting right now
[16:44] <chrisccoulson> (where i probably should be :) )
[16:44]  * micahg should be in a team meeting as weel :)
[16:44] <fta> asac, hi, i didn't change it since last time, you wanted another format or something
[16:44] <micahg> asac: is my mozilla-devscripts idea ok for the clean target?
[16:46] <asac> fta: the copyright? we need it to be complete (with all the license texts etc.)
[16:46] <asac> i dont care about the format if everything is in there
[16:46] <fta> asac, as it's quite complex (a collection of 3 repos, one containing a tarball), i didn't want to drop the comments
[16:46] <asac> new format makes archive admins not look that much though ;)
[16:46] <asac> right
[16:46] <fta> asac, http://paste.ubuntu.com/391896/
[16:46] <asac> if you need complex, just do it different
[17:16] <asac> fta: ok
[17:16] <asac> in my book it looks fine
[17:16] <micahg> asac: what about my mozilla-devscripts merge?
[17:16] <asac> file a FFe bug and i will make this going
[17:16] <asac> micahg: whats the diff?
[17:16] <asac> if its just adding the dirs/files we adde to build system then it should be fine
[17:17] <micahg> asac: http://pastebin.com/YUCbsCZg
[17:17] <asac> ok i informed riddell that there is xul 1.9.2 in new
[17:17] <asac> not sure if he will get to it
[17:17] <asac> micahg: that looks fine i think
[17:17] <asac> in the end we should keep this stuff in one place
[17:18] <asac> most likely xulapp.mk should go to xulrunner-dev
[17:18] <micahg> asac: k, does it need to go through debian?
[17:18] <asac> so we have build system production and build system stripping at same plce
[17:18] <micahg> asac: yeah, that's what I was thinking
[17:18] <micahg> asac: I can move it for ubuntu2
[17:18] <asac> micahg: we can upload to debian
[17:18] <asac> and direclty request a sync
[17:18] <asac> bdrung might volunteer to assist you with that ;)
[17:19] <asac> if he refuses we can put that in ubuntu for now
[17:19] <micahg> asac: if I move it for ubuntu2, we don't need to update devscripts :)
[17:19] <asac> how would you do it? replaces: ?
[17:19] <asac> e.g. currently the rules stuff looks at the mozilla-descript path
[17:19] <asac> i thini we need to touch it anyway
[17:19] <asac> lets fix it lik you suggested for now
[17:19] <micahg> asac: no, I'd just update the packages that use it to reference it in xulrunner-devel-1.9.2/xulapp.mk
[17:20] <asac> and consolidate the whole monzilla-devscript after this cycle/&for next cycle
[17:20] <micahg> k
[17:20] <micahg> I'll merge my change in then and ping bdrung later :)
[17:20] <asac> micahg: right, but we dont want to just change stuff and break others that might use it ;)
[17:20] <asac> at least not without deprecating it for a bit
[17:20] <asac> micahg: great
[17:20] <asac> micahg: also push harder on the porting list ;)
[17:20] <micahg> asac: well, the old one wouldn't have to go away right away
[17:20] <asac> we have xul 1.9.2 now in NEW
[17:21] <asac> once it enters we should get as many stuff as we have in before beta
[17:21] <micahg> asac: I'll start fixing up the patches then so they're archive ready...
[17:21] <asac> cool
[17:21]  * micahg was taking the down and dirty approach to patching before :)
[17:22] <micahg> I'll try to get up to 30 packages by monday
[17:22] <micahg> once I have the debdiff, should I file the bugs with patches?
[17:23] <chrisccoulson> oh, xulrunner 192 is accepted now
[17:23] <chrisccoulson> nice
[17:23] <chrisccoulson> asac - we need to promote it to main don't we?
[17:24] <micahg> directhex: copied
[17:25] <asac> chrisccoulson: heh. so doing two MIRs for riddell seemed to have accellerated this ;)
[17:25] <chrisccoulson> asac - thanks :)
[17:25] <asac> well. we need to promote it when we upload stuff in main
[17:25] <asac> but thats a non deal
[17:25] <asac> and usually happens without MIR
[17:26] <micahg> asac: so, should I file bugs with debdiffs for the porting work?
[17:26] <asac> micahg: if they are ready in ppa i can just sponsor stuff from there
[17:26] <asac> maybe removing the ~...
[17:26] <asac> no need to file bug
[17:26] <asac> s
[17:26] <asac> micahg: however, bugs might help you to track work etc.
[17:26] <chrisccoulson> i can help out with sponsoring too
[17:26] <asac> and regressions
[17:26] <asac> so lets file bugs for each upload
[17:27] <chrisccoulson> i'll sponsor anything in universe and ubuntu-desktop package sets
[17:27] <micahg> asac: k, I'll ping chrisccoulson for uploads?
[17:27] <asac> chrisccoulson: yep. thats the idea ;) ... just keep micah the changelog owner to give him credits ;)
[17:27] <chrisccoulson> yeah, no problem :)
[17:27] <asac> micahg: just ping us both and whoever is there can review and sponsor
[17:27] <asac> micahg: please test the apps before requesting
[17:27] <asac> e.g. not just building
[17:27] <micahg> asac: some of the apps I have no idea how they work, but I'll test the ones I know
[17:27] <asac> also run an strace -eopen -f APP ... so you can see that it really loads the bits from xulrunner 1.9.2
[17:27] <asac> (if you are unsure)
[17:28] <asac> micahg: well. often its just starting
[17:28] <asac> for plugins its good to check if they show up in firefox browser
[17:28] <micahg> asac: some of the stuff is libraries
[17:28] <asac> and dont kill it when loading ;)
[17:28] <micahg> asac: I'll create a Lucid VM for this
[17:28] <asac> micahg: for libraries test the apps that use those libs
[17:28] <asac> VM works, or upgrade completely
[17:28] <asac> we are close to beta ;)
[17:28] <micahg> asac: I'm assuming as soon as an app is ready to file the bug and get it in
[17:29] <asac> micahg: you can also ask chrisccoulson to help verifying apps/libs or me
[17:29] <asac> if you are unsure
[17:29] <asac> micahg: yes, do that
[17:29] <micahg> asac: k, great
[17:29] <micahg> chrisccoulson: I should have ubuntu2 for xulrunner ready as soon as I get to $WORK, so in a couple of hours
[17:31] <micahg> asac: 3 insecure apps for Lucid left (gears, gluezilla, and google-gadgets)...should I prepare debdiffs for all the regular apps first or finish porting these after I have debdiffs for the other insecure apps?
[17:35] <micahg> asac: also TB3 is ready for upload :)
[17:35]  * micahg will bbi 10 min
[17:36] <chrisccoulson> micahg - thanks. i probably won't be able to upload xulrunner once it is in main though
[17:37] <chrisccoulson> which is a bit of a pain ;)
[17:44] <chrisccoulson> asac / micahg - i will upload yelp shortly (once 192 is built)
[17:53] <micahg> chrisccoulson: I thought yelp was ported to webkit
[17:53] <chrisccoulson> micahg - the webkit port was never really official, and isn't well maintained
[17:53] <chrisccoulson> so we dropped it this cycle
[17:54] <micahg> chrisccoulson: k
[17:54] <chrisccoulson> it will most likely be ported to webkit eventually, but not this cycle
[17:54] <micahg> chrisccoulson: k, I'll be back in a little over an hour hopefully with ubuntu2 of xul192 ready :)
[17:54] <chrisccoulson> cool, thanks
[18:14] <asac> chrisccoulson: i think it needs some bin NEW too ;)
[18:14] <asac> chrisccoulson: we dropped yelp?
[18:14] <asac> webkit?
[18:14] <asac> no
[18:14] <asac> thats bad
[18:15] <asac> is there really a bad blocker on that?
[18:15] <asac> me feels like going to desktop channel and kicking around ;)
[18:15] <asac> we talke about getting rid of that for ages
[18:15] <asac> well. if it was straight forward to port its fine ;)
[18:15] <asac> just ranting
[18:16] <chrisccoulson> asac - yelp is straightforward
[18:16] <chrisccoulson> i built it here already a few days ago
[18:17] <chrisccoulson> the webkit branch is quite outdated upstream, and i think there was another issue which required updating yelp to 2.29.x a couple of weeks back
[18:18] <asac> still gnome is inconsistent
[18:18] <asac> they want to get away from gecko -> do it ;)
[18:18] <asac> or dont do it
[18:18] <asac> i maen ... because they said they dont want it all efforts to improve the gecko embedding situation basically were dropped
[18:18] <asac> anyway ;)
[18:19] <asac> if its fine its fine
[18:19] <asac> we wont be able to get rid of it it seems :)
[18:19] <chrisccoulson> asac - yeah, i'm not sure who drove the efforts for porting yelp
[18:19] <chrisccoulson> but it seems like they're not active on that anymore
[18:19] <asac> so gecko is still an official dependency of gnome as of 10.04?
[18:19] <chrisccoulson> and upstream don't officially support the webkit port either
[18:19] <chrisccoulson> which makes it difficult for forwarding bugs
[18:20] <chrisccoulson> asac - yeah, i assume it must be still
[18:20] <asac> maybe they dont even know ... wouldnt be that shocked ;)
[18:20] <chrisccoulson> heh ;)
[18:20] <asac> i mean: everytime they ask they say: we are going away
[18:20] <asac> ... this cycle
[18:21] <asac> if they said: no, we might not be able to do it one could check out the new embedding wrapper API from mozilla
[18:21] <asac> and work with them to get that going rather than having this gtkmozembed stuff for ages
[18:21] <asac> but i was told: dont put effort in it. its decided that its dead ;)
[18:27] <directhex>  Successfully built on thallium (virtual)
[18:27] <directhex> see, i said moon 2.2-0ubuntu1~ffox36~lucid1 would build fine
[18:28] <asac> ;)
[18:28] <asac> well done
[18:28] <asac> directhex: now with the time you have left you can fix the Long.MAX_VALUE++ not throwing and overflow exception on arm ;)
[18:28] <asac> s/and/an/
[18:29] <directhex> yes, i can fiLOOK BEHIND YOU A THREE HEADED MONKEY
[18:29] <asac> exception6.js
[18:29] <asac> hehe
[18:29] <asac> or at least that we can build it with --enable-interpreter --diable-jit ;)
[18:29] <asac> that doesnt even build atm
[19:46] <micahg> chrisccoulson: should I tag 1.9.2 ubuntu2 for release?
[19:48] <micahg> chrisccoulson: nm, it seems it was promoted to main already :)
[19:50] <micahg> asac: if I tag ubuntu2 to xulrunner192, can you push another release?
[19:52] <micahg> bdrung: are you up for spinning a mozilla-devscripts release to debian
[19:54] <samed87> Buonasera
[19:56] <micahg> asac: is there any way to virtualize IA-64 for testing FTBFS fixes?
[20:19] <fta> http://arstechnica.com/open-source/news/2010/03/mozilla-borrows-from-webkit-to-build-fast-new-js-engine.ars
[20:22] <micahg> fta: hopefully they'll dump the part of nanojit that doesn't build on all arches :)
[21:15] <bdrung> micahg: i am back
[21:40] <micahg> bdrung: can you spin a release of mozilla-devscripts with the change to debian
[21:40] <micahg> bdrung: I commited it to the bzr branch
[21:41] <bdrung> micahg: i want to add a xpi-repack script. i only have to write the manpage for it. give me some time. then i can release it
[21:41] <micahg> bdrung: k. great, thanks
[21:41] <micahg> bdrung: I hope my changelog entry was in the proper style
[21:42] <bdrung> micahg: ask asac - the style was not my idea and i don't love it
[21:42] <micahg> bdrung: weird...becuase it's not our normal convention
[21:42] <micahg> asac: what's the deal with the changelog style in m-devscripts?
[21:42] <bdrung> micahg: what's your normal style?
[21:43] <micahg> bdrung: the way we do for firefox/tb
[23:00] <micahg> asac: can you spin tb3.0.3 to Lucid?
[23:51] <chrisccoulson> right, xulrunner 1.9.2 has been processed through binary NEW as well now
[23:51] <chrisccoulson> so, we can begin transitioning tomorrow :)
[23:57] <asac> good
[23:57] <asac> micahg: all done for 3.0.3? we can upload tomorrow mornig this time then


[12:51] <LaserJock> RichEd: ping
[01:36] <cbx33> hey Las
[01:36] <cbx33> oh
[01:36] <cbx33> :(
[02:17] <RichEd> pong las
[02:17] <RichEd> cbx33: hey there
[02:19] <cbx33> hey RichEd
[02:19] <cbx33> howz ti going
[02:19] <cbx33> http://www.progbox.co.uk/wordpress/?p=158
[02:19] <cbx33> hehe
[02:19] <RichEd> well ... we should have 8-10 new features for fiesty :)
[02:20] <cbx33> cool
[02:20] <cbx33> everyone tired?
[02:20] <RichEd> quite knackered now ... about to wind down into the last dinner
[02:24] <RichEd> cbx33: just read the blog ... it's not clear as to what happened to wet the keyboard ?
[02:24] <cbx33> it went in the dishwasher ;)
[02:24] <cbx33> yeh I'll add a little something
[02:25] <RichEd> oh .... and what is the standard recommended drying time for a dishwashed keyboard ?
[02:25] <crimsun> a day
[02:25] <crimsun> probably shorter if you leave it in a warm (not hot), sunny area
[02:26] <crimsun> or you can use the hairdryer method for an hour
[02:26] <cbx33> it was in the airing cupboard.....but that obviously wan't enough ;)
[02:26] <RichEd> oh ... and i hope it was a coffee spil and not some sort of web surfing nocturnal emission that fouled it up in the first place ;)
[02:26] <cbx33> no...just got mucky apparently
[02:26] <cbx33> ;)
[02:26] <cbx33> bbl
[02:26] <RichEd> k
[06:11] <juantao> Hello, do you know of any application that would help a Spanish speaker learn English? ESL for Linux?
[09:00] <pygi> morning all
[11:23] <pygi> highvoltage: poke?
[11:34] <highvoltage> pygi: pongk
[11:34] <pygi> highvoltage: wanna burn multi-session cd? :)
[11:34] <highvoltage> not really.
[11:34] <highvoltage> I want to burn DVD's!@!
[11:34] <highvoltage> ^_^
[11:35] <pygi> uh, well, we didn't implement dvd yet ^_^
[11:35] <highvoltage> yet...
[11:35] <pygi> well, ofcourse :P Everything will be here one day, especially if I can get some books (which I doubt, but oh well)
[11:35] <highvoltage> I can't remember when last I needed to burn a multi-session disc. why do people still do it?
[11:35] <highvoltage> like yellow books and orange books? ;)
[11:36] <pygi> highvoltage: indeed :P
[11:36] <pygi> highvoltage: get me one :P
[11:38] <pygi> highvoltage: actually, entire set of rainbow books is even better =)
[11:38] <pygi> highvoltage: for example, sivang wanna use multi-session for backup storing in HUB
[11:43] <pygi> everything is so quiet
[11:44] <pygi> oh, nice, thanks :P
[11:44] <Kamping_Kaiser> :P
[11:54] <highvoltage> pygi: sorry, busy with other work atm, not meaning to ignore you!
[11:54] <pygi> highvoltage: don't worry ^_^
[11:54] <highvoltage> pygi: isn't the rainbow books publicly available?
[11:54] <highvoltage> or can't you buy them somewhere?
[11:54] <pygi> highvoltage: well, I can probably buy them, but 5000$ is a lot for just red book for example ^_^
[11:55] <highvoltage> wow
[11:55] <highvoltage> perhaps you should get all the pricing and have a fundraiser for all the books.
[11:55] <pygi> heh, I doubt anybody would donate anything :P
[11:56] <highvoltage> a lot of people are interested in libburn, I'm sure many would sponsor
[11:56] <highvoltage> perhaps you could even ask FSF to help out. you might have to call it gnu libburn :)
[11:56] <pygi> lol
[11:56] <pygi> it's interesting actually, altought many people seem to be interested in libburn, none wants to get involved with anything
[11:57] <highvoltage> I think it might be because the type of people who would be interested in it, are already hectically busy in so many other projects
[11:58] <pygi> dunno really, but it's already going very nice
[11:58] <pygi> but I'm constantly rushing into points where I really need those books
[11:58] <pygi> currently I'm reading MMC specs drafts, and such things which at some points aren't even correct
[12:00] <highvoltage> pygi: if I install a new usplas theme, do you know what I need to do to get it in my initrd too? i installed a new usplash theme but the old one still shows when I boot up.
[12:00] <highvoltage> and somehow i forgot how to use mkinitrd :/
[12:01] <pygi> you can use that tool that Seveas wrote for changing usplash themes
[12:02] <pygi> highvoltage: http://www.kaarsemaker.net/files/Software/usplash-switcher.c
[12:02] <highvoltage> At the time of writing, the cost as per the relevant Philips order form (document no. 28/10/04-3122 783 0027 2) is US$5000.
[12:02] <pygi> update-alternatives and update-initramfs otherwise, I think
[12:02] <highvoltage> omg
[12:03] <pygi> highvoltage: and that is only one book :-/
[12:03] <highvoltage> pygi: aaah, update-initramfs is what I'm looking for, I was still looking for the old fasioned tools
[12:03] <highvoltage> perhaps you should write to philips and explain them what you are working on, and that sending the books to you would be seen as a sponsorship of the project?
[12:04] <highvoltage> while you're at it, ask them to send you a bunch of drives too ;)
[12:04] <pygi> I can try, that's true, but I'm not Joerg or anyone else so I could do that
[12:04] <pygi> Andy and Joerg have access to pre-pre-pre prototype drives, all the specs, etc., etc.
[12:04] <highvoltage> wow
[12:04] <pygi> that's how andy implemented blu ray support :P
[12:04] <highvoltage> geez, that's quite cutting edge.
[12:05] <highvoltage> I think you should perhaps still draw up a budget of the materials you would need.
[12:05] <highvoltage> s/would/do
[12:06] <pygi> I can try yes, but the amount will be rather big
[12:07] <highvoltage> I think you should write philips and if they can't sponsor a copy, then ask if they could at least provide some kind of discount (that would also be seen as sponsorship) and then you could get the remainder somewhere else.
[12:07] <highvoltage> I know these companies are heavy on keeping their specs close to them, but sometimes you're just lucky.
[12:08] <highvoltage> if you have a bunch of philips drives you could also assure them that any philips drive will work well becuase it's been tested.
[12:08] <pygi> indeed, and phillips is especially hard on their lightscribe spec
[12:10] <pygi> we'll see how it goes, but I really hope libburn will mature into something really usable in next couple of years
[12:11] <highvoltage> well, it seems that it might be used to burn cd's over ltsp in the next year or so, that's already a nice application for it, even though a niche application.
[12:11] <pygi> I'm neither as good developer as Andy or Joerg, and I don't have the books, but I'm willing and things are looking nice so far ...
[12:11] <highvoltage> if it could burn dvd's I'd be very happy :)
[12:11] <pygi> right, well same here, but I don't even know which book defines dvd standard :)
[12:12] <pygi> but I hope you'll see it in a year or so
[12:20] <highvoltage> for sure.
[12:23] <pygi> highvoltage: I'll stop bothering you now, sorry :)
[12:24] <highvoltage> no, no problem. I talk to you while I wait for things to build :)
[12:25] <pygi> highvoltage: oh, oki then ^_^
[12:25] <pygi> I can't build things because my system refuses to sign the packages :-/
[05:18] <bddebian> Heya
[05:18] <highvoltage> hey mr debian
[05:19] <bddebian> Heh, hi highvoltage
[05:21] <jsgotangco> hey whats up
[05:23] <highvoltage> busy hacking ubiquity... not sure if it's more bravery or stupidity that led me to it :
[05:23] <highvoltage> )
[05:25] <jsgotangco> hahaha
[05:25] <bddebian> Hi jsgotangco
[05:26] <jsgotangco> hey bddebian
[05:26] <jsgotangco> so what's happening at UDS now
[05:26] <jsgotangco> heh
[05:28] <highvoltage> UDS still going?
[05:29] <jsgotangco> oh yeah, its saturday already
[05:29] <jsgotangco> hehe
[05:29] <jsgotangco> i forgot
[07:13] <stgraber> My pastebin client script can now handle a lot of different pastebin
[07:13] <highvoltage> :)
[07:13] <highvoltage> link?
[07:14] <stgraber> (and is shorter) :)
[07:15] <stgraber> http://www.stgraber.org/download/projects/pastebin/pastebinit.py
[07:16] <stgraber> I will just have to update the "usages" part because now you can put as second argument the URL of the pastebin
[07:18] <stgraber> My first python script/software, but it's a really easy to use/learn language
[07:19] <highvoltage> nice. how does it work? you pipe something to the script and it pastes it for you?
[07:19] <nixternal> oy
[07:19] <stgraber> two way
[07:19] <stgraber> 1) a command | ./pastebinit -
[07:19] <stgraber> 2) ./pastebinit /etc/X11/xorg.conf
[07:20] <stgraber> and it simply returns the URL
[07:20] <stgraber> you can also add as a second argument the URL of a pastebin (the default one is http://ubuntu.pastebin.com)
[07:21] <highvoltage> that looks quite useful.
[07:21] <highvoltage> *especially* when working on thin clients
[07:22] <highvoltage> it's always a hassle redirecting the output to a file first, then scp'ing it to my real machine, and then finally pasting it.
[07:22] <highvoltage> if my thin client is natted, and I have this installed in my chroot, it could be useful.
[07:28] <stgraber> http://www.stgraber.org/download/projects/pastebin/pastebinit_0.3_all.deb
[07:28] <stgraber> The .deb version
[07:46] <willvdl> hey all
[07:48] <highvoltage> hey willvdl
[07:48] <willvdl> dood. sitting at airport. already bored and haven't even boarded yet
[07:49] <highvoltage> :-/
[07:49] <highvoltage> from where to where?
[07:50] <willvdl> going to San Fran for Allhands
[07:50] <highvoltage> ah, of course.
[07:50] <willvdl> really looking forward to putting faces to names
[07:51] <highvoltage> the real life meetings are quite useful for that :)
[07:51] <highvoltage> and launchpad doesn't do most people justice...
[07:51] <willvdl> true. hackergotchis are also not quite the representative
[07:52] <willvdl> highvoltage, is there a spot on the edubuntu web where I can get decent sized screenshots?
[07:53] <willvdl> http://www.edubuntu.org/images/tour/*.png ?
[07:54] <highvoltage> probably
[07:54] <highvoltage> i must admit the screenshots are slightly outdated
[07:54] <highvoltage> I took a bunch of screenshots yesterday, some of it would be the same in edubuntu
[07:54] <highvoltage> just a sec...
[07:54] <willvdl> cool
[07:55] <willvdl> well, not really that outdated. they're dapper screenshots...
[07:55] <highvoltage> willvdl: http://www.tuxlab-os.co.za/screenshots
[07:55] <willvdl> shweeeet
[07:55] <highvoltage> that site isn't really launched yet, so it's a bit uncomplete, but the screenshots are from edgy
[07:56] <willvdl> nice, like the rounded edges and drop shadows (a favourate of mine)
[07:58] <willvdl> is that a drupal site?
[07:58] <willvdl> nice theme
[07:59] <highvoltage> yes, drupal site
[08:00] <willvdl> urk. need to find a power point.
[08:02] <highvoltage> what is that?
[08:02] <highvoltage> :)
[08:05] <willvdl> more hamsters more hamster
[08:06] <willvdl> okie outa here.
[08:06] <willvdl> ciao bene
[08:06] <highvoltage> bye
[08:13] <hal9k2010> hello all
[08:13] <highvoltage> hello hal9k2010
[08:14] <highvoltage> edubuntugirl: be hal
[08:14] <edubuntugirl> I can feel my mind going...
[08:15] <hal9k2010> need some help with unbuntu in a mac
[08:16] <hal9k2010> anyone with exp. in instaling enbuntu in a mac ?
[08:18] <stgraber> I have done that several time on a G3 mac
[08:18] <stgraber> maybe I can help
[08:19] <hal9k2010> i have a powerbook wallstreet and i was thinking in trying linux in that mac need info how to do it
[08:19] <hal9k2010> i will apreciate the help
[08:20] <hal9k2010> powerbook wallstreet running mac os 8.6 and 64 mgs of ram
[08:20] <stgraber> ok, what did you try until now ?
[08:22] <hal9k2010> i download from the website the cd data but never mounted in the mac... i transfer the image to this mac i am using now, is a b/w power mac  i dont know what i need for the powerbook to mount the data
[08:24] <hal9k2010> sorry i am totally ignorant about linux and how to install in the mac
[08:26] <stgraber> first, do you have a cdrom reader on the mac ?
[08:27] <hal9k2010> if you mean that if i have a cd rom in the powerbook .. yes
[08:28] <hal9k2010> yes i do  have a cd rom
[08:30] <stgraber> ok, so once you have burned your ubuntu install cdrom (simply burn the image, not extract it on the CD)
[08:31] <stgraber> you should be able to boot it by :
[08:31] <stgraber> Putting the CD in the cdrom reader
[08:31] <stgraber> Shutdown the Mac
[08:31] <stgraber> Power on the mac while pressing the "c" key until the CD-Rom boot
[08:34] <hal9k2010> ok so i need a cd burner...  i guess i have 2 look 4 one now and try that way
[08:35] <hal9k2010> thanks stgraber... hope works this time
[10:57] <sbalneav> Afternoon all
[10:57] <pygi> hey sbalneav
[10:58] <stgraber> hi
[10:58] <pygi> I saw we didn't get a session for ltsp burning
[10:58] <pygi> too bad
[10:58] <pygi> sbalneav: wanted to tell you we implemented multi session support in libburn
[10:58] <pygi> and it freakin' rocks :)
[10:58] <pygi> (dunno if you read planet ubuntu)
[11:50] <pygi> sbalneav, you alive? :P
[11:57] <mario_> edubuntugirl, tell sbalneav I'm very sad that we didn't got the ltsp burning bits session, but oh well, stuff happens. On the other note, -multi now works under -tao in libburn.
[11:57] <edubuntugirl> Righto, mario_!


[01:01] <itnet7> anyone around for the meeting tonight? Only really one topic I'd like to bring up
[01:02] <mxwil_> Good evening
[01:02] <itnet7> Hey there mxwil_ !
[01:02] <itnet7> Well, I am at training for Work stuff this week so I have been pretty scarce lately
[01:03] <itnet7> but I guess I will send and e-mail to the Mailing list, with an updated schedule for the meeting and to start a discussion on the Agenda item that I had added!
[01:03] <itnet7> s/meeting/meetings/
[01:05] <itnet7> Okay, Well that's what I will do... Talk with you soon! bbl
[01:06] <mxwil_> you leaving now
[01:06] <mxwil_> ?
[18:07] <PowerTux> hi all anyone has notebook Dell Vostro 3500 with NVidia GT218 GeForce 310M card ? it works ?
[18:13] <mhall119> PowerTux: try asking in #ubuntu (I know it gets crazy busy in there)
[18:13] <mhall119> or in #ubuntu-beginners-chat
[18:15] <PowerTux> thanks
[18:19] <danstoner> PowerTux: http://webapps.ubuntu.com/certification/hardware/201004-5574/
[18:20]  * danstoner wonders why those hardware compat entries do not include detailed reports (like lspci output).
[18:20] <PowerTux> danstoner: sorry, i mean this card  NVidia GT218 GeForce 310M
[18:21] <PowerTux> i notice that this driver doesnt exist in nvidia drivers GT 218
[18:25] <maxolasersquad> PowerTux: Do you have the laptop already, or are you contemplating getting it?
[18:26] <PowerTux> maxolasersquad:  I have this one, and try to install this card...
[18:27] <RoAkSoAx> .win 3
[18:27] <RoAkSoAx> lol
[18:27] <maxolasersquad> If you go to System->Administration->Hardware Drivers, does it show you the NVidia driver ready to install?
[18:35] <PowerTux> maxolasersquad : it doesnt has this option Hardware Drivers
[18:36] <maxolasersquad> What version of Ubuntu are you running?
[18:36] <PowerTux> maxolasersquad: 10.10
[18:36] <PowerTux> 64 bits
[18:38] <maxolasersquad> Try runnong the following from a command-line: jockey-gtk
[18:40] <PowerTux> maxolasersquad it shows Additional Drivers window
[18:41] <PowerTux> it exist after lspci
[18:42] <PowerTux> i notice that 310 M driver that i´ve installed dont find this card
[18:43] <PowerTux> and on xorg.0.log shows the drivers supported
[18:43] <PowerTux> and the GT 218 doenst exists
[18:43] <PowerTux> i found in nvidia drivers site and it doesnt exists there
[18:44] <PowerTux> there is a 310 M but not gt 218
[18:44] <PowerTux> i´ve download and install this 310 M
[18:45] <PowerTux> NVIDIA-Linux-x86_64-260.19.29.run
[18:46] <PowerTux> Im thinking that the correct driver doesnt exists
[18:46] <PowerTux> yet
[18:46] <maxolasersquad> jockey-gtk should be able to find whatever drivers are available for your card.
[18:49] <PowerTux> yep but shows Additional Drivers windows because this notebook has 2 proprietary drivers, Broadcom (Wireless) and Nvidia
[18:51] <PowerTux> anyone has NVidia GT218 GeForce 310M working properly on 10.10 64 bits ?
[18:53] <andrew> Greetings from the north, how's it feel to be the only state without snow on the ground?
[19:02] <maxolasersquad> PowerTux: You should be able to select the Nvidia from jockey-gtk and install the appropriate Nvidia driver for your card.
[19:02] <maxolasersquad> andrew: It feels great!
[19:02] <andrew> maxolasersquad: I hear that despite the snow, it's still cold down there.
[19:03] <PowerTux> maxolasersquad: it has nvidia there, i´ve installed and the problem was the same ! so i uninstalled nvidia from that
[19:04] <PowerTux> and downloaded from the site
[19:04] <maxolasersquad> PowerTux: What problem do you have?
[19:08] <PowerTux> maxolasersquad: after reboot it goes to shell and the error is (EE) device doesnt exists
[19:09] <PowerTux> in xorg.0.log
[19:10] <maxolasersquad> Some Googling seems to suggest that the card isn't supported under Linux by NVidia yet.
[19:11] <maxolasersquad> You may want to try posting the details of your problem at ubuntuforums.org
[19:11] <PowerTux> yep i´ll do that, thanks do much
[19:25] <maxolasersquad> Does Intel only make graphics chips that are integrated on mobos?
[19:28]  * MichelleQ consults wikipedia
[19:29] <MichelleQ> maxolasersquad: if wikipedia is to be believed (which is sometimes questionable) - yes.
[19:30] <maxolasersquad> :(
[19:30] <MichelleQ> :-/ but I's not an expert
[19:31] <MichelleQ> http://en.wikipedia.org/wiki/Intel_GMA
[19:32] <maxolasersquad> I wonder what the best "free" card is for a desktop.
[19:32] <MichelleQ> as in, stand-alone?
[19:33] <MichelleQ> non-incorporated?
[19:35] <MichelleQ> and I'm going to make the gross assumption that you want it to be ubuntu-compatable, yes?
[19:36] <MichelleQ> wow these articles I'm finding are the sucksville.
[19:39] <maxolasersquad> Free as in free drivers.
[19:39] <MichelleQ> most recent article I can find:  http://www.brighthub.com/computing/linux/articles/38571.aspx
[19:39] <maxolasersquad> But still fully supported.
[19:41] <MichelleQ> yeah, I dunno.  :-/
[19:41] <MichelleQ> then again, I'm probably setting off looking for the wrong bits.
[19:42] <maxolasersquad> That article confirms what I feared to be the case.
[19:43] <MichelleQ> Sorry.  :-/
[19:43] <MichelleQ> I was finding a number of forums/articles/etc, all published in 2002-2005.  Totally not helpful.
[19:49] <maxolasersquad> I think that is the story.  You can either buy a mobo with an integrated Intel chip, or use the FOSS drivers available for NVida or ATI.
[19:50] <MichelleQ> seems to be the deal, yeah
[20:01] <mhall119> awesome google rube goldberg video: http://www.fastcompany.com/1715913/syyn-labs-google-science-fair-ruth-goldberg-machine
[20:01] <mhall119> featuring Ubuntu at one point
[21:37] <rmcbride> re video cards, I've typically used Nvidia with the Nvidia drivers. My main dev box is a laptop with a GTS 360M. I have had far less problems with it in the course of distro testing than the various Intel GMA devices on my netbooks/old laptop.
[21:39] <rmcbride> even the best Intel GMA card I've used is totally useless at any of the decent OpenGL games that I've tried... If I was a driver or kernel developer I'd stick to the FOSS drivers and try to improve them, but... there's really nothing I can do and I consider myself an end user for those kinds of devices.
[21:45] <mhall119> I don't think that's a linux thing
[21:45] <mhall119> from what I hear from windows folks, intel cards are useless for 3d games there too
[21:58] <rmcbride> They're not SUPPOSED to be useless, but for those and things like compiz + multiple monitors I've had horrible luck
[21:59] <rmcbride> though they do seem to be working OK with the compiz based Unity for 11.04. I just don't have secondary monitors on those laptops
[21:59] <mhall119> my brand new work computer scores 3.9 on the windows metric, because of the intel card
[21:59] <rmcbride> ouch
[21:59] <mhall119> 8 cores, 8GB ram
[21:59] <mhall119> only 3.9
[21:59] <mhall119> so I have a 2-core, 4GB VirtualBox image running Ubuntu
[22:00] <mhall119> I use that for everything but Outlook
[22:00] <rmcbride> NIce. back when I was at SYMC I ran Ubuntu and Windows inside seperate sessions under VMWare Fusion on a macbook pro
[22:00] <rmcbride> sadly, for some reason they didn't want me taking that laptop with me when I left


[01:40] <swift110-phone> Hey
[03:18] <FurretUber> Hello, I am having a problem with the sound in my computer: the front jacks don't work, while the rear ones work. I am using Lubuntu 14.04 from a external HDD and in another computer which I tested the front jacks work. Both computers have Intel HDA, but while the one that works has a Realtek codec, mine is VIA VT1818S. I installed alsa-tools-gui and tried to override the not detected pins using HDAJackRestack, but I had no succes
[19:11] <lopta> I'm trying Lubuntu 15.10 on a Dell Optiplex 320
[19:11] <lopta> (that was laying around at the office)
[19:14] <lopta> brb
[20:25] <freddylisbon> I just put it on a Dell Latitude D630.
[20:26] <freddylisbon> Only thing I had to do was install drivers for wireless.
[20:26] <freddylisbon> It's a really lovely laptop now.
[20:30] <patricita> hello
[20:31] <freddylisbon> hi
[20:31] <patricita> soy de venezuela
[20:33] <patricita> respondan
[20:39] <freddylisbon> hola
[21:55] <lopta> Looks promising now.
[22:03] <chris349> Is there any way to replace the screensaver with a shell script? I want the computer after X minutes of inactivity to exit the brower, clear the cache, etc and restart the browser


[07:21] <mark__> 0000
[07:21] <mark__> ...
[09:46] <jolexin> my start panel with the application menu tree doeas not appear after login
[09:47] <jolexin> what can I do?
[10:54] <gordonjcp> morning
[10:54] <gordonjcp> in 17.10, is the Advanced menu gone?
[10:54] <gordonjcp> I'm not seeing a way to enable it
[12:21] <Eightynine> Is it safe to install HWE stack update for Ubuntu 16.04?
[14:18] <gordonjcp> in 17.10, is the Advanced menu gone?
[14:19] <gordonjcp> in mate-tweak there is a dropdown with four options but none of them seem to be the advanced menu
[14:29] <vkareh> gordonjcp: It's no longer switchable in mate-tweak. As far as I can see, only the Redmond layout uses it by default. You can still add it manually, though (it's still included in the install)
[16:42] <gordonjcp> vkareh: yeah, I can use the redmond layout and move the bar to the top, it's pretty close
[16:43] <vkareh> gordonjcp: you can also choose whichever panel layout and manually add it (right-click -> Add to Panel... -> Advanced MATE Menu)
[16:44] <gordonjcp> aha
[16:45] <gordonjcp> seems to be more than just a name change though :-)
[16:46] <vkareh> gordonjcp: what do you mean?
[16:50] <gordonjcp> I think it's laid out differently, or something, I'd need to compare it to 16.04
[16:50] <gordonjcp> it's close enough for muscle memory to work again though :-)
[16:51] <gordonjcp> what's with the names, redmond and cupertino?
[16:55] <vkareh> gordonjcp: Redmond => Microsoft; Cupertino => Apple (those are the cities where the respective companies reside) :P
[16:58] <gordonjcp> oh, cool
[16:58] <gordonjcp> so if I wanted to switch to Windows, it would use something similar?
[17:18] <vkareh> not really, it's just the panel layout. If you choose Redmond, your panel layout resembles that of Windows. If you choose Cupertino, your panel layout looks like a Mac
[17:21] <Jack_Sparrow> !info cairo-dock
[17:25] <Jack_Sparrow> One of my favorite menu bar panel whatever
[17:52] <Eightynine> How can I open Firefox with recently opened tabs if Firefox opened without them?
[17:53] <Jack_Sparrow> You were already told.. In Mint... now stop spying on family and spouse
[17:55] <Eightynine> Why do you think I'm spying?


[00:09] <tsimonq2> slangasek: Can I please get Binary NEW reviews of libdbusmenu-qt and kdeclarative?
[00:51] <cjwatson> I did libdbusmenu-qt, but only because it was trivial with new-binary-debian-universe
[00:52] <cjwatson> not doing kdeclarative (at the moment, anyway)
[00:52] -queuebot:#ubuntu-release- New: accepted check-manifest [amd64] (bionic-proposed) [0.36-1]
[00:52] -queuebot:#ubuntu-release- New: accepted gnustep-gui [arm64] (bionic-proposed) [0.26.2-2]
[00:52] -queuebot:#ubuntu-release- New: accepted gnustep-gui [i386] (bionic-proposed) [0.26.2-2]
[00:52] -queuebot:#ubuntu-release- New: accepted gnustep-gui [s390x] (bionic-proposed) [0.26.2-2]
[00:52] -queuebot:#ubuntu-release- New: accepted libdbusmenu-qt [arm64] (bionic-proposed) [0.9.3+16.04.20160218-1]
[00:52] -queuebot:#ubuntu-release- New: accepted libdbusmenu-qt [i386] (bionic-proposed) [0.9.3+16.04.20160218-1]
[00:52] -queuebot:#ubuntu-release- New: accepted libdbusmenu-qt [s390x] (bionic-proposed) [0.9.3+16.04.20160218-1]
[00:52] -queuebot:#ubuntu-release- New: accepted gnustep-gui [amd64] (bionic-proposed) [0.26.2-2]
[00:52] -queuebot:#ubuntu-release- New: accepted gnustep-gui [ppc64el] (bionic-proposed) [0.26.2-2]
[00:52] -queuebot:#ubuntu-release- New: accepted libdbusmenu-qt [armhf] (bionic-proposed) [0.9.3+16.04.20160218-1]
[00:52] -queuebot:#ubuntu-release- New: accepted r-cran-plotly [amd64] (bionic-proposed) [4.7.1+dfsg-1]
[00:52] -queuebot:#ubuntu-release- New: accepted gnustep-gui [armhf] (bionic-proposed) [0.26.2-2]
[00:52] -queuebot:#ubuntu-release- New: accepted libdbusmenu-qt [ppc64el] (bionic-proposed) [0.9.3+16.04.20160218-1]
[00:52] -queuebot:#ubuntu-release- New: accepted libdbusmenu-qt [amd64] (bionic-proposed) [0.9.3+16.04.20160218-1]
[00:57] <tsimonq2> cjwatson: Thanks.
[01:19] -queuebot:#ubuntu-release- New binary: gnustep-back [s390x] (bionic-proposed/universe) [0.26.2-2] (no packageset)
[01:20] -queuebot:#ubuntu-release- New binary: gnustep-back [ppc64el] (bionic-proposed/universe) [0.26.2-2] (no packageset)
[01:22] -queuebot:#ubuntu-release- New binary: gnustep-back [arm64] (bionic-proposed/universe) [0.26.2-2] (no packageset)
[01:22] -queuebot:#ubuntu-release- New binary: gnustep-back [i386] (bionic-proposed/universe) [0.26.2-2] (no packageset)
[01:23] -queuebot:#ubuntu-release- New binary: gnustep-back [armhf] (bionic-proposed/universe) [0.26.2-2] (no packageset)
[01:26] -queuebot:#ubuntu-release- New binary: gnustep-back [amd64] (bionic-proposed/universe) [0.26.2-2] (no packageset)
[04:05] -queuebot:#ubuntu-release- New binary: qca2 [amd64] (bionic-proposed/universe) [2.1.3-2ubuntu1] (kubuntu)
[04:14] -queuebot:#ubuntu-release- New binary: freefem [s390x] (bionic-proposed/universe) [3.5.8-6ubuntu1] (no packageset)
[04:15] -queuebot:#ubuntu-release- New binary: freefem [ppc64el] (bionic-proposed/universe) [3.5.8-6ubuntu1] (no packageset)
[04:18] -queuebot:#ubuntu-release- New binary: freefem [amd64] (bionic-proposed/universe) [3.5.8-6ubuntu1] (no packageset)
[04:18] -queuebot:#ubuntu-release- New binary: freefem [armhf] (bionic-proposed/universe) [3.5.8-6ubuntu1] (no packageset)
[04:18] -queuebot:#ubuntu-release- New binary: freefem [arm64] (bionic-proposed/universe) [3.5.8-6ubuntu1] (no packageset)
[04:19] -queuebot:#ubuntu-release- New binary: freefem [i386] (bionic-proposed/universe) [3.5.8-6ubuntu1] (no packageset)
[04:27] <tsimonq2> freefem Binary NEW is library v5 rename, cleanup from the GCC 5 transition
[07:13] <tsimonq2> So acheronuk reminded me about the Alpha, and I'm thinking about just skipping Alpha 2 altogether.
[07:14] <tsimonq2> Lubuntu isn't ready, we have some pending changes going on, Kubuntu is in the middle of a Frameworks transition that wouldn't land in time, Ubuntu Kylin has some packages they need to get in that a MOTU (likely me) won't get to in the next 24 hours, Ubuntu MATE said no, Xubuntu doesn't do milestones, Ubuntu Budgie said yes so I'll have to talk to them... am I forgetting about anyone?
[07:14] <tsimonq2> s/won't get to/likely won't get ti/
[07:16] <acheronuk> considering that Kubuntu is also waiting for not just frameworks, but the whole new plasma LTS stack out on 6th Feb, plus a new full applications release, an Alpha2 would not represent anything like what we intend to ship anyway
[07:16] <tsimonq2> Right.
[07:17] <acheronuk> we could always name a days daily iso mid feb, and have a community iso test days, or something, if we really want it
[07:17] <tsimonq2> I might be down for that
[07:18] <tsimonq2> Depends on how things work out for Lubuntu
[07:18] <tsimonq2> (And will likely be the same for Kubuntu, depending on how things work out...)
[07:18] <acheronuk> ditto. just a though
[07:18] <acheronuk> *thought
[07:18] <tsimonq2> right
[07:19] <tsimonq2> acheronuk: If you see sil2100 before me on Monday, I know he signed up to do Nusakan for Alpha 2
[07:21] <acheronuk> ok, can do
[07:24] <valorie> ooo, one more alpha we don't have to do
[07:25] <valorie> an daily ISO test day would be cool though
[07:28] <flocculant> tsimonq2: xubuntu does do milestones - we just don't do Alpha's ;)
[07:28] <tsimonq2> flocculant: bah, whatever ;)
[07:29] <valorie> I think kubuntu skips them often because of KDE release calendars
[07:29] <flocculant> acheronuk: a community iso test day might be something useful - could arrange it at https://community.ubuntu.com easily enough, bear in mind that all the iso's build at different times
[07:31] <acheronuk> the previous 2 days builds are kept on a dated folder, so could name one of those if there is lag between flavours
[07:31] <acheronuk> but yes, a detail to work out
[07:33] <flocculant> acheronuk: the detail of the build times > http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/etc/crontab
[07:33] <flocculant> anyway - useful idea :)
[07:34] <tsimonq2> I think a few weeks ago slangasek said something similar, I would be interested to hear what he has to say on it :)
[07:34] <acheronuk> flocculant: ty
[07:34] <acheronuk> tsimonq2: yeah, I think he did
[07:42] <acheronuk> tsimonq2: https://irclogs.ubuntu.com/2018/01/04/%23ubuntu-release.html#t21:47
[07:42] <tsimonq2> acheronuk: human grep :P
[07:43] <acheronuk> no, grep is grep. literally :P
[07:44] <flocculant> tsimonq2 acheronuk - looks like the 3 flavours who build a goof while after the rest are Lubuntu, Kylin and Studio - Studio are likely to not even notice it happening, Kylin rarely get involved in setting things up
[07:45] <flocculant> so just 1 flavour who might care to join in :D
[07:45] <flocculant> that flavour might perhaps think about building earlier in the day in the future :p
[07:46] <flocculant> I moved our's a few cycles ago to make it easier for Xubuntu
[07:46] <valorie> might be good to have a few people contact Studio
[07:46] <valorie> unless we want to let it die
[07:46] <valorie> :(
[07:46] <flocculant> valorie: I've tried
[07:47] <valorie> maybe it's too late
[07:47] <flocculant> also they're quite close to Xubuntu as they use Xfce - I'm not the only one to have tried
[07:47] <valorie> what happens to their packageset if they die?
[07:47] <flocculant> not a clue
[07:48] <tsimonq2> Eventually it gets abandoned or removed.
[07:48] <valorie> yeah, that's what I thought
[07:48] <valorie> that would be sad
[07:49] <valorie> quite a few people use it with their TVs, etc.
[07:51] <flocculant> do they? I thought that was mythbuntu?
[07:52] <lotuspsychje> mythbuntu is abandoned no?
[07:52] <flocculant> yea
[07:52] <lotuspsychje> thought so
[07:53] <valorie> uh, yeah -- production, not display, sorry
[07:53] <acheronuk> too easy to grab another flavour and add what creator tools you want now I suppose. less need a bundled iso for it
[07:53] <valorie> true
[07:53] <valorie> nobody but them likes jack though
[07:53] <valorie> lol
[07:54] <flocculant> :)
[07:54] <acheronuk> maybe there could be studio meta packages retained/redone, so that you can 'studio up' each flavour?
[07:55]  * valorie volunteers acheronuk to do that wonderful work!
[07:55]  * acheronuk hides
[07:55] <flocculant> well it's not dead yet - just appears so to us ;)
[07:55] <acheronuk> of course. just think out loud
[07:56] <acheronuk> *thinking
[08:25] <flocculant> :)
[12:01] -queuebot:#ubuntu-release- New: accepted gnustep-back [amd64] (bionic-proposed) [0.26.2-2]
[12:01] -queuebot:#ubuntu-release- New: accepted gnustep-back [armhf] (bionic-proposed) [0.26.2-2]
[12:01] -queuebot:#ubuntu-release- New: accepted gnustep-back [ppc64el] (bionic-proposed) [0.26.2-2]
[12:01] -queuebot:#ubuntu-release- New: accepted gnustep-back [arm64] (bionic-proposed) [0.26.2-2]
[12:01] -queuebot:#ubuntu-release- New: accepted gnustep-back [s390x] (bionic-proposed) [0.26.2-2]
[12:01] -queuebot:#ubuntu-release- New: accepted gnustep-back [i386] (bionic-proposed) [0.26.2-2]
[12:02] <acheronuk> .
[12:03] <acheronuk> hi, can kdeclarative new binary be reviewed please if someone can spare the time? that is blocking the rest of frameworks building. thanks
[12:29] <cjwatson> acheronuk: done
[12:29] -queuebot:#ubuntu-release- New: accepted kdeclarative [amd64] (bionic-proposed) [5.42.0-0ubuntu1]
[12:29] -queuebot:#ubuntu-release- New: accepted kdeclarative [armhf] (bionic-proposed) [5.42.0-0ubuntu1]
[12:29] -queuebot:#ubuntu-release- New: accepted kdeclarative [ppc64el] (bionic-proposed) [5.42.0-0ubuntu1]
[12:29] -queuebot:#ubuntu-release- New: accepted kdeclarative [arm64] (bionic-proposed) [5.42.0-0ubuntu1]
[12:29] -queuebot:#ubuntu-release- New: accepted kdeclarative [s390x] (bionic-proposed) [5.42.0-0ubuntu1]
[12:30] -queuebot:#ubuntu-release- New: accepted kdeclarative [i386] (bionic-proposed) [5.42.0-0ubuntu1]
[12:30] <acheronuk> cjwatson: thank you very much :)
[17:34] <tsimonq2> Hello, could I please get a Binary NEW review of freefem?
[17:53] <tsimonq2> I miscalculated things... could a kind soul please RM kde-baseapps from bionic-proposed?
[18:59] <flocculant> infinity: re the non-booting 32 bit iso issue I appear to have, I managed to get a vid of the boot with some info - if it's any use I don't know ;)
[18:59] <flocculant> bug 1744357
[23:09] -queuebot:#ubuntu-release- New binary: vdr-plugin-epgsync [ppc64el] (bionic-proposed/none) [1.0.1-3] (no packageset)
[23:09] -queuebot:#ubuntu-release- New binary: vdr-plugin-skinenigmang [s390x] (bionic-proposed/none) [0.1.2+git20180128-1] (no packageset)
[23:09] -queuebot:#ubuntu-release- New binary: vdr-plugin-epgsync [s390x] (bionic-proposed/none) [1.0.1-3] (no packageset)
[23:09] -queuebot:#ubuntu-release- New binary: vdr-plugin-epgsync [arm64] (bionic-proposed/none) [1.0.1-3] (no packageset)
[23:09] -queuebot:#ubuntu-release- New binary: vdr-plugin-skinenigmang [ppc64el] (bionic-proposed/universe) [0.1.2+git20180128-1] (no packageset)
[23:10] -queuebot:#ubuntu-release- New binary: vdr-plugin-epgsync [armhf] (bionic-proposed/universe) [1.0.1-3] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: vdr-plugin-skinenigmang [armhf] (bionic-proposed/universe) [0.1.2+git20180128-1] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: vdr-plugin-skinenigmang [arm64] (bionic-proposed/universe) [0.1.2+git20180128-1] (no packageset)
[23:24] <wgrant> flocculant: That's a kernel bug that I tracked down on Friday. Affects hardware with an IOMMU, and only on our 4.13 i386 with Meltdown fix. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745118
[23:24]  * wgrant dupes
[23:55] -queuebot:#ubuntu-release- New binary: vdr-plugin-epgsync [amd64] (bionic-proposed/universe) [1.0.1-3] (no packageset)
[23:56] -queuebot:#ubuntu-release- New binary: vdr-plugin-epgsync [i386] (bionic-proposed/universe) [1.0.1-3] (no packageset)
[23:58] -queuebot:#ubuntu-release- New binary: vdr-plugin-skinenigmang [amd64] (bionic-proposed/universe) [0.1.2+git20180128-1] (no packageset)
[23:58] -queuebot:#ubuntu-release- New binary: vdr-plugin-skinenigmang [i386] (bionic-proposed/universe) [0.1.2+git20180128-1] (no packageset)


[02:20] <Ahmuck> what is the software goal, target audience of edubuntu?
[03:39] <highvoltage> mhall119: just uploaded a new debmower, tested it on a clean machine and it makes a bootable disc from the qimo template
[03:40] <highvoltage> mhall119: still shows all those (mostly harmless) error messages and you can't cancel it, but that's what I'm doing next
[03:57] <highvoltage> mhall119: ah and it still asks for the grub installation which you should just manually cancel for now
[04:00] <mhall119> highvoltage: have you tried booting the resulting iso?
[12:25] <mgariepy> good morning everyone
[12:56] <highvoltage> mhall119: yep
[12:56] <highvoltage> good morning mhall119
[13:21] <mhall119> morning highvoltage
[13:29] <highvoltage> oops I actually meant to say mgariepy, but yes good morning to you too mhall119 :)
[13:33] <mhall119> :P
[13:33]  * mhall119 is off to the passport office
[13:34] <mgariepy> so highvoltage did you had time to think about washing my car ?
[13:38] <highvoltage> mgariepy: I might have to do that since I'll need your car to move those desks :)
[13:44] <mgariepy> highvoltage, nice :D
[13:44] <mgariepy> but those desk fit very very tight in my car..
[13:45] <mgariepy> i moved one at mike's place last summer...
[13:45] <mgariepy> those are ikea corner table right ?
[13:46] <highvoltage> mgariepy: yep
[13:46] <highvoltage> mgariepy: but I guess I can make a plan B
[13:49] <mgariepy> well you know, i kinda like the idea that involve someone but not me washing my car part of the plan A :P
[13:50] <mgariepy> just kidding haha
[13:50] <mgariepy> i'll gladly help you move those :)
[18:43] <asdfghhh> HI


[00:12] <hml> wallyworld: i’m not going to change unit to use refresh instead of common.Life - it’s not strictly needed and we can’t get ride of common.Life easily anyways.
[00:12] <wallyworld> where is the life() call made?
[00:15] <hml> wallyworld: st.Unit(tag) api/uniter/uniter.go ln 147 ish
[00:16] <wallyworld> we should be calling refresh there
[00:16] <wallyworld> why construct an incomplete unit
[00:16] <wallyworld> when we can call refresh() instead of life() and get all the data
[00:17] <hml> wallyworld: okay -
[00:17] <wallyworld> but there are places in Application that call life() that we would retain
[00:17] <wallyworld> as currently the application life mirrors the unit life
[00:48] <wallyworld> babbageclunk: if you had time for a smallish mechanical review that would be great https://github.com/juju/juju/pull/7815
[00:49] <babbageclunk> wallyworld: sure
[01:03] <wallyworld> axw: were you free now for 1:1? or soon?
[01:03] <axw> wallyworld: sure, can do now
[01:03] <wallyworld> ok
[02:00] <babbageclunk> axw: thanks for the review - can you look at https://github.com/juju/1.25-upgrade/pull/24 as well? :)
[02:00] <axw> babbageclunk: yup, looking now
[02:11] <babbageclunk> wallyworld: sorry, I totally got sidetracked on your review - back to it now
[02:27] <babbageclunk> wallyworld: approved!
[03:52] <babbageclunk> wallyworld: I'm popping out for a while, but I'll be back online tonight.
[04:52] <wallyworld> babbageclunk: awesome, thank you for review
[07:18] <wallyworld> axw: swap you reviews? https://github.com/juju/juju/pull/7818
[09:57] <axw> wallyworld: sorry, I took jeremy to his friend's place. sure, but I think you're getting a raw deal ;p
[10:58] <wallyworld> axw: no worries, thanks for review. the azure one looked sane; i can't give expert opinion on the implementation but testing seemed thorough


[19:33] <slangasek> mhall119: so, how does summit fare under django 1.6 nowadays?  I'm hitting a strange issue with the debconf14 site which I suspect is a django bug; wondering if there's any hope of testing with the new upstream
[19:48] <mhall119> slangasek: I'm working on an upgrade
[19:49] <mhall119> slangasek: lp:~mhall119/summit/django-1.6-port
[19:49] <mhall119> sponsorships app isn't working in 1.6, because it uses FormWizards and those have changed significantly since Summit was written
[19:49] <slangasek> mhall119: so if I tried to run it on django 1.6 as-is, it would fall over badly? :)
[19:49]  * slangasek nods
[19:49] <mhall119> schedule and common work in the above branch
[19:50] <slangasek> and it's precisely sponsorship that I'm currently working on sorting out
[19:50] <slangasek> so I guess that doesn't help me
[19:50] <slangasek> was worth asking, though - thanks
[19:50] <mhall119> but I don't know enough about (a) the sponsorship app or (b) form wizards in django to quickly fix it
[19:50] <mhall119> slangasek: what version of django are you running it on?
[19:50] <slangasek> 1.4
[19:50] <slangasek> that's the supported version, right?
[19:52] <mhall119> yeah


[10:18] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: Design and Web team summary – 25 October 2019 @ https://ubuntu.com/blog/design-and-web-team-summary-25-october-2019
[14:09] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: LibreOffice 6.4 Will Ship with Native GTK Dialogs on Linux @ https://www.omgubuntu.co.uk/?p=155549 (by Joey Sneddon)
[15:10] -SwissBot:#ubuntu-news- ::Softpedia:: Dell's Latest XPS 13 Ubuntu Laptop Is Now Available in 18 New Configurations @ https://news.softpedia.com/news/dell-s-latest-xps-13-ubuntu-laptop-is-now-available-in-18-new-configurations-528091.shtml (by Marius Nestor)
[15:49] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: The State of Robotics – October 2019 @ https://ubuntu.com/blog/the-state-of-robotics-october-2019
[20:58] -SwissBot:#ubuntu-news- ::Softpedia:: KaOS Linux Gets October Release with KDE Plasma 5.17 Desktop, Linux Kernel 5.3 @ https://news.softpedia.com/news/kaos-linux-gets-october-release-with-kde-plasma-5-17-desktop-linux-kernel-5-3-528093.shtml (by Marius Nestor)
[23:17] -SwissBot:#ubuntu-news- ::Portugal:: Ep 62 – De volta à terra @ https://podcastubuntuportugal.org/2019/11/01/ep-62-de-volta-a-terra/?pk_campaign=feed&pk_kwd=ep-62-de-volta-a-terra
[23:32] -SwissBot:#ubuntu-news- ::Planet:: Podcast Ubuntu Portugal: Ep 62 – De volta à terra @ https://podcastubuntuportugal.org/2019/11/01/ep-62-de-volta-a-terra/?pk_campaign=feed&pk_kwd=ep-62-de-volta-a-terra


[05:15] <didrocks> good morning
[05:15] <duflu> Hi didrocks
[05:16] <didrocks> hey duflu
[06:23] <oSoMoN> good morning desktoppers
[06:30] <didrocks> sesalut oSoMoN
[06:34] <oSoMoN> sesalut didrocks :)
[06:35] <duflu> Morning oSoMoN
[06:59] <Wimpress> Morning
[07:05] <marcustomlinson> goedemorgen
[07:09] <duflu> Morning Wimpress and marcustomlinson
[07:16] <didrocks> hey Wimpress, marcustomlinson
[07:18] <seb128> lut didrocks
[07:18] <seb128> good morning desktopers
[07:18] <didrocks> salut seb128
[07:19] <seb128> en forme ?
[07:19] <duflu> Hi seb128
[07:19] <seb128> hey duflu
[07:21] <didrocks> ça va, et toi ?
[07:25] <seb128> ça va bien !
[07:26] <seb128> duflu, oh, I forgot to mention it again, but that keeps coming as an issue in team meetings, please don't directly nominated bugs to stable serie without assignee. Either you/Marco plan to work on the fix and assign it as appropriate or rls-bb-incoming tag them so they go through the proper team review process
[07:27] <duflu> seb128, ok
[07:27] <seb128> thanks!
[07:28]  * duflu assigns self
[07:28] <seb128> it's a bit annoying that we don't have a proper way to flag "affects that serie" that doesn't conflict with the rls tracking process but that's the way it is atm :/
[07:34] <duflu> didrocks, I would like to drop the patch for bug 1797355, because it's preventing us from getting a bigger bug 1705369 fixed. I can't seem to reproduce 1797355 - can you?
[07:35] <didrocks> duflu: I need to retry with a newer GNOME SHell, but the fix isn't applied upstream IIRC, so let's see
[07:36] <didrocks> duflu: mind if I test it either tomorrow/next Monday? Don't want to reboot/context switch with the potential of not booting right now :p
[07:36] <duflu> I know. It looks to me like upstream had it right
[07:36] <duflu> didrocks, no problem -- I'll just block any code review waiting for you some timwe
[07:36] <duflu> time
[07:37] <didrocks> duflu: I'll retry and keep you posted
[07:43] <seb128> bah, it's ranting week or what on discourse/forums
[07:43] <seb128> snaps, i386, ...
[07:44] <duflu> People care about things. Which means people have opinions
[07:44] <duflu> The good news is that it means they care about Ubuntu
[07:44] <seb128> the french forum seems to have turned into a group of old school people who think a community is about complaining about anything done in the project you are supposed to care about...
[08:02] <Laney> yo
[08:08] <duflu> sup Laney
[08:08] <didrocks> hey Laney
[08:13] <Laney> hey duflu didrocks
[08:20] <oSoMoN> seb128, complaining is very French, nothing new under the sun :)
[08:23] <seb128> hey Laney
[08:23] <seb128> oSoMoN, yeah, just wrote a long reply on discourse
[08:24] <duflu> Remember you can always mute a topic at the bottom of each page
[08:24] <seb128> I'm refraining to register on the french forum to tell them "weird view of being part of a community/project to see that as $must_bitch_about_the_thing_Im_supposed_to_care_about)
[08:25] <seb128> they look like a bunch of biter old linux men :/
[08:25] <duflu> https://xkcd.com/386/
[08:25] <seb128> duflu, :-)
[08:26] <marcustomlinson> all absolute statements are wrong
[08:31] <seb128> well, they are right that our gnome-calculator startup time is embarassing and we should fix that
[08:32] <duflu> Yeah, though I was refraining from discussing that till someone else opened the bug. I just find the slowness annoying and not practical right now
[08:33] <didrocks> I guess this is the most visible point which starts this fud
[08:33] <didrocks> and TBH, it's a little bit embarrassing after having snaps by default for multiple releases. So, I can understand, this is why I asked them to come with facts on the french forum
[08:33] <didrocks> rather the "I think/I don't like/blablabla"
[08:33] <seb128> we transitioned those in 17.10 IIRC
[08:34] <seb128> they wake up 2 years later and act like it was the end of the world today
[08:34] <didrocks> they don't wake up 2 years later :)
[08:34] <didrocks> I've been containing those topics (and raised them here already) multiple times on the french forum
[08:34] <didrocks> telling them we are working on the speed improvements (and we did for some)
[08:35] <seb128> right, that's what I'm telling
[08:35] <didrocks> I guess after 2 years, as everything isn't fixed, they are coming to the conclusion it won't get fixed (but that's just my perception)
[08:35] <seb128> they prefer to bitch in their closed group
[08:35] <seb128> rather than try to work with us on solution...
[08:35] <didrocks> oh… "opening bugs/talking about it in the community forum" is a mantra I have for years with them :)
[08:35] <didrocks> but it doesn't always succeed
[08:35] <seb128> thx for keeping reminding them :)
[08:35] <didrocks> also, I think speaking in english is a high barreer
[08:35] <didrocks> barrier*
[08:36] <seb128> right
[08:36] <seb128> well I read a bit their post
[08:36] <didrocks> yeah, you can find something 3-4 pages for each release since 17.10
[08:36] <seb128> I don't like their mentality, unsure if we can make them reconsider their approach
[08:36] <didrocks> (the topic is archived on the "instable" forum)
[08:37] <seb128> their reply to any "$software has $issue" is "remove the snap, install the deb"
[08:37] <didrocks> I think if we come with "there is now more speed difference between snaps & debs", it will get harder for them to argue
[08:37] <seb128> which then goes "I've a years old version"
[08:37] <seb128> where they reply" try that ppa"
[08:37] <didrocks> yeah, the ppa approach is :/
[08:37] <seb128> would be more constructive to figure out the issue in the snap and get it reported/fixed
[08:37] <didrocks> I don't think they are technical enough for this
[08:37] <didrocks> especially when helping people on the LTS (which is where we pushed the snap)
[08:38] <didrocks> but TBH, I think we have enough "issues" we know about (like the startup time), already, getting those fixed, will help a lot in the perception of the tech
[08:38] <seb128> right
[08:38] <seb128> it's just sad the way they go about it
[08:38] <seb128> like one user had an issue with "retroarch"
[08:39] <seb128> it went through the "ah, it's because you use the snap"
[08:39] <seb128> they recommended installing the deb
[08:39] <seb128> and the user said "I've an year old version now and it still doesn't work"
[08:39] <seb128> so they are making thing more complicated
[08:39] <seb128> and not helping the users
[08:39] <seb128> he's off in a worth situation after they "helped"
[08:39] <seb128> they would better just not reply
[08:39] <didrocks> yeah, I guess this is the issue with not technical enough people
[08:40] <didrocks> the "use the deb" could be understandable: they are just trying to get things fixed for the use case (like sys admins)
[08:40] <didrocks> without seeing the greeter good, but at the same time, they are not beta tester
[08:40] <didrocks> which doesn't help us fixing issues, I agree
[08:40] <didrocks> BUT, in cases like this
[08:40] <didrocks> you end up in a worse situation, I agree
[08:41] <didrocks> "tinkering", was the term I was looking for
[08:41]  * seb128 must refrains from subscribing and trying to reply to every user problem :p
[08:41] <didrocks> good luck then :p
[08:42] <didrocks> I only monitor the "unstable version" topic
[08:42] <didrocks> and sometimes, on Monday, it's already a lot :p
[08:42] <seb128> I did a long reply on discourse, hopefully it's a bit usefulk
[08:42] <didrocks> yeah, read it, sounds good to me
[08:42] <seb128> thx :)
[08:42] <seb128> k, I just close that french forum
[08:42] <seb128> already too much to do, I don't need more distraction
[08:42] <didrocks> I think we should admit that the startup time issue is taking longer to fix than we thought, and this will help
[08:43] <seb128> right
[08:43] <seb128> I also think that for some reason gnome-calculator is praticularly slow
[08:43] <seb128> evince or gnome-calendar are faster to start than the calculator for me
[08:44] <seb128> also the snap exec metric shows that the desktop-launcher is not the main offender, which I though it would have been
[08:44] <didrocks> yeah, I guess we fixed most of the issues there
[08:44] <seb128> but there is no obvious time consumer in the top 10 either
[08:44] <didrocks> so, could be in snapd itself
[08:44] <seb128> right, maybe the compression
[08:44] <seb128> we need mvo&co to get to the bottom of that
[08:46] <didrocks> yep
[08:51] <oSoMoN> seb128, good answer on discourse, also thanks popey for your patience and repeated requests for actionable data
[08:51] <seb128> oSoMoN, thx!
[08:51] <popey> oSoMoN: np
[08:52] <mvo> seb128: you can test if its the compression by using "snap try" on the gnome-calculator prime dir and measure this
[08:53] <oSoMoN> I also like Ian Weisser's articulate replies, they contrast nicely with all those very emotional and unhelpful rants
[08:53] <mvo> seb128: we did some measurements just last week and it looks like squashfs/compression overhead is very small (chipaca wrote a script and measured a bunch of snaps)
[08:53] <seb128> mvo, the dir is /snap/<name>/current counts as "prime"?
[08:54] <oSoMoN> you'll probably need to unsquashfs the snap file to measure that reliably
[08:56] <mvo> seb128: sry was a bit terse, what oSoMoN said is easiest, just unsquash and snap try it
[08:56] <seb128> mvo, k, needs more debugging then :/ Like that recent discussion/report, the user has a 7 seconds start time, the desktop-launcher is the biggest offender in the snap exec metrics with 1 s and the other items are 0.3 seconds or such
[08:56] <mvo> seb128: snap try /path/to/unpack/dir
[08:56] <mvo> seb128: do you have a link?
[08:57] <mvo> seb128: is that hdd or ssd?
[08:57] <seb128> mvo, https://bugs.launchpad.net/snappy/+bug/1833004
[08:57] <mvo> seb128: I wonder if library loading/symbole resolving is slow, we never got around to measure this but I would love to get data for that too
[08:57] <popey> i get 7 second launch if i haven't used chromium for a day - so the cache is cold
[08:58] <popey> https://paste.ubuntu.com/p/mN8MtCPzYW/
[08:58] <seb128> on warm cache with calculator I get 0.7s vs 2s
[08:58] <seb128> like I already position my mouse on the X to close the dialog as it opens and click click click
[08:58] <popey> faster to use alt-f4
[08:58] <popey> as soon as the window appears
[08:58] <seb128> k
[08:58] <popey> IMO
[08:58] <seb128> bah, laptop flat
[08:58] <seb128> I need to go back to my desk
[08:58] <seb128> brb
[08:59] <popey> ^ totally not seb pressing alt-f4 accidentally on irc
[09:01] <oSoMoN> :)
[09:10] <seb128> and back
[09:16] <seb128> popey, mvo, that chromium pastebin is a bit weird btw
[09:16] <seb128>   8.304s /snap/chromium/750/usr/lib/chromium-browser/chrome
[09:16] <seb128>   4.624s /proc/self/exe
[09:16] <seb128> Total time: 9.529s
[09:17] <seb128> until now I though that the list if items were chunck of the total
[09:17] <duflu> Is that second line a fork() ?
[09:17] <duflu> Or just a bad lookup and should be grouped into the first?
[09:18] <mvo> the measure code may encounter something unexpected
[09:20] <duflu> I guess chrome does fork lots. That might be it
[09:22] <oSoMoN> it does fork a lot
[14:22] <tkamppeter> Anyone familiar with the autopkg tests of network-manager, this Python stuff using the unittest Python module?
[14:22] <Laney> a bit
[14:23] <Laney> tkamppeter: what's the problem?
[14:24] <tkamppeter> Laney, I have added some extra print() statements and I do not get the output of them in the log, even not the output of the already existing statements, like print('******* NM initialized *********\n\n'). I have set the NM_LOG_STDOUT env variable and actually get live view of the log output.
[14:35] <Laney> tkamppeter: hmm I dunno, sorry, I certainly saw a lot of output when I ran it before
[14:41] <tkamppeter> Laney, seems that only pitti knows it who has initially created it and then there was never a failure and I am the very first one having it fail.
[14:42] <Laney> No, we've certainly fixed things with it in the past
[14:43] <Laney> It's not something that's been touched a lot - Martin did a good job in making a robust test script - but it has been maintained a bit.
[15:06] <pitti> Laney, tkamppeter: where is this now? (not sure if I missed some distro git packaging changes)
[15:07] <pitti> at first sight it smells like a subprocess issue that gets redirected
[15:07] <Laney> hey pitti
[15:07] <pitti> hey Laney and tkamppeter, wie  geht's?
[15:07] <Laney> I think Till's working from https://code.launchpad.net/~network-manager/network-manager/+git/ubuntu/+ref/gir-nm
[15:10] <pitti> tkamppeter: so where exactly in https://git.launchpad.net/network-manager/tree/debian/tests/nm.py?h=gir-nm did you try and add a print?
[15:11] <pitti> print() in these tests should work fine
[15:17]  * Laney would think so too: buffering's off, stderr redirected to stdout
[15:18] <Laney> pitti: I'm juju 2-ifying/Mojoing autopkgtest atm :-)
[15:18] <Laney> RIP deploy.sh
[15:18] <Laney> hope you're well too
[15:18] <pitti> Laney: oh, poor man's juju! :)
[15:18] <pitti> Laney: I am, thanks! enjoying the summer
[15:19] <Laney> heh
[15:19] <Laney> we've not had one of those yet
[15:20] <Laney> http://[2001:ba8:1f1:d03:216:3eff:fef0:f2f0]/running <- first lxd/armhf test is a-go
[15:21]  * Trevinho undecided weather to go wild and try to fix a g++ thing or just leave the bug and testcase for the future generations :)
[15:21] <Trevinho> whether*
[15:21] <Laney> hey Trevinho
[15:21] <Trevinho> hi Laney
[15:21] <Laney> ¿cómo estás?
[15:21] <seb128> Trevinho, stop getting too much distracted by fixing all the world issues :)
[15:22] <Trevinho> seb128: you know, making better world is my mission :P, but I won't try this one indeed
[15:22] <seb128> :-)
[15:22] <Trevinho> Laney: all good
[15:23] <Trevinho> just was helping with one big improvement to gjs, which is blocked by mozjs, which I've workarounded also upstream, but still is eventually a g++ issue
[15:24] <Trevinho> Laney: as I expect you to be curious, try https://www.pastery.net/dvmjsj/ with both g++ and clang++ and see the nm inconsistency
[15:26] <Laney> I am, but it's 16:25 and I didn't eat my lunch yet, so I'll be curious later :P
[15:26]  * Laney was sweating trying to get lxd stuff to work
[15:27] <Laney> not many things left to do now ^_^
[15:27] <seb128> Laney, woot, well done! enjoy the lunch :-)
[15:28] <Laney> 1) poking the proxies in, 2) testing if ExecReload= works properly, 3) hooking up github stuff
[15:29] <Laney> 4) ssl, but can't really test that without a domain name, which requires the staging environment
[15:29] <Laney> biab
[15:53] <kenvandine> oSoMoN: i repacked the chromium snap adding the gnome-3-28-1804 content interface
[15:53] <kenvandine> and it seems to shave roughly 20% off startup time
[15:53] <kenvandine> very unscientific measurement
[15:53] <kenvandine> rm -rf ~/snap/chromium
[15:54] <kenvandine> time snap run chromium
[15:54] <kenvandine> then alt-f4 when i see the window
[15:55] <oSoMoN> kenvandine, so that's a 20% gain on first run, right? what about subsequent runs?
[15:55] <kenvandine> first run
[15:55] <kenvandine> 2nd run is hard to measure because it starts very fast
[15:55] <oSoMoN> kenvandine, also, the chromium snap launcher will copy an existing profile in ~/.config/chromium, so for measurements you should ensure there's nothing there
[15:56] <kenvandine> oSoMoN: do you know if there is an arg i can pass to exit after startup?
[15:56] <kenvandine> oSoMoN: yeah, i created a new user account
[15:56] <kenvandine> so completely empty home dir
[15:56] <oSoMoN> good
[15:58] <kenvandine> i seem to recall firefox having an arg you can pass to exit after it loads, which seems silly but it very useful for this kind of profiling :)
[15:58] <kenvandine> my reaction time to hit alt-f4 after seeing the window is included here
[15:59] <oSoMoN> kenvandine, not that I know of
[15:59] <kenvandine> the subsequent runs are under 2 seconds including my reaction time
[15:59] <kenvandine> so i'm guessing ~1 second startup
[16:00] <oSoMoN> there's the --product-version switch, but it doesn't actually perform a full initialization of the browser, so it doens
[16:00] <oSoMoN> doesn't count
[16:00] <kenvandine> yeah
[16:01] <Laney> could you use Selenium to close the window?
[16:03] <marcustomlinson> or remove some runtime that causes it crash late :)
[16:03] <Laney> you hackers
[16:05] <ahayzen[m]> instead of using $ time command  you could start a script which scans open X11 windows until Chrome appears?  like hitting xwininfo -root -tree  or something
[16:05] <kenvandine> ahayzen[m]: that's a good idea
[16:06] <Laney> in case you don't know, Selenium is a browser testing framework.
[16:07] <marcustomlinson> XD
[16:09] <marcustomlinson> It's be nice though to have a solution that works on non-browser desktop snaps too
[16:09] <kenvandine> yeah, not sure i want the overhead of running that :)
[16:09] <Laney> depends if you only ever want the most trivial tests or if actually making sure the thing works is interesting ...
[16:15] <Laney> chromium's deb had some autopkgtests that used selenium
[16:16] <Laney> one of them basically opened the browser, checked the version, and quit it
[16:16] <Laney> not sure, but I would guess that the snap doesn't have anything like that/
[16:16] <Laney> (the other one ran a copy of html5test.com)
[16:28] <oSoMoN> Laney, the snap has the same tests, they're installed in /snap/chromium/current/tests/
[16:28] <oSoMoN> but they're run headless, so no window is shown
[16:28] <oSoMoN> although it's trivial to remove the headless parameter, and they should work equally fine
[16:30] <Laney> nice!
[16:49] <oSoMoN> that'll do for today, have a good evening everyone!