As described in the previous comments, your report lacks the information
we need to investigate the problem further. We'll close this report for
now - please reopen it if you can give us the missing information.
** Changed in: gdm (Ubuntu)
Status: Needs Info => Rejected
--
Cannot run gdms
Do you have a /tmp/.gdm_socket when you get that problem? Do you use
something like bootclean?
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** This bug is no longer a duplicate of bug 79660
gdmsetup halts on futex
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
*** This bug is a duplicate of bug 79660 ***
** This bug has been marked a duplicate of bug 79660
gdmsetup halts on futex
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Tried going back to S13 for gdmand the old problem came back, long
delays before the desktop comes up and gdmsetup can't run. Spash screen
reverts to default as well.
Back to S21 and everything is normal.
Something between S13 and S20 has to run before GDM, and why is there no
socket when GDM
dunno, i'm on mac os x now... but I will reinstall ubuntu on the
other machine for my parents, then I can reopen the bug if it still
persists.
Em 25/12/2006, às 19:35, Sebastien Bacher escreveu:
> Do you still have that bug on edgy without changing the gdm startup?
>
> --
> Cannot run gdmset
Do you still have that bug on edgy without changing the gdm startup?
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Well I am "happy" with the workaround but it bugs me why the problem
only seemed to affect 3 or 4 people. Looking at the init scripts for
Dapper and Edgy, I did notice that dbus runs from an s20 script in Edgy,
while it is s12 in Dapper. GDM runs with s13 in both cases ( except as I
changed it to
maybe, we are not going to change the package without any rationnal just
to workaround a problem which happened to one people, could be due to
something on your configuration. If you are happy with the workaround we
can close the bug, otherwise trying what need to be started before gdm
would be a g
Never did try to figure it out. I changed S13gdm to S21gdm and it
worked well, so obviously something in between has to run first ?
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desk
Do you still have that problem? Could anybody try to figure what should
be started before gdm and is not with the current numbers used?
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/de
** Attachment added: "gdm.conf-custom"
http://librarian.launchpad.net/4874119/gdm.conf-custom
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Yes, I had noticed that. Funny thing is, I'm not running (or have
installed) nvidia-glx, so that's purely redundant. I'm using the nv
driver because of the security vuln that appeared some days ago and
because frankly I've got no use for the 3d driver yet. Still, it'd be a
pretty big thing to miss.
S13gdm and S20nvidia-kernel should be a tip as to why it doesn't work...
at least in my case.
When will this be fixed?
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
The problem here is Ubuntu devs are keen on starting GDM as soon as
possible, to give the user the illusion of a faster bootup (just like
Windows, I might add), while things keep loading in the background.
Evidently there's a balance to be struck and we got caught in the "ugly"
side of it.
It's a
Works for me. Simple solution to what seemed a complex problem,
On Mon, 23 Oct 2006 12:46:38 +
Adriano Varoli Piazza <[EMAIL PROTECTED]> wrote:
> My mistake, I'd mystyped s21gdm instead of S21gdm. It now works
> (though it seems like it takes more to open gdm, probably because it
> does). M
My mistake, I'd mystyped s21gdm instead of S21gdm. It now works (though
it seems like it takes more to open gdm, probably because it does).
Maybe some other initscript can be moved after it? I attach my
(modified) setup for /etc/rc2.d as a text file.
** Attachment added: "modified setup for rc2.d
No, mv'ing the symlinks didn't help, in fact gdm didn't start at all.
Running
sudo /usr/sbin/gdm
gave me the normal, edgy gdm screen.
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/de
After the comments in the upstream bug, this seems to be caused because
GDM is started too early by init, so a possible solution is going to
/etc/rc2.d/ and changing S13gdm to, say, S21gdm . It's worth a try, so
I'll post more about it in a reboot.
--
Cannot run gdmsetup
https://launchpad.net/bug
I subscribe the above, same results here after I booted up today (I'd
noticed it before, but didn't worry about it).
Plus, in my case the gdm screen has reverted to the "default" Flowers theme.
I see no /tmp/.gdm_socket file either (after logging in at least).
--
Cannot run gdmsetup
https://laun
Here they are :
** Attachment added: "gdm.conf"
http://librarian.launchpad.net/4874117/gdm.conf
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I looked in /tmp and there is no socket with gdm in the name. I have
attached syslog with debug turned on. I don't use either NFS or NIS.
** Attachment added: "syslog with debug"
http://librarian.launchpad.net/440/syslog
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
deskt
That looks like bug #62342. Do you know how to rebuild a package with a
gdm? The issue looks similar to
http://bugzilla.gnome.org/show_bug.cgi?id=343091 upstream. Do you have a
/tmp/.gdm_socket? Do you use NFS or NIS?
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs maili
Can you attach your /etc/gdm/gdm.conf*?
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Thanks for your bug report. Which version of gdm do you use? Can you run
sudo gdmsetup
from the command line and paste the full output here?
** Changed in: gdm (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
25 matches
Mail list logo
