--------------------------------------------------------------------- Fedora Test Update Notification FEDORA-2006-661 2006-06-06 ---------------------------------------------------------------------
Product : Fedora Core 5 Name : gdm Version : 2.14.4 Release : 1.fc5.2 Summary : The GNOME Display Manager. Description : Gdm (the GNOME Display Manager) is a highly configurable reimplementation of xdm, the X Display Manager. Gdm allows you to log into your system with the X Window System running and supports running several different X sessions on your local machine at the same time.
--------------------------------------------------------------------- Update Information:
This update corrects a dependency. --------------------------------------------------------------------- * Tue Jun 6 2006 Matthias Clasen mclasen@redhat.com - 1:2.14.4-1.fc.2 - Require system-logos, not fedora-logos - Add missing BuildRequires
--------------------------------------------------------------------- This update can be downloaded from: http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/5/
00a43e93147d507ba0baaff8fc8b85e5e7ba20a1 SRPMS/gdm-2.14.4-1.fc5.2.src.rpm 00a43e93147d507ba0baaff8fc8b85e5e7ba20a1 noarch/gdm-2.14.4-1.fc5.2.src.rpm 7060b2daa9c92a815426bd7453a6d3276256c2ae ppc/gdm-2.14.4-1.fc5.2.ppc.rpm 51ba6f069b6e182054e42607fb07877f0b814058 ppc/debug/gdm-debuginfo-2.14.4-1.fc5.2.ppc.rpm afdb1dd29769557f294f66bfe6424841b8cbecbb x86_64/gdm-2.14.4-1.fc5.2.x86_64.rpm c6906d499beb38a50dd089f34ceb550776c9ef33 x86_64/debug/gdm-debuginfo-2.14.4-1.fc5.2.x86_64.rpm c5311c928b51bbc0b778f4096ccf1983b01890bc i386/debug/gdm-debuginfo-2.14.4-1.fc5.2.i386.rpm 2d847968092a76733c8928c3a3f23ae1edecf6ad i386/gdm-2.14.4-1.fc5.2.i386.rpm
This update can be installed with the 'yum' update program. Use 'yum update package-name' at the command line. For more information, refer to 'Managing Software with yum,' available at http://fedora.redhat.com/docs/yum/. ---------------------------------------------------------------------
GDM didn't startup after the update:
cat :0.log GDM: Xserver not found: /usr/X11R6/bin/X :0 -audit 0 -auth /var/gdm/:0.Xauth-nolisten tcp vt7 Error: Command could not be executed! Please install the X server or correct GDM configuration and restart GDM.
On 6/6/06, Matthias Clasen mclasen@redhat.com wrote:
Fedora Test Update Notification FEDORA-2006-661 2006-06-06
Product : Fedora Core 5 Name : gdm Version : 2.14.4 Release : 1.fc5.2 Summary : The GNOME Display Manager. Description : Gdm (the GNOME Display Manager) is a highly configurable reimplementation of xdm, the X Display Manager. Gdm allows you to log into your system with the X Window System running and supports running several different X sessions on your local machine at the same time.
Update Information:
This update corrects a dependency.
- Tue Jun 6 2006 Matthias Clasen mclasen@redhat.com - 1:2.14.4-1.fc.2
- Require system-logos, not fedora-logos
- Add missing BuildRequires
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/5/
00a43e93147d507ba0baaff8fc8b85e5e7ba20a1 SRPMS/gdm-2.14.4-1.fc5.2.src.rpm 00a43e93147d507ba0baaff8fc8b85e5e7ba20a1 noarch/gdm- 2.14.4-1.fc5.2.src.rpm 7060b2daa9c92a815426bd7453a6d3276256c2ae ppc/gdm-2.14.4-1.fc5.2.ppc.rpm 51ba6f069b6e182054e42607fb07877f0b814058 ppc/debug/gdm- debuginfo-2.14.4-1.fc5.2.ppc.rpm afdb1dd29769557f294f66bfe6424841b8cbecbb x86_64/gdm- 2.14.4-1.fc5.2.x86_64.rpm c6906d499beb38a50dd089f34ceb550776c9ef33 x86_64/debug/gdm- debuginfo-2.14.4-1.fc5.2.x86_64.rpm c5311c928b51bbc0b778f4096ccf1983b01890bc i386/debug/gdm- debuginfo-2.14.4-1.fc5.2.i386.rpm 2d847968092a76733c8928c3a3f23ae1edecf6ad i386/gdm-2.14.4-1.fc5.2.i386.rpm
This update can be installed with the 'yum' update program. Use 'yum update package-name' at the command line. For more information, refer to 'Managing Software with yum,' available at http://fedora.redhat.com/docs/yum/.
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On Tue, Jun 06, 2006 at 08:08:47PM -0500, Justin Conover wrote:
GDM didn't startup after the update:
It seems that it is good to have an "overspecified" /etc/gdm/custom.conf as I did not notice that something went awry. Of course that also means that I missed the bug. :-)
Seriously though. At least for the time beeing you can override wrong locations and commands in your custom.conf. Whatever you will change will take a precedence over /usr/share/gdm/defaults.conf, which you can use as a source of patterns, and gdm will start working again.
Michal
On 6/6/06, Michal Jaegermann michal@harddata.com wrote:
On Tue, Jun 06, 2006 at 08:08:47PM -0500, Justin Conover wrote:
GDM didn't startup after the update:
It seems that it is good to have an "overspecified" /etc/gdm/custom.conf as I did not notice that something went awry. Of course that also means that I missed the bug. :-)
Seriously though. At least for the time beeing you can override wrong locations and commands in your custom.conf. Whatever you will change will take a precedence over /usr/share/gdm/defaults.conf, which you can use as a source of patterns, and gdm will start working again.
To fix the problem I had to first 'chmod +w /usr/share/gdm/defaults.conf' as root and then replace all instances of '/usr/X11R6/bin' to '/usr/bin' in defaults.conf. I have a custom.conf as well but it's not overspecified.
Then it worked. I guess the latest GDM rpm is borked then?
Benjy
Michal
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On Wed, Jun 07, 2006 at 12:10:40PM -0400, Benjy Grogan wrote:
To fix the problem I had to first 'chmod +w /usr/share/gdm/defaults.conf' as root and then replace all instances of '/usr/X11R6/bin' to '/usr/bin' in defaults.conf.
That is precisely what I suggested NOT to do. Instead of changing /usr/share/gdm/defaults.conf you can override settings in /etc/gdm/custom.conf. Both to fix some mistakes and to make your own changes. This is exactly why you have the later file. 'defaults.conf' will get clobbered on the next update.
I guess the latest GDM rpm is borked then?
Indeed. In no uncertain terms.
Michal
On Wed, 2006-06-07 at 10:51 -0600, Michal Jaegermann wrote:
On Wed, Jun 07, 2006 at 12:10:40PM -0400, Benjy Grogan wrote:
To fix the problem I had to first 'chmod +w /usr/share/gdm/defaults.conf' as root and then replace all instances of '/usr/X11R6/bin' to '/usr/bin' in defaults.conf.
That is precisely what I suggested NOT to do. Instead of changing /usr/share/gdm/defaults.conf you can override settings in /etc/gdm/custom.conf. Both to fix some mistakes and to make your own changes. This is exactly why you have the later file. 'defaults.conf' will get clobbered on the next update.
I guess the latest GDM rpm is borked then?
Indeed. In no uncertain terms.
Michal
At least the changes to /usr/share/gdm/defaults.conf will revert back to default (hopefully correct) on the next update, whereas /etc/gdm/custom.conf will not (I assume).
Therefore, change /usr/share/gdm/defaults.conf for the workaround and /etc/gdm/custom.conf for customization.
Bob...
----- Original Message ----- From: "Bob Chiodini" robert.chiodini-1@ksc.nasa.gov To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Sent: Wednesday, June 07, 2006 10:02 AM Subject: Re: Fedora Core 5 Test Update: gdm-2.14.4-1.fc5.2
On Wed, 2006-06-07 at 10:51 -0600, Michal Jaegermann wrote:
On Wed, Jun 07, 2006 at 12:10:40PM -0400, Benjy Grogan wrote:
To fix the problem I had to first 'chmod +w /usr/share/gdm/defaults.conf' as root and then replace all instances of '/usr/X11R6/bin' to '/usr/bin' in defaults.conf.
That is precisely what I suggested NOT to do. Instead of changing /usr/share/gdm/defaults.conf you can override settings in /etc/gdm/custom.conf. Both to fix some mistakes and to make your own changes. This is exactly why you have the later file. 'defaults.conf' will get clobbered on the next update.
I guess the latest GDM rpm is borked then?
Indeed. In no uncertain terms.
Michal
At least the changes to /usr/share/gdm/defaults.conf will revert back to default (hopefully correct) on the next update, whereas /etc/gdm/custom.conf will not (I assume).
Therefore, change /usr/share/gdm/defaults.conf for the workaround and /etc/gdm/custom.conf for customization.
Bob...
You can also do a workaround by doing a 'ln -s ../../bin/X X' in the /usr/X11R6/bin directory.
Jim
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
Jim Bevier wrote:
----- Original Message ----- From: "Bob Chiodini" robert.chiodini-1@ksc.nasa.gov To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Sent: Wednesday, June 07, 2006 10:02 AM Subject: Re: Fedora Core 5 Test Update: gdm-2.14.4-1.fc5.2
On Wed, 2006-06-07 at 10:51 -0600, Michal Jaegermann wrote:
On Wed, Jun 07, 2006 at 12:10:40PM -0400, Benjy Grogan wrote:
To fix the problem I had to first 'chmod +w /usr/share/gdm/defaults.conf' as root and then replace all instances of '/usr/X11R6/bin' to '/usr/bin' in defaults.conf.
That is precisely what I suggested NOT to do. Instead of changing /usr/share/gdm/defaults.conf you can override settings in /etc/gdm/custom.conf. Both to fix some mistakes and to make your own changes. This is exactly why you have the later file. 'defaults.conf' will get clobbered on the next update.
I guess the latest GDM rpm is borked then?
Indeed. In no uncertain terms.
Michal
At least the changes to /usr/share/gdm/defaults.conf will revert back to default (hopefully correct) on the next update, whereas /etc/gdm/custom.conf will not (I assume).
Therefore, change /usr/share/gdm/defaults.conf for the workaround and /etc/gdm/custom.conf for customization.
Bob...
You can also do a workaround by doing a 'ln -s ../../bin/X X' in the /usr/X11R6/bin directory.
Jim
Or yum erase gdm, which I did.
At first symptom, a respawning gdm, I ran system-config-display thinking it was a problem with the xorg-updates. X started with startx. Upon the next reboot, gdm crashed again.
Anyway, other factors are broken with gdm. One of the problems is to configure auto-login and probably other features as well.
I noticed gdm is updated within the last development updates. Is it safe to install again?
Jim Cornette
On Wed, 2006-06-07 at 18:33 -0400, Jim Cornette wrote:
Jim Bevier wrote:
----- Original Message ----- From: "Bob Chiodini" robert.chiodini-1@ksc.nasa.gov To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Sent: Wednesday, June 07, 2006 10:02 AM Subject: Re: Fedora Core 5 Test Update: gdm-2.14.4-1.fc5.2
On Wed, 2006-06-07 at 10:51 -0600, Michal Jaegermann wrote:
On Wed, Jun 07, 2006 at 12:10:40PM -0400, Benjy Grogan wrote:
To fix the problem I had to first 'chmod +w /usr/share/gdm/defaults.conf' as root and then replace all instances of '/usr/X11R6/bin' to '/usr/bin' in defaults.conf.
That is precisely what I suggested NOT to do. Instead of changing /usr/share/gdm/defaults.conf you can override settings in /etc/gdm/custom.conf. Both to fix some mistakes and to make your own changes. This is exactly why you have the later file. 'defaults.conf' will get clobbered on the next update.
I guess the latest GDM rpm is borked then?
Indeed. In no uncertain terms.
Michal
At least the changes to /usr/share/gdm/defaults.conf will revert back to default (hopefully correct) on the next update, whereas /etc/gdm/custom.conf will not (I assume).
Therefore, change /usr/share/gdm/defaults.conf for the workaround and /etc/gdm/custom.conf for customization.
Bob...
You can also do a workaround by doing a 'ln -s ../../bin/X X' in the /usr/X11R6/bin directory.
Jim
Or yum erase gdm, which I did.
At first symptom, a respawning gdm, I ran system-config-display thinking it was a problem with the xorg-updates. X started with startx. Upon the next reboot, gdm crashed again.
Anyway, other factors are broken with gdm. One of the problems is to configure auto-login and probably other features as well.
I noticed gdm is updated within the last development updates. Is it safe to install again?
It should be, I'm about to reboot to test :) Jeremy rebuilt yesterday with a fix targetted at this exact problem.
Dan
Jim Cornette
--
- liw prefers not to have Linus run Debian, because then /me would have to run Red Hat, just to keep the power balance :) -- #Debian
On 6/8/06, Dan Williams dcbw@redhat.com wrote:
On Wed, 2006-06-07 at 18:33 -0400, Jim Cornette wrote:
Jim Bevier wrote:
----- Original Message ----- From: "Bob Chiodini" robert.chiodini-1@ksc.nasa.gov To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Sent: Wednesday, June 07, 2006 10:02 AM Subject: Re: Fedora Core 5 Test Update: gdm-2.14.4-1.fc5.2
On Wed, 2006-06-07 at 10:51 -0600, Michal Jaegermann wrote:
On Wed, Jun 07, 2006 at 12:10:40PM -0400, Benjy Grogan wrote:
To fix the problem I had to first 'chmod +w /usr/share/gdm/defaults.conf' as root and then replace all
instances
of '/usr/X11R6/bin' to '/usr/bin' in defaults.conf.
That is precisely what I suggested NOT to do. Instead of changing /usr/share/gdm/defaults.conf you can override settings in /etc/gdm/custom.conf. Both to fix some mistakes and to make your own changes. This is exactly why you have the later file. 'defaults.conf' will get clobbered on the next update.
I guess the latest GDM rpm is borked then?
Indeed. In no uncertain terms.
Michal
At least the changes to /usr/share/gdm/defaults.conf will revert back
to
default (hopefully correct) on the next update, whereas /etc/gdm/custom.conf will not (I assume).
Therefore, change /usr/share/gdm/defaults.conf for the workaround and /etc/gdm/custom.conf for customization.
Bob...
You can also do a workaround by doing a 'ln -s ../../bin/X X' in the /usr/X11R6/bin directory.
Jim
Or yum erase gdm, which I did.
At first symptom, a respawning gdm, I ran system-config-display thinking it was a problem with the xorg-updates. X started with startx. Upon the next reboot, gdm crashed again.
Anyway, other factors are broken with gdm. One of the problems is to configure auto-login and probably other features as well.
I noticed gdm is updated within the last development updates. Is it safe to install again?
It should be, I'm about to reboot to test :) Jeremy rebuilt yesterday with a fix targetted at this exact problem.
Dan
Jim Cornette
--
- liw prefers not to have Linus run Debian, because then /me would have to run Red Hat, just to keep the power balance :) -- #Debian
--
I can confirm that gdm is back and running in update-testing.
Thanks,
Dan Williams wrote:
On Wed, 2006-06-07 at 18:33 -0400, Jim Cornette wrote:
Or yum erase gdm, which I did.
At first symptom, a respawning gdm, I ran system-config-display thinking it was a problem with the xorg-updates. X started with startx. Upon the next reboot, gdm crashed again.
Anyway, other factors are broken with gdm. One of the problems is to configure auto-login and probably other features as well.
I noticed gdm is updated within the last development updates. Is it safe to install again?
It should be, I'm about to reboot to test :) Jeremy rebuilt yesterday with a fix targetted at this exact problem.
Dan
X is bootable now. The problem with running gdmsetup in order to change themes, make an account auto-login is still broken.
I'll attach to or file a report for that problem.
Thanks!
Jim
On 6/7/06, Michal Jaegermann michal@harddata.com wrote:
On Wed, Jun 07, 2006 at 12:10:40PM -0400, Benjy Grogan wrote:
To fix the problem I had to first 'chmod +w /usr/share/gdm/defaults.conf' as root and then replace all instances of '/usr/X11R6/bin' to '/usr/bin' in defaults.conf.
That is precisely what I suggested NOT to do. Instead of changing /usr/share/gdm/defaults.conf you can override settings in /etc/gdm/custom.conf. Both to fix some mistakes and to make your own changes. This is exactly why you have the later file. 'defaults.conf' will get clobbered on the next update.
But the problem is with defaults.conf. Too much work to overspecify everything.
Benjy
I guess the latest GDM rpm is borked then?
Indeed. In no uncertain terms.
Michal
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On Wed, Jun 07, 2006 at 02:47:01PM -0400, Benjy Grogan wrote:
But the problem is with defaults.conf. Too much work to overspecify everything.
Who said "everything"? 'StandardXServer=...' in custom.conf should likely do for the moment. Just make sure that you comment that out when testing the next version. This goes into '[daemon]' section.
Michal
On 6/6/06, Justin Conover justin.conover@gmail.com wrote:
GDM didn't startup after the update:
cat :0.log GDM: Xserver not found: /usr/X11R6/bin/X :0 -audit 0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7 Error: Command could not be executed! Please install the X server or correct GDM configuration and restart GDM.
I've got the identical problem. I have the updates-testing and aiglx repositories enabled.
Benji
On 6/6/06, Matthias Clasen mclasen@redhat.com wrote:
Fedora Test Update Notification FEDORA-2006-661 2006-06-06
Product : Fedora Core 5 Name : gdm Version : 2.14.4 Release : 1.fc5.2 Summary : The GNOME Display Manager. Description : Gdm (the GNOME Display Manager) is a highly configurable reimplementation of xdm, the X Display Manager. Gdm allows you to log into your system with the X Window System running and supports running several different X sessions on your local machine at the same time.
Update Information:
This update corrects a dependency.
- Tue Jun 6 2006 Matthias Clasen <mclasen@redhat.com > - 1:2.14.4-1.fc.2
- Require system-logos, not fedora-logos
- Add missing BuildRequires
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/5/
00a43e93147d507ba0baaff8fc8b85e5e7ba20a1 SRPMS/gdm-
2.14.4-1.fc5.2.src.rpm
00a43e93147d507ba0baaff8fc8b85e5e7ba20a1
noarch/gdm-2.14.4-1.fc5.2.src.rpm
7060b2daa9c92a815426bd7453a6d3276256c2ae
ppc/gdm-2.14.4-1.fc5.2.ppc.rpm
51ba6f069b6e182054e42607fb07877f0b814058 ppc/debug/gdm-
debuginfo-2.14.4-1.fc5.2.ppc.rpm
afdb1dd29769557f294f66bfe6424841b8cbecbb
x86_64/gdm-2.14.4-1.fc5.2.x86_64.rpm
c6906d499beb38a50dd089f34ceb550776c9ef33
x86_64/debug/gdm-debuginfo-2.14.4-1.fc5.2.x86_64.rpm
c5311c928b51bbc0b778f4096ccf1983b01890bc i386/debug/gdm-
debuginfo-2.14.4-1.fc5.2.i386.rpm
2d847968092a76733c8928c3a3f23ae1edecf6ad
i386/gdm-2.14.4-1.fc5.2.i386.rpm
This update can be installed with the 'yum' update program. Use 'yum
update
package-name' at the command line. For more information, refer to
'Managing
Software with yum,' available at
http://fedora.redhat.com/docs/yum/.
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On Jun 6, 2006, "Justin Conover" justin.conover@gmail.com wrote:
GDM didn't startup after the update: cat :0.log GDM: Xserver not found: /usr/X11R6/bin/X :0 -audit 0 -auth /var/gdm/:0.Xauth-nolisten tcp vt7 Error: Command could not be executed! Please install the X server or correct GDM configuration and restart GDM.
Yep, same problem as in rawhide for the past 2 days.
Even gdm-binary references the inexistent /usr/X11R6/bin/X :-(