Bug 274140
| Summary: | net-p2p/transmission-remote-gui: access violation on app startup, broken statusbar, etc. | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Anton Saietskii <vsasjason> | ||||||||||||
| Component: | Individual Port(s) | Assignee: | Jose Alonso Cardenas Marquez <acm> | ||||||||||||
| Status: | Closed Unable to Reproduce | ||||||||||||||
| Severity: | Affects Only Me | CC: | iaesauarannymfibhy | ||||||||||||
| Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(acm) |
||||||||||||
| Version: | Latest | ||||||||||||||
| Hardware: | Any | ||||||||||||||
| OS: | Any | ||||||||||||||
| URL: | https://www.freshports.org/net-p2p/transmission-remote-gui/ | ||||||||||||||
| Attachments: |
|
||||||||||||||
Created attachment 245304 [details]
poudriere build log
Just in case here's the build log to indicate which depends my transgui if built against.
(In reply to Anton Saietskii from comment #1) s/if/is/ Created attachment 245322 [details] dirty patch This is a quick and dirty patch to switch to xavery@ fork, which is most starred (https://github.com/xavery/transgui). Unfortunately, it doesn't fix access violation on startup. Moreover, clicking anywhere in menu which should open new forms (like "About") causes invalid type cast error and application termination. Attaching it here for reference. Created attachment 245353 [details]
poudriere build logs
Build logs for both versions -- in-tree & xavery@ fork, using both lazarus and lazarus-devel.
Created attachment 245354 [details]
broken statusbar screenshot
Hello, I can not reproduce Access Violation pops up. Could you tell me what version of FreeBSD are you using? What desktop? I have tested it (gtk2 and qt5) on FreeBSD 14-BETA4 Plasma and It works without problems excepts paths issue (In reply to Jose Alonso Cardenas Marquez from comment #6) Using FreeBSD 13.2-RELEASE-p2 amd64 with XFCE (everything built from latest ports tree). (In reply to Anton Saietskii from comment #7) Hello, I tested on 13.2-amd64-p3 xfce and it is working with no Access Violation pops up. Take a look at https://people.freebsd.org/~acm/ports/transgui/ Btw, I didn't compile it from ports. I installed it from packages-latest (In reply to Jose Alonso Cardenas Marquez from comment #8) Must say that I've lost interest in further investigation -- not using transgui anymore in favor of another tool. Would you prefer to get additional info (like port options and other configuration) to continue or just closing this with "overcome by events" would be enough? Thanks for your report. I can't reproduce the issues. Feel free to open this PR in any moment (In reply to Jose Alonso Cardenas Marquez from comment #10) Likely I won't -- doubt that fixing something I don't use anymore worth my time. However, I'd like to encourage you to do a thorough consideration of the following points: 1. Latest release was made on October 12th, 2019, which usually isn't a common thing for a well-maintained software (except TeX maybe). Additionally, there were no significant commits in repo, mostly like translations. Thus, I'd call transmission-remote-gui/transgui GitHub project as abandonware. 2. Abandonware means that most likely there are issues, and we can see 460 (!) open on project's GitHub (https://github.com/transmission-remote-gui/transgui/issues). Notable ones: 2.1. "New release please #1428" (https://github.com/transmission-remote-gui/transgui/issues/1428) -- people complaining about bugs (though indistinctively), asking for a new release, and even discussing alternative GUIs being tired waiting. 2.2. "Increase efficiency of communication between GUI and daemon #1422" (https://github.com/transmission-remote-gui/transgui/issues/1422) -- transgui doesn't support compressed RPC connections to daemon, which makes it almost unusable over a not-so-fast connections to daemon with large numbers of torrents. 2.3. "Randomly build failed with "Access violation" error #1453" (https://github.com/transmission-remote-gui/transgui/issues/1453) 2.4. "Missing support for TLSv1.3 #1370" (https://github.com/transmission-remote-gui/transgui/issues/1370) 3. As number of issues is high and counting, I suppose it may be worth trying to do something with port instead of leaving it as-is. Wouldn't say it should be marked as DEPRECATED, but please take a look at comment #3. We can see a list of transgui forks (active repos, last year, sort by stars desc): https://github.com/transmission-remote-gui/transgui/forks?include=active&page=1&period=1y&sort_by=stargazer_counts -- it appears that xavery@' fork is the best since most others updated a long time ago (not as long as original project, but anyway). There are few updated recently, but 0 stars (so likely they're new without many fixes). In contrast, xavery fork has at least some of issues fixed, e.g. #1422 and, (though I'm not 100%-sure here) #1370. Actually I was even thinking about making my own fork, but stopped at the point of discovery that FreePascal didn't receive updates for a considerable amount of time too... (In reply to Anton Saietskii from comment #11) Hello, also I think the best is used xavery fork instead of current one. I'll try give me time for do that freepascal and lazarus are active projects but they are not release binary (mostly fpc) until a bunch of new features/fixes are added. You can use fixes_3_2 branch (it is like an stable version) or main. Take a look at fpcupdeluxe tool (https://wiki.lazarus.freepascal.org/fpcupdeluxe). Maybe the best could be send PR to xavery fork. Btw, I'll do some changes to freepascal/lazarus ports asap. It will include support for qt6 for example, fpc-devel ports, etc The "Access violation" pop-up and seconds long delay following clicking the Ok button also happen in NixOS 23.11 stable and unstable under Sway but not under Gnome (wayland) or i3 (xorg). Stable uses https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/applications/networking/p2p/transgui/default.nix from 2022-02-02. Unstable uses https://github.com/NixOS/nixpkgs/blob/nixpkgs-unstable/pkgs/applications/networking/p2p/transgui/default.nix from 2024-02-26. Both are pulling from https://github.com/transmission-remote-gui/transgui. Using htop after clicking Ok and waiting shows xwayland to be throttling heavily. |
Created attachment 245303 [details] error screenshot Each time I start transgui, that nasty access violation pops up. Though it seems to finally start after pressing "OK" button, this isn't the only issue--for example, I can't edit path mappings in "Application settings -> Paths", simply nothing happens after clicking text box. Perhaps we can try to update that ancient release from 2019 to current snapshot or switch to xavery/transgui fork which appears to be alive?