[00:43] <britt> can someone take a look at bug 1132033 for me
[00:46] <darkxst> britt, you need to re-enable the background plugin
[00:46] <britt> how do I do that exactly?
[00:46] <darkxst> dconf-editor
[00:46] <britt> and why does it turn off only with fglrx?
[00:47] <britt> with OS drivers, without touching any dconf settings, it works great
[00:47] <darkxst> no idea, but if you have ubuntu-settings installed then it will be disabled
[00:48] <britt> I dont
[00:48] <darkxst> check org.gnome.settings-daemon.plugins.background
[00:48] <britt> I dont think it's a plugin issue. Because when I have fglrx installed and I toggle file manager handling desktop it alternates working normally and not
[00:49] <britt> well I dont have fglrx installed but it says it is active
[00:49] <britt> would fglrx disable that?
[00:49] <britt> that would be odd
[00:49] <darkxst> don't think so
[00:49] <darkxst> but I dont use fglrx
[00:50] <britt> is it possible that there is some incompatibility between the new gnome-shell package that we have and fglrx? Because using gnome-shell 3.6 on 12.10 worked great.
[00:50] <britt> Because I can point out two other bugs with the current version of gnome-shell
[00:51] <darkxst> britt, which version are you using?
[00:51] <darkxst> and what are the other 2 bugs?
[00:51] <britt> I'm using 13.04 raring dev, and running gnome shell 3.6.3.1-0ubuntu1
[00:52] <britt> and the two bugs are bug 1131104, and another where with dual monitors theres about a 50pixel region on the bottom where the mouse gets hung up on the main monitor
[00:54] <britt> and by "hung" up, I mean that in the notification region on the main monitor I cannot pan to the second monitor. It gets stuck on the screen edge
[00:56] <darkxst> first is a pointer barrier
[00:56] <darkxst> I though it had been removed but maybe that happened in 3.7
[00:56] <britt> perhaps
[00:56] <darkxst> its the same height as the messagetray?
[00:57] <britt> yes exactly the same
[00:57] <britt> though the barrier is up whether the message tray is showing or not
[00:58] <britt> the other bug was where AM/PM time is not working
[00:58] <britt> it is only showing 24 hour time, no matter how it is set in "Date and Time Settings"
[01:00] <darkxst> is there a launchpad bug for the barrier thing? I will backport the patch
[01:01] <britt> no I didn't report that one. Would you like me to?
[01:01] <darkxst> yes
[01:01] <britt> ok give me a few min for the bug report to upload
[01:02] <britt> do you know anything about the AM/PM clock issue?
[01:02] <darkxst> no, but its working fine in 3.7
[01:03] <britt> is raring sticking with 3.6 or will 3.8 make it into the gnome-3ppa?
[01:03] <darkxst> the ISO's will be 3.6
[01:03] <darkxst> but 3.8 will be available via gnome3-staging ppa
[01:03] <darkxst> ^are
[01:04] <britt> that's good, though I know a lot of people that use this version of ubuntu don't use the ppa
[01:04] <britt> which means that gnome-shell-3.6 needs to get the bugs worked out :-/
[01:06] <britt> ok the cursor barrier is bug 1132308
[01:16] <britt> well I hope the AM/PM issue and the fglrx issue get fixed by launch. That would be unfortunate if they weren't
[01:16] <britt> I dont know what I can do to help though
[01:17] <jbicha> britt: could you report the time bug too?
[01:18] <britt> that one is reported bug 1131104
[01:24] <darkxst> brit is time broken on screenshield also?
[01:25] <jbicha> darkxst: gnome-shell 3.7.90 is in the staging PPA if you want to see if that improves the login transition for you
[01:26] <darkxst> jbicha, that patch that fixes that landed after .90
[01:27] <britt> is the gnome-shell package in 13.04 the same as in 12.10?
[01:27] <darkxst> britt, mostly yes
[01:27] <britt> or at least in the gnome3 ppa for 12.10?
[01:27] <britt> hrm, in 12.10 I didn't have any of these same bugs
[01:27] <britt> does that mean that the issue is in a different package?
[01:28] <darkxst>  is the clock working in the screenshield?
[01:29] <darkxst> looks like the time is pulled straight from gnome-desktop
[01:29] <britt> is that the same as the lockscreen? Both the login screen and the lock screen show the same 24 hour time, regardless of the settings in date and time
[01:29] <darkxst> settings panel display correct though?
[01:30] <britt> yes in the settings panel the toggle switch is set to AM/PM
[01:30] <britt> and it shows it in am/pm in the settings panel
[01:31] <britt> though the actually top panel/lock screen/login screen all show 24 hour time
[01:31] <darkxst> try this in lg
[01:31] <darkxst> wc = new imports.gi.GnomeDesktop.WallClock()
[01:31] <darkxst> wc.clock
[01:31] <britt> where should I paste that coad?
[01:31] <britt> code*
[01:35] <darkxst> Alt+F2, lg
[01:37] <britt> all that did was print me the date and time (in 24 hour time)
[01:37] <darkxst> so gnome-desktop is broken
[01:37] <darkxst> no gnome-shell
[01:38] <darkxst> or perhaps g-s-d
[01:38] <britt> I dont know :-/
[01:39] <britt> dconf shows 12h time, so whatever it is isn't listening to dconf
[01:39] <britt> the other settings are working though like "show second" and "show date"
[01:40] <darkxst> perhaps this https://bugzilla.gnome.org/show_bug.cgi?id=690703
[01:41] <britt> is there a way we can pull in that fix?
[01:41] <darkxst> sure
[01:41] <britt> http://git.gnome.org/browse/gnome-desktop/commit/?id=0940370f82730359a7771aae750136e3fe6bfaa9
[01:42] <britt> seems like it's just a boolean value set incorrectly
[01:42] <britt> at least from what I am reading
[01:44] <britt> hey I made progress on the fgrlx issue in gnome-shell
[01:44] <britt> https://bugs.freedesktop.org/show_bug.cgi?id=56657
[01:44] <britt> apparently it is attributed to cairo
[01:47] <britt> fglrx (and apparently xf86-video-intel also) and cairo 1.12.6 aren't playing nicely
[01:47] <britt> they reported rolling back to cairo 1.12.2 fixes the issue
[01:48] <britt> hrm it looks like we are on 1.12.14
[01:48] <britt> ugh
[01:49] <britt> well maybe a newer fglrx version will work. they're still running a super outdated build which is crap
[01:52] <darkxst> fglrx is just crap ;)
[01:54] <britt> lol I know. I need it for my graphics card to do anything remotely usefull with 3d though. And 12.10 and fglrx worked fine together
[01:54] <britt> and the 13.1 drivers were supposed to make things better, but for some reason ubuntu refuses to upgrade fglrx, even in the fglrx-updates package which is MEANT for updates lol
[01:56] <britt> well if the issue is with cairo...then I have no clue on who would help fix this bug
[01:56] <darkxst> britt, attach the upstream bug to your report
[01:57] <britt> I am. Can you possible bring in the cairo and the fglrx people to the bug report? I cannot change it's status
[01:58] <darkxst> britt, you should be able to add them using "also affects distribution"
[02:00] <britt> nice thank you. I didn't know I could do that
[02:02] <britt> well hopefully that gets worked out. TBH i'm hoping that a new fglrx version will work the issue out passively
[02:02] <britt> we'll see
[02:02] <britt> is there anything else I should do for the other two bugs or do you and jbicha have it?
[02:02] <darkxst> britt, you could try fglrx on xorg-edgers ppa
[02:03] <darkxst> britt, looking at clock thing now, that other patch doesnt apply in 3.6
[02:04] <britt> ergh
[02:05] <britt> I did use the xorg-edgers ppa, it's the same issue. They're also running the same fglrx version (though it's marked as beta6, so I dont know what that is)
[02:05] <darkxst> it should be the latest fglrx available
[02:05] <britt> thank you for looking into these issues. I, and quite possibly everyone, greatly appreciate your help
[02:05] <britt> it isn't unfortunately
[02:06] <darkxst> britt, you could ask ricotz next time he is around
[02:06] <britt> maybe theres probems with newer fglrx versions and they're holding off on it. Is rocotz an amd user?
[02:07] <britt> ooh I now see hes the maintainer for the edgers ppa haha
[02:07] <darkxst> not sure, but he uploaded the fglrx
[02:07] <britt> I maybe will ask him
[02:07] <britt> he is also the uploader for cairo
[02:07] <britt> maybe I can get two birds with one stone
[02:10] <darkxst> britt, just pushed an updated gnome-desktop to my ppa, if you can try it later once it builds
[02:10] <britt> absolutely, I'll report back
[02:10] <britt> it's weird that the gnome-desktop commit woudn't apply considering it was made just 2 months ago
[02:10] <darkxst> britt, it sits on another patch that wasnt in 3.6
[02:11] <darkxst> so I pulled that one in as well
[02:11] <britt> I see
[02:11] <britt> oh wow
[02:11] <darkxst> https://launchpad.net/~darkxst/+archive/ppa
[02:11] <britt> how long does it usually take to build?
[02:12] <darkxst> queues are big today, ~5hrs for amd64, ~1hr for i386
[02:12] <britt> gotcha
[02:12] <jbicha> darkxst: there's a shortcut for that
[02:13] <darkxst> jbicha, really?
[02:13] <jbicha> if you set the urgency to medium in the changelog you can jump to pretty much the front of the line
[02:15] <darkxst> :)
[02:22] <darkxst> britt, ok its building now, shouldnt be long
[02:26] <britt> thank you sir:-) that is indeed a handy trick
[02:33] <britt> hrm it's not seeing the package
[02:34] <britt> it's weird that my gnome-desktop3-data package is 3.7.2
[02:34] <britt> the one in the gnome3ppa I mean
[02:35] <darkxst> you probably want to purge gnome3 ppa ;)
[02:36] <britt> lol
[02:36] <britt> lol just temp or in general?
[02:37] <darkxst> in general, if you have stale packages left over (after disabling) thats always likely to cause problems
[02:37] <jbicha> britt: um... maybe that's why you have the time bug on 13.04 and not on 12.10
[02:37] <britt> perhaps I'll check now
[02:37] <britt> give me 2 min
[02:38] <britt> i'm purging it now
[02:38] <britt> is it only safe to use that ppa once the release is final?
[02:39] <darkxst> gnome3 is fairly safe
[02:40] <darkxst> gnome3-staging will probably break occasionally
[02:42] <britt> hey so purging the gnome3 ppa fixed the clock with the need for having darkxst's gnome-desktop3 package
[02:42] <britt> I'm assuming it's because theres a gnome-desktop3-data package in the gnome3ppa that is 3.7.2 but all the other packages are still 3.6 branch
[02:43] <jbicha> britt: that version has the bug that was fixed by a later git commit
[02:44] <britt> so that package was the one causing the issue this whole time? lol
[02:44] <jbicha> we had a tricky upgrade problem which we worked around by sticking a new old gnome-desktop package there
[02:44] <britt> thats sucks, but it's good to know
[02:45] <britt> well thats not confusing at all ;-)
[02:45] <jbicha> britt: it's good for us to know too, so we can fix it
[02:45] <britt> yeah by ppa-purging it replaced it with gnome-desktop3-data 3.6.2
[02:45] <britt> and that works great
[02:45] <britt> sorry for wasting your time darkxst on that patch. I feel bad
[02:46] <darkxst> jbicha, can you sponsor this one http://pastebin.com/byhXFpu5
[02:47] <darkxst> britt, thats ok, atleast we know which package needs fixing now ;)
[02:48] <britt> haha yeah tracking that down was fun
[02:48] <britt> nice reccomendation on purging the ppa though
[02:49] <britt> I still do have the cursor-barrier bug though so whenever you get a chance for that one ;-)
[02:49] <jbicha> britt: ok, I uploaded the time fix to the gnome3 ppa
[02:49] <jbicha> darkxst: you have a second screen right?
[02:50] <britt> very cool, I'll re-add it in a bit
[02:51] <britt> if I readd the ppa i'll pull in gnome-desktop3-data 3.7.2 though, is that ok if all of my other gnome packages are 3.6.2?
[02:51] <darkxst> jbicha, yes although I didnt directly test that package, I know it works ;)
[02:53] <jbicha> britt: it should be mostly harmless, the old gnome-system-monitor would have claimed you were running gnome 3.7.2 though
[02:53] <britt> gotcha
[02:54] <jbicha> darkxst: the barrier problem affects quantal too right?
[02:55] <darkxst> jbicha, yes it would
[02:55] <britt> it looks like I have gnome-system-monitor 3.7.90, and that is in the main repos. I never noticed that the newer version was pulled in
[02:55] <britt> I can verify that the barrier problem was in quantal
[02:57] <darkxst> I suppose I should update the quantal g-s before it gets uploaded for SRU;)
[02:57] <darkxst> jbicha, or won't the SRU team  like that combining bug fixes with MRE?
[03:00] <jbicha> darkxst: SRUs are about fixing high impact bugs and I think this qualifies so it shouldn't be a problem
[03:12] <darkxst> jbicha, ok, added it to the MP
[03:14] <britt> jbicha, I added the gnome3ppa again and pulled in the new package you uploaded and the am/pm issue came back
[03:14] <britt> just fyi
[03:16] <britt> when I add the gnome3-ppa it pulls in 5total packages, gir1.2-gnomedesktop-3.0, libgnome-desktop-3-4, gnome-desktop3-data
[03:16] <britt> it has to be in one of those 3 packages
[03:16] <britt> my money is the gnome-desktop3-data like we though before
[03:17] <britt> there must be more going in in the desktop3 3.7.2 package than conflicts with gnome-shell 3.6.3
[03:18] <britt> that*
[03:18] <britt> well I'm off for a while guys, thanks for your help!
[03:24] <jbicha> I think he still had the raring3 version
[03:25] <darkxst> probably
[03:39] <darkxst> jbicha, is there another way to get a list of sponsors that have uploaded my packages apart form that UDD sponsor miner?
[03:40] <darkxst> ^ it is not providing a very complete list
[03:47] <jbicha> darkxst: https://launchpad.net/~/+related-packages if you click the version number it should show you who sponsored
[03:50] <darkxst> well that really doesnt help for packages where I have submitted many different versions
[03:54] <darkxst> jbicha, or do I even need other endorsements given that you have sponsored the majority
[03:55] <jbicha> oh yeah I guess that page isn't super useful :(
[03:57] <jbicha> darkxst: the DMB prefers multiple endorsements, the threshold shouldn't be too high for contributing developer
[03:58] <jbicha> I should let other people sponsor your stuff though
[04:03] <darkxst> yeh I think its been mostly random, didier sponsored a few, but they were mostly trivial updates I think
[10:17] <britt> hey darkxst or ricotz you guys there?
[10:24] <britt> hey I just wanted to report that I am having trouble booting with the staging ppa installed without having the xorg-edgers ppa also installed
[10:24] <britt> the computer will not load gdm, it goes to a black screen without a cursor right after showing the blue gnome-background
[14:04] <jbicha> ricotz: I guess I should have waited on pushing the cogl/gnome-shell update to coordinate with your PPA, sorry about that
[14:12] <ricotz> jbicha, yeah, just wanted to point that out ;)
[14:12] <ricotz> hmm..
[14:14] <ricotz> jbicha, yeah, just wanted to point that out ;)
[14:19] <jbicha> ricotz: for your clutter-1.0, you may want to build-depend on cogl >= 1.13.4 and have libclutter-1.0 break libcogl11
[14:19] <ricotz> jbicha, dont worry about that
[14:20] <ricotz> i havent split the packaging out for quantal yet
[14:20] <jbicha> well the build-depend probably isn't important but the breaking is
[14:22] <ricotz> will try to go through the packages, after the gnome-session mess is fixed :\\
[14:22] <jbicha> what happened with gnome-session?
[14:22] <ricotz> bad patch update
[14:23] <ricotz> btw gnome-shell needs a versioned dep on gir1.2-caribou...
[14:24] <jbicha> ricotz: I think gnome-shell needs to depend on caribou directly too
[14:25] <ricotz> yeah, maybe
[20:53] <britt> hey guys, I enabled the staging repo last night and have noticed a few issues, but I cannot file bugs in launchpad against them
[20:53] <britt> is there a proper channel for letting you guys know about bugs?
[20:55] <jbicha> it depends on the bug, but you can discuss them here :)
[20:55] <darkxst> britt, use launchpad and just specify you are using staging ppa
[20:56] <britt> Thats what I was planning, but using Ubuntu-bug to pull in logs wont even let me get that far. It says "cannot create bug because packages are not official" or something along those lines
[20:56] <darkxst> yeh that will happen
[20:56] <darkxst> anyway what are the ussyes?
[20:56] <darkxst> issues
[20:56] <jbicha> right, I think there's some hack we can do for our packages to enable apport to work with them but I don't know how to set it up
[20:57] <britt> well the main issue was that I couldn't get gdm to load without having the xorg-edgers ppa installed. It just went to a solid black screen with no cursor before gdm showed
[20:57] <britt> I dont know if it is because gdm requires a higher xorg version or something....but it was surprising
[20:58] <darkxst> britt probably 3D/drm was broken
[20:58] <britt> maybe. It worked fine on 3.6 though
[20:59] <britt> I'm running open sourced drivers + mesa btw
[20:59] <darkxst> gdm has no dependency on xorg really
[21:00] <britt> i wonder why it was failing to load then. I did get the blue background to show for about 2 seconds before the screen went black, which means my video drivers which means X did start
[21:00] <britt> (wow that was a terrible sentence)
[21:00] <darkxst> gdm uses gnome-shell to render the login screen
[21:00] <darkxst> if openGL is broken, then that is the usual reason you get a black screen
[21:01] <darkxst> however if openGL is non-existent it will fallback to software rendering
[21:01] <britt> well heres the funny part. After I installed all of the 3.7 packages I did an alt-f2>r and reloaded shell just fine and it looked great. Only after rebooting did I have issues
[21:02] <britt> so the old drivers were able to render gnome-shell for a short while anyway
[21:04] <darkxst> did you go from fglrx to radeon drivers at about the same time?
[21:04] <britt> no. I was using the OS drivers before and after
[21:05] <britt> (and still am, just I am using the edgers ppa versions)
[21:10] <darkxst> you can use 'glxinfo | grep -i openGL' to check if openGL is working correctly
[21:10] <britt> jbicha, http://jderose.blogspot.com/2012/09/how-to-use-apport-in-your-daily-ppa.html
[21:13] <darkxst> any mention of llvm or software rendering and openGL is messed up
[21:14] <britt> gotcha
[21:14] <darkxst> I think radeon might report Gallium3D or similar when it is working
[21:14] <britt> well could newer gnome versions break opengl? I dont think the staging ppa brings in any part of the x stack
[21:15] <darkxst> britt, mesa provides the openGL stuff
[21:16] <britt> do we pull in mesa with the staging?
[21:16] <britt> or anything that conflicts with mesa?
[21:16] <darkxst> no but is in xorg-edfers
[21:16] <britt> yeah I know
[21:16] <darkxst> gnome-shell just doesnt handle the case of broken openGL
[21:17] <darkxst> well not very well
[21:17] <britt> I am just trying to deduce what broke from gnome-shell 3.6 -3.7 with no changes to mesa
[21:17] <britt> I can purge the xorg edgers ppa and run that command though to see if opengl is running
[21:17] <darkxst> it is fine when GL is missing, i.e. blacklist radeon kernel driver, and it will just run using llvmpipe
[21:18] <britt> give me 10 min or so to remove xorg-edgers, reboot and run that command, and then reinstall so I have a working desktop again
[21:18] <britt> are you guys running the edgers ppa as well?
[21:20] <darkxst> yes, but with nvidia here
[21:20] <britt> can you test and see whether you can boot without the edgers ppa with nvidia. That way we can test if it is vendor specific
[21:21] <jbicha> britt: I use Intel and I don't use edgers
[21:21] <britt> kk well thats good then
[21:21] <britt> give me 5-10 min and I'll be back to report if openGL was borked
[21:21] <darkxst> britt, before you go
[21:23] <britt> weird it worked this time
[21:24] <britt> though yesterday it failed 6 times in a row
[21:24] <britt> there was an update to gdm at like 1am, I wonder if that inadvertantly fixed it
[21:24] <darkxst> britt, its not gdm
[21:25] <britt> I have no idea what could have changed then, unless they pushed some new mesa stuff from last night to today in the main repos
[21:25] <britt> well anyway if it's working then woo! I'll let you know if it happens again
[21:25] <darkxst> its possible that packages were broken after purging xorg-edgers
[21:26] <britt> possibly. It did pull all new ones down when I purged again
[21:26] <britt> well I'm happy it is working
[21:26] <darkxst> often reinstalling xserver-xorg-core and xserver-video-radeon will clean up any issues
[21:27] <britt> thats good to know for the future
[21:29] <britt> btw one of the issues I was having was with switching the background image with file manager handling the desktop. Every so often the background will not register as changing if I tell it to, until I turn off file manager handling the desktop
[21:29] <britt> it happened twice yesterday, though it worked fine about 10 other times
[21:29] <britt> so I do not know what triggers it
[21:29] <darkxst> background handling was moved into the shell for 3.7.90, possible fallout from that
[21:30] <britt> hrm possibly.
[21:30] <darkxst> or are you using 3.6?
[21:30] <britt> maybe it will get cleaned up once 3.8 comes closer
[21:30] <britt> no I'm using whatever is in the staging ppa since yesterday
[21:30] <britt> so 3.7.90 I believe
[21:32] <britt> oh hey another thing! Where is the networking settings in the gnome-settings panel? Its gone all of a sudden, and clicking the network icon and then "network settings" results on nothing happening
[21:35] <darkxst> they made a new network panel, but it still lives in settings
[21:35] <britt> I can't see it in settings
[21:35] <britt> do I have to get a new file for it to work?
[21:37] <darkxst> no it was working in 3.7.5, let me run an update and see
[21:43] <britt> yeah it looks like the functionality is missing from my build
[21:43] <darkxst> jbicha, yeh network panel is lost with 3.7.90
[22:11] <jbicha> cool it works: bug 1132560
[22:12] <britt> oh nice so that worked?
[22:13] <darkxst> awesome
[22:13] <jbicha> yes we just need something like http://paste.ubuntu.com/5563137/ in the source_gnome-shell.py or equivalent
[22:14] <britt> do you need that for each package? or just in the one place?
[22:15] <jbicha> it has to be done for every package we care about, I think most of these packages don't have apport hooks so it needs to be added
[22:17] <britt> gotcha
[22:18] <britt> btw jbicha did you see that darkxst repoted that network panel was lost with 3.7.90 before you logged out?
[22:18] <britt> I can confirm
[22:19] <jbicha> britt: yes I think the fix is building now
[22:21] <britt> great :-)
[22:34] <britt> damn, upstream changes to gnome terminal removed my ability to have transparent backgrounds
[22:34] <britt> thats a shame
[22:35] <jbicha> https://bugzilla.gnome.org/show_bug.cgi?id=692609
[22:36] <britt> it looks like they intentionally removed it then
[22:37] <britt> unfortunate. I really wish they would stop removing things that I like lol
[22:40] <jbicha> britt: I guess the theory is "Why should the terminal be special? Why not allow for every app to be translucent?"
[22:41] <britt> fair enough....but imo they should have kept that feature in the terminal up until they added that functionality into every app...not remove it from terminal so they dont 'have' to add it in every app
[22:49] <britt> hrm I just noticed a weird glitch when trying to drag a file. The animation does not continuously show the file being moved, but instead the file freezes about a half inch from it's starting position
[22:50] <britt> and it looks like dragging and dropping from out of nautilus is completely broken
[22:57] <britt> jbicha, the gnome-settings network fix works great, but clicking the networking icon>network settings in the upper right hand of the shell doesn't seem to do anything
[22:58] <jbicha> britt: yes, except for 'Settings' itself, all of the settings links in the top bar are broken, I haven't figured out why though
[22:59] <britt> ahh I see that.
[23:01] <britt> jbicha, have you though about bring in the gnome-tweak-tool as a default app? I know fedora brings it in by default and calls it "advanced settings" an even adds a link to it in the gnome-settings
[23:01] <britt> I was just seeing your thought on that
[23:02] <jbicha> britt: tweak tool was included by default in 12.10 :)
[23:02] <britt> oh nice haha. I must have not realized having installed it soo many times manually
[23:03] <britt> that is very cool
[23:03] <britt> what about adding a link to it in the gnome-settings-panel ;-)
[23:05] <jbicha> britt: you'll have to ask GNOME about that one, we try not to tweak GNOME too much
[23:06] <britt> haha ok. I really think at this point they should pull it into the gnome ecosystem as a native app. The community has basically deemed it as essential anyway
[23:26] <darkxst> jbicha, I wonder if we should do this at distro level? https://live.gnome.org/Terminal/FAQ#How_can_I_make_new_terminals_start_in_the_working_directory_of_the_current_terminal.3F
[23:28] <britt> https://bugzilla.gnome.org/show_bug.cgi?id=694629 I opened a bug on the topic of the tweak tool as a default app.
[23:29] <jbicha> darkxst: yes, I couldn't get it to work when I tried though
[23:29] <darkxst> jbicha, for some reason vte.sh does not get sourced
[23:34] <darkxst> no idea why not, but it works if you manually source /etc/profile.d/vte.sh first
[23:37] <britt> can you guys check and see if you have issues dragging files in nautilus? I am trying to check if it is an upstream bug or with us
[23:38] <darkxst> fine here
[23:39] <britt> the animation does freeze about a half inch away from where the file originated?
[23:40] <britt> I can take a screen cast to show you guys if you want
[23:43] <britt> yup I I can't drag any file more than 20pixels at a time with nautilus, and if I try dragging files on my desktop I can get slightly further, but it automatically opens my desktop folder in a new nautilus window for some reason
[23:48] <darkxst> try disable desktop handling perhaps
[23:48] <britt> kk
[23:48] <britt> nope it didn't help dragging from within nautilus
[23:49] <britt> its odd that I am having issues that you guys cannot replicate unless you guys are running different packages than me lol
[23:50] <britt> I wouldn' think a nautilus issue would be hardware specific