GNOME Bugzilla – Bug 420822
crash in Power Manager: após digitar a snha pois...
Last modified: 2007-03-21 01:45:52 UTC
What were you doing when the application crashed? após digitar a snha pois estava no sistema que estava em modo de espera Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.18.0 2007-03-19 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.2999.fc7 #1 SMP Mon Mar 19 20:20:42 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299902 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 49516544 vsize: 49516544 resident: 6287360 share: 4534272 rss: 6287360 rss_rlim: 4294967295 CPU usage: start_time: 1174434709 rtime: 26 utime: 15 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-power-manager' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208121632 (LWP 2321)] (no debugging symbols found) 0x002f9402 in __kernel_vsyscall ()
+ Trace 120606
Thread 1 (Thread -1208121632 (LWP 2321))
----------- .xsession-errors (999 sec old) --------------------- 22:07:35 : ---> Loop Number: 2 22:07:35 : --> Executando Teste de Transação Checking deps for sinjdoc.i386 0-0.5-2.fc7 - u Checking deps for java-1.5.0-gcj.i386 0-1.5.0.0-6.fc7 - u Checking deps for jpackage-utils.noarch 0-1.7.3-1jpp.2.fc7 - u Checking deps for libgcj.i386 0-4.1.2-5 - u 22:07:43 : --> Processando Dependências: java_cup >= 0.10 para o pacote: sinjdoc 22:07:43 : --> Reinicialize a Resolução de Dependências com as novas alterações. 22:07:43 : ---> Loop Number: 3 22:07:43 : --> Executando Teste de Transação Checking deps for sinjdoc.i386 0-0.5-2.fc7 - u Checking deps for java-1.5.0-gcj.i386 0-1.5.0.0-6.fc7 - u Checking deps for java_cup.i386 1-0.10-0.k.6jpp.1 - u Checking deps for jpackage-utils.noarch 0-1.7.3-1jpp.2.fc7 - u Checking deps for libgcj.i386 0-4.1.2-5 - u --------------------------------------------------
*** This bug has been marked as a duplicate of 420419 ***