Mailinglist Archive: opensuse-testing (54 mails)
| < Previous | Next > |
[opensuse-testing] RC2 upgrade caused more bugs: Gnome/YaST2 bug
- From: "Terje J. Hanssen" <terje@xxxxxxxxxxxxxxxxxxx>
- Date: Sun, 27 Feb 2011 11:29:57 +0100
- Message-id: <4D6A27A5.6000903@nordland-teknikk.no>
Hi list,
1)
Previous 'zypper dup' from 11.4 M6 x86_64/Gnome to RC1 caused a GLib-GIO:ERROR on my machine. This bug is reported but it still arise in RC2 as follows:
~> su
Password:
# /sbin/yast2 sw_single
**
GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed: (connection->initialization_error == NULL)
YaST got signal 6 at YCP file Wizard.ycp:707
/sbin/yast2: line 423: 30328 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
# exit
~>
2) Now neither clicking YaST2 modules on the control-center started from the menu does work - that is nothing happends - the surrounding pointer dies out. Starting YaST2 control-center with the same command in a Gnome terminal, reports that a MIT-MAGIC-COOKIE issue is the reason:
~> /usr/bin/xdg-su -c /sbin/yast2
** (y2controlcenter-gnome:30236): WARNING **: key not found [/apps/yast-control-center/cc_actions_list]
Invalid MIT-MAGIC-COOKIE-1 keyCannot open display:
Invalid MIT-MAGIC-COOKIE-1 keyCannot open display:
^C
~>
3) Entering 'su -' to root makes it is possible to start individual yast2 modules directly.
~> su -
Password:
# /sbin/yast2 sw_single
#
But starting the YaST2 control-center first this way and from there click on the YaST2 modules causes the following error messages:
# /sbin/yast2
** (y2controlcenter-gnome:30512): WARNING **: tast ikke funnet [/apps/yast-control-center/cc_actions_list]
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkWidget::cursor-color' of type `GdkColor' from rc file value "((GString*) 0x90da20)" of type `GString'
Invalid MIT-MAGIC-COOKIE-1 keyxprop: unable to open display ':0.0'
Invalid MIT-MAGIC-COOKIE-1 keyWarning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm Xt error: Can't open display: %s
#
4)
Starting another application 'gedit' works, but also reports the corresponding Gtk-message:
~> su -
Password:
# gedit
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkWidget::cursor-color' of type `GdkColor' from rc file value "((GString*) 0xa24560)" of type `GString'
#
This is on a hp8710w/Intel/Nvidia machine with upgrade history since M4. On another machine, Asus/AMD/ATI with a shorter upgrade history since M6, it is possible to start YaST modules from Gnome/YaST2 control-center, but also here the Gtk-error message popup in a box.
Can someone confirm this behaviour, possible other experiences using Gnome/GDM?
Thanks,
Terje J. Hanssen
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-testing+help@xxxxxxxxxxxx
1)
Previous 'zypper dup' from 11.4 M6 x86_64/Gnome to RC1 caused a GLib-GIO:ERROR on my machine. This bug is reported but it still arise in RC2 as follows:
~> su
Password:
# /sbin/yast2 sw_single
**
GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed: (connection->initialization_error == NULL)
YaST got signal 6 at YCP file Wizard.ycp:707
/sbin/yast2: line 423: 30328 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
# exit
~>
2) Now neither clicking YaST2 modules on the control-center started from the menu does work - that is nothing happends - the surrounding pointer dies out. Starting YaST2 control-center with the same command in a Gnome terminal, reports that a MIT-MAGIC-COOKIE issue is the reason:
~> /usr/bin/xdg-su -c /sbin/yast2
** (y2controlcenter-gnome:30236): WARNING **: key not found [/apps/yast-control-center/cc_actions_list]
Invalid MIT-MAGIC-COOKIE-1 keyCannot open display:
Invalid MIT-MAGIC-COOKIE-1 keyCannot open display:
^C
~>
3) Entering 'su -' to root makes it is possible to start individual yast2 modules directly.
~> su -
Password:
# /sbin/yast2 sw_single
#
But starting the YaST2 control-center first this way and from there click on the YaST2 modules causes the following error messages:
# /sbin/yast2
** (y2controlcenter-gnome:30512): WARNING **: tast ikke funnet [/apps/yast-control-center/cc_actions_list]
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkWidget::cursor-color' of type `GdkColor' from rc file value "((GString*) 0x90da20)" of type `GString'
Invalid MIT-MAGIC-COOKIE-1 keyxprop: unable to open display ':0.0'
Invalid MIT-MAGIC-COOKIE-1 keyWarning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm Xt error: Can't open display: %s
#
4)
Starting another application 'gedit' works, but also reports the corresponding Gtk-message:
~> su -
Password:
# gedit
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkWidget::cursor-color' of type `GdkColor' from rc file value "((GString*) 0xa24560)" of type `GString'
#
This is on a hp8710w/Intel/Nvidia machine with upgrade history since M4. On another machine, Asus/AMD/ATI with a shorter upgrade history since M6, it is possible to start YaST modules from Gnome/YaST2 control-center, but also here the Gtk-error message popup in a box.
Can someone confirm this behaviour, possible other experiences using Gnome/GDM?
Thanks,
Terje J. Hanssen
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-testing+help@xxxxxxxxxxxx
| < Previous | Next > |