Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: closing rquickshare, sgement violation. #147

Closed
jjsarton opened this issue Aug 8, 2024 · 10 comments
Closed

bug: closing rquickshare, sgement violation. #147

jjsarton opened this issue Aug 8, 2024 · 10 comments
Labels
bug Something isn't working

Comments

@jjsarton
Copy link

jjsarton commented Aug 8, 2024

I have compiled the latest version from github under Fedora 40 XFCE.
The close button accessible via the Setting button don't work.
If I close rquickshare after I have transmitted a file via rquickshare, I get the following terminal output:

024-08-08T19:55:00Z ERROR rqs_lib::manager: TcpServer: error while handling client: early eof (Finished)
2024-08-08T19:55:21Z  INFO rqs_lib::hdl::blea: BleAdvertiser: tracker cancelled, returning
2024-08-08T19:55:21Z  INFO rqs_lib::hdl::mdns_discovery: MDnsDiscovery: tracker cancelled, breaking
2024-08-08T19:55:21Z  INFO rqs_lib::hdl::ble: BleListener: tracker cancelled, breaking
2024-08-08T19:55:21Z  INFO rqs_lib::manager: TcpServer: tracker cancelled, breaking
2024-08-08T19:55:21Z  INFO rqs_lib::hdl::mdns: MDnsServer: tracker cancelled, breaking
2024-08-08T19:55:21Z ERROR mdns_sd::service_daemon: Failed to send event: sending on a closed channel
2024-08-08T19:55:21Z  INFO rqs_lib::hdl::mdns: MDnsServer: service unregistered: OK
Aborted (core dumped)

The first error message appear after the file was transferred.

If I close rquickshare without file transfer, there is no problem.

@Martichou
Copy link
Owner

Do you have the same issue with the latest available release ? I recently reworked the closing mechanism to be more streamlined, I don't see why it would segv tho (the rework is not yet released, that's why I'm asking)

@Martichou Martichou changed the title closing rquickshare, sgement violation. bug: closing rquickshare, sgement violation. Aug 8, 2024
@Martichou Martichou added the bug Something isn't working label Aug 8, 2024
@jjsarton
Copy link
Author

jjsarton commented Aug 9, 2024

I have installed the official rpm on an other system (r-quick-share-main_v0.10.2_glibc-2.39_1-x86_64.rpm) and also the official appImage on the test pc.
If I run the appimage no crash.
With the self compiled version which was rebuild today (2024-08-09), the same problem.
The settings for rquickshare is:

Start on boot: disabled
Keep Running on close: disabled
Start minimized: disabled (only available on compiled version)

The difference between the official appImage and the self compiled version is the following.
The appImage remain running!
The self compiled version perform a crash if I close the window.

@Martichou
Copy link
Owner

Okay so can you confirm this:

The officially released version doesn't close when you close the app? But the master version will close (but segv)?

Could you gather some logs using the Trace level? #104

@jjsarton
Copy link
Author

RQuickShare-close-abort.log
RQuickShare-close-ok.log

Attached 2 files. For the file RQuickShare-close-abort.log, I selected a file to transmit and then canceled the action and closed the window.
The trace seem not to contain valuable informations.

@Martichou
Copy link
Owner

Could you try with the new pre-released version ? (v0.11.1).

@jjsarton
Copy link
Author

Could you try with the new pre-released version ? (v0.11.1).

I have compiled rquickshare from the master branch and also from release-please--branches--master.
in both cases rquickshare don't work as expected.
If I try to send a file to an android smartphone, the left part of the GUI disappear and clicking on the name of the android device don't do anything.

@jjsarton
Copy link
Author

I tried also the AppImage with libc 2.31 which work as expected. Against the 2.39 libc the self compiled or the AppImage don't work as expected and closing the window produce a core dump.

@Martichou
Copy link
Owner

Ok so you confirm that the AppImage with libc 2.31 is working just fine? If that's the case I'll close this issue as you have a stable version to use.

There can be a multitude of reason why the other libc doesn't work on your system, that's why I released RQuickShare with two different targeted LIBC version.

Please confirm that the AppImage with 2.31 is working correctly.

@jjsarton
Copy link
Author

I have also run the 2.39 AppImage on an mint 22 system, the problems are the same as the self compiled version as well as the rpm and appImage from github.
The 2.31 AppImage work without the crash and the wrong layout.

@Martichou
Copy link
Owner

I'm gonna close this as there's two versions of Rquickshare for that very same purpose. A system can't be compatible with both the main and the legacy version. So if the 2.31 (legacy) works for you, use that one :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants