when the system was opening :systemd-journald crashed with SIGSEGV in __find_specmb()

Bug #1436694 reported by riosaeba
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I have opened xubuntu than i have seen 4 windows alert. I have closed 3 of 4 than cliched one of them and report this.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu9
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu4
Architecture: i386
Date: Wed Mar 25 18:12:17 2015
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2014-12-21 (94 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
MachineType: ASUSTeK Computer INC. 1015PW
ProcCmdline: /lib/systemd/systemd-journald
ProcEnviron:
 LANG=it_IT.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=4d7cab7b-ad63-4fe0-985f-dfb06a812a95 ro quiet splash vt.handoff=7
Signal: 11
SourcePackage: systemd
StacktraceTop:
 __find_specmb (format=0xb77a4f69 "%s: IO error, rotating.") at printf-parse.h:108
 _IO_vfprintf_internal (s=0xbff08500, format=0xb77a4f69 "%s: IO error, rotating.", ap=0xbff08eb8 "X\217\351\270\332!x\267\b}{\267\373\377\377\377\t") at vfprintf.c:1315
 ___vsnprintf_chk (s=0xbff0863c "", maxlen=<optimized out>, flags=1, slen=2048, format=0xb77a4f69 "%s: IO error, rotating.", args=0xbff08eb8 "X\217\351\270\332!x\267\b}{\267\373\377\377\377\t") at vsnprintf_chk.c:63
 ?? ()
 ?? ()
Title: systemd-journald crashed with SIGSEGV in __find_specmb()
UpgradeStatus: Upgraded to vivid on 2015-03-18 (7 days ago)
UserGroups:

dmi.bios.date: 05/06/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1015PE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd05/06/2011:svnASUSTeKComputerINC.:pn1015PW:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1015PW
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
riosaeba (papparappappa) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __find_specmb (format=0xb77a4f69 "%s: IO error, rotating.") at printf-parse.h:108
 _IO_vfprintf_internal (s=0xbff08500, format=0xb77a4f69 "%s: IO error, rotating.", ap=0xbff08eb8 "X\217\351\270\332!x\267\b}{\267\373\377\377\377\t") at vfprintf.c:1315
 ___vsnprintf_chk (s=0xbff0863c "", maxlen=<optimized out>, flags=1, slen=2048, format=0xb77a4f69 "%s: IO error, rotating.", args=0xbff08eb8 "X\217\351\270\332!x\267\b}{\267\373\377\377\377\t") at vsnprintf_chk.c:63
 vsnprintf () at /usr/include/i386-linux-gnu/bits/stdio2.h:77
 log_internalv (level=4, error=0, file=0xb77a27a4 "../src/journal/journald-server.c", line=479, func=0xb77a52f1 <__func__.14752> "shall_try_append_again", format=0xb77a4f69 "%s: IO error, rotating.", ap=0xbff08eb8 "X\217\351\270\332!x\267\b}{\267\373\377\377\377\t") at ../src/shared/log.c:657

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in systemd (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
information type: Private → Public
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

This was a in-development Ubuntu 15.04 release and systemd has seen upgrades since then. Have you been able to reproduce it since then?

Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

Changed in systemd (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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