also, for those of us who have a shared network home directory, logging onto
two machines causes them
to stomp on the same .xsession-errors file. It would be nice to have a per-host
.xsession-errors file.
Someone suggested we argue upstream so I've done that:
This was fixed in gdm 3.6 which saves user logs to
$XDG_CACHE_HOME/gdm/session.log by default.
** Changed in: gdm (Ubuntu)
Status: Confirmed = Fix Released
** Bug watch added: GNOME Bug Tracker #627939
https://bugzilla.gnome.org/show_bug.cgi?id=627939
** Changed in: gdm
Importance:
** Changed in: gdm
Status: Unknown = Fix Released
** Changed in: gdm
Importance: Unknown = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/382879
Title:
gdm should not hardcode
Thank you for your bug report. The issue is an upstream one and it would
be nice if somebody having it could send the bug the to the people
writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)
** Changed in: gdm (Ubuntu)
Importance: Low = Wishlist
** Changed in: gdm (Ubuntu)
Not sure why would anybody want to change the log names but if whoever
feel strongly about that should argue upstream too
--
gdm should not hardcode name of ~/.xsession-errors
https://bugs.launchpad.net/bugs/382879
You received this bug notification because you are a member of Ubuntu
Bugs, which
Not sure why would anybody want to change the log names
If you re-read my original bug report, you'll see that we're more
interested in changing the path of the file than its name. GDM, like
most GNOME products, assumes that all home directories are stored on
local disk and that processes
Right, not sure if allowing changing the log file is the right way
though, the gdm user code should perhaps just copy this log somewhere
else in such cases, to discuss upstream in any case since the bug is not
ubuntu specific
** Also affects: gdm
Importance: Undecided
Status: New
--
did you have any change to try on karmic?
--
gdm should not hardcode name of ~/.xsession-errors
https://bugs.launchpad.net/bugs/382879
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It looks like GDM still hard-codes the ~/.xsession-errors path (see
GDM_SESSION_DEFAULT_PATH in daemon/gdm-session-worker.c).
There is, of course, a slightly different problem. As of gdm 2.80, it
seems that GDM no longer displays a popup if your login session lasts
less than 10 seconds. Now we
To reproduce:
1) Set up an AFS infrastucture with Kerberos authentication, or an NFS
infrastructure where the local gdm daemon (running as root) does not have
permission to read a user's remote home directory.
2) Ensure that the login process fails (perhaps by setting the user's shell to
tcsh
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: gdm (Ubuntu)
Could you also try the new gdm codebase on karmic?
--
gdm should not hardcode name of ~/.xsession-errors
https://bugs.launchpad.net/bugs/382879
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
12 matches
Mail list logo
