GNOME Bugzilla – Bug 481837
crash in System Log: trying to setup mysql
Last modified: 2007-10-06 11:08:39 UTC
Version: 2.18.1 What were you doing when the application crashed? trying to setup mysql Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 277143552 vsize: 277143552 resident: 20508672 share: 14766080 rss: 20508672 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191148224 rtime: 134 utime: 117 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/sbin/gnome-system-log' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496347984 (LWP 3990)] (no debugging symbols found) 0x0000003624a0d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 166583
Thread 1 (Thread 46912496347984 (LWP 3990))
----------- .xsession-errors --------------------- mysqld mysqld (pid 3452) is running... NetworkManager NetworkManager (pid 2573) is running... NetworkManager NetworkManager (pid 2573) is running... NetworkManager NetworkManager (pid 2573) is running... (nautilus:2927): Eel-WARNING **: No extension, not implemented yet _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost6.localdomain6 (gnome-terminal:4129): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket. Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-3099--861017909-1191146068 --active --geometry 80x24+5+73 --title root@localhost6:~ --work --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 442846 ***