abrt 1.0.0 detected a crash. How to reproduce ----- 1. Start Yumex 2. Remove Firefox (as described below) 3. Install Firefox alternatives (as described below) Comment ----- I was using YUMEX to remove the FIREFOX-3.5.5 that was automatically installed with Fedora 12 (because it uses 100% (sometimes more) of the CPU and is unusable); and at the same time alternative browsers were being installed. For example Epiphany (and devel, extensions), Galeon, Midori, Seamonkey, Rekonq, WebShell, arora, elinks, Links, Sufraw. Dependencies were also being installed, for example: clucene-core, constantine-backgrounds-kde, constatine-kde-theme, kde-filesystem, kde-settings, kdebase-runtime, kdebase-runtime-libs, kdebase-workspace, kdebase-workspace-libs, kdelibs, kdelibs-common, kdelibs-experimental, kdepimilibs NOTE: The Automatic Bug Reporting Tool first tried to download about 70 missing symbol tables/data and failed. It then suggested I manually install: debuginfo-install metacity First I tried sudo yum install debuginfo* then sudo debuginfo-install * and both reported no debuginfo packages available * I thought to install all the debug symbols so whatever was needed would be available in the future. After following the instructions: sudo debuginfo-install metacity more than 30 symbol tables were still "absent." For example: Debuginfo absent: 0afdfc236fadadc174323855991e9afa63360400 Maybe that means something to you folks, but it doesn't tell me what is missing, nor how to provide what is missing so that ... in the future, everything needed (to debug) is available. ALSO: This is the second time I installed and "updated" Fedora 12. The first time ssh was hogging 100% (or more of the CPU) -- making the computer useless. So I reinstalled Fedora 11 and everything was fine (well, there were errors on startup and 60% of the time it wouldn't shut off unless I pressed the power button. So I reinstalled Fedora 12. Now, I get 4 errors (actually 2-errors are duplicated for the second cpu) when i start up. One (duplicated) error is the same F11 startup error: ACPI: Invalid PBLK length [8] OTHER: metacity[1639]: segfault at 30 ip 00000000004485d6 sp 00007fff2413ff00 error 4 in metacity[400000+86000] ACPI: Fujitsu FUJ02E3 [FEXT] (on) fujitsu-laptop: BTNI: [0x30f0101] fujitsu-laptop: driver 0.5.0 successfully loaded. apanel: Fujitsu BIOS signature 'FJKEYINF' not found... mmc0: Unknown controller version (2). You may experience problems. [drm:intel_dp_i2c_init] *ERROR* i2c_init DPDDC-B [drm:intel_dp_i2c_init] *ERROR* i2c_init DPDDC-D [drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own Attached file: backtrace cmdline: metacity component: metacity executable: /usr/bin/metacity kernel: 2.6.31.6-166.fc12.x86_64 package: metacity-2.28.0-11.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 378314 [details] File: backtrace
I'm sorry that you ran into these difficulties. The Metacity backtrace attached here is a duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=546509 (I plan to do an updated package with a fix for that this week.) I think the dmesg errors here are probably not that serious: > ACPI: Invalid PBLK length [8] Something is wrong in the BIOS tables governing power management, but it's probably not important. > apanel: Fujitsu BIOS signature 'FJKEYINF' not found... This has something to do with the "application keys" on your keyboard > mmc0: Unknown controller version (2). You may experience problems. THis is your SD card reader > [drm:intel_dp_i2c_init] *ERROR* i2c_init DPDDC-B > [drm:intel_dp_i2c_init] *ERROR* i2c_init DPDDC-D This is about probing the properties of your laptops panel > [drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own An internal warning from the kernel graphics driver. My advice would be to ignore these warnings if things are working properly. However, if you have problems in the related areas (SD card reader not working, suspend/resume problems, etc.) then definitely include these messages in any bug report you file about it. Problems with downloading debuginfo information with ABRT are known and being worked on; ABRT is new in F-12 and still evolving rapidly. *** This bug has been marked as a duplicate of bug 546509 ***