[02:50] <c_smith> where would I put a theme to install it System-wide? it's a neither an Icon theme nor a cursor theme
[02:51] <c_smith> /usr/share/themes, right?
[05:37] <parin> darkxst: Hi. I tried printing g_getenv("DISPLAY") and both the displayconfig code and mutter recognize :0.0
[05:39] <parin> there is no backtrace. GDK_DISPLAY_XDISPLAY (gdk_display_get_default ()); gave an assertion error that it wasn't fed a valid display. Changing it to XOpenDisplay() removed that error but the program crashes with a segfault in meta_monitor_manager_xrandr_read_current()
[07:06] <Uallas> Good Morning
[11:05] <darkxst> parin, hi
[11:08] <darkxst> parin, can you send a patch with your changes (or push it to github and I will take a look)
[11:42] <parin> darkxst: okay
[11:55] <darkxst> parin, and as soon as you get a seg fault you should be firing up gdb and getting a backtrace ;)
[12:54] <parin> darkxst: I've pushed the changes to https://github.com/parinporecha/mutter-compiz/tree/gnome-3-10
[12:54] <parin> darkxst: I do know where the segfault occurs
[12:55] <parin> it's all due to the null display we're getting from gdk_display_get_default
[12:57] <darkxst> maybe you need Xopendisplay there as well?
[12:57] <parin> when I replace it with XOpenDisplay (is the replacement okay ?), we don't get null, but I get this error - X Error of failed request:  BadName (named color or font does not exist)
[12:58] <darkxst> I don't think you can just replace it!
[12:58] <darkxst> you may need both
[12:59] <parin> both, how ?
[13:02] <darkxst> hmm no I was thinking of XopenScreen i suppose
[13:03] <parin> darkxst: I think we're using gdk_display_get_default in a wrong way
[13:03] <parin> in the mutter code, I replaced meta_get_display()->xdisplay with GDK_DISPLAY_XDISPLAY (gdk_display_get_default ());, and it's giving the same error
[13:05] <darkxst> possibly there is some initialization missing?
[13:05] <parin> meta_get_display() calls the same function GDK_DISPLAY_XDISPLAY (gdk_display_get_default ()) in ui.c But, yes there maybe some initialization missing. I'm looking into it
[13:08] <darkxst> parin, whats with all the whitespace cleanups?
[13:09] <parin> some problem with Geany
[13:09] <darkxst> change editor then, it bloats the patches
[13:10] <parin> darkxst: okay, I'll see that it doesn't happen again
[13:13] <darkxst> also I don't really need to see your debug statements ;0
[13:13] <darkxst> ^ that is what gdb is for anyway
[13:43] <parin> darkxst: i was wrong. mutter does get the display from gdk_display_get_default (). Doesn't matter when it's called. The same line when replaced in our displayconfig code, it doesn't work. GdkDisplay doesn't have any function to set default display or something also. I'll ask this on gnome-shell mailing list, see if I get anywhere
[13:45] <darkxst> ok, I'm off for the night, will have a look at it in the morning
[23:21] <roasted> hello friends
[23:22] <roasted> by chance has anybody ever done an in-place upgrade of say 13.04 >> 13.10 while having PPAs installed to bring in the newest Gnome?
[23:31] <darkxst> don't do it
[23:31] <darkxst> ppa-purge PPA's, upgrade, then re-install PPA's
[23:33] <roasted> ah, alright
[23:34] <roasted> I was hoping for a clean break from 13.04 to 13.10, but ppa-purge is a small price to pay I suppose.
[23:36] <darkxst> PPA's are disabled (not purged) when you run an upgrade, from there any packaging changes from the ppa that are not in 13.10 will just confuse the do-release-upgrade
[23:37] <roasted> ah, that's the part I mixed up then.
[23:37] <roasted> purge vs simply disabled.
[23:38] <roasted> so I'd effectively bring 13.04 down to 3.6 before the upgrade then.
[23:38] <darkxst> yeh
[23:39] <roasted> are you the only core dev at this point darkxst?
[23:39] <darkxst> ricotz as well
[23:39] <darkxst> hey I gotta run
[23:39] <roasted> take it easy!