Ubuntu
gnome-system-log package

gnome-system-log crashed with SIGSEGV

Bug #1231439 reported by Thaddaeus Tintenfisch on 2013-09-26

74

This bug affects 16 people

Affects		Status	Importance	Assigned to	Milestone
	gnome-system-log (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

crash during application launch

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-system-log 3.8.1-1svn1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 2.12.4-0ubuntu1
Architecture: i386
Date: Thu Sep 26 15:02:51 2013
ExecutablePath: /usr/bin/gnome-system-log
InstallationDate: Installed on 2013-09-21 (4 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130920)
MarkForUpload: True
ProcCmdline: /usr/bin/gnome-system-log
SegvAnalysis:
Segfault happened at: 0xb7386072: mov (%eax),%edx
PC (0xb7386072) ok
source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-system-log
StacktraceTop:
?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
Title: gnome-system-log crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount) wrote on 2013-09-26:

#1

Dependencies.txt Edit (5.6 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (600 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (305 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (23.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (812 bytes, text/plain; charset="utf-8")
Registers.txt Edit (499 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (6.0 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Apport retracing service (apport) wrote on 2013-09-26: Stacktrace.txt

#3

Stacktrace.txt Edit (11.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-09-26: StacktraceSource.txt

#4

StacktraceSource.txt Edit (9.6 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-09-26: StacktraceTop.txt

#5

StacktraceTop.txt Edit (1.2 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-09-26: ThreadStacktrace.txt

#6

ThreadStacktrace.txt Edit (16.0 KiB, text/plain)

Changed in gnome-system-log (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-09-28:

#7

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-system-log (Ubuntu):
status:	New → Confirmed

Revision history for this message

Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount) wrote on 2013-10-31:

#8

The Gtk+ themes from Shimmer Project (Greybird, Bluebird, Numix,...) prevent gnome-system-log from launching properly.

(gnome-system-log:1234): Gtk-CRITICAL **: _gtk_css_rgba_value_get_rgba: assertion 'rgba->class == &GTK_CSS_VALUE_RGBA' failed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-10-31:

#9

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in shimmer-themes (Ubuntu):
status:	New → Confirmed

Revision history for this message

Satyajit Sahoo (satyajit-happy) wrote on 2013-10-31:

#10

It looks like that GTK fails to get a color value from the theme. It also happens with Zukitwo.

I cannot find any error in the theme files. Even if there are errors, CSS errors should be ignored. At least that's the expected behavior. So I guess, it's rather a bug in GTK or gnome-system-log. I cannot confirm though.

Anyways, I'm now on GTK3.10 and the bug doesn't happen. So the bug might be a regression in GTK3.8 and it has been fixed in GTK3.10.

Alberto Salvia Novella (es20490446e) on 2014-01-27

Changed in shimmer-themes (Ubuntu):
importance:	Undecided → Medium

Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount) on 2014-02-17

no longer affects:

shimmer-themes (Ubuntu)

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.