Bug 50212
Summary: | nautilus doesn't start on any display besides :0 | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Ed McKenzie <eem12> |
Component: | fam | Assignee: | Alexander Larsson <alexl> |
Status: | CLOSED DUPLICATE | QA Contact: | Aaron Brown <abrown> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 1.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-08-10 15:02:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ed McKenzie
2001-07-28 05:57:22 UTC
Works for me if I add a display in gdm, or change the only display to 1. Maybe my interpretation of "change the default display number" is different from yours? Exactly what is the line in gdm.conf that you have? If I create a new profile and run startx -- :1, nautilus won't start; if I strace it from the console, it seems to hang on a select call (lots of strings beginning with 'GIOP' are being read() at the time, if that's useful info.) The same profile starts nautilus flawlessly every time on :0. This is all with nautilus-1.0.4.1-1. I should add that having a display running on :0 doesn't seem to affect how nautilus behaves on other displays. Where did you get nautilus-1.0.4.1-1? Our current is nautilus-1.0.4-25. Does it happen with whatever is latest in rawhide? nautilus-1.0.4.1-1 was from rawhide (18 july 2001.) i'll do a clean install of roswell this weekend and see if that fixes it. Roswell fixed it. Thanks Actually, I lied -- it's still broken. If I create users A, B, and C and log in simultaneously on :0, :1, and :2, nautilus only starts on :0. Each user's profile works properly when logged in on :0. The multiple-users thing is a fam problem. Alex was looking into that, so I've assigned him the bug. |