Hi,

I have running Suse Linux leap 42.2 without major problems.

The machine is a Dell 780 optiplex 8Gb ram 1Tb HD and is dedicated to Linux.

I have now got a catastrophic failure.

After some discussion elsewhere on this forum, it is not clear whether it is actually a hardware or a software problem.

Briefly, after some days away from the machine, I found a message "Screen lock is broken"

There was some advice as to what to do next, which I followed, all to no avail.

I can boot into a terminal and would like to rescue any logs you recommend to better understand what has happened.

I have looked at the disk and the partitions are there but I don't know exactly where to look, or exactly what to look for.

A disk examination shows it has either failed or is on the point of failing. The "D bus" Warning that came with the "screen lock broken" declaration has been suggested as a software problem.

So, as a Newby, I'm finding it confusing.

I'm planning to fit 2 new disks in raid 1 and reinstall 42.2. I'll put the suspected faulty drive as a stand alone and recover whatever I can.

Any advice and specific information regarding useful logs will be gratefully received.

Run smartmontools.

This program reads the health status of discs.

Boot with any linux live CD/USB and try to mount partitions from the internal drive.
If you can do it you probably can save your important data.
And check partitions for free space, if free space exhausted (or less then 5% of free) it may cause a strange problems like yours.

This could be much less problem than you think, nothing to do with any hardware. Running logged into any of vtty[1-6] as root, open mc, a text mode swiss army knife file manager. If mc is not installed, install it: 'zypper in mc'. Ordinary commands can be run from within mc, with or without normal mc output on the screen. Use Ctrl-o to toggle between those modes. Persistent logs are found in /var/log/.

I've seen the subject of broken screen locking in 42.2 on the opensuse mailing list recently. This might be curable by simply updating and rebooting. To update from cmdline, simply do 'zypper ref; zypper up' logged in as root. OTOH, it seems there may be a matching open openSUSE bug.

Something else to try is a fallback window manager. If your current problem is related to XFCE, Mate, Gnome or KDE, stopping the display manager and using 'startx /usr/bin/icewm' or 'WINDOWMANAGER=icewm startx' could be instructive. If this fails as ordinary user, you could try startx logged in as root, or logged in as root execute 'chmod 4711 /usr/bin/Xorg' and try again as ordinary user.

To stop the display manager, as root, do 'systemctl stop display-manager', or reboot appending a 3 to the Grub cmdline using the e key when the Grub menu appears.

Perhaps (fewer) small steps first.
I would second the use of smartctl first to attempt to ascertain where the problem might lie.


Oops - I see you've already ascertained the disk is the problem. Don't worry about logs, just get your data backed up. Then maybe try to figure out what packages you added so you can re-install them.

Hi Guys and Gals,

There was no important data on the disc. Apart from installing various apps, it was all exploratory.

I have fitted a new disk. I am using RAID 1 and have installed 42.2.

I now am confronted with various problems.

Using YaST, I selected wicked over NetworkManager however my Wlan does not start. 'Ifup wlan0' declare it is up, but it isn't. I cannot ping my BT Hub.

In yast>networks settings for Wlan, the network setup method is 'wicked', the DHCP Client identifier is blank.
The host name to send is linux-dxa1.
Change default route via DHCP is not ticked.
Ipv6 is not enabled.
On the Hostname page:

The host name is linux-dxa1

Domain name is empty

Assign host name to loop back is selected.

There are no named servers.

In Routing:

The default Ipv4 gateway is the Wlan0 ip address

Ipv4 forwarding is enabled.

I cannot move forward from here until I Sudo NetworkManager

Wlan then starts and I can ping my BT hub and my windows machine but I cannot connect to the Internet.

I am able to log on to the BT Hub and check that the Linux box is there, which it is, and connected, which it is.

My firewall is disabled

What am I missing?

Well thank you for giving me those fine tips.

I've changed back from wicked and now the Wlan starts automatically.

Thrashing about is a sort of way to learn, but not the best.

There are suggestions that this site is to change its name from linuxquestions to Linuxstoneysilence

:-)

You probably should have started a new thread for the second question, that's all.

you just mention systemd and see how quickly that changes!

but seriously, this is your second thread for what i consider to be the same problem:
"After some discussion elsewhere on this forum"
i think you should take at least partial responsibility for that stony silence.
and learn more about general troubleshooting and how to help others to help you:
https://wiki.archlinux.org/index.php...roubleshooting
http://catb.org/~esr/faqs/smart-questions.html