[opensuse] Yast broken
Hi, Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2. After some problems with the video (solved) I can't get the Yast-gui to work. Running from the command-line I get this : /sbin/yast2: regel 440: 15837 Segmentatiefout $y2ccbin $Y2UI_ARGS "$@" With the ncurses version of yast (I think) I forced to re-install all yast2-modules, but that didn't help. Any suggestions ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-02-13 19:24, Koenraad Lelong wrote:
Hi,
Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2.
DVD boot, or zypper dup? - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlTgAnEACgkQja8UbcUWM1yZTQD8D0J+UfZpn/Y0fdJmezB5hJ7d Xs0A3/4m5jq78i04hjcA/iFxpNnwaiupMeCX7Z2dUvPmv2Rdv/QegOStVKRXq/aY =i7dU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15/02/15 13:20, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-02-13 19:24, Koenraad Lelong wrote:
Hi,
Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2. DVD boot, or zypper dup?
Your question caught my eye so I went looking for the info which (I thought) was available years ago telling people if one could upgrade oS from one version to the latest and by which method. In doing so I came across this: https://en.opensuse.org/Portal:Installation which offers no real info to justify its Heading, "Portal: Installation". And to make it even more interesting, at the bottom of this informative article it is stated, "Last updated by --Muhlemmer 13:46, 13 March 2011 (MDT) ". WOW! How up-to-date can one be, I ask you?! BC -- Using openSUSE 13.2, KDE 4.14.4 & kernel 3.19.0-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/15/2015 01:46 AM, Basil Chupin wrote:
Your question caught my eye so I went looking for the info which (I thought) was available years ago telling people if one could upgrade oS from one version to the latest and by which method.
In doing so I came across this:
https://en.opensuse.org/Portal:Installation
which offers no real info to justify its Heading, "Portal: Installation".
And to make it even more interesting, at the bottom of this informative article it is stated, "Last updated by --Muhlemmer 13:46, 13 March 2011 (MDT) ".
WOW! How up-to-date can one be, I ask you?!
1. Since it has a reference to 13.2 under "get your software" it seems up to date. That's regardless of any update to the time stamp. 2. A "Portal" is only about where to go for detailed information and that's what it has its its up to date on that, as #1. I don't expect a portal to be updates often or to contain the detailed information. I also note that the "last update" you refer to is not on the main "portal" part but within a box titled "Things to do". Your criticism is unfounded. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 15-02-15 om 03:20 schreef Carlos E. R.:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-02-13 19:24, Koenraad Lelong wrote:
Hi,
Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2.
DVD boot, or zypper dup?
I did the upgrade via DVD. Most things do work. Things that do not work (media-playing, ICA-connection maybe) I can't try to correct because I find the ncurses Yast very limited. Is there a zypper command I can use to force to re-install the yast-modules ? Thanks, Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op maandag 16 februari 2015 10:27:16 schreef Koenraad Lelong:
Is there a zypper command I can use to force to re-install the yast-modules ?
zypper in --force <list with package names separated by spaces> -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 16-02-15 om 11:19 schreef Freek de Kruijf:
Op maandag 16 februari 2015 10:27:16 schreef Koenraad Lelong:
Is there a zypper command I can use to force to re-install the yast-modules ?
zypper in --force <list with package names separated by spaces>
I re-installed all packaged this way, but the problem persists. Thanks anyway. Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-02-16 10:27, Koenraad Lelong wrote:
I did the upgrade via DVD.
Most things do work. Things that do not work (media-playing, ICA-connection maybe) I can't try to correct because I find the ncurses Yast very limited.
Is there a zypper command I can use to force to re-install the yast-modules ?
DVD upgrade misses many components, because the DVD itself is too small. I would recommend, with the minimal repositories enabled⁽¹⁾, to run a zypper dup, up, and patch. (Alternatively, use the DVD, but tell it to use internet repos for the upgrade, ignoring the local content) (1) Meaning oss, non-oss, and updates. Not packman. Maybe nvidia/amd repos if you need the proprietary drivers. Not extra things like kde/gnome repos. Once system works right, do the multimedia switch if you want, and add other repos. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Hello, On Tue, 17 Feb 2015, Carlos E. R. wrote:
I would recommend, with the minimal repositories enabled?¹?, to run a zypper dup, up, and patch.
(Alternatively, use the DVD, but tell it to use internet repos for the upgrade, ignoring the local content)
(1) Meaning oss, non-oss, and updates. Not packman. Maybe nvidia/amd repos if you need the proprietary drivers. Not extra things like kde/gnome repos.
Once system works right, do the multimedia switch if you want, and add other repos.
Since zypper works ok (say 11.2), I've dupped with _all_ repos enabled without a hitch I could not definitely blame on a lock/taboo set by me. And I do have even a bunch of devel- and home-repos. Ok, I have not done many d'ups, but well, I've got tons of locks and repos and did at least those: 11.2(32bit) -> 11.4(64bit) 11.4 -> 12.1 still using 12.1, but did further test-upgrades: 12.1 -> 12.3 [1] 12.1 -> 13.1 [1] [1] had to massage zypper a bit cause of sysvinit->systemd, and me having thus far tabooed any and all of systemd related stuff, so that's expected that I had to solve some conflicts there (basically allowing systemd), but you don't do that, do you? which did work as expected (i.e. just tons of systemd crap not working), but the dup worked even though it included the switch from sysvinit to systemd. Having to disable all "other" repos is a myth. And, if you got literally hundreds of packages from a mix of other repos, you can't just do a "switch system packages to ...", after you dupped with "other" repos disabled. Carlos, have you ever tried it? I do it this way: 1. on ORG: clone the system to a free partition as CLONE (with rsync) 2. on ORG: adjust CLONE to boot (edit grub config, fstab) 3. on ORG: add a chainloader entry for the CLONE partition (if not there) add a line to grub to boot the CLONE directly, and boot that. 4. on CLONE: install grub to /, so it can be chainloaded and yast2 can update the kernel stuff 5. on CLONE: adjust repos, e.g. cd /etc/zypp cp -a repos.d repos.d.13.1 cd repos.d perl -pi -e 's/13\.1/13.2/g' *.repo 6. on CLONE: zypper clean ref 7. on CLONE: zypper dup (repeat until all ok) 8. test CLONE until you're content ORG is untouched and can be used until CLONE is up and running. -dnh -- George: So, my whole life, everything, all I get to keep are thoughts and memories? Rube: That's all we ever have, Peanut. -- Dead Like Me -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/13/2015 07:24 PM, Koenraad Lelong wrote:
Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2.
Upgrading with jumps are not supported and most probably won't work. I hope you did "zypper dup" etc. from 12.3 .. 13.1 .. 13.2? Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-02-15 13:25, Bernhard Voelker wrote:
On 02/13/2015 07:24 PM, Koenraad Lelong wrote:
Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2.
Upgrading with jumps are not supported and most probably won't work. I hope you did "zypper dup" etc. from 12.3 .. 13.1 .. 13.2?
AFAIK, it is not via dup, but it is via dvd method. Since decades. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlTgv7sACgkQja8UbcUWM1zV0gD/fHS0llmE3pwHHx5/2rVL5JR0 YrGEXMhdXDZUa1HpLr8A/juno7HFAP6k+rrH+hQMuO8ElhCRGRxi81/zJ6dHZIZQ =ng9u -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/02/15 02:48, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-02-15 13:25, Bernhard Voelker wrote:
On 02/13/2015 07:24 PM, Koenraad Lelong wrote:
Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2. Upgrading with jumps are not supported and most probably won't work. I hope you did "zypper dup" etc. from 12.3 .. 13.1 .. 13.2? AFAIK, it is not via dup, but it is via dvd method. Since decades.
"Since decades" ago it has been to dup from a version to the next version to the next version to the next version until you reach the (latest) version you are upgrading to. But if you want to *jump* 'several' versions and upgrade to the latest then you use the DVD and *make* *a* *fresh* *install*. Koenraad jumped 12.3 to 13.2 using dup which is a *NO-NO*. The failures associated with doing so have been spelt out in past documentation but it now appears that this is no longer so. We progress backwards. BC -- Using openSUSE 13.2, KDE 4.14.4 & kernel 3.19.0-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-02-16 08:08, Basil Chupin wrote:
On 16/02/15 02:48, Carlos E. R. wrote:
On 2015-02-15 13:25, Bernhard Voelker wrote:
On 02/13/2015 07:24 PM, Koenraad Lelong wrote:
Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2. Upgrading with jumps are not supported and most probably won't work. I hope you did "zypper dup" etc. from 12.3 .. 13.1 .. 13.2? AFAIK, it is not via dup, but it is via dvd method. Since decades.
"Since decades" ago it has been to dup
Dup was invented about 5 years ago, not decades ago. There is another, way older, upgrade procedure. A decades old method, which supports version jumping.
But if you want to *jump* 'several' versions and upgrade to the latest then you use the DVD and *make* *a* *fresh* *install*.
No.
Koenraad jumped 12.3 to 13.2 using dup which is a *NO-NO*.
He did not. I asked him. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlTisGIACgkQja8UbcUWM1wkjgEAnnKImkSe8+FTLVRddtr2aQB6 duQA7wGTbrzfHo/Ho+YA/jCkjXz3Wg7PI11wZwxbB+ePaVgXgXiVyxAazNstzAVj =ouu8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 13 of February 2015 19:24:25 Koenraad Lelong wrote:
Hi,
Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2. After some problems with the video (solved) I can't get the Yast-gui to work. Running from the command-line I get this : /sbin/yast2: regel 440: 15837 Segmentatiefout $y2ccbin $Y2UI_ARGS "$@"
With the ncurses version of yast (I think) I forced to re-install all yast2-modules, but that didn't help.
Any suggestions ?
I have exactly the same problem here, after upgrading an installation of 12.3 to 13.2 x86. The message: Out of memory allocating 1048576*4 bytes! appears right before the segfault, and the backtrace is similar to the one in https://bugzilla.novell.com/show_bug.cgi?id=889329, which is marked as a duplicate of a fixed issue. The upgrade from 12.3 to 13.2 was relatively straightforward; actually, the only serious problem was that systemd would suspend the system shortly after boot without any obvious reason. -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 13.02.2015 um 19:24 schrieb Koenraad Lelong:
Hi,
Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2. After some problems with the video (solved) I can't get the Yast-gui to work. Running from the command-line I get this : /sbin/yast2: regel 440: 15837 Segmentatiefout $y2ccbin $Y2UI_ARGS "$@"
With the ncurses version of yast (I think) I forced to re-install all yast2-modules, but that didn't help.
Any suggestions ?
Hi Koenraad, try a "rpm -qa 'yast2*' | sort" and look for the installed YaST modules. oS 12.3 came with YaST 2.x, while 13.1 introduced YaST 3.x. Uninstall each and every YaST2 package version 2.x (with "zypper rm ..."), if there is an equivalent 3.x package, it will be pulled in (I hope), since zypper knows how to solve the dependencies. If the dependencies are not pulled in automatically, try "zypper in --force yast2", which should reinstall the main package and its dependencies. HTH, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 17-02-15 om 07:54 schreef Werner Flamme:
try a "rpm -qa 'yast2*' | sort" and look for the installed YaST modules. oS 12.3 came with YaST 2.x, while 13.1 introduced YaST 3.x. Uninstall each and every YaST2 package version 2.x (with "zypper rm ..."), if there is an equivalent 3.x package, it will be pulled in (I hope), since zypper knows how to solve the dependencies.
If the dependencies are not pulled in automatically, try "zypper in --force yast2", which should reinstall the main package and its dependencies.
HTH, Werner
Just did a rpm -qa 'yast2*' every package is version -3. So that's not the problem. Thanks anyway. Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/21/2015 07:49 AM, Koenraad Lelong wrote:
Op 17-02-15 om 07:54 schreef Werner Flamme:
try a "rpm -qa 'yast2*' | sort" and look for the installed YaST modules. oS 12.3 came with YaST 2.x, while 13.1 introduced YaST 3.x. Uninstall each and every YaST2 package version 2.x (with "zypper rm ..."), if there is an equivalent 3.x package, it will be pulled in (I hope), since zypper knows how to solve the dependencies.
If the dependencies are not pulled in automatically, try "zypper in --force yast2", which should reinstall the main package and its dependencies.
HTH, Werner
Just did a rpm -qa 'yast2*' every package is version -3.
So that's not the problem.
Thanks anyway.
Just for paranoia's sake, you might want to do a # zypper verify and possibly a # zypper install-new-recommends --dry-run -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 13 of February 2015 19:24:25 Koenraad Lelong wrote:
Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2. After some problems with the video (solved) I can't get the Yast-gui to work. Running from the command-line I get this : /sbin/yast2: regel 440: 15837 Segmentatiefout $y2ccbin $Y2UI_ARGS "$@"
With the ncurses version of yast (I think) I forced to re-install all yast2-modules, but that didn't help.
Any suggestions ?
Try removing desktop-translations. If it is installed, memory corruption occurs in yast2. Has anyone else seen this? -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 21-02-15 om 08:22 schreef auxsvr@gmail.com:
Try removing desktop-translations. If it is installed, memory corruption occurs in yast2.
Has anyone else seen this?
Removed that, no solution. Thanks anyway Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday 21 of February 2015 13:50:40 Koenraad Lelong wrote:
Op 21-02-15 om 08:22 schreef auxsvr@gmail.com:
Try removing desktop-translations. If it is installed, memory corruption occurs in yast2.
Has anyone else seen this?
Removed that, no solution.
Thanks anyway
Could you run strace -e file /usr/lib/YaST2/bin/y2base sw_single qt to see the files accessed right before the segfault? In my case, they were the files in desktop-translations. If it is installed, both software management and online update crash right before the main screen is displayed, but the crashes only occur if they are launched remotely. -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 21-02-15 om 17:59 schreef auxsvr@gmail.com:
strace -e file /usr/lib/YaST2/bin/y2base sw_single qt
Last lines : stat("/var/log/YaST2/y2log", {st_mode=S_IFREG|0644, st_size=2791439, ...}) = 0 open("/var/log/YaST2/y2log", O_WRONLY|O_CREAT|O_APPEND, 0666) = 9 stat("/var/log/YaST2/y2log", {st_mode=S_IFREG|0644, st_size=2791526, ...}) = 0 open("/var/log/YaST2/y2log", O_WRONLY|O_CREAT|O_APPEND, 0666) = 9 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 stat("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", {st_mode=S_IFREG|0644, st_size=40, ...}) = 0 open("/usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/vendor/empty.mo", O_RDONLY|O_CLOEXEC) = 19 YaST got signal 11 at file /usr/share/YaST2/modules/Wizard.rb:431 +++ killed by SIGSEGV +++ Segmentatiefout -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 13/02/15 18:24, Koenraad Lelong wrote:
Hi,
Last weekend I upgraded my daughter's laptop from OS12.3 to OS13.2. After some problems with the video (solved) I can't get the Yast-gui to work. Running from the command-line I get this : /sbin/yast2: regel 440: 15837 Segmentatiefout $y2ccbin $Y2UI_ARGS "$@"
With the ncurses version of yast (I think) I forced to re-install all yast2-modules, but that didn't help.
Any suggestions ?
Just a thought, but is ruby properly installed? Dx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (10)
-
Anton Aylward -
auxsvr＠gmail.com -
Basil Chupin -
Bernhard Voelker -
Carlos E. R. -
David Haller -
Dylan -
Freek de Kruijf -
Koenraad Lelong -
Werner Flamme