Strange keyboard behavior after OS 4.2.1 upgrade

When typing (at least, so far, in Safari) the keyboard will randomly (or so it seems) retract after typing a letter, instead of that letter being registered in the text box. It's necessary to re-locate the insertion point back in the text box to bring the keyboard back. And when I do, then the caps lock is on even though it wasn't before. This happens every few characters, but unpredictably.

I'm getting this too. Been looking all over the Internet to find other people with the same problem.
Its very annoying, and I'm not touching any other part of the screen - it does exactly what the OP describes, and it seems to do it all the time, when I'm typing. Only noticed it in safari because that is all I type in, and strangely enough it is not happening as I type this, and when it does happen i make sure the webpages are fully loaded. Very strange and very frustrating
I'm also finding that rss feeds aren't updating, but thats a different problem.

Similar Messages

Strange keyboard behavior - odd characters

My friend's Macbook is acting weird. All the keys on the keyboard type correctly except the "H" and "V" keys. When typing a lower case "h", a superscript dot appears. Shift-"H" gives you a capital "O" with an accent mark over it. The "V" key doesn't do anything but give you a sound like you're running up against the end of something and can't input a character.
I've monkeyed around with the input menu to make sure US Qwerty was the only keyboard layout selected. Tried switching to something else and back to US Qwerty. Still nothing.
Any ideas what's going on here?

I am also having strange laptop keyboard behavior, but a little different than inserting odd characters.
While I'm inputting text, the cursor may jump back to the beginning of a text field or to the middle of a sentence and resume, resulting in a jumble of letters. Sometimes the cursor jumps multiple lines or letters ahead. When I try entering three of the same letters, it will only enter two, unless I insert the cursor manually. And all of this is intermittent.
Has my keyboard gone wacko? I've tried looking for possible keyboard viruses in Google, but nothing seems to match the symptoms. Also, the space bar under the track pad seems a little tight—doesn't always fell like it clicks when I press it.
Any ideas?

Strange keyboard behavior - multiple repetition of a character

I have a wireless Apple keyboard. From time to time keyboard locks into repeating multiple instances of a character, i.e. pppppppppppp and is doing that until I switch off the keyboard and reinstall bluetooth connection through the passkey.
How I can cure this strange behavior? Is anyone else experiencing the same problem?
Thanks
sercher
G5 2.5G Mac OS X (10.4.7)

Yes! I'm gettttttttttting the same issue! It happens randommmmmmmly with my apple bluetooth keyboard and drives me insane. (I didn't edit my typing.)
Also, sommetimes the the characters are slow to react after I have typed them and other times it's fine. The keyboard is always the same distance away from my powerbook.
What is the problem? Can Apple support answer one of these tttttthreads please?!

[solved] xorg 1.8 strange keyboard behavior

I've updated to xorg 1.8 on my MSI VR630 laptop.
But now some keys trigger two keypress events.
Examples:
* [Del] triggers [Del] and [Print]
* [Down] triggers [Down] and [Enter]
* [Ins] triggers [Ins] and [/]
and so on.
EDIT:
I overlooked that kbd setings had been overwritten by /etc/X11/xorg.conf.d/10-evdev.conf.
Had to disable evdev keyboard section.
Last edited by ColdSphinX (2010-05-13 13:10:07)

Nothing ?
Switchng off hal deamon and cleaning ~/.kde* has no effect...
So, after searching on google again an again, still nothing found.... even among the Ubuntu specific issue where post are terminated
with "wait next version of the package", the windows-style answer.
I will continue my attempts to fix this... but my conclusion about this is that hal was more precise in his behavior than udev...

Strange Client Behavior after upgrading to 10g

Hello Friends !!!!
Here is my scenario:
Oracle Database 10g 10.2.0.3
Windows 2008 Server SP2
After upgrading from oracle 9.2.0.1.0 and Windows 2003 Server I'm facing a strange behavior.
Many times over the days some machines do not release some table resources even having their status "INACTIVE" and the wait event "SQL *Net message from client" and wait class "IDLE".
Therefore, i got a lot of locked sessions, and users complaining..... until I kill them
The client machine was as well switched to Oracle 10g client....
Have you guys got any tips about this scenario?
Tks for any advice.

About the lock queue:
1. blocking session has an exclusive table lock on VENDEDORES table; this is very rare in application because most of the time not needed: application code should try to avoid to take such kind of lock.
2. blocked sessions request a row share table lock: it looks like that VENDEDORES table is a child table linked to some parent table with a foreign key constraint and that an index on the child table foreign key is missing (this kind of lock is requested if you DELETE from parent table or update parent table primary key).
About the lock session: this is the blocking session that is waiting since 19 seconds on client: it is likely an application issue: you should try to investigate what the client (aservice.exe) is doing while holding an exclusive table lock.

Tecra 8000: Strange keyboard behaviour after reassembling

Hi,
after reassembling the single keys to my keyboard from Tecra 8000 the keys have a strange behaviour. For example if i press the key 2 the display shows '82' or 'q'. if i hold the key longer, the display shows '2222222222222....', the right sign for the key.
Do you knwo, what i can do?
i had to reassemble the key because my little niece took all the keys off.
thanks for your answer,
Butch

Hi
I agree with Daniel. There is some technical problem and only thing you can do is try to clean the contacts. If there is no success you should replace the keyboard. This unit is older one and I am pretty sure that you can find a cheap used keyboard.
Bye

Lumia 800 - Strange UI Behavior after Touch!!!

When moving my finger horizontally or vertically (more noticeable when vertically scrolling) and leaving my finger on the screen after the move, the UI begins to shake up and down or side to side depending on whether I moved the UI vertically or horizontally. I found this when playing assassins creed first, the virtual joy stick under my thumb was moving on its own when my thumb was still. Trying this on the start screen by scrolling up or down a little and leaving my finger on the screen presented me with the UI moving on its own.
This is quite frustrating especially in game that require me to leave my finger/thumb on the screen. This behavior is noticeable in all elements for me, menus, internet browser, all hubs and so on. If you want to try it on your devices let me know if you have experienced the same thing. Remember just go to the start screen, scroll up or down slightly and don't take your finger off the screen, after a second or two the UI may start moving on its own like it does with me.
If there is anyway to reset the screen calibration through diagnostics apps or anything let me know please.
I have uploaded a video, its pretty poor quality but if you watch the calendar tile whilst I keep my finger still you will see how the UI moves on its own. More noticeable when you see it in person. http://youtu.be/vaJGcN7UfoE

It doesn't do that on mine Lumia, and I have put mine of my desk keeping my fingers steady after scrolling. Usually capacitive screens, and especially amoled ones are quite sensitive, and from looking at your video where you hold the phone in one hand up in front of cam and touches it with your other hand while the device is shaking like crazy doesn't make it easy to actually know if it's your or the device.
I guess you of course have done this already, but if not lay it down on a desk or table. Hold it tight with one hand and do the scrolling with your other hand. Then make sure the phone is dead still and so with your finger. Does it still do it?
I haven't found a setting or way to calibrate the screen. And it might only be my ignorance, but I haven't seen any setting or so regarding calibrating screen on any on my previous devices - I guess I have had 6-8 phones with capacitive displays.
I know that at least some of the s60 Nokia devices with resistive screen had it, but that's something else.

Strange keyboard behavior

I am filling out a form, but mistyped a character. When I any button in the keyboard, including the backspace key, the keyboard goes away. I doesn't do this everywhere, just on the ATT my account page.
Any suggestions?

Can you provide a bit more info?
I do understand this occurs on the at&t account page. Is this at&t wireless website? or another at&t website?
And is it occurring during Login of the account or another area?
Thanks for any extra info. It helps us all better understand how to better assist.

Strange GDM behavior after recent update

Hi folks,
3 days ago I ran pacman -Syu, and since then GDM behaves different. Before, it had the blue background and started instantly, now it takes several seconds after the switch from tty and then first displays the blue background, then turns dark and shows the login dialog. After logging in, it takes several seconds again and then shows the blue background again, and then finally starts gnome with its own background.
To describe the issue completely, there was one warning during the pacman -Syu which I fixed later, but during the update this was the only problem:
[2012-11-02 15:26] installed libpwquality (1.2.0-1)
[2012-11-02 15:26] warning: directory permissions differ on usr/share/polkit-1/rules.d/
filesystem: 700 package: 755
The update also replaced the following packages:
libwebkit => webkitgtk2
libwebkit3 => webkitgtk3
pyatspi => python2-atspi
I updated the system on November 2nd, and this is what sudo journalctl -u gdm says since then (i just enabled gdm debug mode):
-- Reboot --
Nov 01 13:09:10 Jan-Arch gdm-simple-slave[414]: WARNING: Child process 1629 was already dead.
-- Reboot --
Nov 01 17:44:22 Jan-Arch gdm-simple-slave[343]: WARNING: Child process 1588 was already dead.
-- Reboot --
Nov 02 01:39:14 Jan-Arch gdm-simple-slave[334]: WARNING: Child process 1581 was already dead.
-- Reboot --
Nov 02 03:30:55 Jan-Arch gdm-simple-slave[331]: WARNING: Child process 1579 was already dead.
-- Reboot --
Nov 02 11:59:50 Jan-Arch gdm-simple-slave[311]: WARNING: Child process 1614 was already dead.
-- Reboot --
Nov 02 12:18:10 Jan-Arch gdm-simple-slave[359]: WARNING: Child process 1613 was already dead.
-- Reboot --
Nov 02 15:49:48 Jan-Arch gdm-simple-slave[797]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 02 15:50:02 Jan-Arch gdm-password][1695]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 02 15:50:02 Jan-Arch gdm-password][1695]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 02 15:50:02 Jan-Arch gdm-simple-slave[797]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 02 15:50:02 Jan-Arch gdm-simple-slave[797]: WARNING: Child process -1537 was already dead.
Nov 02 15:51:03 Jan-Arch gdm-simple-slave[797]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: ******************* START ********************************
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 0: /usr/sbin/gdm-binary() [0x4288eb]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 1: /usr/sbin/gdm-binary() [0x428cda]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 2: /usr/lib/libpthread.so.0(+0xf1a0) [0x7f8d346b91a0]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 3: /usr/lib/libc.so.6(gsignal+0x35) [0x7f8d34337fd5]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 4: /usr/lib/libc.so.6(abort+0x148) [0x7f8d34339458]
Nov 02 15:51:03 Jan-Arch gdm-simple-slave[797]: WARNING: Child process 1695 was already dead.
Nov 02 15:51:03 Jan-Arch gdm-simple-slave[797]: WARNING: Unable to kill session worker process
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 5: /usr/lib/libglib-2.0.so.0(g_assertion_message+0x137) [0x7f8d34d3f8f7]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 6: /usr/lib/libglib-2.0.so.0(g_assertion_message_error+0x9f) [0x7f8d34d3fb2f]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 7: /usr/lib/libgio-2.0.so.0(+0xda5d5) [0x7f8d352f45d5]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 8: /usr/lib/libgio-2.0.so.0(+0xdacee) [0x7f8d352f4cee]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 9: /usr/lib/libgio-2.0.so.0(g_dbus_object_manager_server_unexport+0x6c) [0x7f8d352f56fc]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 10: /usr/lib/libglib-2.0.so.0(g_hash_table_find+0x9b) [0x7f8d34d0e1bb]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 11: /usr/sbin/gdm-binary() [0x40adfb]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 12: /usr/sbin/gdm-binary() [0x410b78]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 13: /usr/lib/libgobject-2.0.so.0(g_object_unref+0x1e8) [0x7f8d34fe10f8]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 14: /usr/sbin/gdm-binary() [0x409425]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 15: /usr/lib/libffi.so.6(ffi_call_unix64+0x4c) [0x3c49005e48]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 16: /usr/lib/libffi.so.6(ffi_call+0x1e0) [0x3c49005850]
Nov 02 15:51:03 Jan-Arch gdm-binary[790]: Frame 17: /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_generic+0x1fb) [0x7f8d34fdcafb]
Nov 02 15:51:03 Jan-Arch gdm[790]: **
Nov 02 15:51:03 Jan-Arch gdm[790]: GLib-GIO:ERROR:gdbusobjectmanagerserver.c:969:g_dbus_object_manager_server_emit_interfaces_removed: assertion failed (error == NULL): Verbindung ist g
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: ******************* START ********************************
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 0: /usr/sbin/gdm-binary() [0x4288eb]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 1: /usr/sbin/gdm-binary() [0x428cda]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 2: /usr/lib/libpthread.so.0(+0xf1a0) [0x7f8d346b91a0]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 3: /usr/lib/libc.so.6(gsignal+0x35) [0x7f8d34337fd5]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 4: /usr/lib/libc.so.6(abort+0x148) [0x7f8d34339458]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 5: /usr/lib/libglib-2.0.so.0(g_assertion_message+0x137) [0x7f8d34d3f8f7]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 6: /usr/lib/libglib-2.0.so.0(g_assertion_message_error+0x9f) [0x7f8d34d3fb2f]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 7: /usr/lib/libgio-2.0.so.0(+0xda5d5) [0x7f8d352f45d5]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 8: /usr/lib/libgio-2.0.so.0(+0xdacee) [0x7f8d352f4cee]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 9: /usr/lib/libgio-2.0.so.0(g_dbus_object_manager_server_unexport+0x6c) [0x7f8d352f56fc]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 10: /usr/lib/libglib-2.0.so.0(g_hash_table_find+0x9b) [0x7f8d34d0e1bb]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 11: /usr/sbin/gdm-binary() [0x40adfb]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 12: /usr/sbin/gdm-binary() [0x410b78]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 13: /usr/lib/libgobject-2.0.so.0(g_object_unref+0x1e8) [0x7f8d34fe10f8]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 14: /usr/sbin/gdm-binary() [0x409425]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 15: /usr/lib/libffi.so.6(ffi_call_unix64+0x4c) [0x3c49005e48]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 16: /usr/lib/libffi.so.6(ffi_call+0x1e0) [0x3c49005850]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 17: /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_generic+0x1fb) [0x7f8d34fdcafb]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 18: /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x190) [0x7f8d34fdc1a0]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 19: /usr/lib/libgobject-2.0.so.0(+0x215b0) [0x7f8d34fed5b0]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 20: /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0xdac) [0x7f8d34ff551c]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 21: /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x82) [0x7f8d34ff56b2]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 22: /usr/lib/libgio-2.0.so.0(+0xb8d25) [0x7f8d352d2d25]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 23: /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x135) [0x7f8d34d1d865]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 24: /usr/lib/libglib-2.0.so.0(+0x47b98) [0x7f8d34d1db98]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 25: /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x72) [0x7f8d34d1df92]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 26: /usr/sbin/gdm-binary() [0x409054]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 27: /usr/lib/libc.so.6(__libc_start_main+0xf5) [0x7f8d34324725]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: Frame 28: /usr/sbin/gdm-binary() [0x409301]
Nov 02 15:51:03 Jan-Arch gdm[790]: gdm-binary[790]: ******************* END **********************************
-- Reboot --
Nov 03 13:18:36 Jan-Arch gdm-simple-slave[690]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 03 13:23:07 Jan-Arch gdm-password][7480]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 03 13:23:07 Jan-Arch gdm-password][7480]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 03 13:23:07 Jan-Arch gdm-simple-slave[690]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 03 13:23:07 Jan-Arch gdm-simple-slave[690]: WARNING: Child process -1448 was already dead.
Nov 03 13:58:48 Jan-Arch gdm-simple-slave[690]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 03 13:58:48 Jan-Arch gdm-simple-slave[690]: WARNING: Child process 7480 was already dead.
Nov 03 13:58:48 Jan-Arch gdm-simple-slave[690]: WARNING: Unable to kill session worker process
Nov 03 13:58:49 Jan-Arch gdm-simple-slave[690]: GLib-GObject-CRITICAL: g_object_unref: assertion `object->ref_count > 0' failed
Nov 03 13:58:49 Jan-Arch gdm-simple-slave[12329]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 03 13:59:03 Jan-Arch gdm-password][12860]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 03 13:59:03 Jan-Arch gdm-password][12860]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 03 13:59:03 Jan-Arch gdm-simple-slave[12329]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 03 14:53:22 Jan-Arch gdm[12325]: gdm-binary[12325]: WARNING: GdmDisplay: display lasted 0,001517 seconds
Nov 03 14:53:22 Jan-Arch gdm-binary[12325]: WARNING: GdmDisplay: display lasted 0,001517 seconds
Nov 03 14:53:23 Jan-Arch gdm-simple-slave[22606]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 03 14:54:02 Jan-Arch gdm-simple-slave[22606]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
-- Reboot --
Nov 03 14:54:19 Jan-Arch gdm-simple-slave[769]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 03 14:54:32 Jan-Arch gdm-password][1633]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 03 14:54:32 Jan-Arch gdm-password][1633]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 03 14:54:32 Jan-Arch gdm-simple-slave[769]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 03 14:54:32 Jan-Arch gdm-simple-slave[769]: WARNING: Child process -1486 was already dead.
Nov 03 15:44:44 Jan-Arch gdm-simple-slave[769]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 03 15:44:44 Jan-Arch gdm-simple-slave[769]: WARNING: Child process 1633 was already dead.
Nov 03 15:44:44 Jan-Arch gdm-simple-slave[769]: WARNING: Unable to kill session worker process
Nov 03 15:44:45 Jan-Arch gdm-simple-slave[769]: GLib-GObject-CRITICAL: g_object_unref: assertion `object->ref_count > 0' failed
Nov 03 15:44:46 Jan-Arch gdm-simple-slave[16298]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 03 15:44:58 Jan-Arch gdm-password][16420]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 03 15:44:58 Jan-Arch gdm-password][16420]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 03 15:44:58 Jan-Arch gdm-simple-slave[16298]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 03 18:54:32 Jan-Arch gdm-simple-slave[16298]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 03 18:54:32 Jan-Arch gdm-simple-slave[16298]: WARNING: Child process 16420 was already dead.
Nov 03 18:54:32 Jan-Arch gdm-simple-slave[16298]: WARNING: Unable to kill session worker process
-- Reboot --
Nov 03 20:42:04 Jan-Arch gdm-simple-slave[840]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 03 21:34:49 Jan-Arch gdm-password][9919]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 03 21:34:49 Jan-Arch gdm-password][9919]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 03 21:34:49 Jan-Arch gdm-simple-slave[840]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 03 21:34:49 Jan-Arch gdm-simple-slave[840]: WARNING: Child process -1636 was already dead.
Nov 03 23:01:12 Jan-Arch gdm-simple-slave[840]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 03 23:01:12 Jan-Arch gdm-simple-slave[840]: WARNING: Child process 9919 was already dead.
Nov 03 23:01:12 Jan-Arch gdm-simple-slave[840]: WARNING: Unable to kill session worker process
-- Reboot --
Nov 04 11:06:12 Jan-Arch gdm-simple-slave[805]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 04 11:06:54 Jan-Arch gdm-password][2294]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 04 11:06:54 Jan-Arch gdm-password][2294]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 04 11:06:54 Jan-Arch gdm-simple-slave[805]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 04 11:15:02 Jan-Arch gdm-simple-slave[805]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 04 11:15:03 Jan-Arch gdm-simple-slave[805]: WARNING: Child process 2294 was already dead.
Nov 04 11:15:03 Jan-Arch gdm-simple-slave[805]: WARNING: Unable to kill session worker process
Nov 04 11:15:03 Jan-Arch gdm-simple-slave[13769]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 04 11:15:15 Jan-Arch gdm-password][13855]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 04 11:15:15 Jan-Arch gdm-password][13855]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 04 11:15:15 Jan-Arch gdm-simple-slave[13769]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 04 11:19:18 Jan-Arch gdm-simple-slave[13769]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 04 11:19:18 Jan-Arch gdm-simple-slave[13769]: WARNING: Child process 13855 was already dead.
Nov 04 11:19:18 Jan-Arch gdm-simple-slave[13769]: WARNING: Unable to kill session worker process
Nov 04 11:19:19 Jan-Arch gdm-simple-slave[19495]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 04 11:19:44 Jan-Arch gdm-password][20033]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 04 11:19:44 Jan-Arch gdm-password][20033]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 04 11:19:44 Jan-Arch gdm-simple-slave[19495]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: WARNING: Child process 20033 was already dead.
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: WARNING: Unable to kill session worker process
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: GLib-GIO-CRITICAL: g_dbus_connection_unregister_object: assertion `G_IS_DBUS_CONNECTION (connection)' failed
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: GLib-GIO-WARNING: (gdbusinterfaceskeleton.c:739):remove_connection_locked: runtime check failed: (g_dbus_connection_unregister_object (
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
-- Reboot --
Nov 04 12:02:32 Jan-Arch gdm-simple-slave[722]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 04 12:02:45 Jan-Arch gdm-password][1643]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 04 12:02:45 Jan-Arch gdm-password][1643]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 04 12:02:46 Jan-Arch gdm-simple-slave[722]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 04 13:31:18 Jan-Arch gdm-simple-slave[722]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 04 13:31:18 Jan-Arch gdm-simple-slave[722]: WARNING: Child process 1643 was already dead.
Nov 04 13:31:18 Jan-Arch gdm-simple-slave[722]: WARNING: Unable to kill session worker process
-- Reboot --
Nov 04 13:31:36 Jan-Arch gdm-simple-slave[796]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 04 13:31:52 Jan-Arch gdm-password][1718]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 04 13:31:52 Jan-Arch gdm-password][1718]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 04 13:31:52 Jan-Arch gdm-simple-slave[796]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 04 13:31:52 Jan-Arch gdm-simple-slave[796]: WARNING: Child process -1569 was already dead.
(END)
Nov 03 15:44:58 Jan-Arch gdm-simple-slave[16298]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 03 18:54:32 Jan-Arch gdm-simple-slave[16298]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 03 18:54:32 Jan-Arch gdm-simple-slave[16298]: WARNING: Child process 16420 was already dead.
Nov 03 18:54:32 Jan-Arch gdm-simple-slave[16298]: WARNING: Unable to kill session worker process
-- Reboot --
Nov 03 20:42:04 Jan-Arch gdm-simple-slave[840]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 03 21:34:49 Jan-Arch gdm-password][9919]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 03 21:34:49 Jan-Arch gdm-password][9919]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 03 21:34:49 Jan-Arch gdm-simple-slave[840]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 03 21:34:49 Jan-Arch gdm-simple-slave[840]: WARNING: Child process -1636 was already dead.
Nov 03 23:01:12 Jan-Arch gdm-simple-slave[840]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 03 23:01:12 Jan-Arch gdm-simple-slave[840]: WARNING: Child process 9919 was already dead.
Nov 03 23:01:12 Jan-Arch gdm-simple-slave[840]: WARNING: Unable to kill session worker process
-- Reboot --
Nov 04 11:06:12 Jan-Arch gdm-simple-slave[805]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 04 11:06:54 Jan-Arch gdm-password][2294]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 04 11:06:54 Jan-Arch gdm-password][2294]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 04 11:06:54 Jan-Arch gdm-simple-slave[805]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 04 11:15:02 Jan-Arch gdm-simple-slave[805]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 04 11:15:03 Jan-Arch gdm-simple-slave[805]: WARNING: Child process 2294 was already dead.
Nov 04 11:15:03 Jan-Arch gdm-simple-slave[805]: WARNING: Unable to kill session worker process
Nov 04 11:15:03 Jan-Arch gdm-simple-slave[13769]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 04 11:15:15 Jan-Arch gdm-password][13855]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 04 11:15:15 Jan-Arch gdm-password][13855]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 04 11:15:15 Jan-Arch gdm-simple-slave[13769]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 04 11:19:18 Jan-Arch gdm-simple-slave[13769]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 04 11:19:18 Jan-Arch gdm-simple-slave[13769]: WARNING: Child process 13855 was already dead.
Nov 04 11:19:18 Jan-Arch gdm-simple-slave[13769]: WARNING: Unable to kill session worker process
Nov 04 11:19:19 Jan-Arch gdm-simple-slave[19495]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 04 11:19:44 Jan-Arch gdm-password][20033]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 04 11:19:44 Jan-Arch gdm-password][20033]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 04 11:19:44 Jan-Arch gdm-simple-slave[19495]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: WARNING: Child process 20033 was already dead.
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: WARNING: Unable to kill session worker process
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: GLib-GIO-CRITICAL: g_dbus_connection_unregister_object: assertion `G_IS_DBUS_CONNECTION (connection)' failed
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: GLib-GIO-WARNING: (gdbusinterfaceskeleton.c:739):remove_connection_locked: runtime check failed: (g_dbus_connection_unregister_object (
Nov 04 12:02:14 Jan-Arch gdm-simple-slave[19495]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
-- Reboot --
Nov 04 12:02:32 Jan-Arch gdm-simple-slave[722]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 04 12:02:45 Jan-Arch gdm-password][1643]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 04 12:02:45 Jan-Arch gdm-password][1643]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 04 12:02:46 Jan-Arch gdm-simple-slave[722]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 04 13:31:18 Jan-Arch gdm-simple-slave[722]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Nov 04 13:31:18 Jan-Arch gdm-simple-slave[722]: WARNING: Child process 1643 was already dead.
Nov 04 13:31:18 Jan-Arch gdm-simple-slave[722]: WARNING: Unable to kill session worker process
-- Reboot --
Nov 04 13:31:36 Jan-Arch gdm-simple-slave[796]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Nov 04 13:31:52 Jan-Arch gdm-password][1718]: pam_unix(gdm-password:session): session opened for user jan by (unknown)(uid=0)
Nov 04 13:31:52 Jan-Arch gdm-password][1718]: pam_ck_connector(gdm-password:session): nox11 mode, ignoring PAM_TTY :0
Nov 04 13:31:52 Jan-Arch gdm-simple-slave[796]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Nov 04 13:31:52 Jan-Arch gdm-simple-slave[796]: WARNING: Child process -1569 was already dead.
I have no idea how to fix this, i googled and tried the half day. Xorg.0.log also does not report any suspicious WWs or EEs. Any help would be greatly appreciated!
Thanks in advance,
Jan

One other possibility would be to reapply that update and/or the The combo update for Intel-based Macs...
http://www.apple.com/support/downloads/macosx10411comboupdateintel.html
Repair Permissions before & after re-install, then reboot again each time.

Weird keyboard behavior in MacBook Pro 13'

Hi guys, I have a MacBook Pro that's starting to show a strange keyboard behavior.
The problem is that the keys: e r t y u i o (curiously all belong to the same row) sometimes get unresponsive.
It's very annoying of course and it happened about 4 months after upgraded to Lion.
The geneal perfomance of the laptop was deteriorated and I've read that a clean install of Lion might help so I've did it thinking that it will also fix any OS weirdness about the keys too.
The machine works way better after the clean Lion install but the problem of those same keys persist.
What I did next was to reset the PRAM thinking it might be interference from some weird state there. But after the reset the problem persisted.
Curiously, I've figured out that when, for example the i key gets unresponsive, if I press AND hold the e key then the i key works totally fine (think of typing an "I" but using e instead of shift).
If, when pressing the unresponsive keys, I use different angles or quantity of force in the pressure of the keys or cornes of the key the behavior stays the same. The only thing that seems to affect is holding the e key down before pressing it. Every time it gets weird I do it and it kind of get normal for a while.
Also, sometimes, keeping some seconds the unresponsive key ends up getting responsive again (but not always).
This mac has about two years now and it's very well preserved.
Do this happen to anyone? ideas?
Is there some other thing than PRAM I could reset to see if it gets normal again?

You are making me dig into nightmare-ish memories here.
Ok, I'll share.
This is how turned out:
Needed to send my MBP to another town with an Apple authorized service provider and asked to change the keyboard for a new one.
It was ~20 days waiting until they got the new keyboard part from Apple and about ~3 more to get it fixed and ~2 more to get it again in town.
I received it very well packaged and all was fine after that but the whole thing was very expensive, ~40% of the price I paid for the whole MPB in the first place plus all that time without being able to use it.

Sequence behavior after importing via DataPump

Hi Friends,
I'm running Oracle DB 11.2.0.3 on Windows 2008 R2 SP1 Servers and I faced a strange sequences behavior after importing a schema via Data Pump.
The export is done this way:
EXPDP userid/password dumpfile= logfile= directory= remap_dumpfile=y (no news)
The import is done this way
IMPDP userid/password dumpfile= logfile= directory= remap_schema=(old_one:new_one) remap_tablespace=(old_ones:new_ones, so on...)
The import works fine. There are no errors and the sequences are as well imported with no warnings.
The strange behavior is that the sequences seems to "reset". When we call a sequence the NEXTVAL is just lower than the values already stored in the Database, and we get ORA-00001 a lot. The sequence should know that vale. I don't have this problem when using exp/imp, just via DataPump.
So that when we create an order that should receive the value of 100, as an example, because we have 99 orders on the system, Oracle suggest a value lower than 99 or even the number one value (01).
We then wrote a script to check the CURVAL of the sequences on the base schema to recreate the sequences using this initial value on the new imported schema.
Does anyone faced this problem before?
Any suggestions?
Tks a lot

Richard
I've tried what you just said.
Adding the parameter consistent=y makes Oracle to show a message like that at the beginning of the export
"flashback_time=TO_TIMESTAMP('2013-09-03 12:18:12', 'YYYY-MM-DD HH24:MI:SS')"
It warns me: Legacy Parameter CONSISTENT=TRUE, and replaces with flashback_time.
Really, I did not know about this behavior with this "old" parameter. I'm very appreciated about your help.
I was almost thinking it was a DataPump bug or something.
Thanks a lot Richard. I'll now update my scripts and make lots of test.
If you have more advices using this parameter please share us.
Cheers

SQL strange behavior after 11g upgrade

Hi all,
After upgrading from 10.2.0.3 to 11.2.0.1 (64-bit RedHat), one of my SQLs behaves very strangely.
These are the facts:
- This is upgrade evaluation phase in 'lab' environment
- First run (after db restart) returns results very quickly (acceptable 0.4 secs)
- Every consecutive run is very slow (3-4 minutes)
- Explain Plan did NOT change between runs;
- Number of 'consistent gets' changed drastically (from few thousands to few millions) ...which would usually lead to inefficient data access plan (index), but again, the explain plan did not change!
- If I flush shared_pool, next run is quick again, and the story repeats ... flushing shared_poll is possible in test system only, it's out of question for prod system of course
- All above happens in 'lab' environment, i.e. no multi-user load yet ... practically 'one-session' system
- I have tried both AMM and ASSM memory management(s) and same problem happens regardless (my old 10g database uses ASSM and I am trying to implement ASM in new 11g db)
- On same server, the SQL in question performs correctly if I run it in 10g environment;
- I have updated my 11g Oracle software/db with the latest CPU;
In addition, I have played with 'result cache' in 11g, and putting 'result_cache' hint in my sql resolved the issue. But that will open a lot of new questions for implementation in real app environment ... so at this moment, I don't want to evaluate result cache ...if I don't have to
I am thinking to try this on another server and eliminate eventual issue with some kind of faulty memory on existing server ... after that - to open ticket with Oracle ...
Any similar experience out there? Any thoughts?
Thanks a lot ...

Welcome to the forums !
How to post a tuning request
HOW TO: Post a SQL statement tuning request - template posting
When your query takes too long ...
HTH
Srini

[SOLVED]Very strange laptop behavior: keymap changing on fly

I have had arch up and running on my Lenovo T440s without issue for over 2 months now. Today I ran into some very strange behavior. After being on for about 45 minutes, with only a browser and thunderbird running, the keyboard started being selective in which keys woud work. I could no longer mange the windows with my normal AwesomeWM key bindings. The only thing I could do was restart by turning off and back on. I checked journalctl and there had been a weird message around the time the error occured, something along the lines of "HKEY error 0x600, unknown thermal alarm or keyboard input".
Now I can barely login, ocassionally I can get my credentials input before the machine stops reading in certain letters. When I use xterm rather than the usual urxvt the letters are all some different unicode symbols, it's like the keymap has been changed to something bizarre on the fly, right after loading up. The time at which this issue arises is not predicatable, sometimes I can get further before it happens. For example, sometimes I can't even enter my username and other times I get a few minutes, just enough to try to enable sshd so I can effectively troubleshoot remotely. I was able to run an update and install lm_sensors remotely. The cpu temps are right at or below 40 deg C.
Any ideas on how to debug this would be very appreciated.
Dave
Last edited by dam5h (2014-07-01 13:04:20)

Hello, thank you for the reply.
Actually this is a laptop so the keyboard is internal. However I have input a usb keyboard from my desktop to try to isolate the issue when it occurs. I get the same behavior out of my desktop usb keyboard.
I am seeing no messages in the journal when the event occurs (since that one mentioned above happened yesterday). The problem has since arisen about 20 times and I am not getting any messages. Perhaps there is a verbosity setting in the journalctl config, I haven't yet had time to look into that.
Two other oddities /clues are:
1. When I go into the BIOS, I cannot get consistent response from the keys. At first the bios just beeps at me when I try to use the arrows of other keys, although usually eventually they start working. At first I thought this may have to do with me pressing several keys to initiate the bios rapidly as the boot is so fast, but now I'm not sure that's it--based on the amount of time that the unresponsive beep alarm is occuring for (sometimes I stop waiting and restart).
2. When I get the bad behavior, I am able to put the machine to sleep (suspend) temporarily by closing the lid for 5 secs and reopening it. After doing this I get normal keyboard behavior for another few minutes before it goes wonky again.
I need this machine for work in the evenings so any help troubleshooting would be very appreciated. Will probably be calling lenovo soon, but given that I altered the OS from preinstalled windows they may not be very helpful.

Keyboard issues after upgrading to Leopard

Seems there's been quite a bit of discussion about this topic already but it's been confined to laptops and I haven't seen a solution yet. I'm seeing the same problems on a desktop computer using either a wireless or USB keyboard.
After upgrading to Leopard, my keyboard would occasionally stop responding to keystrokes. I have seen this happen on both an Apple USB keyboard and my Logitech wireless keyboard. With either keyboard, the letter and number keys would stop responding but keys like the CapsLock and Delete keys would still work. I have seen this happen when using Mac Office 2004 (Excel and Word) and Safari. With Excel, when the keyboard stops responding, if I click on a different cell, the keyboard comes back. I did update to 10.5.2 and I do have the latest version of the Logitech software but the problems still persist.
Strangely, I have only seen this happen on my MacPro but NOT my MacBook. There is a difference on how each machine was upgraded to Leopard though. On my MacBook, I did a clean install of Leopard on a new hard drive and then migrated my docs and apps from the old drive. On my Mac Pro, I did an upgrade installation over Tiger. Fortunately, I cloned my hard drive prior to installing Leopard so going back is an option and so is doing a clean install followed by a migration which is what I did on my MacBook.
Is there a fix for the keyboard problems? Am I going to have to downgrade back to Tiger?

Thanks for posting this. I thought I was alone in the universe. I have the problem with my mini, which came with Leopard installed. The USB keyboard will stop working in Word or Entourage ('04) and I have to close and reopen the document to get the keyboard going again. Thankfully, my mouse still works when this happens, so I can use it to close and save.
It seems to sometimes be triggered when I switch between applications, but I haven't been able to replicate it consistently. It is particularly bad when using find in Word. The find window will go dead and I have to close it and reopen it to do another search. (Though interestingly, I don't have to close the Word doc.)
It's irritating.

Strange Permissions Behavior with Public/Private Drop Box

Strange Permissions Behavior with Non-Course Drop Box
In an effort to promote iTunes U on campus this semester (and to get people working with audio and video more) we're having a contest in which people can submit personal or group audio/video projects.
This being an iTunes promo, we intend for students to submit their contributions via a drop box.
To that end, I began experimenting with drop boxes in iTunes U, which I haven't done much of previously. I've created a course called "iTunes U Drop Box Test" under "Campus Events". Within that, I have two tabs: "Featured Submissions" and "Dropbox". My goal with this drop box was to allow faculty, students and college folks the ability to use the drop box ("college" being a role I've defined for those who don't fit into the faculty/student roles).
When I first started experimenting, access to the "iTunes U Drop Box Test" course looked like this:
--- Credentials (System) ---
Edit: Administrator@urn:mace:itunesu.com:sites:lafayette.edu
Download: Authenticated@urn:mace:itunesu.com:sites:lafayette.edu
Download: Unauthenticated@urn:mace:itunesu.com:sites:lafayette.edu
Download: All@urn:mace:itunesu.com:sites:lafayette.edu
--- Credentials ----
Download: College@urn:mace:lafayette.edu
Download: Instructor@urn:mace:lafayette.edu
Download: Instructor@urn:mace:lafayette.edu:classes:${IDENTIFIER}
Download: Student@urn:mace:lafayette.edu
Download: Student@urn:mace:lafayette.edu:classes:${IDENTIFIER}
For the "Featured" Submissions tab, I gave the non-system credentials the "download" right, and for the "Dropbox" tab I gave the non-system credentials the "dropbox" right.
My understanding of this setup is that everyone should have had the ability to view the course and the contents of the "Featured Submissions" tab and that those in the College/Instructor/Student roles would be able to upload files via the "Dropbox" tab ... but not see the contents of said tab after the files were uploaded (aside from any files they uploaded themselves).
This is not the behavior we saw however. While the College/Instructor/Student roles could upload files to the dropbox, everyone (including the unauthenticated public) was able to see all of the contents of the dropbox.
The only way I could get this to work as advertised was to change all of the system credentials save the "Administrator" to "No Access":
--- Credentials (System) ---
Edit: Administrator@urn:mace:itunesu.com:sites:lafayette.edu
No Access: Authenticated@urn:mace:itunesu.com:sites:lafayette.edu
No Access: Unauthenticated@urn:mace:itunesu.com:sites:lafayette.edu
No Access: All@urn:mace:itunesu.com:sites:lafayette.edu
Once I did this, everything worked as advertised: College/Instructor/Student roles could upload tracks, and the "Dropbox" tab would only display tracks they uploaded.
So my question is ... is this the correct behavior for the drop box? It looks like when the system credentials are in play, they're simply overriding whatever the normal "view" rule is for the drop box, which doesn't seem right.

Your current configuration where things work as you wanted does seem correct to me. You are not using any System Credentials to accomplish the functionality and that's fine.
Here's some more info to clarify how / why this is working for you and why you had to set "No Access" for the System Credentials:
The System Credential "Authenticated@..." is going to get assigned to any user that goes through your transfer script. Even if you transfer script assigns no credentials to a user, upon entering iTunes U they will have at least 1 - the "Authenticated@..." credential. Therefore, unless you block access using "No Access", any user that passes through your transfer script is going to be able to access the area in question.
When you change values for "Unauthenticated@..." or "All@..." you are defining what someone that DOES NOT pass through your transfer script can do. You want both of those to be "No Access" at the top level of your site if you do not want unauthenticated visitors.
The distinction between "Unauthenticated" and "All" is that "All" applies to all users whether they pass through the transfer script or not.
Here's another way to remember things:
User passes through your transfer script, iTunes U automatically assigns:
Authenticated@....
All@....
User does not pass through your transfer script and instead access your iTunes U site through derivable URL*, they get assigned:
Unauthenticated@....
All@....
*The derivable URL for a site is: http://deimos.apple.com/WebObjects/Core.woa/Browse/site-domain-name
Mac OS X (10.4.6)

Strange keyboard behavior after OS 4.2.1 upgrade

Similar Messages

Maybe you are looking for