Computer hangs on boot for 2min with error code 99
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Computer works with windows without problems.
As soon as I install Ubuntu the PC hangs on booting.It stops for 2 min with error code 99 on boot up.(I have an dual boot system)Then when I boot up in Windows there is an error message in the device manager with an usb error.
When I boot in ubuntu there is also an error message saying the system has an error(dont remember the excatly name).
this error dissapears only if I shut down the power completly.
Tried out ubuntu 15.04,mint 17.3,ubuntu mate 15.10 ,ubuntu 16.04 beta 2
have installed nvidia proprietary drivers.
system : asrock x99x killer
inter wlan card intel wireless n 7260 desktop
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-settings-
Uname: Linux 4.5.0-040500-
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 14 20:27:11 2016
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2016-04-11 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=de_DE.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7f1368114e69 <up_exported_
PC (0x7f1368114e69) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-settings-
StacktraceTop:
up_exported_
gsd_power_
?? () from /usr/lib/
gnome_
?? ()
Title: unity-settings-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
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 #1546641, 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.