The same for me :) No gdm upgrade but something else, but don't know
which package exactly but yes, xorg-driver-fglrx is installed:
[EMAIL PROTECTED]:~$ dpkg-query -W xorg-driver-fglrx
xorg-driver-fglrx 1:7.1.0-8-3+2.6.24.12-16.34
So maybe it's not about gdm but package xorg-driver-fglrx ?
Again today, after dist-upgrade. But this time gdm was not upgraded,
although xorg-driver-fglrx (which has atieventsd) was.
I tried to look deeper into this, and it seems that in this case it is
caused by atieventsd calling "xauth add/remove -f /home/xxx/.Xauthority"
as root, which triggers the ow
So I've altered the status to confirmed since this problem affects other
users too, it seems. For me, dist-upgrade often triggers this bug.
** Changed in: gdm (Ubuntu)
Status: Incomplete => Confirmed
--
After gdm upgrade no X cliens can be run
https://bugs.launchpad.net/bugs/196464
You re
I forgot to say: This also happened immediately after "aptitude dist-
upgrade". A number of packages were updated, including gdm.
--
After gdm upgrade no X cliens can be run
https://bugs.launchpad.net/bugs/196464
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I have seen the same problem (I do not know if it is related to GDM, but
this is with hardy).
At the moment it's particularly bad; .Xauthority reverts to root:root
within a second of changing it by hand to user:user.
It seems to be atieventsd which is the trigger of this (but possibly not
the cau
And happened again. This time no screen lock just a simple apt-get
update / upgrade. Then no X clients could be run. Again. .Xauthority was
owned by the root user! After chowin'ing back to my user everything
continued to work, it seems.
--
After gdm upgrade no X cliens can be run
https://bugs.lau
And happened again! My home directory IS writable, no disk full issue.
However I found this:
[EMAIL PROTECTED]:~$ sudo stat .Xauthority
File: `.Xauthority'
Size: 214 Blocks: 8 IO Block: 4096 regular file
Device: 802h/2050d Inode: 6996468 Links: 1
Access: (0600/
I have this issue again and again ... Yesterday I started dist-upgrade
and lock the screen to have some coffee. When I returned I had the same
issue I couldn't get the unlock password dialog, switching to text
terminal I was able to correct the ownership of that /tmp/.gdm* file.
After this move I w
switching to new, that doesn't seem to be a bug, something is changing
the xauthority location usually that is the case when the user directory
is not writable
--
After gdm upgrade no X cliens can be run
https://bugs.launchpad.net/bugs/196464
You received this bug notification because you are a m
something makes gdm switch the xauthority there, not sure what, to debug
by somebody having the issue
--
After gdm upgrade no X cliens can be run
https://bugs.launchpad.net/bugs/196464
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Ok, but if it's true that gdm should not using tmp, what's this in the
output of strace (it's an example, now I run xterm)?
[EMAIL PROTECTED]:~$ strace -o /tmp/L xterm
[...]
access("/tmp/.gdmFV696T", R_OK) = 0
open("/tmp/.gdmFV696T", O_RDONLY) = 4
Since the file has "gdm" in its nam
could you run env and mount and copy the log to a comment? are you sure
you have no disk issue? gdm should not be using tmp to store things and
other software should not have to stat this one
--
After gdm upgrade no X cliens can be run
https://bugs.launchpad.net/bugs/196464
You received this bug
Some files packed into a tgz file is attached. My home directory:
[EMAIL PROTECTED]:~$ ls -ld ~
drwxr-xr-x 239 lgb lgb 20480 2008-03-03 09:06 /home/lgb
[EMAIL PROTECTED]:~$ whoami
lgb
(note: pidgin segfault can be seen in file 'dmesg' is already reported
as #197146 by me, so ignore it here)
Now
Could you attach your gdm.conf-custom, .xsession-errors, Xorg.0.log,
dmesg, messages and syslog? Is your user directory writable?
--
After gdm upgrade no X cliens can be run
https://bugs.launchpad.net/bugs/196464
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
As I've mentioned I'm not sure that it's caused by gdm or gdm upgrade
but this problem occurs on larger upgrades and at least it seemed for me
that gdm can be the reason. However I'm only sure in the symptom: no X
clients can be run at one point (as far as I remember after upgrades),
trying to stra
Thank you for your bug report. Could you attach your gdm configuration
and log to the bug? There should be no file under tmp used, are you sure
you are running the ubuntu version?
** Changed in: gdm (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs (deskto
16 matches
Mail list logo
