similar to: Segfault creating font metrics

Everytime I start a program with wine-20010629 on Red Hat Linux, font metrics get updated. I am getting fonts through the Xserver (no xfont server) (currently M$, ghostscript, Type1, misc and 75dpi fonts) Is this behaviour normal? Everytime this happens, I get lots of output like fixme:font:LFD_InitFontInfo DBCS fonts like '-urw-century schoolbook

I have tried to run this unsuccessfully, the error log being as follows: Building font metrics. This may take some time... fixme:font:LFD_InitFontInfo DBCS fonts like '-daewoo-gothic-medium-r-normal--16-120-100-100-c-160-ksc5601.1987-0' are not working correctly now. fixme:font:LFD_InitFontInfo DBCS fonts like '-daewoo-mincho-medium-r-normal--16-120-100-100-c-160-ksc5601.1987-0'

Hi All Newbie to wine here :) I have installed wine, and can get notepad and winemine up, but when I do, I get a painfully long list of messages and then it goes into Font Metrics 1.1% - Font Metrics 1.2% untill we eventually get to 100%. I also tried to run File Maker Pro 5 for windows, however the window opened and just hung for about 15 mins before I killed the process. I have checked the

Hi, When I ran wine for the first time, font metrics information is built. It doesn't take a lot of time, but when you are forwarding X session over half a world, this can be pretty slow and annoying. Well, I know that there is probably no way how to avoid this, but I think there is a way how to avoid this when you reinstall wine. So, question is, where is stored font metrics information

Sylvain wrote: > Running into problems with fonts, > I erased the ~/.wine/cachedmetrics file to regenerate > them. > > Lots of fixme are displayed, a sample : > fixme:font:LFD_InitFontInfo font > '-greek-lucidatypewriter-medium-r-normal-sans-14-140-75-75-m-90-dos-737' > has unknown registry 'dos' and character encoding > '737' > > Can I

This is a problem I've had on my machines (several) recently. All are Debian 3.0 (Woody) machines. The problem is reproducable 100% of the time, whether I am using WINE locally or exporting the display across the LAN to my laptop; the problem exists in pre-built RH 7.3 WINE RPMs Debianized with alien --to-deb _AND_ with WINEs I built from source. When starting up WINE, it starts building the

Wine spits out a buch of error messages of the form: fixme:font:LFD_InitFontInfo font '-monotype-times new roman-medium-r-normal--0-0-0-0-p-0-fcd8859-15' has unknown registry 'fcd8859' and character encoding '15' Is there a switch to get it forget about it's font server. I'm running batch mode programs so fonts are irrelevant. Thanks,

Hi, Running into problems with fonts, I erased the ~/.wine/cachedmetrics file to regenerate them. Lots of fixme are displayed, a sample : fixme:font:LFD_InitFontInfo font '-greek-lucidatypewriter-medium-r-normal-sans-14-140-75-75-m-90-dos-737' has unknown registry 'dos' and character encoding '737' Can I ignore them or could them be source of problems ?

Guests other than domain 0 using the console output have previously been controlled by the VERBOSE define, but with no designation of which guest''s output was on the console. This patch converts the HVM output buffering to be used by all domains, line buffering their output and prefixing it with the domain ID. This is especially useful for debugging stub domains. Signed-off-by: Daniel De

On Sun, 2004-08-08 at 14:10, Dr Mike Waters wrote: snip > Thanks for the responses guys. > > I used to have RH9 installed on this machine and I found out about the > separate developer packages then. I thought that I had got the relevant > XFree devel package installed, but although it showed up in the rpm database > as being present, the required files were not present. I did

OpenSSH 5.1p1 I can't grasp why, when connecting with 'ssh -Y' to this test host, I am not tickling the verbose() call below that I have added. I am logging as auth + verbose in sshd_config The X11 forward for the session works fine as tested with xterm. At any rate, I am looking for some guidance on where to log X11 forwards that are established, ideally with a username and remote

The variable local_user was allocated by xstrdup and is not freed or pointed to in this branch. This patch adds the xfree. This entire set of patches passed the regression tests on my system. Bug found by Coverity. Signed-off-by: Kylene Hall <kjhall at us.ibm.com> --- sshconnect.c | 1 + 1 files changed, 1 insertion(+) diff -uprN openssh-4.3p2/sshconnect.c

This fixes an actual bug (failure to exit from a function after an allocation failure), an inconsistency (not removing the cpufreq_dom list member upon failure), and a latent bug (not clearing the current governor upon governor initialization failure when there was no old one; latent because the only current code path leading to this situation frees the policy upon failure and hence the governor

Jan, This patch just used to stick all 1''s to MCi_CTL, it should not involve much argue, so I sent it separately. Thanks, Jinsong ==================== Xen/MCE: stick all 1''s to MCi_CTL of vMCE This patch is a middle-work patch, prepare for future new vMCE model. It remove mci_ctl array, and keep MCi_CTL all 1''s. Signed-off-by: Liu, Jinsong

Hi ! Here's a patch to add remote port forwarding support (protocol 2) for openssh. I have tried to test that it works like it should but a more thorough testing is needed. This patch adds both client/server support. The patch should be applied to openssh-2.1.1p4 source tree. Also included is a PortForwarding sshd_config option, new ./configure option --disable-forwarding that should make it

Hi all I'm trying to play the game "BOH" (http://www.bohthegame.com/) on OS X using Darwine. I downloaded 1.1.19 and dragged the Darwine folder to /Applications. Then I opened the BOH installer using WineHelper and installed the game. For some reason it put the installed files inside the WineHelper application bundle. When I tried to open the game's executable using WineHelper,

--- mux.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/mux.c b/mux.c index d90605e..fa796bd 100644 --- a/mux.c +++ b/mux.c @@ -1195,6 +1195,7 @@ muxserver_listen(void) close(muxserver_sock); muxserver_sock = -1; } + xfree(orig_control_path); xfree(options.control_path); options.control_path = NULL; options.control_master = SSHCTL_MASTER_NO;

And while we are at it, can you please comment on these patches as well, originally submitted around one year ago. Oh, and I think we can agree, that the secsh-filexfer standardization is dead, so there's not much point in trying to support newer protocol versions, which don't have statfs anyway. Thanks, Miklos ----- This is needed to be able to support statfs operation on an SSH

Hi, the following patch fixes a potential security hole in the Cygwin version of sshd. If you're logging in to a Cygwin sshd with version 2 protocol using an arbitrary user name which is not in /etc/passwd, the forked sshd which is handling this connection crashes with a segmentation violation. The client side encounters an immediate disconnect ("Connection reset by peer").

As far as I know this patch has no security implications -- I don't believe that allowing sshd to use get_local_name() (in canohost.c) on a connected socket to determine it's own fqdn will allow a malicious client (or router or dns server) to make it come to the wrong conclusion. But please let me know if you think I'm wrong. Please also let me know if you're just not interested