GNOME Bugzilla – Bug 159716
Bug tool initiated while doing shut down. Problem remains after boot. Desktop dissappear.
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: Bug tool initiated while doing shut down. Problem remains after boot. Desktop dissappear. Bugzilla-Product: gnome-utils Bugzilla-Component: gdict Bugzilla-Version: 0.17 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: I got this bug report tool initiated. That was the first thing I noticed that anything is wrong. Up to that point everything worked fine. That is, everything that I expect working fine. As nothing seemed to be wrong and I had no idea why bug tool initiated, I did not send the bug report. Instead I proceeded to shut down my system as I intended to. Ever since I have started up the system, desktop is epmty and several of these bug tools keep initiating. Also, some configuration tools to fix desktop does nothing but freeze. Also, log off didn't work when I tried it and I had to user power switch to get laptop booting. Before problems started I was trying to configure my printer driver oki4drv with instructions I found at http://www.linuxprinting.org/pipermail/okidata-list/2003q3/000264.html. I have printer okipage 8iM and somewhere at net it was said to use same driver as okipage 8w. As I use Fedora Core 3, I figured RedHat instructions might work. I was about to shut down to try what the changes has effect. I failed the step 8 the first time I tired it. I don't know why. I proceeded onwards. Step 12 of the instructions was the first that keeps failing. I tried instructions onwards and after my printer testing message of not finding /dev/oki4drv had changed to message no permission to /dev/oki4drv I tried step 8 again and now I managed to do that. After that test printing still failed, but I did not get any errors to the log file. I tried find-command to find it, but failed to use it and about that point I decided to restart and try if printing would work better. At doing that I got the bug report tool initiated the first time. I omited the step 15 because step 12 failed. Steps to reproduce the crash: 1. Not the faintest idea. See description above. 2. 3. Expected Results: How often does this happen? First occurance at when I tried to shut down. I made a mistake of saving settings, so I get the problem again now every time I login. 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 -151164640 (LWP 3880)] (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)...(no debugging symbols found)...0x002ff7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52792
Thread 1 (Thread -151164640 (LWP 3880))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-28 07:58 ------- 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 ithelog@hotmail.com. 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 ***