[power]: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I was installing and the installer couldn't define the HDD to install. I had 3 HDD installed on the computer. One is running W7. The small one, 240Gb, was with U11.10 running. It did not try to install on it; it tried to install parallel to W7 with no other option. When I choose the U11.10 HDD to be the recepient it ask for repartition it; it was going back and forth and keep asking for the root. I took all partitions out and tried to let the installer choose its options. It did not. When I click on Quit to abort the installation and start from scratch, the installer crashed. Sorry I'm totally new to Ubuntu and Linux as well. Ubuntu has not been friendly at all setting up a network connection (wired, this is a desktop) or wireslly through my Linksys E3000 router and the PCs and Macs. Sorry, but Ubuntu sounds like a malfunction toy from my perspective. It is not intuitive and a lot of confusion is going on. i.e. there is no documentation addressing this issue; it seems more the issue from Ubuntu's perspective that issues are taking place in the wireless environment. It is not the case.
I'll appriciate any help. Thank you.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-
ProcVersionSign
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CasperVersion: 1.312
Date: Fri Mar 30 15:18:40 2012
ExecutablePath: /usr/lib/
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=
TERM=linux
PATH=(custom, no user)
LANG=
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-
Title: [power]: gnome-settings-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #968651, 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.