primordic/IssueDupesLite huggingface dataset:
Repository: jmathai/elodie

Issue #107: Allow destination file name structure to be customized
Created: 2016-04-14T01:11:13Z
Hey,
I see this issue has already been discussed for folder naming ( #5 ), but I'd like to control the structure of [image] file naming
More specifically, retaining the filename during a "first pass" is useful as an ID, but I'd like the ability to remove the filename with a second pass; since I now have a unique timestamp:

Is this possible?
FYI I played with http://www.sno.phy.queensu.ca/~phil/exiftool/ a while back and decide the ideal naming structure for me would involve the following:
CreateDate: 2015:03:02 07:54:33 or SubSecCreateDate: 2015:03:02 07:54:33.33
DateTimeOriginal: 2015:03:02 07:54:33 or SubSecDateTimeOriginal: 2015:03:02 07:54:33.33
ImageSize: 3872x2592
Make: NIKON CORPORATION
Model: NIKON D200

Hope to hear back
Kind thanks

Duplicate issue #110: omit renaming if photo name is already in yyyy-mm-dd mm-ss format
Created: 2016-04-18T15:01:14Z
I've set my camera to provide yyyy-mm-dd mm-ss.jpg/raw file names (which probably wasn't the best idea), if I proceed them with Elodie I end up with yyyy-mm-dd_mm-ss-yyyy-mm-dd mm-ss.jpg which is a bit confusing.

Closing comment (2016-12-31T06:35:17Z): Marking this as a duplicate of #107. We should have this option included in a couple weeks.
Repository: jonaswinkler/paperless-ng

Issue #404: [BUG] Mail consumption fails for mails with defects / Mails don't get picked up
Created: 2021-01-21T18:40:36Z
See #379
When the python mail parsing backend reports errors on mails, the library imap-tools silently ignores these mails. Either provide error messages, or investigate if we can allow mail processing despite certain errors.
The error in the related issue is email.errors.InvalidMultipartContentTransferEncodingDefect.

Duplicate issue #650: [BUG] Some mails are not recognized by the mail scanner
Created: 2021-02-27T11:55:19Z
I have some mails that don't show up when the mail checker task runs:
The log output is the following:
[2021-02-27 12:41:47,652] [DEBUG] [paperless_mail] Account paperless@giffhorn-net.de: Processing 1 rule(s)
[2021-02-27 12:41:47,664] [DEBUG] [paperless_mail] Rule paperless@giffhorn-net.de.Paperless-Mail: Selecting folder INBOX
[2021-02-27 12:41:47,701] [DEBUG] [paperless_mail] Rule paperless@giffhorn-net.de.Paperless-Mail: Searching folder with criteria (SINCE 4-Jun-2018)
[2021-02-27 12:41:50,574] [DEBUG] [paperless_mail] Rule paperless@giffhorn-net.de.Paperless-Mail: Processed 0 matching mail(s)
[2021-02-27 12:41:50,585] [DEBUG] [paperless_mail] Rule paperless@giffhorn-net.de.Paperless-Mail: Running mail actions on 0 mails
However there are clearly Mails with attachments in this INBOX which match the criteria:

The attachment/file itself is working fine. If I use the file and send it in another mail to the Mail-Account, it is picked up properly. So it seems that the original attachment/mail format could be the cause for this.
I could export and send sample mails, however I don't want to upload them here to be publicly available.

Closing comment (2021-03-14T14:55:23Z): Probably a duplicate of #404.
Repository: jonaswinkler/paperless-ng

Issue #343: Export feature
Created: 2021-01-14T15:56:30Z
First of all I must say I absolutely love this version of Paperless. I was sad when development on the old version ceased, and I was soo extremely happy when I found this.
It is NOT overly complicated. It is easy to manage. I understand it. PERFECT!
The reason I am writing is however a small feature request.
The ./manage.py document_exporter will not export when files is present in the folder.
I suggest a -f  argument, where it will either overwrite the backup, but even better, only update changed documents.

Duplicate issue #344: export function
Created: 2021-01-14T15:56:58Z
First of all I must say I absolutely love this version of Paperless. I was sad when development on the old version ceased, and I was soo extremely happy when I found this.
It is NOT overly complicated. It is easy to manage. I understand it. PERFECT!
The reason I am writing is however a small feature request.
The ./manage.py document_exporter will not export when files is present in the folder.
I suggest a -f  argument, where it will either overwrite the backup, but even better, only update changed documents.

Closing comment (2021-01-14T16:01:35Z): Closing as duplicate of #343
Repository: jonaswinkler/paperless-ng

Issue #668: [BUG] Putting a regular expression (.*anything.*) in correspondent but selecting text stops processing documents
Created: 2021-02-28T21:15:06Z
When a regular expression like (.anything.) into the correspondent recognition field but forgetting to set type to regular processing causes stoping of document processing with error log:
Error messagt:
[DEBUG] [paperless.consumer] Saving record to database
[ERROR] [paperless.consumer] The following error occured while consuming XXXX.pdf: missing ), unterminated subpattern at position 2
To Reproduce
Steps to reproduce the behavior:

Go to administration of correspondents
create a new one with a regular expression  (.anything.) as identifier and set type to Any Text (in german: Irgendein Wort)
Click save
import an document
see error:
[DEBUG] [paperless.consumer] Saving record to database
[ERROR] [paperless.consumer] The following error occured while consuming XXXX.pdf: missing ), unterminated subpattern at position 2

Expected behavior
At least a better information where the error comes from would be nice

Duplicate issue #605: [BUG] Consumer crashes when using brackets for matching.
Created: 2021-02-23T09:13:28Z
Describe the bug
PDF upload failed
To Reproduce

Go to self hosted paperless-ng's site
try to upload the PDF via drag and drop

Expected behavior

PDF uploaded

Relevant information
Error Message:

Version: Paperless-ng 1.1.4
I have "data" and "media" stored on a mount on a second drive

Closing comment (2021-02-28T21:32:43Z): Duplicate of #668
Repository: jonaswinkler/paperless-ng

Issue #67: CRITICAL Document has gone
Created: 2020-11-29T12:29:59Z
Hey, after throwing in a couple of items into the consumption directory, I get this error on quite a few (but not all) files:
11/29/20, 8:47 AM INFO Document 20201129084623: 1195_201101094445_001 consumption finished

11/29/20, 8:47 AM CRITICAL Document 20201129084623: 1195_201101094445_001: File /usr/src/paperless/src/../media/documents/originals/none/none/2020-11-29-0846237063410100 1195_201101094445_001 - Typ none-0000432.pdf has gone.

11/29/20, 8:47 AM INFO Unable to detect date for document

11/29/20, 8:47 AM INFO Consuming 1195_201101094445_001.pdf

But apparently it is there (again):
$ ls "/usr/src/paperless/src/../media/documents/originals/none/none/2020-11-29-0846237063410100 1195_201101094445_001 - Typ none-0000432.pdf"`

-rw-r--r-- 1 paperless paperless 160052 Nov 29 08:47 '/usr/src/paperless/src/../media/documents/originals/none/none/2020-11-29-0846237063410100 1195_201101094445_001 - Typ none-0000432.pdf'

And at least this file also made it into paperless, i.e. I can see it in the UI.
Consumption dir is empty. I'll have to check if all files really made it - still that critical warning seems unwanted to me :-)
Anything else, I can provide?

Duplicate issue #68: CRITICAL Document has gone
Created: 2020-11-29T12:34:49Z
Hey, after throwing in a couple of items into the consumption directory, I get this error on quite a few (but not all) files:
11/29/20, 8:47 AM INFO Document 20201129084623: 1195_201101094445_001 consumption finished

11/29/20, 8:47 AM CRITICAL Document 20201129084623: 1195_201101094445_001: File /usr/src/paperless/src/../media/documents/originals/none/none/2020-11-29-0846237063410100 1195_201101094445_001 - Typ none-0000432.pdf has gone.

11/29/20, 8:47 AM INFO Unable to detect date for document

11/29/20, 8:47 AM INFO Consuming 1195_201101094445_001.pdf

But apparently it is there (again):
$ ls "/usr/src/paperless/src/../media/documents/originals/none/none/2020-11-29-0846237063410100 1195_201101094445_001 - Typ none-0000432.pdf"`

-rw-r--r-- 1 paperless paperless 160052 Nov 29 08:47 '/usr/src/paperless/src/../media/documents/originals/none/none/2020-11-29-0846237063410100 1195_201101094445_001 - Typ none-0000432.pdf'

And at least this file also made it into paperless, i.e. I can see it in the UI.
Consumption dir is empty. I'll have to check if all files really made it - still that critical warning seems unwanted to me :-)
Anything else, I can provide?

Closing comment (2020-11-29T13:05:55Z): duplicate : #67
Repository: jonaswinkler/paperless-ng

Issue #195: Missing search results
Created: 2020-12-27T14:32:58Z
Hi,
i am currently using the version 0.9.9 docker-compose version.
I added some documents and they were correctly processed. I can see the content of the documents.
But if i search with the top bar the results are not appearing:

But the auto completion is working:

The container log doesn't show any hint:
webserver_1  | WARNING 2020-12-27 14:30:16,799 log Bad Request: /api/search/
webserver_1  | 172.23.0.3 - - [27/Dec/2020:14:30:19 +0000] "GET /api/search/autocomplete/?term=leben HTTP/1.1" 200 164 "https://pl.xxx.de/search?query=lebenslauf%20" "Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0"
webserver_1  | 172.23.0.3 - - [27/Dec/2020:14:30:20 +0000] "GET /api/search/autocomplete/?term=lebens HTTP/1.1" 200 164 "https://pl.xxx.de/search?query=lebenslauf%20" "Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0"
webserver_1  | 172.23.0.3 - - [27/Dec/2020:14:30:20 +0000] "GET /api/search/autocomplete/?term=lebensl HTTP/1.1" 200 14 "https://pl.xxx.de/search?query=lebenslauf%20" "Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0"
webserver_1  | 172.23.0.3 - - [27/Dec/2020:14:30:20 +0000] "GET /api/search/autocomplete/?term=lebensla HTTP/1.1" 200 14 "https://pl.xxx.de/search?query=lebenslauf%20" "Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0"
webserver_1  | 172.23.0.3 - - [27/Dec/2020:14:30:21 +0000] "GET /api/search/autocomplete/?term=lebenslau HTTP/1.1" 200 14 "https://pl.xxx.de/search?query=lebenslauf%20" "Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0"
webserver_1  | 172.23.0.3 - - [27/Dec/2020:14:30:22 +0000] "GET /api/search/autocomplete/?term=lebenslauf HTTP/1.1" 200 14 "https://pl.xxx.de/search?query=lebenslauf%20" "Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0"
webserver_1  | 127.0.0.1 - - [27/Dec/2020:14:30:31 +0000] "GET / HTTP/1.1" 302 0 "-" "curl/7.64.0"

Duplicate issue #328: Bug: Bad Request: /api/search/
Created: 2021-01-11T22:41:29Z
Certain search terms are producing a bad request even though I know that the search term is in many of the documents.
I get this message when I search for certain words:
Invalid search query: Document matching query does not exist.

When I look at the logs
I see a bad request:
Bad Request: /api/search/

I haven't found a pattern yet.
My paperless-ng install has 333 documents.

Closing comment (2021-01-11T22:48:07Z): Duplicate of #195
Repository: jonaswinkler/paperless-ng

Issue #514: [BUG] Counts are not updates in document overview
Created: 2021-02-08T10:43:47Z
When I update some documents in bulk (eg. adding/removing tags, correspondents, ...) the counts in their respective filters (post-apply) are not updated. After a hard refresh, this is updated. Note that this is mostly a QoL issue, and thus small bug. I'm reporting it in case it's easy to fix.
To Reproduce

Go to the "Documents" page
Select a number of documents
Assign some tag to those documents
Refresh and check the number of documents with this tag in the filter-dropdown
(Optional) Filter documents with that tag
Select some documents in the filtered view / with that tag
Bulk-remove the tag
Wait for the list to update
Click on the tag-filter dropdown and observe the same number as in 4. The number in the description under the textbox is correct
Refresh: the number is now correct in both locations

Expected behavior
After performing any bulk-operations, the counters should be updated too.
Screenshots

Relevant information

Version: 1.1.0
Installation method: docker

Duplicate issue #898: [BUG] Numbers in document overview on tag list and correspondents will not be updated after changing
Created: 2021-04-12T11:00:17Z
Describe the bug
I noticed the counts of the tags in the search fields will not be updated while tagging the documents.
To Reproduce
Steps to reproduce the behavior:

Go to the Documents list having a set of documents lets say with Tag "New". The counter next to the Tag is 5
Update the tags and remove the "New" tag from the 2 documents
The Tag counter still is at 5 till I reload the page, but it should be 3 now.

Expected behaviour

The Tag counter still is at 5 till I reload the page, but it should be 3 now.

Screenshots
N/A
Relevant information

Host OS of the machine running paperless: Ubuntu 20.04 on Browser side, Ubuntu 18.04 on Host side
Browser: Firefox
Version 1.4.0
Installation method: docker

Closing comment (2021-04-12T12:53:48Z): Duplicate of #514
Repository: jonaswinkler/paperless-ng

Issue #1233: [BUG] [SECURITY] Password of emailaccount is plaintext and visible
Created: 2021-08-16T10:38:04Z
Describe the bug
The password of the account to access the mailbox is visible in plaintext in the webinterface (and therefore also in the database)
To Reproduce
Steps to reproduce the behavior:

Go to '/admin/paperless_mail/mailaccount/1/change/'
Scroll down to 'Password'
See error

Expected behavior
A hidden/obscured representation (all asterisks or something)
And also stored as a hash in the database.
Screenshots
I do not think so ;)
Webserver logs
Irrelevant

Relevant information

Host OS of the machine running paperless: [e.g. Archlinux / Ubuntu 20.04]
Browser [e.g. chrome, safari]
Version [e.g. 1.0.0]
Installation method: [docker / bare metal]
Any configuration changes you made in docker-compose.yml, docker-compose.env or paperless.conf.

Duplicate issue #1483: [BUG] Email Account Password is not Obscured
Created: 2021-12-12T20:03:25Z
Describe the bug
In the admin view when adding an email account, the password will always be displayed as clear text. Also when returning to that tab, the email account password is still not obscured (e.g. by dots).
To Reproduce

Add Email Account
Enter Password
See that Password is not obscured

Expected behavior
Obscure password upon entry and do not ever show it in clear text.
Screenshots
not applicable
Webserver logs
irrelevant
Relevant information
irrelevant

Closing comment (2021-12-13T08:02:52Z): Duplicate of #1233
Repository: joncampbell123/dosbox-x

Issue #2109: [Feature Request] Port of the Rewind and Savestate/Serialization feature from Libretro's DOSBox Pure?
Created: 2020-12-21T17:46:18Z
I've noticed that Retroarch/Libretro's version of DOSBox, DOSBox Pure, has implemented its own savestate feature as well as rewind. The savestate feature seems to be stable. (https://twitter.com/b_schelling/status/1338934696374222849?s=21, https://twitter.com/libretro/status/1341086625678372865?s=21, https://www.youtube.com/watch?v=rHkIz4-SewI, https://github.com/schellingb/dosbox-pure) Could this be imported into DOSBox-X?
EDIT: Turns out it's in Libretro, not dosbox staging.

Duplicate issue #3064: Rewind feature in DOSBox-X
Created: 2021-11-10T19:28:34Z
Code of Conduct & Contributing Guidelines

 I agree to follow the code of conduct and the contributing guidelines.

Have you checked that no other similar feature request(s) already exists?

 I have searched and didn't find any similar issues.

Is your feature request related to a problem? Please describe.
No response
What you want
Is there any possibility that a future DOSBox-X may get a rewind feature? That would be nice for very difficult games, I think.
Describe alternatives you've considered
No response
Additional context
No response

Closing comment (2022-01-01T08:01:52Z): possible duplicate: #2109
Repository: joncampbell123/dosbox-x

Issue #2726: SB PCI on Windows 98
Created: 2021-07-27T01:00:20Z
When I installed Windows 98 on DOSBOX-X, I noticed the music in some of the games sounded different compared to when they were played on another machine with Win 98 installed via VM-Ware.  It appears that the latter uses SB PCI, is there a way to install that on DOSBOX-X?

Duplicate issue #4851: Ensoniq AudioPCI (ES1371) emulation.
Created: 2024-02-28T03:27:44Z
Is your feature request related to a problem? Please describe.
Attempts to install via drivers has been unsuccessful.
What you want
Emulation of the Ensoniq AudioPCI (ES1371) soundcard in DOSBox X.
Describe alternatives you've considered
Installed it on a Windows 98 virtual machine in 86box successfully.
Additional information
No response
Have you checked that no similar feature request(s) exist?

 I have searched and didn't find any similar feature request.

Code of Conduct & Contributing Guidelines

 I agree to follow the code of conduct and the contributing guidelines.

Closing comment (2024-09-02T10:34:25Z): Duplicate?

#2726

Related:

#4551
Repository: joncampbell123/dosbox-x

Issue #893: Libretro core
Created: 2018-10-07T00:51:13Z
I noticed there's a RetroArch core for the original DOSBox, but not DOSBox-X.
I found a request on reddit but nothing on the issue tracker.
Much like the creator of the reddit post, I would also like to see DOSBox-X core as it's better than the original DOSBox.

Duplicate issue #2958: compile dosbox-x as retroarch core?
Created: 2021-10-02T10:21:30Z
Is it possible to compile dosbox-x as a retroarch core?
If so, how do I go about doing that?

Closing comment (2021-10-03T08:34:27Z): can libretro support be implemented? I'd like to use dosbox-x with retroarch.

Idk
By the way this issue is a duplicate of #893 you can take a look to see if it answers your question
Repository: joncampbell123/dosbox-x

Issue #4342: Migrating configuration after each release is a pain.
Created: 2023-06-17T02:44:06Z
Describe the bug
-userconf picks up ~/.config/dosbox-x/dosbox-x-version.conf instead of ~/.config/dosbox-x/dosbox-x.conf.
After each release, I have to rename the configuration file. This is painful. I want a configuration file that persists over versions.
Steps to reproduce the behaviour

Upgrade dosbox-x
-userconf picks up a different config file after each upgrade.

Have you checked that no similar bug report(s) exist?

 I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

 I agree to follow the code of conduct and the contributing guidelines.

Duplicate issue #4609: Update .conf file
Created: 2023-11-15T17:47:18Z
Is your feature request related to a problem? Please describe.
I have to manually change the settings in the .conf file when a new version of Doxbox-x is released.
What you want
I use the vsbuild win64 version. It would be nice to have a way of updating the .conf file to the current version when we update DosBox-x.
Describe alternatives you've considered
No response
Additional information
No response
Have you checked that no similar feature request(s) exist?

 I have searched and didn't find any similar feature request.

Code of Conduct & Contributing Guidelines

 I agree to follow the code of conduct and the contributing guidelines.

Closing comment (2023-11-16T06:01:17Z): Duplicate of?

#4342
#4057

Will config -wc pickup old .conf user customizations and update all other settings in the file to match latest version capabilities?
If correct - maybe good to mention it in INSTALL.md
Repository: joncampbell123/dosbox-x

Issue #905: PC-98: bit7 of 0000:053Ch should be 1
Created: 2018-10-30T12:48:11Z
bit7 of 0000:053Ch shows a CRT type. 0 for 15kHz, 1 for 24kHz, so should be 1. 大貧民 (Daihimmin) game checks this field to manage game and music speed based on horizontal blank signal but the bit is 0 so the game runs too fast. The game can be downloaded at https://www.vector.co.jp/soft/dos/game/se001269.html

Duplicate issue #906: PC-98: bit 6 and bit 3 of 0000:054Ch should be 1
Created: 2018-10-30T13:31:51Z
bit 6 of 0000:054Ch is same as #905
bit 3 shows number of user-defined, modifiable fonts. The bit was 0 for old models that only had small RAM for 63 characters. Gajet, a pattern editor can be downloaded at https://www.vector.co.jp/soft/dos/writing/se001839.html, checks the bit and shows an error that the application does not run on PC-9801/E/F/M:

According to the DOSBox-X source file vga_pc98_cg.cpp, modifiable code range is 0x56xx and 0x57xx, so the bit 3 should be 1.

Closing comment (2018-10-30T23:59:39Z): Same as #905, that bit is documented (in what I have) to mean a high resolution CRT, not a 15khz rate.
Also according to documentation I have, "high resolution" is said to be much higher than the standard 640x400 video mode used by PC-98, so as far as I know, none of the video modes emulated in DOSBox-X are "high resolution".

No, it is not correct. It is mistakable.
https://www.webtech.co.jp/company/doc/undocumented_mem/memsys.txt
bit6=0, 標準ディスプレイ can be translated as a standard display.
bit6=1, 専用高解像度ディスプレイ, can be translated as a dedicated high-resolution display.
高解像度 means high-resolution, and ハイレゾ also means high-resolution. But ハイレゾ is only used for the mode higher than 640x400. The 400 line mode is called as 高解像度 because of a historically reason: a display used for PC-8001, the ancestor of PC-98, is called as 標準ディスプレイ which only has 200 lines. SW1-1 selects which type of display is used. PC-8800 series models also support both type of displays. When 高解像度 display was released, ハイレゾ mode was not released.
https://ja.wikipedia.org/wiki/PC-9800%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA#cite_note-75
This note also describes the mistakable terms. It says that the ハイレゾ mode resolution is 超高解像度, super high resolution.
Repository: joncampbell123/dosbox-x

Issue #3974: Joystick stopped working in version 2022.12.26 ( non SDL2 )
Created: 2023-01-28T13:53:45Z
Describe the bug
My joystick ( Gladiator NXT ) is no longer working in version 2022.12.26 ( non SDL2 ) for some reason.
It is working in the previous release version 2022.09.0. ( non SDL2 ).
It still seems to work in the SDL2 build though !
Steps to reproduce the behaviour

Attach a joystick
Run DosBox-X non SDL2 version
Try Using Joystick ( for example in a DOS joystick tester program )

Expected behavior
Joystick should work as before
What operating system(s) this bug have occurred on?
Windows 7
What version(s) of DOSBox-X have this bug?
2022.12.26 ( no SDL2 )
Used configuration
No response
Output log
No response
Additional information
Still works in the SDL2 build
Have you checked that no similar bug report(s) exist?

 I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

 I agree to follow the code of conduct and the contributing guidelines.

Duplicate issue #5342: Logitech Extreme 3D Pro (DirectInput) not detected
Created: 2024-12-25T11:34:26Z
Describe the bug
Self explanatory.
Edit: DualShock 4 and DualSense controllers are also not detected
Mapper Editor promptly shows [missing joystick] when selecting a joystick key.
Steps to reproduce the behaviour

Plug in Logitech Extreme 3D Pro
Open DOSBox-X

Expected behavior
Joystick should be detected and usable
What operating system(s) this bug have occurred on?
Windows 11 24H2
What version(s) of DOSBox-X have this bug?
v2024.12.04, Visual Studio SDL1 64-bit
Used configuration
No response
Output log
No response
Additional information
dosbox-x.conf.txt
edit 2: DirectInput controllers work after installing the SDL2 version as according to #3974. What is the difference between SDL1 and 2 anyways and why is SDL1 default?
Have you checked that no similar bug report(s) exist?

 I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

 I agree to follow the code of conduct and the contributing guidelines.

Closing comment (2024-12-25T11:53:22Z): Duplicate of #3974.
Also, some information can be found here as you may encounter similar problems with other games using joysticks as well.
Repository: joncampbell123/dosbox-x

Issue #3914: v2022.12.26 release doesn't come with Windows installers
Created: 2022-12-31T08:43:16Z
Describe the bug
Recent DOSBox-X releases usually come with Windows installer programs, however there are none released for v2022.12.26.
Steps to reproduce the behaviour

Go to the release's page
Notice the absence of dosbox-x-winXX-2022.12.26-setup.exe

Expected behavior
No response
What operating system(s) this bug have occurred on?
Windows
What version(s) of DOSBox-X have this bug?
v2022.12.26
Used configuration
No response
Output log
No response
Additional information
I would also like to mention that among the released binaries, there are two Windows ARM builds and two Windows ARM64 builds. Were their inclusion accidental?
Have you checked that no similar bug report(s) exist?

 I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

 I agree to follow the code of conduct and the contributing guidelines.

Duplicate issue #3918: https://dosbox-x.com/  issue
Created: 2023-01-05T17:42:19Z
Attempted download from home page link "https://dosbox-x.com/" goes to github "https://github.com/joncampbell123/dosbox-x/releases/download/dosbox-x-v2022.12.26/dosbox-x-win64-2022.12.26-setup.exe" with return of 404.
Pictures included to show issue

Closing comment (2023-01-06T06:51:20Z): Related to #3914
Repository: joncampbell123/dosbox-x

Issue #5480: Blank screen when `output=ttf` on PC-98 mode
Created: 2025-02-09T13:58:54Z
Describe the bug
The screen is totally blank when output=ttf on PC-98 mode.
It is actually not freezing, but it is just blank.

Steps to reproduce the behaviour
Launch DOSBox-X by the following command.
dosbox-x -defaultconf -set output=ttf -set machine=pc98
Expected behavior
TTF mode works for text mode in PC-98 mode.
What operating system(s) this bug have occurred on?
Windows 10
What version(s) of DOSBox-X have this bug?
Since 2025.01.01 release upto latest commit 5d509c8
Used configuration
`dosbox-x -defaultconf -set output=ttf -set machine=pc98`
Output log


Additional information
The screen is blank, but you can enjoy the emulator by switching to other output options.

Have you checked that no similar bug report(s) exist?

 I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

 I agree to follow the code of conduct and the contributing guidelines.

Duplicate issue #5581: machine = PC-98 results in black screen
Created: 2025-03-23T12:32:39Z
Describe the bug
I have created a new config file and changed the machine option to:
machine                   = pc98

However, when launching DOSBox-X, I am met with a black screen that says DOSBox-X 2025.02.01: COMMAND - 23880 cycles/ms. After seeking advice, saw the suggestion to change the CPU Type from Auto to 486, and I have set it to this CPU Type, but it still results in a black screen.

Steps to reproduce the behaviour

Change machine from svga_s3 to pc98 inside dosbox-x.conf
Open DOSBox-X
Black Screen

Expected behavior
Expected would be to see something different than a pure black screen.
What operating system(s) this bug have occurred on?
Windows 10 Pro 22H2
What version(s) of DOSBox-X have this bug?
DOSBox-X ver.2025.02.01 (VS SDL2 64-bit)
Used configuration

Output log


Additional information
Config: https://pastebin.com/sKtU7Mxb
Have you checked that no similar bug report(s) exist?

 I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

 I agree to follow the code of conduct and the contributing guidelines.

Closing comment (2025-03-23T14:08:51Z): Duplicate of #5480
Repository: jookies/jasmin

Issue #1224: https://setup.jasminsms.com/deb timing out
Created: 2024-08-12T02:16:29Z
Hey Team
The Jasmin setup link seems to be timing out.
https://setup.jasminsms.com/deb
Cheers

Duplicate issue #1256: I can't install Jasmin since curl to setup.jasminsms.com not working
Created: 2025-04-03T21:22:41Z
Hi Folks,
I tried to install Jazmin using this command but I got a time out, I tried from different servers in different locations and the result is the same,
curl -s https://setup.jasminsms.com/deb | sudo bash
sudo apt-get install jasmin-sms-gateway
Is there any problem to reach https://setup.jasminsms.com/deb  ?
Regards

Closing comment (2025-04-04T08:31:57Z): This is related to #1224 - with a solution
Repository: jookies/jasmin

Issue #477: latest docker image is not starting
Created: 2016-09-28T18:25:49Z
i have pulled the latest image from docker and i noticed that the jasmin is not starting and exposing the ports properly

Duplicate issue #104: bind_ton and src_ton settings on connector not working
Created: 2015-02-26T19:22:06Z
Thank you very much, for the hard work on #97 - now the connectors are updating OK!
Though, in jasmin 0.6b3 - still had to hardcode in /jasmin/protocols/smpp/configs.py to get working connection with another SMPP gateway:
"#        self.bind_addr_ton = kwargs.get('bind_addr_ton', AddrTon.UNKNOWN)"
self.bind_addr_ton = kwargs.get('bind_addr_ton', AddrTon.INTERNATIONAL)
"#        self.source_addr_ton = kwargs.get('source_addr_ton', AddrTon.NATIONAL)"
self.source_addr_ton = kwargs.get('source_addr_ton', AddrTon.INTERNATIONAL)

Closing comment (2016-09-29T12:21:55Z): This is related to #477, investigating issue.
Repository: jookies/jasmin

Issue #1: Add, start, remove, add the same, start: an error is generated
Created: 2013-03-25T19:57:10Z

Duplicate issue #21: Remove and re-add a connector will cause an exception
Created: 2013-10-30T21:20:22Z
When a connector is already created, removing and re-adding will throw the following exception:
2013-10-30 22:17:10+0100 [AmqpProtocol,client] Unhandled Error
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 422, in errback
self._startRunCallbacks(fail)
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 489, in _startRunCallbacks
self._runCallbacks()
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 576, in _runCallbacks
current.result = callback(current.result, _args, *_kw)
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1127, in gotResult
_inlineCallbacks(r, g, deferred)
---  ---
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1069, in _inlineCallbacks
result = result.throwExceptionIntoGenerator(g)
File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
return g.throw(self.type, self.value, self.tb)
File "/home/fourat/workspace/jasmin/managers/clients.py", line 132, in remote_connector_add
yield self.amqpBroker.chan.basic_consume(queue=routingKey_submit_sm, no_ack=False, consumer_tag=consumerTag)
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1069, in _inlineCallbacks
result = result.throwExceptionIntoGenerator(g)
File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
return g.throw(self.type, self.value, self.tb)
File "/home/fourat/workspace/txamqp/protocol.py", line 86, in invoke
raise Closed(self.reason)
txamqp.client.Closed: Method(name=close, id=50) (530, "NOT_ALLOWED - attempt to reuse consumer tag 'SMPPClientFactory.SMGS'", 60, 20) content = None

Closing comment (2013-12-18T20:28:25Z): Duplicate #1
Repository: jookies/jasmin

Issue #464: Tuning messaging performance by storing multi-part tracking in runtime memory
Created: 2016-09-15T10:27:30Z
This will be an option to switch from redis to runtime memory for better performance, the runtime memory must have a way to expire keys to avoid overflows.
This may turn into default behaviour (and redis will turn optional) in future.

Duplicate issue #463: Tuning messaging performance by storing DLR tracking in runtime memory
Created: 2016-09-15T10:26:50Z
This will be an option to switch from redis to runtime memory for better performance, the runtime memory must have a way to expire keys to avoid overflows.
This may turn into default behaviour (and redis will turn optional) in future.

Closing comment (2016-11-25T21:54:23Z): Same as #464, feature dropped.
Repository: jookies/jasmin

Issue #264: Users reporting persisted configuration loss after upgrading Jasmin
Created: 2015-07-20T08:29:17Z

Duplicate issue #277: How to take backup Of Configurations
Created: 2015-07-29T08:57:27Z
Hi
I updated the git and previous Configuration got lost after rebuild of the app. Is there can way we shall retain the previous config Or any Configuration backup .
Thanks in advance

Closing comment (2015-07-29T09:02:15Z): This is related to #264:

If you install/update Jasmin using pip then your /etc/jasmin will be reset everytime you update, pip is for dev. and not for prod.
Install Jasmin using deb or rpm packages, upgrades will never touch your config and persisted data
If you need to stay with pip, then back your /etc/jasmin/jasmin.cfg and /etc/jasmin/store before updating, then restore them after, you'll keep going without config loss
Repository: jookies/jasmin

Issue #210: Recognize msg id when returned in deliver_sm with different encoding (int or hex)
Created: 2015-06-24T14:21:23Z

Duplicate issue #205: No DLR From Jasmin
Created: 2015-06-22T14:14:52Z
Hello community.
I've noticed that while using the scheme ESME - Jasmin- SMSC, Jasmin doesn't give back delivery reports to the ESME. I mean Jasmin got the report from SMSC but he doesn't throw it back to ESME.
Are there any specific settings to make it work?

Closing comment (2015-06-24T14:22:32Z): Issue related to #210
Will close this one
Repository: jookies/jasmin

Issue #543: MO Re-routing 
Created: 2017-03-09T13:53:05Z
Hi Z!,
I have a situation, If we get any specific ERR code from any Uplink, We want to re-route it to another uplink based on Tag filter but the message ID shall remain same.  This situation is imp for our SMPP Users.
SMPP CLIENT 1 ------->>SUBMIT_SM>>-------->>>>>-->>>>UPLINK 1
SMPPCLIENT 1 <-------MESSAGE_ID <-------JASMIN  (While submission)
While We got DLR from uplink 1 with specific error code
We resent it to Uplink 2 with some other re-routing. But message ID shall remain same and again if we got status then we send to SMPP Client final report after that retry.
Please advice. how can we handle this situation.
-Anshu

Duplicate issue #561: re-queue MT message after DLR received
Created: 2017-04-19T20:53:17Z
Hi
I am now trying to explore interceptor-client. Can you share any method to re-queue the same MT message again with some specific Tag, While we receive any specific DLR Err code.
Please advice.

Closing comment (2017-04-27T13:31:02Z): duplicate #543
Repository: jookies/jasmin

Issue #20: Handle variation of message_id when playing with DLR
Created: 2013-08-27T21:53:43Z
The number base the SMSC is using for the message ID numbers in the corresponding submit_sm_resp and deliver_sm PDUs can be different (hex / dec).
listeners.deliver_sm_callback() must read the right number whatever number base is used by the SMSC

Duplicate issue #24: Verify behaviour when msgid is differently coded between submit_sm_resp and deliver_sm (dlr)
Created: 2013-11-03T01:11:15Z

Closing comment (2013-12-22T18:24:42Z): Duplicate #20
Repository: jookies/jasmin

Issue #493: unable update dlr in mysql db at jasmin v0.9.b11
Created: 2016-10-23T18:58:55Z
hi

i am using sms_logger.py file to insert and update dlrs in mysql db (In jasmin v0.9.b3)
using jasmin v 0.9.b11 i am able to insert  but unable to update dlr into mysql database( update query not executing )
plz help me , thanks in advance

Duplicate issue #492: How to update dlr reports to particular messageId in new jasmin0.9.b11
Created: 2016-10-19T10:48:40Z
HI i am using jasmin 0.9.b3 version but unfortunately new version 0.9.b11 is updated in repository due to new version we are unable to update dlr reports to particular messageId. so, plz help us ,Thanks in Advance .

Closing comment (2016-10-23T19:09:48Z): Seems same as #493, continuing discussion there.
Repository: jookies/jasmin

Issue #643: Delivery error - DLRMapNotFound: Got a DLR for an unknown message id
Created: 2017-12-23T01:03:13Z
Not sure why "DLRMapNotFound: Got a DLR for an unknown message id" this error shows up for DLR, hence sharing message.log and smpp logs for a single message sent.
I have even tried with all parameters 0,1 and 2 in dlr_msgid still no luck.
Would highly appreciate if someone can help me out or point me in the right direction? I do see that  0e999f21 and E999F21 (difference where 0 is missing)
2017-12-23 00:46:39 INFO     5350 SMS-MT [uid:u1] [cid:routesms] [msgid:b036c3b7-6120-4ced-bdbe-cc1d8e684958] [prio:0] [from:SPRGPS] [to:8******849] [content:f1]
2017-12-23 00:46:39 INFO     5350 SMS-MT [cid:routesms] [queue-msgid:b036c3b7-6120-4ced-bdbe-cc1d8e684958] [smpp-msgid:0e999f21-81ef-4974-a414-3de98174e3c7] [status:ESME_ROK] [prio:0] [dlr:NO_SMSC_DELIVERY_RECEIPT_REQUESTED] [validity:none] [from:SPRGPS] [to:8******849] [content:'f1']
2017-12-23 00:46:45 ERROR    5353 [msgid:E999F21-81EF-4974-A414-3DE98174E3C7] (retrials: 1/2) DLRMapNotFound: Got a DLR for an unknown message id: 0e999f21-81ef-4974-a414-3de98174e3c7 (coded:E999F21-81EF-4974-A414-3DE98174E3C7)
2017-12-23 00:46:55 ERROR    5353 [msgid:E999F21-81EF-4974-A414-3DE98174E3C7] (final) DLRMapNotFound: Got a DLR for an unknown message id: 0e999f21-81ef-4974-a414-3de98174e3c7 (coded:E999F21-81EF-4974-A414-3DE98174E3C7)

Duplicate issue #535: Alphanumeric DLR smc_id
Created: 2017-02-12T16:53:15Z
The DLR smc_id I'm getting is alphanumeric with dashes... I guess something like the jasmin message ID. It's around 36 characters long. So it's failing (it's not hexa, and it's not decimal).

Closing comment (2017-12-30T08:08:39Z): @tarikogut given example is not about the same ID format described by @ominds:
I guess something like the jasmin message ID. It's around 36 characters long. So it's failing (it's not hexa, and it's not decimal).
This issue is same as #643
Repository: jordanbaird/Ice

Issue #139: [Feature Request]: Hide icon from dock
Created: 2024-06-11T10:33:42Z
Description
An option to hide the app's icon from the dock
when I start up and login the ice icon is always in the recently-active part of the dock
Screenshots

Duplicate issue #161: [Feature Request]: Hide dock icon
Created: 2024-06-17T09:14:57Z
Description
Would be possible to hide the Ice icon in the dock? As an always running application the dock icon is not needed.
Thanks for the great app!
Screenshots
No response

Closing comment (2024-06-17T09:16:28Z): Duplicate of #139
Repository: jordanbaird/Ice

Issue #264: Option to make menubar taller on Macs without the notch
Created: 2024-07-23T07:27:12Z
Check Existing Issues

 I have searched existing issues, and this issue is not a duplicate

Description
Found the app today, seems great so far.
If possible, I'd love to see an option to make the menubar taller so that it matches how it looks on the newer notched MacBooks. I am on an M1 Air and it is annoying how short the menubar is with no padding between the text and the top/bottom edges of the menubar.
Hopefully this is something that is feasible and is added soon. Best of luck to the developer for the future of the app
Screenshots
No response

Duplicate issue #373: [Feature Request]: Adjustable Menu Bar Height
Created: 2024-09-23T23:26:15Z
Check Existing Issues

 I have checked existing issues, and this issue is not a duplicate

Description
One of the thing I hate most using a mac with a notch now is that the menu bar is weirdly tall- and there is a 5ish pixel gap between the bottom of the menu bar and the bottom of the notch. It would be nice if I could make the menu bar shorter so that it lines up with the notch and is closer to its old height. It would also be nice if doing this naturally adjusts the area a window can take up so that a max height window does not have that same gap once the menu bar is shorter.
(I found this reddit post complaining about what I'm talking about and took the image from there)
Screenshots

Closing comment (2024-10-08T18:10:16Z): Marking as a duplicate of #264 for future reference.
Repository: jordanbaird/Ice

Issue #344: [Bug]: Menu bar items move to hidden or always hidden section
Created: 2024-09-04T11:18:27Z
Check Existing Issues

 I have checked existing issues, and this issue is not a duplicate

Description
whenever the mac is restarted  all ice icons go to the always hidden section
Steps to Reproduce
turn on ice bar
restart yor mac
check ice bar
Ice Version
0.10.5
macOS Version
14.6.1
Screenshots

Duplicate issue #470: [Bug]: menu bar layout not recalling prior after restart
Created: 2024-12-26T18:34:22Z
Check Existing Issues

 I have checked existing issues, and this issue is not a duplicate

Description
When I've restarted my latptop since 0.11.x relases (I'm on 0.11.13) the menu bar layout is not recalling what is was prior. For example on restart it shows some in ice bar and some in menu bar.  I also have to re-arrange them.
Steps to Reproduce

restart
click as normal to show ice bar
see icons re-arranged or not in prior order.

Ice Version
0.11.12
macOS Version
15.3
Screenshots
No response

Closing comment (2024-12-28T13:10:41Z): Duplicate of #344
Repository: jordanbaird/Ice

Issue #170: [Bug]: MacOS 15 Privacy Popups
Created: 2024-06-20T16:39:38Z
Check existing issues

 I have checked existing issues and believe that my issue is not a duplicate

Description
So since macos 15 I get this popup each time Ice records something on my screen. If I click Continue, it popups again.
This is very annoying, anything that could be done to keep it to a minimum?
Steps to Reproduce

Install MacOS 15
Run Ice

Ice Version
0.10.0-beta.4
macOS Version
15.0
Screenshots

Duplicate issue #280: [Bug]: macos 15 alert
Created: 2024-07-30T19:35:07Z
Check Existing Issues

 I have searched existing issues, and this issue is not a duplicate

Description
When clicking on the Ice menu bar icon after... a while, I'd guess it's somewhere around 30 minutes, a macos alert will continuously pop up, saying Ice is recording the display, asking for re-approval. It's only after clicking approve that Ice reacts. No further bugs spotted so far though :)
Will screenshot the next time it happens.
Steps to Reproduce
Quite unclear, stated above
Ice Version
0.10.3
macOS Version
15.0
Screenshots
No response

Closing comment (2024-07-30T20:45:07Z): Duplicate of #170
Repository: jordanbaird/Ice

Issue #6: [Feature Request] Change the location where new menu bar icons come up.
Created: 2024-02-04T21:14:08Z
It would be awesome if we could change where new icons come up.

Duplicate issue #357: [Feature Request]: Preference for which section to place new menu bar items into
Created: 2024-09-17T20:08:56Z
Check Existing Issues

 I have checked existing issues, and this issue is not a duplicate

Description
Would love to have a preference allowing us to choose which of the sections (Visible, Hidden, Always Hidden) new menu bar items go into. By default, it dumps into Always Hidden, which feels wrong to me; sending it to either Visible (and letting me update) or Hidden (and inviting me to either surface or banish it - this is my personal preference).
Screenshots
No response

Closing comment (2024-09-17T22:27:16Z): Duplicate of #6
Repository: jordanbaird/Ice

Issue #371: [Bug]: Unable to open Ice settings panel
Created: 2024-09-23T17:26:58Z
Check Existing Issues

 I have checked existing issues, and this issue is not a duplicate

Description
Hello there, thank's so much for this really useful and free tool !
It seems that there is an issue with the latest release. I'm on macOS 15.0 Sequoia (M2 pro chip) et now it's impossible to open Ice settings directly from the menubar (right click "Ice settings..."). On the click, nothing happen. I have to quit the app, then reload it and now I am able do access the settings panel. But after a computer startup, the problem reappear. Alternatively, when I go to launchpad after clicking on the "Ice settings..". menubar sub-menu, and when I click on the app icon from the launchpad, that's open the settings. I tried to deinstall the app with AppCleaner, but it seems to be the same. I installed Ice with homebrew.
Could you take a look at that ?
Steps to Reproduce
My config :

Set up the launch at login function
Enable automatically rehide
Enable show ice icon
Enable use ice bar
Use ellipsis Icon
None for tint
Border "1px" and shape kind "Split" with round corner
Enable the notch option
Try to change the menubar spacing, apply then reset it to normal behavior
Restart the computer then try to open the settings under the Ice icon and with a right click
Try to open the settings from the app icon in launchpad

Ice Version
0.11.3
macOS Version
15.0
Screenshots
No response

Duplicate issue #375: [Bug]: Ice Settings window does not show up [OS 18.1 beta 4-5]
Created: 2024-09-24T06:04:57Z
Check Existing Issues

 I have checked existing issues, and this issue is not a duplicate

Description
After upgrading to Mac OS 18.1 beta 4, the Ice Settings window does not show up when I choose it from the Ice menu bar. I need to manually quit Ice and then relaunch Ice to be able to access the settings.
Steps to Reproduce

right click the Ice menu bar item, settings screen does not show up
quit Ice
relaunch Ice
now the Settings window is shown

Ice Version
0.11.3
macOS Version
18.1 beta 5
Screenshots
No response

Closing comment (2024-09-24T16:02:47Z): Duplicate of #371
Repository: jordanbaird/Ice

Issue #344: [Bug]: Menu bar items move to hidden or always hidden section
Created: 2024-09-04T11:18:27Z
Check Existing Issues

 I have checked existing issues, and this issue is not a duplicate

Description
whenever the mac is restarted  all ice icons go to the always hidden section
Steps to Reproduce
turn on ice bar
restart yor mac
check ice bar
Ice Version
0.10.5
macOS Version
14.6.1
Screenshots

Duplicate issue #447: [Bug]: Application update new version does not go back to menubar set
Created: 2024-11-26T16:46:50Z
Check Existing Issues

 I have checked existing issues, and this issue is not a duplicate

Description
When a new version or app updates occur example shottr app - I download to new version and copied to the app folder it does not go back to the menubar I had configured.  Had to go to settings in Ice and move it there.
Steps to Reproduce
I download to new version and copied to the app folder it does not go back to the menubar I had configured.  Had to go to settings in Ice and move it there.
Ice Version
0.11.12
macOS Version
15.2
Screenshots
No response

Closing comment (2025-01-14T11:33:48Z): Duplicate of #344