[Bug 524497] Re: Positioning of login screen 'panel' inconsistent with desktop's
Are there any reasons not to move the panel to the top in GDM? The consistency with the desktop could be increased even more by making the panel (as well as the login pane) dark, since this is the default setting for the desktop (Ambiance). This is of less importance than the position, though. I for one absolutely agree with Jani's reasoning. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/524497 Title: Positioning of login screen 'panel' inconsistent with desktop's -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 612383] Re: 'use_action_appearance' property changes location when saving file
Marking the bug as fixed as the ordering of properties in UI files seems to be permanent in Natty. ** Changed in: glade-3 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. https://bugs.launchpad.net/bugs/612383 Title: 'use_action_appearance' property changes location when saving file -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 612383] Re: 'use_action_appearance' property changes location when saving file
A bug fix seems to have been committed upstream, but it isn't present in the Maverick package as the bug can still be reproduced. I'll update the report as soon as I'll be testing Natty. ** Bug watch added: GNOME Bug Tracker #628253 https://bugzilla.gnome.org/show_bug.cgi?id=628253 ** Changed in: glade-3 Importance: Medium => Unknown ** Changed in: glade-3 Remote watch: GNOME Bug Tracker #626328 => GNOME Bug Tracker #628253 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. https://bugs.launchpad.net/bugs/612383 Title: 'use_action_appearance' property changes location when saving file -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 279579] Re: MRO error crash when accessing the 'focus_widget' property of a file selection dialog
Closing the bug report as it cannot be reproduced anymore in Maverick. This probably applies to some of the previous releases as well. Besides, LottaNZB has dropped support for Intrepid long ago. ** Changed in: pygtk (Ubuntu) Status: Triaged => Invalid ** Changed in: pygtk (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in ubuntu. https://bugs.launchpad.net/bugs/279579 Title: MRO error crash when accessing the 'focus_widget' property of a file selection dialog -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 701875] Re: rhythmbox assert failure: *** glibc detected *** rhythmbox: munmap_chunk(): invalid pointer: 0x00007f1d04ae4b1f ***
Unfortunately, the crash doesn't occur when running Rhythmbox using Valgrind. It does when launching it with GDB, but the resulting information has already been added to the bug report and is thus not particularly useful. Marking the bug as 'Incomplete'. ** Changed in: rhythmbox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. https://bugs.launchpad.net/bugs/701875 Title: rhythmbox assert failure: *** glibc detected *** rhythmbox: munmap_chunk(): invalid pointer: 0x7f1d04ae4b1f *** -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 701875] Re: rhythmbox assert failure: *** glibc detected *** rhythmbox: munmap_chunk(): invalid pointer: 0x00007f1d04ae4b1f ***
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. https://bugs.launchpad.net/bugs/701875 Title: rhythmbox assert failure: *** glibc detected *** rhythmbox: munmap_chunk(): invalid pointer: 0x7f1d04ae4b1f *** -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 612374] Re: 'translatable' property of GtkAction labels lost when saving
The bug has been forwarded upstream. -- 'translatable' property of GtkAction labels lost when saving https://bugs.launchpad.net/bugs/612374 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 612383] Re: 'use_action_appearance' property changes location when saving file
The bug has been forwarded upstream. -- 'use_action_appearance' property changes location when saving file https://bugs.launchpad.net/bugs/612383 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 614814] Re: Impossible to override action appearance
The bug has been reported upstream. ** Bug watch added: GNOME Bug Tracker #626332 https://bugzilla.gnome.org/show_bug.cgi?id=626332 ** Also affects: glade-3 via https://bugzilla.gnome.org/show_bug.cgi?id=626332 Importance: Unknown Status: Unknown -- Impossible to override action appearance https://bugs.launchpad.net/bugs/614814 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 612374] Re: 'translatable' property of GtkAction labels lost when saving
** Bug watch added: GNOME Bug Tracker #626330 https://bugzilla.gnome.org/show_bug.cgi?id=626330 ** Also affects: glade-3 via https://bugzilla.gnome.org/show_bug.cgi?id=626330 Importance: Unknown Status: Unknown -- 'translatable' property of GtkAction labels lost when saving https://bugs.launchpad.net/bugs/612374 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 612383] Re: 'use_action_appearance' property changes location when saving file
** Bug watch added: GNOME Bug Tracker #626328 https://bugzilla.gnome.org/show_bug.cgi?id=626328 ** Also affects: glade-3 via https://bugzilla.gnome.org/show_bug.cgi?id=626328 Importance: Unknown Status: Unknown -- 'use_action_appearance' property changes location when saving file https://bugs.launchpad.net/bugs/612383 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 614814] Re: Impossible to override action appearance
** Attachment added: "demo.py" http://launchpadlibrarian.net/53244382/demo.py ** Description changed: Binary package hint: glade-3 When saving a glade file that contains a button or a menu item based on an action but overriding its appearance, the following line will, erroneously, *not* be part of the file: False But unless this line is added to such a button or menu item, the default action appearance will be used by GtkBuilder. Manually adding the line is possible, but it will be discarded again when the file is loaded and saved the next time using glade. + + ProblemType: Bug + DistroRelease: Ubuntu 10.04 + Package: glade 3.7.0.is.3.6.7-0ubuntu1 + ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 + Uname: Linux 2.6.32-24-generic x86_64 + Architecture: amd64 + InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) + ProcEnviron: + LANGUAGE=en + PATH=(custom, user) + LANG=de_CH.utf8 + SHELL=/bin/bash + SourcePackage: glade-3 -- Impossible to override action appearance https://bugs.launchpad.net/bugs/614814 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 614814] Re: Impossible to override action appearance
In the following demo, the button will have the label "The label of the GtkAction", unless "False" is added manually to demo.ui. This very line will be lost when loading and saving demo.ui using glade the next time. ** Attachment added: "demo.ui" http://launchpadlibrarian.net/53244373/demo.ui -- Impossible to override action appearance https://bugs.launchpad.net/bugs/614814 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 614814] [NEW] Impossible to override action appearance
Public bug reported: Binary package hint: glade-3 When saving a glade file that contains a button or a menu item based on an action but overriding its appearance, the following line will, erroneously, *not* be part of the file: False But unless this line is added to such a button or menu item, the default action appearance will be used by GtkBuilder. Manually adding the line is possible, but it will be discarded again when the file is loaded and saved the next time using glade. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: glade 3.7.0.is.3.6.7-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 Architecture: amd64 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: LANGUAGE=en PATH=(custom, user) LANG=de_CH.utf8 SHELL=/bin/bash SourcePackage: glade-3 ** Affects: glade-3 (Ubuntu) Importance: Undecided Status: New -- Impossible to override action appearance https://bugs.launchpad.net/bugs/614814 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 612383] Re: 'use_action_appearance' property changes location when saving file
** Attachment added: "demo.ui" http://launchpadlibrarian.net/52841817/demo.ui ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/52841644/Dependencies.txt ** Description changed: Binary package hint: glade-3 - After applying changes to a GtkBuilder UI file, 'use_action_appearance' - properties (or 'related_action', respectively) reproducibly change their - position in the list of properties of widgets related to a GtkAction. - This is annoying because it clutters diffs and makes the actual changes - harder to spot. + When saving a GtkBuilder UI file, 'use_action_appearance' properties (or + 'related_action', respectively) reproducibly change their position in + the list of properties of widgets related to a GtkAction. This is + annoying because it clutters diffs and makes the actual changes harder + to spot. A file for the purpose of demonstration is attached. Take the following steps to reproduce it: 1. Open demo.ui in a text editor and notice that 'use_action_appearance' is located in the line above 'related_action'. 2. Open demo.ui using glade, select the widget 'test_button' by clicking on it, and save the file. 3. Open demo.ui in a text editor and notice that 'use_action_appearance' is located in the line *below* 'related_action'. 4. Open demo.ui using glade, select the widget 'test_button' by clicking on it, and save the file. 5. Go back to step 1. If anyone can confirm this bug, I'd be happy to report it upstream. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: glade 3.7.0.is.3.6.7-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 Architecture: amd64 Date: Mon Aug 2 01:37:57 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: - LANGUAGE=en - PATH=(custom, user) - LANG=de_CH.utf8 - SHELL=/bin/bash + LANGUAGE=en + PATH=(custom, user) + LANG=de_CH.utf8 + SHELL=/bin/bash SourcePackage: glade-3 -- 'use_action_appearance' property changes location when saving file https://bugs.launchpad.net/bugs/612383 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 612383] [NEW] 'use_action_appearance' property changes location when saving file
Public bug reported: Binary package hint: glade-3 When saving a GtkBuilder UI file, 'use_action_appearance' properties (or 'related_action', respectively) reproducibly change their position in the list of properties of widgets related to a GtkAction. This is annoying because it clutters diffs and makes the actual changes harder to spot. A file for the purpose of demonstration is attached. Take the following steps to reproduce it: 1. Open demo.ui in a text editor and notice that 'use_action_appearance' is located in the line above 'related_action'. 2. Open demo.ui using glade, select the widget 'test_button' by clicking on it, and save the file. 3. Open demo.ui in a text editor and notice that 'use_action_appearance' is located in the line *below* 'related_action'. 4. Open demo.ui using glade, select the widget 'test_button' by clicking on it, and save the file. 5. Go back to step 1. If anyone can confirm this bug, I'd be happy to report it upstream. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: glade 3.7.0.is.3.6.7-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 Architecture: amd64 Date: Mon Aug 2 01:37:57 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: LANGUAGE=en PATH=(custom, user) LANG=de_CH.utf8 SHELL=/bin/bash SourcePackage: glade-3 ** Affects: glade-3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- 'use_action_appearance' property changes location when saving file https://bugs.launchpad.net/bugs/612383 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 612374] Re: 'translatable' property of GtkAction labels lost when saving
** Attachment added: "demo.ui" http://launchpadlibrarian.net/52839509/demo.ui ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/52839369/Dependencies.txt -- 'translatable' property of GtkAction labels lost when saving https://bugs.launchpad.net/bugs/612374 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 612374] [NEW] 'translatable' property of GtkAction labels lost when saving
Public bug reported: Binary package hint: glade-3 When using objects of type GtkAction in a GtkBuilder file, the attribute 'translatable' of 'label' properties is reproducibly lost when saving the file using glade. This is extremely annoying as those attributes need to be restored manually in a text editor after having made a change to the file using glade. If this isn't done, the labels won't be recognized by gettext anymore. A file is attached for demonstration purposes. As far as I know, the version in Maverick is also affected. If anyone can confirm this bug, it should be forwarded upstream. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: glade 3.7.0.is.3.6.7-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 Architecture: amd64 Date: Mon Aug 2 00:12:47 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: LANGUAGE=en PATH=(custom, user) LANG=de_CH.utf8 SHELL=/bin/bash SourcePackage: glade-3 ** Affects: glade-3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- 'translatable' property of GtkAction labels lost when saving https://bugs.launchpad.net/bugs/612374 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507739] Re: Widget names not set when using GtkBuilder
** Changed in: lottanzb (Ubuntu Lucid) Importance: Undecided => Medium ** Changed in: lottanzb (Ubuntu Lucid) Status: New => Fix Released ** Changed in: lottanzb (Ubuntu Lucid) Assignee: (unassigned) => Severin Heiniger (lantash) -- Widget names not set when using GtkBuilder https://bugs.launchpad.net/bugs/507739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 537958] Re: genre tab displays numbers in magnatune catalogue instead of genre names
I can confirm this bug on Lucid with the latest version of rhythmbox (0.12.7-0ubuntu7) installed. @kristoffer: The problem is not related to the locale used of your system, as it can also be reproduced when launching rhythmbox in English using "LANGUAGE=C rhythmbox". ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Confirmed -- genre tab displays numbers in magnatune catalogue instead of genre names https://bugs.launchpad.net/bugs/537958 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507739] Re: Widget names not set when using GtkBuilder
** Changed in: lottanzb (Ubuntu) Status: Triaged => Fix Released -- Widget names not set when using GtkBuilder https://bugs.launchpad.net/bugs/507739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 521886] Re: lottanzb crashed with AttributeError in _autoconnect_by_method_name()
*** This bug is a duplicate of bug 507739 *** https://bugs.launchpad.net/bugs/507739 This bug has been fixed in LottaNZB 0.5.3. Unfortunately, the package hasn't arrived in Ubuntu 10.04 yet. For the time being, you can install the package provided at http://www.lottanzb.org/downloads/ubuntu/. -- lottanzb crashed with AttributeError in _autoconnect_by_method_name() https://bugs.launchpad.net/bugs/521886 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu (via bug 507739). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507739] Re: Widget names not set when using GtkBuilder
** Changed in: lottanzb Status: Fix Committed => Fix Released -- Widget names not set when using GtkBuilder https://bugs.launchpad.net/bugs/507739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507739] Re: Widget names not set when using GtkBuilder
** Changed in: lottanzb (Ubuntu) Status: Invalid => Won't Fix ** Changed in: lottanzb (Ubuntu) Status: Won't Fix => Triaged ** Changed in: lottanzb (Ubuntu) Importance: Undecided => Medium ** Changed in: lottanzb (Ubuntu) Assignee: (unassigned) => Severin Heiniger (lantash) -- Widget names not set when using GtkBuilder https://bugs.launchpad.net/bugs/507739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515257] Re: lottanzb crashed with AttributeError in _autoconnect_by_method_name()
*** This bug is a duplicate of bug 507739 *** https://bugs.launchpad.net/bugs/507739 There's an error in the commands mentioned above. If you're interested in running LottaNZB on Ubuntu 10.04 at this point of time, you should enter: bzr branch lp:lottanzb/0.5 cd 0.5 ./run-lottanzb.sh ** Description changed: Binary package hint: lottanzb Upgraded stable 9.10 to daily load of 10.04 and LottaNZB crashes. ProblemType: Crash Architecture: i386 Date: Sun Jan 31 16:02:04 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/lottanzb InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2) InterpreterPath: /usr/bin/python2.6 Package: lottanzb 0.5.2-1 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/lottanzb /home/username/Downloads/02\ Firefox\ Downloads/NCIS.S01E02.WS.AC3.DVDRip.XviD-RiVER.nzb ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-12.16-generic - PythonArgs: ['/usr/bin/lottanzb', '/home/username/Downloads/02 Firefox Downloads/NCIS.S01E02.WS.AC3.DVDRip.XviD-RiVER.nzb'] + PythonArgs: ['/usr/bin/lottanzb'] RelatedPackageVersions: - lottanzb 0.5.2-1 - hellanzb 0.13-5.4 + lottanzb 0.5.2-1 + hellanzb 0.13-5.4 SourcePackage: lottanzb Title: lottanzb crashed with AttributeError in _autoconnect_by_method_name() Uname: Linux 2.6.32-12-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare log: - 2010-01-31 16:02:17 lottanzb.util DEBUGPrevious lock detected: - 2010-01-31 16:02:17 lottanzb.core ERRORLottaNZB is already running on this computer. + 2010-01-31 16:02:17 lottanzb.util DEBUGPrevious lock detected: + 2010-01-31 16:02:17 lottanzb.core ERRORLottaNZB is already running on this computer. ** Description changed: Binary package hint: lottanzb Upgraded stable 9.10 to daily load of 10.04 and LottaNZB crashes. ProblemType: Crash Architecture: i386 Date: Sun Jan 31 16:02:04 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/lottanzb InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2) InterpreterPath: /usr/bin/python2.6 Package: lottanzb 0.5.2-1 PackageArchitecture: all - ProcCmdline: /usr/bin/python /usr/bin/lottanzb /home/username/Downloads/02\ Firefox\ Downloads/NCIS.S01E02.WS.AC3.DVDRip.XviD-RiVER.nzb + ProcCmdline: /usr/bin/python /usr/bin/lottanzb ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-12.16-generic PythonArgs: ['/usr/bin/lottanzb'] RelatedPackageVersions: lottanzb 0.5.2-1 hellanzb 0.13-5.4 SourcePackage: lottanzb Title: lottanzb crashed with AttributeError in _autoconnect_by_method_name() Uname: Linux 2.6.32-12-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare log: 2010-01-31 16:02:17 lottanzb.util DEBUGPrevious lock detected: 2010-01-31 16:02:17 lottanzb.core ERRORLottaNZB is already running on this computer. -- lottanzb crashed with AttributeError in _autoconnect_by_method_name() https://bugs.launchpad.net/bugs/515257 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu (via bug 507739). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 512961] Re: lottanzb crashed with AttributeError in _autoconnect_by_method_name()
*** This bug is a duplicate of bug 507739 *** https://bugs.launchpad.net/bugs/507739 You're welcome. I'm not the only LottaNZB developer, but apparently the one with the least number of hobbies beside LottaNZB. :-P -- lottanzb crashed with AttributeError in _autoconnect_by_method_name() https://bugs.launchpad.net/bugs/512961 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu (via bug 507739). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 512961] Re: lottanzb crashed with AttributeError in _autoconnect_by_method_name()
*** This bug is a duplicate of bug 507739 *** https://bugs.launchpad.net/bugs/507739 There's no need to close the ticket as the bug has already been marked as a duplicate. Thanks for giving the latest code a try! It's good to hear that it works for you. -- lottanzb crashed with AttributeError in _autoconnect_by_method_name() https://bugs.launchpad.net/bugs/512961 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu (via bug 507739). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 510907] Re: Inhibit suspending (flag 0x4) not working over DBus
I can confirm that the patch works perfectly. Great work! Is there any chance that this change will be uploaded to Ubuntu Karmic as a SRU? The fact that the LottaNZB "Inhibit suspending" plug-in will only work on Ubuntu 9.04 and 10.04 renders it useless for many people at this point of time. -- Inhibit suspending (flag 0x4) not working over DBus https://bugs.launchpad.net/bugs/510907 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 510907] Re: Inhibit suspending (flag 0x4) not working over DBus
Thanks alot for taking care of this, Chris! I'll give the patch a try tomorrow. -- Inhibit suspending (flag 0x4) not working over DBus https://bugs.launchpad.net/bugs/510907 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 510907] Re: Inhibit suspending (flag 0x4) not working over DBus
Reported upstream. ** Bug watch added: GNOME Bug Tracker #607748 https://bugzilla.gnome.org/show_bug.cgi?id=607748 ** Also affects: gnome-power via https://bugzilla.gnome.org/show_bug.cgi?id=607748 Importance: Unknown Status: Unknown -- Inhibit suspending (flag 0x4) not working over DBus https://bugs.launchpad.net/bugs/510907 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 510907] Re: Inhibit suspending (flag 0x4) not working over DBus
After having a look at gnome-power-manager's source code, I also noticed that gpm_manager_is_inhibit_valid is a stub. Implementing it also requires gpm-session.c to be changed, because the term "inhibited" is limited to the concept of session timeouts there. I tried to implement it but unfortunately, it didn't work. I guess this bug should be forwarded upstream, unless this has already happened. -- Inhibit suspending (flag 0x4) not working over DBus https://bugs.launchpad.net/bugs/510907 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 510907] Re: Inhibit suspending (flag 0x4) not working over DBus
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/38200394/Dependencies.txt -- Inhibit suspending (flag 0x4) not working over DBus https://bugs.launchpad.net/bugs/510907 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 510907] [NEW] Inhibit suspending (flag 0x4) not working over DBus
Public bug reported: Binary package hint: gnome-session While porting the "Inhibit suspending" LottaNZB plug-in (written in Python) from the old org.freedesktop.PowerManagement.Inhibit API to the new org.gnome.SessionManager API introduced in Karmic, I noticed that after successfully passing the 0x4 flag to the Inhibit DBus method [1], the computer will still be suspended after the session has timed out and the amount of time stored in /apps/gnome-power- manager/timeout/sleep_computer_ac has passed after that. First I thought that I didn't properly use the new API, but I noticed that Transmission (that also passes 0x4 to the very same Inhibit method) doesn't actually prevent the computer from being suspended either, which means that it's neither LottaNZB's nor Transmission's fault. Passing 0x4 | 0x8 to the Inhibit method works as intended, because the 0x8 flag prevents the session from timing out and thus the computer will not be suspended. However, I'd rather not use 0x4 | 0x8 because an active download operation is not negatively affected by a timed out session, but only by the computer being suspended. I really hope that someone can confirm this problem and know how to tackle it. [1] http://www.gnome.org/~mccann/gnome-session/docs/gnome- session.html#org.gnome.SessionManager.Inhibit ProblemType: Bug Architecture: amd64 Date: Thu Jan 21 23:01:43 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113) Package: gnome-session 2.28.0-0ubuntu8 PackageArchitecture: all ProcEnviron: LANG=de_CH.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-11.15-generic SourcePackage: gnome-session Uname: Linux 2.6.32-11-generic x86_64 ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Inhibit suspending (flag 0x4) not working over DBus https://bugs.launchpad.net/bugs/510907 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507739] Re: Widget names not set when using GtkBuilder
** Changed in: lottanzb Status: In Progress => Fix Committed -- Widget names not set when using GtkBuilder https://bugs.launchpad.net/bugs/507739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507739] Re: Widget names not set when using GtkBuilder
The bug has been marked as a duplicate upstream. The problem is that the "name" property is only meant to be used w.r.t. themes and doesn't need to be unique. The GtkBuilder ID however needs to be unique and was bound to the "name" property until now. This means that the problem can be fixed within LottaNZB using a rather ugly hack by getting the GtkBuilder ID using gtk.Buildable.get_name(widget). Let's hope that the GTK/PyGTK API's will be updated regarding this issue by adding methods/functions like "get_id" or "get_buildable_id". ** Changed in: lottanzb Status: Invalid => Triaged ** Changed in: lottanzb Status: Triaged => In Progress ** Changed in: lottanzb Assignee: (unassigned) => Severin Heiniger (lantash) ** Changed in: lottanzb Importance: Undecided => Critical ** Changed in: lottanzb Milestone: None => 0.5.3 -- Widget names not set when using GtkBuilder https://bugs.launchpad.net/bugs/507739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507739] Re: Widget names not set when using GtkBuilder
** Changed in: gtk+2.0 (Ubuntu) Status: New => Invalid ** Changed in: pygtk (Ubuntu) Status: New => Invalid -- Widget names not set when using GtkBuilder https://bugs.launchpad.net/bugs/507739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507739] Re: Widget names not set when using GtkBuilder
The bug has been reported upstream. ** Bug watch added: GNOME Bug Tracker #607221 https://bugzilla.gnome.org/show_bug.cgi?id=607221 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=607221 Importance: Unknown Status: Unknown -- Widget names not set when using GtkBuilder https://bugs.launchpad.net/bugs/507739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507739] Re: Widget names not set when using gtk.Builder
C test-case. Compile it using gcc testcase.c -Wall -o testcase `pkg-config --cflags --libs gtk+-2.0` and make sure that 'testcase.ui' is in the same directory as 'testcase' when executing it. ** Attachment added: "testcase.c" http://launchpadlibrarian.net/38001124/testcase.c ** Also affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: LottaNZB cannot be launched on an up-to-date Lucid machine because of a - bug in PyGTK (or something more low-level). I tracked down the problem: + bug in GtkBuilder. I tracked down the problem: - When loading a XML UI file using gtk.Builder, the 'name' property of - widgets isn't set. Because of this, get_name() just returns a string - containing the widget type (like GtkWindow). On the other hand, the - 'name' property of 'gtk.Action' objects is properly set. + When loading a XML UI file using GtkBuilder, the 'name' property of + widgets isn't set. On the other hand, the 'name' property of + 'gtk.Action' objects is properly set. - A test case is attached. Compare the output on a Karmic and a Lucid - machine. + A test case written in both Python and C is attached. Compare the output + on a Karmic and a Lucid machine. I'm pretty sure that LottaNZB worked about a week ago, when I initially installed Lucid. This means that the bug could have been introduced in a - recent update of the pygtk package. + recent update. ** Summary changed: - Widget names not set when using gtk.Builder + Widget names not set when using GtkBuilder ** Description changed: LottaNZB cannot be launched on an up-to-date Lucid machine because of a bug in GtkBuilder. I tracked down the problem: When loading a XML UI file using GtkBuilder, the 'name' property of - widgets isn't set. On the other hand, the 'name' property of - 'gtk.Action' objects is properly set. + widgets isn't set. On the other hand, the 'name' property of 'GtkAction' + objects is properly set. A test case written in both Python and C is attached. Compare the output on a Karmic and a Lucid machine. I'm pretty sure that LottaNZB worked about a week ago, when I initially installed Lucid. This means that the bug could have been introduced in a recent update. ** Changed in: lottanzb Status: New => Invalid ** Changed in: lottanzb (Ubuntu) Status: New => Invalid -- Widget names not set when using GtkBuilder https://bugs.launchpad.net/bugs/507739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507739] Re: Widget names not set when using gtk.Builder
I just ported the Python testcase to raw C code. The bug can also be reproduced here. Everything is fine in Karmic, but in Lucid, the widget names are not set. This means that it's not actually a bug in PyGTK, but GTK itself. -- Widget names not set when using GtkBuilder https://bugs.launchpad.net/bugs/507739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507739] Re: Widget names not set when using gtk.Builder
I'd be glad if someone confirmed the bug so that it could be forwarded upstream. ** Also affects: pygtk (Ubuntu) Importance: Undecided Status: New -- Widget names not set when using gtk.Builder https://bugs.launchpad.net/bugs/507739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 204567] Re: downloads should go to $HOME/Downloads : XDG_DOWNLOAD_DIR should be set to "$HOME/Downloads"
Well, looks like I should have read the comments at brainstorm.ubuntu.com. Are there any Ubuntu deverlopers (preferably usability experts ;-)) who could say a word or two about this issue? -- downloads should go to $HOME/Downloads : XDG_DOWNLOAD_DIR should be set to "$HOME/Downloads" https://bugs.launchpad.net/bugs/204567 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 204567] Re: downloads should go to $HOME/Downloads : XDG_DOWNLOAD_DIR should be set to "$HOME/Downloads"
I know that "me-too" comments are not particularly useful, but I think it's time to make this rather trivial change. Are there any valid reasons that this hasn't been done in previous release cycles? -- downloads should go to $HOME/Downloads : XDG_DOWNLOAD_DIR should be set to "$HOME/Downloads" https://bugs.launchpad.net/bugs/204567 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334784] Re: Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
This bug has somehow been fixed. As I mentioned above, LottaNZB works just fine using Python 2.6. ** Changed in: lottanzb Status: New => Invalid ** Changed in: pygobject (Ubuntu) Status: Incomplete => Invalid -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334784] Re: Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
According to a message by Matthias Klose in ubuntu-devel, the Python interpreter will be updated from 2.5.4 to 2.6 within the next days and numerous packages will be rebuilt for that purpose. Since the bug only affects Python 2.5 I assume that everything will be fine after the transition. I'll problably make a clean install a couple of days after Alpha 5. -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334784] Re: Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
Sorry for bothering you once more. I'm not quite sure what to think about it. In addition to the ubuntu1, I built the ubuntu2 pacakge by myself a few minutes ago, and now it looks as if the application segfaults if either the self-built ubuntu1 package (why did this work before?!) or the official ubuntu2 package is used. Running the application using my own ubuntu2 build works fine. I just commited a "fix" described above for this problem to the LottaNZB development branch, so that at least this application can be started again on Jaunty. If noone can reproduce this bug using the demo files one might consider marking this bug as invalid or incomplete for the moment. -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334784] Re: Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
lant...@gauss:~/Desktop$ python demo.py # Using 2.16.1-0ubuntu2. Segmentation fault (core dumped) lant...@gauss:~/Desktop$ sudo dpkg --install --force-all python-gobject_2.16.1-0ubuntu1_amd64.deb [...] Vorbereiten zum Ersetzen von python-gobject 2.16.1-0ubuntu2 (durch python-gobject_2.16.1-0ubuntu1_amd64.deb) ... [...] lant...@gauss:~/Desktop$ python demo.py lant...@gauss:~/Desktop$ sudo apt-get upgrade [...] Vorbereiten zum Ersetzen von python-gobject 2.16.1-0ubuntu1 (durch .../python-gobject_2.16.1-0ubuntu2_amd64.deb) ... [...] lant...@gauss:~/Desktop$ python demo.py Segmentation fault (core dumped) -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334784] Re: Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
@Matthias: I've downloaded the required files from https://edge.launchpad.net/ubuntu/jaunty/+source/pygobject/2.16.1-0ubuntu1, built it using dpkg-source -x and installed the package using dpkg --install --force-all (which replaced the ubuntu2 version). Everything was fine after this. Upgrading back to ubuntu2 using apt-get upgrade reintroduced the bug. -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334784] Re: Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
The most interesting thing about it is that the order of the three import statements in demo.py has an effect on what happens: # Finally leads to the segfault described in this bug report. from kiwi.environ import Application from gobject import property, GObject from demo_util import GObjectSingletonMeta # Everything works fine from gobject import property, GObject from kiwi.environ import Application from demo_util import GObjectSingletonMeta # Raises # Exception exceptions.TypeError: 'could not get typecode from object' in ignored from gobject import property, GObject from demo_util import GObjectSingletonMeta from kiwi.environ import Application Can anyone confirm this behaviour? -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334784] Re: Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
...and the demo_util.py file. ** Attachment added: "demo_util.py" http://launchpadlibrarian.net/23146823/demo_util.py -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334784] Re: Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
Forgot to remove unnecessary stuff from the demo.py file. Download this one and not the one above. ** Attachment added: "demo.py" http://launchpadlibrarian.net/23146820/demo.py -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334784] Re: Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
I seem to have found a solution. Right now, the GObjectSingletonMeta metaclass is part of the util module. Moving it to the core module where it is actually used by the App class solved the problem. This is totally weird. I was able to create a simple script that demonstrates the problem. demo.py and demo_util.py. Install the python-kiwi package (!). Run demo.py using Python 2.5 and the latest python-gobject package (2.16.1-0ubuntu2). Make sure that the demo_util.py file is in the same directory. ** Attachment added: "demo.py" http://launchpadlibrarian.net/23146745/demo.py -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334784] Re: Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
Changelog of python-gobject_2.16.1-0ubuntu2: https://edge.launchpad.net/ubuntu/jaunty/+source/pygobject/2.16.1-0ubuntu2 * Remove explicit dependencies on python2.5. * Rename -dbg extensions for python2.6 as well. LP: #333557. ** Also affects: lottanzb Importance: Undecided Status: New -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334784] [NEW] Segfault starting with 2.16.1-0ubuntu2 using Python 2.5
Public bug reported: A few days ago, the development version of the PyGTK application LottaNZB 0.5 (https://code.edge.launchpad.net/~lottanzb/lottanzb/main) stopped working because of a segmentation fault during startup. I was able to track down the problem: 2.16.1-0ubuntu1: Works fine both using Python 2.5 and Python 2.6. 2.16.1-0ubuntu2 when launching the application using Python 2.5: Segmentation fault. 2.16.1-0ubuntu2 when launching the application using Python 2.6: Works fine. I wasn't able to produce a simple demonstration of the Python 2.5 problem yet, but in our code the situation is as follows: class GObjectSingletonMeta(GObjectMeta): """GObject singleton metaclass""" def __init__(mcs, name, bases, _dict): # THIS IS WHERE THE APPLICATION SEGFAULTS. GObjectMeta.__init__(mcs, name, bases, _dict) mcs.__instance = None def __call__(mcs, *args, **kwargs): """Creates an instance of mcs if it doesn't exist yet""" if mcs.__instance is None: mcs.__instance = GObjectMeta.__call__(mcs, *args, **kwargs) return mcs.__instance class App(GObject, kiwi.environ.Application): __metaclass__ = GObjectSingletonMeta lock = property(type=object) [...] It's possible to prevent the application from segfaulting in the singleton metaclass by *either* removing the Application parent class from the App class or by removing all GObject properties from the App class. I'm using an up-to-date Jaunty amd64 machine. I only exchanged the python-gobject package for the tests. I'll try to provide further information about the problem and I wonder if someone else can reproduce this. You can try to reproduce the problem by branching the project and running ./run-lottanzb.sh (which will run the application using Python 2.5 by default). ** Affects: lottanzb Importance: Undecided Status: New ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 279579] Re: MRO error crash when accessing the 'focus_widget' property of a file selection dialog
Filed upstream: http://bugzilla.gnome.org/show_bug.cgi?id=555384 -- MRO error crash when accessing the 'focus_widget' property of a file selection dialog https://bugs.launchpad.net/bugs/279579 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 279579] Re: MRO error crash when accessing the 'focus_widget' property of a file selection dialog
** Attachment added: "filechooser.glade" http://launchpadlibrarian.net/18289267/filechooser.glade -- MRO error crash when accessing the 'focus_widget' property of a file selection dialog https://bugs.launchpad.net/bugs/279579 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 279579] Re: MRO error crash when accessing the 'focus_widget' property of a file selection dialog
** Attachment added: "test_pygtk_crash.py" http://launchpadlibrarian.net/18289262/test_pygtk_crash.py ** Description changed: As a developer of LottaNZB (a PyGTK app), I recently gave our application a try on Ubuntu Intrepid, with the latest updates applied. The application unexpectedly crashed when opening the file selection dialog with the following error message: TypeError: Cannot create a consistent method resolution order (MRO) for bases ImplementorIface, CellEditable, Editable, Buildable ** ERROR:/build/buildd/pygobject-2.15.3/gobject/pygobject.c:920:pygobject_new_full: assertion failed: (tp != NULL) Aborted (core dumped) Trying to locate the problem, I dove into the code of Kiwi, the PyGTK framework we use in our application. I finally found the line of code which caused this issue. To my surprise it wasn't a Kiwi-specific problem, as I was able to reproduce it with pure PyGTK code. This crash happens whenever the developer tries to access the property 'focus_widget' of a gtk.FileChooserDialog or a dialog that contains a gtk.FileChooserWidget after the dialog's show() method was invoked. This issue can only be reproduced using Intrepid, but not using Hardy, that's why I assume that certain changes in python-gtk or python-gobject since Hardy cause the error. The only way to prevent the application from crashing is to ensure that this property isn't accessed (when using Kiwi by overwriting the check_focus method). I strongly hope that this bug can be ironed out before the Intrepid release. - Test cases are attached. + Test case is attached. -- MRO error crash when accessing the 'focus_widget' property of a file selection dialog https://bugs.launchpad.net/bugs/279579 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 279579] [NEW] MRO error crash when accessing the 'focus_widget' property of a file selection dialog
Public bug reported: As a developer of LottaNZB (a PyGTK app), I recently gave our application a try on Ubuntu Intrepid, with the latest updates applied. The application unexpectedly crashed when opening the file selection dialog with the following error message: TypeError: Cannot create a consistent method resolution order (MRO) for bases ImplementorIface, CellEditable, Editable, Buildable ** ERROR:/build/buildd/pygobject-2.15.3/gobject/pygobject.c:920:pygobject_new_full: assertion failed: (tp != NULL) Aborted (core dumped) Trying to locate the problem, I dove into the code of Kiwi, the PyGTK framework we use in our application. I finally found the line of code which caused this issue. To my surprise it wasn't a Kiwi-specific problem, as I was able to reproduce it with pure PyGTK code. This crash happens whenever the developer tries to access the property 'focus_widget' of a gtk.FileChooserDialog or a dialog that contains a gtk.FileChooserWidget after the dialog's show() method was invoked. This issue can only be reproduced using Intrepid, but not using Hardy, that's why I assume that certain changes in python-gtk or python-gobject since Hardy cause the error. The only way to prevent the application from crashing is to ensure that this property isn't accessed (when using Kiwi by overwriting the check_focus method). I strongly hope that this bug can be ironed out before the Intrepid release. Test case is attached. ** Affects: pygtk (Ubuntu) Importance: Undecided Status: New -- MRO error crash when accessing the 'focus_widget' property of a file selection dialog https://bugs.launchpad.net/bugs/279579 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 273673] Re: evince crashed with SIGSEGV in Form::findWidgetByRef()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/17888604/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/17888605/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/17888606/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/17888607/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/17888608/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/17888609/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/17888610/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/17888611/ThreadStacktrace.txt ** Visibility changed to: Public ** Description changed: Binary package hint: evince Evince crashes when I try to open the following document: http://www.aloaha.com/cache/incstickynotes.pdf (a link at http://ubuntuforums.org/showthread.php?t=153976 points to it). The document isn't displayed at all and after having minimized and maximized the empty window for a few times, the application crashes. This is a reproducible bug. - - Using up-to-date x86 Intrepid. Evince 2.24.0-0ubuntu1. ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/evince Package: evince 2.24.0-0ubuntu1 ProcAttrCurrent: unconfined ProcCmdline: evince file:///tmp/incstickynotes.pdf ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin LANG=de_CH.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: evince StacktraceTop: Form::findWidgetByRef () from /usr/lib/libpoppler.so.3 AnnotWidget::initialize () from /usr/lib/libpoppler.so.3 AnnotWidget::AnnotWidget () from /usr/lib/libpoppler.so.3 Annots::createAnnot () from /usr/lib/libpoppler.so.3 Annots::Annots () from /usr/lib/libpoppler.so.3 Title: evince crashed with SIGSEGV in Form::findWidgetByRef() Uname: Linux 2.6.27-4-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video -- evince crashed with SIGSEGV in Form::findWidgetByRef() https://bugs.launchpad.net/bugs/273673 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 187766] Re: gedit crashed with SIGSEGV in g_datalist_id_set_data_full()
This annoying bug in gvfs seems to be fixed now. Many thanks to the developers who have been working on it. -- gedit crashed with SIGSEGV in g_datalist_id_set_data_full() https://bugs.launchpad.net/bugs/187766 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 24630] Re: Evince crashes when zooming PDF-File to 400%
** Description changed: Evince starts with wild swapping and finally crashed on my machine when Zooming the attached PDF-File to 400%. - http://bugzilla.gnome.org/show_bug.cgi?id=321138: http://bugzilla.gnome.org/show_bug.cgi?id=321138 -- Evince crashes when zooming PDF-File to 400% https://bugs.launchpad.net/bugs/24630 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 189992] Re: evince does not display pdf files
** Description changed: Binary package hint: evince - Evince does not seems to load normally, but can not display pdf file - pages. Display space is blank. + Evince seems to load normally, but can not display pdf file pages. + Display space is blank. ProblemType: Bug Architecture: i386 Date: Thu Feb 7 10:33:01 2008 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/evince NonfreeKernelModules: vmvirtualnic vm_bridge vm_main hypervisor Package: evince 2.20.1-0ubuntu1 PackageArchitecture: i386 ProcCmdline: evince file:///home/pmd/Desktop/Parallels_Workstation_Getting_Started_Guide_for_Linux.pdf ProcCwd: /home/pmd ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince Uname: Linux hayek 2.6.22-14-generic #1 SMP Fri Feb 1 04:59:50 UTC 2008 i686 GNU/Linux -- evince does not display pdf files https://bugs.launchpad.net/bugs/189992 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 189998] Re: "Separate keyboard layout for each window" in GNOME doesn't keep working after reboot
I can confirm that this bug must have been introduced in a recent update in Hardy. The keyboard layout settings behave quite strange at the moment. The keyboard layout is resetted to the standard US layout after every reboot although the layout manager still displays "Switzerland". To fix this issue, I keep reconfiguring this after every reboot. It's quite annoying in fact. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- "Separate keyboard layout for each window" in GNOME doesn't keep working after reboot https://bugs.launchpad.net/bugs/189998 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
