Red Hat Bugzilla – Bug 134367
Warnings from system-config-samba
Last modified: 2007-11-30 17:07:13 EST
I got [root@gnu-10 rc3.d]# DISPLAY=gnu-d:0 system-config-samba /usr/share/system-config-samba/mainWindow.py:113: DeprecationWarning: use gtk.UIManager item_fac = gtk.ItemFactory(gtk.MenuBar, "<main>", accel_group) /usr/share/system-config-samba/mainWindow.py:138: DeprecationWarning: button = self.toolbar.insert_stock('gtk-add', _("Add a samba share"), None, self.onNewButtonClicked, None, 0) /usr/share/system-config-samba/mainWindow.py:143: DeprecationWarning: self.properties_button = self.toolbar.insert_stock('gtk-properties', _("Edit the properties of the selected directory"), None, self.onPropertiesButtonClicked, None, 1) /usr/share/system-config-samba/mainWindow.py:148: DeprecationWarning: self.delete_button = self.toolbar.insert_stock('gtk-delete', _("Delete the selected directory"), None, self.onDeleteButtonClicked, None, 2) /usr/share/system-config-samba/mainWindow.py:153: DeprecationWarning: self.toolbar.insert_stock('gtk-help', _("View help"), None, self.onHelpClicked, None, 3) /usr/lib/python2.3/site-packages/gtk-2.0/gtk/__init__.py:90: GtkDeprecationWarning: gtk.mainloop is deprecated, use gtk.main instead self.warn(message, DeprecationWarning)
Which version of system-config-samba do you use?
I am using system-config-samba-1.2.14-1.
system-config-samba-1.2.18-1 is currently building which contains fixes for the gtk.mainloop()/gtk.mainquit() warnings. To fix the gtk.ItemFactory and related warnings, part of the UI needs to be reimplemented to use new widgets, which breaks translation etc. I'll postpone this for after FC3 is released.
After fc2test3 mabye if all works out well.
Seeing same warnings in version 1.2.21 (RHEL4B2)
*** Bug 143678 has been marked as a duplicate of this bug. ***
Bug 143678 reopened to keep track of things RHEL4 and FC3 separately.
NEEDINFO_PM has been deprecated. Changing status to NEEDINFO and changing ownership to pm manager.
Nils, do you know if that problem still persists? Proposing for 4.5
Daniel, I'm pretty the problem still exists in RHEL4. But as backporting them would be too much of a hassle (see comment #3, i.e. IMO just rebasing to a new version would impose a similar burden on QE). Besides these warnings aren't harmful at all, it's just a cosmetical issue.
"pretty sure" even
PM NACK for RHEL6 based on Engineering feedback. The impact of this issue is too low to justify the efforts to fix it in RHEL4.
Product Management has reviewed and declined this request. You may appeal this decision by reopening this request.