similar to: Page fault in xinerama_init

This is release 0.9.54 of Wine, a free implementation of Windows on Unix. What's new in this release: - Photoshop CS/CS2 should now work, please help us testing it. See http://wiki.winehq.org/AdobePhotoshop for details. - A number of RPC fixes. - Various improvements to the debugger support. - Lots of bug fixes. Because of lags created by using mirrors, this message may reach you

This is release 0.9.55 of Wine, a free implementation of Windows on Unix. What's new in this release: - Direct3D improvements, including driver version emulation. - Beginnings of support for OLE objects in Richedit. - Several fixes to the animation control. - A bunch of fixes for regression test failures. - Lots of bug fixes. Because of lags created by using mirrors, this message

The Wine development release 1.5.9 is now available. What's new in this release (see below for details): - Support for GPOS font tables in Uniscribe. - Support for XRandr 1.2 and 1.3. - Parser improvements for the HLSL compiler. - More key exchange algorithms supported on Mac OS. - Relay tracing on ARM. - Various bug fixes. The source is available from the following locations:

Wine 9.30 Slackware 11 ATI FireGL 5200 (Propriatory drivers) I found Shogun in a shop as a 'Classic' game and I've been trying to get it to work using Wine. Shogun uses Safedisc and so does not work in it's, ahem, original form. However it can, shall we say, be persuaded to get over it's difficulties and at least run. This is where I am now. I have the game running and

Hi all, The PF_RING seems not to work smoothly in CentOS 5. Several day before, I patched the kernel 2.6.25.3 and installed the PF_RING-patched kernel in my CentOS5. Based on the PF_RING, I developed my program to capture the network packages. I wished it can work until the machine power is off. Unforturnately, no matter how to adjust my program, whole system can not run more than 48 hours.

I am seeing this in dmesg on Dell Poweredge 860 INFO: task tail:17872 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. tail D ffff81021ac87040 0 17872 31199 (NOTLB) ffff810124fc7bd8 0000000000000082 ffff81021c8ad200 ffff8101714f4d80 0000000000000000 0000000000000007 ffff81016471b820 ffff81021ac87040

Dear All, I selected CentOS5 in my works and installed them in two DELL PowerEdge1950. However, a trouble blocked me during the machines run after two days. The machines crashed and the syslog said it got the following messages: ------------------ part dump of /var/log/messages ---------------------- ..... Jul 25 02:15:02 vega2008 kernel: [<c045bc58>] ? exit_mmap+0x93/0xc9 Jul 25

Hi. I have tried this email also with thunderbird imap which works. So this is as special Problem with the imap-module of the Horde framework. I will do some more debugging this evening. My Horde framework has the following Versions: Horde Groupware Webmail Edition 5.2.7 Horde (horde) 5.2.6 Horde_Imap_Client 2.29.1 Regards, Michael. Am 28.07.2015 um 09:12 schrieb Michael Borgelt: > Hi, >

Hi everyone, I hope this is the correct list to discuss this issue; please feel free to redirect me otherwise. I have a nested virtualization setup that looks as follows: - Host: Ubuntu 16.04, kernel 4.4.0 (an OpenStack Nova compute node) - L0 guest: openSUSE Leap 42.3, kernel 4.4.104-39-default - Nested guest: SLES 12, kernel 3.12.28-4-default The nested guest is configured with

Hi, I got the following in my dovecot log's on an particular email message with dovecot-imap. ---snip--- Jul 28 08:42:11 hermes dovecot: imap(mborgelt): Panic: file index-mail-binary.c: line 354 (blocks_count_lines): assertion failed: (ret == -1) Jul 28 08:42:11 hermes dovecot: imap(mborgelt): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x740f2) [0xb75780f2] ->

Hi, I've installed 7.2-PRERELEASE, csup on 20090423 at around 19:00 UTC. When I rebooted after installing world, X started (xdm in /etc/ttys) and immediately panicked the system, even before switching to the new VTY. I removed all ports and installed Xorg from today's ports HEAD, same result. This is the case with my old xorg.conf and a new one from 'Xorg -configure'. I