[Bug 1524000] Re: PyGIWarning: UbuntuAppLaunch was imported without specifying a version first

** Changed in: autopilot Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1524000 Title: PyGIWarning: UbuntuAppLaunch was imported

[Bug 1524000] Re: PyGIWarning: UbuntuAppLaunch was imported without specifying a version first

** Changed in: autopilot Assignee: (unassigned) => Christopher Lee (veebers) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1524000 Title: PyGIWarning: UbuntuAppLau

[Bug 1333512] Re: Failing to import module breaks logging configurability and adds noise

Hi Adam, sorry for the delay. Installing python3-gi (and python3-gi-cairo) version 3.12.0-1ubuntu1 fixed the issue for me. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 1343069] [NEW] Order of imports and method calls alters API

Public bug reported: Using the python gi.repository (gir1.2-gtk-3.0) if I import Gdk make a specific method call and then import GdkX11 the API for GdkX11 is different than if I had imported both before the method call. To reproduce: Run the script found here (details in comments):

[Bug 1339506] [NEW] In Utopic importing Gdk with no XDG_* env vars causes segfault

Public bug reported: When using the gi.repository bindings on Utopic a segfault occurs if an expected environment variable isn't set. On Utopic machines we have a debian/rules build step fail due to a segfault that happens when the expected environment variables are not available. In Trusty

[Bug 1333512] Re: Failing to import module adds noise to the logging stream

** Description changed: - When there is a failure to import a module this failure is logged but - also means that everything else will be logged to stdout from that point - on. + When failing to import a module the gi.repository import.py module logs an error with `logging.error(..)` causing a

[Bug 1333512] [NEW] Failing to import module adds noise to the logging stream

Public bug reported: When there is a failure to import a module this failure is logged but also means that everything else will be logged to stdout from that point on. To reproduce/test: Run the python script found here: http://pastebin.ubuntu.com/7693393/ Expected output: Nothing. No logging

[Bug 1333512] Re: Failing to import module adds noise to the logging stream

** Description changed: When there is a failure to import a module this failure is logged but also means that everything else will be logged to stdout from that point on. + + The Issue: + When failing to import a module the gi.repository import module adds a handler, that sends output

[Bug 1055906] [NEW] Two entries for Launch Terminal in keyboard shotcuts

Public bug reported: After a recent dist-upgrade (running 12.10 Quantal) I was unable to open a terminal using Ctrl-Alt-t I checked the settings and saw that there are 2 entries for Launch Terminal (please see attached screenshot). I initially only saw the first and attempted to reset it by

[Bug 1055906] Re: Two entries for Launch Terminal in keyboard shotcuts

** Attachment added: Screenshot https://bugs.launchpad.net/bugs/1055906/+attachment/3340080/+files/DoubleTerminal_screenshot.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.