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

Bug #861517 reported by Dražen Matešić
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-utils (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was using the log viewer to check what was going on with the system so i first opened 'messages' log after that 'syslog' and last i wanted to open 'kern.log' and at that time it crashed.

I can reproduce this bug..it crashes everytime i try to open 'kern.log'

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-system-log 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Wed Sep 28 17:33:11 2011
ExecutablePath: /usr/bin/gnome-system-log
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110719.2)
ProcCmdline: gnome-system-log
Signal: 6
SourcePackage: gnome-utils
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 free () from /lib/x86_64-linux-gnu/libc.so.6
Title: gnome-system-log crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (gwibber-service:1771): libindicate-WARNING **: Menu being changed when the indicator is visible. Listeners will NOT be notified of this change.

Revision history for this message
Dražen Matešić (crazylemon) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #818516, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
Revision history for this message
trollboy (trollboy) wrote : Hígh dåňgěř. Yøuř åccøuňt wås åttåckěd.
Download full text (4.2 KiB)

Hěllø!

Í åm å håcker whø hås åccess tø yøür øpěråtíng systěm.
Í ålsø håvě full åccěss tø yøür åccøüňt.

Í'vě běěn wåtchíng yøü før å fěw mønths nøw.
Thě fåct ís thåt yøü wěrě ínfěctěd wíth målwårě thrøügh ån ådült sítě thåt yøü vísítěd.

Íf yøü årě nøt fåmílíår wíth thís, Í wíll ěxplåín.
Trøjån Vírüs gívěs mě füll åccěss ånd cøntrøl øvěr å cømpütěr ør øthěr děvícě.
Thís měåns thåt Í cån sěě ěvěrythíng øn yøür scrěěn, türn øn thě cåměrå ånd mícrøphøně, büt yøü dø nøt knøw åbøüt ít.

Í ålsø håvě åccěss tø åll yøür cøntåcts ånd åll yøür cørrěspønděncě.

Why yøür åntívírüs díd nøt detěct målwårě?
Ånswěr: My målwårě üsěs thě drívěr, Í üpdåtě íts sígnåtürěs ěvěry 4 høürs sø thåt yøür åntívírüs ís sílěnt.

Í mådě å víděø shøwíng høw yøü såtísfy yøürsělf ín thě lěft hålf øf thě scrěěn, ånd ín thě ríght hålf yøü sěe thě víděø thåt yøü wåtchěd. Wíth øně clíck øf thě møüsě,
Í cån sěnd thís víděø tø åll yøür ěmåíls ånd cøntåcts øn søcíål nětwørks. Í cån ålsø pøst åccěss tø åll yøür ě-måíl cørrěspønděncě ånd měssěngěrs thåt yøü üsě.

Íf yøü wånt tø prěvěnt thís, trånsfěr thě åmøünt øf $850(USD) tø my bítcøín åddrěss (íf yøü dø nøt knøw høw tø dø thís, wrítě tø Gøøglě: 'Büy Bítcøín').

My bítcøín åddrěss (BŤC Wållět) ís: 1KVX9hCnQ9MfSoEFyxqAXGFXdTFNyzD22n

Åftěr rěcěívíng thě påyměnt, Í ...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments