[Support] binhex - HexChat


Recommended Posts

4 hours ago, Toobie said:

Ok thanks for the explanation.

But - im using 3 of your docker images (at this point, thanks for the work) and they are all a bit "huge"

So, is there a way to optimize this or this already optimised as written above?

 

image.png.95d8c97065e23c08869a142caacfea1e.png

 

the size of the container does not take into account layers shared, for instance if you re-downloaded krusader you would see the amount of data pulled down from docker hub would not be 2.47 GB, it would probably be more something in the range of 300 MB. plus when looking at sizes you should be looking at the image size not the container size, unless you of course have an issue with balloning containers (nearly always due to misconfiguration of the app).

 

in short, nope there is nothing you can do to optimise this. 

 

to prove im really not telling porkies :-), check the pull size of hexchat for me, this is due to me having the intermediate image already, which you should also have:-

 

image.thumb.png.57c46101b0806a58f18c7ebb22ba2e59.png

Edited by binhex
Link to comment
  • 2 weeks later...
  • 5 weeks later...

Great docker -thanks for the hard work to get this going!

Now question: is there a way to link my hex client (windows) with the docker?  

 

-You may wonder why do this? Simple, my unraid docker runs all the time so all the messages posted in a channel are always there, while my windows client disconnects whenever it goes to sleep or I turn it off (therefore losing the history of what was posted while I was gone). In addition the notification/flashing isn't really notifying me of new messages when running in the browser/docker. If I could link my windows client with the docker somehow, it could connect showing all the previous posts and alert me when new messages appear.

Link to comment
Great docker -thanks for the hard work to get this going!
Now question: is there a way to link my hex client (windows) with the docker?  
 
-You may wonder why do this? Simple, my unraid docker runs all the time so all the messages posted in a channel are always there, while my windows client disconnects whenever it goes to sleep or I turn it off (therefore losing the history of what was posted while I was gone). In addition the notification/flashing isn't really notifying me of new messages when running in the browser/docker. If I could link my windows client with the docker somehow, it could connect showing all the previous posts and alert me when new messages appear.
No you can't do this, hexchat is not a client/server model, so there is no way of connecting an external client to an already running instance, at least that's my understanding.

Sent from my CLT-L09 using Tapatalk

Link to comment
  • 1 month later...
  • 2 months later...
On 2/12/2020 at 3:57 PM, sheldon said:

Great docker -thanks for the hard work to get this going!

Now question: is there a way to link my hex client (windows) with the docker?  

 

-You may wonder why do this? Simple, my unraid docker runs all the time so all the messages posted in a channel are always there, while my windows client disconnects whenever it goes to sleep or I turn it off (therefore losing the history of what was posted while I was gone). In addition the notification/flashing isn't really notifying me of new messages when running in the browser/docker. If I could link my windows client with the docker somehow, it could connect showing all the previous posts and alert me when new messages appear.

Soundsl like you want ZNC or Quassel-Core for this.

Link to comment
  • 4 months later...
  • 1 year later...

Since the latest update I am getting this:

2021-12-13 11:02:44,560 DEBG 'start' stderr output:
tint2: xRandr: Found crtc's: 1
tint2: xRandr: Linking output VNC-0 with crtc
2021-12-13 11:02:44,560 DEBG 'start' stderr output:
0, resolution 1024x768, DPI 96
tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc
tint2: Could not read config file.

2021-12-13 11:02:44,560 DEBG 'start' stdout output:
Usage: tint2 [OPTION...]


I opened console for the container and the entire path after /.config is gone

Link to comment
  • 1 month later...

hi. kinda new here.

 

love your  hexchat implementation but i cant seem to figure out how to set the file permission it writes files with.

i thought id achieve more permissions by setting the umask to 000 but no dice.

 

edit: tried 002 and 022 too now which at least one of them should do the trick but doesnt for some reason?

PUID is set to 99 and PGID is set to 100. I have tried to download to several different folder locations too.

 

edit2: setting PUID and PGID to 0 didnt change anything either.

 

welp, what can i do?

 

edit:3~ after further investigating i figured its not the container itself but JUST  the haxchat app. if i create a file through thunar it gets enough permissions (644, -rw-r--r--). if i get sent a file over dcc OR create one through window -> save text (inside hexchat) it gets the permission 600, -rw-------.

 

final edit: thanks for the help everyone, i figured it out. byeeeee

 

 

 

 

 

 

 

 

 

 

 

 

 

just kidding. APPEARENTLY its the entry dcc_permissions in the hexchat.conf. its set to 384 but needs to be at 420 minimum. which makes no sense because even text files created through the client that werent recieved throuch dcc had the low permissions / are effected by this. fml.

Edited by m4rcus
Link to comment
  • 1 year later...

is just me or the latest update broke the app ? because for me latest is not working

 

downgrading to 2.16.1-3-01 is working

 

 

`

Traceback (most recent call last):
  File "/usr/sbin/websockify", line 33, in <module>
    sys.exit(load_entry_point('websockify==0.10.0', 'console_scripts', 'websockify')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/sbin/websockify", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
                       ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 981, in distribution
    return Distribution.from_name(distribution_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 565, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for websockify

2023-05-07 11:45:57,217 DEBG 'start' stderr output:
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

2023-05-07 11:45:57,217 DEBG 'start' stderr output:

Xvnc TigerVNC 1.13.1 - built Mar 10 2023 21:57:50
Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12101006


Sun May  7 11:45:57 2023
 vncext:      VNC extension running!

2023-05-07 11:45:57,217 DEBG 'start' stderr output:
 vncext:      Listening for VNC connections on all interface(s), port 5900
 vncext:      created VNC server for screen 0

2023-05-07 11:45:57,266 DEBG 'start' stderr output:
[mi] mieq: warning: overriding existing handler (nil) with 0x563e1a18b920 for event 2
[mi] mieq: warning: overriding existing handler (nil) with 0x563e1a18b920 for event 3

2023-05-07 11:46:01,157 DEBG 'start' stdout output:
[info] tint2 not running

2023-05-07 11:46:01,167 DEBG 'start' stderr output:
tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavi
2023-05-07 11:46:01,167 DEBG 'start' stderr output:
or or crashes

2023-05-07 11:46:01,172 DEBG 'start' stderr output:
t
2023-05-07 11:46:01,173 DEBG 'start' stderr output:
int2: xRandr: Found crtc's: 1
tint2: xRandr: Linking output VNC-0 with crtc 0, resolution 1024x768, DPI 96

2023-05-07 11:46:01,199 DEBG 'start' stderr output:

(hexchat:93): Gtk-WARNING **: 11:46:01.198: Unable to locate theme engine in module_path: "adwaita",

2023-05-07 11:46:01,338 DEBG 'start' stderr output:

(hexchat:93): Gtk-WARNING **: 11:46:01.338: Unable to locate theme engine in module_path: "murrine",

2023-05-07 11:46:01,349 DEBG 'start' stderr output:

(hexchat:93): Gtk-WARNING **: 11:46:01.349: Unable to locate theme engine in module_path: "adwaita",

2023-05-07 11:46:16,178 DEBG 'start' stderr output:
tint2: warning : WM doesn't respect NETWM specs. tint2 default to 1 desktop.

2023-05-07 11:46:16,178 DEBG 'start' stderr output:
tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc

2023-05-07 11:46:16,181 DEBG 'start' stderr output:
tint2: real transparency on... depth: 32

2023-05-07 11:46:16,182 DEBG 'start' stderr output:
tint2: panel items: TSC
tint2: Systray composited rendering on

2023-05-07 11:46:16,182 DEBG 'start' stderr output:
tint2: nb monitors 1, nb monitors used 1, nb desktops 1
tint2: panel 1 uses scale 1 

2023-05-07 11:46:16,215 DEBG 'start' stderr output:
tint2: Kernel uevent interface initialized...

2023-05-07 11:46:16,215 DEBG 'start' stderr output:
tint2: systray window 4194317
tint2: systray started

`

Edited by Danuel
Link to comment
1 hour ago, Danuel said:

is just me or the latest update broke the app ? because for me latest is not working

 

thanks for letting me know, i will rebuild the image, the issue was due to the switch from python 3.10 to 3.11, it caused me all sorts of fun and games i can tell ya!. try pulling the image in about 30 mins from now.

Link to comment
1 hour ago, binhex said:

it looks to me like you aren't running the latest image, go to unraid/docker then toggle basic view to advanced view, then click on 'force update' for the container, this will then force download the latest image.

 i can confirm, that  foce update fix the problem

Link to comment
  • 2 weeks later...

I've recently installed this container and started using it.

I've noticed something weird. The container seemed to stop itself after a while, and when I started it again, the network list had reset back to default (a network I added was gone and networks I deleted were back), but my other preferences (Settings -> Preferences) seemed to remain.

Link to comment
On 5/25/2023 at 6:30 AM, gamerkonks said:

I've recently installed this container and started using it.

I've noticed something weird. The container seemed to stop itself after a while, and when I started it again, the network list had reset back to default (a network I added was gone and networks I deleted were back), but my other preferences (Settings -> Preferences) seemed to remain.

sorry im unable to reproduce this, i just deleted a server from the network list, restarted the container, recheck network list and the server i deleted is still gone.

Link to comment

Is it possible to route the traffic of this IRC client through a Docker/VPN? I tried passing it my customer network/VPN after adding a modified port (6082, b/c 6080 was occupied by Krusader), but it won't connect locally. It is getting its IP from the Docker/VPN though, so that is working. Just cannot connect locally @ 192.168.1.x:6082.

Link to comment
  • 4 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.