gnome-shell crashed with SIGSEGV in xmlNewInputFromFile__internal_alias()

Bug #978341 reported by PeteGordon
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

This happens when starting gnome-shell

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-shell 3.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
Uname: Linux 3.2.0-22-generic-pae i686
ApportVersion: 2.0-0ubuntu5
Architecture: i386
CrashCounter: 1
Date: Tue Apr 10 21:32:41 2012
Disassembly: => 0x21: Cannot access memory at address 0x21
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvReason: executing NULL 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

Revision history for this message
PeteGordon (petegordon007) wrote :
Revision history for this message
PeteGordon (petegordon007) wrote :

I've attached an excerpt of /var/log/syslog which contains some details of the error

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
summary: - gnome-shell crashed with SIGSEGV in xmlNewInputFromFile()
+ gnome-shell crashed with SIGSEGV in
+ xmlNewInputFromFile__internal_alias()
tags: removed: need-i386-retrace
Revision history for this message
PeteGordon (petegordon007) wrote :

Turning off the onscreen keyboard in Accessability > Typing > Onscreen Keyboard allowed gnome-shell to startup. This is a reproduceable problem for me. I always get the error when the keyboard is on.

visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Jeremy Bícha (jbicha)
Changed in gnome-shell (Ubuntu):
status: Confirmed → Invalid
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.