New gnome-shell_3.8.0.1 in Gnome3 Staging PPA

[Stinger]

@ mc4man
It doesn't matter if I launch nautilus from the GS launcher or the app overview, GS crashes just the same.

[Roasted]

Doesn't happen with latest nautilus git (3.8.0 release+), maybe they (gnome3 ppa) just need to get more current.
Edit- did a deb package build of 3.8.0, nautilus is fine

I actually read earlier that this is the issue. Evidently an older version of Nautilus, 3.6 I have to assume, was the cause of it.

I'm finding it a little frustrating that I can't get as much of a Gnome 3.8 experience as I had hoped for, even with Ubuntu GNOME 13.04. There seems to be some friction between updating certain (and currently broken) packages via the Gnome3 PPA due to Canonical doing their own with their own time frame. I'm halfway tempted to switch to Arch to check out a real Gnome 3.8 experience that isn't quite broken.

On a positive note, besides all of that, I'm loving it.

[mc4man]

@ mc4man
It doesn't matter if I launch nautilus from the GS launcher or the app overview, GS crashes just the same.

Not sure what vindsl was using but here was using plank, fairly sure that doesn't interest you

I actually read earlier that this is the issue. Evidently an older version of Nautilus, 3.6 I have to assume, was the cause of it.

No, definitely a gnome-shell bug

On a side note noticed that keyboard bindings/custom commands are non-functional in Gs unless a window of any sorts is open, a bit of a flaw there. Clear ex. would be the run command dialog (default disabled, typically alt+F2). If enabled only works when a window is open. Or key to open activities overview, again default disabled, same deal.

[Roasted]

Turns out I actually have Nautilus 3.8 installed. But yeah, no matter what I do, all windows closed + opening Nautilus crashes it. Most of the time I get lucky and nothing crashes the first time. But so far, 100% of the time when I close Nautilus and open it a second time the UI tanks.

[VinDSL]

You are correct - just noticed small but critical 'mistake' I & likely vin where doing.[...]

Well...

I still cannot get Nautilus to crash.

I upgraded to 3.8.0...

vindsl@Zuul:~$ apt-cache policy nautilus
nautilus:
  Installed: 1:3.8.0-0ubuntu1~raring
  Candidate: 1:3.8.0-0ubuntu1~raring
  Version table:
 *** 1:3.8.0-0ubuntu1~raring 0
        500 http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ raring/main i386 Packages
        100 /var/lib/dpkg/status
     1:3.6.3-0ubuntu13 0
        500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
        500 http://samaritan.ucmerced.edu/ubuntu/ raring/main i386 Packages
     1:3.5.90.really.3.4.2-0ubuntu4.2 0
        500 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 Packages
vindsl@Zuul:~$

Then I opened 10 instances of Nautilus, and closed them. Nothing.

So, I opened and closed 3 instances. Then, opened and closed another 10 Nautilus windows. Still nothing.

What am I doing "wrong"?

LoL!

[Stinger]

Well...
I still cannot get Nautilus to crash.

I upgraded to 3.8.0...

i386 Packages

What am I doing "wrong"?

I highlighted it for ya

The bugreport is Architecture: amd64

I think that's why you are immune and can't have the bug.

[VinDSL]

I highlighted it for ya

The bugreport is Architecture: amd64

I think that's why you are immune and can't have the bug.

Good job, detective!

I knew I was missing something...

[bmbaker]

hmmm i just tested this opening 5 times nautilus and closing them and also running nautilus as root 5 times and then again as usr and no issues at all!
i am running 64 bit

[Stinger]

@ bmbaker
Lucky you then, I don't know what you are trying to tell though , the bug is very much present as you can see on these bugreports, GNOME Bugzilla – Bug 695030, Launchpad Bug#1164086 and Bug# 1164766

Just had a thought, what if we are 'barking up the wrong tree' and the villain is not GS but nautilus ? Maybe the bug should be reported against nautilus instead ?
But I'm sure the Ubuntu-GNOME team already took this into consideration.