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

Linux AppImage crashes when URL link is clicked on #211

Closed
cement-head opened this issue Jun 17, 2019 · 12 comments
Closed

Linux AppImage crashes when URL link is clicked on #211

cement-head opened this issue Jun 17, 2019 · 12 comments
Assignees
Labels
Status-Fixed Ticket is resolved. Type-Defect This is BUG!!! Type-Deployment Problem is caused by badly deployed application files.
Milestone

Comments

@cement-head
Copy link

cement-head commented Jun 17, 2019

Brief description of the issue.

Using 3.5.8 and 3.5.9 on Ubuntu 18.04 with Unity desktop, everytime I try clicking on the URL link for an article, the application crashes.

How to reproduce the bug?

  1. Download the AppImage & make it executable
  2. Navigate to an article
  3. Click on the blue-boxed URL link for the article

What is the expected result?

The article should be downloaded and displayed in the window within the RSSGuard

What actually happened?

Application immediately crashed; didn't happen with 3.5.6 (Does with 3.5.8 & 3.5.9)

Other information (logs, see Wiki)

@cement-head
Copy link
Author

rss-log.txt

@cement-head
Copy link
Author

Is the libnss3 library being installed to an "incorrect" location? Is the fix to symlink the file location?

@martinrotter martinrotter self-assigned this Jun 27, 2019
@martinrotter martinrotter added Status-Needs-Help Someone else must provide better info, testing or PR. Status-Not-Enough-Data Ticket creator must append more precise info to the ticket. Type-Defect This is BUG!!! Type-Deployment Problem is caused by badly deployed application files. labels Jun 27, 2019
@martinrotter
Copy link
Owner

martinrotter commented Jun 27, 2019

I tested myself and wasn't able to reproduce the issue. Maybe some other things on your system changed? Not sure...

@cement-head
Copy link
Author

3.5.6 works perfectly. Using Ubuntu 18.04 Unity. Maybe I have a missing depedency? But I though AppImages negated that issue. What changed between 3.5.6 and 3.5.6+ in terms of handling of the URL?

@cement-head
Copy link
Author

Maybe this is the same issue: probonopd/linuxdeployqt#35

@cement-head
Copy link
Author

Brand new install 18.04.3 LTS, using Unity, can reproduce the identical issue.

@martinrotter
Copy link
Owner

3.5.6 works perfectly. Using Ubuntu 18.04 Unity. Maybe I have a missing depedency? But I though AppImages negated that issue. What changed between 3.5.6 and 3.5.6+ in terms of handling of the URL?

Literally nothing, really.

@martinrotter
Copy link
Owner

OK, will test soon.

@cement-head
Copy link
Author

cement-head commented May 8, 2020

I think it's because the AppImage uses the library installed by FF, and not what's in the AppImage

libsoftokn3.so: cannot open shared object file:

Here's the issue described in detail, specific to Ubuntu: probonopd/linuxdeployqt#35

@martinrotter
Copy link
Owner

OK, will check myself and see to error. It is probably deployment error because in normal installations across all systems the error cannot be reproduced.

@martinrotter martinrotter added this to the 3.6.2 milestone May 11, 2020
@martinrotter
Copy link
Owner

@martinrotter martinrotter removed Status-Needs-Help Someone else must provide better info, testing or PR. Status-Not-Enough-Data Ticket creator must append more precise info to the ticket. labels May 11, 2020
@martinrotter
Copy link
Owner

OK, closing for now, it seems fixed when I test it. Let me know if it really works for you too.

@martinrotter martinrotter added the Status-Fixed Ticket is resolved. label May 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status-Fixed Ticket is resolved. Type-Defect This is BUG!!! Type-Deployment Problem is caused by badly deployed application files.
Projects
None yet
Development

No branches or pull requests

2 participants