hello, uname -p returns a string at least on x86 platforms and you get a [: too many arguments. --- config/Init.in.orig 2008-10-15 17:33:12.000000000 +0200 +++ config/Init.in 2008-10-15 17:33:41.000000000 +0200 @@ -47,7 +47,7 @@ UNAME=`gdmwhich uname` PROCESSOR=`$UNAME -p` - if [ x$PROCESSOR = xsparc ]; then + if [ x"$PROCESSOR" = xsparc ]; then if $XMODMAP | /usr/bin/grep mod4 | /usr/bin/grep Alt > /dev/null 2>/dev/null then $XMODMAP -e "clear Mod1" \ Also, still present in gdm 2.24.0 package. Reproducible: Always
did you report this upstream ?
(In reply to comment #1) > did you report this upstream ? > No, I didn't.
(In reply to comment #0) > uname -p returns a string at least on x86 platforms and you get a > [: too many arguments. <snip> > - if [ x$PROCESSOR = xsparc ]; then > + if [ x"$PROCESSOR" = xsparc ]; then <snip> Yes, and if it's not exactly equal to "sparc", then it's not supposed to be true anyway :-) This isn't a "bug" per-se but it's definitely a potential bug. PS: I noticed this myself a while ago and came to the conclusion that it wasn't worth reporting ;p
(In reply to comment #3) > PS: I noticed this myself a while ago and came to the conclusion that it wasn't > worth reporting ;p > I have reported it for aesthetic matter :)
(In reply to comment #4) > I have reported it for aesthetic matter :) to gentoo bugzilla of course. We don't want a beach spoiled with tar do we ?
aesthetic is good for upstream, we just care about the damn thing working :) Anyway, I'll forward this upstream and fix it as time permits in portage. > We don't want a beach spoiled with tar do we ? I don't understand this part.
*** Bug 243464 has been marked as a duplicate of this bug. ***
afaik, this problem is only present in gdm 2.24, please report this upstream.
I have sent it to upstream: http://bugzilla.gnome.org/show_bug.cgi?id=563550 Patch was generated for trunk, but can be easily adapted to 2.24 branch Affected people, please check if something is wrong on it as I am still using gdm-2.20 under amd64 and x86 arches and cannot reproduce Thanks
This has been already fixed by upstream in trunk and gdm-2.20.9, I am unsure about 2.24 :-/
2.20.9 is in tree.
gdm-2.26 should be fixed in overlay. Thanks for reporting.