** Tags added: hardy
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Another work-around seems to be to unset the environment variable
XAUTHORITY when upgrading or restarting atieventsd.
As in XAUTHORITY= aptitude dist-upgrade.
--
After gdm upgrade no X cliens can be run
https://bugs.launchpad.net/bugs/196464
You received this bug notification because you are a
Still have this bug, quite annoying on upgrades have something about
atieventsd ... This is 32 bit hardy, Version of xorg-driver-fglrx is
1:7.1.0-8-3+2.6.24.13-19.42
--
After gdm upgrade no X cliens can be run
https://bugs.launchpad.net/bugs/196464
You received this bug notification because you
Confirmed with xorg-driver-fglrx 1:7.1.0-8-3+2.6.24.12-17.35
I'm so glad I finally found a temporary solution to this other than
restarting X, it's been killing my productivity!
It seems that even just *stopping* atieventsd causes this problem. When
atieventsd closes, it runs:
No, this sounds like the normal and expected mode of operation (the gui
update tools also run under sudo, AFAIK).
I have now found an easy way to reproduce:
/etc/init.d/atieventsd restart
You have to log out to get back to normal operation (or do
/etc/init.d/atieventsd stop; chown $USER:$USER
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
reassigning to xorg-driver-fglrx
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Sourcepackagename: gdm = linux-restricted-modules-2.6.24
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned)
--
After gdm upgrade no X cliens can be run
https://bugs.launchpad.net/bugs/196464
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 ?
I usually upgrades distribution and install packages by hand, with 'sudo
bash' in a terminal to get a root shell than do the work with 'apt-get'.
I guess this can be a problem for some config script in packages running
as user root but eg got /home/myuser/ as home directory, or something
similar?
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
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
Bugs, which is
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
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
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:
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
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
Bugs, which is subscribed to Ubuntu.
--
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
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
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
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
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
Bugs, which
21 matches
Mail list logo
