[03:59] <duflu> RAOF: Can you check and confirm Mesa is fixable, and not intrinsically doing the right thing already?... https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1480755/comments/5
[04:02] <RAOF> Checking...
[05:48] <RAOF> Oh, damn.
[05:48] <RAOF> *Of course* it passes under ThreadSanitizer and normally but not under valgrind.
[05:50] <RAOF> *Of course* it passes under ThreadSanitizer and normally but not under valgrind.
[05:50] <RAOF> ...but only when tracking fds?
[05:50] <RAOF> No?
[05:51] <RAOF> Oh, right. --trace-children
[06:24] <duflu> RAOF: Yeah that's a gotcha from binary wrapping. I sent out an email but we've all forgotten now.
[06:24] <duflu> RAOF: P.S. I'm using this tag for the pixel format related issues (and more?): https://bugs.launchpad.net/ubuntu/+source/mesa/+bugs?field.tag=egl-platform-mir
[06:50] <RAOF> Hurray for valgrind accidentally finding race conditions.
[06:51] <RAOF> Also, it'd be *really* nice if we could move into our lambdas.
[07:04] <duflu> RAOF: shared/unique_ptr should do
[07:05] <RAOF> Well, unique_ptr clearly doesn't, because you can't move it into a lambda :)
[07:06] <duflu> RAOF: Parameter by value?
[07:06] <duflu> Or capture
[07:06] <RAOF> Can't by value; it's not copyable.
[07:08] <RAOF> I can emulate what I want with a shared_ptr, but it'd be cleaner without.
[07:09] <duflu> Sweet. In other news, switching my new monitor to DP 1.2 mode Mir now sees 4 DP outputs (multi-stream)
[07:09] <RAOF> Superb
[07:10] <duflu> Still max 3 simultaneous outputs??
[07:10] <duflu> Not sure about that
[07:14] <duflu> Hmm, or was it just a kernel upgrade and I haven't looked in a while
[07:14] <duflu> ?
[07:28] <duflu> RAOF: Yeah confirmed putting the monitor in DP1.2 mode is what gives me twice the outputs available. Unfortunately DP1.2 mode is not understood by the Linux framebuffer and it (along with Plymouth) is in a low-res BIOS mode
[07:28] <duflu> X and Mir both handle it well tho
[07:29] <duflu> I would have thought kernel 4.1 would be more current than that
[07:29] <RAOF> Time for kmscon!
[07:29] <duflu> !
[07:37] <RAOF> I am apparently going to need to fix each and every race in Mir before I can land this thing...
[09:36] <duflu> anpok_...?
[09:36] <duflu> anpok_ ?
[09:39] <anpok_> duflu: tuesday!
[14:46] <anpok> AlbertA: should we land your fix or cherry pick christophers?
[14:48] <AlbertA> anpok: heh I'm about to push the cherry picked solution from Chris
[14:48] <anpok> +1
[19:08] <camako> https://code.launchpad.net/~cemil-azizoglu/mir/add-packaging-for-mir-on-x/+merge/266915/comments/670098
[19:09] <camako> vogons, ^^ known failure?
[19:10] <kdub> not known to me at least
[19:11] <anpok> camako: a fix is about to land
[19:11] <AlbertA> camako: yes: https://code.launchpad.net/~albaguirre/mir/fix-1481034/+merge/266781
[19:12] <anpok> this the shutdown race during the synthetic exception in the input thread
[19:12] <camako> ok thanks... I remember seeing it on other MPs
[23:24] <RAOF> GAH! Why does http://bazaar.launchpad.net/~albaguirre/mir/fix-1481034/revision/2808 compile?
[23:26] <RAOF> Alternatively, why did my attempts to do the same fail to compile?
[23:47] <RAOF> Oh! By moving the std::shared_ptr<promise> rather than the std::promise.
[23:47] <RAOF> Yeah, that'd work ☺


[01:07] <n-iCe> hi
[12:37] <jakey3> i have wireless working on the livecd
[12:37] <jakey3> when i installed the lub 16.04
[12:37] <jakey3> it does not work
[12:38] <Serverhelp> hello?
[12:38] <Serverhelp> anyone there?
[12:39] <hateball> !help | Serverhelp
[12:39] <hateball> jakey3: What wifi chipset?
[12:39] <hateball> jakey3: Broadcom for instance, you may need to install additional packages after install for them to work
[12:40] <hateball> jakey3: run "lspci" in a terminal to determine
[12:40] <jakey3> Centrino Advanced-N 6205 [Taylor Peak]
[12:43] <hateball> jakey3: Oh, so Intel. Hmm, well that *should* work. Is the problem you see no networks at all, or can you not connect to them?
[12:44] <jakey3> i can see them
[12:44] <jakey3> when i try to connect icon goes round for a bit then stops
[12:47] <hateball> jakey3: can you see any messages if you run "dmesg" after trying to connect?
[12:49] <jakey3> hateball: http://paste.ubuntu.com/16705648/
[12:49] <hateball> jakey3: also, this sometimes happens with Intel chipsets. You can "fix" it by disabling 802.11n
[12:50] <hateball> jakey3: as per http://askubuntu.com/questions/663315/unreliable-wireless-connection-with-an-intel-centrino-advanced-n-6230
[12:51] <hateball> Note that you will be restricted to G speeds then
[12:51] <jakey3> will try
[12:51] <jakey3> is it possible that dkms could have donesomething to it
[12:51] <hateball> not really, intel modules come with the kernel, shouldnt need dkms
[12:52] <hateball> jakey3: What one could try however, is installing a later kernel just to try
[12:52] <hateball> !mainline | jakey3
[12:52] <jakey3> i see
[12:53] <jakey3> will give that fix a go
[12:53] <jakey3> other will need to reinstall
[12:53] <hateball> jakey3: it's simple enough to try
[12:53] <jakey3> grrrr
[12:54] <hateball> and testing a different kernel does not need a reinstall either
[12:54] <hateball> And this isnt windows, reinstalling wont (usually) magically fix broken drivers :)
[12:54] <jakey3> hahahaha
[12:54] <jakey3> i though a kick to the machine fixes it
[12:54] <jakey3> :D
[12:56] <hateball> Well sometimes there is no other way than to violently destroy a machine. But I would try module options first, it's cheaper.
[12:56] <jakey3> hehe brb
[12:57] <jakey3> what i doesnt understand is why it works on the live cd
[12:57] <jakey3> *dont
[12:57] <hateball> jakey3: Does it work consistently tho? Usually these problems with the Intel chipsets are intermittent
[12:58] <jakey3> didnt test for to long
[12:58] <jakey3> just opened a broswer
[12:58] <jakey3> went to a few web pages
[12:58] <jakey3> done
[12:58] <hateball> Right, well you have nothing to lose from just trying disabling N
[12:58] <jakey3> brb
[14:28] <mohsen_> Hi, after I set a right to left locale, the panel has too many interferences, the windows are under the icons and half of the file manager icon is on the menus button.
[14:28] <mohsen_> I tried costumizing the panel's settings but no luck.
[14:28] <swift110> hhey all
[14:28] <mohsen_> Is there anything else I can do?
[17:31] <benjarn> anybody can help me to make libreoffice right on lubuntu ?
[17:34] <wxl> benjarn: how is it not right?
[17:37] <benjarn> i have only few letters in the menu
[17:38] <wxl> screen shot?
[17:39] <benjarn> just a minute
[17:44] <benjarn> https://img42.com/Fepz2+
[17:47] <bioterror> looks nice
[17:49] <benjarn> i am performing an apt-get upgrade
[17:49] <bioterror> benjarn, what if you launch libre office writer from the command line?
[17:49] <benjarn> same thing
[17:57] <benjarn> anybody ?
[17:58] <bioterror> benjarn, does it complain anything?
[18:00] <benjarn> i made an upgrade and i still have libreoffice troubles...
[18:01] <benjarn> do you have an idea ?
[18:01] <wxl> i'm thinking of some sort of graphics error
[18:01] <wxl> what version of lubuntu are you on?
[18:03] <benjarn> Lubuntu 14.04 LTS Trusty
[18:03] <benjarn> french version
[18:07] <benjarn> LibreOffice <IP_ADDRESS> 420m0(Build:2)
[18:08] <wxl> what exactly is the "french version?"
[18:08] <benjarn> i am french ( my lubuntu is in french)
[18:09] <wxl> ok, so that's more like "french setting" than it is some separate port of lubuntu
[18:09] <wxl> right?
[18:11] <benjarn> yes
[18:11] <wxl> !info libreoffice trusty
[18:12] <wxl> could you pastebin the results of `apt-cache policy libreoffice`?
[18:12] <benjarn> libreoffice:
[18:12] <benjarn>   Installé : 1:4.2.8-0ubuntu4
[18:12] <benjarn>   Candidat : 1:4.2.8-0ubuntu4
[18:12] <benjarn>  Table de version :
[18:12] <benjarn>  *** 1:4.2.8-0ubuntu4 0
[18:12] <benjarn>         500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/universe i386 Packages
[18:12] <wxl> i DID say pastebin
[18:12] <wxl> !pastebin | benjarn
[18:14] <benjarn> http://paste.ubuntu.com/16713944/
[18:14] <wxl> well too late now :)
[18:15] <benjarn> (yes sorry i'm new to irc)
[18:15] <wxl> libreoffice is gtk i believe
[18:16] <wxl> so were this to be a gtk problem, i'd expect it to be a problem in other applications
[18:16] <wxl> do you have that?
[18:16] <benjarn> never seen
[18:16] <benjarn> not in gimp
[18:16] <benjarn> not in abiword
[18:16] <wxl> k
[18:16] <wxl> dp oy
[18:16] <wxl> oops
[18:16] <wxl> so it's possibly a graphics problem
[18:16] <benjarn> not in gedit neither
[18:17] <wxl> what graphics card do you have and what kernel driver are you using? (pastebin lspci -nnk)
[18:18] <benjarn> http://paste.ubuntu.com/16714064/
[18:19] <wxl> intel i915
[18:19] <wxl> i know we've been having trouble with some intel chip
[18:19] <wxl> although if memory serves that was 16.04
[18:20] <benjarn> my computer is a Dell optiplex 755
[18:21] <wxl> not the same visually, but perhaps turning off anti-aliasing might help https://bugs.documentfoundation.org/show_bug.cgi?id=62480&redirected_from=fdo
[18:27] <benjarn> i tried to turn off but no effect
[18:27] <wxl> system wide/
[18:28] <benjarn> do you think i should upgrade to 16.04?
[18:30] <wxl> it's a good idea in general
[18:30] <benjarn> oki can i do that from command line ?
[18:30] <wxl> sudo do-release-update -d
[18:32] <benjarn> c'est parti !
[18:33] <benjarn> okay thanks guys for your help see you when upgrade is done
[21:47] <n-iCe> hi
[22:28] <Jbmorris289> The official lubuntu channel...hello


[06:36] <pitti> Bonjour tout le monde !
[06:41] <didrocks> hey pitti!
[06:41] <didrocks> how are you ?
[06:41] <pitti> didrocks: bonjour !
[06:42] <pitti> didrocks: quite tired TBH, it was a long night :)
[06:42] <pitti> so many heart attacks
[06:42] <larsu> hi didrocks and pitti!
[06:42] <pitti> larsu: Alter!
[06:42] <didrocks> hey larsu :)
[06:42] <didrocks> pitti: who won at the end ?
[06:42] <didrocks> will we meet you guys ?
[06:42] <pitti> I got up at an outright "normal" time at 8:30 :)
[06:42] <darkxst> hey pitti , didrocks larsu
[06:43] <pitti> didrocks: yes, we will; we won 2:1, but don't ask how :)
[06:43] <larsu> hi darkxst!
[06:43] <didrocks> morning darkxst
[06:43] <pitti> didrocks: so, the big showdown on Friday
[06:43] <didrocks> pitti: ahah, ok, I won't, I'll just say "nice" :)
[06:43] <pitti> didrocks: FRA : GER Friday 18:00 I mean
[06:43] <didrocks> yeah ;)
[06:43] <didrocks> I'm still sure I won't watch it TBH :p
[06:43] <pitti> not that France's game against Nigeria was that much more convincing, so let's see
[06:43] <larsu> pitti: by putting the ball into the goal of the enemy, twice?
[06:44] <didrocks> already had to suffer 10 minutes of to Nigeria-France to order some beers at the bar with seb128
[06:44] <pitti> larsu: you didn't watch it, did you?
[06:44] <didrocks> (it was of course a really packed)
[06:44] <larsu> pitti: lol. no.
[06:44] <pitti> didrocks: poor you
[06:44] <larsu> I donated blood, took a walk, and went to bed fairly early last night
[06:44] <didrocks> pitti: first world issue! :)
[06:44] <pitti> didrocks: I'm really glad that I can at least still be friends with *you* after Friday night!
[06:44]  * didrocks envies you guys being able to donate blood in the evening
[06:45] <didrocks> pitti: ahah, yeah :)
[06:45] <larsu> didrocks: it was more like 5pm (they were available in the school in my street from 4 to 7)
[06:45] <larsu> going too late is bad though, because too many people will be there coming from work
[06:47] <didrocks> larsu: here, there are 2 buildings, both are closing at 3:30pm
[06:47] <didrocks> and they are at 4kms from home
[06:47] <didrocks> so quite hard to leave during the day
[06:48] <didrocks> pitti: you're still up before seb128 if that can reconfort you :)
[06:49] <larsu> didrocks: oh? They don't come around the neighborhoods?
[06:49] <didrocks> larsu: not where I leave, they are doing that close to the business area, but I'm quite far from it
[06:50] <didrocks> going*
[06:50] <larsu> understood
[06:53] <didrocks> ahah, a new IT shop from a brand is opening, and they display that: https://plus.google.com/photos/+ldlc/albums/6030735454222755633/6030735454625964194?pid=6030735454625964194&oid=104301983842916548085
[06:54] <larsu> lol :)
[07:37] <jibel> mvo, can you join #ubuntu-release?
[07:37] <seb128> good morning desktopers!
[07:37] <seb128> hey didrocks pitti mvo jibel
[07:37] <didrocks> hey jibel, seb128!
[07:37] <pitti> bonjour seb128, ça va ! Recontrer à vendredi !
[07:37] <jibel> Good morning seb128 didrocks
[07:37] <seb128> pitti, mvo, larsu, well done, nice game yesterday ;-)
[07:38] <pitti> seb128: well, FSVO "nice" -- the first 30 mins gave all of us a heart attack!
[07:38]  * larsu is unsure what he did…
[07:38] <pitti> (well, and the other 90 mins as well really, but in a slightly better way)
[07:39] <larsu> I'm not sure, but I think pitti knows of a "slightly better way" to have a heart attack
[07:39] <seb128> pitti, yeah, it was nice to watch if you like suspens ;-)
[07:39] <pitti> seb128: c'était une nuit très longue, je suis fatigué
[07:40] <seb128> pitti, tu t'es levé tôt ?
[07:40] <pitti> seb128: non, j'ai me levé à 8h30
[07:40] <pitti> seb128: but of course I woke up with my wife at 5, and didn't really sleep tight after that any more
[07:41] <pitti> seb128: oh, "je suis me levé", not "j'ai me levé" ?
[07:42] <pitti> seb128: I suppose I should learn some French swearing by Friday
[07:43] <seb128> pitti, "je me suis levé" ;-)
[07:43] <seb128> lol
[07:44] <pitti> seb128: what does "never ever was this a foul, you idiot!" mean in French? :-)
[07:44] <mvo> hey seb128
[07:44] <seb128> lol
[07:45] <jibel> mvo, your upload of update-notifier has been rejected, there is no version in the dependency on update-manager. You can talk to RAOF for details.
[07:45] <mvo> jibel: sure, joining now
[07:45] <mvo> jibel: ok, I will do a re-upload right away, but iirc there is no need for a dependency as the code with use os.path.exists() to figure out if it needs it or not
[07:46] <larsu> hm, appearance page in unity-control-center crashes :(
[07:46] <seb128> larsu, bt? missing schemas and gsettings aborts?
[07:47] <larsu> seb128: some assertions about radio button groups not found. I'll have a look later, aftre I finally finish tab theming
[07:47] <larsu> this has been on my todo _forever_
[07:47] <seb128> k
[07:48] <larsu> seb128: speaking of which, do we have a screenshot on how it's supposed to look?
[07:49]  * larsu asks google
[07:49] <seb128> I don't think so
[07:49] <seb128> why? want to change things there?
[07:50] <larsu> no, I want to restore how it's supposed to look and don't have a trusty handy
[07:50] <larsu> I've found a screenshot though
[07:51] <larsu> turns out, theming notebooks is rather messy
[07:51] <larsu> who'd have thought...
[07:51] <seb128> why is it looking different? gtk?
[07:51] <seb128> oh
[07:51] <larsu> yes, after the update. For example, there's a too thick border below tabs
[07:51] <larsu> and frames around the tab header
[08:00] <lool> do you folks get a crash when opening the appearance control panel?
[08:02] <seb128> see what larsu was just saying
[08:03] <seb128> so seems "yes"
[08:03]  * seb128 is on trusty so can't test right now
[08:04] <Laney> hey hey
[08:04] <seb128> Laney, hey, how are you?
[08:05] <Laney> yeah, doing good!
[08:06] <Laney> none of this futbol business to worry about here :-)
[08:06] <Laney> you?
[08:06] <didrocks> morning Laney!
[08:09] <ochosi> hey seb128, may i quickly bug you about https://code.launchpad.net/~ochosi/xdg-utils/support_xfce/+merge/224076 again?
[08:10] <Laney> hey hey didrocks
[08:11] <larsu> hi Laney
[08:13] <darkxst> hey Laney
[08:13] <Noskcaj> ochosi, I notice that the upstream and branch patches are different
[08:14] <ochosi> Noskcaj: well, ubuntu carries a (useless) patch, so ofc they're different
[08:14] <Noskcaj> ok
[08:14] <ochosi> i proposed to drop the patch in ubuntu as well
[08:15] <ochosi> but what i'm primarily interested in (now) and with this MR is an SRU for trusty
[08:15] <ochosi> cause it kinda sucks that the screensaver always kicks in, even if mediaplayers want to inhibit
[08:15] <ochosi> so i kept it minimal
[08:15] <Noskcaj> ok. I've had the same issue
[08:15] <ochosi> yeah, everyone does ;)
[08:16] <seb128> Laney, doing good, thanks ;-)
[08:16] <seb128> ochosi, yeah, no reply from upstream then, I'm just going to upload your change
[08:21] <ochosi> seb128: thanks, i'm willing to work on a different solution with upstream as well, we can always get that into utopic then. but i'd be happy if we can sru this change to trusty and for 14.04.1
[08:21] <seb128> right
[08:26] <didrocks> mvo: pitti: hey, stupid question, but imagine that one function I called GLib.idle_add() on raises an exception, I'm unsure why my try: exception around mainloop.run() doesn't seem to catch it (like a KeyboardInterrupt event), any idea? seems quite common though…
[08:29] <didrocks> I'm trying Ctrl+C in a while True loop and it doesn't seem even to raise the Interrupt
[08:29] <darkxst> didrocks, idle_add probably doesnt run in the main thread?
[08:30] <didrocks> darkxst: it does, let me pastebin a simple example
[08:30] <didrocks> http://paste.ubuntu.com/7730311/
[08:31] <didrocks> when I hit Ctrl + C in the foo function, this should raise an exception…
[08:31] <pitti> didrocks: that's known
[08:31] <pitti> didrocks: pygi can't "tunnel" exceptions through the C layer of callbacks
[08:32] <didrocks> pitti: ok, I'm not that crazy then ;). Any best practice/workaround then?
[08:32] <pitti> didrocks: so your callbacks themselves have to intercept the exceptions and handle them, or pass them to the main thread via global variables, signals, messages, etc.
[08:33] <didrocks> pitti: ok, that makes sense. Thanks Martin! :)
[08:33] <pitti> didrocks: it's not technically multithreading, but behaviourally it's "kind of"
[08:33] <pitti> didrocks: but the main reason is that it's really difficult to propagate exceptions through arbitrary C functions
[08:34] <didrocks> yeah, I guess the conversion isn't really easy, I was just puzzled that even a trivial example wasn't working and was first blaming the input() method or my nested calls :)
[08:34] <didrocks> thanks pitti, will do as you suggest
[08:39] <darkxst> yes pitti's answer is much better than my "guess" at why that would never work!
[08:40] <pitti> well, for synchronous callbacks it could technically work (with lots of effort)
[08:40] <pitti> but with async callbacks, idle handlers etc. the concept itself also makes no sense as they are "kind of" in a separate thread
[08:50] <didrocks> pitti: hum, I propably didn't get exactly what you told then. I tried to have the exception handled in my callback itself, but it didn't work. I reproduced it in that trivial example: http://paste.ubuntu.com/7730381/
[08:51] <pitti> didrocks: I'm not sure about the semantics of KeyboardInterrupt (in fact, first time I hear about it)
[08:51]  * didrocks tries an except without anything then
[08:51] <pitti> didrocks: but python-gi installs its own SIGINT handler
[08:52] <pitti> didrocks: which is mostly due to being backwards compatible how pygobject used to behave
[08:52] <pitti> didrocks: i. e. SIGINT quits the main loop, but doesn't raise an exception
[08:52] <didrocks> pitti: yeah, it's sucked in from what I see
[08:52] <didrocks> hum
[08:52] <didrocks> it doesn't quits the main loop in that example
[08:53] <darkxst> pitti, that was my guess, i.e. separate thread
[08:55] <pitti> interesting; that sounds like a regression then
[08:55] <didrocks> pitti: so, my first example should quit when I hit Ctrl + C, right? http://paste.ubuntu.com/7730311/
[08:56] <pitti> didrocks: no, you'll never get KeyboardInterrupt with pygobject
[08:56] <pitti> didrocks: well, it should quit because pygobject stops the mainloop
[08:56] <didrocks> pitti: but SIGINT should be trapped by the python-gi handler?
[08:57] <didrocks> yeah
[08:57] <pitti> but not through the exception handler
[08:57] <didrocks> it's not the case
[08:57] <didrocks> right right
[08:57] <didrocks> sorry, should have removed the handler
[08:57] <didrocks> pitti: just to be clear, that should quit: http://paste.ubuntu.com/7730404/
[08:57] <pitti> didrocks: correct
[08:57] <didrocks> it doesn't on trusty at least :/
[08:59] <pitti> yeah, that's what I meant with "regression"
[08:59] <pitti> there's a test case in pygobject for SIGINT, but apparently it behaves differently
[08:59]  * pitti bbiab
[08:59] <didrocks> pitti: I wonder if it's not https://bugzilla.gnome.org/show_bug.cgi?id=622084
[09:03] <pitti> didrocks: yeah, there are probably several bugs for that, we already had some a few years ago when I was looking into that
[09:03] <didrocks> pitti: ok, FYI, I used the workaround from the bug description: signal.signal(signal.SIGINT, signal.SIG_DFL)
[09:04] <didrocks> and it works for an INT
[09:04] <didrocks> at least, I would know as well the other cases for the exceptions raised in the callback and adapt my code to it
[09:04] <didrocks> I'm sure it's a declaration of war for Friday!
[09:04]  * didrocks hugs pitti :)
[09:04] <pitti> didrocks: yeah, that'll restore Python's normal SIGINT behaviour with KeyboardInterrupt
[09:38] <seb128> Dir
[09:38] <seb128> ups
[09:39] <seb128> Laney, why did you remove the QDir include in the click changes?
[09:40] <Laney> it's moved to the header
[09:41] <Laney> are you looking at doing a landing soon?
[09:41] <seb128> yes, today or tomorrow
[09:41] <seb128> Saviq has one lined up first to switch to the suru icon theme
[09:41] <seb128> he aims at landing that today
[09:41] <Laney> okay, I think I can fix the rest of the icons based on my earlier investigation
[09:42] <Laney> stupid spec violators
[09:42] <seb128> do you want to do that on the same merge request?
[09:43] <seb128> it might be good to add some comments in there, I'm re-reading the code you "refactored", it seems suboptimal that we need to play with paths and parsing that way, feels like click could be better a providing the info we need
[09:43] <seb128> having the rational of why we need to do that "manual work" could be useful
[09:43] <Laney> k
[09:44] <seb128> thanks
[09:45] <seb128> "Overwrite the icon with the .desktop file's one if we have it. This one is more reliable."
[09:46] <seb128> what's the point of having an icon info if it's not reliable...
[09:48] <Laney> I think the desktop file one is used by the app scope
[09:48] <Laney> so maybe this one can bitrot or something
[09:49] <Laney> although to be fair ...
[09:49]  * Laney notices something
[10:48] <papars> Hi. Can somebody help me? My problem is described here: http://askubuntu.com/questions/490292/dell-fans-not-working
[11:55] <bregma> lool, if you're still having trouble with large text on HiDPI screens, check the Universal Access 'Large Text' setting in the control center -- see bug #1332947
[11:58] <lool> bregma: at the moment the settings panel crashes for me
[11:59] <lool> bregma: but thanks, I've sub-ed there
[11:59] <lool> bregma: and indeed, large text is turned on
[12:20] <Laney> seb128: I pushed a version that finds ALL the icons on my device
[13:32] <sil2100> didrocks: as mentioned, I would like to fetch from launchpad API the list of all bugs with a certain tag
[13:33] <didrocks> sil2100: yeah, I'm afraid you need a bug_target for that, let me reread the doc quickly
[13:33] <sil2100> didrocks: I already asked on #launchpad, but no one knows it seems
[13:33] <sil2100> didrocks: yeah... couldn't find anything, and ubuntu?ws.op=searchTasks only returns ubuntu targetted ones
[13:34] <didrocks> sil2100: you can on project, distro, series, milestones for sure
[13:34] <didrocks> (so not only ubuntu)
[13:34] <didrocks> let me continue to check for available targets
[13:34] <didrocks> I'm sure there is person
[13:34] <didrocks> yeah, person…
[13:34] <sil2100> hmmm...
[13:35] <didrocks> sil2100: project_group is maybe what you want? (but we don't really use project_group in LP, apart from the indicators)
[13:35] <sil2100> Damn, I would have to 'tag' those specific bugs with a certain dummy project then
[13:35] <sil2100> project_group? I wonder what those can be
[13:35]  * sil2100 looks
[13:36] <didrocks> sil2100: yeah, the dummy project is what I did for the unity time
[13:36] <didrocks> you can as well have a team that is subscribed to the bugs
[13:36] <didrocks> and filter on them
[13:36] <didrocks> or ensure they have an ubuntu task
[13:36] <didrocks> and filter on that
[13:37] <sil2100> didrocks: thanks! I'll try to work-around it in that way then ;)
[13:37] <didrocks> that's the 3 easiest options I confirm that is possible (after reareading the doc)
[13:37] <didrocks> yw sil2100 :)
[13:37] <Laney> I think that it's probably deliberate
[13:37] <Laney> to not let people search across the collection of all bugs
[13:37] <didrocks> Laney: well, you can do that for all ubuntu bugs
[13:37] <didrocks> whatever series and so on
[13:37] <sil2100> Yeah, but you can still do that in LP manually, and not sure if people use the API so much
[13:38] <didrocks> which is I guess even bigger that all projects unioned
[13:38] <didrocks> sil2100: there are a lot of people using the API, and if you use a bot, you get kind emails regularly with bots owners :p
[14:12] <seb128> Laney, how did you workaround your issues then print calls were not showing up on stdout from qml?
[14:13] <Laney> use warnings :(
[14:13] <seb128> :/
[14:13] <Laney> I asked in app-devel but nobody replied
[14:27] <Laney> seb128: which bug are you looking at?
[14:28] <seb128> Laney, I just wanted to put a debug print in the click sorting selector, it seems to always be set on "name" even if the gsettings key is false
[14:29] <seb128> did you try to debug that yet?
[14:29] <Laney> no, was going to though
[14:29] <Laney> well, I did some weeks ago
[14:29] <Laney> before I found out about using warnings
[14:46] <seb128> Laney, do you remember what is supposed to set the sort role on start?
[14:46] <seb128> is that the gsettings key being read and a sortRole being written then?
[14:47] <Laney> lemme look
[14:48] <Laney> erm
[14:48] <Laney> when did qtcreator get a windows style file chooser?
[14:48] <seb128> do you have that upstart fix to set the session-id variable?
[14:48] <larsu> Laney: I've noticed the same in qmlscene
[14:48] <larsu> might have happened with the qt 5.3 update?!
[14:49] <Laney> seems likely
[14:49] <Laney> it used GtkFileChooser before
[14:49] <Laney> I have that variable yes
[14:51] <seb128> :-/
[14:55] <larsu> what does qt usually look at to find out which platform it's on? XDG_CURRENT_DESKTOP?
[14:56] <seb128> larsu, GNOME_DESKTOP_SESSION_ID
[14:56] <seb128> oh, sorry, that was qt4
[14:57] <seb128> (https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1305294)
[15:10] <seb128> Laney, you are sure that ever worked since we use the backend rather than the js code we had?
[15:11] <Laney> seb128: I just found the fix
[15:11] <Laney> one liner!
[15:11] <seb128> Laney, great ;-)
[15:11] <Laney> looks like the gsettings isn't hooked up though
[15:11] <seb128> was it a missing init something?
[15:11] <Laney> you have to invalidate the model after re-sorting it
[15:12] <Laney> do you have the bug # handy?
[15:16] <seb128> Laney, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1320160
[15:16] <Laney> ty
[15:17] <Laney> lemme hook up the gsettings key
[15:30] <seb128> oh, it's meeting time!
[15:30] <didrocks> hey! :)
[15:32] <seb128> qengho, Laney, tkamppeter_, larsu, didrocks, hey, it's meeting time
[15:32] <seb128> short list today
[15:32] <qengho> Heya, folks!
[15:32] <brookswarner> morning guys
[15:32] <seb128> Bjoern is on vac, Canada is having a national holiday
[15:32] <qengho> Vacations?
[15:33] <seb128> qengho, hey
[15:33] <seb128> qengho, you can start I guess ;-)
[15:33] <qengho> Okay!
[15:33] <qengho> * Set up chromium-mir build tree. (Current status, upstream bug: linker failures with ozone enabled.)
[15:33] <qengho> * Worked with Legal to satisfy Ad*be that we know how to deliver Fl*sh plugin.
[15:33] <qengho> * Still testing chromium-browser 35.0.1916.153. I delayed to fix a Aura high-dpi geometry problem, but it's taking too long. Just releasing soon.
[15:33] <qengho> EOF
[15:34] <seb128> qengho, thanks
[15:34] <seb128> Laney, hey
[15:35] <Laney> • Continue to fix folks/zeitgeist fallout in Debian, upload new folks upstream.
[15:35] <Laney> • Investigate / cherry-pick fix for glib/gcc-4.9 test failure
[15:35] <Laney> • Fix ubuntu-sso-client adt failure
[15:35] <Laney> • Merges/syncs: vte3 gupnp glade
[15:35] <Laney> • Patch pilot
[15:35] <Laney> • Fix and fwd nautilus segfault upstream (applied, thanks mclasen)
[15:35] <Laney> • Discuss webkigtk/arm64 with Debian
[15:35] <Laney> • Test/discuss gnome-desktop 3.12, give feedback, need to test second round of fixes from Tim
[15:35] <Laney> • u-s-s: show all click icons, make click list sorting work, reviews
[15:35] <Laney> • Chat to fluendo about a segfault in their plugin, get it fixed, upload to Debian & sync
[15:35] <Laney> • Give desktop-next a little warning on its cdimage page directing to the wiki
[15:35] <Laney> • Fight with a flaky VPS
[15:35] <Laney> ☘
[15:36] <seb128> what was the fluendo segfault?
[15:36] <seb128> is that in that lib (don't remember the name) that didn't change for years?
[15:37] <Laney> I had an ancient mp3 that was a bit corrupted
[15:37] <Laney> and its parser didn't like that
[15:37] <Laney> got a mediascanner segfault on every startup because of this
[15:37] <seb128> oh, k
[15:37] <qengho> metadata encoding problem?
[15:38] <seb128> what's the status-quo on the gnome-desktop discussion?
[15:38]  * seb128 lost track
[15:38] <seb128> we are still trying the new service approach?
[15:38] <seb128> rather than robert_ancell code copy one?
[15:39] <Laney> https://core.fluendo.com/gstreamer/trac/changeset/2622/trunk/gst-fluendo-mp3/src/bitstream.c
[15:39] <Laney> yeah just trying darkxst's stuff for now
[15:39] <seb128> k
[15:39] <Laney> but he said he'd be fine doing the other approach if necessary
[15:39] <seb128> right
[15:39] <seb128> let's see how that goes
[15:39] <seb128> Laney, thanks
[15:39] <seb128> tkamppeter_, hey
[15:40] <seb128> no tkamppeter_?
[15:40] <seb128> larsu, hey
[15:41] <larsu> hi!
[15:41] <larsu> last week I did some gsettings-qt cleanup and bug fixing
[15:41] <larsu> added a simpler dbus api to indicator-messages for the push notification guys
[15:42] <larsu> (who I've talked to a lot because libmessaging-menu isn't awesome for their use case on the phone)
[15:42] <larsu> nobody's given me any feedback on that yet, though
[15:42] <larsu> I've also talked to Company and mclasen about the Adwaita -> gtk move and how it effects our theme
[15:43] <larsu> and tested it with master - seems to be fine so far
[15:43] <larsu> also, the dialog/csd patches landed after some cleanup
[15:43] <larsu> hm, I think that's about it ...
[15:43] <seb128> great for master and the csd patches ;-)
[15:44] <seb128> larsu, you got feedback on https://code.launchpad.net/~larsu/indicator-messages/add-simple-dbus-api/+merge/224622
[15:44] <Laney> did you ask push guys for review on the MP?
[15:44] <seb128> but not review feedback
[15:44] <larsu> ah, I've done further work on getting the theme ready for 3.12 (some notebook fixes and getting headerbars to work for us)
[15:44] <seb128> just "user" feedback
[15:44] <seb128> who should be reviewing that?
[15:44] <larsu> seb128: Chipaca is the push notification guy I talked to
[15:44] <seb128> charles?
[15:44] <Laney> fdo notifications sounds nice ;-)
[15:44] <Laney> could we actually have that?
[15:45] <seb128> Laney, don't get larsu started
[15:45] <larsu> seb128: I think ted wanted to do this
[15:45] <Laney> but I want to :(
[15:45] <larsu> Laney: yes, we could, but don't get me started.
[15:45] <seb128> we all would like that here
[15:45] <seb128> but other teams are not on the same line
[15:45] <larsu> ah, some code reviews and the usual bug discussion as well last week. I think that's it then
[15:46] <Laney> ho hum
[15:46] <larsu> seb128: right. There's also some problems with click packaging and org.freedesktop.Application
[15:46] <larsu> and XDG_DATA_DIRS
[15:46] <larsu> I hope those will get sorted sooner rather than later
[15:46] <seb128> right
[15:47] <seb128> let's not go into too much detailed discussion on those topic during the meeting, we could spend an hour on it
[15:47] <larsu> the API I proposed now doesn't have the org.freedesktop.Applicaiton part, otherwise it's very similar to the one GNOME is using now
[15:47] <larsu> so we could consolidate them if we decide that it's worth it
[15:47] <seb128> great
[15:47] <larsu> seb128: ya, sorry.
[15:47] <seb128> larsu, thanks
[15:47] <seb128> nothing to be sorry about ;-)
[15:47]  * seb128 gets confused by the order with the missing Canadians
[15:48] <seb128> I think it's didrocks' turn?
[15:48] <didrocks> yep!
[15:48] <seb128> ;-)
[15:48] <didrocks> * added more and more tests (150+ now) in the developer tools center
[15:48] <didrocks> * shell completion enablement of udtc
[15:48] <didrocks> * fighting/had fun to define a model where I can send arbitrary UI from framework. A lot of force and back and now, expanding it :)
[15:48] <didrocks> * finally, enabling the android studio setup, using that for the base of the future interactions with framework (and will probably refactor + add tests once the base will be done)
[15:48] <didrocks> * some MIRing (still tracker on the list)
[15:48] <didrocks> EOF
[15:48] <charles> seb128, IMO this would be better for ted or tvoss to review; this looks like it's a continuation of the discussion from Malta
[15:48] <seb128> charles, ok, thanks
[15:48] <charles> s/ted/tedg/
[15:49] <seb128> didrocks, you forgot the "fought with python-gi" ;-)
[15:49] <didrocks> I was trying to be politically correct in the notes :p
[15:49] <larsu> charles: I've pinged tedg a couple of times about it - is he on vacation?
[15:49] <Laney> oh cool we got new clutter in release after libinput
[15:49] <seb128> lol
[15:49] <Laney> thanks didrocks!
[15:49] <seb128> ok, let's not get you started about that then :p
[15:49] <didrocks> Laney: yw ;)
[15:49] <didrocks> seb128: yeah :)
[15:49] <seb128> didrocks, thanks
[15:49] <tkamppeter> Sorry, I missed it. Here is my stuff:
[15:49] <seb128> ok, my turn
[15:49] <seb128> ups
[15:49] <tkamppeter> - Got hint to new driver project for proprietary Brother laser printers, "brlaser": https://github.com/pdewacht/brlaser, added entries to OpenPrinting
[15:49] <tkamppeter> - cups-filters: Fixed bug in cups-filters, generating queues pointing to remote raw queues
[15:49] <tkamppeter> - ghostscript: SRU for a crash
[15:49] <tkamppeter> - Mentoring of GSoC students, midterm evaluations
[15:49] <tkamppeter> - Some organizational stuff for OpenPrinting Summit.
[15:49] <seb128> tkamppeter, sure, go ahead
[15:49] <tkamppeter> - Bugs.
[15:50] <seb128> tkamppeter, thanks
[15:50] <seb128> k, my turn this time ;-)
[15:51] <seb128> • debian merges (evince)
[15:51] <seb128> • SRUs (shotwell)
[15:51] <seb128> • sponsoring (synced cinnamon)
[15:51] <seb128> • fixed an issue with the shotwell/online accounts integration
[15:51] <seb128> • landings (overlay-scrollbars)
[15:51] <seb128> • discussed/reviewed the options for gnome-desktop updates/what to do with u-s-d/u-c-c
[15:51] <seb128> reviewed touch settings current designs, looked at some issues, filed some bugs, triaged bugslist
[15:51] <seb128> • bug fixes (shotwell)

[15:51] <Laney> über triaging
[15:52] <seb128> right, did quite some on u-s-s .... there is quite some work to do there :/
[15:52] <charles> larsu, ted is on vacation but I don't know for how many days, checking the calendar now
[15:52] <larsu> Laney: 100 points for proper use of umlauts
[15:53] <Laney> thänkß lärßü
[15:53] <charles> larsu, ah, he's in DC for Independence Day
[15:53] <seb128> ok
[15:53] <larsu> charles: is the the one supposed to work on that api?
[15:53] <seb128> is there any other topic we should discuss?
[15:53] <charles> that's right, we all chatted about that last week
[15:54] <larsu> charles: or can you/tvoss/thostr give input as well?
[15:54] <larsu> the situation is a bit defused now, but only because the push guys did more work than necessary :-/
[15:56] <seb128> seems like that's a wrap then
[15:56] <seb128> thanks everyone
[15:56] <didrocks> thanks!
[15:57] <seb128> Laney, "Some click packages ship spec-violating desktop files" ... shouldn't we fix that/have the click tool refuse to build a .click when the content is invalid?
[15:57] <seb128> "invalid"
[15:58] <Laney> I think it'll result in a spec fix
[15:58] <Laney> to allow relative paths
[15:59] <Laney> but I need to know how the ubuntu app launch stuff works really
[15:59] <Laney> I think it must add some stuff to PATH/XDG_*_DIRS each time


[00:38] <nigelb> akgraner, thank you (was asleep, just waking up :) )
[00:44] <nhandler> akgraner: I got around to listening to you on FLOSS Weekly. It was an interesting episode
[00:45] <akgraner> nhandler, thanks - well interesting means so many things :-)  I hope that is a good interesting
[00:50] <nhandler> akgraner: Yep. It was a nice episode. I got a different sort of perspective about the women in the community. I'm still jealous that I don't qualify for any of these great prize packs you all are giving out ;)
[00:51] <akgraner> nhandler, ;-P
[08:29] <dholbach> good morning
[23:02] <Pendulum> hypa7ia, maco: ping?
[23:05] <hypa7ia> Pendulum: sup!
[23:05] <Pendulum> you were interested in the AAC project, right?
[23:06] <Pendulum> I'm asking for kinda 2 reasons
[23:06] <hypa7ia> remind me what it is?
[23:06] <Pendulum> (that got discussed at my membership meeting)
[23:06]  * hypa7ia has a brain like a sieve these days
[23:06] <hypa7ia> oh right!
[23:06] <hypa7ia> yes yes yes
[23:07] <Pendulum> 1) we're getting closer to a point where we'll be looking for more people and I wanted to check to see who was still interested
[23:07] <hypa7ia> meeeeee
[23:08] <Pendulum> and 2) I think I just volunteered to help resurrect the accessibility team and I wasn't sure if your interest was AAC specific, or general accessibility specific
[23:10] <hypa7ia> i'm interested in accessibility in general
[23:12] <Pendulum> cool
[23:13] <Pendulum> I may poke you for stuff on that at some point
[23:13] <Pendulum> I'm in a weird position where I was trying not to be interested in ubuntu accessibility (just because I *have to* be interested in accessibility everywhere else in my life) and then I started having too many fine motor problems so it became a priority
[23:14] <Pendulum> and I discovered that the team mostly didn't exist anymore and hadn't really done much in years
[23:14] <Pendulum> which I think needs to be fixed
[23:14] <Pendulum> so I'm going to do something about it
[23:22] <hypa7ia> Pendulum: i'm happy to help where i can.  while it sucks that it has to be you taking it on, i'm glad you're feeling up to it :)
[23:23] <Pendulum> hypa7ia: nothing gets me energy like feeling like I can fix some marginalization ;)
[23:23] <Pendulum> or at least make things slightly easier for the next person
[23:24] <Pendulum> not to mention that as far as I can tell all the wiki.ubuntu.com documentation for accessibility stuff is for 6.06 or earlier. which really should be fixed
[23:25] <hypa7ia> wow, yeah
[23:26] <Pendulum> I suspect it's a matter of that's where people have their stable set-ups
[23:26] <Pendulum> especially as from mailing list stuff it sounds like gnome is removing some of the stuff that makes orca work so accessibility may be very broken for lucid or lucid+1 for people with visual impairments
[23:28] <hypa7ia> oh no :(
[23:28] <hypa7ia> sucks that it's happening at lucid
[23:29] <Pendulum> I know :(
[23:29] <hypa7ia> which is also an LTS release
[23:29] <Pendulum> yeah
[23:35] <IdleOne> can someone remind me the ubuntu translations team #?
[23:36] <IdleOne> Good evening btw :-)
[23:37] <Pendulum> #ubuntu-translators
[23:37] <Pendulum> hi IdleOne
[23:37] <IdleOne> thank you Pendulum :-)
[23:37] <IdleOne> and hello
[23:52] <IdleOne> Pendulum: have you done much translation and would you suggest I translate an entire page of a wiki and then post or do a little at a time and have the page live?
[23:53] <IdleOne> right now I am not sure how I should procede :/
[23:53] <IdleOne> having the page live makes it ugly if not completely done
[23:54] <IdleOne> but if I say work on one page how do I let other people know that I am working on it to avoid doubling of efforts
[23:55]  * IdleOne took a big bite and now is trying to figure out how to chew and not spit it out :)
[23:57] <IdleOne> I guess I could put a place holder on the wiki page with info that it is being worked on by me and ask other users to do the same
[23:57] <Pendulum> Pendulum: I have done no translation work. I'm only fluent in English and as the only other language I know is French and there are many more much better French speakers than I, I'd rather just let them do it than need them to fix my mistakes ;)
[23:57] <Pendulum> err
[23:57] <Pendulum> IdleOne: ^^
[23:57] <IdleOne> Pendulum: well I was asking more about what you thought the best way to procede would be.
[23:58] <Pendulum> is this on the UW wiki?
[23:58] <IdleOne> but yeah if you feel like jumping in and doing some translation of the UW-wiki.org that would be great :)
[23:59] <IdleOne> yes
[23:59] <IdleOne> err wiki-UW.org
[23:59] <IdleOne> but yes
[23:59] <Pendulum> do you care if other people work on the same page as long as there's no overlap in actual translation?
[23:59]  * IdleOne failed at simplifying the wiki link :/


[16:56] <pleia2> there's a pcworld article and the ubuntu uk podcast that need summaries (uk podcast writes a blog post about their thing, no need to listen, just write something short based on that)
[17:11] <skellat> pleia2: UUPC done.
[17:13] <pleia2> thank you, feel free to review the summary written for your blog post too :)
[17:14] <skellat> pleia2: I'm cool with it
[17:14] <pleia2> great
[17:14] <skellat> Now I gotta quit stalling and starting scripting out the first Burning Circle in 2 weeks
[17:14] <pleia2> woohoo :)
[17:41] <pleia2> finished up pcworld summary and quick review, copying things to wiki for editors now
[18:25] <pleia2> Unit193: link check? https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue317
[18:25] <pleia2> sent off to editors
[20:04] <Unit193> pleia2: Seems good.
[20:28] <pleia2> thank yo0u
[20:28] <pleia2> -0


[06:47]  * ojwb suddenly remembers he needs an evisitor for .au, but luckily the application approval time seems to be measured in seconds
[22:54] <chilts> ojwb: that was lucky! :)
[22:54] <chilts> are you still on a UK passport?


[00:17] <ali1234> well, it doesn't crash or corrupt any more, so that's something
[00:18] <ali1234> in fact i think it's working perfectly :)
[00:19] <ali1234> or not... it's not copying the pixmap
[00:43] <Unit193> jjfrv8: Welcome back.
[00:44] <jjfrv8> I was working on my desktop and knocked the cable out of my pi :)
[01:00] <ToeTag> Hey, is anyone around that I can ask about the wallpaper submission requests?
[01:00] <ToeTag> I want to make sure that I'm reading a requirement right "No branding assest like "Xubuntu logo" or text to permit use by derivative distributions
[01:01] <ToeTag> So explicitly no text on the wallpapers?
[01:01] <pleia2> in general no text is best, since we can't really translate wallpapers ;)
[01:02] <ToeTag> makes sense
[01:02] <ToeTag> I was surprised at the "no xubuntu logo" requirement. I guess that's very considerate of them
[01:02] <pleia2> yeah, we have downstreams that use xubuntu as a base, we don't want to overbrand
[01:02] <ToeTag> There seems to be no expression of a "submission limit" - anyone see any issues with me submitting multiple cantidates?
[01:03] <pleia2> that's fine
[01:03] <pleia2> I think we might restrict it to 1 next cycle though :)
[01:03] <ToeTag> yeah makes sense
[01:03] <ToeTag> awesome, thanks a lot
[01:03] <ToeTag> really appreciate it
[01:03] <pleia2> thank you!
[01:05] <ali1234> ah! it works!
[01:05] <ali1234> it just doesn't redraw itself now
[01:10] <ali1234> cool. this code now actually works with old style SETROOT wallpapers, and also works with xfdesktop without exploding... and also doesn't have any flickering
[01:34] <ali1234> brainwash, ochosi: please test background branch on my xfwm4 repo... it should fix everything
[01:35] <ali1234> you won't even see the wallpaper flicker if xfdesktop crashes, and if you kill it (5 times) you can even set the wallpaper with hsetroot etc
[01:42] <eric_the_idiot> xfdesktop crashes?
[01:52] <ali1234> crashes/is killed :)
[01:54] <ali1234> eric_the_idiot: this whole epic thing has been about having the wallpaper stay the same from greeter startup to fully logged in... it's now possible, but i had to fix many bugs in the greeter, xfwm4, and xfdesktop :)
[01:55] <ali1234> it all boils down to each one implementing http://www.eterm.org/docs/view.php?doc=ref#trans in a slightly different and incompatible way
[01:55] <eric_the_idiot> any other patches for xfdesktop?
[01:56] <ali1234> tomorrow, yes
[01:56] <ali1234> see the post i just did on xfce-dev
[01:56] <eric_the_idiot> will do
[03:24] <winstonebook> hello
[03:25] <Unit193> Howdy.
[08:53] <ochosi> morning evryone
[08:53] <Noskcaj> evening ochosi
[08:53] <ochosi> ali1234: that sounds great!
[09:32] <knome> hullo
[09:34] <ochosi> heya knome
[09:35] <ochosi> updated the submissions page, as you'll have noticed
[09:35] <knome> yep
[09:36] <ochosi> also added that note with a link to the history
[10:07] <koegs> can you tell me how xfce in xubuntu provides the gtk-3.0 theme-name?
[10:07] <knome> i'm not sure i follow...
[10:07] <koegs> i am trying awesome within xubuntu, but not all gtk(3)-apps use the correct theme although i have ~/.config/gtk-3.0/settings.ini
[10:08] <koegs> when i start the xubuntu-session, all apps have the correct theme, but not in awesome
[10:08] <ochosi> koegs: how do you set your theme in awesome?
[10:09] <ochosi> oh, and, let's take this to #xubuntu
[10:09] <koegs> ochosi: with ~/.gtkrc-2.0 and ~/.config/gtk-3.0/settings.ini
[10:09] <koegs> ok, i wasnt sure because of the awesome-thingy :)
[10:10] <knome> if it isn't suitable for #xubuntu because you have a non-default component, it isn't really suitable in #xubuntu-devel either
[10:10] <knome> i mean, the question is fine, but by your logic...
[10:12] <koegs> yeah, not the best logic :D
[15:01] <slickymaster> good afternoon all
[16:33] <brainwash> ali1234: screen corruption remains and light-locker behaves really odd (cursor jumps around occasionally)
[16:34] <brainwash> and there seems to be a brief black screen flicker when xfdesktop launches
[16:34] <ali1234> reinstall everything
[16:49] <brainwash> ali1234: the black flicker is new since I've compiled the background branch like 30min ago
[16:49] <ali1234> when does it happen?
[16:49] <brainwash> exactly when xfdesktop launches, before the icons get displayed
[16:52] <brainwash> replaced xfwm4, locked the screen and everything works, no screen corruption
[16:52] <brainwash> no cursor jumping
[16:54] <ali1234> replaced with what?
[16:55] <brainwash> mutter
[16:56] <brainwash> or even with the unpatched xfwm4 I guess
[16:58] <ali1234> so what happens if you kill xfdesktop first?
[17:01] <brainwash> it happened even if xfdesktop was not started at all
[17:02] <ochosi> ali1234: sorry, i haven't been able to test your xfwm4 branch up to now, i'll try to get to it though
[17:03] <ochosi> it's the background branch, right?
[17:03] <brainwash> yes, already did some testing
[17:04] <brainwash> but xfwm4 is somehow causing the screen corruption
[17:05] <brainwash> and I've noticed a brief black flicker when xfdesktop launches
[17:05] <ochosi> so what doesn't work for you now?
[17:05] <ochosi> and that's it?
[17:05] <brainwash> well, lets see if you can confirm this black flicker
[17:05] <ochosi> yeah, am about to reboot..
[17:05] <ochosi> brb
[17:07] <ochosi> i don't have any problems with the background branch
[17:07] <ochosi> i mean there is a flicker, but that's xfdesktop
[17:07] <ochosi> because i'm using the unpatched version from the 4.12 PPA atm
[17:07] <brainwash> :D
[17:08] <brainwash> ok, what about lightdm locking?
[17:08] <ochosi> just normal locking or suspend-locking?
[17:08] <brainwash> normal
[17:08] <ochosi> k
[17:08] <brainwash> and/or via "dm-tool lock"
[17:09] <ochosi> totally fine
[17:09] <ochosi> no problems whatsoever with that
[17:09] <brainwash> ok :(
[17:09] <ochosi> could be an amd issue
[17:09] <ochosi> or i dunno
[17:09] <brainwash> I start thinking the same
[17:10] <ochosi> alternatively, how clean is your build/test-env?
[17:10] <brainwash> no hints in any of the log files
[17:10] <ochosi> or have you tried with the open drivers?
[17:10] <brainwash> it's messed up one
[17:10] <brainwash> well, it needs to work with the restricted one
[17:11] <brainwash> but I'll test the open source one too
[17:12] <ali1234> there should not be any flicker at all with the new code
[17:13] <brainwash> and there should not be any theme issue
[17:14] <brainwash> lets wait for ochosi to test the patched xfdesktop
[17:14] <ochosi> ali1234: yeah, i have to switch back to the patched xfdesktop...
[17:14] <ali1234> i didn't patch xfdesktop yet
[17:14] <brainwash> the latest commit?
[17:14] <brainwash> git
[17:15] <ali1234> you should get one transition from the greeter wallpaper to the user wallpaper, and no flicker
[17:15] <ochosi> i'll use git master of xfdesktop now
[17:16] <ali1234> well yeah, you do need *that* patch i guess :)
[17:16] <ali1234> i forgot about that one
[17:16] <ochosi> ;)
[17:16] <ochosi> brb
[17:18] <ochosi> ok, so i do get a brief moment of corruption when xfdesktop loads the wallpaper
[17:18] <ochosi> but there is no grey/white/black flicker
[17:18] <ochosi> i'll try to log out and in again to see whether i can reproduce that
[17:19] <brainwash> corruption?
[17:19] <ochosi> could be the dualhead setup
[17:19] <ochosi> cause my internal display is disabled at the greeter
[17:19] <ochosi> so it flickers briefly when it enables the display with the session
[17:20] <ochosi> and then it seems to draw the wallpaper a bit borked for a split second and then it's there correctly on the second monitor
[17:20] <ochosi> i can try without the external monitor a bit later
[17:20] <brainwash> yeah
[17:20] <brainwash> gtg now, later
[17:22] <ali1234> ah i know what that is
[17:23] <ali1234> it's doing the operations int he wrong order - i had that problem in lightdm
[17:35] <ali1234> i assume you're both familiar with double buffering... the problem is that xfdesktop doesn't do this
[18:12] <ochosi> hmm
[18:12] <ochosi> ali1234: is that easy to implement?
[18:13] <ochosi> bbiab
[19:32] <ali1234>     XFreePixmap (dpy, pixmap);
[19:32] <ali1234> wow, how did i never see that before
[19:34] <ochosi> ali1234: what do you mean?
[19:34] <ali1234> well, i thought all this time something else was freeing the pixmap out from under xfwm4
[19:35] <ali1234> but actually, xfwm4 does it
[19:35] <ali1234> so making that copy is probably unneccesary
[19:35] <ali1234> all it needs to do is NOT free the pixmap unless it created it
[19:37] <ali1234> i'm going to push branches of xfwm4, xfdesktop, and greeter, all with syslog debugging (because order of operations is important)
[19:37] <ali1234> then we can get to the bottom of this finally
[19:39] <ochosi> sweet
[19:40] <ali1234> just tried without the copy and it works
[19:41] <ochosi> bbabl
[19:45] <ali1234> wow, that turns the fix into a one liner
[19:53] <ali1234> actually i bet that fix will fix everything... lol
[19:54] <ali1234> i dunno. maybe it's never appropriate to free the pixmap
[20:00] <ali1234> #xorg has the most users and the least amount of talk :/
[20:00] <brainwash> it fixes what? you said that everything was already working for you
[20:01] <ali1234> yeah, but my "fix" is long winded and unneccessary
[20:01] <ali1234> anyway just because it works for me doesn't mean the code is correct
[20:01] <ali1234> Q i just asked on #xorg: is it valid to create a pixmap, then create a XRender picture from it, then free the pixmap, and carry on using the picture? http://paste.ubuntu.com/6486175/
[20:02] <ali1234> the answer to this question might explain why you still get corruption
[20:03] <ali1234> apparently the answer is it's valid
[20:46] <ochosi> ali1234: hm, there seems to be lots of back and forth, so were do you stand now?
[20:47] <ali1234> well, i'm happy with xfwm4
[20:47] <elfy> lol - I got completely lost some time last week ;)
[20:47] <ali1234> i'm happy with gtk-greeter
[20:47] <ali1234> i'm not happy with xfdesktop yet
[20:49] <ali1234> the trouble is, because there is so much communication between them via atoms, a bug in one can mess up all the others
[20:49] <ali1234> so you see corruption on the xfwm4 root tile, because xfdesktop passed a bad pixmap
[20:49] <ali1234> or you see xfdesktop crash because xfwm4 called XFreePixmap()
[20:49] <ali1234> and so on, so even if 2/3 have correct code, the whole thing can still exlode
[20:50] <ochosi> right
[20:50] <ochosi> it's just strange that a pixmap has to be passed around so much
[20:52] <ali1234> it's prefectly reasonable when you understand it
[20:53] <ali1234> the pixmap has to be shared because the greeter exits before the window manager starts
[20:54] <ali1234> the mechanism that is used to share the pixmap between greeter and wm also is used by xfdesktop
[20:54] <ali1234> but none of them used it properly, so they all fight each other
[20:54] <ali1234> it's not strictly necessary to fix xfdesktop, but i don't like to leave stuff broken
[20:54] <ochosi> what's broken there atm?
[20:55] <ali1234> well it sets it sets the ESETROOT atom, which is like hanging a big sign around it's own neck which reads "Please kill me"
[20:55] <ochosi> that's quite graphic :)
[20:56] <ali1234> it keeps a reference to the pixmap it puts into the atom and reuses it later, after xfwm4 has freed it.... which is why it crashes
[20:57] <ali1234> that is a bug of xfwm4, but... programs which do this should not set ESETROOT
[20:57] <ochosi> but not messing with that atom isn't a solution?
[20:57] <ali1234> no, using the atoms for message passing is absolutely fine
[20:58] <ali1234> just as long as you do it correctly
[20:58] <ochosi> yeah, but is the atom really needed in the desktop?
[20:58] <ali1234> yes, because xfdesktop has no other way to tell the window manager what to render in the root tile
[20:59] <ali1234> now the root tile is hardly ever visible, but that isn't the point
[20:59] <ali1234> the code exists for this, but is broken
[20:59] <ali1234> it shouldn't be broken
[20:59] <ochosi> agreed
[20:59] <ali1234> as i wrote on the ML, there's three ways to use the MONITOR_ROOT_PIXMAP code
[21:00] <ali1234> not at all, all the time, or only at startup
[21:00] <ali1234> i want all three to work, even if we only use one
[21:00] <ali1234> do you know how to remove xfdesktop from the session startup?
[21:06] <ali1234> if this code still doesn't work, it might be that we need to do some server grabs to keep things from happening at the same time
[21:06] <ali1234> i already added that to the greeter, but xfwm4 might need it to
[21:12] <ochosi> not sure, i think xfce4-session starts it
[21:12] <ochosi> but you can remove it from there
[21:12] <ochosi> ali1234: settings-manager > sessions > session
[21:13] <ali1234> it's not in there in mine...
[21:15] <ali1234> ok, bgfix2 branch, please test :)
[21:15] <ali1234> i haven't added debugging yet, just doing that now
[21:33] <ochosi> ali1234: i'm at it
[21:35] <ochosi> do i need anything apart from the bgfix2 branch?
[21:37] <ali1234> well, i;ve just done the debugging for lightdm-gtk-greeter and xfwm4, so hang on 1 second while i push it
[21:38] <ali1234> right please test these branches:
[21:38] <ochosi> ah ok
[21:39] <ali1234> lp:~a-j-buxton/lightdm-gtk-greeter/experimental-debug
[21:39] <ali1234> and bgfix2-debug for xfwm4
[21:39] <ochosi> so those two branches write some logs?
[21:39] <ochosi> or how can i check the debugging stuff
[21:39] <ali1234> yes, all logs go to /var/log/syslog
[21:40] <ochosi> right, it'd be ideal if brainwash could test these, as he's the one seeing troublesome stuff
[21:40] <ali1234> yeah, i need to add logging to xfdesktop too for that... gotta fork that on github first tho
[21:40] <ali1234> also, there might be bugs in my logging code :)
[21:40] <ali1234> that's what you're really testing at this point :)
[21:42] <ochosi> hehe, fine :)
[21:42]  * ochosi puts on the guinea-pig t-shirt
[21:42] <ali1234> so, in order to test, do this: tail -f /var/log/syslog
[21:42] <ali1234> then try killing xfdesktop one time
[21:43] <ali1234> then kill it 5 times and try "hsetroot -color \#ff00ff" - you should see the background change to purple
[21:43] <ochosi> wait, first install the branches, then restart, then kill xfdesktop?[24;2~
[21:43] <ali1234> yeah, oviously you gotta install it all :)
[21:43] <ali1234> anyway you should see stuff like "found pixmap" and so on
[21:44] <ali1234> pastebin all that so i can check it makes sense
[21:44] <ali1234> you should also see "set root pixmap" from lightdm-gtk-greeter, then when xfwm4 starts you should see it find the same pixmap XID
[21:45] <ali1234> also stuff about GrabServer
[21:47] <ochosi> ok, restarting now...
[21:47] <ochosi> brb
[21:50] <ochosi> ok, i'm back
[21:50] <ali1234> just in time for patched xfdesktop
[21:50] <ochosi> holy crap, xfdesktop won't go away
[21:50] <ochosi> i mean it says "no process found"
[21:50] <ochosi> but the wallpaper is still there
[21:51] <ochosi> ah, that's xfwm4 then
[21:51] <ochosi> the hsetroot command didn't work though
[21:52] <ali1234> yeah :)
[21:52] <ochosi> i mean the syntax doesn't work out :)
[21:52] <ali1234> the wallpaper should remain even after xfdesktop is killed - that's the *whole* point :)
[21:52] <ochosi> good, i guess that means that part is working
[21:52] <ochosi> nice
[21:52] <ali1234> oh sorry, hsetroot -solid ...
[21:52] <ochosi> yeah, works
[21:52] <ali1234> git://github.com/ali1234/xfdesktop
[21:52] <ali1234> add that in to the mix please :)
[21:53] <ochosi> and, gahh, my poor eyes!
[21:53] <ochosi> terrible color-choice
[21:53] <ochosi> back to black...
[21:53] <ali1234> \#ff7f00 is nice orange :)
[21:53] <ali1234> xfdesktop is still pushing
[21:54] <ochosi> yeah, i was wondering why i received a message about pulling an empty repo :)
[21:54] <ochosi> that's the problem with these old code-bases
[21:54] <ochosi> lotsa history
[21:54] <ochosi> and my connection is lame
[21:54] <ali1234> well if you have a clone of it already you can just add my repo, it will only fetch the changes
[21:54] <ali1234> git ftw...
[21:55] <ochosi> yeah, it's pretty clever
[21:55] <ali1234> git remote add ali1234 git://github.com/ali1234/xfdesktop && git fetch ali1234 && git checkout ali1234/master
[21:55] <ochosi> i can't understand why they had to create bzr...
[21:55] <ali1234> bzr can probably do this too, but i don't know how
[21:56] <ochosi> ping me when the pushing is done
[21:56] <ali1234> its done
[21:56] <ochosi> cool
[21:58] <ochosi> so i presume restarting xfdesktop is enough?
[21:58] <ali1234> yeah, just kill it (if you did make install)
[21:58] <ali1234> the greeter is the only one that is funny about that stuff
[21:59] <ochosi> ok, done
[21:59] <ochosi> the wallpapers are back
[21:59] <ali1234> you should see it set the pxmap, then xfwm4 will pick up the new pixmap
[21:59] <ochosi> Nov 27 22:58:46 legume xfdesktop[7665]: set root pixmap XID=0x3a00023
[21:59] <ochosi> Nov 27 22:58:46 legume xfwm4[1557]: display=:0.0, screen=0 - found pixmap 0x3a00023
[21:59] <ali1234> perfect
[21:59] <ali1234> this is what should happen. the XID should match
[22:00] <ochosi> it does indeed
[22:00] <ochosi> need more syslog output?
[22:00] <ali1234> only if you have corruption or anything like that
[22:00] <ali1234> try locking the screen :)
[22:00] <ochosi> no, eveything seems fine
[22:00] <ochosi> ok :)
[22:00] <ali1234> you should see that lightdm uses display:1.0
[22:01] <ali1234> and xfwm4 will not notice that pixmap change
[22:01] <ochosi> yeah it does
[22:01] <ochosi> yup, it doesn't
[22:01] <ali1234> as it shouldn't since it's a different display
[22:01] <ochosi> worked perfectly
[22:01] <ali1234> so now we need brainwash to test this, then maybe we see why it corrupts
[22:01] <ochosi> yup
[22:01] <ochosi> although if it is a driver issue, we probably won't
[22:02] <ali1234> perhaps not
[22:02] <ochosi> but still
[22:02] <ochosi> this is quite informative
[22:02] <ali1234> if the log looks okay it can only really be a driver issue :(
[22:02] <ochosi> fwiw, with all the messing around, the greeter doesn't seem to pick up my wallpaper anymore
[22:02] <ochosi> it always seems to display one i haven't used for a while
[22:02] <ali1234> yes, because xfdesktop and accountservice
[22:02] <ochosi> yeah
[22:03] <ochosi> but also when i switched back to the 4.12 PPA
[22:03] <ali1234> it's picking up an old setting - the new xfdesktop uses different keys
[22:03] <ochosi> oh
[22:03] <ochosi> so the patch doesn't work anymore?
[22:03] <ali1234> it's quite messed up for me, i think i need to clear out the settings
[22:03] <ali1234> i haven't aplied the account service patch
[22:03] <ali1234> never even looked at it
[22:03] <ochosi> well, would be nice if that worked again here
[22:04] <ochosi> will now revert to my tabwin branch again
[22:04] <ochosi> there's still some work to do there
[22:04] <ali1234> going to need to update it for the new xfdesktop
[22:08] <ochosi> weird, i was using xfdesktop 4.11 before and i think it worked
[22:09] <ali1234> probably picking out the old key/value
[22:10] <ochosi> probably
[22:10] <ochosi> my desktop settings seem quite oldish
[22:10] <ochosi> think i'll clear them out
[22:11] <slickymaster> night all
[22:12] <ochosi> night slickymaster
[22:12] <slickymaster> hi ochosi
[22:12] <ali1234> brb...
[22:16] <ali1234> i saw the corruption :(
[22:16] <ali1234> i think i know why though
[22:16] <ali1234> also got the missing gtk theme stuff
[22:16] <ali1234> no idea at all what that's about
[22:17] <ochosi> oh
[22:17] <ochosi> i didn't get that
[22:17] <Unit193> "Corruption", black and white lines by chance that go away?
[22:17] <ochosi> no, just a slightly garbled version of my wallpaper for a split-second
[22:18] <ali1234> yes, that's what i mean
[22:18] <ali1234> it's because it sets the root pixmap *before* copying in the wallpaper
[22:18] <ali1234> i had this problem in the greeter but fixed it
[22:18] <ali1234> need to fix in in xfdesktop too
[22:24] <ochosi> right, that sounds promising
[22:25] <ochosi> so it'll be really smooth in the end
[22:26] <ali1234> yeah, it's nearly there now... just needs the xfdesktop fixings now
[22:30] <ali1234> ok, that was easy
[22:31] <ali1234> https://github.com/ali1234/xfdesktop/commit/d88d5405d0b42334d1b1a14b509708f13813c434
[22:31] <ali1234> eric_the_idiot: ^
[22:33] <ali1234> brainwash: testing instructions: http://paste.ubuntu.com/6486852/
[22:34] <slickymaster> elfy, at your disposal https://code.launchpad.net/~slickymaster/ubuntu-manual-tests/ubuntu-manual-tests/+merge/196989
[22:53] <brainwash> ali1234: ok, test results tomorrow, cannot access my test machine at the moment
[22:53] <ochosi> ali1234: nice, all in all your patches really don't look like they hurt at all, they just remove the communication troubles between the components
[22:53] <ali1234> right. i think i've made the code shorter overall too
[22:54] <ali1234> got a really helpful piece of advice from #xorg: use XRenderCreateSolidFill instead of messing about with pixmaps
[22:59] <ochosi> wowza, anyone ever heard of this before? http://gmc-holle.github.io/xfdashboard/
[22:59] <ali1234> hah... no
[23:00] <ochosi> just read about it on the xfce-users ml
[23:00] <ali1234> looks like a weird cross between unity and gnome-shell... my two "favourite" desktops
[23:00] <ochosi> yeah, it's strange, the guy said he's a gnome3 refugee, but then again he seems to want gnome3...
[23:01] <ochosi> and it uses clutter
[23:01] <ali1234> lol
[23:01] <ochosi> which might be important for the stuff he does, but eh...?
[23:02] <ali1234> >.<
[23:02] <ochosi> just makes me wonder why he doesn't just use gnome3 with some xfce components instead
[23:02] <ali1234> or unity
[23:02] <ali1234> does he use a distro that isn't ubuntu?
[23:03] <Unit193> You can install Unity just fine on Arch.
[23:03] <ali1234> yeah but not anywhere else
[23:03] <ali1234> also, "just fine" is a bit of a stretch. there's one guy maintaining the whole unity stack
[23:03] <ali1234> which is about 10x bigger than all of xfce