gnome-system-log crashed with SIGSEGV in g_closure_invoke()

[Savvas Radevic]

Binary package hint: gnome-utils

I clicked system > administration > system log, typed my password, read some log files.
Then I clicked File > Open and selected dpkg.log

(dpkg.log was already in the list)

I tried to reproduce it, but couldn't

ProblemType: Crash
Architecture: amd64
Date: Sun Oct 7 03:29:34 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gnome-system-log
NonfreeKernelModules: nvidia
Package: gnome-utils 2.20.0.1-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: gnome-system-log
ProcCwd: /home/forger
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-utils
StacktraceTop:
 ?? ()
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
Title: gnome-system-log crashed with SIGSEGV in g_closure_invoke()
Uname: Linux ubuntu 2.6.22-13-generic #1 SMP Thu Oct 4 17:52:26 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:logview_menus_set_state (logview=0x679000) at logview.c:276
logview_select_log (logview=0x679000, log=0x1) at logview.c:216
IA__g_closure_invoke (closure=0x86ef90, return_value=0x0, n_param_values=1,
signal_emit_unlocked_R (node=0x867d50, detail=0, instance=0x857540, emission_return=0x0,
IA__g_signal_emit_valist (instance=0x857540, signal_id=<value optimized out>, detail=0,

[Pedro Villavicencio (pedro)]

Thanks for your report, Does it happen again? I cannot reproduce this crash in my gutsy desktop. thanks

[Savvas Radevic (medigeek)]

Yes I reproduced it once more:
- open system log
- select dpkg.log
- from the menu: file > open dpkg.log
- nothing should happen
- select Xorg.0.log from the list
- then go file > open again
- select dpkg.log
- there should be a crash or forced closing of the system log viewer
Crashes every time

[Pedro Villavicencio (pedro)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=494240

[Savvas Radevic (medigeek)]

there's another way to crash the system log application, click on dpkg.log and then kern.log, then dpkg.log again.
I couldn't attach the crash report on gnome site, so I'll attach it here, I hope it's helpful.

[Sam_ (and-sam)]

Hi,
I've just send the apport crash log from var/crash. Its from the 14th and today the same.
From the GUI system log:
apport.log:
apport (pid 25634) Wed Apr 16 17:43:44 2008: apport: report /var/crash/_usr_bin_gnome-system-log.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS

What I did was two days ago and today, opening the GUI system log and selecting anything, e.g. syslog, kern.log, debug.log, after two different selectings the GUI just closed.
Two days ago I've removed vino, (don't need it, but was default with gutsy) and with no choice it also removed ubuntu-desktop. Also removed xsane and with no choice also removing hplip (don't have printer or scanner).

I don't have an idea if removing applications has something to do with that. I'm sorry in advance if this information is obsolet. Thank you.

[Sebastien Bacher (seb128)]

the bug should be fixed in the 2.25 version which will be uploaded to jaunty

[Sam_ (and-sam)]

Great job, thanks a lot.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-utils - 2.25.2-0ubuntu1

---------------
gnome-utils (2.25.2-0ubuntu1) jaunty; urgency=low

  * New upstream version

gnome-utils (2.25.1-0ubuntu1) jaunty; urgency=low

  * New upstream version:
    - Completely rewritten System Log Viewer (lp: #47134, #55512, #94489,
      #92575, #150056, #183615, #212380, #216377, #217605, #258729, #290053)
    Dictionary
    - Fix bug #454691 – Messages in the gnome-dictionary --help output
      are not all translated
    - Use the right order when passing arguments to PANEL_APPLET_BONOBO_FACTORY
    Floppy
    - Fix bug #565388 - Drop libgnome/libgnomeui dependency
    System Log Viewer
    - Merged the rewrite to trunk.
    - Bug #375684 - Rename the menu item to read a more descriptive
      "Log File Viewer"
  * debian/control.in:
    - updated build-depends to the new version requirements
  * debian/patches/01_lpi.patch:
    - new version update
  * debian/patches/02_autoconf.patch:
    - new version update
  * debian/patches/04_menu_changes.patch:
    - new version update
  * debian/patches/05_handle_signals.patch:
    - the code has been rewritten in the new version

gnome-utils (2.25.0-0ubuntu1) jaunty; urgency=low

  * New upstream version:
    Baobab
    - Fix bug #561257 - Use single GTK+ include
    - Root partition cannot be unselected
    - Plug a mem leak
    - Drop libgnome dependency (#557264)
    - Fix bug #557226 - Do not scan /sys
    Dictionary
    - Remove libgnome/libgnomeui dependency (#563970)
    - Fix bug #561257 - Use single GTK+ include
    - Fix bug #558980 - gnome-dictionary desktop file hardcodes icon extension
    Floppy
    - Nothing
    Screenshot
    - Plug memory leaks
    - Set a meaningful title for the interactive dialog (lp: #200872)
    - Fix the mouse cursor overlay when not in fullscreen mode (lp: #310771)
    - Always use the delay command line argument if present
    - Move the "Copy to Clipboard" button as per HIG
    - Drop libgnomeui dependency
    Search Tool
    - Fix bug #561257 - Use single GTK+ include
    System Log Viewer
    - Start some clean up of the code base to bring it to the XXI century
  * debian/control.in:
    - updated gtk requirement
  * debian/patches/01_logview_gksu.patch:
    - don't use gksu that's not required (lp: #314039)
  * debian/patches/01_lpi.patch:
    - new version update
  * debian/patches/02_autoconf.patch:
    - new version update

 -- Sebastien Bacher <email address hidden> Fri, 09 Jan 2009 14:38:45 +0100

[Savvas Radevic (medigeek)]

Sebastien, is this tested or should we test it?

[Sebastien Bacher (seb128)]

the code got rewritten so it's not likely that the new code has the same issues, you can give it some testing though and open new bugs if required

[Savvas Radevic (medigeek)]

> you can give it some testing though and open new bugs if
> required

Will do, once jaunty alpha 4 is out! :)