[Bug 1237059] Re: dbus-daemon crashed with SIGSEGV

Unit 193 1237059 at bugs.launchpad.net
Wed Oct 9 00:32:03 UTC 2013


Ah, thanks for the pointers.

It's from kernel.org with custom config, also had tested the liquorix
kernel (http://liquorix.net/sources/)

During the upgrade, seems the saucy kernel was never pulled in, and as
I'm used to using my custom kernel all during Raring (issues with
-generic, checked randomly throughout the cycle) I may not have noticed
the generic kernel was still on 3.8.

In addition to that, seems the updated apparmor packages just came
through a few minutes ago, but guessing that's not the issue here.

Thanks for looking into this issue (and sorry about it!), do you know
when/if any patches will become part of upstream source?

** Changed in: dbus (Ubuntu)
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1237059

Title:
  dbus-daemon crashed with SIGSEGV

Status in “dbus” package in Ubuntu:
  Invalid

Bug description:
  Upgraded from Raring to Saucy, fully updated system.
  dbus: 1.6.12-0ubuntu8

  Symptom: When you first load the desktop all seems normal except you
  are unable to launch applications.  After rebooting into a known good
  kernel, I got an apport window.  After sending the bug data, no
  browser appears, unable to open one, a terminal, or anything else.
  Switching to a TTY and restarting dbus will give you the terminal and
  browser, but the rest of the desktop is black and the border themes
  are the basic theme.  At this point the desktop is still unusable.

  Expected: Fully functional desktop.

  Steps taken to repair:
  1. Reboot into a known working kernel.
  2. Clearing out old config/cache.
  3. Reinstalling dbus (apt-get install --reinstall.)
  4. Downgrading dbus-x11, dbus, libdbus-1-dev, and libdbus-1-3 to 1.6.12-0ubuntu7.
  Only the last step had any effect.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: dbus 1.6.12-0ubuntu8
  Uname: Linux 3.11.4-u193 i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Tue Oct  8 15:12:24 2013
  ExecutablePath: /bin/dbus-daemon
  ExecutableTimestamp: 1381192108
  InstallationDate: Installed on 2011-04-15 (906 days ago)
  InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413.2)
  MarkForUpload: True
  ProcCmdline: dbus-daemon --fork --session --address=unix:abstract=/tmp/dbus-noQydCFQad
  ProcCwd: /
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x804f3f3:	mov    0x8(%eax),%esi
   PC (0x0804f3f3) ok
   source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: dbus
  Stacktrace:
   #0  0x0804f3f3 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0xbff9adcc
  StacktraceTop: ?? ()
  ThreadStacktrace:
   .
   Thread 1 (LWP 4638):
   #0  0x0804f3f3 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0xbff9adcc
  Title: dbus-daemon crashed with SIGSEGV
  UpgradeStatus: Upgraded to saucy on 2013-10-08 (0 days ago)
  UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1237059/+subscriptions



More information about the foundations-bugs mailing list