[Bug 849571] New: yast2 apparmor crashes
https://bugzilla.novell.com/show_bug.cgi?id=849571 https://bugzilla.novell.com/show_bug.cgi?id=849571#c0 Summary: yast2 apparmor crashes Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: suse-beta@cboltz.de QAContact: jsrain@suse.com Found By: Beta-Customer Blocker: --- Created an attachment (id=566660) --> (http://bugzilla.novell.com/attachment.cgi?id=566660) y2log Using current factory, yast2 apparmor crashes after some clicks. Reproducer: - start yast2 apparmor - click "Manage existing profiles" - choose a profile (for example /sbin/klogd) - click "Next" - see YaST crashing The y2log is attached, other files in /var/log/YaST2 were not changed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=849571
https://bugzilla.novell.com/show_bug.cgi?id=849571#c
Arvin Schnell
https://bugzilla.novell.com/show_bug.cgi?id=849571
https://bugzilla.novell.com/show_bug.cgi?id=849571#c2
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=849571
https://bugzilla.novell.com/show_bug.cgi?id=849571#c3
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=849571
https://bugzilla.novell.com/show_bug.cgi?id=849571#c4
Christian Boltz
Christian - log lines above is not related. Why you think that YaST crashes?
Following the workflow I described as reproducer, I expected something to happen/be displayed after clicking "Next". I thought it's a crash (as in "disappears unexpectedly"), but maybe it just exited.
AppArmor was originally developed outside of Yast team, so there is some inconsistent UI decisions like that everything is done immediatelly and in fact button "Next" means only exit. What actually edit profile is "Edit" button. What is annoying that "Abort" and "Next" in fact do same thing. I agree that it is really bad UX, but I am not original author and if we change UI, I hope there is a designer who can create something much better then I.
Ah, now I notice there's an "edit" button on the left (where typically only the "Help" button is). Yes, that's really bad UX ;-) I expected the workflow to be select -> click "next" to edit it. It would be a good start to rename the "next" button to "Finish" (I'd guess that "Abort" is different and doesn't save edited profiles). For bonus points, move the "Edit" and "Delete" buttons to the right (at least that's the place where I typically look for buttons). BTW: the changelog mentions drop reporting and profile generation tools (FATE#308684,308683) I'd like to know some details/reasons, but those fate entries are non-public :-( I know reporting was disabled since a long time because the upstream code didn't support it anymore, but the profile generation part was working last time I tested it. So what was the reason for dropping it? (That said: personally, I prefer the commandline tools anyway, so I don't care too much - but it seems some users prefer clicking over typing ;-) I only noticed the changes in YaST after a user complained on the german ML.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=849571
https://bugzilla.novell.com/show_bug.cgi?id=849571#c5
Josef Reidinger
(In reply to comment #3)
Christian - log lines above is not related. Why you think that YaST crashes?
Following the workflow I described as reproducer, I expected something to happen/be displayed after clicking "Next". I thought it's a crash (as in "disappears unexpectedly"), but maybe it just exited.
Yes, it is probably result. as new Yast when crashes show something useful ( red error popup that internal error happen and message from ruby exception ).
AppArmor was originally developed outside of Yast team, so there is some inconsistent UI decisions like that everything is done immediatelly and in fact button "Next" means only exit. What actually edit profile is "Edit" button. What is annoying that "Abort" and "Next" in fact do same thing. I agree that it is really bad UX, but I am not original author and if we change UI, I hope there is a designer who can create something much better then I.
Ah, now I notice there's an "edit" button on the left (where typically only the "Help" button is). Yes, that's really bad UX ;-)
Yes, I am original author and also find it really strange. But I don't have time to modify it. Feel free to modify it, I welcome any pull request.
I expected the workflow to be select -> click "next" to edit it.
It would be a good start to rename the "next" button to "Finish" (I'd guess that "Abort" is different and doesn't save edited profiles). For bonus points, move the "Edit" and "Delete" buttons to the right (at least that's the place where I typically look for buttons).
And this is problem as big part of module is in perl and written stateless, so it cannot do last final commit, but do it immediatelly, so after three edits you cannot easily revert it.
BTW: the changelog mentions drop reporting and profile generation tools (FATE#308684,308683) I'd like to know some details/reasons, but those fate entries are non-public :-(
I know reporting was disabled since a long time because the upstream code didn't support it anymore, but the profile generation part was working last time I tested it. So what was the reason for dropping it?
OK, in short, reason is that upstream is not interested in maintaining it, so it means that if something is broken, I or other maintainer of yast2-apparmor must maintain such feature and it is definitively too big task to my available time and also my knowledge of apparmor is not big enough to maintain such task.
(That said: personally, I prefer the commandline tools anyway, so I don't care too much - but it seems some users prefer clicking over typing ;-) I only noticed the changes in YaST after a user complained on the german ML.)
It would be nice if such users can write to yast-devel or at least to opensuse-factory as yast-team base time allocation also on feeling how much users use given module and for apparmor it looks like almost no-one use GUI. I change title of bug and set priority properly as it is about UX and not crash. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=849571
Josef Reidinger
participants (1)
-
bugzilla_noreply@novell.com