After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 458873 - crash in Gimmie: Initial launch on Ubuntu...
crash in Gimmie: Initial launch on Ubuntu...
Status: RESOLVED DUPLICATE of bug 458048
Product: gimmie
Classification: Deprecated
Component: general
0.2.x
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
: 455831 456853 464489 467122 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-07-21 04:10 UTC by Andrew Conkling
Modified: 2007-08-31 08:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Andrew Conkling 2007-07-21 04:10:40 UTC
What were you doing when the application crashed?
Initial launch on Ubuntu Gutsy, I only see four blank sections at the bottom--blue, green, pink, and gray.


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.19.5 2007-07-11 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Outdoors
Icon Theme: Tango

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0



----------- .xsession-errors ---------------------
 *** Reloading TopicRunningList: Active Conversations
 *** Reloading TopicRunningList: Computer Running Source
 *** Reloading TopicRunningList: Running Applications
 *** Reloading TopicRunningList: Opened Documents
 *** Reloading TopicRunningList: Active Conversations
 *** Reloading TopicRunningList: Computer Running Source
 *** Reloading TopicRunningList: Computer Running Source
 *** Reloading TopicRunningList: Computer Running Source
 *** Reloading TopicRunningList: Running Applications
 *** Reloading TopicRunningList: Opened Documents
 *** Reloading TopicRunningList: Active Conversations
 *** ReloadiGimmie Version: 0.2.7
TypeError: <lambda>() takes exactly 1 argument (2 given)
--------------------------------------------------
Gimmie Version: 0.2.7

TypeError: <lambda>() takes exactly 1 argument (2 given)
Comment 1 Andrew Conkling 2007-07-21 04:13:41 UTC
Sorry, here's the crash with debug symbols installed:

Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.19.5 2007-07-11 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Outdoors
Icon Theme: Tango

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0



----------- .xsession-errors ---------------------
(bug-buddy:14137): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:14137): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
ng TopicRunningList: Computer Running Source
 *** Reloading TopicRunningList: Running Applications
 *** Reloading TopicRunningList: Opened Documents
 *** Reloading TopicRunningList: Active Conversations
 *** Reloading TopicRunningList: Computer Running Source
***MEMORY-WARNING***: gimmie[14253]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program
Gimmie Version: 0.2.7
TypeError: <lambda>() takes exactly 1 argument (2 given)
--------------------------------------------------
Gimmie Version: 0.2.7

TypeError: <lambda>() takes exactly 1 argument (2 given)
Comment 2 Benedikt Henrichs 2007-08-22 22:24:40 UTC
*** Bug 455831 has been marked as a duplicate of this bug. ***
Comment 3 Benedikt Henrichs 2007-08-22 22:25:03 UTC
*** Bug 456853 has been marked as a duplicate of this bug. ***
Comment 4 Benedikt Henrichs 2007-08-22 22:25:34 UTC
*** Bug 464489 has been marked as a duplicate of this bug. ***
Comment 5 Benedikt Henrichs 2007-08-22 22:43:52 UTC
*** Bug 467122 has been marked as a duplicate of this bug. ***
Comment 6 Benedikt Henrichs 2007-08-31 08:23:43 UTC
This bug actually is a dupe itself. Sorry for the confusion...

If you have time to do so it would also be great, if you could test Jesse Hallet's patch for this issue attached to the original bug.


*** This bug has been marked as a duplicate of 458048 ***