Status

()

Core
Widget: Gtk
--
critical
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: Jeremy Rempel, Assigned: blizzard)

Tracking

({crash})

1.7 Branch
x86
Linux
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0

Quite often firefox crashes. I'm using suse w/ kde. I don't know if this is a
firefox bug, kde bug or x bug. I went into .xsession-errors and pulled this out:

(Gecko:10559): Gtk-CRITICAL **: file gtkwidget.c: line 3703
(gtk_widget_reparent): assertion `widget->parent != NULL' failed
*****sendCommand Truncated*****
*****sendCommand Truncated*****
Launched ok, pid = 11144
konqueror: ERROR: Error in BrowserExtension::actionSlotMap(), unknown action :
searchProvider
kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject
*parent, const char *name, KInstance *instance )
KonqSidebar::property( "modified" ) failed: property invalid or does not exist
KonqKfmIconView::property( "modified" ) failed: property invalid or does not exist
/bin/sh: William Rivers Pitt - TO Overview 12.09.04: command not found
ALSA lib pcm_hw.c:563:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:563:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:563:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
/bin/sh: : command not found
/bin/sh: 1026: command not found
DCOPReply<>: cast to 'QStringList' error
DCOPReply<>: cast to 'QString' error

(Gecko:10559): Gtk-CRITICAL **: file gtkwidget.c: line 3703
(gtk_widget_reparent): assertion `widget->parent != NULL' failed
*****sendCommand Truncated*****
ALSA lib pcm_hw.c:563:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
kwin: X_SetInputFocus(0xa521b2): BadMatch (invalid parameter attributes)
kwin: X_SetInputFocus(0xa521b2): BadMatch (invalid parameter attributes)
ALSA lib pcm_hw.c:563:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:563:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:563:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
*****sendCommand Truncated*****
*****sendCommand Truncated*****

(Gecko:10559): Gtk-CRITICAL **: file gtkwidget.c: line 3703
(gtk_widget_reparent): assertion `widget->parent != NULL' failed
ALSA lib pcm_hw.c:563:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe


Reproducible: Sometimes
Steps to Reproduce:

Updated

14 years ago
Severity: normal → critical
Keywords: crash

Comment 1

14 years ago
Is this specific to some URL or in general ?

Comment 2

13 years ago
I'd like to add completely uninformative confirmation. Uninformative because I'm
too clueless about linux to know how to go about tracing back the cause of the
error, but I shall do my best to say what I do know and hope it adds to the pile
of information. I'm running Suse 9.1 with KDE 3.4 and Firefox crashes a lot for
me as well. It particularly crashes when Sage is running (I'll go and report
that separately), but it has a habit of just totally dying, with no error
report, under no specific circumstances that I can identify.

It seems to have a particularly bad interaction with Konqueror. I've taken to
playing BBC radio programmes on Konqueror so that if Firefox crashes then I
don't have to start again, but often when I'm doing this, Firefox will hang,
hanging everything else as well. Eventually it brings up a "program not
responding" message and I agree to close it, or I manage to kill if from the
console. Firefox then refuses to start up again. I can click the icon and the
waiting icon starts but the program then doesn't open and the waiting icon
ceases. Sometimes it asks me which profile I want to use, having set a lock on
my normal profile. Deleting the lock file does not resolve the problem as it
simply relocks it when I try to open it. The only cure is to shut down and
reboot from cold as the rest of kde goes haywire, with kicker crashing, the
login process failing, and often the internet going down as well.

I will report this at KDE as well, but the profile lock seems to me to indicate
at least some connection with firefox itself rather than simply a general
problem. Sorry to be so unhelpful. If I can identify other factors I will come
and add them.

Updated

13 years ago
Assignee: bugs → blizzard
Component: OS Integration → Widget: Gtk
Product: Firefox → Core
QA Contact: os-integration → ian
Version: unspecified → 1.7 Branch
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.