Hello Everyone,
Is possible release package for arm64 ?

sudo snap install winbox
error: snap "winbox" is not available on stable for this architecture (arm64) but exists on other
       architectures (amd64, i386).

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I think last connection info can be found drive_c/users/<user>/Application\ Data/Mikrotik/Winbox/settings.cfg.vi
Could be fine to persist this file

Describe the solution you'd like
A clear and concise description of what you want to happen.
I don't know how snap works.
May be the file must be copied at start and saved to user local snap persistent dir of this app ?

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

The log of winbox without snap:

saving settings to .\viw2dc9.tmp... for C:\users\gil\Application Data\Mikrotik\Winbox\settings.cfg.viw
[..]
loadConfig C:\users\gil\Application Data\Mikrotik\Winbox\Addresses.cdb
[...]
saving settings to .\viwc5be.tmp... for C:\users\gil\Application Data\Mikrotik\Winbox\settings.cfg.viw

Addresses is working fine, is only the last connection data

Describe the bug
Fonts appear to be rendering too small. The text cursor is out of position. This has no functional impact as text can be modified as normal. However it is a visual bug that might be confusing and frustrating for users trying to modify existing text.

This bug is NOT an issue with the Snap package, however a workaround can be applied to the Snap to fix this bug. See additional context below.

To Reproduce
Steps to reproduce the behavior:

1. Launch Winbox

Expected behavior
The text cursor should be at the end of the string of characters.

Screenshots

Distribution (please complete the following information):

• Name: Ubuntu
• Version: 20.04
• Architecture: amd64

** snap version **

snap    2.51.7
snapd   2.51.7
series  16
ubuntu  20.04
kernel  5.11.0-37-generic

** snap info winbox **

name:      winbox
summary:   small utility that allows administration of MikroTik RouterOS
publisher: ThePanaceya
store-url: https://snapcraft.io/winbox
license:   unset
description: |
  Winbox is a small utility that allows administration of MikroTik RouterOS using a fast and simple
  GUI.
  
  Snap conatins Wine runtime and winbox client.
commands:
  - winbox
snap-id:      UdK6K4ZjRfjL0wRFh0tWGO7vPhA4Qge4
tracking:     latest/stable
refresh-date: today at 20:43 CDT
channels:
  latest/stable:    3.30 2021-09-12 (68) 36MB -
  latest/candidate: ↑                         
  latest/beta:      ↑                         
  latest/edge:      ↑                         
installed:          3.30            (68) 36MB -

** snap list winbox **

Name    Version  Rev  Tracking       Publisher    Notes
winbox  3.30     68   latest/stable  thepanaceya  -

Additional context

I was able to fix this issue by applying a registry key to a WINEPREFIX outside of the Snap.

Here's the workaround I used to achieve my results.

[HKEY_CURRENT_USER\Software\Wine\X11 Driver]
"ClientSideWithRender"="N"

Source: MikroTik Forums

Hi,

I have an issue about session in this app, if i reopen a winbox session, its open a new session instead of continuing the previous session.

Thanks!

Winbox does not find a neighbor when connected directly to an RB that does not have an IP. I want to configure a new RB that does not have a defined IP. Therefore, I would like to access the equipment via the mac address of an ethernet interface. On Windows systems this is possible, but on Linux I haven't managed it yet. Can you guide me why it's not working?

I have already run the sudo ufw allow 5678/udp command on Linux Mint.

I noticed that via the network, Winbox lists RBs in production as neighbors. The problem occurs on new RBs that I try to access via mac address.

Hi, have a problem with showing columns.
For example in IP - DHCP - Leases
If I click on arrow - Show Columns - check Last Seen, columns are bad. Don't see Last Seen column, it shows me a lot of other columns, some columns are hidden again.

Distribution (please complete the following information):

• Name: Ubuntu
• Version: 20.04 LTS

** snap version **

latest

** snap info winbox **

3.30

btw when will be 3.31 available?

Thank you

There is a problem with one of the versions of winbox, an illegible text is obtained in the "note" column when writing information in Cyrillic

The following packages have unmet dependencies:
winehq-stable : Depends: wine-stable (= 6.0.1~hirsute-1)
E: Unable to correct problems, you have held broken packages.

Please add StartupWMClass=winbox.exe to the .desktop file to correctly display a running app in a single icon, but not two - one winbox and second a wine. GNOME.

Hi, a problem for winbox in ubuntu 24.04 LTS.
Instalation is ok, more when i open, the program starts wine, but does not open winbox,

can't run winbox on wine with env variable WINEARCH=win64

I tried to reinstall the snap, but I'm getting basically the same error in journalctl logs.
It comes down to "000b:err:module:__wine_process_init failed to load L"C:\windows\system32\wineboot.exe", error c0000018".

On 2024-02-21 I updated my packages after a month of not updating. 441 packages were updated as a regular system update.
Nothing except of that changed on my system.

snap info:
tracking: latest/stable refresh-date: 21 days ago, at 16:03 CET channels: latest/stable: 3.40 2024-01-30 (133) 47MB - latest/candidate: ↑ latest/beta: ↑ latest/edge: ↑ installed: 3.40 (133) 47MB -

journalctl info:
lut 23 15:44:22 legion-y530 systemd[10204]: Started app-gnome-winbox_winbox-615420.scope - Application launched by gnome-shell. lut 23 15:44:23 legion-y530 audit[615587]: SECCOMP auid=1000 uid=1000 gid=1000 ses=5 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=615587 comm="wineserver" exe="/snap/winbox/133/wine-platform/wine-stable/bin/wineserver" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7eff8bd88f09 code=0x50000 lut 23 15:44:23 legion-y530 audit[615587]: SECCOMP auid=1000 uid=1000 gid=1000 ses=5 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=615587 comm="wineserver" exe="/snap/winbox/133/wine-platform/wine-stable/bin/wineserver" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7eff8bd88f09 code=0x50000 lut 23 15:44:46 legion-y530 audit[615996]: SECCOMP auid=1000 uid=1000 gid=1000 ses=5 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=615996 comm="wineserver" exe="/snap/winbox/133/wine-platform/wine-stable/bin/wineserver" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f1564401f09 code=0x50000 lut 23 15:44:46 legion-y530 winbox_winbox.desktop[615998]: 000b:err:module:__wine_process_init failed to load L"C:\\windows\\system32\\wineboot.exe", error c0000018 lut 23 15:44:46 legion-y530 winbox_winbox.desktop[615993]: 0009:err:environ:run_wineboot failed to start wineboot c0000018 lut 23 15:44:46 legion-y530 audit[615996]: SECCOMP auid=1000 uid=1000 gid=1000 ses=5 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=615996 comm="wineserver" exe="/snap/winbox/133/wine-platform/wine-stable/bin/wineserver" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f1564401f09 code=0x50000 lut 23 15:44:46 legion-y530 winbox_winbox.desktop[616000]: 000f:err:module:__wine_process_init failed to load L"C:\\windows\\system32\\wineboot.exe", error c0000018 lut 23 15:44:46 legion-y530 winbox_winbox.desktop[615993]: 000d:err:environ:run_wineboot failed to start wineboot c0000018 lut 23 15:44:46 legion-y530 winbox_winbox.desktop[615993]: 000d:err:module:__wine_process_init failed to load L"C:\\windows\\system32\\start.exe", error c0000018 lut 23 15:44:49 legion-y530 systemd[10204]: app-gnome-winbox_winbox-615420.scope: Consumed 23.588s CPU time.

Any ideas what might be going on?

Describe the bug
Winbox not start when the network is attached but no internet is present, like misconfiguration of LAN ora DNS not configured.
If i start winbox with network cable detached, no problem, if i start winbox with internet OOK, no problem.

To Reproduce
Configure LAN with wrong parameter
Attach network cable
Run winbox

Expected behavior
The expected behaviour is the winbox open in any case

Screenshots

Distribution (please complete the following information):

• Name: Red Hat
• Version: Red Hat Enterprise Linux 8.8 (Ootpa)
• Architecture: amd64

** snap version **

2.58.3-1.el8

** snap info winbox **

name:      winbox
summary:   small utility that allows administration of MikroTik RouterOS
publisher: ThePanaceya
store-url: https://snapcraft.io/winbox
license:   unset
description: |
  Winbox is a small utility that allows administration of MikroTik RouterOS using a fast and simple
  GUI.
  
  Snap conatins Wine runtime and winbox client.
  
  Readme: https://github.com/panaceya/winbox/blob/main/README.md
commands:
  - winbox
snap-id:      UdK6K4ZjRfjL0wRFh0tWGO7vPhA4Qge4
tracking:     latest/stable
refresh-date: 49 days ago, at 11:41 CET
channels:
  latest/stable:    3.40 2024-03-09 (135) 47MB -
  latest/candidate: ↑                          
  latest/beta:      ↑                          
  latest/edge:      3.40 2024-03-05 (135) 47MB -
installed:          3.40            (135) 47MB -

** snap list winbox **

Name    Version  Rev  Tracking       Publisher    Notes
winbox  3.40     135  latest/stable  thepanaceya  -

Additional context

winbox does not start on ubuntu desktop 24.04 gnome 46 wayland does not show the graphical interface

[ ] support armhf platform
[ ] test

after doing snapcraft, this the result...

• snapcraftctl set-version 3.39+git
  Staging winbox
• snapcraftctl stage
  Priming winbox
• snapcraftctl prime
  The interpreter 'bash' for 'winbox' was resolved to '/bin/bash'.
  The command 'winbox' has been changed to '/bin/bash $SNAP/winbox' to safely account for the interpreter.
  A shell wrapper will be generated for command '/bin/bash $SNAP/winbox' as it does not conform with the command pattern expected by the runtime. Commands must be relative to the prime directory and can only consist of alphanumeric characters, spaces, and the following special characters: / . _ # : $ -
  Snapping |
  Snapped winbox_3.39_amd64.snap

then i try to run winbox, this the result...

root@debian:~/winbox# winbox
2023/09/24 09:00:29.827082 cmd_run.go:1055: WARNING: cannot start document portal: write unix @->/run/user/1000/bus: write: broken pipe
mkdir: cannot create directory ‘/run/user/0’: Permission denied
/snap/winbox/121/winbox: line 287: wine: command not found
/snap/winbox/121/winbox: line 335: notify-send: command not found
cp: target '/run/user/0/snap.winbox/' is not a directory

do have any idea...?
thanks

Describe the bug
I cannot upload file to device

To Reproduce
click files

1. click upload
2. select file from your home directory
3. click open

Expected behavior
files should be appeared on remote device.

.

After installing winbox via snap install command, I try to run winbox. Winbox comes up, I connect to a router, open some windows and move them in place, then close winbox. The next time I open winbox, the session is not saved and the window positions are reset to defaults. The snap installation does create a ~/snap/winbox directory structure.

If I install winbox outside of the snap environment, winbox can save it sessions and window positions.

I'm testing Ubuntu 24.04. Winbox snap isn't work.

journalctl:

Apr 18 10:21:56 mrai-noc systemd[2621]: Started snap.winbox.winbox-82307a99-1f85-41bf-8625-fdf97e4b276d.scope.
Apr 18 10:21:57 mrai-noc kernel: audit: type=1326 audit(1713446517.390:359): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.winbox.winbox pid=32832 comm="wineserver" exe="/snap/winbox/135/wine-platform/wine-stable/bin/wineserver" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7621626b3f09 code=0x50000
Apr 18 10:21:57 mrai-noc winbox_winbox.desktop[32834]: 000b:err:module:__wine_process_init failed to load L"C:\windows\system32\wineboot.exe", error c0000018
Apr 18 10:21:57 mrai-noc winbox_winbox.desktop[32829]: 0009:err:environ:run_wineboot failed to start wineboot c0000018
Apr 18 10:21:57 mrai-noc kernel: audit: type=1400 audit(1713446517.682:360): apparmor="DENIED" operation="open" class="file" profile="snap.winbox.winbox" name="/run/" pid=32832 comm="wineserver" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 18 10:21:57 mrai-noc kernel: audit: type=1326 audit(1713446517.687:361): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.winbox.winbox pid=32832 comm="wineserver" exe="/snap/winbox/135/wine-platform/wine-stable/bin/wineserver" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7621626b3f09 code=0x50000
Apr 18 10:21:57 mrai-noc kernel: audit: type=1400 audit(1713446517.790:362): apparmor="DENIED" operation="connect" class="file" profile="snap.winbox.winbox" name="/run/cups/cups.sock" pid=32836 comm="winbox64.exe" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0
Apr 18 10:21:57 mrai-noc winbox_winbox.desktop[32836]: 000d:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
Apr 18 10:21:57 mrai-noc winbox_winbox.desktop[32836]: 000d:err:winediag:nodrv_CreateWindow The explorer process failed to start.

It gives the following error > wget -O winbox32.exe https://download.mikrotik.com/winbox/3.40/winbox.exe
--2024-04-30 10:06:20-- https://download.mikrotik.com/winbox/3.40/winbox.exe
Resolving download.mikrotik.com (download.mikrotik.com)... 159.148.147.251, 2a02:610:7501:3000::251
Connecting to download.mikrotik.com (download.mikrotik.com)|159.148.147.251|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2024-04-30 10:06:21 ERROR 403: Forbidden.

Failed to run 'override-build': Exit code was 8.
Run the same command again with --debug to shell into the environment if you wish to introspect this failure.

when ufw enable i can't neighbors from mikrotik...

Since second start after successfull first (very slow init wine conf) its unable to start - please see detail below.

To Reproduce
Steps to reproduce the behavior:

1. snap install winbox
2. w8 zillion of seconds to bring few MB simple APP to be installed - under wine, not snap
3. PS: import of wbx/wba files do nothing - another issue
4. the actual disconnect close the app - why?
5. app is closed, its not running but cant be opened anymore with such a stupid nonsense error:

notify-send: relocation error: /snap/winbox/97/wine-runtime/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0: symbol inflateGetHeader version ZLIB_1.2.2 not defined in file libz.so.1 with link time reference
wine: failed to initialize: /opt/wine-stable/lib64/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
0009:err:environ:run_wineboot failed to start wineboot c00000e5
wine: failed to initialize: /opt/wine-stable/lib64/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: Internal error.

Expected behavior
Import of regular previous export to be working
Disconnect shall just disconnect - NOT close the app
It could work at least for a while when its freshly installed & running

Distribution (please complete the following information):

• Name: Fedora
• Version: 36
• Architecture: amd64

** snap version **

snap    2.56.2-4.fc36
snapd   2.56.2-4.fc36
series  16
fedora  36
kernel  6.0.5-200.fc36.x86_64

** snap info winbox **

name:      winbox
summary:   small utility that allows administration of MikroTik RouterOS
publisher: ThePanaceya
store-url: https://snapcraft.io/winbox
license:   unset
description: |
  Winbox is a small utility that allows administration of MikroTik RouterOS using a fast and simple
  GUI.
  
  Snap conatins Wine runtime and winbox client.
  
  Readme: https://github.com/panaceya/winbox/blob/main/README.md
commands:
  - winbox
snap-id:      UdK6K4ZjRfjL0wRFh0tWGO7vPhA4Qge4
tracking:     latest/stable
refresh-date: today at 11:59 CET
channels:
  latest/stable:    3.37 2022-10-06 (97) 47MB -
  latest/candidate: ↑                         
  latest/beta:      ↑                         
  latest/edge:      ↑                         
installed:          3.37            (97) 47MB -

** snap list winbox **

Name    Version  Rev  Tracking       Publisher    Notes
winbox  3.37     97   latest/stable  thepanaceya  -

I've installed this snap and compared the md5sum result for the winbox64.exe file obtained from the snap and the one obtained from https://download.mikrotik.com/winbox/3.40/winbox64.exe - Both executables are Winbox 3.40 version and I noticed the md5 hashes does not match as I demonstate below:

$ md5sum /snap/winbox/123/usr/libexec/winbox64.exe
048e1265d4db9196583e9d23ad4d70d5  /snap/winbox/123/usr/libexec/winbox64.exe
$ wget -q https://download.mikrotik.com/winbox/3.40/winbox64.exe;md5sum winbox64.exe
0b5da86bd6f2603b9427a18d192b61b6  winbox64.exe

While I can find results for 0b5da86bd6f2603b9427a18d192b61b6 on Google search engine (with links directing to mikrotik.com official website), the hash 048e1265d4db9196583e9d23ad4d70d5 was never mentioned before.

Shouldn't both files be exactly the same? Why the binary provided by this package is not the same provided by the official manufacturer website?

** snap version **

ayub@indaiatuba:/tmp$ snap info winbox
name:      winbox
summary:   small utility that allows administration of MikroTik RouterOS
publisher: ThePanaceya
store-url: https://snapcraft.io/winbox
license:   unset
description: |
  Winbox is a small utility that allows administration of MikroTik RouterOS using a fast and simple
  GUI.
  
  Snap conatins Wine runtime and winbox client.
  
  Readme: https://github.com/panaceya/winbox/blob/main/README.md
snap-id: UdK6K4ZjRfjL0wRFh0tWGO7vPhA4Qge4
channels:
  latest/stable:    3.40 2023-10-16 (123) 47MB -
  latest/candidate: ↑                          
  latest/beta:      ↑                          
  latest/edge:      ↑ 

how to upgrade the winbox to version 3.31 ?

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Distribution (please complete the following information):

• Name: [e.g. ubuntu, neon, debian]
• Version: [e.g. 20.04, 18.04]
• Architecture: [e.g. amd64 or i386 or ...]

** snap version **

** snap info winbox **

** snap list winbox **

Additional context
Add any other context about the problem here.

Is your feature request related to a problem? Please describe.
I am use UFW firewall on my PC. After adding port UDP 5678 "Neighbors" works fine.
Wine64-preloader uses also port to communicate with RouterOS, but every time other port.

Describe the solution you'd like
I am do not know. :-/

Describe alternatives you've considered
Apply default port for Wine? Any rule for UFW?

Thanks You.