Bug Report Problem

I think there's a bug in the "bug report" procedure. Says I'm signed in but on next page says sign-in which takes me in a loop.

I have move my 5 x LC around, rebuild pref ?
yes, something like that. Firstly I would try to bring the LCs and XTs to default. Choose "Logic Pro/Preferences.../Control Surfaces/Rebuild Defaults".
If that doesn't help shut down all your devices and delete them from the CS-setup window. Quit Logic and delete
~/Library/Preferences/Logic/com.apple.logic.pro.cs
start Logic. When started switch on the LCs one after the other from left to right.
If that doesn't help, re-write the firmware. And if that doesn't help or if you already did all this:
sorry!
cheers
Martin

Similar Messages

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

Acrobat X Scanning Cancelled Problem / WORKAROUND / BUG REPORT

As you have read in other threads, Acrobat X on Windows has a serious scanning problem with HP and possibly other scanners.
Whereas in Acrobat 9 scanning worked reasonably well, Acrobat X seems to be unable to cope with scanning documents from the flat bed of a multifunction scanner.
So, if you are scanning from the feeder, scanning works, but if you are scanning from the flatbed, you will get a brief pause and the phrase SCANNING CANCELLED.
This is, of course, not acceptable.
The problem is that Acrobat X does not play nicely with the scanner drivers. Previously, Acrobat 9 would "auto-detect" the source of a document, using the feeder if loaded, and "falling back" to the flatbed otherwise. However, Acrobat X does not fall back. If there is nothing loaded in the document feeder, the scan will be cancelled by Acrobat X.
The workaround - and I would NOT call this a "solution" - is to use only the "Custom Scan" command from Acrobat X. When the window pops up, choose the "Options" button and select "Native Mode" and "Show Scanner's Native Interface" from the two menus. (Acrobat X does seem to remember these settings at least within a session, so if you're scanning multiple documents you only need to do this once.) Then scan.
You will see a new window pop up - the scanner's "native interface." On my computer, this window shows up BEHIND the Acrobat X screen (annoyingly) so you have to watch for it and click forward. Be sure to select "flat bed" from the "document source" menu. On my computer, this setting is NOT remembered between scans, so you have to do this for EVERY SCAN. Then, the document will scan, and you can do what you want with it in Acrobat X.
Needless to say, this is a long, painful, slow process, especially if you're scanning lots of flatbed items, as I do. Hence it's a "workaround" and NOT a "solution".
The SOLUTION will be for Adobe to FIX this. ADOBE: THIS IS A BUG REPORT. PLEASE LOG THIS IN AND FIX IT. Acrobat 9 with CS5 worked perfectly, as did Acrobat 8 before it. Moving to CS5.5 with Acrobat X broke this. Sloppy. Please fix! Thank you!
Glen Barney

I used your workaround (thank you!) but it was very annoying. Although I set up the options for a single multi-page document, Adobe gave me separate files and I had to consolidate them. I also had to fill out the options (color, flatbed vs feeder) for each page. This function was working for me at some point, so I don't know what happened to make my HP Multifunction and Adobe part ways. I hope Adobe comes up with a successful patch for this problem.

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: The keyboard focus doesn't automatical...

Bug Report: When a conversation window opens, the focus doesn't automatically land in the chat entry text field.
Since the new interface for Skype was introduced officially in Skype 7.0, there is a bug with the system/keyboard focus for a new conversation window. When Skype is in "Split Window View" and each new conversation automatically pops up in a separate window, the system/keyboard focus doesn't land in the chat entry edit field. Instead, the user has to press Shift+TAB a couple of times, to move it there and reply to the chat message received. This especially problematic for screen reader users, who rely on keyboard navigation. This mainly occurs when a new conversation is started with an incoming message, but it sometimes occurs when moving the focus out of that conversation window and later back in it again (while it is still opened).
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Tell someone to send you a chat message. When the message arrives, Move the system focus to the conversation window in question, preferably with Alt+TAB. The system/keyboard will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should by default, but in some unknown place in the window.
7. Move the system/keyboard focus in the chat entry edit field and keep it there.
8. Switch to another window, preferably from another application.
9. With Alt+TAB, switch back to the window of the opened Skype conversation. There is a chance that the system/keyboard focus will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should do by default, but again in some unknown place in the conversation window. But that is harder to reproduce.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Bug report: 3.2; DAC; GridControl; Navigation - Invalid reaction to mouse drag

Hi,
This is a bug report, I think.
I have a one-column GridControl with mandatory column. Normally, DAC framework prohibits from navigation out of empty field and emits one of those DAC-1002 or DAC-603 errors. The only exception I noticed was a double-click on another row. In this case navigation allowed but an error is still produced.
Today I was playing with this GridControl and discovered that I can drag the yellow frame across rows. And here comes a bug - GridControl doesn't change the current row on InfoBus according to current selection marked by yellow frame.
In my case it brings the following problem: if the cursor is placed on the new empty row, user drags the cursor to another row and then tries to use any other navigation means except dragging, he gets a navigation error. DAC framework still thinks that the current row is the empty one and produces an error telling that the attribute cannot be empty.
Dev Team, any comments?
Regards,
Vladimir

Hmm... Nobody answers. I'll try another variation of the same question.
DAC framework implicitly validates attributes on the base of Mandatory constraint in the Entity Object definition. Is it possible to set the level of this validation? For example, I want to conduct validation only when user navigates out of the row or the whole rowset, but not when he just leaves a field.
Regards,
Vladimir

Bug report: vpn (ipsec) interface number in snmp always change

Hi,
this is a bug report for RV082 hardware version 3 and 4, firmware version 1.x, 2.x and 4.x (all latest versions). I hope someone from cisco/belkin reads it.
Summary:
The snmp interface number of a VPN Tunnel change when the VPN tunnel disconnect and then re-connects.
What should happend:
The VPN Tunnel number 1, should always have the same snmp interface number. In RV082 v4, this number should always be 10. For example, the LAN, WAN1 and WAN2 always have the same snmp interface number.
What is the problem:
The VPN Tunnel number 1 change the snmp interface number, from 10, to 11, to 12, etc.
How to reproduce:
create a VPN Tunnel using 2 RV082 or 1 RV082 and 1 RV042. Once the VPN Tunnel is connected write down the snmp interface number. A few days later, disconnect the cable of block internet access. Then restore the internet conection and write down the snmp interface number, you should note that the snmp interface number have changed.
Tools used:
PRTG Network Monitor
Please take a look at the attached image, note all the "ppp" interfaces, theres only 1 VPN Tunnel (gateway-to-gateway) defined.

Hi Tom,
many thanks for your reply.
I see that I have to call Tech-support, in order to report a very technical situation, explaining them this is a bug report and I want them to make a better product.
Since I won't pay a dime for this problem to be fixed, I can only see pain in this path(calling to speak with a tech support representative).
I also readed that Belkin has bought Linksys, so I don't know if the RV082 will remain with Cisco or will go with Belkin.
So, my only hope is to document this bug, that is pressent inall firmware version and hardware version of the RV082 as of today.
many thanks for your help,
regards,
Oliver

Bug report: A keyboard layout is incorrect on the remote with Japanese keyboard

This is a bug report for Microst Remote Desktop
===================================================
## Summary
A keyboard layout is incorrect on the remote with Japanese keyboard
## Version Information, I tested
* Client
   * Case 1
       * MacBook Pro with JIS106 Keyboard
       * Mac OS X Lion 10.7.5
       * Microsoft Remote Desktop 8.0.24308
   * Case 2
       * MacBook Pro with JIS106 Keyboard
       * Mac OS X Mavericks 10.9.1
       * Microsoft Remote Desktop 8.0.24308
* Remote
   * Case 1
       * Windows 7 Professional Japanese
   * Case 2
       * Windows Server 2008R2 Datacenter Japanese
   * Case 3
       * Windows Server 2012R2 Datacenter Japanese
## Detail of bug
When login from Mac OS X with Microsoft Remote Desktop, the keyboard layout is always incorrect on the remote.
The client machine have a built-in keyboard of JIS 106 layout,
and the primary language is set to Japanese.
But on the remote, the keyboard layout is US 101.
So a input of Shift+2 does not result " but @.
I've seen the above behavior on the 3 remote enviornments described the above.
This bug did not occcur with Microsoft Remote Desktop Connection Client for Mac 2.1.1, even if the system language is English and keyboard layout is Japanese.
## Captures
I've took some of screen captures.
I'm sorry for the capture includes Japanese words, so I added description in English.
Capture 1:
Mac OS X Keyboard Setting
Capture 2:
Windows Server 2012R2 Screen Keyboard
Capture 3:
Windows Server 2012R2 Screen Keyboard, with a additional registry key configured.

This bug also affects the Canadian English settings. If the client is set to Canadian English with a US keyboard the remote server is setup using a Canadian French keyboard. Using the language selection in the toolbar you can temporarily correct
the problem but the keyboard resets to french at the most inopportune times. The was a problem in the earlier RDP client and was fixed so it's sad to see it reoccur in the new client.
Lawrence

Bug report 02

Bug report 02
In the ScoreWindow
with the INbutton activated
with Quantize 128,384
with Interpretation OFF
with Syncopation OFF
with No Overlap OFF
with the 1/128th NoteSymbol selected in the PartBox :
Playing a note on an external MIDI-keyboard will insert
a 1/64th note instead of the selected 1/128th note.
Anybody experiencing the same problem ?
Kind regards,
Urban Utan
Rotterdam.

or use the Safari button with the bug symbol. There you could easily add a screenshot, sourcecode and problem type of your bug on a html page.
Andreas

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: New conversation window stills the sys...

Bug Report: Skype Desktop: New conversation window stills the system/keyboard focus.
When the UI is in multi-window mode and a conversation window pops up (due for example to a newly received chat message), that window steals the system/keyboard focus, even though it appears in a minimized state in the Windows taskbar. And this should not happen by default, because it is impractical (especially for screen reader users). And it didn't happen in Skype 6.21 and earlier. But since the new UI was introduced officially in Skype 7.0, it started happening constantly.
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Move the system focus to another application.
7. Tell someone to send you a chat message. When the message arrives and the conversation window pops up minimized in the Windows Taskbar, everything seams to be as it should. A few seconds after that however, the system/keyboard focus gets moved to that new conversation window, even though it is neither restored/maximized (it is minimized), nor it is visible on the screen (except as a button in the taskbar).
Actual results:
When a new conversation window pops up in the Windows taskbar, it stills the system/keyboard focus to itself from the currently focused application.
Expected results:
Skype's popping up new conversation windows should not still the system/keyboard focus to themselfs from the currently focused application.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

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

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

Solaris 9 x86 bug report - el_GR.ISO8859-7 & CDE

I'm posting this article here, because I can't find any official Solaris 9 x86 bug report page. I hope the developers will notice it. I'm using Solaris 9 x86 (12/02), with the latest 9_x86_Recommended patch cluster installed, and support for Greek installed too.
It seems there is some kind of problem, when trying to view text files with Greek (el_GR.ISO8859-7) characters, which were created under Windows. To be more specific:
If I boot at CDE with language el_GR.ISO8859-7, and try to view a .txt file (just with a simple double click), which I have created under Windows, with Greek characters,
the screen goes black, and the CDE login screen appears again (restarts). If I keep the Greek language or change the language to US English, I can boot at CDE again, with
no problems. If I try "command line logging", the screen goes off - just like when the computer is powered off, and I can't do anything, (well, except pressing the reset button, that's the sure way). And if I use the "init 6" command, while being logged at CDE, from a terminal, the Graphical Desktop exits, and then, the screen goes off again (just like the computer is powered off), but finally the computer manages to restart.
I'm using the Sun X server, NOT the XFree86 porting kit and I use the entry
:0 Local local_uid@console nobody /usr/openwin/bin/Xsun :0 -dpsfileops
in /usr/dt/config/Xservers file, to start the X server.
Here is the $HOME_DIR/.dt/startlog file:
--- ??? 23 ??? 2003 12:10:51
--- /usr/dt/bin/Xsession starting...
--- starting /usr/openwin/bin/speckeysd
--- Xsession started by dtlogin
--- starting /usr/dt/bin/dtsession_res -load -system
--- sourcing /root/.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- sourcing /usr/dt/config/Xsession.d/1000.solregis...
--- could not read /root/.profile
--- starting /usr/dt/bin/dthello &
--- starting /usr/dt/bin/dtsearchpath
--- starting /usr/dt/bin/dtappgather &
--- starting /usr/dt/bin/dsdm &
--- session log file is /root/.dt/sessionlogs/www_DISPLAY=:0
--- DTSOURCEPROFILE is 'true' (see /root/.dtprofile)
--- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
--- starting desktop on /dev/pts/3
Sun Microsystems Inc. SunOS 5.9 Generic_112234-03 November 2002
/usr/dt/bin/ttsession[337]: starting
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
I don't know if this is a bug or something, and I'm very curious about the cause. I didn't have much time for any other "experiments".
Anyway, I hope this will help developers solve a problem -if it really exists-.
Angelos Vasilopoulos
Site Security Officer
[email protected]

I'm posting this article here, because I can't find any official Solaris 9 x86 bug report page. I hope the developers will notice it. I'm using Solaris 9 x86 (12/02), with the latest 9_x86_Recommended patch cluster installed, and support for Greek installed too.
It seems there is some kind of problem, when trying to view text files with Greek (el_GR.ISO8859-7) characters, which were created under Windows. To be more specific:
If I boot at CDE with language el_GR.ISO8859-7, and try to view a .txt file (just with a simple double click), which I have created under Windows, with Greek characters,
the screen goes black, and the CDE login screen appears again (restarts). If I keep the Greek language or change the language to US English, I can boot at CDE again, with
no problems. If I try "command line logging", the screen goes off - just like when the computer is powered off, and I can't do anything, (well, except pressing the reset button, that's the sure way). And if I use the "init 6" command, while being logged at CDE, from a terminal, the Graphical Desktop exits, and then, the screen goes off again (just like the computer is powered off), but finally the computer manages to restart.
I'm using the Sun X server, NOT the XFree86 porting kit and I use the entry
:0 Local local_uid@console nobody /usr/openwin/bin/Xsun :0 -dpsfileops
in /usr/dt/config/Xservers file, to start the X server.
Here is the $HOME_DIR/.dt/startlog file:
--- ??? 23 ??? 2003 12:10:51
--- /usr/dt/bin/Xsession starting...
--- starting /usr/openwin/bin/speckeysd
--- Xsession started by dtlogin
--- starting /usr/dt/bin/dtsession_res -load -system
--- sourcing /root/.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- sourcing /usr/dt/config/Xsession.d/1000.solregis...
--- could not read /root/.profile
--- starting /usr/dt/bin/dthello &
--- starting /usr/dt/bin/dtsearchpath
--- starting /usr/dt/bin/dtappgather &
--- starting /usr/dt/bin/dsdm &
--- session log file is /root/.dt/sessionlogs/www_DISPLAY=:0
--- DTSOURCEPROFILE is 'true' (see /root/.dtprofile)
--- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
--- starting desktop on /dev/pts/3
Sun Microsystems Inc. SunOS 5.9 Generic_112234-03 November 2002
/usr/dt/bin/ttsession[337]: starting
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
I don't know if this is a bug or something, and I'm very curious about the cause. I didn't have much time for any other "experiments".
Anyway, I hope this will help developers solve a problem -if it really exists-.
Angelos Vasilopoulos
Site Security Officer
[email protected]

Bug Report Problem

Similar Messages

Maybe you are looking for