Related topics

Bug#256668: g++-3.3 report internal error even on simplest program
However, this method merely gets the "bugs" filed somewhere - it does not currently guarantee that anyone will even look at them, let alone do something about it - you will almost certainly get no feedback so there is no way of knowing what has happened to your bug report. Can'tI report it to a Microsoft newsgroup?

How do I report a bug in the IDE?
Why should someone have to pay to report a bug? Bug reports are beneficial to both the consumer and the vendor, and so it doesn't make any sense that someone would have to pay to do this. No, it looked as if he wanted support. Bug reporting can be done via the bug report process I mentioned, or via e-mail.

NVidia Bug reporting
Ok. For example, from: Bug-Submit-To: sub...@bugs.debian.org to: Bug-Submit-To: qu...@bugs.debian.org This is a bad example, IMHO. I still maintain that the Bug-Submit-To field - whether it resides on the packages itself or in an origin conffile - should NOT include submit@ for the debbugs style of bug reporting.

Bug reporting
As to the bug reporting path: I do not know what sorts of support contracts are available in Australia. I do know that if you had a support contract directly with I did report the bug through the dealer; the only responses I've gotten back is: 1) It's not a bug; ps is supposed to do that; and 2) It's not a bug

if I report debian bugs will I get emailed for life?
However if you are certain that you have a bug you can report it by e-mail using cw_...@austin.metrowerks.com So it's okay if I just change my FormMaker's destination address to cw_bug for bug reports? Is there something I could use for "possibles"? You know, it's funny that after the Apple feedback sessio nat

Bug#466177: smbnetfs crashes
Jeff Overcash (TeamB) overc...@onramp.net borland public cppbuilder non-technical Edward Diener wrote: If there is going to be a new bug reporting system in the future, in which Borland is actually going to attempt to address bugs, it would be very nice of them if they can give the rest of us some clue as to when

Proposed revision of PEP 3 (using the issue tracker)
Peppe just wanted to point out that there is a special mailing list where bug and news features are being discussed - "vim-...@vim.org". Yes, I can understand that you may not want subscribe to this list for reporting a bug, but I'd like to point out that you should not expect that your bug report on comp.editors

Xah's Edu Corner: the bug-reporting attitude
Depends on the balance between my expectance of the bug report actually leading to a bugfix, and the effort required to report the bug. If I expect the bug report to lead to a bugfix, I go to significant lengths to report bugs (eg, the current gcc bug reporting system). As a vendor, when a user reports a bug,

Bug#466848: webkit - FTBFS: Undefined behaviour
El ds 16 de 02 del 2008 a les 12:03 +0000, en/na Debian Bug Tracking System va escriure: This is an automatic notification regarding your Bug report which was filed against the Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 458...@bugs.debian.org,

Fundamental flaw in bug reporting system
Wouldn't have an official bug reporting methodology, as MS used to have, be better than the either of the situations above ? I wouldn't even mind if someone notices the report and responds that they can not duplicate the problem, but to issue a bug report on an NG and have it completely ignored,

Bug#254676: xargs: environment is too large for exec
Henrique de Moraes Holschuh h...@debian.org linux debian project On Thu, 29 Jun 2006, Evan Prodromou wrote: On Thu, 2006-29-06 at 11:30 +0100, Ian Jackson wrote: I think that the difficulty of submitting a Debian bug report via the BTS (which is after all a fairly minor challenge to anyone who can read and

Bug reporting - Where??
Martin Schulze j...@infodrom.org linux debian devel Bernd Eckenfels wrote: Hello, how should an DD handle upstream bug reporting scripts (eg pre configured Gnats clients)? ircii for example ships a "ircbug" program for that purpose. I left it out, cause I expected the debian user to use the debian bug reporting.

Why should I report bugs to Opera when...
I'm going to partially disabuse you of this notion below. and I would like to know how to report them to Borland. As Stefan said the bug reporting process is currently being reworked completely. The second bug relates to virtual constructors. If V is a variable of type C, which is a class with a virtual constructor

filename contains ":" characters in scp?
A much better way would be a wizard, where first you only need to select what type of bug you would like to report, then the specialized bug reporting form should come up. The types I can think of are: PHP, PEAR, Documentation, Website There can be more in the future (eg. Smarty, PHP-GTK, etc).

What is the best way to report a bug?
Christian Gebauer geba...@bigfoot.com comp windows x kde Steve Loft wrote: I tried to use the bug report facility in knode 0.4 beta 4, and having filled it all in, I pressed 'send' and it told me it has sent it, but I don't believe anything left my machine. I have knode configured to use 'localhost' for SMTP as I

Integrating PEAR bug reporting into bugs.php.net
To a certain extent, I'm grateful for any bug reports, but obviously some are better than others - the less work I have to do the better :-) The following is a description of what I'd consider the second-best sort of bug report (the best of course, being a report that's accompanied by a patch file and ChangeLog

Bug report on SQL 7.0 same error as Q176479 for SQL 6.5
It would be too difficult to remove the name of whoever submitted the report wouldn't it? Or any information that was sensitive, for that matter... The complete report should be inaccessible to the public - the sensitive info is not just in the email address of the reporter. Only the date of the bug-report could

How to report bug on a (buggy) bug report?
It would be nice if they did it, but a novce user is perfectly free to just file a bug report. I know I often do. I find an error, usually that by itself is a frustrating experience, also, it is likely to be in the middle of a largish upgrade (I upgrade ever so often). I am not into going over and looking up stuff

#19022 [NoF]: PHP Warning: Failed to write session data (files)
"How to Report a Bug". Correct, MSDN and the beta testers are on the same build. The build includes the "How to report a bug" shortcut If you open it, it has a link to download the "beta client" bug reporting tool. That tool does not work. Isn't it supposed to? Only if you're on the technical beta Is it not working

#19022 [Com]: PHP Warning: Failed to write session data (files)
Matt Zimmerman m...@debian.org linux debian project On Tue, Jul 11, 2006 at 05:16:52PM +0100, Ian Jackson wrote: Adam McKenna writes ("Re: Fundamental flaw in bug reporting system"): Frustrating the user could lead to an even poorer quality bug report than would have been given in the first place.