boot process interrupts

[hoppel]

Hi,

I just managed to misconfigure my Mint (again...), so it won't startup anymore. Instead I get the following message, which appears right after the start of gdm as it seems (the mouse pointer is already working):

Code: Select all

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.

I tried to solve it by using the "fix the x-system" command (which helped another time with the same failure message), but now this doesn't do anything. I have one clue what might be the reason: before the error occured I disabled some daemons which I thought I wouldn't need (for instance: I remember disabling the Bluetooth daemon).
I'm really stuck - is there a way to enable those daemons again? Could one of them be the cause?

[rbanavara]

not sure if this helps, but try logging with failsafe gnome session (click on sessions from login window).

[hoppel]

Well, unfortunately I'm not able to reach the login window (my gdm is configured to boot completely until the desktop appears - normally I don't see that screen).

[rbanavara]

There should be a way to disable the automatic login (just to resolve this issue). But I am not sure how to do this.

But you can try this: once you login (if you can get up to there!), log out & log back in with gnome in safe mode. See if this works.

[jrd]

To get a terminal you can type "ctrl alt f1" and from there you can log in and add your daemons back.

[hoppel]

To be clear: I cannot do anything in the graphical mode except moving the mouse. The error message is displayed as a single window, it has a close-button which doesn't react on clicking. Though I can change to the terminal, as described by jrd. But I do not have clue how to add the missing daemons by using that terminal - I mean, I can login there, and what do I have to do after that? I'm not very familiar with the terminal - that's why I posted this under newbie questions...

[rbanavara]

not sure if this works..., if the automatic login is setup, pressing ctrl+al+backspace will it get you to login screen or will log you in back automatically...? The above key combination will kill the current x session & resatrt the xsession again. I am not sure how to reconfigue / add back the missing demon (also i dont think disabling bluetooth demon is causing this issue as they are totally not related).

But if you get back to login screen by pressing ctrl+al+backspace, then you can try out failsafe gnome session.

[hoppel]

Thanks for your help, but it didn't work that way. Instead it suddenly started to work again - because of one little change in the environment: my wireless network didn't work for two weeks, now that it is online again, I can boot again. Since I experienced something like this earlier already I'm quite sure that the cause lies in a bug in Mint or Ubuntu. If a configured network isn't present, for instance because the router is offline or the signal is weak, Mint seems to stop working correctly. I also experienced problems when trying to shutdown after the router went offline.
Didn't happen with Darynna though...