GNOME Bugzilla – Bug 424151
crash in System Log:
Last modified: 2007-03-30 14:45:50 UTC
Version: 2.16.0 What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:46 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- --> [Errno 4] IOError: <urlopen error (-3, 'Tijdelijke mislukking bij naamoplossing')> Trying other mirror. [Yum] Loading "installonlyn" plugin Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mirrorlist?repo=core-6&arch=i386 error was [Errno 4] IOError: <urlopen error (-3, 'Tijdelijke mislukking bij naamoplossing')> Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-fc6&arch=i386 error was [Errno 4] IOError: <urlopen error (-3, 'Tijdelijke mislukking bij naamoplossing')> Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mirrorlist?repo=extras-6&arch=i386 error was [Errno 4] IOError: <urlopen error (-3, 'Tijdelijke mislukking bij naamoplossing')> Using default mirror detection Failure getting http://macromedia.rediris.es/rpm/repodata/repomd.xml: --> [Errno 4] IOError: <urlopen error (-3, 'Tijdelijke mislukking bij naamoplossing')> Trying other mirror. ** (bug-buddy:2783): WARNING **: Kon geen pictogram laden voor Map openen -------------------------------------------------- Memory status: size: 49721344 vsize: 0 resident: 49721344 share: 0 rss: 11554816 rss_rlim: 0 CPU usage: start_time: 1175181806 rtime: 0 utime: 18 stime: 0 cutime:12 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/sbin/gnome-system-log' (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 -1208645408 (LWP 2781)] (no debugging symbols found) 0x00744402 in __kernel_vsyscall ()
+ Trace 123236
Thread 1 (Thread -1208645408 (LWP 2781))
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 366458 ***