Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1158778

Summary: odb file association does not work in kde file manager
Product: Red Hat Enterprise Linux 7 Reporter: Jose Traver <traverj>
Component: shared-mime-infoAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.0CC: caolanm, info
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-07 11:35:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
this makes it work none

Description Jose Traver 2014-10-30 08:32:04 UTC
Description of problem:
In a graphical environment, clicking a libreoffice database file (odb extension) using dolphin (KDE file manager) opens that file using ark instead of libreoffice-base. It also uses a wrong icon (compressed file).

Other libreoffice file extensions in KDE are opened by the rigt program and use the right icon (documents, spreadsheets, presentations, etc.). Gnome file manager opens odb files without any problem.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Select a KDE desktop during installation (or "yum group install" the KDE desktop)
2. Install libreoffice-base (yum install libreoffice-base)
3. Use dolphin to open a database odb file

Actual results:
File is opened by ark and uses an icon related to a compressed file.

Expected results:
File is opened by libreoffice-base and uses a database file icon.

Additional info:
I'm not sure about which package is this bug related to, so please forward it to the relevant owner.

Right-clicking the odb file and forcing it to be opened by libreoffice-base works well but it should work in a fresh installation as all the other libreoffice extensions do.

Comment 2 Caolan McNamara 2014-10-30 12:18:37 UTC
shared-mime-info I believe. At least I can make it work in dolphin by tweaking shared-mime-info

Comment 3 Caolan McNamara 2014-10-30 12:19:25 UTC
Created attachment 952075 [details]
this makes it work

Comment 4 info@kobaltwit.be 2014-11-01 18:25:18 UTC
I checked the upstream bug which is already marked as fixed. Pretty swift response.

In addition this bug is affecting Fedora 20 as well. Should I file a separate report against Fedora for this ?

Comment 5 Bastien Nocera 2015-04-07 11:32:37 UTC
Not enough bandwidth for RHEL 7.2. If you need something quicker, please contact your support representative.

(In reply to info from comment #4)
> I checked the upstream bug which is already marked as fixed. Pretty swift
> response.
> 
> In addition this bug is affecting Fedora 20 as well. Should I file a
> separate report against Fedora for this ?

It would require a separate bug, yes, but Fedora 20 is unlikely to receive this sort of update now, best to focus on newer versions.

Comment 6 RHEL Program Management 2015-04-07 11:35:54 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.