Thanks for the update. Unfortunately we are still trying to reproduce the Magic Trackpad/ Mouse issue. Are you using any special settings for these devices? Does the issue happen even if you use the mirror mode settings?

Debug information
 

Hello everybody,

here is the debug information you asked for: DisplayLink Information

I managed to use Firefox 5.0 now without the Use Hardware Acceleration feature, but if possible, I would like to re-enable it in the future. The click/drag problem occurs with the Magic Trackpad AND any other HID device. I am using a Logitech MX500. If necessary I can screen capture the problem for you and put it on Youtube or so.

:) Thanks for your help!

mhhhhhhhhcookies :)

Thanks, for the debug information. Unfortunately we are still unable to reproduce the click/drag problem. It seems that your system acts as the drag lock option is active for your mouse. Does the problem disappear if you unplug the DisplayLink monitor? Does the issue happens if you reboot the machine without plugging in the DisplayLink monitor? Thanks

1.7b2 Bug: Dock uneditable and can't log in if autologin is turn off
 

I installed 1.7b2 on a machine running a GM of Lion. Immediately, after the restart I noticed the following things.

1. If I have autologin disabled then the system boots to the login screen but doesn't display any users. Basically, all I see is the gray wallpaper.

2. Once I enable autologin, the restart is gets me into my desktop. From there the dock is non-editable. For instance, try to drag an app into the dock. You cannot. You have to launch the app, right click on the icon in the dock, go to options, keep in dock. You also cannot remove an app, by dragging it out of the dock.

3. The system takes a lot longer to shut down and reboot.

Once I remove the driver, the system functions normally. The display hooked up to the displaylink adapter does work, but these performance issues make it hard to keep it installed and in use.

I also have the Firefox 5 issue where it doesn't show any content and only the header.

Also, with the DisplayLink driver installed, I can't play any videos using VLC or Quicktime. All I see is a blank window and I can hear the audio. If I uninstall the driver, the videos work correctly.

Same situation as above. However enabling autologin is not an option for me. So I booted into safe mode and uninstalled. Worked fine afterwards.

Can't wait for beta 3 :)

Ways to reproduce it:
MacBook Pro (fall 09), fresh Lion GM install, fresh beta2 driver install. Without attaching the monitor nor attaching a USB mouse, after the restart of os x the magic track pad has said bugged functionality. Very strange.

Thanks.

I can confirm the drag issue. I tried to drag an icon and the "release mouse button" never triggered.

Also, my earlier issue with no video playing with VLC/Quicktime was resolved if I use 9600M instead of the 9400M on my 2009 Macbook Pro. Firefox also works with the 9600M in use.

Crash Report from DisplayLinkManager
 

Process: DisplayLinkManager [114]
Path: /System/Library/Extensions/DisplayLinkDriver.kext/DisplayLinkAgent/DisplayLinkManager
Identifier: DisplayLinkManager
Version: ??? (0.3)
Code Type: X86 (Native)
Parent Process: USBNivoListener [97]

Date/Time: 2011-07-05 09:12:22.129 +0100
OS Version: Mac OS X 10.7 (11A511)
Report Version: 9

Crashed Thread: 6

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
objc[114]: garbage collection is OFF
abort() called
terminate called throwing an exception

Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x91b98c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91b981f6 mach_msg + 70
2 com.apple.CoreFoundation 0x961609ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x96169b14 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x961691ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x96179f11 CFRunLoopRun + 129
6 DisplayLinkManager 0x000190be dl::sys::Logger::Logged::LogStream::~LogStream() + 14126
7 DisplayLinkManager 0x0001a44c dl::sys::Logger::Logged::LogStream::~LogStream() + 19132
8 DisplayLinkManager 0x0000ee69 std::vector<dl::sys::VideoTiming, std::allocator<dl::sys::VideoTiming> >::push_back(dl::sys::VideoTiming const&) + 28425
9 DisplayLinkManager 0x0000ed98 std::vector<dl::sys::VideoTiming, std::allocator<dl::sys::VideoTiming> >::push_back(dl::sys::VideoTiming const&) + 28216

Thread 1:
0 libsystem_kernel.dylib 0x91b9ab5e __select_nocancel + 10
1 libsystem_kernel.dylib 0x91b99af6 select + 89
2 DisplayLinkManager 0x000b9808 dl::sys::PersistBadAccess::~PersistBadAccess() + 1224
3 DisplayLinkManager 0x000b98fa dl::sys::PersistBadAccess::~PersistBadAccess() + 1466
4 DisplayLinkManager 0x0002d460 non-virtual thunk to dl::nivo::DeviceManagerImpl::~DeviceManagerImpl() + 13344
5 DisplayLinkManager 0x000bbd1d dl::sys::Thread::State::StartThread(void*) + 45
6 libsystem_c.dylib 0x95a53ed9 _pthread_start + 335
7 libsystem_c.dylib 0x95a576de thread_start + 34

Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x91b9b90a kevent + 10
1 libdispatch.dylib 0x929e0ccc _dispatch_mgr_invoke + 969
2 libdispatch.dylib 0x929df71b _dispatch_mgr_thread + 53

Thread 3:
0 libsystem_kernel.dylib 0x91b9b02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x95a55ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x95a576fe start_wqthread + 30

Thread 4:
0 libsystem_kernel.dylib 0x91b9b02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x95a55ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x95a576fe start_wqthread + 30

Thread 5:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x91b9ab42 __select + 10
1 com.apple.CoreFoundation 0x961b79e5 __CFSocketManager + 1557
2 libsystem_c.dylib 0x95a53ed9 _pthread_start + 335
3 libsystem_c.dylib 0x95a576de thread_start + 34

Thread 6 Crashed:
0 libsystem_kernel.dylib 0x91b9a9c6 __pthread_kill + 10
1 libsystem_c.dylib 0x95a55f78 pthread_kill + 106
2 libsystem_c.dylib 0x95a46bdd abort + 167
3 libc++abi.dylib 0x94660921 abort_message + 94
4 libc++abi.dylib 0x9465e1bc default_terminate() + 36
5 libc++abi.dylib 0x9465e1fe safe_handler_caller(void (*)()) + 15
6 libc++abi.dylib 0x9465e268 std::terminate() + 23
7 libc++abi.dylib 0x9465f2a0 __cxa_throw + 112
8 DisplayLinkManager 0x0001e51e dl::sys::display::MonitorId::MonitorId() + 11374
9 DisplayLinkManager 0x0001767b dl::sys::Logger::Logged::LogStream::~LogStream() + 7403
10 DisplayLinkManager 0x00017c68 dl::sys::Logger::Logged::LogStream::~LogStream() + 8920
11 DisplayLinkManager 0x000185d9 dl::sys::Logger::Logged::LogStream::~LogStream() + 11337
12 libsystem_c.dylib 0x95a53ed9 _pthread_start + 335
13 libsystem_c.dylib 0x95a576de thread_start + 34

It seems that you are using the 9400M, could you please switch to the 9600M and check if the issues are still there? Thanks