- Previous thread: [Cooker] Cooker on Virtual Box hangs
- Next thread: [Cooker] fglrx and X.org 7.5 (fglrx-8.712.3.1)?
- Threads sorted by date: mandriva 201003
Hi all,
I'm pushing "new" gdm (ie 2.29.92) in cooker. This new gdm should allow
better integration with plymouth (not enabled yet) and is almost
complete rewrite from the old gdm. Unfortunately, this rewrite doesn't
yet have all the features from the old gdm 2.20 (like multiseat,
configuration UI, themes support, etc..) so old GDM will be available in
contrib as gdm-220 package.
I haven't finished UI customizations in new GDM and I haven't imported
Canonical gdmsetup in the package either.
--
Frederic Crozat
Mandriva
I'm pushing "new" gdm (ie 2.29.92) in cooker. This new gdm should allow
better integration with plymouth (not enabled yet) and is almost
complete rewrite from the old gdm. Unfortunately, this rewrite doesn't
yet have all the features from the old gdm 2.20 (like multiseat,
configuration UI, themes support, etc..) so old GDM will be available in
contrib as gdm-220 package.
I haven't finished UI customizations in new GDM and I haven't imported
Canonical gdmsetup in the package either.
--
Frederic Crozat
Mandriva
2010/3/26 Frederic Crozat :
> I'm pushing "new" gdm (ie 2.29.92) in cooker. This new gdm should allow
> better integration with plymouth (not enabled yet) and is almost complete
> rewrite from the old gdm. Unfortunately, this rewrite doesn't yet have all
> the features from the old gdm 2.20 (like multiseat, configuration UI, themes
> support, etc..) so old GDM will be available in contrib as gdm-220 package.
>
> I haven't finished UI customizations in new GDM and I haven't imported
> Canonical gdmsetup in the package either.
are we going to have a migration path for the configuration files ?
Does drakedm will allow to choose between GDM 2.20 and GDM 2.29 ?
For example "GDM legacy" ( aka 2.20 ) and GDM ( aka 2.29 )
--
Close the World, Open the Net
http://www.linux-wizard.net
> I'm pushing "new" gdm (ie 2.29.92) in cooker. This new gdm should allow
> better integration with plymouth (not enabled yet) and is almost complete
> rewrite from the old gdm. Unfortunately, this rewrite doesn't yet have all
> the features from the old gdm 2.20 (like multiseat, configuration UI, themes
> support, etc..) so old GDM will be available in contrib as gdm-220 package.
>
> I haven't finished UI customizations in new GDM and I haven't imported
> Canonical gdmsetup in the package either.
are we going to have a migration path for the configuration files ?
Does drakedm will allow to choose between GDM 2.20 and GDM 2.29 ?
For example "GDM legacy" ( aka 2.20 ) and GDM ( aka 2.29 )
--
Close the World, Open the Net
http://www.linux-wizard.net
Le 26/03/2010 12:40, Fabrice Facorat a écrit :
> 2010/3/26 Frederic Crozat:
>
>> I'm pushing "new" gdm (ie 2.29.92) in cooker. This new gdm should allow
>> better integration with plymouth (not enabled yet) and is almost complete
>> rewrite from the old gdm. Unfortunately, this rewrite doesn't yet have all
>> the features from the old gdm 2.20 (like multiseat, configuration UI, themes
>> support, etc..) so old GDM will be available in contrib as gdm-220 package.
>>
>> I haven't finished UI customizations in new GDM and I haven't imported
>> Canonical gdmsetup in the package either.
>
> are we going to have a migration path for the configuration files ?
Features which are still supported are handled by new gdm without need
to migrate configuration.
> Does drakedm will allow to choose between GDM 2.20 and GDM 2.29 ?
> For example "GDM legacy" ( aka 2.20 ) and GDM ( aka 2.29 )
No and I don't think it is worth it.
--
Frederic Crozat
Mandriva
> 2010/3/26 Frederic Crozat:
>
>> I'm pushing "new" gdm (ie 2.29.92) in cooker. This new gdm should allow
>> better integration with plymouth (not enabled yet) and is almost complete
>> rewrite from the old gdm. Unfortunately, this rewrite doesn't yet have all
>> the features from the old gdm 2.20 (like multiseat, configuration UI, themes
>> support, etc..) so old GDM will be available in contrib as gdm-220 package.
>>
>> I haven't finished UI customizations in new GDM and I haven't imported
>> Canonical gdmsetup in the package either.
>
> are we going to have a migration path for the configuration files ?
Features which are still supported are handled by new gdm without need
to migrate configuration.
> Does drakedm will allow to choose between GDM 2.20 and GDM 2.29 ?
> For example "GDM legacy" ( aka 2.20 ) and GDM ( aka 2.29 )
No and I don't think it is worth it.
--
Frederic Crozat
Mandriva
Frederic Crozat wrote:
>> I'm pushing "new" gdm (ie 2.29.92) in cooker.
Do you want bug reports for this yet ?
I've noticed two odd things so far:
1) For users whose desktops were previously set to GNOME, the first
login through the new GDM brings up KDE. All subsequent logins for that
user bring up GNOME.
2) When you logout, you return to the GDM screen at once. If you try to
login again, to the same userid or a different one, you get a popup
saying that an application is still running (the popup names "Power
Manager") and do I want to logout anyway ? If I choose Logout Anyway,
the login proceeds normally.
>> I'm pushing "new" gdm (ie 2.29.92) in cooker.
Do you want bug reports for this yet ?
I've noticed two odd things so far:
1) For users whose desktops were previously set to GNOME, the first
login through the new GDM brings up KDE. All subsequent logins for that
user bring up GNOME.
2) When you logout, you return to the GDM screen at once. If you try to
login again, to the same userid or a different one, you get a popup
saying that an application is still running (the popup names "Power
Manager") and do I want to logout anyway ? If I choose Logout Anyway,
the login proceeds normally.
Le 26/03/2010 14:55, Frank Griffin a écrit :
> Frederic Crozat wrote:
>>> I'm pushing "new" gdm (ie 2.29.92) in cooker.
> Do you want bug reports for this yet ?
Yes please.
> I've noticed two odd things so far:
>
> 1) For users whose desktops were previously set to GNOME, the first
> login through the new GDM brings up KDE. All subsequent logins for that
> user bring up GNOME.
I guess the migration between the old user settings and new one isn't
done properly.
> 2) When you logout, you return to the GDM screen at once. If you try to
> login again, to the same userid or a different one, you get a popup
> saying that an application is still running (the popup names "Power
> Manager") and do I want to logout anyway ? If I choose Logout Anyway,
> the login proceeds normally.
I think this one is an upstream bug, I'll double check.
--
Frederic Crozat
Mandriva
> Frederic Crozat wrote:
>>> I'm pushing "new" gdm (ie 2.29.92) in cooker.
> Do you want bug reports for this yet ?
Yes please.
> I've noticed two odd things so far:
>
> 1) For users whose desktops were previously set to GNOME, the first
> login through the new GDM brings up KDE. All subsequent logins for that
> user bring up GNOME.
I guess the migration between the old user settings and new one isn't
done properly.
> 2) When you logout, you return to the GDM screen at once. If you try to
> login again, to the same userid or a different one, you get a popup
> saying that an application is still running (the popup names "Power
> Manager") and do I want to logout anyway ? If I choose Logout Anyway,
> the login proceeds normally.
I think this one is an upstream bug, I'll double check.
--
Frederic Crozat
Mandriva
Dnia 2010-03-26, o godz. 11:54:45
Frederic Crozat napisa=C5=82(a):
> Hi all,
>=20
> I'm pushing "new" gdm (ie 2.29.92) in cooker. This new gdm should
> allow better integration with plymouth (not enabled yet) and is
> almost complete rewrite from the old gdm. Unfortunately, this rewrite
> doesn't yet have all the features from the old gdm 2.20 (like
> multiseat, configuration UI, themes support, etc..) so old GDM will
> be available in contrib as gdm-220 package.
>=20
> I haven't finished UI customizations in new GDM and I haven't
> imported Canonical gdmsetup in the package either.
Looks like gdm doesn't work at all with xfce4.
This is all i got in logs:
gdm-simple-slave[26728]: WARNING: Could not start command
'/usr/bin/gnome-session
--autostart=3D/usr/share/gdm/autostart/LoginWindow/': Wykonanie procesu
potomnego "/usr/bin/gnome-session" (Nie ma takiego pliku ani katalogu)
si=C4=99 nie powiod=C5=82o
Does this new gdm is that simple, so it tries to execute a hardcoded
gdm-session?
--=20
Regards
TPG
http://cia.vc/stats/author/tpg
---
Frederic Crozat napisa=C5=82(a):
> Hi all,
>=20
> I'm pushing "new" gdm (ie 2.29.92) in cooker. This new gdm should
> allow better integration with plymouth (not enabled yet) and is
> almost complete rewrite from the old gdm. Unfortunately, this rewrite
> doesn't yet have all the features from the old gdm 2.20 (like
> multiseat, configuration UI, themes support, etc..) so old GDM will
> be available in contrib as gdm-220 package.
>=20
> I haven't finished UI customizations in new GDM and I haven't
> imported Canonical gdmsetup in the package either.
Looks like gdm doesn't work at all with xfce4.
This is all i got in logs:
gdm-simple-slave[26728]: WARNING: Could not start command
'/usr/bin/gnome-session
--autostart=3D/usr/share/gdm/autostart/LoginWindow/': Wykonanie procesu
potomnego "/usr/bin/gnome-session" (Nie ma takiego pliku ani katalogu)
si=C4=99 nie powiod=C5=82o
Does this new gdm is that simple, so it tries to execute a hardcoded
gdm-session?
--=20
Regards
TPG
http://cia.vc/stats/author/tpg
---
2010/3/26 Tomasz Pawe=C5=82 Gajc :
> Dnia 2010-03-26, o godz. 11:54:45
> Frederic Crozat napisa=C5=82(a):
> gdm-simple-slave[26728]: WARNING: Could not start command
> '/usr/bin/gnome-session
> --autostart=3D/usr/share/gdm/autostart/LoginWindow/': Wykonanie procesu
> potomnego "/usr/bin/gnome-session" (Nie ma takiego pliku ani katalogu)
> si=C4=99 nie powiod=C5=82o
>
> Does this new gdm is that simple, so it tries to execute a hardcoded
> gdm-session?
https://qa.mandriva.com/show_bug.cgi?id=3D58443
--=20
Close the World, Open the Net
http://www.linux-wizard.net
> Dnia 2010-03-26, o godz. 11:54:45
> Frederic Crozat napisa=C5=82(a):
> gdm-simple-slave[26728]: WARNING: Could not start command
> '/usr/bin/gnome-session
> --autostart=3D/usr/share/gdm/autostart/LoginWindow/': Wykonanie procesu
> potomnego "/usr/bin/gnome-session" (Nie ma takiego pliku ani katalogu)
> si=C4=99 nie powiod=C5=82o
>
> Does this new gdm is that simple, so it tries to execute a hardcoded
> gdm-session?
https://qa.mandriva.com/show_bug.cgi?id=3D58443
--=20
Close the World, Open the Net
http://www.linux-wizard.net
Related Threads
- [HACKERS] SPI nesting in plperl - pgsql
- [pretty-ipa, PATCH, commited] New FIXME comment in get_ref_base_and_extent() - gcc
- Re: USB printer problem [SOLVED] - freebsd
- How to know no. of times the script has been executed? - perl
- [PHP-DEV] generator/yield operator feature request - php
- setting up bootable copy of server on my home PC - freebsd
- [ruby-core:21371] Google Group Archive Cut Off ? - ruby
- [wwwdocs] Remove linux.ihep.su mirror - gcc
- INDEX build failed for 6.x - freebsd
- difference in file.join between Linux, win32? - ruby