[Solved] can not log into Gnome

Pluribootent · #1 January 14th, 2011, 17:49

Hi!

As the title says, I can't log into Gnome by GDM.
I get the following error:

Code:

freebsd gnome-keyring-daemon[1965]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk

What happens:
I type my password, hit 'Enter', the screen goes black and after 2 seconds my screen shows me GDM again.

A week ago I had to exchange my old mainboard by a new one:
old: Gigabyte GA-MA770T-UD3P:Chipset: AMD 770/SB710
new: Gigabyte GA-870A-UD3:Chipset AMD 870/SB850

The problem occured and I kept tryin to log in and finally once it worked, but never since. I read some threads about others complaining about that error-message, but they all still seemed to be able to log into Gnome, despite that error.

Maybe this issue is associated with changing the mainboard (since then the network isnt working reliable, too, and sometimes the system just hangs while starting).

Unfortunately I have not got enough experience to solve this. I appreciate any suggestions that get me back to using Gnome, so I can solve all the other issues.

edit: I can now log into gnome by using

Code:

startx

, but the network isnt working.

Code:

/etc/rc.d/netif restart

and

Code:

/etc/rc.d/routing restart

starts my network, but thats all kinda weird, since it used to work flawlessly before changing the hardware. Do I have to do something to tell the system about my new hardware?

Pluribootent · #2 January 14th, 2011, 18:16

Another error-message while loggin into Gnome through GDM:

Code:

freebsd gdm-session-worker[1821]: gkr-pam: couldn't get the user name: conversation failure

**SirDice** · #3 January 15th, 2011, 15:31

Quote:

Originally Posted by Pluribootent

As the title says, I can't log into Gnome by GDM.
I get the following error:

Code:

freebsd gnome-keyring-daemon[1965]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk

Ignore it. Everybody gets that one.

Make sure /proc (see procfs(5)) is mounted and both hald and dbus are running.

Pluribootent · #4 January 15th, 2011, 17:25

proc is mounted.

I cannot ignore it as it may not be an important error message, but still I can't login to Gnome.

Pluribootent · #5 January 17th, 2011, 14:05

Gnome seems to be working fine, but I still can't login through gdm. I reinstalled gnome and gdm. No luck upto now.

nakal · #6 January 17th, 2011, 17:35

You get the most important information from ~/.xsession-errors, in cases when password is correct and no session appears.

Also.. what type of session did you select? What is inside your ~/.xinitrc?

Pluribootent · #7 January 17th, 2011, 18:53

Thanks a lot, nakal!

Libassuan shared library was missing or something like that. So I reinstalled seahorse-plugins and it is working fine now.

Thanks again.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Solved] I can't log on using Gnome	tab2tab	GNOME	5	October 4th, 2010 20:30
[Solved] g530 gnome log in bug after 8.0 -> 8.2	big_girl	GNOME	3	September 8th, 2010 18:30
very good and nice way for read log file and search in log file	mfaridi	General	8	April 22nd, 2009 22:21
[Solved] pkg_add -r gnome will install gnome 2.22 instead of 2.24	alie	GNOME	16	March 20th, 2009 18:27
[Solved] syslogd logs to all.log, but not to my.log	fredBSD	Web & Network Services	1	March 5th, 2009 06:34

The Following User Says Thank You to nakal For This Useful Post:
Pluribootent (January 17th, 2011)