GNOME Bugzilla – Bug 330892
config/Xession.in: failsafe session information text unreadable.
Last modified: 2006-02-13 18:49:34 UTC
Please describe the problem: The failsafe Xsession shows a small zenity dialog, containing only the word "This". Steps to reproduce: run ${sysconfdir}/etc/gdm/Xsession failsafe, for example under Xnest. Actual results: Failsafe session comes up, but the information dialog (telling a user how to QUIT the session) is unreadable. Expected results: the complete text in the dialog. Does this happen every time? yes. Other information: A patch to prevent the problem (it adds one level of quoting): -------------- --- config/Xsession.in.orig Tue Jul 19 09:53:41 2005 +++ config/Xsession.in Sun Feb 12 13:34:34 2006 @@ -79,7 +79,7 @@ if [ x"$command" = xfailsafe ] ; then if [ -n "$zenity" ] ; then - "$zenity" --info --text `gettextfunc "This is the failsafe xterm session. Windows now have focus only if you have your cursor above them. To get out of this mode type 'exit' in the window in the upper left corner"` + "$zenity" --info --text "`gettextfunc "This is the failsafe xterm session. Windows now have focus only if you have your cursor above them. To get out of this mode type 'exit' in the window in the upper left corner"`" else echo "$0: Starting the failsafe xterm session." fi @@ -239,7 +239,7 @@ echo "$0: Executing $command failed, will run xterm" if [ -n "$zenity" ] ; then - "$zenity" --info --text `gettextfunc "Failed to start the session, so starting a failsafe xterm session. Windows will have focus only if the mouse pointer is above them. To get out of this mode type 'exit' in the window in the upper left corner"` + "$zenity" --info --text "`gettextfunc "Failed to start the session, so starting a failsafe xterm session. Windows will have focus only if the mouse pointer is above them. To get out of this mode type 'exit' in the window in the upper left corner"`" fi exec xterm -geometry 80x24+0+0
Thanks for the report. I see this problem too. Your proposed fix didn't work on Solaris, so I fixed the problem by first setting a variable with the gettextfunc output and passing that into zenity, which makes the script a little easier to read I think and works on Solaris too. This should fix the problem.