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 647389 - Segmentation fault when launching application launcher
Segmentation fault when launching application launcher
Status: RESOLVED DUPLICATE of bug 641325
Product: gnome-panel
Classification: Other
Component: general
3.0.x
Other Linux
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-04-10 21:27 UTC by Balló György
Modified: 2011-04-11 13:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.91/3.0

Attachments
Stack trace (1.70 KB, text/plain)
2011-04-11 02:00 UTC, Balló György 		Details

Description Balló György 2011-04-10 21:27:29 UTC 
Gnome Panel crash with segmentation fault when I click on an application launcher. I use Arch Linux with Gnome 3 in fallback mode.

Program versions:
gnome-panel 3.0.0.1
gtk3 3.0.8
glib2 2.28.5

Steps to reproduce:
1. Open the main menu.
2. Drag a menu item from there and drop on the panel next to the main menu to create an application launcher.
3. Launch the newly created application launcher.
Panel will crash shortly after.
Comment 1 André Klapper 2011-04-11 00:34:52 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 Balló György 2011-04-11 02:00:17 UTC 
Created attachment 185676 [details]
Stack trace

Thank you for responding this bug. Here is the stack trace.
Comment 3 André Klapper 2011-04-11 10:04:08 UTC 
Looks like GTK+ only to me - which GTK version is this?
Comment 4 Vincent Untz 2011-04-11 13:01:49 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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