Closed
Bug 244564
Opened 21 years ago
Closed 13 years ago
"Client Certificates" and "Private Keys" causes Roaming sync to fail [@ gtk_widget_destroy ()]
Categories
(Core Graveyard :: Profile: Roaming, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jmccabe, Unassigned)
References
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
|
3.73 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040524
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040524
Selecting either "Client Certificates" or "Private Keys" as data to be stored in
the Roaming Store causes the sync to throw an error and then a core file.
Dialog box contains this error:
Transfer error with file "undefined": NS_ERROR_ILLEGAL_VALUE
Stack of the core will be attached.
Reproducible: Always
Steps to Reproduce:
| Reporter | ||
Comment 1•21 years ago
|
||
| Reporter | ||
Updated•21 years ago
|
Blocks: roamingtracking
#6 0x4029ba33 in gtk_widget_destroy () from /usr/lib/libgtk-x11-2.0.so.0
#7 0x40f4097a in moz_gtk_shutdown ()
from /usr/local/mozilla/components/libgfx_gtk.so
#8 0x40f72fbb in nsNativeThemeGTK::~nsNativeThemeGTK() ()
from /usr/local/mozilla/components/libgfx_gtk.so
#9 0x40ae0b87 in nsObserverService::GetObserverList(char const*,
nsObserverList**) () from /usr/local/mozilla/libxpcom.so
#10 0x417d72a1 in NSGetModule ()
from /usr/local/mozilla/components/libnsappshell.so
#11 0x417d000a in NSGetModule ()
from /usr/local/mozilla/components/libnsappshell.so
#12 0x417dd9a7 in NSGetModule ()
from /usr/local/mozilla/components/libnsappshell.so
#13 0x417cb342 in NSGetModule ()
from /usr/local/mozilla/components/libnsappshell.so
#14 0x415264f2 in GlobalWindowImpl::ReallyCloseWindow() ()
from /usr/local/mozilla/components/libgklayout.so
#15 0x41528ec8 in GlobalWindowImpl::CloseWindow(nsISupports*) ()
from /usr/local/mozilla/components/libgklayout.so
#16 0x4151b1f6 in nsJSContext::ScriptEvaluated(int) ()
Keywords: crash
Summary: "Client Certificates" and "Private Keys" causes Roaming sync to fail → "Client Certificates" and "Private Keys" causes Roaming sync to fail [@ gtk_widget_destroy ()]
Comment 3•21 years ago
|
||
These files probably don't exist. Might be related to or a dup of bug 244589,
but I didn't get the error dialog.
The crash is probably a related, but different bug. Roaming is in JS here,
should not be able to cause a crash (although it may trigger it).
| Reporter | ||
Comment 4•21 years ago
|
||
That was my first thought, but the files do exist:
# ls ~/.mozilla/DzM/x5ds2mfh.slt/*[38].db
/home/dzm/.mozilla/DzM/x5ds2mfh.slt/cert8.db
/home/dzm/.mozilla/DzM/x5ds2mfh.slt/key3.db
Comment 5•21 years ago
|
||
Grrr! cert7.db changed to cert8.db (wth?). Bug 244558. "Security module
database" is secmod.db.
| Reporter | ||
Comment 6•21 years ago
|
||
cert7.db was prone to corruption when dealing with writes larger than the OS
page size. This was most often encountered when installing large CRLs, but could
happen elsewhere too.
| Reporter | ||
Comment 7•21 years ago
|
||
I should point out that my old cert7.db is still present, and secmod.db is
pushed to the remote store.
Assignee: nobody → ben.bucksch
Component: Profile: BackEnd → Profile: Roaming
QA Contact: core.profile-manager-backend → core.profile-roaming
Updated•21 years ago
|
Assignee: ben.bucksch → nobody
Also on Windows (Server 2003):
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8a3) Gecko/20040816
Dialog box with
Title: Fatal error while trying to transfer files
Body: Transfer error with file "undefined": NS_ERROR_ILLEGAL_VALUE
Updated•21 years ago
|
Severity: normal → critical
Comment 9•20 years ago
|
||
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/
Comment 10•20 years ago
|
||
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
Closed: 20 years ago
Resolution: --- → EXPIRED
Updated•20 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
| Assignee | ||
Updated•14 years ago
|
Crash Signature: [@ gtk_widget_destroy ()]
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 13 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme INCO 2012-09-01
| Assignee | ||
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•