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 85057 - gnome-session segfaults on startup
gnome-session segfaults on startup
Status: RESOLVED DUPLICATE of bug 84117
Product: gnome-session
Classification: Core
Component: general
unspecified
Other FreeBSD
: Normal critical
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-06-12 17:59 UTC by cwenham
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description cwenham 2002-06-12 17:58:48 UTC
Package: gnome-session
Severity: blocker
Version: 1.5.21
Synopsis: gnome-session segfaults on startup
Bugzilla-Product: gnome-session
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.0)

Description:
Description of Problem:

gnome-session segfaults on start.

Steps to reproduce the problem:
1. Run "gnome-session"

Actual Results:

Bang.

Expected Results:

A Gnome Desktop.

How often does this happen?

Every time.

Additional Information:

Using FreeBSD 4.6 Current. Bult from ports collection


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)...0x489c2370 in _thread_sys_poll ()
   from /usr/lib/libc_r.so.4

Thread 1 (process 46794, 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-12 13:58 -------

Reassigning to the default owner of the component, gnome-session-maint@bugzilla.gnome.org.

Comment 1 Luis Villa 2002-06-15 12:07:10 UTC

*** This bug has been marked as a duplicate of 84117 ***
Comment 2 Elijah Newren 2003-03-04 22:56:03 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."