Re: [VBox-users] alternate ways to report bugs

2021-11-06 Thread Fernando Cassia
On 29/10/2021, Cliff wrote: > Well said. I ran into the same issue when trying to file a bug report. I > didn’t want to share all that info so didn’t file the bug report. > > Regards, > Cliff Scott It sounds to me like the broad legalese terms of service used by all big corporations. I hope

Re: [VBox-users] alternate ways to report bugs

2021-10-29 Thread Cliff
Well said. I ran into the same issue when trying to file a bug report. I didn’t want to share all that info so didn’t file the bug report. Regards, Cliff Scott > On Oct 29, 2021, at 18:03, Gregory Nowak wrote: > > On Fri, Oct 29, 2021 at 08:35:56AM -0300, Fernando Cassia wrote: >> I don't

Re: [VBox-users] alternate ways to report bugs

2021-10-29 Thread Gregory Nowak
On Fri, Oct 29, 2021 at 08:35:56AM -0300, Fernando Cassia wrote: > I don't think anybody forces you to provide real information. Quoting from: 7. Security, Passwords and Means of Accessing the Site and Content "If any of the Services require you to open

Re: [VBox-users] alternate ways to report bugs

2021-10-29 Thread Fernando Cassia
On Fri., 29 Oct. 2021, 08:12 Brad Bell, wrote: > I have decided not to report my problem installing fedora34 in vbox > because of the issues discussed > below. > Sorry. I don't quite grasp what the issue is with creating an account. I don't think anybody forces you to provide real information.

Re: [VBox-users] alternate ways to report bugs

2021-10-29 Thread Brad Bell
I have decided not to report my problem installing fedora34 in vbox because of the issues discussed below. On 10/24/21 20:05, Gregory Nowak wrote: Hi all. Are there alternate ways to report VirtualBox bugs other than through the public tracker? I seem to also be experiencing bug #20499 since

[VBox-users] alternate ways to report bugs

2021-10-24 Thread Gregory Nowak
Hi all. Are there alternate ways to report VirtualBox bugs other than through the public tracker? I seem to also be experiencing bug #20499 since VirtualBox 6.1.24. When I noticed the issue still persists in 6.1.28, I started research into either reporting it, or finding an already open ticket.