Closed Bug 219882 Opened 22 years ago Closed 22 years ago

sometimes crash when I try select text

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: alexejs_mj, Assigned: bugzilla)

Details

(Keywords: crash)

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Build Identifier: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Sometimes crash when I try select text in any text fields: address bar, text fields in pages. Reproducible: Sometimes Steps to Reproduce: 1. left-click where start to select text 2. move mouse to needed direction Actual Results: Browser crashes - does not show any error message windows, exits Expected Results: Select needed text :) OS: Red Hat Linux 9.0 (linux 2.4.20-19.8) WM: Gnome 2.2.0 PC: C633/RAM192 Theme: Mozilla Firebird
Knowing what build of Firebird you are using is important but you didn't report it. Does it occur in a new profile?
Severity: normal → critical
Keywords: crash
Firebild 0.6.1 build 2003072801
Firebird 0.6.1 build 2003072801
QA Contact: asa
I hope that this will help: I tried to run Firebird in terminal and after Firebird crashed there was: Gtk-CRITICAL **: file gtkselection.c: line 597 (gtk_selection_convert): assertion `widget != NULL' failed.
Alexejs, did you also try to create a new profile as suggested by Bill? If so, please report back - additionally your build is rather old (over two month) so I'd kindly ask you to - download latest 0.7 Release Candidate from http://ftp.mozilla.org/pub/firebird/nightly/latest-0.7/ - create an additional new, vanilla profile without installing any themes / extensions - and to re-test your problem
I tried Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031003 Firebird/0.7 This build didn't crash anytime last week.
Marking WFM per reporter's comment (comment 6)
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
QA Contact: bugzilla
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
QA Contact: bugzilla → general
You need to log in before you can comment on or make changes to this bug.