gnome-zeitgeist team mailing list archive
-
gnome-zeitgeist team
-
Mailing list archive
-
Message #00409
[Bug 513930] Re: Crashes on startup
Committed, thanks!
------------------------------------------------------------
revno: 534 [merge]
author: Abderrahim Kitouni <a.kitouni@xxxxxxxxx>
committer: Siegfried-Angel Gevatter Pujals <rainct@xxxxxxxxxx>
branch nick: gnome-activity-journal
timestamp: Thu 2010-01-28 20:24:36 +0100
message:
Use get_screen() instead of instantiating gtk.gdk.Screen.
------------------------------------------------------------
** Changed in: gnome-activity-journal
Importance: Undecided => Medium
** Changed in: gnome-activity-journal
Status: New => Fix Released
** Changed in: gnome-activity-journal
Milestone: None => 0.3.3
** Changed in: gnome-activity-journal
Assignee: (unassigned) => Abderrahim Kitouni (a-kitouni)
--
Crashes on startup
https://bugs.launchpad.net/bugs/513930
You received this bug notification because you are a member of GNOME
Zeitgeist Team, which is the registrant for GNOME Activity Journal.
Status in GNOME Activity Journal: Fix Released
Bug description:
On startup, g-a-j crashes with an assertion error in gdk. The problem is that GdkScreen is being instantiated and used (which seems crazy to me, I wonder why it isn't crashing for everybody). The following snippet crashes almost every time I run it.
import gtk
screen = gtk.gdk.Screen()
screen.get_monitor_geometry(0)
Attached is a patch to fix this (using bzr bundle, it's the closest thing I found to hg export, should I use something else?)
References