https://bugs.winehq.org/show_bug.cgi?id=44167
Bug ID: 44167 Summary: UK's Kalender crashes on startup. Product: Wine Version: 3.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: old.git@net98.eml.cc Distribution: ---
Created attachment 59931 --> https://bugs.winehq.org/attachment.cgi?id=59931 Wine crash report saved to file
UK's Kalender crashes on startup.
Was working flawlessly on Wine 2.22. Immediately on update to 3.0 rc1 it reliable crashes on startup.
System is standard Wine with extra dlls via Winetricks (cmd.exe, ffdshow, mfc42, vb6run, vc6run, vc6runsp6, wsh57). All needed to get various programs running.
Program is portable version of UK's Kalender.exe from http://www.ukrebs-software.de/download/kalender/Kalender_Portable.zip Present on this machine is one of the 2.5.x series (not sure which and cannot start the program to check)
Steps to reproduce: Start running the program either 1. from PSMenu portable program launcher (itself install on Wine), OR 2. right click the Kalender.exe file in Thunar and select "Open wwith Wine Windows Program Loader"
Actual Result: Program fails to start, crash report displayed.
Expected Result: Program to work without flaw (as on Wine 2.22)
Bug first encountered: with Wine 3.0rc1
Other systems: Program runs exactly as expected on Wine 2.22 and below, and on Windows 98SE to Windows XP Pro.
https://bugs.winehq.org/show_bug.cgi?id=44167
old git old.git@net98.eml.cc changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |old.git@net98.eml.cc
https://bugs.winehq.org/show_bug.cgi?id=44167
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x@gmail.com
--- Comment #1 from Louis Lenders xerox.xerox2000x@gmail.com --- Hi, I cannot confirm this. I downloaded the zipfile, and ran the exe, and it just starts without crashing here.
wine --version wine-3.0-rc1
sha1sum Kalender_Portable.zip 756b378f723aa0f73dec6ae2d4de03810c25cd68 Kalender_Portable.zip
https://bugs.winehq.org/show_bug.cgi?id=44167
--- Comment #2 from old git old.git@net98.eml.cc --- OK, you catch me out for being a first time bug reporter.
I did not try to run the download raw and without any existing data file. I have now done that and agree that used in that manner the program operates.
The moment I introduce my existing data file (happily saved by Kalender 2.5.1 using Wine 2.22 on Linux Mint 17.3) it crashes. It seems to me that the way it parses the data file was OK in W2.22, but has been changed with W3.0rc1.
https://bugs.winehq.org/show_bug.cgi?id=44167
--- Comment #3 from Louis Lenders xerox.xerox2000x@gmail.com --- (In reply to old git from comment #2)
OK, you catch me out for being a first time bug reporter.
I did not try to run the download raw and without any existing data file. I have now done that and agree that used in that manner the program operates.
The moment I introduce my existing data file (happily saved by Kalender 2.5.1 using Wine 2.22 on Linux Mint 17.3) it crashes. It seems to me that the way it parses the data file was OK in W2.22, but has been changed with W3.0rc1.
Could you attach that datafile, so we can reproduce the crash to investigate? (or another datafile that makes the app crash if it contains private stuff that you don`t wont to share)
https://bugs.winehq.org/show_bug.cgi?id=44167
--- Comment #4 from old git old.git@net98.eml.cc --- With almost every detail of my life over the past umpteen years in the active data file, you will understand my reticence about providing that file for public display!
In trying to replicate the problem with a freshly manufactured data file I hit several difficulties. I am unaware whether each should be filed as a separate bug or not, please advise
1. The calender only displays 1 - 15 and 31 of every month. Dates 16 - 30 inclusive are instead transformed into 01 Jan and are unresponsive.
2. Scrolling using the big arrow buttons are the top of the screen does not work.
3. The data file (that I am trying to give you a dummy of) contains many birthdays. When I try to set a template for birthdays (see helpfile | FAQ | last item: How can I display the age ..etc..) I can open the template editor (Extras | Categories). In the Edit Category window go to the Category line and press the button immediately to the right of the down arrow. A new sub-window headed New Category will open. Amend the entry to Birthday, press OK, and be rewarded for your pains with the Wine Program Error window.
There are probably other things that do not work as expected that I have not yet noticed.
I have now installed Wine3.0rc2 with no discernable difference on this problem.
https://bugs.winehq.org/show_bug.cgi?id=44167
--- Comment #5 from old git old.git@net98.eml.cc --- Just started using Wine 3.0 rc3. Problems all seem to have vanished.
https://bugs.winehq.org/show_bug.cgi?id=44167
old git old.git@net98.eml.cc changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME
--- Comment #6 from old git old.git@net98.eml.cc --- Vanished with Wine 3.0 rc3
https://bugs.winehq.org/show_bug.cgi?id=44167
old git old.git@net98.eml.cc changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|WORKSFORME |---
--- Comment #7 from old git old.git@net98.eml.cc --- In Wine 3.0-rc4 the data file opens and operates as expected. HOWEVER, in attempting to make a new entry if the user attempts to change the CATEGORY from Event to Birthday for example, the program crashes as before.
I had previously marked the status as RESOLVED on the basis of limited checking of rc3. I now mark it as the worst that I can, which is UNCONFIRMED.
https://bugs.winehq.org/show_bug.cgi?id=44167
--- Comment #8 from old git old.git@net98.eml.cc --- In Wine 3.0-rc5 the issue remains unresolved
https://bugs.winehq.org/show_bug.cgi?id=44167
--- Comment #9 from old git old.git@net98.eml.cc --- Wine 3.0-rc6 Program appears to run OK on first sight but continues to crash when trying to change event category.
https://bugs.winehq.org/show_bug.cgi?id=44167
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #10 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-5.22?
https://bugs.winehq.org/show_bug.cgi?id=44167
wineuser101@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wineuser101@mailbox.org
--- Comment #11 from wineuser101@mailbox.org --- I can confirm that the program crashes using the latest development version of wine (8.6) when trying to change the event category of an entry as described before by "old git". There is a workaround that solves this crash and other bugs that I will detail below (winetricks comctl32), but it also introduces new bugs.
As "old git" have written before, the crash at startup is no longer a problem. However, it can't start without installing mfc42 via winetricks.
If one has a clean install of the program the most straightforward way to induce the crash is to go to Extras, Categories and then press on the small button with a blank paper on it, right to the "Event" box. After writing a random name of a new category, and it will crash when one presses "OK". I've attached a screenshot with the cursor on top of the button in question. I've also attached a backtrace log of the crash.
There are also several bugs related to the ToDo tab. They can be visualized by adding two new entry to the list by right-clicking and pressing New.
The first bug is that one can't reliably select the entry by either double-clicking or right clicking. If one changes tab to Week for example, and then goes back to the ToDo tab, one entry can be selected and edited, but if one right clicks on the other entry the edit windows will still open the other entry. Sometimes the entries can't be selected at all.
The other bug is that the progress bar is broken. If one changes the Progress Done percentage of a todo entry, the green progress bar is broken.
I discovered a workaround by bruteforce-installing different winetrick DLLs until it got resolved. The specific DLL that solves the crash and the other 2 bugs is comctl32. However, after adding that DLL you cannot export HTML, CSV files from the calendar anymore or do a backup/restore. This seems to be due to a known bug related to the file open dialog; https://bugs.winehq.org/show_bug.cgi?id=43188
Should I make a new bug-report that's more specific to the current problems with UK's Kalender & comctl32? The title of this bug report is no longer correct from what I can tell.
https://bugs.winehq.org/show_bug.cgi?id=44167
--- Comment #12 from wineuser101@mailbox.org --- Created attachment 74356 --> https://bugs.winehq.org/attachment.cgi?id=74356 Backtrace crash
https://bugs.winehq.org/show_bug.cgi?id=44167
--- Comment #13 from wineuser101@mailbox.org --- Created attachment 74357 --> https://bugs.winehq.org/attachment.cgi?id=74357 Screenshot add event category
https://bugs.winehq.org/show_bug.cgi?id=44167
temp82@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |temp82@luukku.com
--- Comment #14 from temp82@luukku.com --- one bug report shouldn't be used to report all issues some program has. also bug reports should be made against up to date wine versions. preferably wine-devel so fixes would land into stable version eventually.
https://bugs.winehq.org/show_bug.cgi?id=44167
--- Comment #15 from wineuser101 wineuser101@mailbox.org --- (In reply to temp82 from comment #14)
Thank you for your reply. I have a couple of questions:
one bug report shouldn't be used to report all issues some program has.
OK, should I open 3 different bug reports for the 3 different bugs (all related to the comctl32 DLL)? Or maybe 1 for the crash and 2 for the GUI related bugs?
bug reports should be made against up to date wine versions. preferably wine-devel so fixes would land into stable version eventually.
Isn't 8.6 the latest development release? The Wine-devel package doesn't seem to contain anything that would impact the bug report:
"wine-devel contains applications, scripts, header files, and libraries for building applications that use wine and/or winelib." https://superuser.com/questions/293797/difference-between-wine-and-wine-deve...
https://bugs.winehq.org/show_bug.cgi?id=44167
--- Comment #16 from Austin English austinenglish@gmail.com --- (In reply to wineuser101 from comment #15)
OK, should I open 3 different bug reports for the 3 different bugs (all related to the comctl32 DLL)? Or maybe 1 for the crash and 2 for the GUI related bugs?
Ideally there would be 3 bugs, one for the crash, and 1 each for the individual GUI issues.
FYI, the problems related to _native_ comctl32 (exporting HTML/CSV, and backup/restore) should _not_ be reported to Wine (in general, we can't do much for bugs in native DLLs).
bug reports should be made against up to date wine versions. preferably wine-devel so fixes would land into stable version eventually.
Isn't 8.6 the latest development release? The Wine-devel package doesn't seem to contain anything that would impact the bug report:
Yes, it currently is. That version is perfectly fine to report bugs against.
https://bugs.winehq.org/show_bug.cgi?id=44167
--- Comment #17 from wineuser101 wineuser101@mailbox.org --- (In reply to Austin English from comment #16)
Thank you for your reply. I've now opened 3 new bug report regarding these issues:
https://bugs.winehq.org/show_bug.cgi?id=54861 https://bugs.winehq.org/show_bug.cgi?id=54862 https://bugs.winehq.org/show_bug.cgi?id=54863
-
wine-bugs＠winehq.org -
WineHQ Bugzilla