Bug#600927: gdm3: mouse cursor remains a 'clock'
Miklos Quartus
Version: 2.30.5-6
Severity: minor
Hi
I experience the same problem after a clean install of Debian Squeeze
from "squeeze-di-beta2" i386 CD. Cursor remains a 'clock' in the login
screen even after login-logout. I have no metacity. Otherwise no impact
on overall behaviour of the system.
FYI, in /var/log/gdm3/:0-greeter.log gnome-session complains about not
being able to launch metacity as below:
"
gnome-session[1832]: WARNING: Could not launch application
'metacity.desktop': Unable to start application: Failed to execute child
process "metacity" (No such file or directory) .
"
My X.Org core version is 2:1.7.7-10 (xserver-xorg-core) and 1:7.5+8
(xserver-xorg). Kernel version is 2.6.32-5-686, libc6 version is
2.11.2-7 . Perl version is 5.10.1. My X Window Manager is xfce4, version 4.6.2 .
At this moment I have no suggestion for a fix.
Thank you for your help and support.
Regards
--
Miklos Quartus
Linux/FreeBSD System Administrator
Josselin Mouette
> I experience the same problem after a clean install of Debian Squeeze
> from "squeeze-di-beta2" i386 CD. Cursor remains a 'clock' in the login
> screen even after login-logout. I have no metacity. Otherwise no impact
> on overall behaviour of the system.
Does removing the “X-GNOME-Autostart-Notify=true” line
in /usr/share/gdm/autostart/LoginWindow/metacity.desktop help?
In all cases I don’t think it’s a good idea to have gdm3 without
metacity. Maybe it should be made a dependency.
Cheers,
--
.''`.
: :' : “You would need to ask a lawyer if you don't know
`. `' that a handshake of course makes a valid contract.”
`- -- J???rg Schilling
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Emilio Pozuelo Monfort
> Le mardi 21 décembre 2010 à 19:58 +0100, Miklos Quartus a écrit :
>> I experience the same problem after a clean install of Debian Squeeze
>> from "squeeze-di-beta2" i386 CD. Cursor remains a 'clock' in the login
>> screen even after login-logout. I have no metacity. Otherwise no impact
>> on overall behaviour of the system.
>
> Does removing the “X-GNOME-Autostart-Notify=true” line
> in /usr/share/gdm/autostart/LoginWindow/metacity.desktop help?
>
> In all cases I don’t think it’s a good idea to have gdm3 without
> metacity. Maybe it should be made a dependency.
Not sure why, but at least with a mutter alternative I guess? I'm using
gnome-shell now, though I still have metacity installed, so I'm not sure whether
gdm would keep working if I removed it.
Cheers,
Emilio
Miklos Quartus
> Does removing the “X-GNOME-Autostart-Notify=true” line
> in /usr/share/gdm/autostart/LoginWindow/metacity.desktop help?
> In all cases I don’t think it’s a good idea to have gdm3 without
> metacity. Maybe it should be made a dependency.
Yes, perhaps.
Installing the 'metacity' package and restarting gdm3 service has
solved the problem. I guess we should go for requesting to update the
dependencies for the gdm3 package in order to fix and close this bug.
Currently 'metacity' is a suggestion only:
"
[qmi@szonja: ~]$ apt-cache depends gdm3
(...)
Suggests: libpam-gnome-keyring
Suggests: metacity
^^^^^^^^^^^^^^^^^^
Suggests: gnome-mag
Suggests: gnome-orca
(...)
Josselin Mouette
écrit :
> > In all cases I don’t think it’s a good idea to have gdm3 without
> > metacity. Maybe it should be made a dependency.
>
> Not sure why, but at least with a mutter alternative I guess? I'm using
> gnome-shell now, though I still have metacity installed, so I'm not sure whether
> gdm would keep working if I removed it.
That would require setting defaults for mutter as well, which means
doing this through GSettings → not until we have gdm 3.0, I’d say.
--
.''`. Josselin Mouette
: :' :
`. `' “If you behave this way because you are blackmailed by someone,
`- […] I will see what I can do for you.” -- Jörg Schilling