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 320889 - Applications->Run Application... crashes
Applications->Run Application... crashes
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: panel
2.10.x
Other other
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 323235 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-11-07 16:07 UTC by maly.velky
Modified: 2005-12-18 08:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description maly.velky 2005-11-07 16:07:57 UTC
Distribution: Debian testing/unstable
Package: gnome-panel
Severity: critical
Version: GNOME2.10.2 2.10.x
Gnome-Distributor: Debian
Synopsis: Applications->Run Application... crashes
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
Bugzilla-Version: 2.10.x
BugBuddy-GnomeVersion: 2.0 (2.10.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. Click the menu "Applications" on the gnome panel
2. Click the menu item "Run Application..."
The "Run Application" dialog appears but immediately a notification of
its crash pops out.

Expected Results:
No crash notification; the dialog should appear and let me entrer the
program to run.

How often does this happen?
Always (4 out of 4 attemps)

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1223117120 (LWP 10394)]
[New Thread -1226749008 (LWP 10397)]
(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)
(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)
0xb7942201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread -1223117120 (LWP 10394))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib/tls/libc.so.6
  • #4 panel_properties_dialog_present
  • #5 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #9 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug moved to this database by unknown@gnome.bugs 2005-11-07 16:07 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was maly.velky@email.cz.

Comment 1 Sebastien Bacher 2005-11-20 15:19:08 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash. Can you get us one with debugging symbols?
Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Teppo Turtiainen 2005-12-05 17:52:24 UTC
*** Bug 323235 has been marked as a duplicate of this bug. ***
Comment 3 Chong Luo 2005-12-06 06:14:19 UTC
Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1220802880 (LWP 6577)]
[New Thread -1238156368 (LWP 6625)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1220802880 (LWP 6577))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 739
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 panel_properties_dialog_present
  • #6 g_idle_dispatch
    at gmain.c line 3817
  • #7 IA__g_main_context_dispatch
    at gmain.c line 1934
  • #8 g_main_context_iterate
    at gmain.c line 2565
  • #9 IA__g_main_loop_run
    at gmain.c line 2769
  • #10 IA__gtk_main
    at gtkmain.c line 1009
  • #11 main
  • #0 __kernel_vsyscall

Comment 4 Chong Luo 2005-12-06 15:25:05 UTC
Is this information enough? I've installed libgnomeui-dbg, libgtk-dbg,
libglib-dbg etc. Is there any other dbg package I need to install? btw: my
system is Debian Sid.
Comment 5 Teppo Turtiainen 2005-12-09 15:59:30 UTC
Maybe. Reopening for now.
Comment 6 Vincent Untz 2005-12-12 10:49:10 UTC
Is gnome-panel-dbg available? :-)
Comment 7 Chong Luo 2005-12-14 03:03:56 UTC
I can't find gnome-panel-dbg. Do I need to install this one?

gnome-applets-dbg - Various applets for GNOME 2 panel - binary files with
debugging symbols
Comment 8 Vincent Untz 2005-12-14 19:10:21 UTC
No, we're only interested in gnome-panel, and not in gnome-applets. What is your
distribution?
Comment 9 Sebastien Bacher 2005-12-14 19:50:37 UTC
Vincent, the Debian package have no -dbg variant for gnome-panel, that's Ubuntu
specific
Comment 10 Vincent Untz 2005-12-15 08:12:50 UTC
Chong: can you follow the steps outlined at
http://wiki.debian.org/?HowToGetABacktrace to get a better stack trace? It
shouldn't be too hard.

If you can't, we probably can find someone who can make a dbg package for you.

Thanks,
Comment 11 Chong Luo 2005-12-16 19:44:49 UTC
I will try to do it during the weekends.
Comment 12 Chong Luo 2005-12-18 06:59:50 UTC
I followed the steps you gave, and re-generated the back trace:
----------------------
Backtrace was generated from '/usr/bin/gnome-panel'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1220786496 (LWP 11855)]
[New Thread -1230980176 (LWP 11893)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1220786496 (LWP 11855))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 739
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 panel_run_dialog_add_items_idle
    at /home/john/tmp/gnome-panel-2.10.2/./gnome-panel/panel-run-dialog.c line 754
  • #6 g_idle_dispatch
    at gmain.c line 3817
  • #7 IA__g_main_context_dispatch
    at gmain.c line 1934
  • #8 g_main_context_iterate
    at gmain.c line 2565
  • #9 IA__g_main_loop_run
    at gmain.c line 2769
  • #10 IA__gtk_main
    at gtkmain.c line 1009
  • #11 main
    at /home/john/tmp/gnome-panel-2.10.2/./gnome-panel/main.c line 90
  • #0 __kernel_vsyscall

Comment 13 Vincent Untz 2005-12-18 08:58:33 UTC
Okay, this bug is fixed since 2.12.1:

2005-09-16  Vincent Untz  <vuntz@gnome.org>

	* panel-properties-dialog.c: (panel_properties_dialog_toplevel_notify):
	(panel_properties_dialog_background_notif): check the value we got
	from panel_gconf_basename()
	* panel-run-dialog.c: (fuzzy_command_match):
	(panel_run_dialog_add_items_idle): add sanity checks before strcmp()

Debian people can either add a patch to the package or you can wait for GNOME
2.12 being uploaded to sid. You can also recompile a package for you with the
following patch:
http://cvs.gnome.org/viewcvs/gnome-panel/gnome-panel/panel-run-dialog.c?r1=1.55&r2=1.56

Thanks for helping us!