After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 84117 - gnome-session segfaults immediatley on freebsd
gnome-session segfaults immediatley on freebsd
Status: RESOLVED NOTGNOME
Product: gnome-session
Classification: Core
Component: gnome-session
unspecified
Other FreeBSD
: Normal critical
: ---
Assigned To: Session Maintainers
Session Maintainers
: 84437 85057 85731 88725 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-06-04 14:12 UTC by chrisholl
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description chrisholl 2002-06-04 14:12:39 UTC
Package: gnome-session
Severity: normal
Version: 1.5.19
Synopsis: gnome-session segfaults immediatley on freebsd
Bugzilla-Product: gnome-session
Bugzilla-Component: gnome-session
BugBuddy-GnomeVersion: 2.0 (1.117.1)

Description:
Description of Problem:

I have installed gnome 2 in FreeBSD 4.5 from the gnome2 metaport
(x11/gnome2). When I try and run gnome-session, it immediatley
segfaults. Other programs such as nautilus and the gnome-panel run ok. I
have tried using different users, and have tried removing all the
~/.gnome* folders, but gnome-session still segfaults.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:




Debugging Information:

Backtrace was generated from '/usr/X11R6/bin/gnome-session'

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x289977fc in _thread_sys_poll ()
   from /usr/lib/libc_r.so.4

Thread 1 (process 9381, thread 1)

  • #0 _thread_sys_poll
    from /usr/lib/libc_r.so.4
  • #1 _thread_kern_sched_state_unlock
    from /usr/lib/libc_r.so.4
  • #2 _thread_kern_scheduler
    from /usr/lib/libc_r.so.4
#3  0x0 in ?? ()
No symbol table info available.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-04 10:12 -------

The original reporter (chrisholl@btinternet.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-session-maint@bugzilla.gnome.org.

Comment 1 Luis Villa 2002-06-04 21:47:46 UTC
Marking this critical but it isn't high right now. We need a more
rigorous deferral system so that I can push this more formally. :/ As
it is, that stack trace is probably pretty useless, unfortunately,
Chris, so unless someone actually on BSD can track it down and fix it,
it is unlikely to get fixed by the core gnome folks. [Unless Jacob can
duplicate it on his 'BSD' box ;)
Comment 2 jacob berkman 2002-06-05 15:06:12 UTC
i wouldn't be surprised if this is due to not having your fonts set up
correctly.

i don't know any ways to check this, though.
Comment 3 Luis Villa 2002-06-07 15:59:50 UTC
*** Bug 84437 has been marked as a duplicate of this bug. ***
Comment 4 Luis Villa 2002-06-15 12:07:08 UTC
*** Bug 85057 has been marked as a duplicate of this bug. ***
Comment 5 Luis Villa 2002-06-18 18:07:52 UTC
*** Bug 85731 has been marked as a duplicate of this bug. ***
Comment 6 Luis Villa 2002-06-18 18:22:42 UTC
cwenham, sven, eldooran, chrisholl: you guys are going to need to
rebuild with useful symbols and (most likely) get someone
knowledgeable from the FreeBSD community to help track this down, as
this trace is not useful and none of the gnome-session people are BSD
users. :/ Sorry about that- I'd certainly push to get a patch in ASAP,
if someone comes up with one.
Comment 7 anthony taranto 2002-07-08 06:34:35 UTC
this is due to some problems in the freebsd X4.1 and X4.2 ports at
some point.

removing all your system font dirs and reinstalling the latest x fonts
port has been reported to fix this problem.
Comment 8 Luis Villa 2002-07-09 04:16:05 UTC
OK, closing then. Thanks for tracking it down.
Comment 9 Luis Villa 2002-07-29 16:04:14 UTC
*** Bug 88725 has been marked as a duplicate of this bug. ***
Comment 10 Elijah Newren 2003-03-04 22:54:14 UTC
I apologize for the spam, but in talking to David Kennedy on #bugs we decided
that it might be useful for me to add a comment to a lot of bugs that have
nearly identical stack traces that aren't very useful.  (It took me a while
because I gave up on several bugzilla queries that simply hung).  Anyway, I may
have caught some bugs with this query that aren't relevant, so I apologize again
if this bug is one of those.  If not:

The following comment from 100709 may be relevant: "It turns out this was an
accidental FreeBSD ABI change during the import of gcc-3.2.1. div(), a structure
returning function, was the culprit."