Xubuntu terminal crashes X under kvm

Bug #221293 reported by to be removed on 2008-04-24
4
Affects Status Importance Assigned to Milestone
kvm (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: kvm

When I run Xubuntu (dapper, gutsy) under kvm, and start their terminal emulator, the guest X server crashes. Every time.

I'm told this doesn't happen on real hardware, so it is probably a kvm bug, though I admit I can't imagine what might cause it.

I've had this happen both when running the live cd session, and on the installed system.

Arno Peters (awpeters) on 2008-05-12
Changed in kvm:
status: New → Confirmed
Arno Peters (awpeters) wrote :

I see the same thing. Starting xfce4-terminal from the menu causes the X server to crash.

The relevant lines in .xsession-errors seem to be:

(xfdesktop:5145): GLib-CRITICAL **: g_hash_table_foreach: assertion `hash_table != NULL' failed

(xfdesktop:5145): GLib-CRITICAL **: g_hash_table_foreach: assertion `hash_table != NULL' failed
x-session-manager: Fatal IO error 11 (Hulpbron is tijdelijk onbeschikbaar) on X server :0.0.
xfce-mcs-manager: Fatal IO error 104 (Verbinding is weggevallen) on X server :0.0.
xfce4-panel: Fatal IO error 104 (Verbinding is weggevallen) on X server :0.0.
update-notifier: Fatal IO error 11 (Hulpbron is tijdelijk onbeschikbaar) on X server :0.0.
applet.py: Fatal IO error 11 (Hulpbron is tijdelijk onbeschikbaar) on X server :0.0.
xfdesktop: Fatal IO error 11 (Hulpbron is tijdelijk onbeschikbaar) on X server :0.0.
xfce4-terminal: Fatal IO error 104 (Verbinding is weggevallen) on X server :0.0.
nm-applet: Fatal IO error 104 (Verbinding is weggevallen) on X server :0.0.

Starting xfce4-terminal from the failsafe xterm session starts the terminal window without a crash.

Sergio Zanchetta (primes2h) wrote :

Could you attach the output of 'lspci -v' command please?

Arno Peters (awpeters) wrote :

$ lspci -v
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
 Flags: fast devsel

00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
 Flags: bus master, medium devsel, latency 0

00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] (prog-if 80 [Master])
 Flags: bus master, medium devsel, latency 64
 [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8]
 [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1]
 [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8]
 [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1]
 I/O ports at c000 [size=16]

00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
 Flags: medium devsel, IRQ 9

00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 [VGA controller])
 Flags: bus master, fast devsel, latency 0
 Memory at f0000000 (32-bit, prefetchable) [size=32M]
 Memory at f2000000 (32-bit, non-prefetchable) [size=4K]

00:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20)
 Flags: bus master, fast devsel, latency 64, IRQ 11
 I/O ports at c100 [size=256]
 Memory at f2001000 (32-bit, non-prefetchable) [size=256]

00:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20)
 Flags: bus master, fast devsel, latency 64, IRQ 10
 I/O ports at c200 [size=256]
 Memory at f2001100 (32-bit, non-prefetchable) [size=256]

Sergio Zanchetta (primes2h) wrote :

Try this workaround:
Open your xorg.conf, then scroll down to the Screen section, and find the DefaultDepth
option. Change that number to 16 (it should be 24).
Restart X.

Tell me if it helps.

Arno Peters (awpeters) wrote :

It does: setting colordepth to 16 bits eliminates the crash.

Changed in kvm:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers