Forum Bug Report

I'd like to report an irritating bug in the forum software.  I composed a post in an plain-text TextEdit window.  It had several paragraphs marked off by double carriage returns.  I then selected that text and pasted it into a forum message window.  Once pasted, each sequence of return-return had been replaced by return-space-return-space-return.  This is wasting my time, as when I use an auto-typing utility to paste in a multi-paragraph text block, I always have to go back in to delete the extra characters.

Hello Brent,
unluckily I think you misunderstood Michael original point.
Because some time passed, I too would like to report same issue again but let me explain and guide you (or others) how I too reached same sentence.
As of now even from your own 'Forums preferences' profile page you should be able to find on right side a
'Help' URL that leading to an intermediate page stating :
"The Frequently Asked Questions has Moved
The Forums help file has been moved to the
Community Wiki. Please update any bookmarks you may have."
Now a part from correcting that 'Help' URL once you or anyone reach 'Forums
Help (FAQ) - TechNet Articles - United States (English) - TechNet Wiki' you can find 'How
do I report issues with the Forums?' question, and then there's this other sentence :
"How do I report issues with the Forums?
You can report bugs, suggestions, and other issues for Forums, by performing one of the following actions:
Bug: If the issue seems like a bug in the forums code, go to the Bug Reporting Forum and report the bug
by using the template provided in the top forum thread.
But once anyone reach that Forum, now called 'Forums Issues (not product support)' there's no real forum bug reporting template in the top forum threads (as of now I only found 'Verify Your Account 15' and 'How to report
spam') and also to find this post thread I really had to search for "report a bug".
Regards
Rob

Similar Messages

  • Link to Bug Report Forum on Forum help page is dangling...

    The link Bug Reporting Forum (http://social.answers.microsoft.com/forums/en-us/reportabug/threads/) on page
    Answers >
    Forums Home
    > Help (http://social.answers.microsoft.com/Forums/en-US/help) is dangling. Makes it a bit more complicated than necessary to find this forum...
    Cheers, Michael

    Hello Brent,
    unluckily I think you misunderstood Michael original point.
    Because some time passed, I too would like to report same issue again but let me explain and guide you (or others) how I too reached same sentence.
    As of now even from your own 'Forums preferences' profile page you should be able to find on right side a
    'Help' URL that leading to an intermediate page stating :
    "The Frequently Asked Questions has Moved
    The Forums help file has been moved to the
    Community Wiki. Please update any bookmarks you may have."
    Now a part from correcting that 'Help' URL once you or anyone reach 'Forums
    Help (FAQ) - TechNet Articles - United States (English) - TechNet Wiki' you can find 'How
    do I report issues with the Forums?' question, and then there's this other sentence :
    "How do I report issues with the Forums?
    You can report bugs, suggestions, and other issues for Forums, by performing one of the following actions:
    Bug: If the issue seems like a bug in the forums code, go to the Bug Reporting Forum and report the bug
    by using the template provided in the top forum thread.
    But once anyone reach that Forum, now called 'Forums Issues (not product support)' there's no real forum bug reporting template in the top forum threads (as of now I only found 'Verify Your Account 15' and 'How to report
    spam') and also to find this post thread I really had to search for "report a bug".
    Regards
    Rob

  • Inclusion of a bug report section in Forum

    I had contacted Sony on this matter, that a Bug report Forum should be created or this functionality should be added in the existing Forum.
    I sent them tem this:
    would like to suggest you that you should start an interactive forum like website just for software updates wherein all bugs in software can be reported directly to Sony and if on the spot solution is there then should be provided and the reported bugs should be quickly removed through quick and frequent OTA updates for all Xperia Phones. This is a humble request and a must do for Sony. Regards.
    And got this:
    Greetings from Sony Xperia support.
    We would like to take this opportunity to express our appreciation for your interest in Sony products and services.
    We have taken this as a valuable feedback and we have forwarded the same to the consumer feedback division for their due consideration.
    Any update in this regard will be posted on our web site.
    If you need any assistance or clarifications, please feel free to contact Sony Xperia Support at the Toll Free number 1800-3000-2800 (Working Timings-9:00am to 9:00pm: Mon-Sun) alternately, you can email us at [email protected]
    For the latest news, information and product support please visit www.sonymobile.com/in
    Always looking to serve you better.
    Kind Regards,
    So this has to be done, where users can report bugs for their Xperia devices and Sony making use of them should quickly swnd a small firmware upgrade as soon as possible , making the users wait for 6 months or so for a bug fix update.

    Thank you again for sending us your feedback.
    At the moment we don't have any specific board for this on our forum but you can always submit any reports or issues you may experience via your local support or here on the forum (in the concerned models board).
     - Community Manager Sony Xperia Support Forum
    If you're new to our forums make sure that you have read our Discussion guidelines.
    If you want to get in touch with the local support team for your country please visit our contact page.

  • Do discussions (threads) in this forum ever get elevated to bug reports seen by the Adobe dev's?

    This forum is a fertile source of user feedback for Adobe. Is there a system in place to create tickets or bug reports or something like that out of issue brought up here? Seems like a good idea.

    User to User forum.
    Adobe may read some items here. That's up to the development teams. If the dev team sees something and is interested then it may perhaps get logged, But you should never assume anything on the forums is actually logged anywhere but here.
    If you've found a bug, you should log it using the feadback link at the bottom of this (or any) page.

  • Did you know that Google toolbar doesn't work properly in FF rc1? I have filed a bug report to Google about this

    The Google toolbar doesn't recognize a left mouse click when selecting a 'suggestion'. It's OK using the keyboard, however. I have filed a bug report with Google, but as this is an important extension thought you should know.

    See also:  http://forums.adobe.com/message/4662367#4662367
    -Noel

  • Bug Report: Feature Request/Bug Report Form

    Re: Feature Request/Bug Report Form
    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
    The Feature Request/Bug Report Form does not include a drop-down option for Creative Cloud.

    Hi Stephen,
    We are collecting feature requests as idea threads here on the forums versus using that form. If you believe you have discovered a bug with Creative Cloud please post about it here on the forums.
    Thanks,
    -Dave

  • Bug report: ignore not working

    Bug report: ignore in the forum here not working
    I set some SPAM users to 'ignore' - still can see their SPAM.
    Please fix it.

    The "Ignore a community user" feature will only block private messages received from other community users. See also the community help here: http://community.skype.com/t5/help/faqpage/faq-category-id/pm#pm
    Is that what you are referring to or do you expect this also to hide public messages posted by these users (which is not what it is currently designed to do).
    If you should spot content on the community that is violating our Community Guidelines please use the "Report inappropriate content" link from the "Post Options" menu next to the message. These abuse reports will then be reviewed by our moderation team.
    Follow the latest Skype Community News
    ↓ Did my reply answer your question? Accept it as a solution to help others, Thanks. ↓

  • Bug Report iOS 7 iTunes. Since it is repeatable on 3 iPhones and 4 iPads here, I'm sure others are experiencing the same thing. Apple, might want to take a peek at this. When a tv show or movie is deleted from Videos, the Videos app shuts down.

    Bug Report iOS 7 iTunes. Since it is repeatable on 3 iPhones and 4 iPads here, I'm sure others are experiencing the same thing. Apple, might want to take a peek at this. When a tv show or movie is deleted from Videos, the Videos app shuts down instead of returning to video playlist.
    Restarting videos works and looks like video is getting deleted.
    Just a bug report

    You might want to report that to Apple instead of to the other users in this forum.
    http://www.apple.com/feedback/iphone.html

  • Bug report 01

    Bug report 01
    In the ScoreWindow, with the INbutton activated, and
    with the WholeNoteSymbol selected in the PartBox :
    Playing a note on an external MIDI-keyboard will insert
    a note with any note length, EXCEPT the selected whole (1/1) note.
    Anybody experiencing the same problem ?
    Kind regards,
    Urban Utan
    Rotterdam.

    These are user-to-user forums, they are not monitored by Apple (there are too many forums/threads/messages for that to happen). If you want to leave feedback for Apple then you can do so here : http://www.apple.com/feedback/ipad.html

  • BUG REPORT FIRMWARE 5.1.7  PLEASE FORWARD TO SUPERVISOR....

    BUG REPORT FIRMWARE 5.1.7  PLEASE FORWARD TO SUPERVISOR.
    The spa-3102 has the following two bugs.
    When the unit sends a hook-flash to the fxo port it:
    a)      does not send the hook flash to the fxo port  for PSTN Hook Flash Len:  Instead it uses a very short pulse of about 100ms or 1/10 of a second.  It should honor the PSTN Hook Flash Len configurable parameter of .2 – 1.5 seconds.
    b)      Does not change the line voltage from –7 (off-hook) to –48(on-hook) during a flash-hook to the fxo port.  Instead it varies the voltage only by about 2.5 volts.
    This was reported as early as June 07 to linksys support.  It is reported they agreed and would fix in the next firmware release.  There is info that firmware 5.2 being released and is this fix in 5.2 and how can I get it.

    Although the problem is still not solved, at least I now know WHY the problem is happening... and Apple's Firmware Update is NOT to blame!
    Through a series of coincidences, I was actually lucky enough to get in touch with the engineers in Apple's Airport firmware division, and they were helping me to nail down this problem.
    Turns out that Apple takes great PRIDE in the fact that they are one of the VERY FEW manufacturers who make routers that behave properly in this regards: they SPECIFICALLY test for their Airport Extreme routers to allow you to connect to servers behind the NAT by way of the public WAN IP address of the NAT box. This is the way that apparently the NAT/DHCP specification is SUPPOSED TO WORK! You're SUPPOSED to be able to connect this way, if you so desire.
    So what was causing the problem on my network, then?
    Something I hadn't thought about... the Vonage Linksys RTP300 router that we're using for our Vonage VoIP service. Turns out that this router does NOT support clients behind the NAT connecting to servers behind the NAT by way of the public WAN IP address.
    Linksys is to blame, not Apple!
    And apparently, this feature may have actually been working in an earlier
    firmware update, but apparently, Vonage AUTOMATICALLY pushes firmware
    updates to RTP300's, apparently without user notification:
    <http://www.vonage.com/help.php?article=1066&category=90&nav=5>
    And a forum thread on vonage-forums.com seems to indicate that the 1.00.60 firmware in the RTP300 started getting pushed to customer units on or before 1/26/06, making it less than a month after Apple shipped the 5.7 firmware update for AirPort Extreme Base Stations:
    <http://www.vonage-forum.com/ftopic10915.html>. So if the problem cropped up then, it's possible that I accidentally attributed it to Apple when really the RTP300 got a firmware update around then too which may have broken this feature (assuming it was working before then).
    Power Mac G4 QuickSilver Dual 800 MHz   Mac OS X (10.4.4)  

  • Bug report: ube_ipa: internal error when compiling with -xO5

    When compiling imlib2-1.1.2, one source file causes compilation to fail with the following error message:
    ube_ipa: internal error
    cc: ube_ipa failed for loader_tiff.c
    The command which fails is (probably wrapped):
    cc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I.. -I../src -I../loaders -I../libltdl -I/usr/X11R6/include -I/usr/openwin/include -I/opt/csw/include -I/opt/csw/include -I/opt/csw/include -g -fast -xarch=386 -xstrconst -v -xildoff -xO5 -c loader_tiff.c -KPIC -DPIC -o .libs/loader_tiff.o
    Changing -xO5 to -xO4 works around the problem. The source file in question is imlib2-1.1.2/loaders/loader_tiff.c
    Patch 112756-10 has been applied, and doesn't correct the problem. GCC doesn't have any problem compiling the file.
    A quick note to any Sun employees reading this: it took me 45 minutes to find somewhere to submit this bug report. Searching sun.com for "submit bug report" turned up many forum postings where people asked "Where do I submit bug reports?", a bug report form for Sun One Java Studio, and not much else. It might be in your interest to make submitting bugs easier.

    Internal errors, such as the one you encountered, are generally considered compiler bugs. They indicate that the compiler reached an unexpected state and therefore bailed out. I opened bug 20703141: internal error: pic_relocs(): hh reltype? to investigate. I see the same error message emitted by the current Studio development release; I will update this thread if I find a work-around.
    Thanks,
    Mark

  • Sending a bug report on the OS and a sleep mode problem.

    I find the bug button in Safari really convenient for sending Apple bug reports. And when other applications crash, you usually get an error dialog with a button to send a bug report. But sometimes problems arise that require reporting, but which don't fall in either of these categories. It would be very handy to have a bug "button" for the OS, or perhaps just a menu selection in the Finder menu bar that invokes a bug report dialog box. I know you can dig around and find the URL for Apple's bug report web page, but I am always forgetting it -- I suppose I could just bookmark it, but then I'd just have to dig around in all the bookmarks to find it. Better would be a utility built-in to the OS for sending bug reports (like Safari's). It could also automatically transfer necessary info about the OS rev and such.
    The problem I had was this. I have a script that puts my iMac to sleep. I put the script alias on the task bar and a single click puts the computer to sleep (easier than using the menu). Unfortunately, I sometimes click it by mistake when I am trying to click an adjacent icon in the task bar, and the Mac starts going through its cycle to enter sleep mode and is impervious to anything I do to try and cancel it. I tried pressing the space bar continuously to prevent it from going to sleep, but that did not work. Worse, when it went to sleep and I woke it up again, the task bar would not appear, clicking on app windows did not activate them, Finder menus could not be selected, etc. The cursor would move, but I could not do anything else. (I wish now I had noted if the clock in the menu bar was still advancing, but I didn't think to do that.) I powered down the iMac from the power key and rebooted. Things are working fine now.
    I wanted to send a bug report on this, but realized that unlike Safari, there was no button or menu selection for doing that. So here I am.
    Any suggestions are welcome.
    TIA,
    Drake

    [email protected]
    1. If any post helps you please click the below the post(s) that helped you.
    2. Please resolve your thread by marking the post "Solution?" which solved it for you!
    3. Install free BlackBerry Protect today for backups of contacts and data.
    4. Guide to Unlocking your BlackBerry & Unlock Codes
    Join our BBM Channels (Beta)
    BlackBerry Support Forums Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • FAQ: I found a bug. How do I write a useful bug report? Or send bug files to Adobe?

    If you think you've found a bug in Photoshop CS6, please post your findings here on the forums.
    Here is a list of the information we'll want for you to gather at a minimum:
    Clear and concise steps so that someone who isn't in front of your comptuer can reproduce the issue you are seeing
    Include information on the operating system/version you are running. (e.g. "Mac OS 10.7.3" or "Win XP Service Pack 3")
    Here are some more detailed instructions for writing a useful, complete bug report for us on the forums:
    Provide a descriptive title that includes your OS information:Example: "Photoshop crashes when I save a JPEG file using the File>Save For Web & Devices... command (Mac OS 10.7.3)"
    Provide concise, step-by-step details on how to reproduce the issue you are seeing.
    Example:
    Open an 8-bit, RGB image by selecting File>Open...
    Create a new layer by clicking the "Create New Layer" button on the bottom of the Layers panel
    Paint on the layer created in Step #2 using the default Brush tool
    Choose File>Save For Web & Devices...
    Make sure the optimized format is set to "JPEG" and set the Quality setting to "80"
    Click the Save button at the bottom of the Save For Web & Devices dialog, choose the desktop as the location for saving the file
    Provide a description of the "Result" you are observing:
    Example: "Result: Photoshop crashes"
    If there is an error dialog, please include the exact wording displayed in the dialog or provide a screen shot or video of the entire screen so we can see the dialog as well as the state of the application - i.e. what panels are shown, the state of the Layers panel, etc.
    If the error is a visual defect, either in the user interface or the image itself, provide a screen shot or video of the entire screen so we can see the dialog as well as the state of the application - i.e. what panels are shown, the state of the Layers panel, etc.
    Provide a description of the "Expected Result":
    Example: "Expected Result: Photoshop to save JPEG file to the desktop, no crash"
    In some cases this may be obvious (such as in the case of a crash) but in others, what you expect to happen may be different than what the application was designed to do. Please be as specific as possible.
    Provide the crash log by submitting all crash reports, including your email address, for every single crash your encounter:
    You may also include the contents of your crash log in your forum posts as well, but always submit them using the above instructions as well.
    Crash logs are located on Macintosh here: Users/<your user name>/Library/Logs/CrashReporter
    Provide your System Info from Photoshop: What's even more useful is if you can share your System Info from Photoshop as it contains all kinds of useful information (OS/version, graphics card, driver version, 3rd party plug-ins used, etc) that will help the team track down your issue.
    On occasion, the Photoshop engineers may request that you provide problematic files in order to reproduce and debug your issue.
    In these cases, please post the file somewhere using your own servers or one your favorite online document/distribution services and provide a URL/instructions to download the file:
    Dropbox
    Adobe SendNow
    YouSendIt
    If the file isn't something you can post publically, you can request that someone from the engineering team contact you to figure out a secure way to get the affected files.
    Thanks,
    The Photoshop Development Team

    First thing would be to realise the exact error. Second would be to check your logs to see what you have installed/upgraded which might be causing this error. Third, google your error and see if matches turn up. Fourth, search in Arch bugtracker to see if a match exist. Else file a report.

  • FAQ: How do I submit a bug report or feature request or otherwise give feedback about Premiere Pro?

    The best way to submit a bug report or feature request is to use the bug-report/feature-request form.
    The Premiere Pro team doesn’t  necessarily see and record every post on every forum and social network, but we do see, record, and track every entry  through the the official feature-request/bug-report form.
    It also helps a lot if you opt into the Product Improvement Program.
    Also, be sure to use the crash reporter.
    We really do read all of the bug reports and feature  requests, and the software really does get a lot of benefit from  detailed crash reports.
    Don’t forget about contacting Adobe Technical Support or Customer  Service, too. For information on how to contact Adobe Technical Support,  see this page. (Note that you must register your product before you can open a technical support case for it.)
    If you have tried to get help from our support staff, but the service  was inadequate, I can help you to escalate your issue if you send me  your case number at kopriva at adobe dot com. You must provide me  a case number. I am not offering to solve your problem myself; rather, I  am willing to forward your information to someone if you have already  hit a dead end with our Technical Support or Customer Service.
    If you have feedback about the content of the Premiere Pro Help document,  then please add a comment at the bottom of the relevant page. You can  add comments to add information, to add links, to make corrections, or  to ask for clarification.
    If you want to keep up with the Premiere Pro team, then you can follow our blogs, Facebook page, and Twitter feed and so on.
    Oh, and I can’t resist this opportunity to remind you to update to  the most recent version of the application. Don’t be surprised when the  first thing that you hear back from us is that you need to install the  latest updates. We fix a lot of things in updates, and we don’t want to go chasing bugs that we’ve already fixed. We’ll keep you posted on our blogs, Facebook page, and Twitter feed about updates as they become available.

    Hi qwerty,
    Dun tink that creative customer support sucks cos I had been dealing with them in the past and I can say that their service are quite gd and fast. If you wanted a refund, I tink you need to contact the store that sells you the product. Dun tink creative will refund you though.

  • How and where can I submit a bug report to Nokia ?

    How and where can I submit a bug report to Nokia ? I haven't found any Nokia's webpage where it is explained.

    wait for the next nokia beta test program (they usually annouce it on this forum) and enrol
    then you will have access to the developers to report bugs
    the last beta test finished end of November.. so it will be a while b4 the next beta test
    cheers
    Nokia N95 8GB, 6234, 6101, N-Gage Classic, 8250, 3350, 3315

Maybe you are looking for