FS#30809 - [python2-gobject2] trying to register gtype 'GMountMountFlags' as enum when it is of type 'GFlags'
Attached to Project:
Community Packages
Opened by John Barranco (Mr_Kartoffelsalat.) - Monday, 23 July 2012, 01:05 GMT
Last edited by Jan Alexander Steffens (heftig) - Saturday, 20 October 2012, 09:01 GMT
Opened by John Barranco (Mr_Kartoffelsalat.) - Monday, 23 July 2012, 01:05 GMT
Last edited by Jan Alexander Steffens (heftig) - Saturday, 20 October 2012, 09:01 GMT
|
Details
Description:
When starting batti the following warnings occur: WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags' WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags' WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags I'm not sure if this is also the reason why stalonetray gets broken when tarting batti. (Batteryicon occurs in xxl, ignoring stalonetrays settings) Additional info: 3.4.6-1-ARCH i686, xorg-server 1.12.3-1, Openbox 3.5.0-7, python2-dbus 1.1.1-1, hicolor-icon-theme 0.12-2, pygtk 2.24.0-3, upower 0.9.17-1, (notification-daemon 0.7.4-1) Steps to reproduce: Start batti in X from terminal emulator. |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Saturday, 20 October 2012, 09:01 GMT
Reason for closing: Duplicate
Additional comments about closing: Duplicate of FS#30083
Saturday, 20 October 2012, 09:01 GMT
Reason for closing: Duplicate
Additional comments about closing: Duplicate of
A quick web search for "WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'" shows that this is probably a glib or pyobject bug instead.
More research is needed to find out which package to pin this one to.
See: https://bugzilla.redhat.com/show_bug.cgi?id=790053
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/918607
https://launchpad.net/ubuntu/+source/pygobject-2
exo-open pkls
which opens pkls with medit
medit produces the error messages
there is a patch at http://bugzilla-attachments.gnome.org/attachment.cgi?id=209543
that has been applied at https://bugzilla.redhat.com/show_bug.cgi?id=790053
for Fedora that seem to fix the problem.
I think I have the dots connected but I don't know how to get this info to the
proper people for the Arch distro.
Please advise.