GNOME Bugzilla – Bug 364106
crash in System Log: string_get_date_string() at logrtns.c:136
Last modified: 2008-08-25 10:51:19 UTC
Version: 2.16.1 What were you doing when the application crashed? start this application Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 29827072 vsize: 0 resident: 29827072 share: 0 rss: 11333632 rss_rlim: 0 CPU usage: start_time: 1161504942 rtime: 0 utime: 25 stime: 0 cutime:24 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-log' (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 -1224951616 (LWP 5607)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 77627
Thread 1 (Thread -1224951616 (LWP 5607))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Hopefully that is what you need. Greetings. Backtrace was generated from '/usr/bin/gnome-system-log' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225189184 (LWP 6910)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 77660
Thread 1 (Thread -1225189184 (LWP 6910))
hi konzentrat, the stacktrace looks good, thanks! :-) confirming the bug.
*** Bug 364202 has been marked as a duplicate of this bug. ***
*** Bug 364869 has been marked as a duplicate of this bug. ***
*** Bug 362606 has been marked as a duplicate of this bug. ***
*** Bug 355557 has been marked as a duplicate of this bug. ***
*** Bug 367182 has been marked as a duplicate of this bug. ***
*** Bug 365444 has been marked as a duplicate of this bug. ***
*** Bug 368351 has been marked as a duplicate of this bug. ***
*** Bug 370382 has been marked as a duplicate of this bug. ***
*** Bug 377038 has been marked as a duplicate of this bug. ***
Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/gnome-utils/+bug/69622
*** Bug 378909 has been marked as a duplicate of this bug. ***
*** Bug 379636 has been marked as a duplicate of this bug. ***
*** Bug 380139 has been marked as a duplicate of this bug. ***
*** Bug 381258 has been marked as a duplicate of this bug. ***
*** Bug 382448 has been marked as a duplicate of this bug. ***
*** Bug 383231 has been marked as a duplicate of this bug. ***
*** Bug 383223 has been marked as a duplicate of this bug. ***
*** Bug 383990 has been marked as a duplicate of this bug. ***
*** Bug 387957 has been marked as a duplicate of this bug. ***
*** Bug 388651 has been marked as a duplicate of this bug. ***
*** Bug 389598 has been marked as a duplicate of this bug. ***
*** Bug 389696 has been marked as a duplicate of this bug. ***
*** Bug 390130 has been marked as a duplicate of this bug. ***
*** Bug 390519 has been marked as a duplicate of this bug. ***
*** Bug 390704 has been marked as a duplicate of this bug. ***
*** Bug 391766 has been marked as a duplicate of this bug. ***
*** Bug 396676 has been marked as a duplicate of this bug. ***
*** Bug 398976 has been marked as a duplicate of this bug. ***
*** Bug 399585 has been marked as a duplicate of this bug. ***
*** Bug 400083 has been marked as a duplicate of this bug. ***
*** Bug 403675 has been marked as a duplicate of this bug. ***
*** Bug 394478 has been marked as a duplicate of this bug. ***
*** Bug 403361 has been marked as a duplicate of this bug. ***
*** Bug 406676 has been marked as a duplicate of this bug. ***
*** Bug 406883 has been marked as a duplicate of this bug. ***
*** Bug 408738 has been marked as a duplicate of this bug. ***
bug 364106, bug 374663, bug 366458 seem to share the same traces
*** Bug 409797 has been marked as a duplicate of this bug. ***
*** Bug 412747 has been marked as a duplicate of this bug. ***
*** Bug 413747 has been marked as a duplicate of this bug. ***
*** Bug 414671 has been marked as a duplicate of this bug. ***
*** Bug 415204 has been marked as a duplicate of this bug. ***
*** Bug 417454 has been marked as a duplicate of this bug. ***
*** Bug 417544 has been marked as a duplicate of this bug. ***
*** Bug 417721 has been marked as a duplicate of this bug. ***
*** Bug 418831 has been marked as a duplicate of this bug. ***
*** Bug 420093 has been marked as a duplicate of this bug. ***
*** Bug 420838 has been marked as a duplicate of this bug. ***
launchad has a GNOME 2.18.0 duplicate
*** Bug 421163 has been marked as a duplicate of this bug. ***
*** Bug 421254 has been marked as a duplicate of this bug. ***
*** Bug 419852 has been marked as a duplicate of this bug. ***
*** Bug 422365 has been marked as a duplicate of this bug. ***
*** Bug 422686 has been marked as a duplicate of this bug. ***
*** Bug 422688 has been marked as a duplicate of this bug. ***
*** Bug 422690 has been marked as a duplicate of this bug. ***
*** Bug 422710 has been marked as a duplicate of this bug. ***
*** Bug 422786 has been marked as a duplicate of this bug. ***
*** Bug 422792 has been marked as a duplicate of this bug. ***
*** Bug 422900 has been marked as a duplicate of this bug. ***
*** Bug 423359 has been marked as a duplicate of this bug. ***
*** Bug 424282 has been marked as a duplicate of this bug. ***
*** Bug 424968 has been marked as a duplicate of this bug. ***
*** Bug 425696 has been marked as a duplicate of this bug. ***
*** Bug 426261 has been marked as a duplicate of this bug. ***
*** Bug 366458 has been marked as a duplicate of this bug. ***
*** Bug 374663 has been marked as a duplicate of this bug. ***
*** Bug 422773 has been marked as a duplicate of this bug. ***
*** Bug 427129 has been marked as a duplicate of this bug. ***
*** Bug 427442 has been marked as a duplicate of this bug. ***
*** Bug 428441 has been marked as a duplicate of this bug. ***
the useful trace in comment 2 is the same as in https://launchpad.net/ubuntu/+source/gnome-utils/+bug/69622 . 169 dups, 107 in the last 30 days. gnome 2.18.x blocker.
*** Bug 428667 has been marked as a duplicate of this bug. ***
*** Bug 428738 has been marked as a duplicate of this bug. ***
*** Bug 428741 has been marked as a duplicate of this bug. ***
in gnome-utils/logview/logrtns.c:252 while (newdate == NULL && !done) { i++; date_string = string_get_date_string (buffer_lines[i]); Isn't that i++ wrong? I don't quite get the code of the file but I guess that if you always add 1 to 'i' under some circumstance you'll get an out of range error. Just a guess, I'm no hardcore hacker.
Created attachment 86331 [details] [review] Add check for i < n-1 if no date string is found. Proposed Fix.
thanks jan; the patch looks fine. someone experiencing this bug can try with jan's patch and see if it fixes the issue? if I get some feedback I'll apply it to the stable branch and release a 2.18.1 version of gnome-utils.
I used the attached log file at bug 374663 as test case.
(In reply to comment #82) > I used the attached log file at bug 374663 as test case. okay then. :-) patch applied to trunk and gnome-2-18 branches, will release ASAP. again, thanks for your patch!
Who has reviewed this patch ? AFAICS, it just breaks the loop. All the ways, the code below that check is never run.
(In reply to comment #84) > Who has reviewed this patch ? > AFAICS, it just breaks the loop. All the ways, the code below that check is > never run. I reviewed the patch and tested it, and it showed no regressions. if the counter reaches the sentinel, then there's no point in looking any further, which is correct. the whole code in that section needs refactoring, but that is a task for the unstable branch.
0k thanks
Reply to comment #84: The code below that check is run if date_string != NULL.
Oh right, nice obfuscation :)
*** Bug 429145 has been marked as a duplicate of this bug. ***
*** Bug 429531 has been marked as a duplicate of this bug. ***
*** Bug 429633 has been marked as a duplicate of this bug. ***
*** Bug 432794 has been marked as a duplicate of this bug. ***
*** Bug 432944 has been marked as a duplicate of this bug. ***
*** Bug 439752 has been marked as a duplicate of this bug. ***
*** Bug 441392 has been marked as a duplicate of this bug. ***
*** Bug 442520 has been marked as a duplicate of this bug. ***
*** Bug 446867 has been marked as a duplicate of this bug. ***
*** Bug 446860 has been marked as a duplicate of this bug. ***
*** Bug 446846 has been marked as a duplicate of this bug. ***
*** Bug 448446 has been marked as a duplicate of this bug. ***
*** Bug 448445 has been marked as a duplicate of this bug. ***
*** Bug 447874 has been marked as a duplicate of this bug. ***
*** Bug 452610 has been marked as a duplicate of this bug. ***
*** Bug 457261 has been marked as a duplicate of this bug. ***
*** Bug 463211 has been marked as a duplicate of this bug. ***
*** Bug 463026 has been marked as a duplicate of this bug. ***
*** Bug 463872 has been marked as a duplicate of this bug. ***
*** Bug 468615 has been marked as a duplicate of this bug. ***
*** Bug 461967 has been marked as a duplicate of this bug. ***
*** Bug 464232 has been marked as a duplicate of this bug. ***
*** Bug 468783 has been marked as a duplicate of this bug. ***
*** Bug 470079 has been marked as a duplicate of this bug. ***
*** Bug 473478 has been marked as a duplicate of this bug. ***
*** Bug 474293 has been marked as a duplicate of this bug. ***
(In reply to comment #114) > *** Bug 474293 has been marked as a duplicate of this bug. *** > Alright, Bugzilla for non IT experts. What am I supposed to do with the patch, where, what directory, terminal?? Don't make it so hard for Linux Newbies, please. Everyone has to start at some point. Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/gnome-utils/+bug/69622 Now should I follow the Ubuntu Steps? Or patch my forehead with the attachment at the bottom of this page????? Thank you, Thomas
Hi Thomas, *if* you compile from source (read: if you are an IT expert), you can apply the patch. If you are normal user, the easiest way is to update to a recent version that includes this patch, for example GNOME 2.18. GNOME 2.18 is included in Fedora 7.
the only thing I compiled so far, was Quanta via Fink in Darwin, speaking OSX, actually I was surprised to find it working. I cannot upgrade to Fedora 7, the CD media check gives me an error and lectures me that my CPU doesn't support "slow mode" or long mode, dunno anymo (i386, yep). It's a Pentium III, well Dual, but mmppf. ok, I'll try to shoot that Gnome 2.18 into my system and let y'all know. Vielen Dank, Thomas
Lost again, I visited the Gnome web site, well, there is 2.18 Live CD and other stuff, what am I supposed to do?
again: you are running fedora 6 which provides gnome 2.16. the easiest way for you: gnome 2.18 and a fix for this problem here are included in Fedora 7, so upgrade to fedora 7. perhaps some volunteers have also packaged some gnome 2.18 packages for fedora 6, but this is definitely a question for your distribution. the hard way would be: compile the whole gnome 2.18 stack on your own (i wouldn't recommend that to an average user). if you want to compile GNOME yourself, you can use GARNOME for example.
well, I understood the thing with Fedora 7. But perhaps I made it not clear enough on my end: I cannot run Fedora 7, and I am talking about the 386 32 bit version. No one out there seems to believe me: I get a media error and it tells me something in my CPU does not support long or slow mode or whatever. BTW, I had no chance to install Ubuntu, Suse 10.2, or Debian. Only Fedora 6 and below works. Now on what: It's a dual server board, 2x Pentium III, 866Mhz, 512MB Ram, no AGP support, hence Graphics via PCI, should be enough, or not? I read the specs for all the other distro, but nope. I guess I simply won't have a system log than, I dunno what to do with it anyway, LOL. I have Fedora 7 on another sytems, same DVD that gives me an error on PC1 worked fine on PC (an HP Pavillion). hmm, is there something in the MB Bios I need to know?!? Sorry, if this is not the place for it, but I really appreciate your efforts to help me. Garnome, ..., I'll look at it, but well I am sure I don't know enough about all this ...
Just had a thought, I have an older FC6 installation on a different hard drive. Could I just find the file that's doing 'it' and replace the bugged one? Getting creative here .... but hey, which file is it??
I found this here, couldn't I take those files from my other FC6 installation and copy them? http://linux.die.net/man/1/gnome-system-log Files /var/log/messages The system's main logfile. /etc/syslog.conf Configuration file for syslogd. See syslog.conf(5) for exact information.
no, you can't just replace the file, and i already told you what's possible. if you can't upgrade to a newer version it means that you can't upgrade and won't receive a fix for this issue.
*** Bug 483079 has been marked as a duplicate of this bug. ***
*** Bug 483616 has been marked as a duplicate of this bug. ***
*** Bug 490808 has been marked as a duplicate of this bug. ***
*** Bug 492710 has been marked as a duplicate of this bug. ***
*** Bug 499684 has been marked as a duplicate of this bug. ***
*** Bug 520027 has been marked as a duplicate of this bug. ***