Bug 982408 - Remote gthumb segfaults
Summary: Remote gthumb segfaults
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-09 00:11 UTC by Jan "Yenya" Kasprzak
Modified: 2015-02-17 15:59 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 15:59:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan "Yenya" Kasprzak 2013-07-09 00:11:07 UTC
Description of problem:
When attempting to run gthumb from a remote host using SSH tunnel, it segfaults.

Version-Release number of selected component (if applicable):
gthumb-3.2.2-1.fc19.x86_64

How reproducible:
100 %

Steps to Reproduce:
1. ssh -X fedora19host
2. cd .../directory_with_images
3. fedora19host$ gthumb .

Actual results:
libGL error: failed to load driver: r600
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
Segmentation fault

Expected results:
gthumb window displayed at ssh client.

Additional info:
fedora19host$ LIBGL_DEBUG=verbose gthumb .
libGL: OpenDriver: trying /usr/lib64/dri/tls/r600_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/r600_dri.so
libGL error: failed to authenticate magic 30
libGL error: failed to load driver: r600
libGL: OpenDriver: trying /usr/lib64/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/swrast_dri.so
Segmentation fault

Comment 1 rmhristev 2013-08-29 21:50:39 UTC
The same occurs when trying to run it as a different user.

Under X runing from a terminal:
    su <USER>
    gthumb

However, it appears to be related to the dri device permission, error message:
libGL error: failed to open drm device: Permission denied

Now, /dev/dri/card0 have permission 0660 and group ownership 'video'.

If I add the "different user" to the video group then gthumb works.

I hope this helps.

Comment 2 Fedora End Of Life 2015-01-09 18:47:00 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-02-17 15:59:35 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.