You are not logged in.
The latest update from 3.6.0 to 3.6.1 makes Gnome unusable for me.
A few seconds after login I will see some "unhappy computer" error picture and need to re-login.
3.6.0 was fine & I'm aware that not all packages are at 3.6.1 yet (maybe that's the issue?!)
Fallback-Mode is a temporary solution for me a.t.m.
Someone can or cannot confirm, workarounds, etc. ... ??
Last edited by init0 (2012-10-18 14:02:58)
Offline
same issue
Offline
paste the log from ~/.cache/gdm/session.log
Give what you have. To someone, it may be better than you dare to think.
Offline
Uploaded to http://pastebin.com/e0e5Ja67
Guess the fontconfig spam doesn't hurt ;-)
Offline
if it helps
Offline
same here, sudden crashes after login with the new updates. i downgraded to 3.6.0 and installed the 3.6.1 updates one by one. no crashes until i installed mutter-3.6.1-1.
downgrading to mutter-3.6.0-1 "fixed" it.
Last edited by bratkartoffel (2012-10-16 17:59:56)
Offline
Same issue here. I have a dual screen monitor and managed to get the Oh no! error into the second monitor and otherwise gnome 2.6.1 is completely usable.
my .catch/gdm/session log
Offline
same here, sudden crashes after login with the new updates. i downgraded to 3.6.0 and installed the 3.6.1 updates one by one. no crashes until i installed mutter-3.6.1-1.
downgrading to mutter-3.6.0-1 "fixed" it.
Downgrading mutter fixed it for me too thanks
Offline
I've cleared my package cache, and the Arch Rollback Machine isn't tracking the gnome-unstable repo (at least not for 3.6). Is there anyone who could upload the 3.6.0 x86_64 mutter package or PKGBUILD somewhere for me.
Thanks
Also, are we clear yet if this is a packaging bug or a problem w/ mutter 3.6.1?
Offline
i get the oh-no-fail "window", but can just alt+f4 it. here my ~/.cache/gdm/session.log
Offline
I've cleared my package cache, and the Arch Rollback Machine isn't tracking the gnome-unstable repo (at least not for 3.6). Is there anyone who could upload the 3.6.0 x86_64 mutter package or PKGBUILD somewhere for me.
Thanks
Also, are we clear yet if this is a packaging bug or a problem w/ mutter 3.6.1?
It should be in your cache, unless you cleared it.
Last edited by Jodell (2012-10-16 21:24:33)
Offline
@Jodell - I'll refer you to my first sentence...
Last edited by techryda (2012-10-16 21:34:16)
Offline
@Jodell - I'll refer you to my first sentence...
Whoops hehe.
Just change the version number and generate a new checksum https://projects.archlinux.org/svntogit … ges/mutter
Offline
@Jodell, thanks, I didn't realize gnome-unstable packages were publicly visible on https://projects.archlinux.org
Offline
same issue here thanks for the workaround
Offline
Here I uploaded mutter-3.6.0-1 here on my dropbox >> https://www.dropbox.com/s/b8rbuaimp4jil … pkg.tar.xz
Last edited by tyler1234567 (2012-10-18 01:03:05)
Offline
hups forgot my logs
~.cache/gdm/session.log http://sprunge.us/TgZF (anything at and after the ERROR:object_proxy.cc came after the fail window)
journal http://sprunge.us/OLQK
Offline
Fixed in 3.6.1-2
Offline
I have yet to restart and test that change, but it strikes me how it would fix the problem, since what it apparently does is install libsm, which I already have...
Edit: but it indeed solved the problem!
Last edited by nDray (2012-10-18 19:43:09)
Offline
Hi guys!
Same issue here...
I've upgraded from Gnome 3.4.2-1 (extras) to Gnome 3.6.0-1 (unstable). In my case, I have mutter 3.6.0-1. The weirdest thing is, ~/.cache/gdm/session.log does not exist.
Any thought?
Last edited by vKmC (2012-10-19 13:58:32)
Offline
Well, I had this issue only with mutter 3.6.1-1
3.6.0-? and 3.6.1-2 seem to work fine, why don't you try the _latest_ version?
Offline
i'm also experiencing immediate crashes w/ the latest gnome 3.6 from the testing repo. just after logging in from lightdm or gdm i get the oops screen forcing me to log out again.
the only thing i get a glance of is the "unlock login keyring" promt.
i've already reset my themes to default, but this had no effect at all. even downgrading mutter to mutter-3.6.0-1 didn't solve the prob.
Last edited by helge (2012-10-22 09:59:28)
Offline
i'm also experiencing immediate crashes w/ the latest gnome 3.6 from the testing repo. just after logging in from lightdm or gdm i get the oops screen forcing me to log out again.
the only thing i get a glance of is the "unlock login keyring" promt.
i've already reset my themes to default, but this had no effect at all. even downgrading mutter to mutter-3.6.0-1 didn't solve the prob.
Try to rename your ~/.config/dconf
Offline
Try to rename your ~/.config/dconf
This had no effect, still the same error right after logging in.
In fact, it even crashes using a completely new user... additionally gdm crashes in the same way, i cannot even enter a username.
Last edited by helge (2012-10-22 21:05:05)
Offline
xzy3186 wrote:Try to rename your ~/.config/dconf
This had no effect, still the same error right after logging in.
In fact, it even crashes using a completely new user... additionally gdm crashes in the same way, i cannot even enter a username.
Could you post your
~/.cache/gdm/session.log
Offline