/srv/irclogs.ubuntu.com/2013/11/27/#xubuntu-devel.txt

ali1234well, it doesn't crash or corrupt any more, so that's something00:17
ali1234in fact i think it's working perfectly :)00:18
ali1234or not... it's not copying the pixmap00:19
Unit193jjfrv8: Welcome back.00:43
jjfrv8I was working on my desktop and knocked the cable out of my pi :)00:44
ToeTagHey, is anyone around that I can ask about the wallpaper submission requests?01:00
ToeTagI want to make sure that I'm reading a requirement right "No branding assest like "Xubuntu logo" or text to permit use by derivative distributions01:00
ToeTagSo explicitly no text on the wallpapers?01:01
pleia2in general no text is best, since we can't really translate wallpapers ;)01:01
ToeTagmakes sense01:02
ToeTagI was surprised at the "no xubuntu logo" requirement. I guess that's very considerate of them01:02
pleia2yeah, we have downstreams that use xubuntu as a base, we don't want to overbrand01:02
ToeTagThere seems to be no expression of a "submission limit" - anyone see any issues with me submitting multiple cantidates?01:02
pleia2that's fine01:03
pleia2I think we might restrict it to 1 next cycle though :)01:03
ToeTagyeah makes sense01:03
ToeTagawesome, thanks a lot01:03
ToeTagreally appreciate it01:03
pleia2thank you!01:03
ali1234ah! it works!01:05
ali1234it just doesn't redraw itself now01:05
ali1234cool. this code now actually works with old style SETROOT wallpapers, and also works with xfdesktop without exploding... and also doesn't have any flickering01:10
ali1234brainwash, ochosi: please test background branch on my xfwm4 repo... it should fix everything01:34
ali1234you 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 etc01:35
eric_the_idiotxfdesktop crashes?01:42
ali1234crashes/is killed :)01:52
ali1234eric_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:54
ali1234it all boils down to each one implementing http://www.eterm.org/docs/view.php?doc=ref#trans in a slightly different and incompatible way01:55
eric_the_idiotany other patches for xfdesktop?01:55
ali1234tomorrow, yes01:56
ali1234see the post i just did on xfce-dev01:56
eric_the_idiotwill do01:56
winstonebookhello03:24
Unit193Howdy.03:25
ochosimorning evryone08:53
Noskcajevening ochosi 08:53
ochosiali1234: that sounds great!08:53
knomehullo09:32
ochosiheya knome 09:34
ochosiupdated the submissions page, as you'll have noticed09:35
knomeyep09:35
ochosialso added that note with a link to the history09:36
koegscan you tell me how xfce in xubuntu provides the gtk-3.0 theme-name?10:07
knomei'm not sure i follow...10:07
koegsi am trying awesome within xubuntu, but not all gtk(3)-apps use the correct theme although i have ~/.config/gtk-3.0/settings.ini10:07
koegswhen i start the xubuntu-session, all apps have the correct theme, but not in awesome10:08
ochosikoegs: how do you set your theme in awesome?10:08
ochosioh, and, let's take this to #xubuntu10:09
koegsochosi: with ~/.gtkrc-2.0 and ~/.config/gtk-3.0/settings.ini10:09
koegsok, i wasnt sure because of the awesome-thingy :)10:09
knomeif it isn't suitable for #xubuntu because you have a non-default component, it isn't really suitable in #xubuntu-devel either10:10
knomei mean, the question is fine, but by your logic...10:10
koegsyeah, not the best logic :D10:12
slickymastergood afternoon all15:01
brainwashali1234: screen corruption remains and light-locker behaves really odd (cursor jumps around occasionally)16:33
brainwashand there seems to be a brief black screen flicker when xfdesktop launches16:34
ali1234reinstall everything16:34
brainwashali1234: the black flicker is new since I've compiled the background branch like 30min ago16:49
ali1234when does it happen?16:49
brainwashexactly when xfdesktop launches, before the icons get displayed16:49
brainwashreplaced xfwm4, locked the screen and everything works, no screen corruption16:52
brainwashno cursor jumping16:52
ali1234replaced with what?16:54
brainwashmutter16:55
brainwashor even with the unpatched xfwm4 I guess16:56
ali1234so what happens if you kill xfdesktop first?16:58
brainwashit happened even if xfdesktop was not started at all17:01
ochosiali1234: sorry, i haven't been able to test your xfwm4 branch up to now, i'll try to get to it though17:02
ochosiit's the background branch, right?17:03
brainwashyes, already did some testing17:03
brainwashbut xfwm4 is somehow causing the screen corruption17:04
brainwashand I've noticed a brief black flicker when xfdesktop launches17:05
ochosiso what doesn't work for you now?17:05
ochosiand that's it?17:05
brainwashwell, lets see if you can confirm this black flicker17:05
ochosiyeah, am about to reboot..17:05
ochosibrb17:05
ochosii don't have any problems with the background branch17:07
ochosii mean there is a flicker, but that's xfdesktop17:07
ochosibecause i'm using the unpatched version from the 4.12 PPA atm17:07
brainwash:D17:07
brainwashok, what about lightdm locking?17:08
ochosijust normal locking or suspend-locking?17:08
brainwashnormal17:08
ochosik17:08
brainwashand/or via "dm-tool lock"17:08
ochositotally fine17:09
ochosino problems whatsoever with that17:09
brainwashok :(17:09
ochosicould be an amd issue17:09
ochosior i dunno17:09
brainwashI start thinking the same17:09
ochosialternatively, how clean is your build/test-env?17:10
brainwashno hints in any of the log files17:10
ochosior have you tried with the open drivers?17:10
brainwashit's messed up one17:10
brainwashwell, it needs to work with the restricted one17:10
brainwashbut I'll test the open source one too17:11
ali1234there should not be any flicker at all with the new code17:12
brainwashand there should not be any theme issue17:13
brainwashlets wait for ochosi to test the patched xfdesktop17:14
ochosiali1234: yeah, i have to switch back to the patched xfdesktop...17:14
ali1234i didn't patch xfdesktop yet17:14
brainwashthe latest commit?17:14
brainwashgit17:14
ali1234you should get one transition from the greeter wallpaper to the user wallpaper, and no flicker17:15
ochosii'll use git master of xfdesktop now17:15
ali1234well yeah, you do need *that* patch i guess :)17:16
ali1234i forgot about that one17:16
ochosi;)17:16
ochosibrb17:16
ochosiok, so i do get a brief moment of corruption when xfdesktop loads the wallpaper17:18
ochosibut there is no grey/white/black flicker17:18
ochosii'll try to log out and in again to see whether i can reproduce that17:18
brainwashcorruption?17:19
ochosicould be the dualhead setup17:19
ochosicause my internal display is disabled at the greeter17:19
ochosiso it flickers briefly when it enables the display with the session17:19
ochosiand then it seems to draw the wallpaper a bit borked for a split second and then it's there correctly on the second monitor17:20
ochosii can try without the external monitor a bit later17:20
brainwashyeah17:20
brainwashgtg now, later17:20
ali1234ah i know what that is17:22
ali1234it's doing the operations int he wrong order - i had that problem in lightdm17:23
ali1234i assume you're both familiar with double buffering... the problem is that xfdesktop doesn't do this17:35
ochosihmm18:12
ochosiali1234: is that easy to implement?18:12
ochosibbiab18:13
ali1234    XFreePixmap (dpy, pixmap);19:32
ali1234wow, how did i never see that before19:32
ochosiali1234: what do you mean?19:34
ali1234well, i thought all this time something else was freeing the pixmap out from under xfwm419:34
ali1234but actually, xfwm4 does it19:35
ali1234so making that copy is probably unneccesary19:35
ali1234all it needs to do is NOT free the pixmap unless it created it19:35
ali1234i'm going to push branches of xfwm4, xfdesktop, and greeter, all with syslog debugging (because order of operations is important)19:37
ali1234then we can get to the bottom of this finally19:37
ochosisweet19:39
ali1234just tried without the copy and it works19:40
ochosibbabl19:41
ali1234wow, that turns the fix into a one liner19:45
ali1234actually i bet that fix will fix everything... lol19:53
ali1234i dunno. maybe it's never appropriate to free the pixmap19:54
ali1234#xorg has the most users and the least amount of talk :/20:00
brainwashit fixes what? you said that everything was already working for you20:00
ali1234yeah, but my "fix" is long winded and unneccessary20:01
ali1234anyway just because it works for me doesn't mean the code is correct20:01
ali1234Q 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:01
ali1234the answer to this question might explain why you still get corruption20:02
ali1234apparently the answer is it's valid20:03
ochosiali1234: hm, there seems to be lots of back and forth, so were do you stand now?20:46
ali1234well, i'm happy with xfwm420:47
elfylol - I got completely lost some time last week ;)20:47
ali1234i'm happy with gtk-greeter20:47
ali1234i'm not happy with xfdesktop yet20:47
ali1234the trouble is, because there is so much communication between them via atoms, a bug in one can mess up all the others20:49
ali1234so you see corruption on the xfwm4 root tile, because xfdesktop passed a bad pixmap20:49
ali1234or you see xfdesktop crash because xfwm4 called XFreePixmap()20:49
ali1234and so on, so even if 2/3 have correct code, the whole thing can still exlode20:49
ochosiright20:50
ochosiit's just strange that a pixmap has to be passed around so much20:50
ali1234it's prefectly reasonable when you understand it20:52
ali1234the pixmap has to be shared because the greeter exits before the window manager starts20:53
ali1234the mechanism that is used to share the pixmap between greeter and wm also is used by xfdesktop20:54
ali1234but none of them used it properly, so they all fight each other20:54
ali1234it's not strictly necessary to fix xfdesktop, but i don't like to leave stuff broken20:54
ochosiwhat's broken there atm?20:54
ali1234well 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
ochosithat's quite graphic :)20:55
ali1234it keeps a reference to the pixmap it puts into the atom and reuses it later, after xfwm4 has freed it.... which is why it crashes20:56
ali1234that is a bug of xfwm4, but... programs which do this should not set ESETROOT20:57
ochosibut not messing with that atom isn't a solution?20:57
ali1234no, using the atoms for message passing is absolutely fine20:57
ali1234just as long as you do it correctly20:58
ochosiyeah, but is the atom really needed in the desktop?20:58
ali1234yes, because xfdesktop has no other way to tell the window manager what to render in the root tile20:58
ali1234now the root tile is hardly ever visible, but that isn't the point20:59
ali1234the code exists for this, but is broken20:59
ali1234it shouldn't be broken20:59
ochosiagreed20:59
ali1234as i wrote on the ML, there's three ways to use the MONITOR_ROOT_PIXMAP code20:59
ali1234not at all, all the time, or only at startup21:00
ali1234i want all three to work, even if we only use one21:00
ali1234do you know how to remove xfdesktop from the session startup?21:00
ali1234if 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 time21:06
ali1234i already added that to the greeter, but xfwm4 might need it to21:06
ochosinot sure, i think xfce4-session starts it21:12
ochosibut you can remove it from there21:12
ochosiali1234: settings-manager > sessions > session 21:12
ali1234it's not in there in mine...21:13
ali1234ok, bgfix2 branch, please test :)21:15
ali1234i haven't added debugging yet, just doing that now21:15
ochosiali1234: i'm at it21:33
ochosido i need anything apart from the bgfix2 branch?21:35
ali1234well, i;ve just done the debugging for lightdm-gtk-greeter and xfwm4, so hang on 1 second while i push it21:37
ali1234right please test these branches:21:38
ochosiah ok21:38
ali1234lp:~a-j-buxton/lightdm-gtk-greeter/experimental-debug21:39
ali1234and bgfix2-debug for xfwm421:39
ochosiso those two branches write some logs?21:39
ochosior how can i check the debugging stuff21:39
ali1234yes, all logs go to /var/log/syslog21:39
ochosiright, it'd be ideal if brainwash could test these, as he's the one seeing troublesome stuff21:40
ali1234yeah, i need to add logging to xfdesktop too for that... gotta fork that on github first tho21:40
ali1234also, there might be bugs in my logging code :)21:40
ali1234that's what you're really testing at this point :)21:40
ochosihehe, fine :)21:42
* ochosi puts on the guinea-pig t-shirt21:42
ali1234so, in order to test, do this: tail -f /var/log/syslog21:42
ali1234then try killing xfdesktop one time21:42
ali1234then kill it 5 times and try "hsetroot -color \#ff00ff" - you should see the background change to purple21:43
ochosiwait, first install the branches, then restart, then kill xfdesktop?[24;2~21:43
ali1234yeah, oviously you gotta install it all :)21:43
ali1234anyway you should see stuff like "found pixmap" and so on21:43
ali1234pastebin all that so i can check it makes sense21:44
ali1234you should also see "set root pixmap" from lightdm-gtk-greeter, then when xfwm4 starts you should see it find the same pixmap XID21:44
ali1234also stuff about GrabServer21:45
ochosiok, restarting now...21:47
ochosibrb21:47
ochosiok, i'm back21:50
ali1234just in time for patched xfdesktop21:50
ochosiholy crap, xfdesktop won't go away21:50
ochosii mean it says "no process found"21:50
ochosibut the wallpaper is still there21:50
ochosiah, that's xfwm4 then21:51
ochosithe hsetroot command didn't work though21:51
ali1234yeah :)21:52
ochosii mean the syntax doesn't work out :)21:52
ali1234the wallpaper should remain even after xfdesktop is killed - that's the *whole* point :)21:52
ochosigood, i guess that means that part is working21:52
ochosinice21:52
ali1234oh sorry, hsetroot -solid ...21:52
ochosiyeah, works21:52
ali1234git://github.com/ali1234/xfdesktop21:52
ali1234add that in to the mix please :)21:52
ochosiand, gahh, my poor eyes!21:53
ochositerrible color-choice21:53
ochosiback to black...21:53
ali1234\#ff7f00 is nice orange :)21:53
ali1234xfdesktop is still pushing21:53
ochosiyeah, i was wondering why i received a message about pulling an empty repo :)21:54
ochosithat's the problem with these old code-bases21:54
ochosilotsa history21:54
ochosiand my connection is lame21:54
ali1234well if you have a clone of it already you can just add my repo, it will only fetch the changes21:54
ali1234git ftw...21:54
ochosiyeah, it's pretty clever21:55
ali1234git remote add ali1234 git://github.com/ali1234/xfdesktop && git fetch ali1234 && git checkout ali1234/master21:55
ochosii can't understand why they had to create bzr...21:55
ali1234bzr can probably do this too, but i don't know how21:55
ochosiping me when the pushing is done21:56
ali1234its done21:56
ochosicool21:56
ochosiso i presume restarting xfdesktop is enough?21:58
ali1234yeah, just kill it (if you did make install)21:58
ali1234the greeter is the only one that is funny about that stuff21:58
ochosiok, done21:59
ochosithe wallpapers are back21:59
ali1234you should see it set the pxmap, then xfwm4 will pick up the new pixmap21:59
ochosiNov 27 22:58:46 legume xfdesktop[7665]: set root pixmap XID=0x3a0002321:59
ochosiNov 27 22:58:46 legume xfwm4[1557]: display=:0.0, screen=0 - found pixmap 0x3a0002321:59
ali1234perfect21:59
ali1234this is what should happen. the XID should match21:59
ochosiit does indeed22:00
ochosineed more syslog output?22:00
ali1234only if you have corruption or anything like that22:00
ali1234try locking the screen :)22:00
ochosino, eveything seems fine22:00
ochosiok :)22:00
ali1234you should see that lightdm uses display:1.022:00
ali1234and xfwm4 will not notice that pixmap change22:01
ochosiyeah it does22:01
ochosiyup, it doesn't22:01
ali1234as it shouldn't since it's a different display22:01
ochosiworked perfectly22:01
ali1234so now we need brainwash to test this, then maybe we see why it corrupts22:01
ochosiyup22:01
ochosialthough if it is a driver issue, we probably won't22:01
ali1234perhaps not22:02
ochosibut still22:02
ochosithis is quite informative22:02
ali1234if the log looks okay it can only really be a driver issue :(22:02
ochosifwiw, with all the messing around, the greeter doesn't seem to pick up my wallpaper anymore22:02
ochosiit always seems to display one i haven't used for a while22:02
ali1234yes, because xfdesktop and accountservice22:02
ochosiyeah22:02
ochosibut also when i switched back to the 4.12 PPA22:03
ali1234it's picking up an old setting - the new xfdesktop uses different keys22:03
ochosioh22:03
ochosiso the patch doesn't work anymore?22:03
ali1234it's quite messed up for me, i think i need to clear out the settings22:03
ali1234i haven't aplied the account service patch22:03
ali1234never even looked at it22:03
ochosiwell, would be nice if that worked again here22:03
ochosiwill now revert to my tabwin branch again22:04
ochosithere's still some work to do there22:04
ali1234going to need to update it for the new xfdesktop22:04
ochosiweird, i was using xfdesktop 4.11 before and i think it worked22:08
ali1234probably picking out the old key/value22:09
ochosiprobably22:10
ochosimy desktop settings seem quite oldish22:10
ochosithink i'll clear them out22:10
slickymasternight all22:11
ochosinight slickymaster 22:12
slickymasterhi ochosi 22:12
ali1234brb...22:12
ali1234i saw the corruption :(22:16
ali1234i think i know why though22:16
ali1234also got the missing gtk theme stuff22:16
ali1234no idea at all what that's about22:16
ochosioh22:17
ochosii didn't get that22:17
Unit193"Corruption", black and white lines by chance that go away?22:17
ochosino, just a slightly garbled version of my wallpaper for a split-second22:17
ali1234yes, that's what i mean22:18
ali1234it's because it sets the root pixmap *before* copying in the wallpaper22:18
ali1234i had this problem in the greeter but fixed it22:18
ali1234need to fix in in xfdesktop too22:18
ochosiright, that sounds promising22:24
ochosiso it'll be really smooth in the end22:25
ali1234yeah, it's nearly there now... just needs the xfdesktop fixings now22:26
ali1234ok, that was easy22:30
ali1234https://github.com/ali1234/xfdesktop/commit/d88d5405d0b42334d1b1a14b509708f13813c43422:31
ali1234eric_the_idiot: ^22:31
ali1234brainwash: testing instructions: http://paste.ubuntu.com/6486852/22:33
slickymasterelfy, at your disposal https://code.launchpad.net/~slickymaster/ubuntu-manual-tests/ubuntu-manual-tests/+merge/19698922:34
brainwashali1234: ok, test results tomorrow, cannot access my test machine at the moment22:53
ochosiali1234: nice, all in all your patches really don't look like they hurt at all, they just remove the communication troubles between the components22:53
ali1234right. i think i've made the code shorter overall too22:53
ali1234got a really helpful piece of advice from #xorg: use XRenderCreateSolidFill instead of messing about with pixmaps22:54
ochosiwowza, anyone ever heard of this before? http://gmc-holle.github.io/xfdashboard/22:59
ali1234hah... no22:59
ochosijust read about it on the xfce-users ml23:00
ali1234looks like a weird cross between unity and gnome-shell... my two "favourite" desktops23:00
ochosiyeah, it's strange, the guy said he's a gnome3 refugee, but then again he seems to want gnome3...23:00
ochosiand it uses clutter23:01
ali1234lol23:01
ochosiwhich might be important for the stuff he does, but eh...?23:01
ali1234>.<23:02
ochosijust makes me wonder why he doesn't just use gnome3 with some xfce components instead23:02
ali1234or unity23:02
ali1234does he use a distro that isn't ubuntu?23:02
Unit193You can install Unity just fine on Arch.23:03
ali1234yeah but not anywhere else23:03
ali1234also, "just fine" is a bit of a stretch. there's one guy maintaining the whole unity stack23:03
ali1234which is about 10x bigger than all of xfce23:03

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!