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 446764 - crash in Panel: Just starting the Sessio...
crash in Panel: Just starting the Sessio...
Status: RESOLVED DUPLICATE of bug 446593
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-12 14:48 UTC by the_thunderbolt
Modified: 2007-06-12 16:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description the_thunderbolt 2007-06-12 14:48:01 UTC
Version: 2.18.2

What were you doing when the application crashed?
Just starting the Session F7 is crap! I had hundreds of crashes since i used it. I'm on Fedora since FC2 and used everey Release but this is just a Nightmare!


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194_2.fc7.cubbi_suspend2 #1 SMP Thu May 31 10:24:31 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 36085760 vsize: 36085760 resident: 17874944 share: 15273984 rss: 17874944 rss_rlim: 4294967295
CPU usage: start_time: 1181659645 rtime: 12 utime: 11 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208981792 (LWP 3435)]
(no debugging symbols found)
0x00b08402 in __kernel_vsyscall ()

Thread 1 (Thread -1208981792 (LWP 3435))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #6 gtk_rc_reset_styles
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_cclosure_marshal_VOID__PARAM
    from /lib/libgobject-2.0.so.0
  • #9 ??
    from /lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #11 ??
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /lib/libgobject-2.0.so.0
  • #16 g_object_notify
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #20 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #21 ??
    from /lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
localuser:thunderbolt being added to access control list
SESSION_MANAGER=local/z10n:/tmp/.ICE-unix/3320
** Message: failed to load session from /home/thunderbolt/.nautilus/saved-session-HHJETT
** (nautilus:3433): WARNING **: Can not caclulate _NET_NUMBER_OF_DESKTOPS
** (nautilus:3433): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS
** (nautilus:3433): WARNING **: Can not get _NET_WORKAREA
** (nautilus:3433): WARNING **: Can not determine workarea, guessing at layout
(gnome-panel:3435): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
error getting update info:  Cannot open/read repomd.xml file for repository: livna
--------------------------------------------------
Comment 1 palfrey 2007-06-12 16:27:44 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

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