can't login to kubuntu 8.10 after install on paralells 3.0

Bug #294836 reported by jgc94131
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After installing Kubuntu 8.10 with Parallels 3.0 on Max OS X 10.5.5, login screen comes up OK, but after loging in, X server crashes.
See syslog output screen shot. Failsafe sesion not possible either (different bug).

Revision history for this message
jgc94131 (jgc) wrote :
Revision history for this message
Matthew Harmon (mjh) wrote :

Having the same issue on MacBook Pro, 10.5.3 runing within Parallels Desktop 3.0 Build 4128.

Errors in each image, include;

KubuntuFail0:
kdm_greet: Cannot open default user face
kernel: mtrr no MTRR for c0000000,1000000 found
kernel: mtrr your processor doesn't support write-combining
kdm[]: X server for display :0 terminated unexpectedly
console-kit-daemon[]: Glib-GObject-WARNING: instance with invalid (NULL) class pointer
console-kit-daemon[]: GLib-GObject-CRITICAL: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

KubuntuFail1:
kdm_greet[]: Cannot open default user face
kernel: mtrr no MTRR for c0000000,1000000 found
kernel: mtrr your processor doesn't support write-combining

Revision history for this message
Matthew Harmon (mjh) wrote :

KubuntuFail1:
kdm_greet[]: Cannot open default user face
kernel: mtrr no MTRR for c0000000,1000000 found
kernel: mtrr your processor doesn't support write-combining

Revision history for this message
Matthew Harmon (mjh) wrote :

From ~/.xsession-errors:

(Soprano::Redland::BackendPlugin) creating model of type "hashes" with options "hash-type='memory',contexts='yes'"
<unknown program name>(4708)/: Communication problem with "kmix" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.Disconnected" : " "Connection was disconnected before a reply was received" "
QObject: Do not delete object, 'unnamed', during its event handler!
QDBusConnectionPrivate::connectSignal: received error from D-Bus server while coop.DBus.Error.NoReply (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
klipper: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 15 requests (8 known processed) with 0 events remaining.
QProcess: Destroyed while process is still running.
ksmserver: Fatal IO error: client killed

Revision history for this message
kimptoc (chris-kimptoc) wrote :

Hi,

I am getting this with Parallels Desktop 3.0 for Mac, build 5638... I wonder if there is a Parallels fix for this - will try their forums.

Regards,
Chris

Revision history for this message
Michael Fletcher (mikefletcher) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please run the command 'apport-collect 294836' which will attach necessary information for debugging this as an Xorg problem. Thanks in advance.

affects: ubuntu → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
kimptoc (chris-kimptoc) wrote :

mmm - was on a 10.5/Leopard system - now running 10.6/Snowy and Parallels 3 dont run on it... moved to VirtualBox and Ubuntu works just fine with that :)

Revision history for this message
Michael Fletcher (mikefletcher) wrote :

Ok, thanks. I will leave this bug as Incomplete until the original bug reporter has a chance to comment.

Bryce Harrington (bryce)
tags: added: kubuntu
tags: added: intrepid
Revision history for this message
Bryce Harrington (bryce) wrote :

The 'mtrr' errors in the screenshots indicate this to be a kernel issue.

affects: xorg (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi jgc94131,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 294836

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
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.