For me this mornings daily du locks up the system at the login page. The screen shows the login dialogue but the keyboard and mouse are not usable. A cold reset is the only option available but this only repeats the cycle. Any offers of help will be gratefully received because I am, at the moment, at a complete loss as to what to do.

The only things of note during the du was a reference to a libclutter bug which I didn't consider as significant and ignored and an offer to accept the maintainers version of mountkernfs.sh which I declined to accept thinking this was the safe thing to do(!).

Last edited by clubex on 19.12.2011, 14:21; edited 3 times in total

clubex

Post subject: RE: System lock after DU Posted: 18.12.2011, 13:56

Joined: 2010-09-11
Posts: 100

Status: Offline

More clues which suggest the maintainers new version of mountkernfs,sh should have been taken.

So what you are saying is if xserver-xorg-input-evdev is gone then remove xserver-xorg-core 2:1.11.99.1-1 and re-install xserver-xorg-input-evdev?

DeepDayze

Post subject:Posted: 18.12.2011, 16:03

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline

so was xserver-xorg-input-evdev removed as part of the DU? I haven't seen any removals in the DU I did last night. If so hopefully there will be a newer version that's compatible with the newer xorg packages in the repo soon

As for mountkernfs.sh I haven't been presented with a debconf dialog either. It sounds like the config for this script has changed to become incompatible with the original. So what package is this script part of?

EDIT: this is in initscripts package and I have updated this a few days ago and was not really presented with any dialogs for it.

Last edited by DeepDayze on 18.12.2011, 16:11; edited 1 time in total

clubex

Post subject:Posted: 18.12.2011, 16:08

Joined: 2010-09-11
Posts: 100

Status: Offline

I certainly didn't see anything removed in this morning's DU.

If mountkernfs.sh (via initscripts) isn't the cause of the lockup (or rather just no input devices maybe) I've no idea what's causing it.

DeepDayze

Post subject:Posted: 18.12.2011, 16:15

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline

have you tried getting into single user mode? Perhaps then you can grep the logs to find anything related to mountkernel.sh and post up what you find so smart minds can help you find the problem and how to fix it.

have you tried getting into single user mode? Perhaps then you can grep the logs to find anything related to mountkernel.sh and post up what you find so smart minds can help you find the problem and how to fix it.

Is this when starting X or going into init 3?

I've not tried much as I haven't had the time (family pressure).
Not tried going into single user mode yet.

X seems to start as I can get to the KDE login dialogue. Then the keyboard mouse are inactive.

tty_1_disc_hangup: waiting(init) for tty1 took too long, but we keep waiting.

I haven't checked out the kde4 startup scripts yet as haven't found out where they are.

All comments welcome.

Edit: I also notice there is no Nvidia splash when booting from cold.

slam

Post subject:Posted: 19.12.2011, 07:56

Team Member

Joined: 1970-01-01
Posts: 607
Location: w3
Status: Offline

As a user of the nvidia driver you need to manually reinstall the driver after kernel upgrades, and reinstall nvidia-glx after Xorg upgrades. See also the related page in our manuals.
Alternatively, use the free nouveau driver which does not have such problems with upgrades following this HowTo.
Greetings,
Chris

Yes I do know that and it's been done. But it's a bit more serious. ps aux shows that dbus is not running. This suggests to me that something is wrong with initscripts, as I originally suspected. I'll be able to investigate more when I'm back on the machine this afternoon.

clubex

Post subject:Posted: 19.12.2011, 12:25

Joined: 2010-09-11
Posts: 100

Status: Offline

For all those who are still interested.

All back to normal.

I downgraded initscripts to testing, accepted the maintainer's version of mountkernfs.sh. Now dbus starts during boot and the system is up and running again.

At tomorrow's DU I'll let initscripts be upgraded to unstable and accept the mainainer's new version of mountkernfs.sh. I don't expect any problems.