reset-compiz-gconf crashed with GError in __main__: No D-BUS daemon running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
este erro apareceu após fazer upgrade para 12.04 através do 11.10
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-gnome 1:0.9.7.2-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-21-generic i686
.tmp.unity.
ApportVersion: 2.0-0ubuntu2
Architecture: i386
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
Date: Mon Apr 2 18:19:49 2012
DistUpgraded: 2012-04-02 18:17:51,318 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
ExecutableTimes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
InterpreterPath: /usr/bin/python2.7
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/bin/python /usr/lib/
ProcCwd: /home/fpssm
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: compiz
Title: reset-compiz-gconf crashed with GError in __main__: No D-BUS daemon running
UpgradeStatus: Upgraded to precise on 2012-04-02 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin mythtv nopasswdlogin plugdev sambashare
XorgConf:
Section "Device"
Identifier "Default Device"
Option "NoLogo" "True"
EndSection
dmi.bios.date: 08/27/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0702
dmi.board.
dmi.board.name: P5KPL-CM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.7.2-0ubuntu4
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.