[yast-devel] more helpful error message (was: Re: [opensuse-factory] Leap 42.2 RC2 says internal ruby error on install)
Hello, I'd like to propose a small, but IMHO important improvement: Am Donnerstag, 10. November 2016, 02:48:48 CET schrieb Carlos E. R.:
YaST2
Error
Internal error. Please report a bug report with logs. Details: Unknown udev device /dev/disk/by-label/msdos. Caller: /usr/share/YaST2/lib/bootloader/udev_mapping.rb:33:in `to_kernel_device`
Start the Ruby debugger now and debug the issue? (Experts only)!)
[Yes] No
Instructions? I have the laptop stopped at that point and waiting.
Logs? It is a ramdisk. Not that simple, but I can try if I can mount a partition. I suppose you want the /var/log/ - wait, it would be systemd journal? Or YaST logs?
What logs exactly do you want? Only the install ramdisk is available for commands.
It is not obvious for "normal users" [1] which logs are needed. Please change the error message so that it contains a hint about save_y2logs, for example: Error Internal error. Please report a bug report with logs. Run "save_y2logs" to collect the needed logfiles. <---- add this Details: [...] This one-line addition will make it easier for users and give you better bugreports. Bonus points if you also add the bugzilla URL ;-) Regards, Christian Boltz [1] Based on this definition (and after reporting several YaST bugs in the past, and even somewhat understanding the YaST log format), I probably don't count as "normal user" anymore ;-) -- For Linux an additional file permission should be invented: Stooge-Hidden. You set this permission on every file that average user does not understand. The flag does hide the file from the average user, because otherwise average user will cry at you for multiple weeks if they see the file, which might start to become pretty annoying. [Robert Schiele in opensuse-factory] -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Thu, 10 Nov 2016 13:23:58 +0100
Christian Boltz
Hello,
I'd like to propose a small, but IMHO important improvement:
Am Donnerstag, 10. November 2016, 02:48:48 CET schrieb Carlos E. R.:
YaST2
Error
Internal error. Please report a bug report with logs. Details: Unknown udev device /dev/disk/by-label/msdos. Caller: /usr/share/YaST2/lib/bootloader/udev_mapping.rb:33:in `to_kernel_device`
Start the Ruby debugger now and debug the issue? (Experts only)!)
[Yes] No
Instructions? I have the laptop stopped at that point and waiting.
Logs? It is a ramdisk. Not that simple, but I can try if I can mount a partition. I suppose you want the /var/log/ - wait, it would be systemd journal? Or YaST logs?
What logs exactly do you want? Only the install ramdisk is available for commands.
It is not obvious for "normal users" [1] which logs are needed.
Please change the error message so that it contains a hint about save_y2logs, for example:
Error
Internal error. Please report a bug report with logs. Run "save_y2logs" to collect the needed logfiles. <---- add this Details: [...]
This one-line addition will make it easier for users and give you better bugreports.
Bonus points if you also add the bugzilla URL ;-)
This looks good to me. About bugzilla URL we discuss also in past and only tricky way is how to properly report bugzilla.opensuse.org/bugzilla.suse.com on proper project. Otherwise opensuse community complains about using suse one with its branding and vise versa. Thanks for idea. Josef
Regards,
Christian Boltz
[1] Based on this definition (and after reporting several YaST bugs in the past, and even somewhat understanding the YaST log format), I probably don't count as "normal user" anymore ;-)
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Hello, Am Donnerstag, 10. November 2016, 13:45:45 CET schrieb Josef Reidinger:
On Thu, 10 Nov 2016 13:23:58 +0100 Christian Boltz wrote:
I'd like to propose a small, but IMHO important improvement: ... It is not obvious for "normal users" [1] which logs are needed.
Please change the error message so that it contains a hint about
save_y2logs, for example: Error
Internal error. Please report a bug report with logs. Run "save_y2logs" to collect the needed logfiles. <---- add
this Details: [...]
This one-line addition will make it easier for users and give you better bugreports.
Bonus points if you also add the bugzilla URL ;-)
This looks good to me. About bugzilla URL we discuss also in past and only tricky way is how to properly report bugzilla.opensuse.org/bugzilla.suse.com on proper project. Otherwise opensuse community complains about using suse one with its branding and vise versa.
Well, when this message appears, the user sees YaST exploding and burning - and complaining about a "wrong" bugzilla link is a luxery problem in this case ;-) Even as an openSUSE user, I'd argue that in doubt you should go for bugzilla.suse.com here, because SUSE pays your salery ;-) and SLE therefore wins. If someone really complains about the "wrong" link, you can send him/her to me ;-) and/or point to this mail. Yes, you could use an if condition, and in theory, YaST knows if it's running on SLE or openSUSE - but in a crash handler, every added complexity is too much IMHO. I don't want to see an "Error while displaying the error message" dialog ;-)) So: please don't think about this detail too much and integrate the improved message! Regards, Christian Boltz --
Ideally, upstream projects would care for AppArmor profiles (as much as they would care for SELinux), Oh, upstream projects really care for SELinux? ;-) At least as much as they do for AppArmor ;-) [> Christian Boltz and Sascha Peilicke in opensuse-factory]
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 10.11.2016 13:23, Christian Boltz wrote:
Run "save_y2logs" to collect the needed logfiles. <---- add this
Or, in the Qt UI
Press Shift-F8 or run "save_y2logs" to collect the needed logfiles.
It might be a bit tricky to get the user to save the logs to a permanent
location if this happens during the installation, though, because the
inst-sys runs from a RAM disk, so the logs will be gone after a reboot (which
is inevitable for most users in that situation).
See also
https://en.opensuse.org/SDB:YaST_tricks
https://en.opensuse.org/openSUSE:Report_a_YaST_bug#Attachments_-_y2logs.2C_h....
Kind regards
--
Stefan Hundhammer
participants (3)
-
Christian Boltz -
Josef Reidinger -
Stefan Hundhammer