reset-compiz-gconf crashed with GError in __main__: No D-BUS daemon running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
One of the many compiz crashes I'm seeing
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.8.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-20-generic x86_64
.tmp.unity.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Thu Mar 29 07:27:04 2012
DistUpgraded: 2012-01-18 14:21:54,170 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110824)
InterpreterPath: /usr/bin/python2.7
MachineType: CLEVO CO. W150HNM/W170HN
ProcCmdline: /usr/bin/python /usr/lib/
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: unity
Title: reset-compiz-gconf crashed with GError in __main__: No D-BUS daemon running
UpgradeStatus: Upgraded to precise on 2012-01-18 (70 days ago)
UserGroups: adm admin lpadmin sambashare vboxusers
dmi.bios.date: 05/09/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: HR_2.1.0.128 X64
dmi.board.
dmi.board.name: W150HNM/W170HN
dmi.board.vendor: CLEVO CO.
dmi.board.version: D03
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: CLEVO CO.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: W150HNM/W170HN
dmi.product.
dmi.sys.vendor: CLEVO CO.
version.compiz: compiz 1:0.9.7.2-0ubuntu4
version.ia32-libs: ia32-libs 20090808ubuntu35
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #965998, 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.