migrate_favorites.py crashed with OSError in _execute_child()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: unity
migrate_
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.2.0-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.37-7-generic i686
Architecture: i386
CompizPlugins: No value set for `/apps/
Date: Tue Nov 30 21:02:58 2010
ExecutablePath: /usr/lib/
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101130.1)
LiveMediaBuild_: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101130.1)
MachineType: ASUSTeK Computer Inc. F7Se
PciDisplay: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility Radeon HD 3400 Series [1002:95c4] (prog-if 00 [VGA controller])
ProcCmdline: /usr/bin/python /usr/lib/
ProcEnviron:
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: noprompt cdrom-detect/
ProcVersionSign
PythonArgs: ['/usr/
RelatedPackageV
xserver-xorg 1:7.5+6ubuntu3b1
libgl1-mesa-glx 7.9+repack-1ubuntu2
libdrm2 2.4.22-2ubuntu1
xserver-
xserver-
SourcePackage: unity
Title: migrate_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/
dmi.bios.date: 03/21/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 307
dmi.board.
dmi.board.name: F7Se
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: F7Se
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
glxinfo: Error: [Errno 2] No such file or directory
system: distro = Ubuntu, architecture = i686, kernel = 2.6.37-7-generic
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 #682314, 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.