Mailinglist Archive: yast-devel (55 mails)

< Previous Next >
Re: [yast-devel] more helpful error message (was: Re: [opensuse-factory] Leap 42.2 RC2 says internal ruby error on install)
On Thu, 10 Nov 2016 13:23:58 +0100
Christian Boltz <opensuse@xxxxxxxxx> wrote:

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@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References