Bug 40328 - Linux Crashes When Scoll Bar Dragged
Summary: Linux Crashes When Scoll Bar Dragged
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-core   
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2001-05-11 23:23 UTC by Need Real Name
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-05-14 14:36:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Need Real Name 2001-05-11 23:23:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (X11; U; Linux 2.2.16-22smp i686)

Description of problem:
When the scroll bar is dragged on a window on the Gnome desktop the cursor
pauses for a couple of seconds.  If the cursor is dragged at the side of a
Linuxconfig window Linux crashes.  If the cursor is dragged in help window
for Applixware LInux crashes.  If the scroll bar is dragged in an new
device edit window Linux crashes.

How reproducible:

Steps to Reproduce:
1.  Open any Linuxconfig window
2.  Drag the scroll bar
3.  Linux crashes

Actual Results:  Linux crashes

Expected Results:  The scroll bar should have moved up and down and the
contents of the window should have scrolled

Additional info:

I am using a Logitech three button Pilot mouse, and an ATI Expert 2000
graphics card.  The PC is an HP XM600 with a 700MHZ PIII processor.

Comment 1 Owen Taylor 2001-05-14 14:36:43 UTC
Since Red Hat 7.0 was released quite a while ago, and we haven't
had any other reports of this sort of problem, it's probably
something particular to your setup.

 - Are you using the standard 7.0 X packages?

 - Are you using the default GTK+ theme, or some other GTK+ theme?
   (The theme is selected from the "Theme Selection" option
   in the GNOME control center.)

Note You need to log in before you can comment on or make changes to this bug.