[opensuse-factory] factory Y2 partitioner
for some time on factory the yast partitioner fails with YaST got signal 11 at YCP file StorageDevices.ycp:288 /sbin/yast2: line 399: 26922 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS The boot loader seems to be affected also. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, 06 Jun 2010 14:30:30 -0400, Dale Ritchey
for some time on factory the yast partitioner fails with YaST got signal 11 at YCP file StorageDevices.ycp:288 /sbin/yast2: line 399: 26922 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
The boot loader seems to be affected also.
Yea -- Web mail, POP3, and SMTP http://www.beewyz.com/freeaccounts.php -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 06 June 2010 20:48:08 Trifle Menot wrote:
On Sun, 06 Jun 2010 14:30:30 -0400, Dale Ritchey
wrote:
for some time on factory the yast partitioner fails with YaST got signal 11 at YCP file StorageDevices.ycp:288 /sbin/yast2: line 399: 26922 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
The boot loader seems to be affected also.
Yea
That's bad. Could you file a bugreport, please? Thanks, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 06/07/2010 03:16 AM, Andreas Jaeger wrote:
On Sunday 06 June 2010 20:48:08 Trifle Menot wrote:
On Sun, 06 Jun 2010 14:30:30 -0400, Dale Ritchey
wrote:
for some time on factory the yast partitioner fails with YaST got signal 11 at YCP file StorageDevices.ycp:288 /sbin/yast2: line 399: 26922 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
The boot loader seems to be affected also.
Yea
That's bad. Could you file a bugreport, please?
Thanks, Andreas
I checked and it looks like one is filed already http://bugzilla.novell.com/show_bug.cgi?id=610454 Martin Czeranski 2010-05-31 18:06:51 UTC Created an attachment (id=365933) [details] /var/log/YAST/y2log User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.4) Gecko/20100513 SUSE/3.6.4-1.12 Firefox/3.6.4 Start YAST2 Select System Select Partitioner Message if I want to continue appears, select YES After a few seconds error message YaST got signal 11 at YCP file StorageDevices.ycp:288 /sbin/yast2: Zeile 399: 27126 Speicherzugriffsfehler $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS popped up Partitioner terminates Factory update done on 2010-05-31 Happens on two different systems Reproducible: Always Steps to Reproduce: 1.Start YAST2 2.Select System 3.Select Partitioner Actual Results: Partitioner terminates with error Expected Results: Partitioner starts [reply] [-] Comment 1 Thomas Fehr 2010-06-01 08:10:12 UTC I just tried the same on Milestone 7 of openSuSE 11.3 and it works. The sources of yast2-storage and libstorage are the same on Milestone 7 and FACTORY so probably FACTORY was inconsistent at time of your install (as it is most of the time since it gets rebuilt almost continously). If this is reproducible on a Milestone or some other stable release, please reopen and attach y2log files. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Monday 07 June 2010 06:40:58 Dale Ritchey wrote:
On 06/07/2010 03:16 AM, Andreas Jaeger wrote:
On Sunday 06 June 2010 20:48:08 Trifle Menot wrote:
On Sun, 06 Jun 2010 14:30:30 -0400, Dale Ritchey
wrote:
for some time on factory the yast partitioner fails with YaST got signal 11 at YCP file StorageDevices.ycp:288 /sbin/yast2: line 399: 26922 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
The boot loader seems to be affected also.
Yea
That's bad. Could you file a bugreport, please?
Thanks, Andreas
I checked and it looks like one is filed already http://bugzilla.novell.com/show_bug.cgi?id=610454
Martin Czeranski 2010-05-31 18:06:51 UTC
Created an attachment (id=365933) [details] /var/log/YAST/y2log
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.4) Gecko/20100513 SUSE/3.6.4-1.12 Firefox/3.6.4
Start YAST2 Select System Select Partitioner Message if I want to continue appears, select YES After a few seconds error message YaST got signal 11 at YCP file StorageDevices.ycp:288 /sbin/yast2: Zeile 399: 27126 Speicherzugriffsfehler $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS popped up Partitioner terminates
Factory update done on 2010-05-31 Happens on two different systems
Reproducible: Always
Steps to Reproduce: 1.Start YAST2 2.Select System 3.Select Partitioner Actual Results: Partitioner terminates with error
Expected Results: Partitioner starts
[reply] [-] Comment 1 Thomas Fehr 2010-06-01 08:10:12 UTC
I just tried the same on Milestone 7 of openSuSE 11.3 and it works. The sources of yast2-storage and libstorage are the same on Milestone 7 and FACTORY so probably FACTORY was inconsistent at time of your install (as it is most of the time since it gets rebuilt almost continously).
If this is reproducible on a Milestone or some other stable release, please reopen and attach y2log files.
This also occurs for me on 2 different systems and again, AFTER a factory update OF MILESTONE 7 fresh install. It worked for M7 UNTIL the update which IMO was what was reported by the OP. who did supply you with logs which look essentially the same as what I show...repeatedly. I now have 2 machines that cannot adjust/change partitioning except by using things like FDISK and MDADM and LVM tools. Partitioner and Yast2 were broken by the update. Subsequent updates have not fixed this and have only added to the list of NEW failures of YAST2 and its modules as now NFS and SSH fail in a similar way IF you use YAST2 however, manual editing normally still work. Oh, add firewall modifications.... No, I'm not going to file a bug report...I'm afraid the same person will handle that/those reports in the same caviler and superficial way as this one and many like it have been handled. Richard -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
I didn't agree with the conclusion and reopened the bugreport - it occured as well on my system (without this thread I wouldn't have checked), Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Monday 07 June 2010 07:13:42 Andreas Jaeger wrote:
I didn't agree with the conclusion and reopened the bugreport - it occured as well on my system (without this thread I wouldn't have checked),
Andreas
Thank you Andreas. Too bad the bug-reporting system isn't as effective as the mail list threads. It seems as broken as the bugs being reported. I personally have been bitten by the "Ooooh, this is too hard" bug reports (especially in the system repair module arena as far back as 10.3) which often were closed even though not fixed simply because a new version came out. The repair system wasn't fixed, for example, from 10.3 to 11.0 and hasn't improved too much since then in major areas like handling RAIDs and LVMs, but the handling was, well, a new release, close, reopen if it still exists and we will ignore this one too because it is too hard. To me, fundamental tools like the partitioner and repair system should be the ones that work at all costs because when the system fails in some way, they are needed most to work. When the system is working, they aren't as needed, but a Linux convert from Doze needs those basic tools to have a hope to revive a dead system when an errant power failure has hosed his ability to boot his computer and the repair system or partitioner and other basic tools fail, even make it worse. Andreas, there are a few in the openSuSE/Novell camp that seem to really care, and overall, I think you belong on that list, but the list is woefully too short of late IMO and because of that, I am seeing increasingly people searching for alternatives. I have stuck with openSuSE so far because with one exception, (no, not 'buntu'), there are few that "Just work". I do, however, no longer recommend openSuSE as a first distro to Doze converts but so far, openSuSE overall is still the distro of choice despite the warts. Before openSuSE turns into the "elephant man" because of the increasing number of warts, I hope Andreas, that you can influence a return to the quality of attitude and product openSuSE once held. Richard -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Richard, I invite you to the discussion about openSUSE Strategy that should start the next days on opensuse-project. You raise some great questions and we should find answers for them together as a project. Thanks, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Richard Creighton schreef:
On Monday 07 June 2010 07:13:42 Andreas Jaeger wrote:
I didn't agree with the conclusion and reopened the bugreport - it occured as well on my system (without this thread I wouldn't have checked),
Andreas
Thank you Andreas. Too bad the bug-reporting system isn't as effective as the mail list threads. It seems as broken as the bugs being reported. I personally have been bitten by the "Ooooh, this is too hard" bug reports (especially in the system repair module arena as far back as 10.3) which often were closed even though not fixed simply because a new version came out. The repair system wasn't fixed, for example, from 10.3 to 11.0 and hasn't improved too much since then in major areas like handling RAIDs and LVMs, but the handling was, well, a new release, close, reopen if it still exists and we will ignore this one too because it is too hard.
To me, fundamental tools like the partitioner and repair system should be the ones that work at all costs because when the system fails in some way, they are needed most to work. When the system is working, they aren't as needed, but a Linux convert from Doze needs those basic tools to have a hope to revive a dead system when an errant power failure has hosed his ability to boot his computer and the repair system or partitioner and other basic tools fail, even make it worse.
Andreas, there are a few in the openSuSE/Novell camp that seem to really care, and overall, I think you belong on that list, but the list is woefully too short of late IMO and because of that, I am seeing increasingly people searching for alternatives. I have stuck with openSuSE so far because with one exception, (no, not 'buntu'), there are few that "Just work". I do, however, no longer recommend openSuSE as a first distro to Doze converts but so far, openSuSE overall is still the distro of choice despite the warts. Before openSuSE turns into the "elephant man" because of the increasing number of warts, I hope Andreas, that you can influence a return to the quality of attitude and product openSuSE once held.
Richard
Helas for me this is about the same... Not to be able to fix a broken system is the worst thing that can happen... Half broken or invalid pkgs, crappy x-drivers, to 'restore a 'glimps' of a desktop, keyboards that don't work, or apps that are half out of the monitor and cannot be moved..... it is getting a little too bad for me too.... Everything is so broken, you do not know where to start... And it even destroys working configs, to spent half an hour just to get things that worked, back to work again.... Should i say bye suse? -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Monday 07 June 2010 17:49:31 Oddball wrote:
Richard Creighton schreef:
On Monday 07 June 2010 07:13:42 Andreas Jaeger wrote:
I didn't agree with the conclusion and reopened the bugreport - it occured as well on my system (without this thread I wouldn't have checked),
<snip>
To me, fundamental tools like the partitioner and repair system should be the ones that work at all costs because when the system fails in some way, they are needed most to work. When the system is working, they aren't as needed, but a Linux convert from Doze needs those basic tools to have a hope to revive a dead system when an errant power failure has hosed his ability to boot his computer and the repair system or partitioner and other basic tools fail, even make it worse.
<snip>
Helas for me this is about the same... Not to be able to fix a broken system is the worst thing that can happen... Half broken or invalid pkgs, crappy x-drivers, to 'restore a 'glimps' of a desktop, keyboards that don't work, or apps that are half out of the monitor and cannot be moved..... it is getting a little too bad for me too.... Everything is so broken, you do not know where to start... And it even destroys working configs, to spent half an hour just to get things that worked, back to work again....
Yes, such things are indeed frustrating. It is why I don't recommend openSuSE to first-timers anymore. I now recommend one of several flavors of PCLinuxOS which do a good job of 'just working'. That said; as good as that distro is, it still is lacking in some of the more advanced areas of system configuration. It has no "Yast2" for instance, but does have a decent group of semi-integrated replacements. It fails worst in what SuSE's partitioner handles best, RAIDs and LVMs. It simply doesn't seem to support them (directly) but does still supply the CLI tools that get the job done. Since 10.3, I have used a rather complex combination of RAIDs and LVMs, so as the partitioner evolved, it made setting up increasingly complex (read useful) systems much easier. Alas, the repair system never has worked even to the point of attempting to FSCK the individual members of a RAID, etc.
Should i say bye suse?
I don't really think so. None of the distros are fault-free. My first choice for newbies comes close in many areas, but I can find fault without looking overly hard. SuSE *used* to have a reputation for both being on the (relative) cutting edge *and* stability. Alas, that reputation is sorely tarnished of recent times and no, I don't blame Novell for the most part. I do blame a lot of it on bad management of resources. Much more of it is poor attitudes of those "in charge" of their little niches within the openSuSE structure and by those individuals making bad decisions rather unilaterally about the direction and timing of events within the product. While many of the 'events' are somewhat beyond the direct control of these managers, (KDE for instance) often their poor decisions alienated often large subsets of the openSuSE userbase. In other words, replacing things that were relatively functional and stable with things that simply weren't ready yet for general distribution. To remain "cutting edge" infers taking some risks, but most of them can be done by leaving the tried and true in place and allowing alternative installations of the things that might, in the long run, be a step forward and better. Unfortunately, the tendency is to rip out the current, relatively stable and mostly debugged code and replace it with ultra new technology without considering all of the domino effect changes that occur, at least not thoroughly enough. So, that being said, if you say 'bye to suse' as you suggest, I suggest the current alternatives won't be a whole lot better in most cases for various and often quite different reasons than those affecting openSuSE. I subscribe to a fairly large number of distro support/user mail lists and see many of the same issues (sometimes a whole new group) being "discussed". So, I don't feel leaving openSuSE is a particularly good solution. Giving support to the good 'civilians' like Dotan that report "zillions" of bugs and to people like Andreas Jaeger that are part of the Novell/openSuSE management structure that repeatedly seem to do a lot more good than harm, is a better answer. Hopefully he and a few others, both in and out of management can do things to improve the general attitude of the organization(s) toward the userbase members. Hopefully the elitism of many of the gifted programmers that man the Buglist mechanism can be tempered with the realization that their programming ability doesn't make them smarter about what is good and right about openSuSE, but it simply gives the skills that many don't have to *implement* the programs that help achieve those goals. I am at the end of my "product cycle" in life now but I have written many tens of thousands lines of code in my time so I empathize with those that can program. Unfortunately, my skills were not in C++ or Java or some of the more recent "languages". So, I am somewhat unable to fix current program bugs myself so I can also empathize with the *users* of the programs which exhibit bugs and other undocumented features. I am not sure what the solution is, but I suspect it doesn't involve "running", but more likely involves an "attitude adjustment", both on the side of the Devs/management *and* the userbase members who are often too quick to anger. So, in a word, NO, not yet, don't leave, but do try to figure out a solution and work toward it. Sorry for the dissertation, but I really felt it needed to be said because both devs and bug-testers are here in this forum and it is here that the changes that need to be made can have the most effect, IMO. Richard -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, 7 Jun 2010 19:23:25 -0400, Richard Creighton
I am at the end of my "product cycle" in life now but I have written many tens of thousands lines of code in my time so I empathize with those that can program. Unfortunately, my skills were not in C++ or Java or some of the more recent "languages". So, I am somewhat unable to fix current program bugs myself so I can also empathize with the *users* of the programs which exhibit bugs and other undocumented features. I am not sure what the solution is
When you stop working you start dying. Why not learn C++. -- Web mail, POP3, and SMTP http://www.beewyz.com/freeaccounts.php -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 08 June 2010 01:23:25 Richard Creighton wrote:
[...] I am at the end of my "product cycle" in life now but I have written many tens of thousands lines of code in my time so I empathize with those that can program. Unfortunately, my skills were not in C++ or Java or some of the more recent "languages". So, I am somewhat unable to fix current program bugs myself so I can also empathize with the users of the programs which exhibit bugs and other undocumented features. I am not sure what the solution is, but I suspect it doesn't involve "running", but more likely involves an "attitude adjustment", both on the side of the Devs/management and the userbase members who are often too quick to anger.
openSUSE has evolved from SUSE Linux which was a distribution developed behind the firewall to a project with open mailing lists, bugzilla and wiki now to a real open source project. It's not anymore only Novell/SUSE employees that can do things - everybody in the community can get involved. That includes filing bug reports - like Richard does -, software translation, writing documentation, marketing the project and development. There might need to be some attitude adjustement for Novell developers for many of whom openSUSE is not the first priority and I'm happy to help with that when it gets pointed out to me. The question remains how to grow the openSUSE contributor community so that Richard doesn't need to learn C++ to get a bug fixed ;) If you like to continue this thread, please followup on the opensuse-project mailing list with a different subject, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Monday 07 June 2010 13:13:42 Andreas Jaeger wrote:
I didn't agree with the conclusion and reopened the bugreport - it occured as well on my system (without this thread I wouldn't have checked),
Bug is fixed ;) Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 06/07/2010 07:13 AM, Andreas Jaeger wrote:
I didn't agree with the conclusion and reopened the bugreport - it occured as well on my system (without this thread I wouldn't have checked),
Andreas
I fixed the problem on my machine by installing hwinfo from http://download.opensuse.org/distribution/11.3-Milestone7/ untill the fix hits factory -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (5)
-
Andreas Jaeger -
Dale Ritchey -
Oddball -
Richard Creighton -
Trifle Menot