notify-osd crashed with signal 7
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Yet another andom bug. May have something to do with BleachBit. Running Precise development branch 64 bit with all the latest updates.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: notify-osd 0.9.34-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
Date: Sat Apr 14 20:46:14 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
ExecutableTimes
GtkTheme: Ambiance
IconTheme: ubuntu-mono-dark
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120320)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcCmdline: /usr/lib/
ProcCwd: /
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.6+12ubuntu1
libgl1-mesa-glx 8.0.2-0ubuntu3
libdrm2 2.4.32-1ubuntu1
xserver-
xserver-
Signal: 7
SourcePackage: notify-osd
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: notify-osd crashed with signal 7
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
WindowManager: No value set for `/desktop/
dmi.bios.date: 11/07/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.29
dmi.board.
dmi.board.name: 163D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 65.38
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
glxinfo: Error: [Errno 2] No such file or directory
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 #957886, 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.