View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002431 | GeoSetter | User Interface | public | 2023-01-12 12:38 | 2023-04-12 10:40 |
| Reporter | ThunderBoy | Assigned To | Friedemann | ||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Summary | 0002431: 4.0.15 - The selected image (file) cannot be deleted. | ||||
| Description | When selecting an image (file), deletion does not work. I think it still worked in version 4.04. In newer ones it doesn't. It doesn't work with the Del key, and there is no delete available in the right-click image menu either. I looked, but even in the menu there is no option to delete the file. | ||||
| Steps To Reproduce | Delete key | ||||
| Tags | No tags attached. | ||||
|
|
I confirm the reported behavoiur. In previous BETA version a "delete" button and the "Delete" key were both available, but in most cases deleting image files resulted in Geosetter crashing. Maybe this is why the delete feature was removed, but of course this is not a "solution"... |
|
|
WIth V4.0.43 some action has reappeared with the "delete" button (although no explicite delete command is available). As a matter of fact, selecting inages and pressing "delete" seems to telete the images BUT most of the times results in GS freezeing and crashing a few second later |
|
|
As of today (V4.0.47) the issue is stil present: pressind "DEL" for a selected image nearly always results in GS crashing. As a hint, I can say that crash happens AFTED the actuale deletion of the image (after restarting, the image is indeed erased) |
|
|
@zava I just tried in 4.0.47 under Windows 10 22H2 and deleting (i.e. moving to trash) with the Delete key did work for me. Something must be different in you environment - version of Windows, for example ...? Did you send a bug report? But you are right, there is not delete option - neither in the menu nor context menu. |
|
|
@zava I have no problem with this on Windows 7. Have you tried it on a completely clean install? Attach here or send a bug report to the boss. I haven't tried it on any new version since. In version 4.0.47 it really works with the Del key, just like in older versions. There is no mention in the change log that anything was done about this. See if it was related to another problem that has been fixed in the meantime. I accidentally found out that this same problem was already solved a long time ago: 0000720 We'll see if it goes in the new version. PS: I also noticed that the Help menu in the program is missing a link to this forum. I'm not going to create a new thread for it. :) |
|
|
Quite puzzled... There are two major causes of systematic GS crashing, both of which happpen virtually always: - pressing DEL on an image (image IS deleted but GS crashes). Virtually 100% of times. This did NOT happen pre-V4 - selecting a new working folder: this also crashes GS 90% of the times. This happened also pre-V4 |
|
|
strange! For me all works fine! |
|
|
The "delete" and "selecting a new working folder" also works on my PC: Windows 11 Pro Version 22H2 |
|
|
Del key also works in the latest version (4.0.49) without error messages. |
|
|
I have now installed 4.0.49: the del key erased four pictures without a crash! This never happened before. But upon deleting the fifth image, GS again crashed... There is surely some difference in my environment, but I have no idea what I could check... I guess I'll have to stick to my old habit of renaming the files to be deleted to "xxx-filename" and then deleting them with some external tool... If anybody has a clue about any check or test that may prove useful to a diagnosys, I will try... |
|
|
@zava You just write here over and over again that it keeps crashing, but you don't attach any bug report. I'm sure you're not even sending it to the supervisor to finally have a look at it. |
|
|
Thank you for your suggestion; in fact I was assuming *this* was a bug report... Since apparently it is not, can you pls suggest how a proper bug report is sent and what additional info can be retrieved? GS Help simply mentions registering and sending to the Mantis system... Thank you |
|
|
@zava The error message is obtained directly when the program crashes. The program itself requires it when it crashes! Here it just says that something is wrong and attaches this message or sends it to the manager by email. You can get such a message directly from the program e.g. here: 0002505 |
|
|
Thank you thunderboy, I was aware of that exception window and I would have sent it if one had been available. But when GS crashes as I reported, no such error message is issued, it simply disappears and gets closed, providing no (readily available) crash information. |
|
|
@Zava are you sure, GeoSetter really ends? Since quite a long time, I often run into situations that the GeoSetter window is hidden by other windows. To find the window, I use the alt-Tab key combination. If the window really did disappear, I would suggest use the Windows task manager and see if the GeoSetter task still shows up there. Another option is to check Windows event log (see https://answers.microsoft.com/en-us/windows/forum/all/how-to-open-event-log-viewer-windows-10/bb4fb2ac-5aa0-4bbf-afc6-45642b92a6bc ) Maybe @heiko or @Friedemann have other hints for problem determination, if the program really ends silently. |
|
|
Thank you WilfriedB, Step by step: - GS is running - GS is listed in the process list in task manager - I hit DEL - the selected image IS deleted - GS remains apparently frozen for a few seconds. "Not responding" appears in the top edge if GS's window - GS is closed - GS process is no longer in the process list in task manager - Event manager lists TWO ERRORs attributed to GS generating an exception The standard GS exception/error window never appeared. Event maanger lists as follows (in italian but I believe it's understandable): Nome dell'applicazione che ha generato l'errore: GeoSetter.exe, versione: 4.0.49.2233, timestamp: 0x2a425e19 Nome del modulo che ha generato l'errore: unknown, versione: 0.0.0.0, timestamp: 0x00000000 Codice eccezione: 0xc000041d Offset errore 0x00000012 ID processo che ha generato l'errore: 0x4a88 Ora di avvio dell'applicazione che ha generato l'errore: 0x01d96b08faf23113 Percorso dell'applicazione che ha generato l'errore: C:\Program Files (x86)\GeoSetter beta\GeoSetter.exe Percorso del modulo che ha generato l'errore: unknown ID segnalazione: c37b790d-f5b7-4fcb-9a64-35bf800efaf1 Nome completo pacchetto che ha generato l'errore: ID applicazione relativo al pacchetto che ha generato l'errore: and a nother exception recorded a few seconds earlier: Nome dell'applicazione che ha generato l'errore: GeoSetter.exe, versione: 4.0.49.2233, timestamp: 0x2a425e19 Nome del modulo che ha generato l'errore: unknown, versione: 0.0.0.0, timestamp: 0x00000000 Codice eccezione: 0xc000041d Offset errore 0x00000012 ID processo che ha generato l'errore: 0x4a88 Ora di avvio dell'applicazione che ha generato l'errore: 0x01d96b08faf23113 Percorso dell'applicazione che ha generato l'errore: C:\Program Files (x86)\GeoSetter beta\GeoSetter.exe Percorso del modulo che ha generato l'errore: unknown ID segnalazione: c37b790d-f5b7-4fcb-9a64-35bf800efaf1 Nome completo pacchetto che ha generato l'errore: ID applicazione relativo al pacchetto che ha generato l'errore: The two errors have a different exception code. I hope this may provide some useful info. |
|
|
@zava a great problem report! Now, we can hope this helps @Friedemann to pinpoint the cause and finds some time to investigate. Seems to me, the most important detail is "Codice eccezione: 0xc000041d", which means "STATUS_FATAL_USER_CALLBACK_EXCEPTION" |
|
|
"STATUS_FATAL_USER_CALLBACK_EXCEPTION" Sounds terrible! ;) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-01-12 12:38 | ThunderBoy | New Issue | |
| 2023-01-14 19:17 | zava | Note Added: 0004380 | |
| 2023-02-09 16:00 | zava | Note Added: 0004561 | |
| 2023-02-13 22:17 | Friedemann | Assigned To | => Friedemann |
| 2023-02-13 22:17 | Friedemann | Status | new => assigned |
| 2023-02-15 15:29 | zava | Note Added: 0004613 | |
| 2023-02-15 16:26 | WilfriedB | Note Added: 0004614 | |
| 2023-02-15 20:39 | ThunderBoy | Note Added: 0004616 | |
| 2023-02-19 22:21 | zava | Note Added: 0004628 | |
| 2023-02-19 23:05 | heiko | Note Added: 0004630 | |
| 2023-02-19 23:24 | xyzzy | Note Added: 0004632 | |
| 2023-02-27 08:17 | ThunderBoy | Note Added: 0004690 | |
| 2023-03-01 10:45 | zava | Note Added: 0004698 | |
| 2023-03-01 10:55 | ThunderBoy | Note Added: 0004699 | |
| 2023-04-04 19:42 | zava | Note Added: 0004716 | |
| 2023-04-04 20:07 | ThunderBoy | Note Added: 0004717 | |
| 2023-04-06 12:25 | zava | Note Added: 0004719 | |
| 2023-04-06 19:15 | WilfriedB | Note Added: 0004720 | |
| 2023-04-09 23:32 | zava | Note Added: 0004725 | |
| 2023-04-10 08:51 | WilfriedB | Note Added: 0004726 | |
| 2023-04-12 10:40 | zava | Note Added: 0004741 |
