Launchpad has imported 32 comments from the remote bug at http://bugs.winehq.org/show_bug.cgi?id=6547.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2006-10-28T21:16:30+00:00 Ajackso2-connect wrote: The last Wine version that worked on my system (FC5 x86-64) was 0.9.22. 0.9.23 and 0.9.24 just hang forever when I attempt to run any application, including builtin applications like winecfg. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/0 ------------------------------------------------------------------------ On 2006-10-28T21:17:57+00:00 Ajackso2-connect wrote: Created an attachment (id=3960) 0.9.22 and 0.9.23 strace outputs Outputs of strace -ff -o when running winecfg from 0.9.22 (which works) and from 0.9.23 (which hangs) Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/1 ------------------------------------------------------------------------ On 2006-10-28T22:18:12+00:00 Mike-codeweavers wrote: Please do a regression analysis, as described in the "regression testing" section of the GitWine wiki page, and tell us the ID of the commit which caused the regression. http://wiki.winehq.org/GitWine Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/2 ------------------------------------------------------------------------ On 2006-10-29T02:57:52+00:00 Alexandre Julliard wrote: Most likely the XInitThreads change. You should get a backtrace of the hanging thread to find out which X11 function is deadlocking. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/3 ------------------------------------------------------------------------ On 2006-10-29T03:10:59+00:00 Ajackso2-connect wrote: How do I do that? I assume that I use winedbg, but how do I identify the thread which is hung up? I'm semi-familiar with gdb on Un*x but I have no experience with winedbg and no experience debugging (or programming really) in Windows-land either. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/4 ------------------------------------------------------------------------ On 2006-10-29T03:37:05+00:00 Alexandre Julliard wrote: If you see the hang with winecfg or notepad then there should only be one thread running. Otherwise a 'bt all' will show a backtrace for all the threads, you can then see which one is inside an X11 call. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/5 ------------------------------------------------------------------------ On 2006-10-29T04:08:09+00:00 Ajackso2-connect wrote: Every Wine-related process appears to be stopped at "0xffffe405 in ?? ()" Isn't that a (Linux) kernel space address...? I don't have kernel-debuginfo installed; please tell me if I'm mistaken so I can spare myself the fairly enormous download. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/6 ------------------------------------------------------------------------ On 2006-10-29T04:19:37+00:00 Ajackso2-connect wrote: The hangup is definitely occurring in wine-preloader. Each time I attempt to run a Wine application, after I ctrl-c the hung application a wine-preloader process is left behind which will only die if I kill -9 it (just kill'ing it leaves it [defunct]). All of these processes turn out to be stopped at the exact same (kernel space?) address when I attach gdb to them. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/7 ------------------------------------------------------------------------ On 2006-10-29T05:21:27+00:00 Ajackso2-connect wrote: What am I doing wrong with winedbg? Whether I run winecfg directly through winedbg, or run winedbg from a separate terminal after running winecfg, I can't get a proper backtrace. All the thread backtraces look like this, with only two lines: =>1 0xffffe405 (0x00000001) 2 0x00000000 (0x00000000) Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/8 ------------------------------------------------------------------------ On 2006-10-29T09:06:36+00:00 Alexandre Julliard wrote: I don't think kernel debug info would help much. Maybe you can get more information by attaching to the hung process with gdb? Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/9 ------------------------------------------------------------------------ On 2006-10-29T14:49:06+00:00 Ajackso2-connect wrote: All right, I can get a full backtrace by running "gdb wine" and then attaching it to the hung process, but the backtrace has no symbolic information, because (I think) gdb can't automatically pick up shared libraries when you attach it to an already-running process. Would it help if I built wine from source so as to have the symbolic information right in the binaries, rather than in a debuginfo package? Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/10 ------------------------------------------------------------------------ On 2006-10-30T03:24:18+00:00 Alexandre Julliard wrote: Building from source is probably a good idea, yes. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/11 ------------------------------------------------------------------------ On 2006-10-30T07:07:05+00:00 Ajackso2-connect wrote: I've discovered that the lockup is somehow related to SCIM. If I remove SCIM from my profile by renaming ~/.xinput.d/, log out and log back in, Wine starts normally. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/12 ------------------------------------------------------------------------ On 2006-10-31T13:28:21+00:00 Ajackso2-connect wrote: Confirmed that the "Give XInitThreads another chance" commit is what caused the regression (before this commit, Wine works with SCIM and does not hang) Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/13 ------------------------------------------------------------------------ On 2006-10-31T14:46:59+00:00 Alexandre Julliard wrote: You'll probably want to report this to the SCIM team. Did you get a meaningful backtrace of the hang? Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/14 ------------------------------------------------------------------------ On 2006-11-01T06:29:20+00:00 Ajackso2-connect wrote: Sorry for posting second-hand information, but I've been told by some Japanese users that other input methods (Canna, UIM) are also causing Wine >= 0.9.23 to hang, not just SCIM. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/15 ------------------------------------------------------------------------ On 2006-11-01T06:36:30+00:00 Alexandre Julliard wrote: That's very possible, there's a bug in Xlib where XFilterEvent calls the filters with the display lock held, so if an IM filter gets the lock it deadlocks. I added a workaround for the standard XIM lib, but others input methods probably need the same treatment. If we know exactly what causes the deadlock we may be able to find a way around it too. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/16 ------------------------------------------------------------------------ On 2006-11-08T02:37:10+00:00 Ek-kato wrote: I think this is caused from a bug in Xlib. See https://bugs.freedesktop.org/show_bug.cgi?id=1182, and the patch in comment #12 (https://bugs.freedesktop.org/attachment.cgi?id=4874) should solve the problem. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/17 ------------------------------------------------------------------------ On 2006-11-17T08:58:38+00:00 Alexandre Julliard wrote: *** Bug 6648 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/18 ------------------------------------------------------------------------ On 2006-11-22T20:49:53+00:00 Vitaliy-bugzilla wrote: *** Bug 6754 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/19 ------------------------------------------------------------------------ On 2006-11-28T05:57:20+00:00 Alexandre Julliard wrote: *** Bug 6798 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/20 ------------------------------------------------------------------------ On 2006-11-29T09:39:45+00:00 Chriswhite wrote: I got this in a wine-git I pulled on November 26th. Seems to be isolated to Japanese IM's as stated before. Setting XMODIFIERS to an empty value (export XMODIFIERS="") appears to temporarily fix this for applications. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/21 ------------------------------------------------------------------------ On 2006-12-11T23:42:40+00:00 Vitaliy-bugzilla wrote: *** Bug 6872 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/22 ------------------------------------------------------------------------ On 2006-12-12T09:10:23+00:00 Vitaliy-bugzilla wrote: *** Bug 6875 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/23 ------------------------------------------------------------------------ On 2006-12-13T03:11:10+00:00 Steven McCoy wrote: *** Bug 6886 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/24 ------------------------------------------------------------------------ On 2007-02-10T09:59:45+00:00 Vitaliy-bugzilla wrote: It looks like Fedora Core 6 comes equipped with this bug right from the start. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/25 ------------------------------------------------------------------------ On 2007-02-12T19:13:19+00:00 Vitaliy-bugzilla wrote: *** Bug 7399 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/26 ------------------------------------------------------------------------ On 2007-02-14T20:18:45+00:00 Vitaliy-bugzilla wrote: *** Bug 7429 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/27 ------------------------------------------------------------------------ On 2007-04-14T03:51:18+00:00 Wolput wrote: Wine 0.9.35 works with SCIM. Bug 6547 seems to be fixed! Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/29 ------------------------------------------------------------------------ On 2007-04-14T11:10:51+00:00 Vitaliy-bugzilla wrote: Correct - it is fixed there was a workaround committed right before 0.9.35. Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/30 ------------------------------------------------------------------------ On 2007-04-16T20:51:43+00:00 Vitaliy-bugzilla wrote: *** Bug 8073 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/31 ------------------------------------------------------------------------ On 2007-04-27T22:14:35+00:00 Tony-lambregts wrote: Closing Reply at: https://bugs.launchpad.net/wine/+bug/85430/comments/32 ** Changed in: wine Importance: Unknown => High ** Bug watch added: freedesktop.org Bugzilla #1182 http://bugs.freedesktop.org/show_bug.cgi?id=1182 -- Wine hangs (freezes) when starting any program https://bugs.launchpad.net/bugs/85430 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
