| From | Sent On | Attachments |
|---|---|---|
| Elwood Blues | Jun 8, 2002 9:24 am | |
| Franz Klammer | Jun 8, 2002 10:03 am | |
| Joe Marcus Clarke | Jun 8, 2002 8:56 pm | |
| Elwood Blues | Jun 9, 2002 9:58 am | |
| Joe Marcus Clarke | Jun 9, 2002 11:04 am | |
| Elwood Blues | Jun 10, 2002 7:03 am | |
| Elwood Blues | Jun 12, 2002 1:16 pm | |
| Joe Marcus Clarke | Jun 12, 2002 2:25 pm |
| Subject: | Re: gnome2: gnome-session crashes | |
|---|---|---|
| From: | Joe Marcus Clarke (mar...@marcuscom.com) | |
| Date: | Jun 8, 2002 8:56:44 pm | |
| List: | org.freebsd.freebsd-gnome | |
On Sat, 2002-06-08 at 12:24, Elwood Blues wrote:
Not a single problem when I installed the gnome2 metaport on FreeBSD-4.6-RC built on May 18th, but whenever I try to start gnome-session, I get the following from bug-buddy:
Backtrace was generated from '/usr/X11R6/bin/gnome-session'
Is it actually crashing? What signal is gnome-session exiting on? sobomax found that without scalable fonts installed, GNOME 2 crashed all over the place. Make sure you have all the X fonts installed, and that all the font types are loaded in your XF86Config file.
(no debugging symbols found)... <REPEAT MANY TIMES> (no debugging symbols found)...(no debugging symbols found)...0x28992370 in _thread_sys_poll () from /usr/lib/libc_r.so.4 #0 0x28992370 in _thread_sys_poll () from /usr/lib/libc_r.so.4 #1 0x2899176c in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.4 #2 0x28991083 in _thread_kern_scheduler () from /usr/lib/libc_r.so.4 #3 0x0 in ?? ()
Thread 1 (process 17720, thread 1): #0 0x28992370 in _thread_sys_poll () from /usr/lib/libc_r.so.4 No symbol table info available. #1 0x2899176c in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.4 No symbol table info available. #2 0x28991083 in _thread_kern_scheduler () from /usr/lib/libc_r.so.4 No symbol table info available. #3 0x0 in ?? () No symbol table info available.
Also tried running gdm from /etc/ttys, but the interface hangs after any user input. Any ideas why this might be happening?
This seems to be a popular complaint. I never encountered it since I always start gdm from an rc script from /usr/X11R6/etc/rc.d. A new GNOME 2 snapshot is out, and I will be working on the update. Perhaps the new gdm2 will alleviate this problem.
Joe
-F
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message





