Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash

[Jakub Nietrzeba]

After upgrade from working machine with 14.10 to 15.10 I'm unable to login. Right after password screen I see loading of desktop and I'm returned to password prompt again.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,imgpng,unitymtgrabhandles,move,compiztoolbox,place,grid,wall,vpswitch,regex,resize,gnomecompat,snap,session,animation,expo,workarounds,ezoom,fade,scale,unityshell]
Date: Sun Apr 26 23:07:55 2015
DistUpgraded: 2015-04-26 22:20:44,130 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus: virtualbox, 4.3.26: added
EcryptfsInUse: Yes
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 NVIDIA Corporation GT218M [GeForce 315M] [10de:0a7a] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems GeForce 315M [1179:fd71]
InstallationDate: Installed on 2014-11-07 (170 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: TOSHIBA SATELLITE C670-10V
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=28cea712-ba61-42af-a038-545501a067f8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago)
dmi.bios.date: 04/20/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.40
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: TKBSC
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.40
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd04/20/2011:svnTOSHIBA:pnSATELLITEC670-10V:pvrPSC3QE-00700JPL:rvnTOSHIBA:rnTKBSC:rvr1.40:cvnTOSHIBA:ct9:cvrToBeFilledByO.E.M.:
dmi.product.name: SATELLITE C670-10V
dmi.product.version: PSC3QE-00700JPL
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Sun Apr 26 23:07:32 2015
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: nouveau

[Jakub Nietrzeba (gluth)]

Tried to boot from freshly created live cd, and received the same error. So it looks like it is not corelated to configuration of my computer, but rather an Ubuntu itself.

Can I have some help how to at least try to find a source of this error? Or any workaround for similar bug to look at?

[Stephen M. Webb (bregma)]

demesg contains several dups of the following error.

[ 637.133657] traps: compiz[5430] trap invalid opcode ip:7fe2bd6f05f5 sp:7fff0b63f0b8 error:0
[ 868.799930] traps: compiz[6021] trap invalid opcode ip:7f0fab07c5f5 sp:7fff64019268 error:0

It would be helpful if a stacktrace of compiz could be obtained.

[Jakub Nietrzeba (gluth)]

Tell me how, and it will be delivered.

[Jakub Nietrzeba (gluth)]

I have used apport-cli to dive directly into GDB (with symbols) and found this:

#0 0x00007f03bf4205f5 in ?? ()
#1 0x000000000098cdc0 in ?? ()
#2 0x00007ffd079aa8c0 in ?? ()
#3 0x0000000000000007 in ?? ()
#4 0x0000000000000000 in ?? ()

It has just yelled that it cannot find public key for 55EFCAA8.

[Christopher Townsend (townsend)]

If you feel comfortable doing so, could you please attach the Compiz core dump for when this occurs? It may help give us some clues about what's going on.

Also, it appears you had the nvidia binary driver installed at one time and now you are using nouveau. I'm wondering if there is still some cruft left over from the nvidia driver causing this issue...

Thanks!

[Jakub Nietrzeba (gluth)]

I was sure that it was caused by nvidia graphics, removed it but problem persisted, blamed configuration and brought in livecd and the same problem appeared. I can reproduce it on LiveCD, so in a moment I will attach crash file.

[Jakub Nietrzeba (gluth)]

Here is a crash file with coredump and all other info, created from Ubuntu 15.10 LiveCD.

[Christopher Townsend (townsend)]

I missed your comments about having tried this on a LiveCD:)

Great, thanks for the crash file. I'll see if I can glean any useful info out of it.

[Christopher Townsend (townsend)]

Well, I've looked at the crash dump and I'm not sure what symbols gdb can't find. I've loaded debug symbols for compiz-core and it still complains, so I'm at a loss.

I have been reading up on what the kernel trap means and basically it's saying that a process is performing something the hardware doesn't like. In cases like these, the driver is supposed to tell Compiz if something is supported or not, but apparently it's not. It's possible that the newer drivers are making an assumption about the underlying hardware.

Your BIOS may be outdated which may fix some issues. Is it possible to try to update the BIOS on your machine and see if it helps?

[Jakub Nietrzeba (gluth)]

I can try, but it does not looks like it can be upgraded. This laptop works fine on 14.10 and does not seems to be supported by Toshiba anymore.

For me most interesting in call stack is this:

#4 0x0000000000000000

it's NULL, istn't? It looks like there is some callback, thread or signal catcher which is not initialized correctly, it is called and bad things happend. I'm not sure is this even traceable, maybe there is some compilation option which could help catch such jumps?

[Christopher Townsend (townsend)]

Yes, that is a NULL address. I tried sending a SIGILL to compiz on my test system and I got a valid stacktace out of it. I really wish we could at least get something useful out of your dump.

[Jakub Nietrzeba (gluth)]

SIGILL looks like sirens call of executing data segment after hitting some null at execution path. Problem must be somwhere else. I can reproduce it every time (at each login attempt) and I'm not affraid of compilating packages from the sources. If I can help somehow (maybe some usefull gcc flags, some codeguard library?)

[Christopher Townsend (townsend)]

Maybe just installing the ddeb for the compiz packages is enough to get a decent stacktrace.

If you don't know how to do this already, then please follow the instructions on https://wiki.ubuntu.com/DebuggingProgramCrash#Non-built-in_debug_symbol_packages_.28.2A-dbgsym.29 on adding the ddebs archive to your sources.list. Once that's done, then install compiz-core-dbgsym, compiz-plugins-dbgsym, and compiz-plugins-default-dbgsym and try it again.

Hopefully, we can get a better stacktrace. If not, then I'll think about about how to get this darn stacktrace.

[Jakub Nietrzeba (gluth)]

Added those sources, but those packages does not exists. apt-get is unable to locate them.

[Jakub Nietrzeba (gluth)]

Interesting, created another stack trace and it looks almost identical: long garbage, short garbage, long garbage, seven, zero. Array overflow?

[Andrea Azzarone (azzar1)]

Can you try to boot with upstart? You should be able to do that from grub.

[Jakub Nietrzeba (gluth)]

Tried, same effect. Compiz will crash at every one login attempt. Is there a way to fire compiz with debugging in such situation?

[Andrea Azzarone (azzar1)]

Jakub, you can actually install metacity and run unity from a tty using "unity --advanced-debug".

[Andrea Azzarone (azzar1)]

Also you can try to install gnome-shell (or similar) and run from a terminal:
/usr/lib/nux/unity_support_test -p

And post here the output.

[Jakub Nietrzeba (gluth)]

OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NVA8
OpenGL version string: 3.0 Mesa 10.5.2

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: yes

[Jakub Nietrzeba (gluth)]

Installed gnome-shell (it's ugly and complicated), was able to start gdb with compiz inside and it crashed right after loading opengl plugin, it has also warned about corrupted shared library list.

[Jakub Nietrzeba (gluth)]

To be more specific: it loaded opengl plugin, informed that it's fully supported and then creashed right after starting plugin (creation of new thread).

[Christopher Townsend (townsend)]

Ok, so the OpenGL plugin is doing something the hardware doesn't like. The biggest change in OpenGL for 15.04 is the X11 Sync objects. I'm wondering if the driver is saying it's supported, but the GPU can't handle it.

Could you try opening CCSM and go to the OpenGL tab and uncheck "X11 sync objects"?

[Andrea Azzarone (azzar1)]

Did you start unity from a tty?
On 30 Apr 2015 19:35, "Jakub Nietrzeba" <email address hidden> wrote:

> To be more specific: it loaded opengl plugin, informed that it's fully
> supported and then creashed right after starting plugin (creation of new
> thread).
>
> --
> You received this bug notification because you are subscribed to unity
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1448775
>
> Title:
> Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash
>
> Status in Compiz:
> New
> Status in unity package in Ubuntu:
> New
>
> Bug description:
> After upgrade from working machine with 14.10 to 15.10 I'm unable to
> login. Right after password screen I see loading of desktop and I'm
> returned to password prompt again.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.04
> Package: xorg 1:7.7+7ubuntu4
> ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
> Uname: Linux 3.13.0-39-generic x86_64
> ApportVersion: 2.17.2-0ubuntu1
> Architecture: amd64
> CompizPlugins:
> [core,bailer,detection,composite,opengl,decor,mousepoll,imgpng,unitymtgrabhandles,move,compiztoolbox,place,grid,wall,vpswitch,regex,resize,gnomecompat,snap,session,animation,expo,workarounds,ezoom,fade,scale,unityshell]
> Date: Sun Apr 26 23:07:55 2015
> DistUpgraded: 2015-04-26 22:20:44,130 DEBUG enabling apt cron job
> DistroCodename: vivid
> DistroVariant: ubuntu
> DkmsStatus: virtualbox, 4.3.26: added
> EcryptfsInUse: Yes
> ExtraDebuggingInterest: I just need to know a workaround
> GraphicsCard:
> NVIDIA Corporation GT218M [GeForce 315M] [10de:0a7a] (rev a2) (prog-if
> 00 [VGA controller])
> Subsystem: Toshiba America Info Systems GeForce 315M [1179:fd71]
> InstallationDate: Installed on 2014-11-07 (170 days ago)
> InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
> (20140722.2)
> MachineType: TOSHIBA SATELLITE C670-10V
> ProcEnviron:
> TERM=linux
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=pl_PL.UTF-8
> SHELL=/bin/bash
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic
> root=UUID=28cea712-ba61-42af-a038-545501a067f8 ro quiet splash vt.handoff=7
> SourcePackage: xorg
> Symptom: display
> Title: Xorg crash
> UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago)
> dmi.bios.date: 04/20/2011
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 1.40
> dmi.board.asset.tag: To be filled by O.E.M.
> dmi.board.name: TKBSC
> dmi.board.vendor: TOSHIBA
> dmi.board.version: 1.40
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 9
> dmi.chassis.vendor: TOSHIBA
> dmi.chassis.version: To Be Filled By O.E.M.
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd04/20/2011:svnTOSHIBA:pnSATELLITEC670-10V:pvrPSC3QE-00700JPL:rvnTOSHIBA:rnTKBSC:rvr1.40:cvnTOSHIBA:ct9:cvrToBeFilledByO.E.M.:
> dmi.product.name: SATELLITE C670-10V
> dmi.product.version: PSC3QE-00700JPL
> dmi.sys.vendor: TOSHIBA
> version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
> version.ia32-libs: ia32-libs N/A
> version.libdrm2: libdrm2 2.4.60-2
> version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0u...

[Jakub Nietrzeba (gluth)]

No effect - also other switches from OpenGL does not helped.

[Jakub Nietrzeba (gluth)]

Yes. Started gnome-shell, switched to first console, logged in, started unity with --replace and --advanced-debug, gdb has started, pressed 'r', it loaded some plugins and died. There are two additional warnings:
Glib-warning: In call to g_spawn_sync(), exist status of child process was requested but ECHILD was received by waitpid().
dconf-warning: failed to commit changes to dconf: Error spawnin command line 'dbus-launch ....' child process exited abnormally

[Andrea Azzarone (azzar1)]

Can you post here the full gdb log? You can use "set logging file".

2015-04-30 21:32 GMT+02:00 Jakub Nietrzeba <email address hidden>:

> Yes. Started gnome-shell, switched to first console, logged in, started
> unity with --replace and --advanced-debug, gdb has started, pressed 'r', it
> loaded some plugins and died. There are two additional warnings:
> Glib-warning: In call to g_spawn_sync(), exist status of child process was
> requested but ECHILD was received by waitpid().
> dconf-warning: failed to commit changes to dconf: Error spawnin command
> line 'dbus-launch ....' child process exited abnormally
>
> --
> You received this bug notification because you are subscribed to unity
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1448775
>
> Title:
> Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash
>
> Status in Compiz:
> New
> Status in unity package in Ubuntu:
> New
>
> Bug description:
> After upgrade from working machine with 14.10 to 15.10 I'm unable to
> login. Right after password screen I see loading of desktop and I'm
> returned to password prompt again.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.04
> Package: xorg 1:7.7+7ubuntu4
> ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
> Uname: Linux 3.13.0-39-generic x86_64
> ApportVersion: 2.17.2-0ubuntu1
> Architecture: amd64
> CompizPlugins:
> [core,bailer,detection,composite,opengl,decor,mousepoll,imgpng,unitymtgrabhandles,move,compiztoolbox,place,grid,wall,vpswitch,regex,resize,gnomecompat,snap,session,animation,expo,workarounds,ezoom,fade,scale,unityshell]
> Date: Sun Apr 26 23:07:55 2015
> DistUpgraded: 2015-04-26 22:20:44,130 DEBUG enabling apt cron job
> DistroCodename: vivid
> DistroVariant: ubuntu
> DkmsStatus: virtualbox, 4.3.26: added
> EcryptfsInUse: Yes
> ExtraDebuggingInterest: I just need to know a workaround
> GraphicsCard:
> NVIDIA Corporation GT218M [GeForce 315M] [10de:0a7a] (rev a2) (prog-if
> 00 [VGA controller])
> Subsystem: Toshiba America Info Systems GeForce 315M [1179:fd71]
> InstallationDate: Installed on 2014-11-07 (170 days ago)
> InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
> (20140722.2)
> MachineType: TOSHIBA SATELLITE C670-10V
> ProcEnviron:
> TERM=linux
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=pl_PL.UTF-8
> SHELL=/bin/bash
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic
> root=UUID=28cea712-ba61-42af-a038-545501a067f8 ro quiet splash vt.handoff=7
> SourcePackage: xorg
> Symptom: display
> Title: Xorg crash
> UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago)
> dmi.bios.date: 04/20/2011
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 1.40
> dmi.board.asset.tag: To be filled by O.E.M.
> dmi.board.name: TKBSC
> dmi.board.vendor: TOSHIBA
> dmi.board.version: 1.40
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 9
> dmi.chassis.vendor: TOSHIBA
> dmi.chassis.version: To Be Filled By O.E.M.
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd04/20/2011:svnTOSHIBA:pnSATELLITEC670-10V:pvrPSC3QE-00700JPL:rvnTOSHIBA:rnTK...

[Jakub Nietrzeba (gluth)]

Done.

[Jakub Nietrzeba (gluth)]

I have removed Intel microcode driver from my machine and installed Nvidia driver and unity with Compiz went up and running. Should I thank Nvidia or blame Intel?

[Christopher Townsend (townsend)]

Hmm, what do you mean by the Intel microcode driver? That definitely sounds suspicious...

[Christopher Townsend (townsend)]

Oh, maybe you mean the intel-microcode package. If so, I wonder what is pulling that package in to be installed????

[Jakub Nietrzeba (gluth)]

It was installed by jockey (tool which detects what additional drivers can be installed), I didn't installed it by purpose. I think during update it auto installed all drivers and it caused issues. Or it is preloaded by default on all Intel machines. (I do not remember why I diverged from my AMD-nVidia rule of thumb for Linux machines on this computer. ;) )

[Christopher Townsend (townsend)]

Since Compiz is a victim of bad microcode, I'm going to mark this Invalid. I'm glad you were able to track down the offending package.

If you feel compelled to get intel-microcode fixed, please open a new bug report against that package.

Thanks!

[Jakub Nietrzeba (gluth)]

Thank you for your time, I really appreciate it. Reported as #1452581.