after login, xorg error happens almost everytime
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Error "xorg crashed with sigabrt in osabort()" happens after login, when I under nvidia-384 driver.
I now use nvidia driver-384 and get this error. I can't install more new driver (nvidia-390) coz then, after login, system totally freezes completely -only mouse coursor (it moves) and desktop wallpaper will exist.
Xubuntu 16.04
Nvidia Geforce 1050
Display - LG TV
lsb_release -rd:
Description: Ubuntu 16.04.4 LTS
Release: 16.04
apt-cache policy pkgname:
N: Не удалось найти пакет pkgname [couldnt find pkgname]
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSign
Uname: Linux 4.13.0-38-generic x86_64
NonfreeKernelMo
.proc.driver.
.proc.driver.
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.130 Wed Mar 21 03:37:26 PDT 2018
GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~
.proc.driver.
Your system is not currently configured to drive a VGA console
on the primary VGA device. The NVIDIA Linux graphics driver
requires the use of a text-mode VGA console. Use of other console
drivers including, but not limited to, vesafb, may result in
corruption and stability problems, and is not supported.
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: None
Date: Mon Apr 9 15:39:04 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.8, 4.13.0-37-generic, x86_64: installed
bbswitch, 0.8, 4.13.0-38-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-119-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-89-generic, x86_64: installed
nvidia-384, 384.130, 4.13.0-38-generic, x86_64: installed
ExtraDebuggingI
GraphicsCard:
NVIDIA Corporation Device [10de:1c81] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:85d7]
InstallationDate: Installed on 2017-06-21 (292 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
MachineType: System manufacturer System Product Name
ProcEnviron:
LANGUAGE=ru
PATH=(custom, no user)
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0606
dmi.board.
dmi.board.name: P8B75-M LX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Mon Apr 9 15:34:49 2018
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
input Power Button KEYBOARD, id 6
input Power Button KEYBOARD, id 7
input PixArt USB Optical Mouse MOUSE, id 8
input Eee PC WMI hotkeys KEYBOARD, id 9
input AT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.19.
description: | updated |
summary: |
- after login, error happens almost everytime + after login, xorg error happens almost everytime |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https:/ /errors. ubuntu. com/user/ ID where ID is the content of file /var/lib/ whoopsie/ whoopsie- id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.
3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.
Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.