http://bugs.winehq.com/show_bug.cgi?id=377
*** shadow/377 Tue Jun 4 05:49:44 2002
--- shadow/377.tmp.31043 Wed Jun 5 12:40:36 2002
***************
*** 2,13 ****
| mIRC crashes while backspacing to erase entry |
+----------------------------------------------------------------------------+
| Bug #: 377 Product: Wine |
! | Status: UNCONFIRMED Version: unspecified |
| Resolution: Platform: |
| Severity: normal OS/Version: All |
! | Priority: P1 Component: wine-misc |
+----------------------------------------------------------------------------+
! | Assigned To: wine-bugs(a)winehq.com |
| Reported By: samlb(a)am-cath.org |
+----------------------------------------------------------------------------+
| Milestone: TargetMilestone: --- |
--- 2,13 ----
| mIRC crashes while backspacing to erase entry |
+----------------------------------------------------------------------------+
| Bug #: 377 Product: Wine |
! | Status: NEW Version: unspecified |
| Resolution: Platform: |
| Severity: normal OS/Version: All |
! | Priority: P1 Component: wine-kernel |
+----------------------------------------------------------------------------+
! | Assigned To: andi(a)rhlx01.fht-esslingen.de |
| Reported By: samlb(a)am-cath.org |
+----------------------------------------------------------------------------+
| Milestone: TargetMilestone: --- |
***************
*** 93,95 ****
--- 93,111 ----
trace:edit:EDIT_MakeFit notification EN_ERRSPACE sent to hwnd=00030043
Anybody any suggestions?
+
+ ------- Additional Comments From apa3a(a)yahoo.com 2002-06-05 12:40 -------
+ I found a simpler way to reproduce, one can even be offline.
+ **********************************************
+ 1) Execute mIRC under WINE
+ 2) Click "List Channels" button on the toolbar (the 4th from the left).
+ 3) hold down "." key in the "Match text" combo to generate more than 64
+ characters on a line
+ 4) hold down BS key to erase -- miRC freezes at about 63 characters
+ IIRC --
+ see original bug description
+ **********************************************
+
+ It looks like it is the memory allocation bug. The crash happens while
+ allocating a new block of memory (see the backtrace below).
+ Forwarding to Andreas.
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=757
*** shadow/757 Wed Jun 5 03:14:40 2002
--- shadow/757.tmp.23337 Wed Jun 5 10:45:44 2002
***************
*** 69,71 ****
--- 69,75 ----
Thank you! I am so glad that somebody has a solution!
I shall try it.
+
+ ------- Additional Comments From johane(a)lysator.liu.se 2002-06-05 10:45 -------
+ Have you tried changing the "Drivers" entry in the config file to "winearts.drv"?
+ If that doesn't give sound with the daemon active, I guess it's a Bug.
http://bugs.winehq.com/show_bug.cgi?id=757
*** shadow/757 Tue Jun 4 22:19:25 2002
--- shadow/757.tmp.31943 Wed Jun 5 03:14:40 2002
***************
*** 64,66 ****
--- 64,71 ----
bug is reproducible for me in any application I have : no sound at all
if artsd is not suspended.
+
+ ------- Additional Comments From pavel.reznicek(a)wo.cz 2002-06-05 03:14 -------
+ Thank you! I am so glad that somebody has a solution!
+
+ I shall try it.
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=757
*** shadow/757 Tue Jun 4 21:40:10 2002
--- shadow/757.tmp.19770 Tue Jun 4 22:19:25 2002
***************
*** 2,8 ****
| Sound bug: only sometimes - wodDsCreate DirectSound flag not set |
+----------------------------------------------------------------------------+
| Bug #: 757 Product: Wine |
! | Status: UNCONFIRMED Version: 20020509 |
| Resolution: Platform: |
| Severity: normal OS/Version: All |
| Priority: P1 Component: wine-directx |
--- 2,8 ----
| Sound bug: only sometimes - wodDsCreate DirectSound flag not set |
+----------------------------------------------------------------------------+
| Bug #: 757 Product: Wine |
! | Status: NEW Version: 20020509 |
| Resolution: Platform: |
| Severity: normal OS/Version: All |
| Priority: P1 Component: wine-directx |
***************
*** 13,18 ****
--- 13,19 ----
+----------------------------------------------------------------------------+
| Milestone: TargetMilestone: --- |
| URL: |
+ | Dependencies: BugsThisDependsOn: 325[] |
+============================================================================+
| DESCRIPTION |
In most runs of Wine, I get no sound. But SOMETIMES it luckily happens that I
***************
*** 54,56 ****
--- 55,66 ----
Under Gnome, if I choose the wineoss.drv driver, all works perfect.
Also it did under KDE 2.0.0. But under KDE 3.0.0, there is it a thing of
fortune if the sound starts properly or not. In most cases, it doesn't.
+
+ ------- Additional Comments From spetreolle(a)yahoo.fr 2002-06-04 22:19 -------
+ there is a way to have sound under kde : run artscontrol and suspend it.
+
+ but if I remember this issue was resolved with the implementation of the arts
+ driver. see bug 325.could be a regression.
+
+ bug is reproducible for me in any application I have : no sound at all
+ if artsd is not suspended.
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=63
*** shadow/63 Tue Jun 4 20:51:17 2002
--- shadow/63.tmp.16846 Tue Jun 4 21:06:53 2002
***************
*** 7,13 ****
| Severity: enhancement OS/Version: All |
| Priority: P1 Component: wine-tools |
+----------------------------------------------------------------------------+
! | Assigned To: wine-bugs(a)winehq.com |
| Reported By: fgouget(a)codeweavers.com |
| CC list: Cc: |
+----------------------------------------------------------------------------+
--- 7,13 ----
| Severity: enhancement OS/Version: All |
| Priority: P1 Component: wine-tools |
+----------------------------------------------------------------------------+
! | Assigned To: fgouget(a)codeweavers.com |
| Reported By: fgouget(a)codeweavers.com |
| CC list: Cc: |
+----------------------------------------------------------------------------+
***************
*** 77,79 ****
--- 77,83 ----
it is for me to reassign it to wine-bugs(a)winehq.com and then have someone else
reassign it to me (I guess I should have done something like this a long time
ago, sorry).
+
+
+ ------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-06-04 21:06 -------
+ Reassigning bug to François Gouget. Hope this works...
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=767
*** shadow/767 Tue Jun 4 20:58:40 2002
--- shadow/767.tmp.16369 Tue Jun 4 20:58:40 2002
***************
*** 0 ****
--- 1,28 ----
+ +============================================================================+
+ | Unable to start debugger / recurrent "parse error" message |
+ +----------------------------------------------------------------------------+
+ | Bug #: 767 Product: Wine |
+ | Status: UNCONFIRMED Version: CVS |
+ | Resolution: Platform: |
+ | Severity: normal OS/Version: All |
+ | Priority: P1 Component: wine-debug |
+ +----------------------------------------------------------------------------+
+ | Assigned To: wine-bugs(a)winehq.com |
+ | Reported By: spetreolle(a)yahoo.fr |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | Milestone: TargetMilestone: --- |
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ Running debugger invoked as 'winedbg' everywhere writes endless :
+ Wine-dbg>parse error
+
+ and everytime the debugger is launched by a program, the same message appears
+ and the backtrace is written endless. So I must kill all process.
+
+ The only way to launch it without errors is to launch './winedbg' in source tree
+ or launch the debugger with '--debugmsg +module'.
+
+ If I launch 'winedbg _someapp_', the program starts automatically without being
+ asked to.
\ No newline at end of file