Yast > Partitioner self terminates. VMWare workstation cannot start.

Hi,

Since 2 updates going to Yast > Partitioner (and confirming with Yes) doesn’t show me the list of drives etc as it should but simply terminates the partitioner.

Also after latest update today: trying to start VMWare workstation (or player) (v.11 in case that matters) doesn’t start the VM manager but the mouse pointer simply jumps for 2-3 seconds and nothing happens.

Any idea how to fix those?

EDIT: Just found that the Boot loader config in Yast also doesn’t work (self terminates instantly). Same for Kernel config (maybe others too, didn’t test them all)

Luckily the Services Manager works and I could get that additional info for VMWare:

* vmware.service - LSB: This service starts and stops VMware services
   Loaded: loaded (/etc/init.d/vmware)
   Active: failed (Result: exit-code) since Sat 2015-07-04 12:43:35 EEST; 24min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 2172 ExecStart=/etc/init.d/vmware start (code=exited, status=1/FAILURE)
   CGroup: /system.slice/vmware.service
           |-2438 /usr/lib/vmware/bin/vmware-vmblock-fuse -o subtype=vmware-vmblock,default_permissions,allow_other /var/run/vmblock-fuse
           `-2516 /usr/sbin/vmware-authdlauncher


Jul 04 12:43:32 i7 vmware[2172]: [34B blob data]
Jul 04 12:43:33 i7 vmware[2172]: [49B blob data]
Jul 04 12:43:33 i7 vmware[2172]: [50B blob data]
Jul 04 12:43:35 i7 vmware[2172]: [30B blob data]
Jul 04 12:43:35 i7 vmware[2172]: [27B blob data]
Jul 04 12:43:35 i7 vmware[2172]: [38B blob data]
Jul 04 12:43:35 i7 systemd[1]: vmware.service: control process exited, code=exited status=1
Jul 04 12:43:35 i7 systemd[1]: Failed to start LSB: This service starts and stops VMware services.
Jul 04 12:43:35 i7 systemd[1]: Unit vmware.service entered failed state.
Jul 04 12:43:35 i7 systemd[1]: vmware.service failed.

Tried the same things in Yast but text mode - same result. Certain components simply crash.

Reinstalled twice VMWare workstation from scratch - still no change. Tried booting older kernel version (4.0.1) - same story. Somehow the latest update damaged the VMWare service.

I hope someone can help. :?

VMWare should at least show some dialog even if the VMWare “service” (which just loads the necessary kernel modules on boot) doesn’t work.

Try running vmware in a terminal window and see what output you get. This will probably indicate the problem.

For YaST, please post the last lines of the logs immediately after it crashes:

sudo tail /var/log/YaST2/y2log

And please post your repo list:

zypper lr -d

Also try to run “sudo zypper dup” to get your system fully up to date.
Depending on how you updated and your configured repos, you might have a mixture of incompatible packages installed.

And please, in the future, open separate threads for each problem you have.

Thanks for the feedback @wolfi322.

  1. Sorry for posting both issues in the same thread. They just seemed to be related as they happened after the same action.

I ran zypper dup but it didn’t fix anything. Actually after updating with it even Software Management stopped working (which used to work before dup).

Here is the info about Yast:

I ran a

tail -f /var/log/YaST2/y2log

and simply clicked Date/Time in Yast. That resulted in a long output . Not sure if it is relevant to paste so many screens here, so I put it on Google docs:

https://goo.gl/oC8umB

zypper lr -d#  | Alias                               | Name                        | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                      | Service
---+-------------------------------------+-----------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------+--------
 1 | Google-Chrome                       | Google-Chrome               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                      |        
 2 | http-download.opensuse.org-708407b7 | utilities                   | No      | ----      | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/utilities/openSUSE_Tumbleweed/ |        
 3 | http-download.opensuse.org-cc7197d2 | openSUSE:Tumbleweed         | No      | ----      | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ |        
 4 | http-download.opensuse.org-e97f0609 | hardware                    | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/hardware/openSUSE_Factory/     |        
 5 | openSUSE-20150318-0                 | openSUSE-20150318-0         | Yes     | (r ) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/tumbleweed/repo/oss/                        |        
 6 | packman-essentials                  | packman-essentials          | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://packman.inode.at/suse/openSUSE_Tumbleweed/Essentials/             |        
 7 | repo-debug                          | openSUSE-Tumbleweed-Debug   | No      | ----      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/tumbleweed/repo/oss/                  |        
 8 | repo-non-oss                        | openSUSE-Tumbleweed-Non-Oss | Yes     | ( p) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/tumbleweed/repo/non-oss/                    |        
 9 | repo-source                         | openSUSE-Tumbleweed-Source  | No      | ----      | Yes     |   99     | NONE   | http://download.opensuse.org/source/tumbleweed/repo/oss/                 |        
10 | repo-update                         | openSUSE-Tumbleweed-Update  | Yes     | ( p) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/tumbleweed/                          |        

As for vmware: No, it doesn’t show any window. The only indication of activity is that it appears in the panel for 1-2 seconds and then disappears. But no windows are opened. Tried also to run through console:

vmrun -T ws-shared -h localhost start "[ha-datacenter/standard] openSUSE-12.1-2/openSUSE-12.1-2.vmx"
Host user: heyjoe
Host password: 
Unable to connect to host.
Error: Failed to connect to host or proxy

Unlikely.
YaST and vmware are just too different. They even use different toolkits for their GUI.

Here is the info about Yast:

I ran a

tail -f /var/log/YaST2/y2log

and simply clicked Date/Time in Yast. That resulted in a long output .

I told you to run YaST, make it crash, and then post the output of “sudo tail /var/log/YaST2/y2log”.
That should be much shorter, and really (only) contain the relevant parts.

Anyway, the problem seems to be this:

2015-07-05 14:24:01 <2> i7(5060) [libstorage] CmdParted.cc(probe):58 THROW:      parted complains: Error: Can't have a partition outside the disk!: "/usr/sbin/parted  -s  '/dev/md126' unit cyl print unit s print"

This also affects the Date/Time module because that checks which partitions you have. It does this to determine whether you have Windows installed too (for the RTC is UTC or local time option). The partitioner will probably crash because of the same reason.

You either seem to experience a bug in parted, or something’s wrong with your partitioning.
Maybe file a bug report.

The Software Management shouldn’t use libstorage I think, so please post the last lines of the log immediately after that one crashes.

zypper lr -d#  | Alias                               | Name                        | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                      

Looks ok.
The “hardware” repo could probably cause a problem that you experience (just judging by the name of the repo), so try to disable that one and run “zypper dup” again. Although I don’t really see anything related in that repo.

As for vmware: No, it doesn’t show any window. The only indication of activity is that it appears in the panel for 1-2 seconds and then disappears. But no windows are opened. Tried also to run through console:

vmrun -T ws-shared -h localhost start "[ha-datacenter/standard] openSUSE-12.1-2/openSUSE-12.1-2.vmx"
Host user: heyjoe
Host password: 
Unable to connect to host.
Error: Failed to connect to host or proxy

So you are using “vmrun” with shared VMs. I never used that myself.
Does “vmware” itself open?

Anyway, the problem seems to be that it cannot connect to localhost.
I think you need the vmware-workstation-server running for that.
So please post the output of "systemctl status

It might not be running because the vmware service failed though.

The output of “/etc/init.d/vmware status” might give more detailed information why that one is not running.
Most likely some kernel module could not be loaded, likely on Tumbleweed with its many kernel modules. Some module might even have failed to be built with your current kernel.

I do remember hunting the internet for VMWare patches to make it work with the current kernel everytime I upgraded to the latest openSUSE release. That’s one of the reasons why I stopped using VMWare completely and switched to VirtualBox.
I can imagine that it’s even worse on Tumbleweed with its many Kernel updates…

If you run vmware itself, it should offer you to recompile the kernel modules if they cannot be loaded, so you’d see whether it succeeds or not.

YaST itself doesn’t crash. What crashes is the separate modules in it when executed. That’s why I simply picked one and gave the output.

openSUSE has been complaining about that partition for a long time (even before the updates). So I am not sure if this is an issue. For some reason it thinks it is on a RAID but in fact it is only the second partition on a disk (created by Windows).

Removed “hardware” repo. Ran “zypper dup” again, rebooted. No change.
Here is the output log which yast generates when clicking on Software Management:

https://goo.gl/RqosPq

Yes. That’s the only way to have SCSI passhtrough on Windows and access the LTO drive.

No. I tried that in console, as user and as root - no output at all. Just like hitting enter on an empty line.

Yes. The service fails to start at boot and that started to happen right after latest update and reboot.

There it is:
https://goo.gl/PNyjtO

Looks like it:

etc/init.d/vmware status
Module vmmon not loaded
Module vmnet not loaded

Unfortunately that is not the case. As explained above running “vmware” only gives no output at all. I am also unable to switch to VirtualBox because of the other reasons explained.

I was told that Tumbleweed was a stable distro which I will be able to upgrade easily. Would you rather recommend using the regular distro?

Yes I know.
That’s why I asked you to run YaST, open a module that crashes, and then post the output of “tail /var/log/YaST2/y2log” immediately afterwards to only get the relevant details about that module crash.

openSUSE has been complaining about that partition for a long time (even before the updates). So I am not sure if this is an issue. For some reason it thinks it is on a RAID but in fact it is only the second partition on a disk (created by Windows).

Ok, but some change might cause libstorage to crash now instead of just giving a warning or similar.
It shouldn’t mistake the partition for a RAID anyway, but it shouldn’t crash either.

This might explain the sudden crashes though: Access Denied

AFAICS libstorage always accessed that device like this, probably always receiving that error. Until recently, however, it just silently ignored the error; there was simply no output on stdout to parse, so no partitions or other technical data were ever reported for that device.

Now this is reported as an exception - which seems to be too strict error checking in this case.

That bug has been fixed meanwhile, but the new package is still in review/testing.
Maybe that fix (“Catch I/O errors while probing disks with parted”) will fix your case too.
After all you do get an error from parted that causes the “crash”.

So I’d say wait for the next update to libstorage, if that doesn’t help file a bug report.

Here is the output log which yast generates when clicking on Software Management:

https://goo.gl/RqosPq

Thanks.
Seems to be crashing in Qt5.
I do remember some bug report or mailinglist post about something similar recently, but have yet to find it.
Strange though that not more people complained yet, so that doesn’t seem to be a general issue.

A bug report might help here too if it’s not already reported.

No. I tried that in console, as user and as root - no output at all. Just like hitting enter on an empty line.

Hm, that’s strange too.
No idea how to debug this. Maybe try to run /usr/lib/vmware/bin/vmware directly.

Yes. The service fails to start at boot and that started to happen right after latest update and reboot.

Well, the latest update probably included a kernel update…

There it is:
https://goo.gl/PNyjtO

I meant the output of “systemctl status vmware-workstation-server”. The last part went missing somehow, sorry…

Looks like it:

etc/init.d/vmware status
Module vmmon not loaded
Module vmnet not loaded

And what does “dmesg|grep -i vmmon” say?
Do the modules exist? (in /lib/modules/$kernel_version/misc/ probably)

find /lib/modules/`uname -r`/ -name vmmon.ko

You could try to rebuild them manually yourself:

vmware-modconfig --console --install-all

If they fail to build with your kernel, you need to find some patch that fixes that.
Maybe this will help, or not: VMware - ArchWiki .

Unfortunately that is not the case. As explained above running “vmware” only gives no output at all. I am also unable to switch to VirtualBox because of the other reasons explained.

I wasn’t suggesting that you should switch to VirtualBox, I just mentioned one reason why I do not use VMWare any more.
As VirtualBox is included in the distribution, there’s no problem with the kernel modules.

I was told that Tumbleweed was a stable distro which I will be able to upgrade easily. Would you rather recommend using the regular distro?

It is supposed to be stable in the sense that it should always be usable and not suddenly fall apart completely. But it is definitely not stable in the sense that there are no changes, rather the opposite. Especially Kernel updates are many.
For 3rd party kernel modules, a regular release is indeed a better choice IMHO.

Even the Tumbleweed Portal states:

When you should keep staying at stable release

At this point there is no guarantee to have all additional modules available in the stable release like for Vmware or Virtualbox.

If you don’t know how to compile your own additional kernel modules and you don’t wish to learn or keep a very close eye on what is being updated, please don’t use Tumbleweed.

Special Concerns

  • Third Party Drivers

If you have 3rd party kernel modules it is STRONGLY suggested that you not use Tumbleweed. Seriously, it’s not worth the pain and extra work, unless you really want to do it.

And if you do do it, then again, you are on your own, sorry.

PS, found it:
https://bugzilla.opensuse.org/show_bug.cgi?id=936979

The y2log in that bug report looks exactly like yours, so you might add a comment there.

But again, this doesn’t seem to be a general problem. I have no idea what special circumstances might trigger it.

A “workaround” as mentioned in the bug report:

I then opened another konsole, ran sudo yast sw_single, did not close it and executed: kdesu yast2 sw_single, it waited because the packagemanager was locked.Went back to the sudo yast sw_single, closed it.
The graphical version now continued and dit NOT crash.

That is exactly what I did:

  1. Open YaST;
  2. Run tail -f …
  3. Click the module and wait 1-2 sec for it to crash
  4. send the info to you

I hope that clarifies the logging part.

Re. the problematic partition, here is the output of “parted -l”: https://goo.gl/qLQAOD
Just to note - this partition is not mounted at all. Not sure why it should cause any trouble at all.

So I’d say wait for the next update to libstorage, if that doesn’t help file a bug report.

Sure. Just to ask: Do you think that is related to the LSB service too or only to the problems in YaST?

Seems to be crashing in Qt5.

A bug report might help here too if it’s not already reported.

I don’t know how to do this properly. I am really not an expert. That’s why I looked for help here and I appreciate a lot your feedback.

No idea how to debug this. Maybe try to run /usr/lib/vmware/bin/vmware directly.

Ok:


/usr/lib/vmware/bin/vmware
You have new mail in /var/spool/mail/root

In mail there are quite a few of these. This is the last one:



Message 143:
From root@localhost.localdomain  Sun Jul  5 23:45:01 2015
X-Original-To: root@localhost
Delivered-To: root@localhost.localdomain
From: mdadm monitoring <root@localhost.localdomain>
To: root@localhost.localdomain
Subject: DegradedArray event on /dev/md126:i7
Date: Sun,  5 Jul 2015 23:45:01 +0300 (EEST)


This is an automatically generated mail message from mdadm
running on i7


A DegradedArray event had been detected on md device /dev/md126.


Faithfully yours, etc.


P.S. The /proc/mdstat file currently contains the following:


Personalities : [raid1] 
md126 : active raid1 sdb[0]
      488383488 blocks super external:/md127/0 [2/1] [U_]
      
md127 : inactive sdb[0](S)
      2964 blocks super external:imsm
       
unused devices: <none>



Well, the latest update probably included a kernel update…

That has never been a problem so far. Actually I got pretty used to re-install the NVIDIA driver after each update. But until now nothing else was breaking like that.

I meant the output of “systemctl status vmware-workstation-server”. The last part went missing somehow, sorry…

[QUOTE]

There you go:

systemctl status vmware-workstation-server
● vmware-workstation-server.service - LSB: This services starts and stops the Workstation as a Server daemon.
Loaded: loaded (/etc/init.d/vmware-workstation-server)
Active: failed (Result: exit-code) since Sun 2015-07-05 18:06:06 EEST; 5h 47min ago
Docs: man:systemd-sysv-generator(8)
Process: 2451 ExecStart=/etc/init.d/vmware-workstation-server start (code=exited, status=1/FAILURE)

Jul 05 18:05:57 i7 systemd[1]: Starting LSB: This services starts and stops the Workstation as a Server daemon…
Jul 05 18:06:06 i7 systemd[1]: vmware-workstation-server.service: control process exited, code=exited status=1
Jul 05 18:06:06 i7 systemd[1]: Failed to start LSB: This services starts and stops the Workstation as a Server daemon…
Jul 05 18:06:06 i7 systemd[1]: Unit vmware-workstation-server.service entered failed state.
Jul 05 18:06:06 i7 systemd[1]: vmware-workstation-server.service failed.
Jul 05 18:06:06 i7 vmware-workstation-server[2451]: [39B blob data]

[QUOTE]
And what does “dmesg|grep -i vmmon” say?
Do the modules exist? (in /lib/modules/$kernel_version/misc/ probably)

find /lib/modules/`uname -r`/ -name vmmon.ko

dmesg returns nothing and there is no such module too.

You could try to rebuild them manually yourself:

vmware-modconfig --console --install-all

That one returns:


Failed to get gcc information.

If they fail to build with your kernel, you need to find some patch that fixes that.
Maybe this will help, or not: VMware - ArchWiki .

Yes, I found the same source you recommend and I applied what they suggest there but:


i7:~ # curl http://pastie.org/pastes/9934018/download -o /tmp/vmnet-3.19.patch
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1596  100  1596    0     0   4275      0 --:--:-- --:--:-- --:--:--  4267
i7:/usr/lib/vmware/modules/source # cd /usr/lib/vmware/modules/source
i7:/usr/lib/vmware/modules/source # tar -xf vmnet.tar
i7:/usr/lib/vmware/modules/source # patch -p0 -i /tmp/vmnet-3.19.patch
patching file vmnet-only/driver.c
patching file vmnet-only/userif.c
i7:/usr/lib/vmware/modules/source # tar -cf vmnet.tar vmnet-only
i7:/usr/lib/vmware/modules/source # rm -r *-only
i7:/usr/lib/vmware/modules/source # vmware-modconfig --console --install-all
Failed to get gcc information.

For 3rd party kernel modules, a regular release is indeed a better choice IMHO.

I wouldn’t mind using a regular release although I got pretty used to re-isntalling the NVIDIA driver every time as mentioned. So far there have been no problems, don’t know why they suddenly piled like that.

Re. regular release, just to ask: would I be able to do a complete system upgrade easily when the new version of openSUSE is out? Also can I switch from Tumbleweed to a regular release without re-formatting or loosing current settings? It would be great if you could provide a link explaining the steps to do that. If that is the only solution to the current problems well… I guess I have no choice.

As for the “workaround” - it didn’t work here. But I found that running yast sw_single from console works (strangely). But trying to run Partitioner or the others from console yast still doesn’t work.

Yes, I was fully aware of what you did.

Re. the problematic partition, here is the output of “parted -l”: https://goo.gl/qLQAOD
Just to note - this partition is not mounted at all. Not sure why it should cause any trouble at all.

It doesn’t cause trouble per se. But libstorage calls parted to scan all partitions, and parted gives an error message about this one. That error message causes libstorage/the YaST module to exit.

Btw, the fix for that bug report has been accepted to Factory today, so will be in the next snapshot.
But as mentioned, I don’t know whether it will fix your problem too.

Probably better to “fix” your partition/hard disk anyway.

Sure. Just to ask: Do you think that is related to the LSB service too or only to the problems in YaST?

You mean the vmware service? No, that’s totally unrelated as mentioned.
This just causes the crash of all YaST things that are related to storage.

You might also try to uninstall parted, but I’m not sure whether the YaST partitioner will work then at all.

I don’t know how to do this properly. I am really not an expert. That’s why I looked for help here and I appreciate a lot your feedback.

See my previous post, this has been reported already.

Btw, a user in the german forum found out that it only crashes for him if run from the main YaST window.
Running the software management module directly with “kdesu yast2 sw_single” works for him.
Maybe that’s a workaround for you too.

Ok:

/usr/lib/vmware/bin/vmware
You have new mail in /var/spool/mail/root

The “new mail” message is totally unrelated to vmware or your try to start it too.
The shell checks for new mail after every command you run.

In mail there are quite a few of these. This is the last one:

Message 143:
From root@localhost.localdomain Sun Jul 5 23:45:01 2015
X-Original-To: root@localhost
Delivered-To: root@localhost.localdomain
From: mdadm monitoring root@localhost.localdomain
To: root@localhost.localdomain
Subject: DegradedArray event on /dev/md126:i7
Date: Sun, 5 Jul 2015 23:45:01 +0300 (EEST)

This is an automatically generated mail message from mdadm
running on i7

A DegradedArray event had been detected on md device /dev/md126.

Faithfully yours, etc.


Seems to be another complain about your partition that's uncorrectly detected as RAID.



> P.S. The /proc/mdstat file currently contains the following:


> Personalities : [raid1] 
> md126 : active raid1 sdb[0]
>       488383488 blocks super external:/md127/0 [2/1] [U_]
>       
> md127 : inactive sdb[0](S)
>       2964 blocks super external:imsm
>        
> unused devices: <none>




So the kernel detects it as RAID too.

But I think it would better to open a new thread with a suitable title for your “RAID” problem.

Something on your hard disk seems to make your system and parted think it is part of a Software RAID.

A workaround might be to uninstall mdadm (ignore dependencies or YaST will get removed as well), but I have no idea whether this would affect parted.

sudo rpm -e --nodeps mdadm

That has never been a problem so far. Actually I got pretty used to re-install the NVIDIA driver after each update. But until now nothing else was breaking like that.

As I explained already, apparently error messages from parted were just ignored by YaST/libstorage until recently. Now they cause an exception, and the module to quit.

I meant the output of “systemctl status vmware-workstation-server”. The last part went missing somehow, sorry…

[QUOTE]

There you go:

systemctl status vmware-workstation-server
● vmware-workstation-server.service - LSB: This services starts and stops the Workstation as a Server daemon.
Loaded: loaded (/etc/init.d/vmware-workstation-server)
Active: failed (Result: exit-code) since Sun 2015-07-05 18:06:06 EEST; 5h 47min ago
Docs: man:systemd-sysv-generator(8)
Process: 2451 ExecStart=/etc/init.d/vmware-workstation-server start (code=exited, status=1/FAILURE)

Jul 05 18:05:57 i7 systemd[1]: Starting LSB: This services starts and stops the Workstation as a Server daemon…
Jul 05 18:06:06 i7 systemd[1]: vmware-workstation-server.service: control process exited, code=exited status=1
Jul 05 18:06:06 i7 systemd[1]: Failed to start LSB: This services starts and stops the Workstation as a Server daemon…
Jul 05 18:06:06 i7 systemd[1]: Unit vmware-workstation-server.service entered failed state.
Jul 05 18:06:06 i7 systemd[1]: vmware-workstation-server.service failed.
Jul 05 18:06:06 i7 vmware-workstation-server[2451]: [39B blob data]

Ok, doesn’t really say why it failed.
But without the vmware service (i.e. the kernel modules loaded), this won’t be of much help anyway.

dmesg returns nothing and there is no such module too.

Right, so you have to build the vmware kernel modules for your current kernel.

That one returns:

Failed to get gcc information.

Do you have gcc installed?
Probably yes, if you install the nvidia driver regularly.

Sorry, I can’t help you there.
As mentioned I dropped vmware years ago.

Yes, I found the same source you recommend and I applied what they suggest there but:

i7:~ # curl http://pastie.org/pastes/9934018/download -o /tmp/vmnet-3.19.patch
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1596 100 1596 0 0 4275 0 --:–:-- --:–:-- --:–:-- 4267
i7:/usr/lib/vmware/modules/source # cd /usr/lib/vmware/modules/source
i7:/usr/lib/vmware/modules/source # tar -xf vmnet.tar
i7:/usr/lib/vmware/modules/source # patch -p0 -i /tmp/vmnet-3.19.patch
patching file vmnet-only/driver.c
patching file vmnet-only/userif.c
i7:/usr/lib/vmware/modules/source # tar -cf vmnet.tar vmnet-only
i7:/usr/lib/vmware/modules/source # rm -r *-only
i7:/usr/lib/vmware/modules/source # vmware-modconfig --console --install-all
Failed to get gcc information.

Well, the same error as above.
Apparently the vmware build checks the version of gcc (or with which gcc version the kernel is built), but fails to do so with Tumbleweed’s Kernel or gcc.

No idea whether there’s a patch for that or any other way to fix it.
Maybe you’d have to update vmware to a new version?

You might also try to ask in the vmware forums.

Btw, somebody had the exact opposite problem on 13.2 recently. He couldn’t compile the vmware kernel modules because the vmware installer insisted on gcc version 5 (because the kernel has been compiled with gcc5): http://lists.opensuse.org/opensuse-kernel/2015-06/msg00011.html
That was with vmware 10.0.5 apparently.
What version do you have installed?

I wouldn’t mind using a regular release although I got pretty used to re-isntalling the NVIDIA driver every time as mentioned. So far there have been no problems, don’t know why they suddenly piled like that.

Well, there hasn’t been a snapshot for a while, so there were more/larger changes than usual.
And gcc has been switched to version 5 which is largely incompatible to gcc 4.

Also it’s not that the problems “suddenly piled up”. You said yourself that you have this partition problem for a while now.

And vmware is a 3rd party product (a commercial one even), nothing to do with openSUSE or Tumbleweed.
Complain to them if it doesn’t work with a current, “bleeding edge” (i.e. with the newest stable software that’s available), Linux distribution.

Re. regular release, just to ask: would I be able to do a complete system upgrade easily when the new version of openSUSE is out?

Yes. I do just that since 12 years.

Also can I switch from Tumbleweed to a regular release without re-formatting or loosing current settings? It would be great if you could provide a link explaining the steps to do that. If that is the only solution to the current problems well… I guess I have no choice.

A downgrade might work, but is not really supported. At least I have heard reports from people trying an online downgrade (changing repos and running “zypper dup”) having problems.
So I’d recommend to do it offline, by booting from a 13.2 installation medium and choosing “Upgrade” at the boot menu.

If that fails (it shouldn’t), you can still do a fresh 13.2 installation afterwards. If you have a separate /home partition, you can just format / and keep all your user accounts/user settings.
If you want to keep the system settings too, you should rather back them up first.
Note, that this only applies to a fresh installation. An upgrade (or rather downgrade) will keep all system settings and even all installed packages.
But exactly this might cause problems…

Links for how to upgrade your openSUSE installation: (a downgrade is not different from an upgrade really)
SDB:System upgrade - openSUSE Wiki (online, not recommended at all for downgrading to 13.2)
SDB:Offline upgrade - openSUSE Wiki (offline, by booting from an installation medium)

As for the “workaround” - it didn’t work here. But I found that running yast sw_single from console works (strangely). But trying to run Partitioner or the others from console yast still doesn’t work.

Yes, again, the softwaremanagement problem is a crash in Qt, the GUI toolkit. So it only affects the graphical version.
The partitioner crashes because of a problem in an underlying library, so it doesn’t matter what GUI you use.

Thank you so much wolfi for spending time with me on that.

I understand it is a total mess and perhaps quite complicated to debug further without a developer. As you mention another update might fix some of those, I guess it might be best not to break something else in an attempt to fix it myself.

Perhaps the best option would be to wait a few days, run another “zypper dup” and if it fixes the problems - we celebrate (until the next upgrade which breaks something :slight_smile: ). If that doesn’t help or if such problems persist - I might indeed downgrade to the regular release as per your recommendations. I will post again if and when I have more info on that issue.

BTW “kdesu yast2 sw_single” works. Thanks!

Well, that update just fixes the (one) YaST Partitioner problem (i.e. that it “crashes” when parted gives an error message), and I don’t know whether it fixes your case as well.

It definitely won’t fix your partition problem itself.

And the Software Management problem is totally unrelated anyway.
Just as the vmware problem.

We are discussing at least 4 (or 5 if you count downgrading to 13.2 as well… :wink: ) completely different and unrelated things here…

BTW “kdesu yast2 sw_single” works. Thanks!

If you are using Plasma5, you should have an entry for “Software Management” in the K-Menu (either in Settings or in System) that does just this.

Quite right. In which case I guess #5 is what I need to do to end this travail :slight_smile:

Ok… installed 13.2 as an upgrade (using DVD). Plasma crashes every time at login (even several times). I only have access to a Dolphin window opened from before (no Panel, no nothing). So I am typing this from XFCE.

YaST components seem to work now. “RAID” is still there but doesn’t cause any trouble.

The attempt to start vmware workstation results in a window asking to recompile certain modules but it needs GCC 5.1.1 which is obviously not present in 13.2.

So it seems the only positive result is that YaST component started to work.

BTW not sure if this is normal but the new system uses the old kernel (4.0.5-3). Another strange result is with a repo which worked without any issues so far:

zypper up
Download (curl) error for 'http://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml':
Error code: Connection failed
Error message: 


Abort, retry, ignore? [a/r/i/? shows all options] (a): i
Do you want to disable the repository Google-Chrome permanently? [yes/no] (no): no
Skipping repository 'Google-Chrome' because of the above error.
Loading repository data...
Reading installed packages...


Nothing to do.



You mentioned you were installing the nvidia driver.
You need to reinstall it now. Better remove it completely and install the RPM packages from the nvidia repo:
https://en.opensuse.org/SDB:NVIDIA_drivers

The attempt to start vmware workstation results in a window asking to recompile certain modules but it needs GCC 5.1.1 which is obviously not present in 13.2.

You obviously still boot Tumbleweed’s Kernel, that one is built with GCC 5.1.1 so vmware insists on using GCC 5.1.1 as well (I already mentioned this problem).
Remove Kernel 4.0 in YaST (click on the “Versions” tab below the package list) and/or select 13.2’s Kernel 3.16 in “Advanced Options” in the boot menu.

BTW not sure if this is normal but the new system uses the old kernel (4.0.5-3).

See above. This happens because you can have more than 1 kernel installed. So “downgrading” the kernel does not remove the higher version.

Another strange result is with a repo which worked without any issues so far:

zypper up
Download (curl) error for 'http://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml':
Error code: Connection failed
Error message: 

Abort, retry, ignore? [a/r/i/? shows all options] (a): i
Do you want to disable the repository Google-Chrome permanently? [yes/no] (no): no
Skipping repository ‘Google-Chrome’ because of the above error.
Loading repository data…
Reading installed packages…

Nothing to do.

Apparently you have no internet connection.
Try to reconfigure it.

I just recompiled the NVIDIA driver and I am in Plasma now (no crash). But I will switch to the one in the repo, yes.

Could you please explain how to remove the 4.0 kernel? I couldn’t find what you said.

As for the Internet connection - obviously I have one :slight_smile:

Enter YaST->Software Management, search for “kernel-desktop” and select the package that you have installed.
Then click on “Versions” below the package list to see all installed/available versions.
Mark all that are not part of any repo for uninstallation, i.e. click on the tick until it becomes a red cross.

As for the Internet connection - obviously I have one :slight_smile:

Well, you could write this from another system… :wink:

Ok, so it’s only the Google repo that has problems?
That would be strange indeed, and rather point to a problem with the repo I suppose.
I can access that URL that’s mentioned in your error message though…

I suppose you can disable it for now. You should have Chrome still installed if you had it installed before.

PS: As you downgraded from Tumbleweed, you might be using Plasma 5.2 now (or lower). If you wanted to you can also switch back to KDE4, which is still fully supported in 13.2 (actually Plasma 5 is more of a technical preview there, although it should work fine).
Just install the package kdebase4-session in that case, this will remove some Plasma5 packages which you need to accept.

Thank you for replying so quickly.

I found the Versions tab now. There are 4.0.5-3 and 4.0.5-1 which become red cross. And I should add latest 3.16.7-21.1 (from the repo) - is that correct? (sorry, just to double check as it is a kernel after all)

As for NVIDIA - I tried each of the gfx02/03/04 package combinations but they all lead to text mode after rebooting. So I had to remove them and recompile using the driver downloaded from nvidia.com. Might that be related to the previous question (kernel versions)? I am just scary not to break anything again. The card is GTX680

Also how do I switch to that stable KDE/Plasma?

Re. chrome repo - it doesn’t complain now when I start YaST repo/software management. Might have been a temporary connection issue on their side I guess.

Yes, but 3.16.7-21.1 should get installed automatically when you update your system.

No problem if you do it manually just now though.

As for NVIDIA - I tried each of the gfx02/03/04 package combinations but they all lead to text mode after rebooting. So I had to remove them and recompile using the driver downloaded from nvidia.com. Might that be related to the previous question (kernel versions)? I am just scary not to break anything again. The card is GTX680

Yes.
When you use Kernel 3.16.7, it should work. But only install the nvidia packages after you removed Kernel 4.0.x and booted to 3.16.

You need those 5 packages btw, but they should be auto-selected in YaST if you have the nvidia repo active:

nvidia-gfxG04-kmp-desktop nvidia-uvm-gfxG04-kmp-desktop x11-video-nvidiaG04 nvidia-glG04 nvidia-computeG04

(the G03 variants would work as well, but they are legacy and YaST probably will want to install G04 anyway)

And please, remove the manually installed driver before you install the RPM packages. Otherwise you might run into problems (maybe not even immediately, but in a few weeks/months when there is an update) because of a mixture of versions.

Also how do I switch to that stable KDE/Plasma?

As I said, install kdebase4-session, and the default “KDE Plasma Workspace” entry on the login screen will go into KDE4.

Re. chrome repo - it doesn’t complain now when I start YaST repo/software management. Might have been a temporary connection on their side I guess.

Probably.

Thank you for explaining.

How do I do that? So far the only procedure to install the driver was to download it from nvidia.com and run the .bin file. Supposing that this is compiled into the kernel which will be removed (4.0.5), is there anything additional I need to do as a clean-up?