Closed
Bug 716385
Opened 13 years ago
Closed 12 years ago
crash on attachments
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: s.fendrich, Unassigned)
References
Details
(Keywords: crash, stackwanted)
User Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Build ID: 20111220165912 Steps to reproduce: Anything I try to do with attachments, e.g. a. open an attachment: left click on an attachment b. save an attachment: right click on an attachment, then click "save as" and select a destination c. attach an attachment: click "write", then "attach" d. configure attachments: click "edit", then "preferences", then "attachments" Actual results: attachments are handled as expected, but thunderbird crashes Expected results: thunderbird should not crash
Comment 1•13 years ago
|
||
Can you provide a crash ID from about:crashes ? The easiest way to get the crash id is to install https://addons.mozilla.org/de/thunderbird/addon/viewabout/
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to Matthias Versen (Matti) from comment #1) > Can you provide a crash ID from about:crashes ? > The easiest way to get the crash id is to install > https://addons.mozilla.org/de/thunderbird/addon/viewabout/ Thank you for the response. Unfortunately there are no crash reports and I don't get them enabled. My ~/.thunderbird/Crash Reports/crashreporter.ini looks like this: [Crash Reporter] Enabled=1 EmailMe=0 SubmitReport=1 Meanwhile I have found out that there are some error messages: At startup: failed to create drawable /usr/lib/gio/modules/libgsettingsgconfbackend.so: undefined symbol: gconf_value_free Failed to load module: /usr/lib/gio/modules/libgsettingsgconfbackend.so At crash: /opt/thunderbird/thunderbird-bin: symbol lookup error: /usr/lib/gnome-vfs-2.0/modules/libfile.so: undefined symbol: gnome_vfs_unescape_string
Comment 3•13 years ago
|
||
I somehow missed that you are on linux and that you are very likely using a build from your distribution. The crash reporter works only on Mozilla.org builds because the symbols are extracted during the build process and have to be uploaded to the Mozilla crash server. This looks like http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626076
Reporter | ||
Comment 4•13 years ago
|
||
Yes, the workaround proposed at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626076 works for me, too: in /etc/gnome-vfs-2.0/modules/default-modules.conf uncomment "file: file", that is: #file: file
Comment 5•13 years ago
|
||
Yeah, that looks like the same ld.so bug. You should upgrade your libc.
Comment 6•12 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #5) > Yeah, that looks like the same ld.so bug. You should upgrade your libc. bug invalid?
Severity: normal → critical
Keywords: crash,
stackwanted
Comment 7•12 years ago
|
||
Invalid if confirmed that this is the same problem.
Comment 8•12 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #7) > Invalid if confirmed that this is the same problem. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626076 is going nowhere. However, please reopen this you feel this is still a thunderbird problem.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
See Also: → http://bugs.debian.org/626076
Comment 9•12 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #8) > (In reply to Mike Hommey [:glandium] from comment #7) > > Invalid if confirmed that this is the same problem. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626076 is going nowhere. How is it going nowhere? It's been fixed for a while now.
Comment 10•12 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #9) > (In reply to Wayne Mery (:wsmwk) from comment #8) > > (In reply to Mike Hommey [:glandium] from comment #7) > > > Invalid if confirmed that this is the same problem. > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626076 is going nowhere. > > How is it going nowhere? It's been fixed for a while now. guess I'm no good at reading debian reports
You need to log in
before you can comment on or make changes to this bug.
Description
•