After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 335148 - gnome-system-log crashes when a log is moved
gnome-system-log crashes when a log is moved
Status: RESOLVED OBSOLETE
Product: gnome-utils
Classification: Deprecated
Component: logview
2.16.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-19 18:19 UTC by Sebastien Bacher
Modified: 2007-07-23 14:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Sebastien Bacher 2006-03-19 18:19:04 UTC 
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/gnome-utils/+bug/35263

"version gnome-utils 2.14.0-0ubuntu1

gnome-system-log was running as background when it suddenly
crashed

/var/log/messages was open on log viewer.
...
> Thanks for your bug. The backtrace has not useful information. Could you rebuild a debug package of gnome-utils (https://wiki.ubuntu.com/DebuggingProgramCrash) to get a proper one? Have you find a way to get the issue or did it happen only once?
...
Sure, I'll try with debug build.

I did actually get crash for the second time by deleting and touching a monitored log file. I'll see if I manage to do it again.
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1223969088 (LWP 27609)]
0x0804ecfc in logview_update_statusbar (logview=0x80d6018) at log_repaint.c:180
180        size = gnome_vfs_format_file_size_for_display (log->stats->file_size);
(gdb) thread apply all bt

+ Trace 67057

Thread 1 (Thread -1223969088 (LWP 27609))

  • #0 logview_update_statusbar
    at log_repaint.c line 180
  • #1 logview_repaint
    at log_repaint.c line 488
  • #2 monitor_callback
    at monitor.c line 60
  • #3 gnome_vfs_stat_to_file_info
    from /usr/lib/libgnomevfs-2.so.0
  • #4 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #5 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #8 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 main
    at main.c line 203 



stacktrace was produced by

* opening gnome-sytem-log
* viewing file /var/log/messages (with monitoring enabled from menu)
* renaming /var/log/messages to /var/log/messages.old"
Comment 1 Sebastien Bacher 2006-07-20 08:33:33 UTC 
still happening with 2.15.4
Comment 2 Sebastien Bacher 2006-09-27 09:06:47 UTC 
still crashing with 2.16.0
Comment 3 Andrew Sayman 2007-01-17 04:48:18 UTC 
I haven't quite confirmed this bug, because I'm on a friend's computer. I looks solid though. It looks like putting something at monitor.c:59 like this would make it not crash:

  if (logview->curlog == log && event_type != GNOME_VFS_MONITOR_EVENT_DELETED)

That's just bold the log, and not try to update the status bar with file stats that don't exist.

I initially though just closing the log would be good, but do you really want to stop the display if the file has been deleted?
Comment 4 Sebastien Bacher 2007-07-23 14:05:35 UTC 
the bug submitter states it didn't happen for some time, closing for now