RH bug reports sent to dead Macromedia address

When one reports a RoboHelp bug through
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform,
the bug report is apparently submitted to a no longer existing
Macromedia address.
One gets an e-mail bach with the error message: "Your message
did not reach some or all of the intended recipients. Subject: [
Bug Report ] Sent: [Date]. The following recipient(s) could not be
reached: [email protected] The e-mail account does not
exist at the organization this message was sent to."
Other than being an insult to the RH user community, it ought
to be in Adobe's own interest to get bug info from their users.
Anyone knows an Adobe address to which we can send RH bug reports
(and expect them to be read)?

The link to the page is as below, without the comma at the
end.
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
I just tested it and it worked fine. I got an acknowledgement
immediately. Also I can confirm that all the bug reports and
feature requests do get read and considered.
Try again Morten and see what happens. Nobody has reported
this before so I think there must have been a glitch.

Similar Messages

Bug report sent to my email by my phone? bug report?

obake-maxx_verizon-user 4.4 SU2-3 15 release-keys

No need to worry alyoops! This is a report generated the Android OS when the phone experiences function delays, apps force close, freezing or other app-related issues. This is to be used by the software developer and you may have triggered it by pressing the key sequence unintentionally.
AdaS_VZW
Follow us on Twitter at @VZWSupport

Apple Bug Reporter won't let me sign in

Don't know where else to post this. When I try to sign into the Apple Bug Reporter with my correct email address and password, it redirects to the same login page with no error message.

Hi ..
If you are using Safari to try and login to the bug reporter ...
From your Safari menu bar click Safari > Preferences then select the Privacy tab.
Click Details. Type Apple in the search field then remove all results.
Now empty the Safari cache. Press Command + Option + E
Quit and relaunch Safari and try logging in.

Bug report, Beta 2.12 Standard Edition

Bug report: redundant, confusing, and apparently erroneous calls to
jdoPreClear
and jdoPostLoad. Note in output the null name in the third iteration.
Hi,
A lot of information being sent. Sorry, but I think you'll find it
helpful. I expected the exact same sequence of calls to jdoPreClear
and jdoPostLoad on the 2nd and third iteration. In fact, since,
retain values is true, and no changes are being made, I expected that
jdoPreClear and jdoPostLoad would not be called at all on the 2nd and
3rd iteration.
David Ezzio
Using 2.12 Beta, standard edition
Business method uses one PM. Configured to datastore transaction,
retainValues == true, non-TR == false, and non-TW == false.
The business methods open a transaction and leave it open.
The client calls commitTransaction() to close the open
transaction.
Two persistent objects, Widget and Box. Each implement
InstanceCallbacks and put out a message in jdoPreClear ("will be
made hollow") and in jdoPostLoad ("has been made persistent-clean").
The Widget has a reference to its Box. The number in parenthesis
is the sequence number obtained from the object ID.
Business methods implementation:
public ArrayList getWidgetsByName(String name)
Transaction trans = pm.currentTransaction();
if (!trans.isActive())
trans.begin();
Collection c = (Collection) widgetsByOneName.execute(name);
ArrayList aList = new ArrayList(c);
widgetsByOneName.close(c);
return aList;
public void commitTransaction()
Transaction trans = pm.currentTransaction();
if (trans.isActive())
trans.commit();
Output: from three loops that:
call findWidgetsByName("Maxi-Widget")
list the widgets returned
call commitTransaction()
finding Maxi-Widgets ...
Widget Maxi-Widget (650) has been made persistent-clean
Box Large (652) has been made persistent-clean
Widget Maxi-Widget (650): Box Large (652) at location Top Shelf
Widget Maxi-Widget (709) has been made persistent-clean
Box Large (710) has been made persistent-clean
Widget Maxi-Widget (709): Box Large (710) at location Middle Shelf
Widget Maxi-Widget (708) has been made persistent-clean
Box Large (713) has been made persistent-clean
Widget Maxi-Widget (708): Box Large (713) at location Top Shelf
Widget Maxi-Widget (700) has been made persistent-clean
Box Large (717) has been made persistent-clean
Widget Maxi-Widget (700): Box Large (717) at location Top Shelf
Widget Maxi-Widget (707) has been made persistent-clean
Box Large (716) has been made persistent-clean
Widget Maxi-Widget (707): Box Large (716) at location Top Shelf
Finding them again
finding Maxi-Widgets ...
Widget Maxi-Widget (650) will be made hollow
Widget Maxi-Widget (650): Box Large (652) at location Top Shelf
Widget Maxi-Widget (709) will be made hollow
Widget Maxi-Widget (709): Box Large (710) at location Middle Shelf
Widget Maxi-Widget (708) will be made hollow
Widget Maxi-Widget (708): Box Large (713) at location Top Shelf
Widget Maxi-Widget (700) will be made hollow
Widget Maxi-Widget (700): Box Large (717) at location Top Shelf
Widget Maxi-Widget (707) will be made hollow
Widget Maxi-Widget (707): Box Large (716) at location Top Shelf
Finding them yet again
finding Maxi-Widgets ...
Widget null (650) will be made hollow
Widget Maxi-Widget (650) has been made persistent-clean
Widget Maxi-Widget (650): Box Large (652) at location Top Shelf
Widget null (709) will be made hollow
Widget Maxi-Widget (709) has been made persistent-clean
Widget Maxi-Widget (709): Box Large (710) at location Middle Shelf
Widget null (708) will be made hollow
Widget Maxi-Widget (708) has been made persistent-clean
Widget Maxi-Widget (708): Box Large (713) at location Top Shelf
Widget null (700) will be made hollow
Widget Maxi-Widget (700) has been made persistent-clean
Widget Maxi-Widget (700): Box Large (717) at location Top Shelf
Widget null (707) will be made hollow
Widget Maxi-Widget (707) has been made persistent-clean
Widget Maxi-Widget (707): Box Large (716) at location Top Shelf
-- All done!

Due to better understanding on my part, and the fixes in Beta 2.2, the
issues raised in this thread are put to rest.
Abe White wrote:
>
We'll investigate further. Stay tuned...
"David Ezzio" <[email protected]> wrote in message
news:[email protected]..
Abe,
Actually, it doesn't make sense. The first iteration shows
jdoPostLoad is called just prior to using the fields of Widget and Box.
After the commit, the instances are not cleared. So far, so good.
In the second iteration, we see that jdoPreClear is called, but
jdoPostLoad is not called. Yet the values are there for use during the
call to Widget.toString() and Box.toString() within the iteration. How
did that happen?
On the third iteration, now the value of name is null, but last we
looked it was available in the second iteration. Other than that, I
agree that the third iteration looks ok, since it is being cleared and
loaded prior to use. But in the jdoPreClear, the values should be there
since the values were used in the previous iteration and are not cleared
at transaction commit due to retainValues == true.
David
Abe White wrote:
David --
I believe the behavior you are seeing to be correct. Section 5.6.1 of
the
JDO spec outlines the behavior of persistent-nontransactional instancesused
with data store transactions. As you can see, persistentnon-transactional
instances are cleared when they enter a transaction; thus the calls to
jdoPreClear. When the default fetch group is loaded again (like whenyou
access the name of the widget) a call to jdoPostLoad is made.
You are seeing the name of one instance as 'null' in the third iterationof
your loop because the instance has been cleared in the second iteration,and
the jdoPreClear method is not modified by the enhancer (see section10.3).
Make sense?

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)

KSLD bug report: 32 bit causes target panic

Since the bug report link:
http://soldc.sun.com/developer/support/driver/tools/KSLD/bug-report.html
goes to a non existant email address, I thought I would post here.
Setup:
ksld 1.01
target and host booted with kernel/unix (32 bit)
/proto directory struct as described in starting ksld doc
debugging ramd driver example
ramd directory:
drwxr-xr-x 4 root other 512 Feb 11 12:40 .
drwxr-xr-x 10 root other 512 Feb 11 12:47 ..
drwxrwxrwx 2 bin bin 512 Feb 11 10:26 777
-rw-r--r-- 1 root other 341 Feb 11 11:31 Makefile
-rw-r--r-- 1 root other 1610 Apr 24 2001 README
-rw-r--r-- 1 root other 3588 Apr 18 2001 install
lrwxrwxrwx 1 root other 52 Feb 11 10:47 misc -> /export/home/ksld-space/proto/root_sparc/kernel/misc
-rw-r--r-- 1 root other 2523 Apr 18 2001 ntestram.c
-rw-r--r-- 1 root other 2542 Apr 18 2001 printinfo.c
lrwxrwxrwx 1 root other 6 Feb 11 10:46 proto -> /proto
-rw-r--r-- 1 root other 25713 Feb 11 11:29 ramd.c
-rw-r--r-- 1 root other 291 Apr 18 2001 ramd.conf
-rw-r--r-- 1 root other 210 Apr 18 2001 ramio.h
drwxrwxrwx 4 bin bin 512 Feb 11 19:51 sparc
-rw-r--r-- 1 root other 1785 Apr 18 2001 testram.c
lrwxrwxrwx 1 root other 67 Feb 11 10:48 unix.281 -> /export/home/ksld-space/proto/root_sparc/platform/sun4u/kernel/unix
HOST output
home1# ksld -t hardwire unix.281 99
Reading unix.281
KSLD v1.0 on sun4u [SunOS 5.8]
Current thread is 0x4001fe60
Reading krtld
Reading genunix
Reading platmod
Reading SUNW,UltraSPARC-II
Reading specfs
Reading TS
Reading TS_DPTBL
Reading ufs
Reading fssnap_if
Reading rpcmod
Reading ip
Reading rootnex
Reading options
Reading sad
Reading pseudo
Reading sd
Reading scsi
Reading glm
Reading pcipsy
Reading dada
Reading todmostek
Reading procfs
Reading sockfs
Reading clone
Reading ip6
Reading tcp
Reading md5
Reading tcp6
Reading udp
Reading udp6
Reading icmp
Reading icmp6
Reading arp
Reading timod
Reading conskbd
Reading wc
Reading ebus
Reading su
Reading kb
Reading ms
Reading consms
Reading se
Reading elfexec
Reading fifofs
Reading ldterm
Reading ttcompat
Reading zs
Reading ptsl
Reading ptc
Reading rts
Reading tl
Reading keysock
Reading sysmsg
Reading cn
Reading pipe
Reading mm
Reading hme
Reading ufs_log
Reading doorfs
Reading devinfo
Reading iwscn
Reading log
Reading sy
Reading fctl
ksld_dbx: can't stat /platform/sun4u/kernel/drv/afb -- No such file or directory
Reading afb
ksld_dbx: can't open /platform/sun4u/kernel/drv/afb -- No such file or directory
Reading fd
Reading busra
Reading cs
Reading winlock
Reading seg_drv
Reading usba
Reading kstat
Reading vol
Reading cpc
Reading tnf
Reading pcihp
Reading hpcsvc
Reading pcicfg
Reading nfssrv
Reading nfs
Reading rpcsec
Reading tlimod
Reading seg_mapdev
Reading inst_sync
Reading mntfs
Reading tmpfs
Reading klmmod
Reading autofs
Reading connld
Reading bootdev
Reading shmsys
Reading ipc
Reading ramd
Reading kaio
detected a multithreaded program
t@0 stopped in (unknown) at 0xedd000d8
0xedd000d8: ta %icc,%g0 + 125
(ksld_dbx) module -v ramd.o
Module: ramd.o
Language: ansic
Debugging information: read [stabs version: 3.1]
Source file: /opt/SUNWddk/src/drivers/ramd/ramd.c
Object file: /opt/SUNWddk/src/drivers/ramd/sparc/obj32/ramd.o
Loadobject: /usr/kernel/drv/ramd
(ksld_dbx) stop in ram_strategy
(2) stop in ram_strategy
poll in failed
can't set breakpoint
TARGET output:
connected
New connection: uid 0, fd 7
Begin traceback... sp = edd48290
Called from edd009dc, fp=edd47b41, args=34 edd308ee eddc40a8 34 edd042f0 edd042ec
Called from edd03624, fp=edd47c11, args=fff74000 edda51f0 102d087a ffffffff91d0207e 0 4
Called from edd0c0d0, fp=edd47cd1, args=102d087a 91d0207e ff1bd714102d087a 100 edd48608 27
Called from edd0a394, fp=edd47d81, args=eddb7788 8 eddc16a1 f0000 1 ffff
Called from edd176d4, fp=edd47e31, args=ffff eddb7788 0 1 0 eddc1690
Called from edd0e470, fp=edd47f41, args=edd49058 0 0 3c 0 edda69d8
Called from edd0e214, fp=edd47ff1, args=eddb6d58 eddc1690 edd49158 ffffffffffffffff 10000 edd483e0
Called from edd0e154, fp=edd480a1, args=eddc1640 edda3550 0 0 0 0
Called from edd071b4, fp=edd48121, args=0 0 0 0 0 0
Called from 0, fp=0, args=0 0 0 0 0 0
End traceback...
abort jump: trap 34 sp edd48290 pc edd042ec npc edd042f0
etext edd308ee estack edd489a0 edata edda2388 nofault edda2658
ksld_kadb[0]: (`o403P0801So6mLD42d8N_lK^bH00004)(`o403P0801So6mLD42d8N_lK^bH0000
panic[cpu0]/thread=4001fe60: BAD TRAP: type=34 rp=4002fbc0 addr=40030507 mmu_fsr=0
sched: alignment error:
addr=0x40030507
pid=0, pc=0xedd2ba78, sp=0x4002fc50, tstate=0x1404, context=0x0
g1-g7: 1000c000, edda1f78, edda1f78, 0, edda2658, 14aef0, 4001fe60
panic: entering debugger (continue to save dump)
Trap 7d
What is wrong with the setup,when a breakpoint would cause a traceback and panic on the target?

One other possibility is having sufficient rights, especially if you are invoking it via some other app, rather than manually as a logged in user. If you are not logged in and instead invoke it via a web site action, I believe you will have problems reading the registry, accessing a desktop, writing to disk, etc.
Sorry I can't be more definitive, but perhaps it will help.
Please post your conclusion, if you find it.
--Ian

Help! Macbook Pro Keeps Crashing. Here Is The Bug Report

Please, please, please can someone help me my mac keeps crashing for the last week and I dont know why.
I keep getting the grey screen of death
I have included the bug report below.
Mac Specs
I have a Macbook Pro 17"
Model Identifier: MacBookPro8,3
Late 2011 Version
2.2ghz Intel Core i7
Intel HD Graphics 3000 512 MB
Software OS X 10.9.4 (13E28)
I am running the OS off an SSD 750 GB Drive connected internally (have been for over a year with no issues)
The drive that came with my mac got corrupted so I replaced it with the SSD
I am using an external monitor AOC connected via thunderbolt (have had this set up for over 1.5 years with no issues.
Bug Report
Anonymous UUID: DDEA4723-7244-E776-B61A-34B381E8523F
Tue Jul 29 23:34:57 2014
panic(cpu 5 caller 0xffffff8003e4e5ca): "A kext releasing a(n) GenericUSBXHCI has corrupted the registry."@/SourceCache/xnu/xnu-2422.110.17/libkern/c++/OSObject.cpp:218
Backtrace (CPU 5), Frame : Return Address
0xffffff81ee4cbe00 : 0xffffff8003a22f79
0xffffff81ee4cbe80 : 0xffffff8003e4e5ca
0xffffff81ee4cbed0 : 0xffffff8003e9b6e7
0xffffff81ee4cbef0 : 0xffffff8003ea9d0f
0xffffff81ee4cbf30 : 0xffffff8003eaf292
0xffffff81ee4cbf80 : 0xffffff8003eaf367
0xffffff81ee4cbfb0 : 0xffffff8003ad7417
BSD process name corresponding to current thread: kernel_task
Mac OS version:
13E28
Kernel version:
Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64
Kernel UUID: BBFADD17-672B-35A2-9B7F-E4B12213E4B8
Kernel slide: 0x0000000003800000
Kernel text base: 0xffffff8003a00000
System model name: MacBookPro8,3 (Mac-942459F5819B171B)
System uptime in nanoseconds: 49357323350
last loaded kext at 46443091940: com.apple.driver.AppleBluetoothMultitouch 80.14 (addr 0xffffff7f858c1000, size 77824)
loaded kexts:
com.bresink.driver.BRESINKx86Monitoring 9.0
com.avatron.AVExFramebuffer 1.7
com.displaylink.driver.DisplayLinkDriver 2.1
net.telestream.driver.TelestreamAudio 1.1.0
com.techsmith.TACC 1.0.2
com.logmein.driver.LogMeInSoundDriver 1.0.3
com.avatron.AVExVideo 1.7
com.sonnet.driver.SXHCD 1.27.9b2
net.osx86.kexts.GenericUSBXHCI 1.2.7
com.apple.driver.AppleBluetoothMultitouch 80.14
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.2.6f1
com.apple.driver.AGPM 100.14.28
com.apple.driver.AppleTyMCEDriver 1.0.2d2
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.ApplePolicyControl 3.6.22
com.apple.driver.AppleMikeyDriver 2.6.3f4
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.kext.AMDFramebuffer 1.2.4
com.apple.driver.AppleHDAHardwareConfigDriver 2.6.3f4
com.apple.iokit.IOBluetoothUSBDFU 4.2.6f1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.6f1
com.apple.driver.AppleHDA 2.6.3f4
com.apple.driver.AppleHWAccess 1
com.apple.AMDRadeonX3000 1.2.4
com.apple.driver.AppleIntelMCEReporter 104
com.apple.driver.AppleIntelHD3000Graphics 8.2.4
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleThunderboltIP 1.1.2
com.apple.kext.AMD6000Controller 1.2.4
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleIntelSNBGraphicsFB 8.2.4
com.apple.driver.AppleMuxControl 3.6.22
com.apple.driver.AppleBacklight 170.3.5
com.apple.driver.AppleMCCSControl 1.2.5
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyEventDriver 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleIRController 325.7
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.XsanFilter 404
com.apple.driver.AppleUSBXHCI 683.4.0
com.apple.driver.AppleUSBHub 683.4.0
com.apple.iokit.IOAHCIBlockStorage 2.6.0
com.apple.driver.AppleFWOHCI 5.0.2
com.apple.driver.AirPort.Brcm4331 700.20.22
com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
com.apple.driver.AppleAHCIPort 3.0.5
com.apple.driver.AppleUSBEHCI 660.4.0
com.apple.driver.AppleUSBUHCI 656.4.1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 217.92.1
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 217.92.1
com.apple.driver.IOBluetoothHIDDriver 4.2.6f1
com.apple.driver.AppleMultitouchDriver 245.13
com.apple.kext.triggers 1.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.iokit.IOSurface 91.1
com.apple.iokit.IOBluetoothFamily 4.2.6f1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.6f1
com.apple.driver.DspFuncLib 2.6.3f4
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAcceleratorFamily 98.22
com.apple.driver.AppleThunderboltEDMSink 2.1.3
com.apple.driver.AppleThunderboltDPOutAdapter 3.1.7
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.kext.AMDSupport 1.2.4
com.apple.AppleGraphicsDeviceControl 3.6.22
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleHDAController 2.6.3f4
com.apple.iokit.IOHDAFamily 2.6.3f4
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.7.1d6
com.apple.driver.AppleUSBAudio 2.9.5f8
com.apple.iokit.IOAudioFamily 1.9.7fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.driver.AppleSMC 3.1.8
com.apple.driver.AppleGraphicsControl 3.6.22
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleSMBusController 1.0.12d1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
com.apple.driver.AppleUSBMultitouch 240.9
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.driver.AppleThunderboltNHI 2.0.1
com.apple.iokit.IOThunderboltFamily 3.3.1
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IO80211Family 640.36
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.iokit.IOUSBFamily 683.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.11.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 23
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0

Looks like the Open Source USB 3.0 driver GenericUSBXHCI is causing this. I'd suggest uninstalling it.

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.

Since I can not log in bug report page, not even getting an error message, I'll write all my issues with ios8 here...

Since I can not log in bug report page, not even getting an error message, I'll write all my issues with ios8 here... I have an iphone 4S and I did the last update. Now I am in trouble.
1. When I move the "sound on/off" button, I get it buzzing 10 times before the setting is changed and I can do anything else, just not reacting to the round button on screen touches.
2. Impossible to copy text from most websites into notes.
3. Impossible to delete an email account in settings.
4. Uses up the battery twice as fast as before. I have "update apps" setting turned off, just reading a couple of mails, making a couple of photos and open maps apps twice a day, and the battery is dead well before the evening.
5. Got extremely slow, and it was getting slower and slower with every system update.
I'm sure I forgot something... But well, that already a lot.

Well, actually number 3 in my list is not true any more, I just tried to delete my account 15 times, then I've written my post, then half an hour later my Settings finally updated my accounts list. Whohoo
I did not try restoring it yet, thank you for the link!

Blur Problems (bug report submitted)

I've submitted a bug report and will submit this again since its a better version of when I sent them before. The problem is this:
- Adobe Acrobat Professional shows blur in certain situations. In another situation, the same file opens correctly. The file below is self-explanatory, i.e.:
1. This is what you see when you do a fresh start, with no pre-existing Adobe processes running. Sometimes though the blur will show up even if its a fresh start.
2. Thats what you see when the file has been closed but Acrobat Professional is still running and open.
If anyone needs the original PDF, it can be downloaded at:
http://www.2shared.com/document/P927Y4Vm/scanned-doc-2.html
In area 1, you can see the glaring difference in visual quality. The blur makes it very hard and irritating to read the PDF. Notice how the blur alternates. Some areas are sharp while others are soft. Area 2 is how it should always look like (crisp).
If you cant see this image properly, it is uploaded at:
http://img96.imageshack.us/img96/4113/adobeacrobatproblurbug.jpg
Adobe Acrobat Professional version, latest: 9.3.4
System: Windows XP
BUG: Adobe Acrobat Professional shows blurry PDFs in certain situations.
===
STEPS TO RECREATE THE BUG:
Use Windows XP. I'm not sure if this shows up in Vista too. I'm sure it does.
1. Download the PDF from:
http://www.2shared.com/document/P927Y4Vm/scanned-doc-2.html
2. In the Windows Task Manager, make sure there are no pre-existing Adobe processes running such as:
AcrobatInfo.exe, Acrobat.exe, Acrotray.exe
3. Open the PDF file you got in #1. Set zoom to 100%.
4. Notice the visual quality. You will probably see blurry areas in the PDF. This matches Area 1 in this screen shot:
http://img96.imageshack.us/img96/4113/adobeacrobatproblurbug.jpg
5. Close the file by doing: File---> Close
Do not exit the program. Go to Task Manager and verify that Acrobat.exe is already running.
6. Open the file you got in #1, again. Zoom to 100% again.
7. Notice now that the PDF does not have any blurry areas. What you see should match Area 2 in the same screenshot:
http://img96.imageshack.us/img96/4113/adobeacrobatproblurbug.jpg
-End-

The choices in Bridge > Preferences > Advanced > International > Keyboard are limited, and they do not allow for choosing custom keyboard layouts.
I need the custom keyboard layouts for a variety of reasons, such as being able to type in seven languages with my most used one without switching, two Russian layouts to allow for two non-standard ways of encoding Russian fonts, etc.

Bug report status

Hi, I have previously highlighted an issue with the Xperia C3 D2533 running 5.0, where the back camera is producing low quality images.This is from the Galaxy Note 1 While this is from the Xperia C3 What is appaling is if you zoom in, the N7000 has more detail than the C3, whereby the C3 just paints over the colours unscrupulously giving jagged edges obvious from the USB. I have sent an email to support and received a reply saying it has been forwarded to the developers about two weeks ago. I have heard that the Lollipop 5.1 is coming out in July and am curious as to whether the camera issue has been confirmed as a bug by the developers and are currently looking into it, hopefully rolling out the update with the fix as well. Edit: I have done a software reset and a repair via PC Companion using the steps recommended. The PC Companion told me there are no available updates or softwares for this phone. Therefore to sum it up, what I would like to know is a confirmation on the status of this report among the devs and whomever it may concern in the troubleshooting phase.

Seems like a search of the bug report submission
queue would be useful.Use this:
http://developers.sun.com/contact/feedback.jsp?referer=http://forum.java.sun.com&category=sdn&mailsubject=Forums%20or%20Community
It's as pointless as any other measure in getting Sun to do what you want. ;)

Bug report: Mail sends messages with empty bodies

Over the last year, I have experienced a particularly irritating bug in Mail.app at least a dozen times. I finally have a good idea as to what causes it.
The problem involves long email messages (often with attachments) that end up being sent with blank bodies (and no attachments). Even the copy in the "Sent" folder ends up blank, and several minutes or hours of work vanishes into thin air, not to be seen ever again.
I finally realized that this bug only occurs when sending mail through our work SMTP server while outside the work firewall, and only as a result of a certain sequence of events. Here is what happens:
When we connect to our work SMTP server from outside the local network and without going through the VPN, the SMTP server requires password authentication. If the current SMTP selection in Mail.app is the one that does not require authentication, the SMTP server rejects the message. At that point, Mail.app opens the email I am trying to send and brings up a modal dialog that says "Cannot send message using the server xxx.xxx -- The server response was: xxx@xxx relaying prohibited. You should authenticate first." The dialog also presents a drop-down list of SMTP server choices. I choose the password-authenticated version of the server and then click on "Use Selected Server" to send the message.
This works almost all the time, but on occasion it ends up sending a blank message! If I have a long email, particularly with attachments such as PDFs that are rendered in the body of the message, it takes a few seconds for the mail message to be rendered underneath the modal dialog box. Since I am used to this STMP rejection behavior, sometimes I am too fast to choose another STMP server from the list and click on "Use Selected Server" before the mail message is rendered on screen! The result, invariably, is a blank email message that gets sent.
I guess what is happening is that when the STMP server rejects the message and hands it back to Mail.app, the message gets copied into a buffer in order to be displayed on screen. Selecting another server and resending it immediately (before the message is copied into the buffer completely) causes the message body to get trashed.
I hope that this description is adequate for Apple QA folks to replicate and isolate the problem (and hopefully fix it). One solution (although not the most elegant one) would be to disable the "Use Selected Server" action until the message is copied into the buffer and rendered on screen.

This could be related to another bug reported here recently:
E-mail looses all images if mail server doesn't accept outgoing email...
You cannot count on Apple looking into this or even noticing it if you report it here, so I suggest you the same I suggested in the other thread, i.e. report it in one of the following places:
http://www.apple.com/macosx/feedback/
http://developer.apple.com/bugreporter/

Subject in Email is always "Report sent from Report Builder"

We run Forms 6.08 in C/S - architecture.
Forms calls reports:
ADD_PARAMETER(pl_id, 'SUBJECT',TEXT_PARAMETER, 'Please read appending pdf' );
add_Parameter(pl_id,'DESTYPE',TEXT_PARAMETER, 'Mail');
Run_Product(reports, 'MY_Report', SYNCHRONOUS, BATCH, Filesystem, pl_id);
This works: Lotus pops up and a Email is initialized with a pdf appended.
But the subject isn't filled in properly. There is always a constant text: "Report sent from Report Builder"
How can I control the subject?
Is it possible to fill in some text into the Email-body?
Wolfram

Hi,
Please find my comments below :
1. Subject is coming properly in EN but for DE taking the subject from standard task , BASIC DATA tab, Abbrevatio or Name ...
which i am not able to rectify. i am not required to translate in DE , have to send email as it is in EN. but subject is only missing
and everything is working fine. Can you please suggest me here ?
Ans. Your problem here is not clear...Is this a Work Item or mail ?.. Is your subject missing with Work Item in DE ?...
2. For the (sent) From email address instead of email something like WF_USER , i have to display like below :
densapwfadmin
Ans. Are you using talking about Extended notification here?... or just about mail step in your workflow?...
Regards
Gautam

BUG REPORT: Layers with 100% height in timeline knock bottommost layer(s) out of scrollable area

I have tried to post this twice to the official bug report page, but (somewhat hilariously) the bug report page bounces it back with an internal error about an unknown email address, so I'm posting here too just in case. As I have no idea how to report a bug about the bug report page, I decided I might as well just post the bug here.
CS5.5/Windows 7 - Verified on 6 different machines, some 64 bit, some 32 bit
If I have a layer in the timeline that has been expanded to 200% or 300% (via Layer Properties) height, the bottom-most layers gets pushed outside of the viewable area. The scrollbars simply don't scroll that far. I double-checked and this is new since CS4--which still works correctly--so never let it be said that the engineers aren't working on the code! :-/
Basically, I use this for audio layers, as it is nice to expand them to 200% so it's easier to see the waveform and guess where certain words are ending, etc when doing timeline syncing.
It can be worked around by expanding the timeline to be tall enough to bring everything into view, so I suspect the bug lies in the scrollable area calculation. However, since space is at a premium, usually I only have about 5-6 layers worth of space allocated to the timeline panel, so this bug hits me quite frequently (since I have all my old projects set up with 200% audio tracks).

sam wrote:
I have the same soundcard (or at least the same modules loaded) and I'm getting good volume.
Things to check:
If you have the pcm and main volume all the way up in alsa mixer that should be it. You may have to adjust the volume separately if you use esd, arts, pulse, or jack (I don't use them).
Another thing to test is to make sure your using alsa not oss, and you may want to raise the oss level and see what happens.
The final thing is you want to check to see which sound device the audio programs are using (usually found in the preferences).
If none of that works, then you're out of luck. It would help if you post what sound programs you are using and what sound daemons you are using.
Here is my Daemons line from /etc/rc.conf
DAEMONS=(@syslog-ng @network @netfs @crond @alsa @hal @fam)
So i would think im using alsa not oss. but how would i go about raising the oss to make sure? there is no "oss" option in alsamixer. I have tried just abuot every audio progream there is and even firefox, all of them produce about half of the maximum volume level.

RH bug reports sent to dead Macromedia address

Similar Messages

Maybe you are looking for