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 612056 - Crashed with SIGSEGV in ORBit_c_stub_invoke()
Crashed with SIGSEGV in ORBit_c_stub_invoke()
Status: RESOLVED DUPLICATE of bug 519013
Product: gnome-panel
Classification: Other
Component: general
2.29.x
Other Linux
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-03-07 04:49 UTC by Angel Abad
Modified: 2010-03-13 11:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Angel Abad 2010-03-07 04:49:31 UTC
In Ubuntu Lucid stlubuntu reported: 

When booting into the 64-bit Live CD (actually from a USB stick) for lucid on my asus-quad core AMD 3.0 Ghz (Phenom 945) desktop machine with 2 GB RAM, and 320 GB Sata HD, after selecting my language, then selecting try ubuntu without installing, the splash logo appeared and remained for about a minute, then the mouse pointer appears on a black screen with the following words at the top:

Process 371 GLib Warning

getpwuid_r(): failed due to unknown user ID(0)

init: ureadahead - other main process (1864) terminated with status 4

Could not write bytes: Broken pipe.

The mouse pointer would move around the screen just find but no gnome desktop would appear (and I was unable to select anything with my mouse.) I then did a CTRL-ALT-F2 for a virutal terminal and a

sudo /etc/init.d/gdm restart

Then the gnome desktop appeared normally. When this occurred I was booting to 64-bit Lucid Alpha 3 updated as of 3/3/2010.

Sorry if this is a duplicate but I did not see anything else exactly like it already filed.

ProblemType: Crash
Architecture: amd64
Date: Fri Mar 5 04:40:20 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gnome-panel
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100303)
Package: gnome-panel 1:2.29.91-0ubuntu1
ProcCmdline: gnome-panel
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
SegvAnalysis:
 Segfault happened at: 0x7fc2b346afc5 <ORBit_c_stub_invoke+149>: mov 0x18(%rcx),%rax
 PC (0x7fc2b346afc5) ok
 source "0x18(%rcx)" (0x100000019) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
 Bonobo_Unknown_ref ()
 bonobo_object_dup_ref ()
 bonobo_control_frame_bind_to_control ()
 bonobo_widget_construct_control_from_objref ()
Title: gnome-panel crashed with SIGSEGV in ORBit_c_stub_invoke()
Uname: Linux 2.6.32-15-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:4289): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:4286): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
 (gnome-power-manager:4296): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

Launchpad ref: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-panel/+bug/532414

Thanks!
Comment 1 Fabio Durán Verdugo 2010-03-11 23:30:31 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Angel Abad 2010-03-13 09:37:20 UTC
Hi, in launchpad stlubuntu says:

I would be more than happy to get a stack trace. However, my challenge is that this occurred during the boot process of the Live CD. So, I could sure use some advise on how to have the bug buddy and debug packages installed prior to the boot of the live CD. I will install it to my available hard drive partition and see if it occurs then, but if this occurs for a new users attempting to try the distro via the Live CD, it could be a deal breaker (as a completely new potential user would not have any idea about the workaround of CTRL-ALT-F2 and sudo /etc/init.d/gdm restart

Any advise? Thanks.

Also, thanks so much for taking a serious look into this in any case.

Thanks in advance.
Comment 3 Chris Coulson 2010-03-13 11:16:02 UTC
The downstream report is a duplicate of bug 519013
Comment 4 Chris Coulson 2010-03-13 11:16:15 UTC

*** This bug has been marked as a duplicate of bug 519013 ***