GNOME Bugzilla – Bug 338979
Deskbar in drawer crashes if drawer hasn't been opened yet
Last modified: 2007-04-05 15:36:02 UTC
Steps to reproduce: 1. Place deskbar in a gnome-panel-drawer 2. Reboot 3. Press keyboard shortcut without opening the drawer first Stack trace: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/deskbar/ui/cuemiac/CuemiacAlignedWindow.py", line 29, in <lambda> self.connect ("realize", lambda win : self.__register_realize ()) File "/usr/lib/python2.4/site-packages/deskbar/ui/cuemiac/CuemiacAlignedWindow.py", line 116, in __register_realize self.update_position() File "/usr/lib/python2.4/site-packages/deskbar/ui/cuemiac/CuemiacAlignedWindow.py", line 50, in update_position (ax, ay) = self.widgetToAlignWith.window.get_origin () AttributeError: 'NoneType' object has no attribute 'get_origin' Other information:
+ Trace 67718
I think we need to realize the widgetToAlignTo before trying to align the window. This can be done by calling show() on the widgetToAlignTo in the AlignedWindow.py constructor. Marking as gnome-love since patching should be easy
Removing gnome-love :-) I fear I think this might actually be trickier than you suspect Raph. Showing the window prematurely will lead to visual jumpiness of the window... Maybe, just *maybe*, calling realize() on the widget will do, but this is just a guess - if I recall correctly this has some issues - I might be wrong though.
Strike the "I fear" after the above smilie.
Mikkel have you any ideas on this?
Mikkel: *ping* Raphael, please only use NEEDINFO state if you need additional information submitted by the bug reporter. use ASSIGNED state for developers. thanks a lot and have fun in stockholm, it's a nice city! ;-)
I can't reproduce this with 2.16... Can anyone reproduce? (Andre I hope it is Ok to mark "Needinfo" now...)
mikkel: heh, sure :-)
I just ran across this problem on Ubuntu Edgy (6.10), which uses Gnome 2.16.1. I'll try to see if I can reproduce it again.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 336855 ***
*** Bug 425061 has been marked as a duplicate of this bug. ***
*** Bug 424999 has been marked as a duplicate of this bug. ***