GNOME Bugzilla – Bug 354046
Crash in g_utf8_validate
Last modified: 2007-10-06 14:55:22 UTC
Version: 2.15.9 What were you doing when the application crashed? opening a text file Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.92 2006-08-22 (Ubuntu) BugBuddy Version: 2.15.92 Memory status: size: 63434752 vsize: 0 resident: 63434752 share: 0 rss: 20959232 rss_rlim: 0 CPU usage: start_time: 1157240124 rtime: 0 utime: 54 stime: 0 cutime:51 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226700400 (LWP 4949)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 71453
Thread 1 (Thread -1226700400 (LWP 4949))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. More important, could you also attach the file that cause the crash to this bug ? Thank you.
*** Bug 359026 has been marked as a duplicate of this bug. ***
*** Bug 359184 has been marked as a duplicate of this bug. ***
*** Bug 362973 has been marked as a duplicate of this bug. ***
*** Bug 365578 has been marked as a duplicate of this bug. ***
*** Bug 365809 has been marked as a duplicate of this bug. ***
*** Bug 366279 has been marked as a duplicate of this bug. ***
*** Bug 366367 has been marked as a duplicate of this bug. ***
We have several duplicates of this bug, I'm wondering if something is changed in g_utf8_validate. We still lack a good stack trace. If you are still experiencing this crash, could you please: - send us a file to reproduce the crash - send us a stack trace with debugging symbols (see http://live.gnome.org/GettingTraces for more information on how to do so)
*** Bug 353701 has been marked as a duplicate of this bug. ***
*** Bug 367271 has been marked as a duplicate of this bug. ***
*** Bug 367423 has been marked as a duplicate of this bug. ***
Hopefully this is the information you're looking for. I cannot attach the bookmarks.html file because I can't seem to upload it, to your attachment field or anywhere else for that matter. Can't even copy it to another directory on my computer. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 84025344 vsize: 0 resident: 84025344 share: 0 rss: 25501696 rss_rlim: 0 CPU usage: start_time: 1162219762 rtime: 0 utime: 123 stime: 0 cutime:116 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gedit' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227307344 (LWP 21325)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 80460
Thread 1 (Thread -1227307344 (LWP 21325))
Great Noah! Could you please install also dbg package for glib and resend the new stack trace? Could you also please specify step by step how you are reproducing the crash? Could you attach the section of the ~/.gnome2/gedit-metadata.xml related to the bookmarks.html file? Could you cut&paste the file inside the comment field in bugzilla? Wow... a lot of requests ;) Thank you again. ----- Note for the gedit team: - it looks gedit_convert_to_utf8 is called to convert a text from UTF-8 to UTF-8. This is really strange.
I can no longer recreate the bug right now because fsck decided that the file was messed up when I restarted, and I think it added end of file data to the beginning of the file because the file is now 0kb large and no longer gives me the bug in Gedit - it just opens as though it was a blank empty file. I would produce the crash by attempting to open the file by navigating to its directory in nautilus, and then right-clicking and choosing Open With "Text Editor." Right after this, gedit would open, lock up, and the bug report program would open. I think this is the gedit-metadata.xml section you requested: <document uri="file:///media/sda2/Apps/Mozilla/Firefox/Profiles/hh4699xs.default/bookmarks.html" atime="1162223030"> <entry key="position" value="0"/> </document> I'll be sure to report if I'm able to create this bug again, with the requested trace using the glib debug symbols I hope this gets you closer to the source of the problem!
*** Bug 367686 has been marked as a duplicate of this bug. ***
*** Bug 368184 has been marked as a duplicate of this bug. ***
*** Bug 368435 has been marked as a duplicate of this bug. ***
*** Bug 368526 has been marked as a duplicate of this bug. ***
*** Bug 368709 has been marked as a duplicate of this bug. ***
*** Bug 368696 has been marked as a duplicate of this bug. ***
> Note for the gedit team: > - it looks gedit_convert_to_utf8 is called to convert a text from UTF-8 to > UTF-8. > This is really strange. I don't think this is strange: when no encoding is specified, we query the encodings to try from gconf and we try them. In most locales the first encodin tried is UTF-8
*** Bug 368988 has been marked as a duplicate of this bug. ***
*** Bug 369915 has been marked as a duplicate of this bug. ***
*** Bug 370272 has been marked as a duplicate of this bug. ***
*** Bug 370489 has been marked as a duplicate of this bug. ***
*** Bug 371358 has been marked as a duplicate of this bug. ***
File i tried to open was on ntfs drive and crypted by me in windows, that is allowing no one to access those files, and i think that is the reason for crash, i have not yet tried to boot into windows and remove this protection.
*** Bug 371508 has been marked as a duplicate of this bug. ***
*** Bug 371752 has been marked as a duplicate of this bug. ***
*** Bug 372118 has been marked as a duplicate of this bug. ***
*** Bug 372185 has been marked as a duplicate of this bug. ***
*** Bug 372186 has been marked as a duplicate of this bug. ***
*** Bug 372236 has been marked as a duplicate of this bug. ***
*** Bug 373504 has been marked as a duplicate of this bug. ***
*** Bug 373538 has been marked as a duplicate of this bug. ***
paolo, isn't bug 352099 just a dup?
*** Bug 374205 has been marked as a duplicate of this bug. ***
*** Bug 374843 has been marked as a duplicate of this bug. ***
*** Bug 372379 has been marked as a duplicate of this bug. ***
*** Bug 376137 has been marked as a duplicate of this bug. ***
*** Bug 376704 has been marked as a duplicate of this bug. ***
*** Bug 376967 has been marked as a duplicate of this bug. ***
*** Bug 377881 has been marked as a duplicate of this bug. ***
*** Bug 377776 has been marked as a duplicate of this bug. ***
*** Bug 378005 has been marked as a duplicate of this bug. ***
*** Bug 378328 has been marked as a duplicate of this bug. ***
*** Bug 378994 has been marked as a duplicate of this bug. ***
*** Bug 379019 has been marked as a duplicate of this bug. ***
*** Bug 379169 has been marked as a duplicate of this bug. ***
*** Bug 379245 has been marked as a duplicate of this bug. ***
*** Bug 379443 has been marked as a duplicate of this bug. ***
*** Bug 379600 has been marked as a duplicate of this bug. ***
*** Bug 379786 has been marked as a duplicate of this bug. ***
*** Bug 379632 has been marked as a duplicate of this bug. ***
*** Bug 379877 has been marked as a duplicate of this bug. ***
*** Bug 380093 has been marked as a duplicate of this bug. ***
*** Bug 380567 has been marked as a duplicate of this bug. ***
*** Bug 380583 has been marked as a duplicate of this bug. ***
*** Bug 381613 has been marked as a duplicate of this bug. ***
I hope thats what you need... I have a ntfs volume of my windows xp installation mounted and everytime I access an encrypted file gedit crashes. I mean that´s no problem for me because I didn´t expect to be able to read these files, but maybe you´d like to catch this exception in any way. Please let me know if you need more information/debugging symbols. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 44806144 vsize: 0 resident: 44806144 share: 0 rss: 21254144 rss_rlim: 0 CPU usage: start_time: 1165087225 rtime: 0 utime: 59 stime: 0 cutime:52 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gedit' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227168080 (LWP 19832)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 91121
Thread 1 (Thread -1227168080 (LWP 19832))
Created attachment 77575 [details] testutf8.c Hi Caleb (and everybody else), the info you provided is very useful, but we still need some help to figure out what's wrong. Can you (and anybody) else try this simple test program on the files that cause the crash? To compile the program (you need gcc installed), download the file testutf8.c and compile it with the command: gcc -o testutf8 -g -O0 -fno-inline testutf8.c To run the test, in the directory where you compiled run: ./testutf8 /path/to/the/problematic/file Thanks in advance!
*** Bug 381874 has been marked as a duplicate of this bug. ***
I ran... ./testutf8 /var/crash/_usr_bin_xchat.1000.crash > testutf8.txt ...and uploaded testutf8.txt here: http://expandapps.org/testutf8.txt
Thanks Jacob, though I forgot to mention an important thing: I am interested in the output of the test program only if the test program itself crashes while validating the file in the same way as gedit does. Also, if possible stick to small files or the output of the test program is huge.
*** Bug 382272 has been marked as a duplicate of this bug. ***
*** Bug 382521 has been marked as a duplicate of this bug. ***
*** Bug 382686 has been marked as a duplicate of this bug. ***
*** Bug 382707 has been marked as a duplicate of this bug. ***
*** Bug 382884 has been marked as a duplicate of this bug. ***
*** Bug 383246 has been marked as a duplicate of this bug. ***
*** Bug 383404 has been marked as a duplicate of this bug. ***
*** Bug 384145 has been marked as a duplicate of this bug. ***
*** Bug 384400 has been marked as a duplicate of this bug. ***
*** Bug 384412 has been marked as a duplicate of this bug. ***
*** Bug 384923 has been marked as a duplicate of this bug. ***
*** Bug 385033 has been marked as a duplicate of this bug. ***
*** Bug 385115 has been marked as a duplicate of this bug. ***
*** Bug 385272 has been marked as a duplicate of this bug. ***
*** Bug 385431 has been marked as a duplicate of this bug. ***
*** Bug 385485 has been marked as a duplicate of this bug. ***
*** Bug 386105 has been marked as a duplicate of this bug. ***
*** Bug 387304 has been marked as a duplicate of this bug. ***
*** Bug 387564 has been marked as a duplicate of this bug. ***
*** Bug 388128 has been marked as a duplicate of this bug. ***
*** Bug 389608 has been marked as a duplicate of this bug. ***
*** Bug 389693 has been marked as a duplicate of this bug. ***
*** Bug 390009 has been marked as a duplicate of this bug. ***
Poalo, sorry for my slow response. Been really busy. No, the program does not crash when running. What file should I really be running that test app on?
*** Bug 390858 has been marked as a duplicate of this bug. ***
*** Bug 391085 has been marked as a duplicate of this bug. ***
*** Bug 391287 has been marked as a duplicate of this bug. ***
*** Bug 391318 has been marked as a duplicate of this bug. ***
*** Bug 391490 has been marked as a duplicate of this bug. ***
*** Bug 391552 has been marked as a duplicate of this bug. ***
*** Bug 391553 has been marked as a duplicate of this bug. ***
*** Bug 391624 has been marked as a duplicate of this bug. ***
*** Bug 391630 has been marked as a duplicate of this bug. ***
Thanks to James "Doc" Livingston it seems we have finally discovered what is going on with this crash. gedit uses mmap to read local files, when an IO error occurs reading the mmapped file a SIGBUS signal is emitted by the kernel. We need to handle this signal and report an error if an IO error occurs. Useful links: - http://en.wikipedia.org/wiki/SIGBUS - http://en.wikipedia.org/wiki/Bus_error - http://www.ussg.iu.edu/hypermail/linux/kernel/0205.1/0550.html It seems gtk-gnutella handle this error in a sane way: - http://www.google.com/codesearch?hl=it&q=show:CIJEb4HMdWg:PdX2fAEFpkI:PuVeU2YcdZo&sa=N&ct=rd&cs_p=https://svn.sourceforge.net/svnroot/gtk-gnutella/trunk&cs_f=gtk-gnutella/src/core/bsched.c
Created attachment 79236 [details] [review] patch v1 Here is a patch implementing the proposed fix. however it still needs work: - it just handles SIGBUS. is it ok or should we also handle SIGSEGV? Especially on Solaris etc - The critical section in which the signal is handled could be made smaller (e.g. avoid to do it for the whole duration of update_document_content, even when reading the metadata etc), but how? using a global variable to store a flag that is checked in the signal handler (like one of the link above does) is ugly, since update_document_contents could be in the future be called concurrently by different loader objects (e.g. in an idle for the remote case or something like that) - the error message displayed in the UI needs to be thought out (and also added to the revert case)
(In reply to comment #100) > Created an attachment (id=79236) [edit] > patch v1 Patch looks mainly ok a part from the comment you did. > > Here is a patch implementing the proposed fix. however it still needs work: > > - it just handles SIGBUS. is it ok or should we also handle SIGSEGV? > Especially on Solaris etc I'm afraid we need to catch both, but we could try to ask to some Solaris guru or ask to some Sun guy to ask. > > - The critical section in which the signal is handled could be made smaller > (e.g. avoid to do it for the whole duration of update_document_content, even > when reading the metadata etc), but how? using a global variable to store a > flag that is checked in the signal handler (like one of the link above does) is > ugly, since update_document_contents could be in the future be called > concurrently by different loader objects (e.g. in an idle for the remote case > or something like that) I know the solution is not very nice (well, it is actually very ugly) but we can add a "signalcatched" flag to update_document_content and use a global variable to mark the critical section only if the flag is set. > > - the error message displayed in the UI needs to be thought out (and also > added to the revert case) > Yep. We can start by adding a full stop at the end of the message.
<paolo> the question is: to manage IO errors that occurs accessing a mmapped file, should I handle only SIGBUS (like on Linux) or also SIGSEGV? <paolo> See http://bugzilla.gnome.org/show_bug.cgi?id=354046#c100 <MikeS_> paolo: if you're accessing something where that might be an issue, you probably shouldn't use mmap. <bugsbot> paolo: Bug 354046 cri, High, 2.18.0, gedit-maint@gnome.bugs, UNCO, Crash in g_utf8_validate <MikeS_> paolo: on linux, SIGBUS is sufficient. However, I doubt that's portable. <paolo> MikeS_: we use mmap in gedit to read text files, we don't know what we are accessing. <MikeS_> If it's an application bug (rather than a library bug), then you _could_ handle SIGBUS, but I really doubt it's a good idea. <MikeS_> paolo: maybe that's the problem! <lifeless> aw man, mmap and io errors - dont. <lifeless> the idiom of mmap is not sufficient to work with mmapped files. <MikeS_> signal handling is SO archaic, ugly, and nasty. Really a fucking mess of an API <paolo> yep, but since we are in a single-threaded application, they can be used with some siglongjmp magic <MikeS_> paolo: the fact that you CAN make it work is not a compelling argument that you SHOULD. <lifeless> paolo: errr, as long as you dont care about e.g. malloc data structures being ciorrupted <paolo> the problem is only knowing which signal to handle to be sure to work in most unices <MikeS_> paolo: Avoiding mmap is generally a better idea. <MikeS_> mmap of arbitrary files, that is. You just have to live with the fact that I/O errors on the application and libraries it uses are going to kill your app. <paolo> lifeless: why "malloc data structures being ciorrupted"? <paolo> MikeS_: but there are some interesting pros in most cases <MikeS_> paolo: yes, there are lots of things that are GOOD about using mmap. There's really only one downside: "your application will randomly crash when actual users touch it". And trying to fix that one is Not Worth The Pain. <paolo> MikeS_: does not worth the pain or is "impossible"? <MikeS_> paolo: reliably? I wouldn't expect it to be practical for a volunteer project, though it might be possible. <paolo> MikeS_: thanks for the tips, I will discuss them with the other gedit guys. Can I attach the log to the relevant bugzilla bug? <MikeS_> If you want. <paolo> thanks <MikeS_> we considered doing this in gstreamer. Apart from the general nastiness of libraries doing signal handling, we decided it wasn't practical to make it work anyway. So we just stopped using mmap; the performance advantage wasn't very significant anyway <paolo> MikeS_: yep, doctau told us <lifeless> paolo: I mean that because you use longjmp, you have to hope that any code being interrupted has no transient state, and is atomic on *every operation*, or else chaos can ensue <lifeless> paolo: longjmp when explicitly used is fine, longjmp from signals is real bad <lifeless> because signals can arrive between any two instructions, and then the routine never completes <paolo> lifeless: oh, ok
*** Bug 392277 has been marked as a duplicate of this bug. ***
*** Bug 392332 has been marked as a duplicate of this bug. ***
*** Bug 392507 has been marked as a duplicate of this bug. ***
*** Bug 392509 has been marked as a duplicate of this bug. ***
*** Bug 393098 has been marked as a duplicate of this bug. ***
*** Bug 393402 has been marked as a duplicate of this bug. ***
*** Bug 394120 has been marked as a duplicate of this bug. ***
*** Bug 394387 has been marked as a duplicate of this bug. ***
*** Bug 394822 has been marked as a duplicate of this bug. ***
*** Bug 394593 has been marked as a duplicate of this bug. ***
*** Bug 395073 has been marked as a duplicate of this bug. ***
*** Bug 395243 has been marked as a duplicate of this bug. ***
*** Bug 395332 has been marked as a duplicate of this bug. ***
*** Bug 396323 has been marked as a duplicate of this bug. ***
*** Bug 396266 has been marked as a duplicate of this bug. ***
*** Bug 396546 has been marked as a duplicate of this bug. ***
*** Bug 395993 has been marked as a duplicate of this bug. ***
*** Bug 396977 has been marked as a duplicate of this bug. ***
*** Bug 397038 has been marked as a duplicate of this bug. ***
106 duplicates => blocker. paolo, are you working on this? do you think this can be fixed for 2.16.3 / 2.18.0?
As a last resource, the patch I attached in comment #100 works, but we still hope to implement a better solution before 2.18.0
*** Bug 397476 has been marked as a duplicate of this bug. ***
*** Bug 397646 has been marked as a duplicate of this bug. ***
*** Bug 397647 has been marked as a duplicate of this bug. ***
*** Bug 398302 has been marked as a duplicate of this bug. ***
*** Bug 398657 has been marked as a duplicate of this bug. ***
*** Bug 398656 has been marked as a duplicate of this bug. ***
*** Bug 398440 has been marked as a duplicate of this bug. ***
*** Bug 398953 has been marked as a duplicate of this bug. ***
*** Bug 399689 has been marked as a duplicate of this bug. ***
*** Bug 401104 has been marked as a duplicate of this bug. ***
*** Bug 401325 has been marked as a duplicate of this bug. ***
*** Bug 401387 has been marked as a duplicate of this bug. ***
*** Bug 401388 has been marked as a duplicate of this bug. ***
*** Bug 401425 has been marked as a duplicate of this bug. ***
*** Bug 401460 has been marked as a duplicate of this bug. ***
*** Bug 401505 has been marked as a duplicate of this bug. ***
*** Bug 401744 has been marked as a duplicate of this bug. ***
*** Bug 401858 has been marked as a duplicate of this bug. ***
*** Bug 402631 has been marked as a duplicate of this bug. ***
*** Bug 402632 has been marked as a duplicate of this bug. ***
*** Bug 402729 has been marked as a duplicate of this bug. ***
*** Bug 403263 has been marked as a duplicate of this bug. ***
*** Bug 403271 has been marked as a duplicate of this bug. ***
*** Bug 403497 has been marked as a duplicate of this bug. ***
*** Bug 404203 has been marked as a duplicate of this bug. ***
*** Bug 404287 has been marked as a duplicate of this bug. ***
*** Bug 404623 has been marked as a duplicate of this bug. ***
*** Bug 404702 has been marked as a duplicate of this bug. ***
*** Bug 404984 has been marked as a duplicate of this bug. ***
*** Bug 405145 has been marked as a duplicate of this bug. ***
*** Bug 405650 has been marked as a duplicate of this bug. ***
*** Bug 405665 has been marked as a duplicate of this bug. ***
*** Bug 405813 has been marked as a duplicate of this bug. ***
*** Bug 405585 has been marked as a duplicate of this bug. ***
*** Bug 406183 has been marked as a duplicate of this bug. ***
*** Bug 406313 has been marked as a duplicate of this bug. ***
*** Bug 406705 has been marked as a duplicate of this bug. ***
*** Bug 407652 has been marked as a duplicate of this bug. ***
*** Bug 408365 has been marked as a duplicate of this bug. ***
*** Bug 408420 has been marked as a duplicate of this bug. ***
*** Bug 408429 has been marked as a duplicate of this bug. ***
*** Bug 408686 has been marked as a duplicate of this bug. ***
*** Bug 408758 has been marked as a duplicate of this bug. ***
*** Bug 408763 has been marked as a duplicate of this bug. ***
*** Bug 408993 has been marked as a duplicate of this bug. ***
*** Bug 409315 has been marked as a duplicate of this bug. ***
*** Bug 409349 has been marked as a duplicate of this bug. ***
*** Bug 409353 has been marked as a duplicate of this bug. ***
*** Bug 409384 has been marked as a duplicate of this bug. ***
*** Bug 409744 has been marked as a duplicate of this bug. ***
*** Bug 410184 has been marked as a duplicate of this bug. ***
*** Bug 410195 has been marked as a duplicate of this bug. ***
*** Bug 410340 has been marked as a duplicate of this bug. ***
*** Bug 410388 has been marked as a duplicate of this bug. ***
*** Bug 410521 has been marked as a duplicate of this bug. ***
*** Bug 410513 has been marked as a duplicate of this bug. ***
*** Bug 411066 has been marked as a duplicate of this bug. ***
*** Bug 411183 has been marked as a duplicate of this bug. ***
162 duplicates so far, 47 in the last 30 days. This is a showstopper. Paolo, what are your plans for GNOME 2.18.0? Getting the workaround at comment 100 in? It would break the string freeze, in the worst case you could reuse the existing message "Unexpected error: %s" perhaps? *shrug* Please, do get this fixed for 2.18.0.
*** Bug 411559 has been marked as a duplicate of this bug. ***
I committed the patch in comment 100 after refactoring the code to reduce the number of operation done in the "critical section" where the signal is handled. To avoid string-freeze break, I left the generic error message. Let's hope this stop gap solution works well foe now. A different implementation of the file loader is still planned.
*** Bug 411530 has been marked as a duplicate of this bug. ***
*** Bug 411450 has been marked as a duplicate of this bug. ***
*** Bug 411451 has been marked as a duplicate of this bug. ***
*** Bug 411452 has been marked as a duplicate of this bug. ***
*** Bug 411453 has been marked as a duplicate of this bug. ***
Paolo, thanks for working around this. we'll see the results in the bug report feedback of the distros shipping 2.18.0... now time to take this bug off the showstoppers list that i will send out later today... ;-)
*** Bug 411733 has been marked as a duplicate of this bug. ***
*** Bug 411928 has been marked as a duplicate of this bug. ***
*** Bug 411926 has been marked as a duplicate of this bug. ***
Created attachment 83395 [details] [review] Committed fix (r5511)
Created attachment 83396 [details] [review] GNOME 2.14 backport
*** Bug 412383 has been marked as a duplicate of this bug. ***
*** Bug 412553 has been marked as a duplicate of this bug. ***
*** Bug 412600 has been marked as a duplicate of this bug. ***
Loïc: that patch works, but it's not all it was committed, http://svn.gnome.org/viewcvs/gedit/trunk/gedit/gedit-document-loader.c?r1=5474&r2=5510 This preparatory refactoring patch is needed to make sure the metadata read is done out of the section where the signal is handled
Created attachment 83460 [details] [review] Committed fix, take 2 (r5510 + r5511)
Created attachment 83461 [details] [review] GNOME 2.14 backport, take 2
*** Bug 413168 has been marked as a duplicate of this bug. ***
*** Bug 412884 has been marked as a duplicate of this bug. ***
*** Bug 412952 has been marked as a duplicate of this bug. ***
*** Bug 413302 has been marked as a duplicate of this bug. ***
*** Bug 413303 has been marked as a duplicate of this bug. ***
*** Bug 413410 has been marked as a duplicate of this bug. ***
*** Bug 413555 has been marked as a duplicate of this bug. ***
*** Bug 413614 has been marked as a duplicate of this bug. ***
*** Bug 414034 has been marked as a duplicate of this bug. ***
*** Bug 414408 has been marked as a duplicate of this bug. ***
*** Bug 415016 has been marked as a duplicate of this bug. ***
*** Bug 415213 has been marked as a duplicate of this bug. ***
*** Bug 415331 has been marked as a duplicate of this bug. ***
*** Bug 415437 has been marked as a duplicate of this bug. ***
*** Bug 415428 has been marked as a duplicate of this bug. ***
*** Bug 416242 has been marked as a duplicate of this bug. ***
*** Bug 416583 has been marked as a duplicate of this bug. ***
*** Bug 416594 has been marked as a duplicate of this bug. ***
*** Bug 417152 has been marked as a duplicate of this bug. ***
*** Bug 417700 has been marked as a duplicate of this bug. ***
*** Bug 418030 has been marked as a duplicate of this bug. ***
*** Bug 417860 has been marked as a duplicate of this bug. ***
*** Bug 418306 has been marked as a duplicate of this bug. ***
*** Bug 418957 has been marked as a duplicate of this bug. ***
*** Bug 419345 has been marked as a duplicate of this bug. ***
*** Bug 419576 has been marked as a duplicate of this bug. ***
*** Bug 419297 has been marked as a duplicate of this bug. ***
*** Bug 419842 has been marked as a duplicate of this bug. ***
*** Bug 419776 has been marked as a duplicate of this bug. ***
*** Bug 420004 has been marked as a duplicate of this bug. ***
*** Bug 420566 has been marked as a duplicate of this bug. ***
*** Bug 420764 has been marked as a duplicate of this bug. ***
*** Bug 421122 has been marked as a duplicate of this bug. ***
*** Bug 421225 has been marked as a duplicate of this bug. ***
*** Bug 422118 has been marked as a duplicate of this bug. ***
*** Bug 422219 has been marked as a duplicate of this bug. ***
*** Bug 421989 has been marked as a duplicate of this bug. ***
*** Bug 422542 has been marked as a duplicate of this bug. ***
*** Bug 423166 has been marked as a duplicate of this bug. ***
*** Bug 423167 has been marked as a duplicate of this bug. ***
*** Bug 423311 has been marked as a duplicate of this bug. ***
*** Bug 423388 has been marked as a duplicate of this bug. ***
*** Bug 423502 has been marked as a duplicate of this bug. ***
*** Bug 421374 has been marked as a duplicate of this bug. ***
*** Bug 424666 has been marked as a duplicate of this bug. ***
*** Bug 424560 has been marked as a duplicate of this bug. ***
*** Bug 425593 has been marked as a duplicate of this bug. ***
*** Bug 425713 has been marked as a duplicate of this bug. ***
*** Bug 425724 has been marked as a duplicate of this bug. ***
*** Bug 425938 has been marked as a duplicate of this bug. ***
*** Bug 426019 has been marked as a duplicate of this bug. ***
*** Bug 426084 has been marked as a duplicate of this bug. ***
*** Bug 426148 has been marked as a duplicate of this bug. ***
*** Bug 425099 has been marked as a duplicate of this bug. ***
*** Bug 426347 has been marked as a duplicate of this bug. ***
*** Bug 427291 has been marked as a duplicate of this bug. ***
*** Bug 427267 has been marked as a duplicate of this bug. ***
*** Bug 427284 has been marked as a duplicate of this bug. ***
*** Bug 425928 has been marked as a duplicate of this bug. ***
*** Bug 427080 has been marked as a duplicate of this bug. ***
*** Bug 426679 has been marked as a duplicate of this bug. ***
*** Bug 427558 has been marked as a duplicate of this bug. ***
*** Bug 427491 has been marked as a duplicate of this bug. ***
*** Bug 427634 has been marked as a duplicate of this bug. ***
*** Bug 427654 has been marked as a duplicate of this bug. ***
*** Bug 425038 has been marked as a duplicate of this bug. ***
*** Bug 428476 has been marked as a duplicate of this bug. ***
*** Bug 428501 has been marked as a duplicate of this bug. ***
*** Bug 428647 has been marked as a duplicate of this bug. ***
*** Bug 428645 has been marked as a duplicate of this bug. ***
OK, isn't this bug, like, fixed? :P
Jacob: yes it is, that's why there's a Status: RESOLVED Resolution: FIXED in the upper right corner. ;-)
Does it take this long for duplicate reports to stop flowing in?
*** Bug 428906 has been marked as a duplicate of this bug. ***
Jacob: Yes, especially when distros do not provide updated packages, and users do not install updates. :-)
*** Bug 429328 has been marked as a duplicate of this bug. ***
*** Bug 429459 has been marked as a duplicate of this bug. ***
*** Bug 429614 has been marked as a duplicate of this bug. ***
*** Bug 429778 has been marked as a duplicate of this bug. ***
*** Bug 429915 has been marked as a duplicate of this bug. ***
*** Bug 431122 has been marked as a duplicate of this bug. ***
*** Bug 431362 has been marked as a duplicate of this bug. ***
*** Bug 431594 has been marked as a duplicate of this bug. ***
*** Bug 431747 has been marked as a duplicate of this bug. ***
*** Bug 431822 has been marked as a duplicate of this bug. ***
*** Bug 431853 has been marked as a duplicate of this bug. ***
*** Bug 431914 has been marked as a duplicate of this bug. ***
*** Bug 432173 has been marked as a duplicate of this bug. ***
*** Bug 432806 has been marked as a duplicate of this bug. ***
*** Bug 432903 has been marked as a duplicate of this bug. ***
*** Bug 433174 has been marked as a duplicate of this bug. ***
*** Bug 433681 has been marked as a duplicate of this bug. ***
*** Bug 433762 has been marked as a duplicate of this bug. ***
*** Bug 434161 has been marked as a duplicate of this bug. ***
*** Bug 434298 has been marked as a duplicate of this bug. ***
*** Bug 434743 has been marked as a duplicate of this bug. ***
*** Bug 434699 has been marked as a duplicate of this bug. ***
*** Bug 435360 has been marked as a duplicate of this bug. ***
*** Bug 435228 has been marked as a duplicate of this bug. ***
*** Bug 436410 has been marked as a duplicate of this bug. ***
*** Bug 436411 has been marked as a duplicate of this bug. ***
*** Bug 437045 has been marked as a duplicate of this bug. ***
*** Bug 437063 has been marked as a duplicate of this bug. ***
*** Bug 436995 has been marked as a duplicate of this bug. ***
*** Bug 437125 has been marked as a duplicate of this bug. ***
*** Bug 437310 has been marked as a duplicate of this bug. ***
*** Bug 437413 has been marked as a duplicate of this bug. ***
*** Bug 437366 has been marked as a duplicate of this bug. ***
*** Bug 437357 has been marked as a duplicate of this bug. ***
*** Bug 438013 has been marked as a duplicate of this bug. ***
*** Bug 438497 has been marked as a duplicate of this bug. ***
*** Bug 438999 has been marked as a duplicate of this bug. ***
*** Bug 438994 has been marked as a duplicate of this bug. ***
*** Bug 438993 has been marked as a duplicate of this bug. ***
*** Bug 436451 has been marked as a duplicate of this bug. ***
*** Bug 439692 has been marked as a duplicate of this bug. ***
Removing a bunch of people from the cc list to cut down on bugzilla spam. If anyone is removed from this bug's cc that wanted to remain on the cc list, feel free to add yourself back.
How should I add myself without posting an entire new comment?
*** Bug 439851 has been marked as a duplicate of this bug. ***
*** Bug 440165 has been marked as a duplicate of this bug. ***
*** Bug 440313 has been marked as a duplicate of this bug. ***
*** Bug 440851 has been marked as a duplicate of this bug. ***
*** Bug 442274 has been marked as a duplicate of this bug. ***
*** Bug 443265 has been marked as a duplicate of this bug. ***
*** Bug 443299 has been marked as a duplicate of this bug. ***
*** Bug 443321 has been marked as a duplicate of this bug. ***
*** Bug 443531 has been marked as a duplicate of this bug. ***
*** Bug 444043 has been marked as a duplicate of this bug. ***
*** Bug 444573 has been marked as a duplicate of this bug. ***
*** Bug 445222 has been marked as a duplicate of this bug. ***
*** Bug 445886 has been marked as a duplicate of this bug. ***
*** Bug 445999 has been marked as a duplicate of this bug. ***
*** Bug 447278 has been marked as a duplicate of this bug. ***
*** Bug 449902 has been marked as a duplicate of this bug. ***
*** Bug 451657 has been marked as a duplicate of this bug. ***
*** Bug 451795 has been marked as a duplicate of this bug. ***
*** Bug 452033 has been marked as a duplicate of this bug. ***
*** Bug 452554 has been marked as a duplicate of this bug. ***
*** Bug 452456 has been marked as a duplicate of this bug. ***
*** Bug 452535 has been marked as a duplicate of this bug. ***
*** Bug 452781 has been marked as a duplicate of this bug. ***
*** Bug 453876 has been marked as a duplicate of this bug. ***
*** Bug 454399 has been marked as a duplicate of this bug. ***
*** Bug 454613 has been marked as a duplicate of this bug. ***
*** Bug 455020 has been marked as a duplicate of this bug. ***
*** Bug 457154 has been marked as a duplicate of this bug. ***
*** Bug 457163 has been marked as a duplicate of this bug. ***
*** Bug 457244 has been marked as a duplicate of this bug. ***
*** Bug 458354 has been marked as a duplicate of this bug. ***
*** Bug 458531 has been marked as a duplicate of this bug. ***
*** Bug 459510 has been marked as a duplicate of this bug. ***
*** Bug 460115 has been marked as a duplicate of this bug. ***
*** Bug 464001 has been marked as a duplicate of this bug. ***
*** Bug 465796 has been marked as a duplicate of this bug. ***
*** Bug 468593 has been marked as a duplicate of this bug. ***
*** Bug 467048 has been marked as a duplicate of this bug. ***
*** Bug 465498 has been marked as a duplicate of this bug. ***
*** Bug 463579 has been marked as a duplicate of this bug. ***
*** Bug 463264 has been marked as a duplicate of this bug. ***
*** Bug 475152 has been marked as a duplicate of this bug. ***
*** Bug 475670 has been marked as a duplicate of this bug. ***
*** Bug 476173 has been marked as a duplicate of this bug. ***
*** Bug 471142 has been marked as a duplicate of this bug. ***
*** Bug 479068 has been marked as a duplicate of this bug. ***
*** Bug 477611 has been marked as a duplicate of this bug. ***
*** Bug 480871 has been marked as a duplicate of this bug. ***