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 661245 - Unable to add applets to gnome panel (SIGINT)
Unable to add applets to gnome panel (SIGINT)
Status: RESOLVED DUPLICATE of bug 632369
Product: gnome-panel
Classification: Other
Component: window list
2.32.x
Other Linux
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-10-08 01:42 UTC by David
Modified: 2011-10-10 11:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Stacktrace (932 bytes, text/plain)
2011-10-10 01:27 UTC, David
Details
stacktrace 2 (18.09 KB, text/plain)
2011-10-10 01:27 UTC, David
Details

Description David 2011-10-08 01:42:00 UTC
Using Dual Monitors - on the primary monitor I can add applets via the 'Add to Panel' dialog box but on the 2nd monitor when I click on the Add button for the selected applet I get the error: "Applet Name here" has quit unexpectedly.

Clicking the reload button just cycles the error message.
Comment 1 Fabio Durán Verdugo 2011-10-08 16:54:54 UTC
problable crash and reload but we need the stacktrace. Because 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 David 2011-10-10 01:27:26 UTC
Created attachment 198683 [details]
Stacktrace
Comment 3 David 2011-10-10 01:27:55 UTC
Created attachment 198684 [details]
stacktrace 2
Comment 4 David 2011-10-10 01:29:04 UTC
I'm out of my depth on this, however attached are two files that were generated by following http://live.gnome.org/GettingTraces . 

While running these sequences the error dialogue panel still pops up prompting a reload request. This still recycles as mentioned above.

I don't understand the significance of the following lines:
====
0xffffe424 in __kernel_vsyscall ()
(gdb) cont
Continuing.
[New Thread 0xa3b35b70 (LWP 25438)]
[Thread 0xa3b35b70 (LWP 25438) exited]


^C
Program received signal SIGINT, Interrupt.
0xffffe424 in __kernel_vsyscall ()
(gdb) thread apply all bt
====

Thanks for your patience.
Comment 5 Vincent Untz 2011-10-10 11:13:13 UTC
The first stack trace shows a running panel that just got interrupted by the user while the second one is not even for a running panel ;-)

My guess is that you're experiencing bug 632369. You need this patch: http://git.gnome.org/browse/gnome-panel/commit/?h=gnome-2-32&id=cb969e989477e2671d1e0cdd1519866d61d0c98c

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