[Bug 196464] Re: After gdm upgrade no X cliens can be run
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 ownership change. Do you have this installed (xorg-driver-fglrx)? In any case, to debug I made a simple shell wrapper for xauth which logs when it is called and who calls it. Let me know if you need this. -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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 ? -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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 cause; I tried strace on it but it didn't seem to call chown itself). When I stop it, .Xauthority stays as user:user. -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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 received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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.launchpad.net/bugs/196464 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: 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: (0600/-rw---) Uid: (0/root) Gid: (0/root) Access: 2008-03-02 22:13:58.0 +0100 Modify: 2008-03-02 22:13:58.0 +0100 Change: 2008-03-02 22:13:58.0 +0100 So, ownership of .Xauthority file in my home directory went to root, I've no idea why. Can it be the reason of switching to /tmp/.gdm* files? Now, I deleted /tmp/.gdm* files, and reown to .Xauthority to myself. However this time, I get this: Invalid MIT-MAGIC-COOKIE-1 keyxterm Xt error: Can't open display: :0.0 -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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 was able to get the unlock dialog and everything works. Please note that there is 'full filesystem' or 'unwritable home' issue here, I checked these, since you had the message that this could cause my problem. -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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 member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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 notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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 name (this is the file whose ownership goes to root:root after upgrade it seems), I thought it's a file of gdm. Maybe I'm wrong, as I've written before this is only a guess from me that it's a gdm bug, it can be other, of course. So I could recompose this bugreport as cannot run X clients after major upgrades from remote ssh session, but I don't know upgrade of which package cause this exactly (well, sorry if my comment seems to be intrusive, but because my English is far from perfect I always worry about others not able to understand me correctly ...). By the way, it seems that env.var. XAUTHORITY has got value of /tmp/.gdmFV696T, exactly this file. No disk issue, I'm sure. [EMAIL PROTECTED]:~$ mount /dev/sda2 on / type ext3 (rw,noatime,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) /sys on /sys type sysfs (rw,noexec,nosuid,nodev) varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755) varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777) udev on /dev type tmpfs (rw,mode=0755) devshm on /dev/shm type tmpfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) lrm on /lib/modules/2.6.24-11-generic/volatile type tmpfs (rw) securityfs on /sys/kernel/security type securityfs (rw) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) gvfs-fuse-daemon on /home/lgb/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=lgb) [EMAIL PROTECTED]:~$ env GPG_AGENT_INFO=/tmp/seahorse-5VpTUR/S.gpg-agent:6245:1 SHELL=/bin/bash TERM=xterm XDG_SESSION_COOKIE=92ad7e3941d35ab5cf1cb600464d0b30-1204531474.834884-1282338699 CPPFLAGS=-mtune=pentium4 -march=pentium4 GTK_RC_FILES=/etc/gtk/gtkrc:/home/lgb/.gtkrc-1.2-gnome2 WINDOWID=59149577 USER=lgb LD_LIBRARY_PATH=/home/lgb/.local/lib LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.svgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36: SSH_AUTH_SOCK=/tmp/keyring-5FJjf6/ssh GNOME_KEYRING_SOCKET=/tmp/keyring-5FJjf6/socket SESSION_MANAGER=local/vega:/tmp/.ICE-unix/6176 USERNAME=lgb MAIL=/home/lgb/.maildir/ DESKTOP_SESSION=default PATH=/home/lgb/.local/bin:/home/lgb/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games [EMAIL PROTECTED] GDM_XSERVER_LOCATION=local PWD=/home/lgb LANG=en_US.UTF-8 GNOME_KEYRING_PID=6175 GDM_LANG=en_US.UTF-8 GDMSESSION=default HOME=/home/lgb SHLVL=1 CFLAGS=-mtune=pentium4 -march=pentium4 GNOME_DESKTOP_SESSION_ID=Default LOGNAME=lgb XDG_DATA_DIRS=/usr/local/share/:/usr/share/:/usr/share/gdm/ DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-cpBm0IG9ur,guid=73d41efe1a2c829852672f1947cbb117 DEBFULLNAME=Gabor Lenart [EMAIL PROTECTED] WINDOWPATH=7 DISPLAY=:0.0 COLORTERM=gnome-terminal XAUTHORITY=/tmp/.gdmFV696T _=/usr/bin/env -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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 I've discovered that this bug is easier to reproduce if: 1. lock the screen 2. login from remote via ssh 3. install packages/upgrades (gdm as well?) via apt-get from remote 4. come back to the console 5. try to unlock It does not work, no password input dialog or shown, only mouse cursor blinks. If I switch to text console and kill gnome-screensaver, then switch back to my X/gnome session, the reported bug occures, no X clients can be run. However I don't remember that ALL similar bugs were got only in this mode ... ** Attachment added: stuff.tgz http://launchpadlibrarian.net/12360824/stuff.tgz -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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 (desktop-bugs) Status: New = Incomplete -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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 strace them indicated that a file in /tmp/ directory can't be opened because of the root ownership, after chown'ing back to my user it works, so I assume that it was owened by me before (since X clients worked before) however something alterted the ownership of that file to root and this is the problem. I'm not sure that gdm upgrade caused this, though, only guessing. /etc/gdm/gdm.conf is attached. However I'm not sure what king of log should I post here. ** Attachment added: gdm.conf http://launchpadlibrarian.net/12339480/gdm.conf -- 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196464] Re: After gdm upgrade no X cliens can be run
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, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs