[00:02] <JDAIII> ok I was able to switch to level2 and use gsetting command
[00:03] <JDAIII> not doing that again. BTW: scaling in tweak tool doesn't work as expected
[00:03] <octoquad> I was looking for the gsetting key to reset it. Glad you sorted it out
[00:03] <darkxst> JDAIII, pretty you need GNOME 3.12 or 3.14 for good HiDPI support
[00:04] <darkxst> pretty sure
[00:04] <JDAIII> ok
[00:04] <octoquad> are you using staging ppa for 14.10 JDAIII?
[00:05] <JDAIII> no, I only used the software update tool
[00:05] <JDAIII> sudo update-manager -d
[00:07] <JDAIII> But I'm adventurous and easily trusting, so send me your suggestions.
[00:08] <octoquad> Add this: https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3
[00:09] <octoquad> Then this https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging
[00:09] <octoquad> Then run sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade and reboot
[00:10] <darkxst> you don't need upgrade there, just dist-upgrade is enough
[00:10] <JDAIII> funny enough I tried dist-upgrade and it said that there were no upgrades available. and yes I ran update first
[00:11] <octoquad> darkxst, so the packages from update would be applied under dist-upgrade
[00:11] <darkxst> octoquad, ping the artwork team re screenshots
[00:11] <darkxst> octoquad, yes
[00:11] <octoquad> darkxst, cool, didn't know that
[00:11] <JDAIII> another fun thing though is that I cannot change my background since I changed to 14.10. ugly blueish green background stuck there
[00:12] <darkxst> dist-upgrade does everything upgrade does but also handle packaging transitions
[00:12] <octoquad> JDAIII, there are no packages to update straight after a upgrade using update-manager -d
[00:13] <octoquad> if you add the to ppa's above, there will be a ton of packages to update
[00:13] <octoquad> *two not to
[00:14] <JDAIII> I did that before update-manager -d thinking that I could upgrade from 14.04.1 to 14.10 with just a dist-upgrade
[00:16] <octoquad> darkxst, sent e-mail to artwork
[00:16] <octoquad> JDAIII, ok, please run the following:
[00:17] <octoquad> sudo add-apt-repository ppa:gnome3-team/gnome3
[00:17] <JDAIII> just did that
[00:17] <JDAIII> then update
[00:17] <JDAIII> then upgrade
[00:17] <JDAIII> upgrading now
[00:17] <octoquad> ah ok, soz :)
[00:17] <JDAIII> we're waiting
[00:18] <JDAIII> I did not add the staging yet though, is that necessary?
[00:18] <JDAIII> I figured that the first one was more stable
[00:18] <darkxst> JDAIII, -staging has gnome 3.14
[00:19] <darkxst> provided you are on 14.10
[00:19] <JDAIII> well, is it worth adding the staging repo?
[00:21] <JDAIII> lsb_release says 14.10
[00:21] <octoquad> gnome-shell --version
[00:22] <JDAIII> 3.12.2
 JDAIII, -staging has gnome 3.14
[00:22] <JDAIII> not sure I want to go to 3.14 if there are other bugs though
[00:23] <JDAIII> I'm going to restart and if it still doesn't work, then I will try the staging.
[00:23] <JDAIII> alright, going to reboot, if I'm not back on in 5 minutes, it blew up my machine and I'm hunting for a spork to commit sepuku
[00:23] <octoquad> lol
[00:27] <JDAIII> so, the scaling issue is still there
[00:27] <darkxst> octoquad, you need to subscribe sponsors team on the nautilus bug also, so it gets into sponsorship queue
[00:28] <JDAIII> background works again though
[00:28] <JDAIII> I'm going to go do my best to destroy a server, I'll see you guys later.
[00:28] <darkxst> JDAIII, I not sure settings scaling via xrandr directly is the best way to do it either
[00:30] <octoquad> darkxst, I've added them, do I just add a comment with "@Sponsors Team"
[00:41] <octoquad> darkxst, See https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1322925/comments/52 same version number I used.
[00:52] <darkxst> octoquad, no, you use the "subscribe somone else" link on Right hand sidebar
[00:52] <octoquad> darkxst, that is done and I have added verification-needed tag.
[00:53] <darkxst> no, don't do that! sru team adds tag it when they process
[00:54] <octoquad> I followed this: https://wiki.ubuntu.com/StableReleaseUpdates#Verification
[00:55] <darkxst> octoquad, you don't add the verification-needed tag and it doesnt say to add it there!
[00:57] <darkxst> you may need to rebase patch over that newer version, but leave it for now unless asked, its a simple diff, so whoever sponsors will do it if your lucky!
[01:02] <octoquad> darkxst, I removed the tag. Do sponsors get a message as soon as I subscribe them, or does a comment need to be generated?
[01:02] <darkxst> for now go find another bug to fix ;)
[01:02] <darkxst> it goes into the queue
[01:02] <darkxst> http://reqorts.qa.ubuntu.com/reports/sponsoring/index.html
[01:02] <octoquad> it's 3am, I'm not fixing anything right now
[01:02] <octoquad> lol
[01:02] <octoquad> ah
[01:03] <octoquad> I was looking at http://people.canonical.com/~ubuntu-archive/pending-sru.html
[01:03] <darkxst> it needs to be uploaded first, then it will appear in the sru queue
[01:03] <darkxst> and those pages don't update instantly
[01:40] <darkxst> octoquad, if you want to try, updated sbuild-launchpad-chroot scripts at ppa:darkxst/ppa
[01:40] <darkxst> it will automatically generate aliases with something like './sbuild-launchpad-chroot ppa -n trusty-amd64-sbuild --ppa gnome3-team/gnome3-staging'
[01:42] <darkxst> slightly different format on aliases now, trusty-proposed+gnome3-team~gnome3-staging+main-amd64-sbuild
[01:42] <darkxst> ^Noskcaj if you use sbuild?
[02:11] <Noskcaj> darkxst, I use pbuilder-dist
[02:14] <darkxst> sbuild is way faster provided you have apt-cacher-ng
[02:39] <darkxst> Noskcaj, gnome-icon-theme is still getting pulled into our seeds ;(
[02:46] <Noskcaj> :(
[02:46] <Noskcaj> I'll see if there's anything i can do to fix that
[02:48] <darkxst> i'm fixing gnome-shell thats pulling in gnome-icon-theme-full
[02:50] <darkxst> but seems a lot of apps pull in gnome-icon-theme
[02:50] <darkxst> also a bunch of qt stuff has snuck into the seed, no wonder the image size has gone over 1GB
[02:56] <darkxst> Noskcaj, ok, we really don't want qt-at-spi in our seed I suspect
[02:58] <darkxst> Noskcaj_, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749523
[03:00] <darkxst> perhaps that should have been "at-spi2-core | qt-at-spi"
[03:08] <darkxst> Noskcaj, can you fix that in python3-pyatspi and python-pyatspi and also forward back to debian
[04:08] <Noskcaj> I'll message the debian maintainer first to see if there's some reason for this being the way it is
[04:15] <Noskcaj> darkxst, debian maintainer says nope
[04:15] <Noskcaj> (to changing it)
[04:23] <Noskcaj> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757152
[06:05] <darkxst> Noskcaj, hmm, we really don't need it on our images, where we a limited for space
[07:11] <darkxst> wayland on vivid in vmware actually seems to work, though can't change screen resolution from 640x480
[07:12] <darkxst> ricotz, ^
[12:13] <kamil_> hi guys, i have ubuntu utopic with gnome-shell (actually dont remember whether it was clean ubuntu + gnome or ubuntu gnome)
[12:13] <kamil_> and i have problem with brightness
[12:14] <kamil_> when i boot my computer its always set to max, and when i plug/unplug it dont change automatically
[12:15] <kamil_> what can i do to make this working?
[17:58] <MrSavage> could i get some help with creating a bootable usb of ubuntu-gnome?
[17:58] <MrSavage> I tried using unetbootin but i got an error trying to boot it
[17:58] <MrSavage>  failed to load com32 file menu.c32
[19:03] <JDAIII> good morning
[19:03] <JDAIII> so the drama of my display issues continues
[19:03] <JDAIII> really contemplating self harm at this point. What is the suicide hotline number?