VirtualBox

Ticket #11008 (closed defect: fixed)

Opened 19 months ago

Last modified 7 months ago

PC-BSD guest: Segfault in libX11.so.6.3.0 when choosing ACPI shutdown

Reported by: KenSharp Owned by:
Priority: major Component: other
Version: VirtualBox 4.2.0 Keywords:
Cc: Guest type: BSD
Host type: Linux

Description

kernel: [67331.018664] VirtualBox[9804]: segfault at ffffffffc00c6b28 ip 00007f88119fec58 sp 00007fffabbfbe40 error 4 in libX11.so.6.3.0[7f88119cb000+12f000]

When choosing ACPI shutdown (or Host+H) Vbox simply segfaults and exits. This happens every time.

Not sure how to debug this but will, of course, do any debugging that is necessary.

Running Ubuntu Precise amd64 with Unity 2D, updated.

Change History

comment:1 Changed 19 months ago by KenSharp

This is actually 4.1.22-80657~Ubuntu~natty but I don't seem to be able to edit the details of this bug.

comment:2 Changed 19 months ago by KenSharp

  1. I had no idea 4.2 was out until I opened this bug (Vbox did not say there was an update).
  2. I have no idea why Vbox was choosing Natty over Precise updates <-- bug?

4.2/Precise fixes this. Please close as fixed.

comment:3 Changed 19 months ago by KenSharp

Scrub that previous comment, this happens all the time!

Any guest. Pausing the VM then starting it again gives a black screen. The VM is still running and has to be ACPI shutdown and started again to get it working properly. This affects snapshots as they pause the machine to do so.

[74356.327586] VirtualBox[24190]: segfault at 44086e18 ip 00007f2794ffac58 sp 00007fff8898b320 error 4 in libX11.so.6.3.0[7f2794fc7000+12f000] [77889.531736] VirtualBox[25640]: segfault at ffffffffa0086e18 ip 00007f41f1a60c58 sp 00007fff658780f0 error 5 in libX11.so.6.3.0[7f41f1a2d000+12f000]

comment:4 Changed 19 months ago by frank

Please attach a VBox.log file of such a VM session.

Regarding the Natty/Precise package conflict: How did you install the package, did you download it manually or did your package manager update an older package automatically? In the latter case, check your /etc/apt/sources.list / /etc/apt/source.list.d files, that usually means that the wrong repository is chosen.

comment:5 Changed 16 months ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

No response, closing.

comment:6 Changed 7 months ago by KenSharp

Why the Hell doesn't this system send me an email when I receive a response? It might help!

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use