Hide Forgot
Description of problem: During the usage of nm-connection-editor I'm getting these gtk errors: Gtk-WARNING **: No object called: wired_device_mac Gtk-WARNING **: No object called: wired_device_mac Gtk-WARNING **: No object called: wireless_device_mac Gtk-CRITICAL **: gtk_render_frame_gap: assertion `xy1_gap <= width' failed Version-Release number of selected component (if applicable): NetworkManager-gnome-0.9.2-4.fc17.x86_64 How reproducible: Steps to Reproduce: 1. start nm-connection-editor 2. switch to DSL (which is empty in my case) (xy1_gap message) 3. edit wireless connection - remaining No object.. messages Actual results: Expected results: Additional info:
Gtk-WARNING **: No object called: wired_device_mac Gtk-WARNING **: No object called: wireless_device_mac warnings has been fixed. It was incorrect handling of mnemonics. Upstream commit is 705efdda3c9ce5922972e2850a7b66b4a20fed8b "Gtk-CRITICAL **: gtk_render_frame_gap: assertion `xy1_gap <= width' failed" looks like a bug in GTK+. It could have something in common with https://bugzilla.gnome.org/show_bug.cgi?id=643041. Nonetheless, I can't reproduce that.
Created attachment 560580 [details] Rendering bug for xy1_gap Here is picture snapshot for rendering bug for message: Gtk-CRITICAL **: gtk_render_frame_gap: assertion `xy1_gap <= width' failed It happens when the nm-connection-editor window is resized to small dimensions and messages are issued on console at the moment the right border of tabbed subwindow gets smaller then right corner of DSL tab. I guess the problematic corner should be more obvious from the picture - unsure if it's bug of GUI layeout of NM or an internal GTK bug.
Bug still being reported: (nm-connection-editor:24918): Gtk-CRITICAL **: gtk_render_frame_gap: assertion `xy1_gap <= width' failed
Tested with: nm-connection-editor-0.9.4-4.git20120521.fc18.x86_64
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.