[01:35] <Tumlee> Where does gnome-screenshot save all of its screenshots? I keep activating it accidentally.
[01:36] <Tumlee> gnome-screenshot --help didn't reveal any useful information to me and neither did a google search
[01:39] <Tumlee> Nevermind, I found them.
[02:13] <jaysonr> is anyone else running 3.8 from the PPA getting crashes at logon?
[02:13] <jaysonr> sometimes it'll not crash, but my "X" on my close button is black.
[02:13] <jaysonr> it'll turn white if I do an alt+f2/r to restart shell
[02:14] <jaysonr> other times it'll crash the first time I open a window and then it's white.
[03:19] <darkxst> jaysonr, I have not seen that
[03:19] <darkxst> file a bug with ubuntu-bug after reproducing the crash
[03:28] <jpickett> is there any way to hide the titlebar of windows? on a laptop the webpage doesn't start until 20% down the screen
[03:28] <jaysonr> darkxst: done (I think)
[03:30] <darkxst> jaysonr, link?
[03:31] <darkxst> jpickett, I think there is an extension for that
[03:31] <jaysonr> darkxst: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1177178
[03:31] <ubot5> Launchpad bug 1177178 in gnome-shell (Ubuntu) "GNOME-Shell crashes at logon after launching first application " [Undecided,New]
[03:32] <jaysonr> darkxst: if I didn't do something right, let me know, and I'll close that one and do it again
[03:33] <enrique_> enrique83
[03:34] <enrique_> hola!
[03:34] <enrique_> someone talk spanish?
[03:34] <darkxst> jaysonr, do you have any extensions installed with custom css files?
[03:34] <jaysonr> darkxst: I tried the system monitor extension, but it didn't work and I removed it.
[03:35] <jaysonr> darkxst: is there an easy way to reset GNOME back to complete defaults and start over? I'm happy to try if there is.
[03:35] <darkxst> jaysonr, so it his happening with no extensions installed?
[03:35] <jaysonr> darkxst: yes.
[03:36] <darkxst> jaysonr, would be good if you can get a backtrace of the crash
[03:37] <jaysonr> darkxst: how do I do that?
[03:39] <darkxst> jaysonr, you can use apport/ubuntu-bug
[03:39] <darkxst> make sure apport is enabled, and then when you get the popup to submit bug report, click examine locallu
[03:39] <darkxst> locally
[03:40] <jaysonr> apport never pops
[03:40] <darkxst> jaysonr, its disabled by default on releases
[03:40] <darkxst> or check /var/crash/ for a file with gnome-shell in the name
[03:40] <darkxst> you can run ubuntu-bug straight on that file if its there
[03:41] <jaysonr> yup, sure is
[03:41] <jaysonr> do i do it on the .crash or the .upload?
[03:41] <darkxst> .crash
[03:42] <jaysonr> darkxst: nm, that looks like it's from yesterday
[03:42] <darkxst> jaysonr, delete the file and a new one will be created with the next crash
[03:42] <jaysonr> darkxst: ok, lemme see.
[03:43] <jaysonr> darkxst: should i kill that bug that just got entered?
[03:43] <jaysonr> since that log is kinda nasty
[03:43] <darkxst> jaysonr, no thats fine
[03:43] <jaysonr> ok
[03:43] <darkxst> just add a backtrace to it once you get one
[03:43] <darkxst> i will be back in a bit
[03:50] <jaysonr> darkxst: i attached the .crash to the bug
[03:50] <jaysonr> darkxst: i need to go to bed now, but I left apport open in case I need to do anything with it.
[03:50] <jaysonr> i posted to the list earlier too if you want to reply to me there.
[03:50] <jaysonr> darkxst: thanks again for your help
[04:13] <darkxst> jaysonr, you need to process the crash report with apport first!
[04:16] <darkxst> jaysonr, run 'ubuntu-bug crashfile'
[04:18] <darkxst> click 'examine locally' and then the last option 'add symbolic trace to .crash
=== CripperZ- is now known as CripperZ
=== jaes_ is now known as jaes
=== CripperZ is now known as CripperZ-
[10:27] <darkxst> ricotz, feel like stripping the dbg packages from mozjs17 and pushing for a rebuild so it gets ddebs?
[10:28] <darkxst> I couldnt get apport-retrace to work with old school -dbg packages ;(
[10:37] <jaysonr> darkxst: sorry, when I run ubuntu-bug _usr_bin_gnome-shell.1000.crash I only have "Show Details", "Continue" and a checkbox to send error report.
[10:38] <jaysonr> darkxst: nothing about examine locally
[10:41] <jaysonr> if I click "Continue" it just goes away.
[10:44] <darkxst> jaysonr, I manage to run a trace of your .crash file, but it was useless, since the mozjs17 symbols don't work with apport ;(
[10:45] <jaysonr> darkxst: ok :(
[10:46] <jaysonr> darkxst: shell just crashed randomly on me now :(
[10:47] <jaysonr> gnome-shell crashed with SIGSEGV in clutter_actor_get_accessible()
[10:49] <darkxst> think that one is already filed somewhere
[10:50] <jaysonr> darkxst: it's like if I look at it wrong it crashes. I think I'm just gonna downgrade this box to 3.6
[10:50] <jaysonr> darkxst: will I run into trouble running PPA purge?
[10:52] <darkxst> jaysonr, 3.8 has been really stable here, much more than 3.6
[10:52] <darkxst> ppa_purge should work ok, might get a little confused with the mozjs downgrade though
[10:52] <darkxst> purging staging requires a few extra commands though
[10:52] <jaysonr> darkxst: it seems I have parts of 3.6 and parts of 3.8, is that normal?
[10:53] <jaysonr> gnomer-terminal is 3.6 for example
[10:53] <darkxst> jaysonr, yes, the rest is in staging, and not 100% ready for general use
[10:56] <jaysonr> darkxst: ok. well, when I first saw your messages in my awaylog I deleted that .crash file from the bug b/c i felt like an idot :-/
[10:56] <jaysonr> darkxst: now it's been overwritten by that second crash
[10:56] <darkxst> jaysonr, don't mix crashes! each crash should get its own bug report!
[10:57] <jaysonr> i've got to head to work but I'll fiddle with this some more. it's only a day old install, I may just re-install and see if I did/installed something that caused the instability
[10:57] <jaysonr> darkxst: i know, just wondering if you still have the .crash you processed
[10:57] <jaysonr> darkxst: but you said it wasn't much use anyway
[10:57] <darkxst> yes, but I can't do anything with it!
[10:58] <jaysonr> darkxst: okay. thanks again for being helpful. i'll fiddle more after work. everything runs great execpt for the shell crashes. i can't help but wonder if I caused it somehow. it runs fine on my notebook.
[10:59] <darkxst> jaysonr, test with a new user account?
[11:08] <jaysonr> darkxst: yeah, i'll try that after work
[13:17] <Forage> Ever since I upgraded from Ubuntu GNOME 12.10 to 13.04 the GOA accounts don't function any more. Going to the options of an account only display the Cancel and Done buttons, with no input field or text displayed below. This is the case for existing as well as new accounts.
[13:18] <Forage> It also appears that no accounts connect any more since the Empathy contact list remains empty
[13:19] <Forage> Could this have something to do with having installed the gnome3 staging ppa packages?
[13:21] <Forage> with NOT having installed those packages I mean
[13:23] <Forage> can any one confirm this behaviour with having 13.04 with gnome 3 ppa packages installed, excluding the staging ppa
=== DarkEra2 is now known as DarkEra
[18:45] <Forage> is it safe to assume that only the "*+logind~raring?" packages from the GNOME3 Staging ppa are the ones that require/use logind?
[18:52] <Forage> I found that only updating the packages from the "stable" gnome3 ppa result in a non-functioning GOA. It wasn't until I updated Empathy and libfolks (and their dependencies) that existing GOA accounts worked again. It does, however, leave you with a crashing system settings GOA section so you can't alter/add accounts. I assume this is because it would require an update for gnome-control-center as well
[18:54] <Forage> Shouldn't this have been dealt with by increasing the required version of dependencies?
[19:02] <camelinahat> Forage, I can't say much regarding the packages as I'm not a dev and not familiar with them all myself. However I'm running only the Gnome3 PPA (not staging/testing etc), and my GOA is working fine. I've been running since the Beta2 release as a clean install
[19:03] <Forage> camelinahat: strange. Are you able to modify account settings of e.g. IRC accounts and are you seeing Facebook contacts in Empathy?
[19:13] <camelinahat> I don't have an IRC for GOA only UOA. With Facebook, if I used GOA no it didn't show in Empathy, however if I use UOA and add Facebook it does show the contacts in Empathy.
[19:17] <Forage> camelinahat: than how can you say GOA is working fine for you if you aren't even using it?
[19:19] <Forage> could you perform a test by tying to add a GOA account, like IRC or Jabber (as long as it's not available as UOA account as well)? The only thing I need to know is if you are able to provide any account details in the first place. You don't actually have to save the new account
[19:31] <Forage> OK, fixed the GOA system settings crash by installing account-plugin-empathy
[19:33] <Forage> ...partially
[19:35] <camelinahat> Forage, 1) I have no option to add IRC to GOA. Period. 2) I Added facebook it went in fine but it did not add the Facebook chat contacts to my empathy. Trying it on UOA did work
[21:22] <AbsintheSyringe> what am I doing wrong? I can't see "Privacy" with GNOME 3.8 (gnome3-team ppa) on Ubuntu 13.04?
[21:41] <darkxst> AbsintheSyringe, that is only in gnome-control-center 3.8, which is still in staging
[21:41] <AbsintheSyringe> darkxst, so only way to get privacy is to get staging?
[21:42] <darkxst> AbsintheSyringe, yes, same with notifications panel also
[21:42] <AbsintheSyringe> darkxst, will these move over to "regular" ppa?
[21:42] <AbsintheSyringe> eventually
[21:43] <darkxst> yes eventually, when they are ready for general use, currently some regressions that still need fixing
[21:44] <AbsintheSyringe> I can't wait so I'll just get my hands on staging :)