gnome-shell crashed with SIGSEGV in xmlNewInputFromFile__internal_alias()

[Pawel Jonik]

Error occured when I logged in to wallpaper-only-state* of gnome-shell. Instead of restarting lightdm from terminal, I waited and then ~30secs of waiting, this error occured.

* - wallpaper-only-state has something to do with on-screen-keyboard in accessibility settings. I've got this enabled (in lenovo tabletPC). And sometimes (more ofthen than not)) when I logout and login again to gnome-shell, I see wallpaper only.

I figured out that if I restart lightdm and login to Unity and uncheck on-screen-keyboard in accessibility-settings, I can log back in the gnome-shell again.

Really don't know if this two errors are correlated, but since they occured at the same time basically, (and never when I login correctly to gnome-shell) I described it here.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-shell 3.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 5 05:57:01 2012
Disassembly: => 0x100000001: Cannot access memory at address 0x100000001
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: gnome-shell
Title: gnome-shell crashed with SIGSEGV in xmlNewInputFromFile()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Jeremy Bícha (jbicha)]

Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 LTS reached End of Life in April. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

I apologize that we are not always to respond to bug reports promptly. Do feel free to report any other bugs you may find.