GNOME Bugzilla – Bug 158772
eggcups crashes when user loggs in to GNOME session
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: gnome-utils Severity: normal Version: GNOME2.8.0 0.17 Gnome-Distributor: Red Hat, Inc Synopsis: eggcups crashes when user loggs in to GNOME session Bugzilla-Product: gnome-utils Bugzilla-Component: gdict Bugzilla-Version: 0.17 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Don't know details. This happens every time user logs in to the Gnome session so it somehow related to the gnome startup process. The Gnome session is just plain Fedora Core 3 session, no inherited settings from older FC3 Gnome sessions in user's home directory. These started after user had use Graphics->Photo Tool from "Applications" menu. Steps to reproduce the crash: 1. 2. 3. Expected Results: Startup would go without program to crash. How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/eggcups' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151161152 (LWP 3737)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x008ec7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52240
Thread 1 (Thread -151161152 (LWP 3737))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-19 21:15 ------- Unknown version 0.17 in product gnome-utils. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-utils". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was tikkanen@iki.fi. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
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 151307 ***