Bug 1073926 - YaST causing system lockup
YaST causing system lockup
Status: RESOLVED NORESPONSE
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: YaST2
Current
x86-64 openSUSE 42.3
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
Jiri Srain
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-12-21 19:33 UTC by Dorian Weimar
Modified: 2018-03-03 10:11 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
jreidinger: needinfo? (doriang2015)


Attachments
File generated by save_y2logs (5.56 MB, application/x-xz)
2017-12-21 19:33 UTC, Dorian Weimar
Details
requestted strace file. (418.05 KB, application/x-bzip)
2018-01-04 02:11 UTC, Dorian Weimar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dorian Weimar 2017-12-21 19:33:12 UTC
Created attachment 754100 [details]
File generated by save_y2logs

Upon selecting certain options in the main YaST window, the system completely locks up.  The only option is a forced shutdown.

Options which have frozen the system are;
-Software Repositories
-Hardware Information
-Printer
-Boot Loader
-Kernel Settings
-Partitioner
-Snapper

This is when running the GTK graphical version on Gnome 3.26.2.
It also happened on one occasion using the non-graphical NCURSES/terminal version running in single-user mode when the Boot Loader option was selected.  This has occurred on at least 3 laptops by different manufacturers (MSI, Acer, HP).

I have attached the file generated by save_y2logs.  This log is from the MSI system.
Comment 1 Josef Reidinger 2017-12-29 09:13:23 UTC
(In reply to Dorian Weimar from comment #0)
> Created attachment 754100 [details]
> File generated by save_y2logs
> 
> Upon selecting certain options in the main YaST window, the system
> completely locks up.  The only option is a forced shutdown.
> 
> Options which have frozen the system are;
> -Software Repositories
> -Hardware Information
> -Printer
> -Boot Loader
> -Kernel Settings
> -Partitioner
> -Snapper
> 
> This is when running the GTK graphical version on Gnome 3.26.2.
> It also happened on one occasion using the non-graphical NCURSES/terminal
> version running in single-user mode when the Boot Loader option was
> selected.  This has occurred on at least 3 laptops by different
> manufacturers (MSI, Acer, HP).
> 
> I have attached the file generated by save_y2logs.  This log is from the MSI
> system.

Does it happen always? I check logs and e.g. for software repositories I see some actions like pressing buttons. And does it froze immediatelly when you select module or later when doing something there?
Comment 2 Dorian Weimar 2018-01-03 04:24:23 UTC
> Does it happen always? I check logs and e.g. for software repositories I see
> some actions like pressing buttons. And does it froze immediatelly when you
> select module or later when doing something there?

It happens most of the time, and it is when a module is selected such as the ones I listed.  At that point, the system completely locks up and all I can do is force a shutdown by holding the power button.
Comment 3 Josef Reidinger 2018-01-03 13:01:28 UTC
(In reply to Dorian Weimar from comment #2)
> > Does it happen always? I check logs and e.g. for software repositories I see
> > some actions like pressing buttons. And does it froze immediatelly when you
> > select module or later when doing something there?
> 
> It happens most of the time, and it is when a module is selected such as the
> ones I listed.  At that point, the system completely locks up and all I can
> do is force a shutdown by holding the power button.

So it is complete system lockup? you cannot switch to e.g. console with ctrl+alt+f* ? or can you ssh to machine?

What we can try to identify problematic part is to call it with strace and redirect output to file, which you will attach.

Something like 

strace -ff -o ~/yast.strace /sbin/yast2 bootloader

and then pack and attach all ~/yast.strace.* files

pack e.g. with 
tar cjf ~/yast.strace.tar.bz2 ~/yast.strace*
Comment 4 Dorian Weimar 2018-01-04 02:11:03 UTC
Created attachment 754746 [details]
requestted strace file.

Compressed output of command "strace -ff -o ~/yast.strace /sbin/yast2 bootloader"

As requested
Comment 5 Dorian Weimar 2018-01-04 02:15:24 UTC
(In reply to Josef Reidinger from comment #3)
> So it is complete system lockup? you cannot switch to e.g. console with
> ctrl+alt+f* ? or can you ssh to machine?
> 
> What we can try to identify problematic part is to call it with strace and
> redirect output to file, which you will attach.
> 
> Something like 
> 
> strace -ff -o ~/yast.strace /sbin/yast2 bootloader
> 
> and then pack and attach all ~/yast.strace.* files
> 
> pack e.g. with 
> tar cjf ~/yast.strace.tar.bz2 ~/yast.strace*

I've attached the file above.  And yes it is a complete lockup.  I cannot switch to a different TTY console with CTRL+ALT+F1-6 nor can I SSH into the machine.  HDD and network activity lights are dead.  The machine will not sleep if I close the lid or press the power button.  The only option is forced power off.

The attached file above is the trace from the very first attempt at opening the bootloader.

If any other information may come in handy, please let me know.  I would like to wipe this partition and change to openSUSE Leap to have a working system, but I would like to help provide as much info as possible as well.
Comment 6 Dorian Weimar 2018-01-05 22:04:42 UTC
Final update;

I installed Leap 42.3 alongside my current OSes and it had no issues with YaST.

However, after installing Nvidia optimus drivers using the same instructions page as I used for Tumbleweed, it broke the system. I recovered and retried a few times but never got it working.

Now with 2 broken openSUSE OSes on my system, I've given up on the openSUSE distro and deleted all the partitions.  I hope the information I've provided can help in some way.  I will not be reinstalling openSUSE so I cannot provide any further information.
Comment 7 Karl Cheng 2018-03-03 10:11:27 UTC
We're sorry to hear that openSUSE did not meet your expectations.

Although we attempt to provide a stable, feature rich and high quality Linux distribution for our users, sometimes there can be hiccups that prevent us on delivering on our goals.

Given we haven't been able to reproduce these issues, unfortunately this bug report will have to be closed.

If you ever do reconsider, please feel free to reach out to the openSUSE community so that we can help you to have a smooth experience.

---

If anybody else can reproduce this issue with a current version of openSUSE, please feel free to reopen this bug report or file a new one. Thank you!