Summary: | app-crypt/seahorse-2.22.3: seahorse-agent dies on startup | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrey Vihrov <andrey.vihrov> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bugzilla-gentoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | .xsession-errors as produced by starting Gnome with empty home directory |
Description
Andrey Vihrov
2009-09-13 11:25:04 UTC
please attach .xsession-errors and reopen. Created attachment 203928 [details]
.xsession-errors as produced by starting Gnome with empty home directory
Doesn't look so suspicious... If only the "1252845429.160951 Session manager: disconnected..." line.
Reopening. Could you log into a console before starting your graphical session and start seahorse-agent by hand, if it dies, please start it in gdb and provide a backtrace [1] [1] http://www.gentoo.org/proj/en/qa/backtraces.xml (In reply to comment #4) > Could you log into a console before starting your graphical session and start > seahorse-agent by hand, if it dies, please start it in gdb and provide a > backtrace [1] > > [1] http://www.gentoo.org/proj/en/qa/backtraces.xml > I don't know about the original poster, but I was also seeing this behavior on the same configuration (amd64, gnome 2.24, seahorse-2.22.3). I debugged it down to the same problem as bug #281729 (improper initialization of gpgme 1.2.0). The patch attached in that bug fixed this problem for me. (In reply to comment #5) The patch fixes the problem indeed, thanks. *** This bug has been marked as a duplicate of bug 281729 *** |