[00:00] <GridCube> oh it breaks things up
[00:02] <GridCube> should i report a bug for that?
[00:23] <charlie-tca> no
[00:23] <charlie-tca> Hopefully, it will start working soon
[00:42] <GridCube> ok
[04:18]  * GridCube from #xubuntu-es : xubuntu is very polished and cool
[06:08] <Unit193> I got back about midnight, I don't think a test would help at this point :( (And I'm a little dead after helping moving...)
[14:32] <mr_pouit> charlie-tca: I commented on bug 803499, it's also waiting for lightdm (I could also ship this file in xubuntu-default-settings, but it's better if it's in lightdm directly)
[14:32] <ubottu> Launchpad bug 803499 in xubuntu-default-settings (Ubuntu) "Xubuntu session using wrong settings" [High,Triaged] https://launchpad.net/bugs/803499
[14:33] <charlie-tca> Thanks.
[14:33] <mr_pouit> charlie-tca: no, bug 803519 doesn't affect us afaik
[14:33] <ubottu> Launchpad bug 803519 in lightdm (Ubuntu) "Use Unity as a registered XDG environment" [Wishlist,Triaged] https://launchpad.net/bugs/803519
[14:33] <charlie-tca> Okay, just wanted to make sure.
[14:34]  * charlie-tca suspects Unity is making things harder for Xubuntu
[14:34] <mr_pouit> it could affect xfce upstream though
[14:35] <mr_pouit> e.g. if some xfce program uses OnlyShowIn=XFCE;GNOME;, unity folks might want that to be OnlyShowIn=XFCE;GNOME;Unity;
[14:35] <charlie-tca> yeah
[14:36] <charlie-tca> or they might change some of what we had changed, too. Some of the stuff was OnlyShowIn=GNOME and we had to add XFCE to them
[16:44] <jarnos> Would anyone try this by latest development Xubuntu? http://askubuntu.com/questions/51514/internal-display-is-off-is-this-a-bug (note that you might need to change the display ids to match your hardware.)
[16:46] <charlie-tca> What do you mean by try this? Wouldn't a person be required to have matching hardware to know if this works or not>?
[16:54] <jarnos> charlie-tca, I don't know, if you can get the same result by different laptop. xrandr without arguments gives yo
[16:54] <jarnos> u the names of outputs.
[16:55] <charlie-tca> laptop hardware is very specific, normally. Even kernel fixes vary according to the revision of the laptop 
[16:56] <mr_pouit> bah, that's an overly complicated script that does nothing really useful
[16:58] <mr_pouit> he should check the randr output when both displays are enabled, and when the external display is off
[16:58] <mr_pouit> maybe some modes are't available then
[17:00] <jarnos> mr_pouit, well I use a different script by which I can change between laptop display, external display and extended desktop. If I changed the modes in certain order in Natty, it faild. Thus the test script. 
[17:02] <mr_pouit> compare the output of "xrandr -q --verbose" between each step, and you'll see if a mode disappears or something
[17:06] <jarnos> mr_pouit, both outputs have some current mode then, but laptop display is off. 
[17:08] <mr_pouit> try to compare these mods then, maybe the frequency isn't the same when both displays are on, and the screen doesn't like it
[17:09]  * jarnos added an important comment to the askubuntu.com page
[17:16] <jarnos> mr_pouit, there is no such difference between the the steps.
[17:33] <jarnos> Adding lines that turn off and on the external display before setting up extended desktop makes the script work.
[17:36] <jarnos> That has to be before "xrandr --output $INT --auto;" at line 10