Ubuntu
gnome-system-log package

gnome-system-log crashed with SIGABRT in g_assertion_message()

Bug #1162390 reported by kylea on 2013-03-31

20

This bug affects 3 people

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

Bug Description

Not sure - started gnome-system-log from a script

Linux kylea-hpxt 3.8.0-14-generic #24-Ubuntu SMP Fri Mar 22 19:45:03 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-system-log 3.6.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
Uname: Linux 3.8.0-14-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Sun Mar 31 11:38:27 2013
ExecutablePath: /usr/bin/gnome-system-log
InstallationDate: Installed on 2013-03-22 (8 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130319)
MarkForUpload: True
ProcCmdline: gnome-system-log
Signal: 6
SourcePackage: gnome-system-log
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
Title: gnome-system-log crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo vboxusers

Tags:

Revision history for this message

kylea (kylea) wrote on 2013-03-31:

#1

Dependencies.txt Edit (5.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (863 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (311 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (47.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (835 bytes, text/plain; charset="utf-8")
Registers.txt Edit (661 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (3.6 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (15.3 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Apport retracing service (apport) wrote on 2013-03-31: Stacktrace.txt

#3

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

Revision history for this message

Apport retracing service (apport) wrote on 2013-03-31: StacktraceSource.txt

#4

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

Revision history for this message

Apport retracing service (apport) wrote on 2013-03-31: StacktraceTop.txt

#5

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

Revision history for this message

Apport retracing service (apport) wrote on 2013-03-31: ThreadStacktrace.txt

#6

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

Changed in gnome-system-log (Ubuntu):
importance:	Undecided → Medium
summary:	- gnome-system-log crashed with SIGABRT in raise() + gnome-system-log crashed with SIGABRT in g_assertion_message()
tags:	removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-03-26:

#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

corrado venturini (corradoventu) wrote on 2017-02-22:

#8

I have this bug on Ubuntu Zesty 17.04
corrado@corrado-z2:~$ inxi -Fx
System: Host: corrado-z2 Kernel: 4.10.0-8-generic x86_64 (64 bit gcc: 6.3.0)
           Desktop: Gnome (Gtk 3.22.7-1ubuntu4)
           Distro: Ubuntu Zesty Zapus (development branch)
Machine: Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x
           UEFI: American Megatrends v: F3 date: 04/24/2013
CPU: Dual core Intel Core i3-4130 (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13567
           clock speeds: max: 3400 MHz 1: 3386 MHz 2: 3103 MHz 3: 1710 MHz
           4: 3267 MHz
Graphics: Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller
           bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1680x1050@59.88hz
           GLX Renderer: Mesa DRI Intel Haswell
           GLX Version: 3.0 Mesa 17.0.0 Direct Rendering: Yes
Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.10.0-8-generic
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
           IF: enp2s0 state: up speed: 100 Mbps duplex: full
           mac: 94:de:80:7e:90:a7
Drives: HDD Total Size: 1000.2GB (6.8% used)
           ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 32G used: 8.7G (30%) fs: ext4 dev: /dev/sda4
           ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C
           Fan Speeds (in rpm): cpu: N/A
Info: Processes: 220 Uptime: 1:38 Memory: 1694.6/7861.2MB
           Init: systemd runlevel: 5 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.51) inxi: 2.3.8
corrado@corrado-z2:~$

I have this bug on Ubuntu Zesty 17.04 
corrado@corrado-z2:~$ inxi -Fx
System:    Host: corrado-z2 Kernel: 4.10.0-8-generic x86_64 (64 bit gcc: 6.3.0)
           Desktop: Gnome  (Gtk 3.22.7-1ubuntu4)
           Distro: Ubuntu Zesty Zapus (development branch)
Machine:   Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x
           UEFI: American Megatrends v: F3 date: 04/24/2013
CPU:       Dual core Intel Core i3-4130 (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13567
           clock speeds: max: 3400 MHz 1: 3386 MHz 2: 3103 MHz 3: 1710 MHz
           4: 3267 MHz
Graphics:  Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller
           bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1680x1050@59.88hz
           GLX Renderer: Mesa DRI Intel Haswell
           GLX Version: 3.0 Mesa 17.0.0 Direct Rendering: Yes
Audio:     Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.10.0-8-generic
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
           IF: enp2s0 state: up speed: 100 Mbps duplex: full
           mac: 94:de:80:7e:90:a7
Drives:    HDD Total Size: 1000.2GB (6.8% used)
           ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 32G used: 8.7G (30%) fs: ext4 dev: /dev/sda4
           ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 220 Uptime: 1:38 Memory: 1694.6/7861.2MB
           Init: systemd runlevel: 5 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.51) inxi: 2.3.8 
corrado@corrado-z2:~$

Revision history for this message

corrado venturini (corradoventu) wrote on 2017-02-22:

#9

_usr_bin_gnome-system-log.1000.crash Edit (2.2 MiB, text/plain)

adding crash report ...

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.