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 141331 - Gnome Panel Cores after rapid Vertical Scrolling of Terminal Window.
Gnome Panel Cores after rapid Vertical Scrolling of Terminal Window.
Status: RESOLVED DUPLICATE of bug 105745
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 153588 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-04-28 21:53 UTC by tng
Modified: 2005-01-04 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description tng 2004-04-28 21:53:52 UTC
Package: gnome-panel
Severity: normal
Version: 2.2.0.1
Synopsis: Gnome Panel Cores after rapid Vertical Scrolling of Terminal Window.
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
Gnome Panel Cores after rapid Vertical Scrolling of Terminal window.

Steps to reproduce the problem:
1. Rapidly Verically Scroll the Terminal Application.  The Terminal was
running tcsh and had been up for about 4 hours and had been used for a
number of commands.
2. 
3. 

Actual Results:


Expected Results:
Obviously, it should just scroll the window up and down.

How often does this happen? Rare


Additional Information:




Debugging Information:

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

(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)...[New
Thread 1086431648 (LWP 1101)]

(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)...0xffffe002 in ?? ()

Thread 1 (Thread 1086431648 (LWP 1101))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #5 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #6 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-28 17:53 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-panel".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was tng@bruhn-newtech.com.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Mark McLoughlin 2004-05-13 11:46:15 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash.  Please make sure that the package was
compiled with debugging symbols and see
http://bugzilla.gnome.org/getting-traces.cgi for more information about useful
stack traces.
  
Comment 2 Vincent Noel 2004-09-23 20:51:46 UTC
*** Bug 153588 has been marked as a duplicate of this bug. ***
Comment 3 Vincent Untz 2005-01-04 14:03:31 UTC

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