Xorg crashed with SIGABRT after lockscreen

Bug #1298650 reported by Lázaro Zarê
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I'm having problems with the new lock screen of Ubuntu.
Every time the pc goes into idle and the screen is locked (hence the monitor is blanked as usual) and when I try to put my password, the Gnome lock screen appear mixed the new unity lock screen and the the screen freezes and the computer needs force reboot..
I took a picture of the bug.
Because this, I switched in compizconfig-settings-manager >>Ubuntu unity Plugin>>General>Lockscreen lightdm instead of Unity.
After that in the first time when screen locks, xorg crashed(and rapdly restarted) ocasioning this bug report

Sorry for my very Bad English

Porguguese version:
Estou tendo problemas com a nova tela de bloqueio do Ubuntu.
Toda vez que o pc entra em inatividade e a tela é bloqueada(consequentemente o monitor é apagado como de costume) e quando tento colocar minha senha , ao invés de aparecer a nova tela de bloqueio aparece a tela de bloqueio do Gnome e a tela congela e o computador precisa de uma reinicialização forçada.
Eu tirei uma foto do bug.
Por conta disso, eu troquei a configuração em compizconfig-settings-manager >>Ubuntu unity Plugin>>General>Lockscreen para lightdm ao invés de Unity.
Depois disso, na primeira vez que a tela foi bloqueada, o xorg travou(e rapidamente reiniciou) ocasionando esse relatorio de erro.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-core 2:1.15.0-1ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Thu Mar 27 18:12:16 2014
Disassembly: Nenhuma tabela de símbolos está carregada. Use o comando "file".
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 fglrx, 13.350, 3.13.0-19-generic, x86_64: installed
 virtualbox, 4.3.6, 3.13.0-19-generic, x86_64: installed
ExecutablePath: /usr/bin/Xorg
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:1482]
InstallationDate: Installed on 2014-03-24 (3 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140322)
ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=0b954742-bc59-4bb8-82c4-7c32ced0a042 ro quiet splash
Signal: 6
SourcePackage: fglrx-installer
Stacktrace: Nenhuma tabela de símbolos está carregada. Use o comando "file".
StacktraceTop:

ThreadStacktrace: => 0x7fb2c43cef79: Não é possível acessar a memória no endereço 0x7fb2c43cef79
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/15/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BAP6710H.86A.0055.2011.0215.1656
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DP67DE
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10217-300
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrBAP6710H.86A.0055.2011.0215.1656:bd02/15/2011:svn:pn:pvr:rvnIntelCorporation:rnDP67DE:rvrAAG10217-300:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Mar 27 17:57:34 2014
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/fb0: No such file or directory
 AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
 AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
 AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.0-1ubuntu7
xserver.video_driver: fglrx

Revision history for this message
Lázaro Zarê (lazaronbh) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007fb2c43cef79 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7ffff19467b8
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 5070):
 #0 0x00007fb2c43cef79 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7ffff19467b8

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Lázaro Zarê (lazaronbh) wrote :

anyone?

information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in fglrx-installer (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.