[00:22] <darkxst> octoquad, it applies equally to any files in debian/
[00:23] <darkxst> and if you ever do any work on upstream code, same again
[00:30] <octoquad> ok
[00:31] <octoquad> can't build, seem to be missing: debian/rules:3: /usr/share/cdbs/1/rules/autoreconf.mk: No such file or directory
[00:31] <octoquad> I have cdbs installed
[00:32] <octoquad> ok apt-file helped: dh-autoreconf was not installed
[00:36] <octoquad> is there a step missing between dch -i and debuild -S?
[00:37] <octoquad> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/nautilus_3.10.1-0ubuntu9.5.diff.dBWFeS; dpkg-source: info: you can integrate the local changes with dpkg-source --commit
[00:50] <darkxst> octoquad, that means you somehow edited one of the upstream files
[00:50] <darkxst> you can run:
[00:50] <darkxst> dpkg-source --commit
[00:50] <darkxst> create a tmp.patch
[00:50] <darkxst> quilt pop -a
[00:51] <darkxst> check tmp.patch isnt anything important, then remove the file and the reference from series
[00:51] <darkxst> then try debuild -S again
[00:51] <darkxst> also maybe try quilt pop -a; debuild -S
[00:52] <darkxst> ^first
[00:54] <octoquad> did quilt pop -a; debuild -S same thing. If I look in the tmp file, it starts with a TODO: Put a short description...
[00:59] <octoquad> :q
[01:00] <octoquad> ok, the file changes are for aclocal.m4 and config.guess, configure and more. I don't think that's correct, is there a git checkout -f type command for this lol
[01:09] <octoquad> starting over
[01:40] <darkxst> octoquad, if you somehow run a real build in there that will happend, ie debuild without -S
[01:42] <octoquad> noted. It's building now (sbuild)
[01:43] <octoquad> just enabled apt-cacher for sbuild as well to speed things up
[01:47] <darkxst> octoquad, it should pick it up automatically, atleast it does if its running when you create the schroot
[01:49] <octoquad> apt-cacher is running on a remote server I setup for the company
[01:50] <octoquad> also does caching for debian as well as ubuntu
[01:53] <octoquad> lol, I just realised the bug occurs in 3.12.2-0ubuntu1~trusty3
[01:53] <octoquad> staging ppa
[01:57] <octoquad> but it's also present in 14.04 stock
[02:02] <octoquad> and the patch works on 14.04 stock. yay!
[02:02] <octoquad> How can I grab the 3.12.2-0ubuntu1~trusty3 one for staging ppa
[02:03] <octoquad> might as well get it over and done with
[03:26] <darkxst> octoquad find the link for dsc file via this page https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages
[03:26] <darkxst> and use dget to download it.
[03:27] <darkxst> octoquad, oh in that case it would not be found automaticall, that only applies to localhost
[03:27] <darkxst> also btw gnome3-staging/trusty is essentiall end-of-life now, however if you prepare the fix I will upload
[03:28] <darkxst> you will also need to prepare a debdiff and SRU paperwork for the trusty package
[03:28] <darkxst> https://wiki.ubuntu.com/StableReleaseUpdates
[03:54] <octoquad> Pulled an all nighter lol
[03:54] <octoquad> will sort out the staging one quickly
[03:54] <octoquad> do I need to upload to my own ppa?
[04:17] <darkxst> octoquad, you can send me or Noskcaj a debdiff and we will upload it
[04:59] <darkxst> Noskcaj, odd, the ppa publisher seems stuck!
[04:59] <darkxst> (for your g-s-d upload)
[05:18] <darkxst> anyone feel like testings wayland sessions on vivid?
[05:18] <darkxst> they may work now, just need the session file from gnome-session, that we are not currently installed
[05:19] <darkxst> (best to test on intel hardware)
[07:58] <ricotz> Noskcaj, hi
[07:59] <ricotz> thanks for beginning with 3.15.x updates, although maybe wait for 3.15.4 hopefully this release will be more aligned
[08:00] <ricotz> e.g. be careful with g-s-d
[09:21] <Noskcaj> ricotz, I was just uploading a bunch of stuff before i have to leave for a fortnight. Mostly stuff depended on by other stuff
[13:36] <LinDol_> hi all
[13:36] <LinDol_> today was cold :-)
[15:54] <MrChrisDruif> Anyone here having issues when using fastboot?
[16:04] <MrChrisDruif> fastboot oem unlock keeps hanging, in case someone is wondering.
[16:31] <MrChrisDruif> fastboot oem unlock keeps hanging, in case someone is wondering.
[16:31] <MrChrisDruif> I did a factory reset, enabled adb etc and now it just worked =/
[16:32] <octoquad> MrChrisDruif, are you talking about Android?
[17:35] <MrChrisDruif> octoquad; YUP
[17:35] <MrChrisDruif> It was an Ubuntu GNOME question relating to fastboot but it was in conjuction with Android obviously
[17:37] <JDAIII> got a question. I'm trying to scale my second monitor. 2x2 but when I do, the mouse in constrained to the top left quadrant of the monitor. Anyone else experience this? The only references I find online say that it was a bug that was fixed
[17:38] <JDAIII> It's pretty frustrating since I have a 4k laptop with an external 1080 monitor and the 1080 monitor looks like a childrens toy in comparison of the resolution.
[17:52] <octoquad> MrChrisDruif, I see, for a second I thought you were asking in the wrong channel hehe
[17:52] <MrChrisDruif> ^_^
[17:53] <octoquad> MrChrisDruif, is it working now?
[17:53] <MrChrisDruif> Yup
[17:53] <octoquad> nice
[18:00] <octoquad> JDAIII, did you file this bug report: https://bugs.launchpad.net/bugs/1408123
[18:01] <octoquad> Have you tried to use gnome-tweak-tool and changing the HiDPI Window Scaling option under "Windows" to see if you get a better result?
[18:59] <JDAIII> octoquad, yes I did. Not sure if it was the right direction to go, but felt like it.
[18:59] <JDAIII> and no, there is no setting in tweak that will change that. at least that I can find
[19:01] <JDAIII> I find a font scaling, but that isn't helpful to my issue
[19:04] <octoquad> JDAIII, checking....
[19:09] <octoquad> JDAIII, sorry about that, HiDPI setting was introduced in 14.10
[19:09] <JDAIII> Should I upgrade to 14.10? Will that resolve the issue?
[19:09] <octoquad> I can't guarantee it, but you can maybe try boot a livecd of 14.10 and see if it does fix it for you
[19:10] <octoquad> http://ubuntugnome.org/ubuntu-gnome-14-10-is-released/
[19:11] <JDAIII> Now, since 14.04 is a LTS, I'm assuming that the bug report will not just be closed. I used 14.10 in a VM, but it has library issues with a software that I use so it wasn't an option out of the box without significant anoyances, but I guess that I will have to figure something out
[19:11] <JDAIII> I will test as a live cd
[19:11] <octoquad> I hope it works for you :) Unfortunately, I don't have the hardware to test
[19:12] <octoquad> what library issue are you having with 14.10>
[19:12] <octoquad> ?
[19:13] <octoquad> yes, the bug report will not be closed until it has been fixed or trusty reaches EOL
[19:13] <JDAIII> I can't remember offhand, but it was upgraded to version 5 and my software requires version 4. It was a whole thing so I just went with 14.04 on my laptop
[19:14] <octoquad> well, I don't mind trying to help you with that as well
[19:16] <JDAIII> It would not be today, I have to start doing work today. But I would like to figure out the mouse constraint, or even better, figure out how to get my video card drivers installed without screwing everything up. I've had a hell of a time with the nvidia drivers on here
[19:18] <octoquad> interesting, have a look here and see if any of these bug reports affect you for nvidia
[19:18] <octoquad> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331
[19:18] <octoquad> do you get a black screen when booting a nvidia driver?
[19:20] <octoquad> you can also try the bumblebee project for nvidia, it seems to work a bit better for me on Gnome: https://wiki.ubuntu.com/Bumblebee#Installation
[19:21] <JDAIII> I have a few things that happen, one sec
[19:22] <JDAIII> When I download the NVIDIA*.run file from the nvidia website, I switch to runlevel2, stop gdm, install the driver, reboot and get a black screen. I uninstall and the black screen stays there. Had to reformat.
[19:23] <JDAIII> 2. I use the nvidia-343 off some ppa that I found and it sets the resolution wonky, and restricts my mouse not to work on second monitor after moving the top and bottom gnome taskbars to the second monitor so I can do nothing but uninstall from a lower runlevel
[19:24] <JDAIII> 3. I tried optimus and it did abolutely nothing for me whatsoever. Saw no differences.
[19:24] <Nrober> Hey, there is some bug with gnome-shell when using rhytmbox on 14.10, processor usage jump up to 100 when using this app :(
[19:24] <octoquad> And what about the official package from the repository?
[19:24] <JDAIII> 4. Haven't tried bumblebee yet due to wanting to use a plastic spork from KFC to kill myself after previous expereinces with drivers
[19:24] <octoquad> JDAIII, lol
[19:25] <JDAIII> official package? for the nvidia-343?
[19:25] <octoquad> Nrober, Hi. I'll check for you now.
[19:25] <octoquad> well what ever is in the 14.04 repos when you do apt-get install nvidia
[19:25] <octoquad> sorry I don't know what the full package name
[19:27] <JDAIII> I couldn't find anything in the official repos for my nvidia card so I used the ppa xorg-edgers and the package is called nvidia-343
[19:27] <JDAIII> http://www.ubuntuupdates.org/package/xorg-edgers/utopic/main/base/nvidia-343
[19:27] <octoquad> yeah should be ok then
[19:28] <octoquad> hmm, have you tried booting an older kernel and trying to install the driver
[19:28] <octoquad> ?
[19:28] <JDAIII> no I have not. I wanted to get other people's input as I'm relatively new to linux
[19:28] <octoquad> Nrober, are you using stock 14.10 or 14.10 and our staging ppa
[19:28] <octoquad> ?
[19:28] <JDAIII> only been using it a few months and haven't played with kernels much
[19:29] <Nrober> octoquad : I'm using clean 14.10 but bug only occurs when I'm playing some music, not just rhytmbox in background, and m4a file. I will check with some other
[19:31] <Nrober> octoquad : for diffrent file type same
[19:31] <octoquad> JDAIII, when you boot up, under the first entry, you can select that and choose an older kernel
[19:35] <JDAIII> yea, I just don't play around with it if I don't have to. I am going to try rebooting in a few minutes to 14.10 to see if the constriction issue is there for scaling.
[19:36] <JDAIII> So I'll be offline, but I appreciate the help and I will return shortly. (hopefully)
[19:36] <JDAIII> and my spork has been confiscated by office authorities. no suicide today
[19:40] <octoquad> Nrober, is gnome-shell or rhythmbox cpu usage high?
[19:41] <pkulas_> octoquad : Sorry, network disconected for few minuts
[19:41] <octoquad> no problem
[19:41] <pkulas_> octoquad : Nrober here.
[19:42] <octoquad> pkulas_, , is gnome-shell or rhythmbox cpu usage high?
[19:42] <pkulas_> octoquad: gnome shell
[19:43] <pkulas_> and usage raises when i use mouse cursor or use some gnome-shell interface
[19:44] <octoquad> Can you try this: press ALT+F2 then type r then enter
[19:45] <pkulas_> gnome-shell restart but no changes
[19:45] <octoquad> ok, process of elimination
[19:46] <octoquad> For me, gnome-shell CPU usage spikes to 67% when Rhythmbox is running, nothing more
[19:47] <octoquad> What CPU processor do you have?
[19:47] <pkulas_> Intel(R) Core(TM) i3-4000M CPU @ 2.40GHz
[19:49] <pkulas_> If music is not playing and intensive use of gnome-shell it spikes to 16%
[19:50] <octoquad> well, I can tell you that it is using 100% of a core the other is ok, if it was showing 200% then it would be utilizing all of your CPU usage. So at the moment it's only using 50%.
[19:51] <octoquad> but still, that's hogging
[19:51] <octoquad> and do you get the same result when you something else like Banshee or Clementine?
[19:52] <pkulas_> I will check with Clementine
[19:52] <octoquad> I get slightly less CPU usage when playing an mp3 (~10%)
[19:53] <octoquad> It might actually be a bug in Rhythmbox...let me check if someone has reported it
[19:53] <pkulas_> octoquad : It can raises over 150% when using rhytmbox, just right before I had a problem to stop it
[19:54] <pkulas_> Clementine is working fine
[19:56] <octoquad> ok, so that rules out gstreamer plugins then
[19:59] <octoquad> pkulas_, can you confirm if the cpu usage drops when you make the rhythmbox window smaller
[20:00] <pkulas_> Yeah, when window is smaller usage is way lower and on rhytmbox on full resolution is highest
[20:00] <octoquad> interesting..
[20:01] <octoquad> What graphics card are you using
[20:01] <pkulas_> but spikes up to 50 anyway
[20:01] <pkulas_> intel hd 4400
[20:02] <octoquad> OK, I'm testing in a VM
[20:04] <octoquad> currently testing 15.04 to see if it is there as well
[20:04] <Joshun> hi
[20:04] <octoquad> hi Joshun
[20:04] <Joshun> the file search doesn't seem to be working proplery from the activities dash, is there any way to fix this?
[20:05] <octoquad> Joshun, what is it doing?
[20:05] <octoquad> and which version of Ubuntu Gnome?
[20:05] <Joshun> great work with ubuntu gnome btw, on the whole it is great. searching for a file in my home dir doesn't appear with the file
[20:05] <Joshun> 14.10
[20:06] <Joshun> under search preferences, "Files" has been set to "On"
[20:07] <darkxst> octoquad, hi, you debdiff looks good, however the sru paperwork, needs to go at the very top in original bug report
[20:07] <Joshun> maybe it fails to search recursively
[20:07] <darkxst> also you seem to have misunderstood the regression potential, it about possible issues that this fix might cause
[20:08] <octoquad> darkxst, I don't think there would be any, but those were the only ones I could think of with the patch
[20:08] <octoquad> darkxst, I didn't want to say none
[20:09] <octoquad> Joshun, perhaps, It can find a file in the root of my home directory but not in music
[20:10] <darkxst> well I wouldnt say any of those either there is no technical reason any of those would occur
[20:11] <octoquad> darkxst, so just none then?
[20:13] <Joshun> octoquad yes, it seems this is the case, this ask ubuntu thread[1] seems to have the same issue. not sure if it is a setting or a bug
[20:13] <Joshun> [1]: http://askubuntu.com/questions/496206/tracker-recursive-indexing-fails
[20:14] <octoquad> darkxst, is it possible for tracker to mine the entire home directory? I'm sure it does, but the activities search doesn't bring up a file. Perhaps it's limited to certain mimetypes or filetypes?
[20:14] <darkxst> octoquad, no, not none
[20:15] <Joshun> what is the backend for the file search?
[20:16] <Joshun> is it just tracker?
[20:16] <octoquad> tracker-miner-fs
[20:17] <darkxst> something like "Low, this patch just fixes incorrect handling of owner field, it shouldnt introduce any issues and has been well tested in 3.14"
[20:17] <Joshun> the weird thing is, in tracker preferences each of the folders are set to recurse
[20:18] <Joshun> would it be a good idea for me to file a bug report in tracker-miner-fs ?
[20:18] <darkxst> the search in the shell is provided by nautilus (which uses tracker to get the results)
[20:18] <darkxst> Joshun, test with desktop-file-search, that uses tracker directly
[20:18] <Joshun> is that a command?
[20:19] <darkxst> yes
[20:19] <Joshun> doesn't seem to be installed :(
[20:19] <Joshun> is it in desktop-file-utils?
[20:19] <octoquad> doesn't exist darkxst in 14.10
[20:20] <darkxst> sorry probably wrong name, its part of tracker
[20:20] <Joshun> why does nautilus try to do everything
[20:20] <octoquad> tracker-search
[20:20] <Joshun> I mean, it already handles the desktop
[20:20] <darkxst> tracker-needle
[20:21] <darkxst> nautilus doesnt handle the desktop in gnome-shell (well not by default)
[20:21] <Joshun> oh
[20:21] <Joshun> well yes of course, its disabled by default
[20:21] <Joshun> tracker-search works as expected
[20:22] <darkxst> and it makes sense for gnome-shell to call the file manager search provider for file search
[20:23] <Joshun> tracker-needle also works fine
[20:23] <darkxst> Joshun, so its probably a bug in nautilus
[20:23] <octoquad> pkulas_, rhythmbox works fine vivid! :) So a fix has been released for it then I'm assuming
[20:23] <octoquad> *fine in vivid
[20:23] <Joshun> darkxst - the nautilus file search works ok though
[20:24] <Joshun> or is it a problem with the provider
[20:24] <darkxst> nautilus search is patched in ubuntu
[20:25] <darkxst> but yes its probably an issue with the provider
[20:25] <pkulas_> octoquad : nice, then I will just use Clementine and switch to 15.04 when will be out
[20:26] <octoquad> pkulas_, 23 April
[20:26] <Joshun> I will file a bug in nautilus then, should it be filed in gnome-shell aswell or just nautilus darkxst ?
[20:26] <octoquad> pkulas_, you can also try our staging ppa, this has some updates that never made it into 14.10 before final release and test.
[20:27] <darkxst> gnome-shell is fine
[20:27] <darkxst> I don't think anything else uses the nautilus search provider anyway
[20:29] <octoquad> darkxst, http://pastebin.com/09wx0fgR
[20:30] <octoquad> for nautilus staging ppa
[20:30] <pkulas_> octoquad : is it fine for to use staging ppa? I want to use this system up to April without any new annoying bugs :)
[20:30] <darkxst> octoquad, you need to add the ppa to sbuild for it to work
[20:30] <darkxst> and that is not straight forward
[20:31] <octoquad> pkulas_, yes it's fine, you can always use ppa-purge to remove it if anything goes wrong
[20:32] <octoquad> darkxst, I'm up for the challenge :)
[20:33] <darkxst> octoquad, I had to locally patch some files, and its quite hacky but I will send them to you.
[20:33] <octoquad> Joshun, this problem is not present in 15.04 though
[20:34] <Joshun> oh ok, so it is fixed upstream
[20:34] <octoquad> Joshun, I suppose, since it works :)
[20:36] <octoquad> I have to say, 15.04 is looking and working beautifully!
[20:36] <octoquad> I think Ali was right about the rolling release thing
[20:38] <darkxst> octoquad, put http://pastebin.com/B2NvfaFX into /etc/schroot/setup.d/90apt-sources
[20:39] <darkxst> then you need to alias' in the config files in /etc/schroot/chroot.d
[20:39] <darkxst> like: vivid-proposed+gnome3staging-amd64-sbuild
[20:41] <octoquad> ok, I already have 90apt-sources but without sh, should I just replace?
[20:42] <darkxst> yes replace it
[20:43] <octoquad> I really need to setup a dotfiles repo
[20:51] <pkulas> octoquad : Yeah after gnome upgrade to 3.14 rhythmbox no longer bug cpu usage
[20:52] <octoquad> pkulas, glad to hear that :)
[21:09] <octoquad> darkxst, I get: E: 90apt-sources: E: Failed to execute “90apt-sources”: No such file or directory but its there
[21:11] <darkxst> octoquad, did you make it executable?
[21:11] <octoquad> darkxst, yes, exactly the same as the rest of the files in there
[21:12] <octoquad> brb
[21:12] <darkxst> maybe the script got messed up somehow
[21:13] <darkxst> formatting again?
[21:15] <darkxst> octoquad, maybe try http://pastebin.com/9DV9FXrJ
[21:29] <octoquad> darkxst, no no, I downloaded it a moved it. Learnt my lesson last night
[21:29] <octoquad> darkxst, paste has been removed
[21:33] <darkxst> octoquad, semm to be having issues with pastebinit here, try http://pastebin.com/SX4aqxjN
[21:33] <octoquad> got it
[21:34] <octoquad> ok, it's building no
[21:34] <octoquad> now
[21:38] <octoquad> darkxst, same build failure
[21:38] <darkxst> octoquad, you used the new alias you created with sbuild?
[21:39] <octoquad> I added the vivid-proposed+gnome3staging-amd64-sbuild to /etc/schroot/chroot.d/trusty-amd64-sbuild
[21:39] <octoquad> *I added the alias...
[21:39] <darkxst> it should be  trusty-proposed+gnome3staging-amd64-sbuild
[21:39] <darkxst> for a trusty chroot
[21:39] <octoquad> *smacks forehead
[21:39] <octoquad> of course
[21:39] <darkxst> and you need to use that alias when running sbuild
[21:40] <darkxst> i.e for the -c option
[21:44] <octoquad> sbuild --dist=trusty --arch=amd64 -c trusty-proposed+gnome3staging-amd64-sbuild seems to work
[21:44] <octoquad> grabbing packages at the m
[21:44] <octoquad> moment
[21:47] <octoquad> so, I can easily switch between ppa and normal repos with the -c option and that will chroot with the right packages and essentially "start fresh"?
[21:47] <darkxst> yes
[21:47] <octoquad> ama-zing
[21:51] <octoquad>  just signed up to stack exchange to help out with any questions regarding Ubuntu / Ubuntu Gnome. Had no points to up-vote a gpg issue I had earlier.
[21:57] <octoquad> success!
[21:57] <octoquad> ll
[22:02] <octoquad> darkxst, so I how do I get this to you or to the staging ppa
[22:02] <octoquad> ?
[22:02] <darkxst> paste a debdiff
[22:02] <octoquad> ok, just want to test quickly
[22:15] <octoquad> darkxst, the package name, does it matter if it is now 3.12.2-0ubuntu1~trusty3ubuntu1 from 3.12.2-0ubuntu1~trusty3?
[22:15] <octoquad> shouldn't the ~trusty part be ~trusty4?
[22:16] <darkxst> octoquad, yes change it manually
[22:16] <darkxst> or use `dch -ltrusty`
[22:16] <darkxst> or use `dch -l~trusty` actually I think
[22:17] <octoquad> oh I see, in the changelog
[22:17] <octoquad> :q
[22:18] <octoquad> sorry, I keep typing the vim quit command here lol
[22:46] <octoquad> darkxst, http://pastebin.com/wxmK5qGk
[23:20] <darkxst> octoquad, thanks uploadeded
[23:21] <octoquad> that was fun :)
[23:30] <darkxst> octoquad, it will be much quicker for you next time
[23:30] <octoquad> yeah, most of the time was setting up the tools and learning...
[23:33] <octoquad> we need to update this page: http://ubuntugnome.org/screenshots/
[23:42] <JDAIII> octoquad, are you still online?
[23:42] <octoquad> JDAIII, yes, how did it go?
[23:43] <JDAIII> I upgraded to 14.10 and when I run the xrandr scal command, I still have mouse constraint. I'm using xrandr --output eDP1 --auto --output HDMI1 --auto --scale 2x2 --right-of eDP1
[23:43] <JDAIII> however, now the mouse arrow is gigantic.
[23:43] <JDAIII> that didn't happen before
[23:45] <JDAIII> I have not yet tried installing the nvidia drivers, but I can try that next
[23:45] <JDAIII> figured that I would test the bug first and I still see it
[23:47] <octoquad> JDAIII, please update your bug report with your findings: https://bugs.launchpad.net/ubuntu-gnome/+bug/1408123
[23:48] <octoquad> darkxst, do you have any suggestions for JDAIII? My knowledge of xrandr is non-existent.
[23:48] <octoquad> JDAIII, please also list hardware that you have with lspci -vvv and attach to bug report
[23:48] <octoquad> in a text file
[23:49] <JDAIII> ok
[23:49] <octoquad> thanks :)
[23:51] <JDAIII> uploaded.
[23:54] <octoquad> JDAIII, have you tried the HiDPI setting in gnome tweak tool? Reset everything and try with the HiDPI option and let me know
[23:56] <darkxst> JDAIII, HiDPi support in trusty was not entirely complete I believe
[23:59] <JDAIII> that has screwed up my monitor and I have no way of getting it back.
[23:59] <JDAIII> I can't even see what I am typing in here