Bug 483776 – crash in Panel: J'ai executer le program...

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 483776 - crash in Panel: J'ai executer le program...


Summary:	crash in Panel: J'ai executer le program...


Status:	RESOLVED DUPLICATE of bug 480982

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-05 15:06 UTC by olivier
Modified:	2007-10-06 11:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description olivier 2007-10-05 15:06:53 UTC

Version: 2.20.0.1

What were you doing when the application crashed?
J'ai executer le programme "Utilisateur " de Gnome et cliquer ensuite sur "annuler"


Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.21.5 #1 Mon Jun 25 16:28:27 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Simple
Icon Theme: dlg-etiquette

Memory status: size: 37564416 vsize: 37564416 resident: 22540288 share: 13041664 rss: 22540288 rss_rlim: 4294967295
CPU usage: start_time: 1191596630 rtime: 96 utime: 88 stime: 8 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 0xb6f886b0 (LWP 6261)]
(no debugging symbols found)
0xb77bcbce in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 168029

Thread 1 (Thread 0xb6f886b0 (LWP 6261))

#0 __waitpid_nocancel
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 g_markup_escape_text
from /usr/lib/libglib-2.0.so.0
#6 ??
from /usr/lib/libgtk-x11-2.0.so.0
#7 ??
#8 ??
#9 ??
#10 g_value_transform
from /usr/lib/libgobject-2.0.so.0
#11 g_object_set_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_object_set
from /usr/lib/libgobject-2.0.so.0
#13 gtk_widget_set_tooltip_text
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libwnck-1.so.22
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#0 __waitpid_nocancel
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
(nautilus:6262): gnome-vfs-modules-WARNING **: Could not initialize inotify
(gnome-panel:6261): gnome-vfs-modules-WARNING **: Could not initialize inotify
Initializing gnome-mount extension
** (nautilus:6262): WARNING **: Failed to initialize libhal context: (null) : (null)
** (nautilus:6262): WARNING **: Could not initialize hal context
Shutting down gnome-mount extension
(bug-buddy:6463): gnome-vfs-modules-WARNING **: Could not initialize inotify
--------------------------------------------------

Comment 1 Susana 2007-10-06 11:42:29 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 480982 ***