Bug 2139751 - Launching qvgeapp breaks the user's file type associations
Summary: Launching qvgeapp breaks the user's file type associations
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: qvge
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Eugene A. Pivnev
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-03 10:39 UTC by Aleksey Ischenko
Modified: 2022-11-29 09:44 UTC (History)
1 user (show)

Fixed In Version: qvge-0.6.3-1.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-29 01:27:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Aleksey Ischenko 2022-11-03 10:39:28 UTC
Description of problem:

    Launching the application breaks the user's file type associations.

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

    qvge-0.6.3-0.3git2a44063.fc36.x86_64

How reproducible:

    Reproduced on every launch.

Steps to Reproduce:
  1. Set up a custom association in file manager with some type of file.

  2. Launch this app.

  3. After that, the association from the file manager will stop working.


Actual results:

  File type associations are broken.

  lesha@thinkpad ~]$ cat -n ~/.config/mimeapps.list
     1	[Default Applications]
     2	x-scheme-handler/http=google-chrome.desktop
     3	application/xhtml+xml=google-chrome.desktop
     4	text/html=google-chrome.desktop
     5	x-scheme-handler/https=google-chrome.desktop
     6	video/x-matroska=vlc.desktop
     7	
     8	[Added Associations]
     9	x-scheme-handler/http=google-chrome.desktop;
    10	application/xhtml+xml=google-chrome.desktop;
    11	text/html=google-chrome.desktop;
    12	x-scheme-handler/https=google-chrome.desktop;
    13	video/x-matroska=vlc.desktop;org.gnome.Totem.desktop;
[lesha@thinkpad ~]$ qvgeapp
QSocketNotifier: Can only be used with threads started with QThread
[lesha@thinkpad ~]$ cat -n ~/.config/mimeapps.list
     1	[Added%20Associations]
     2	application\xhtml%2Bxml=google-chrome.desktop
     3	text\html=google-chrome.desktop
     4	video\x-matroska=vlc.desktop
     5	x-scheme-handler\http=google-chrome.desktop
     6	x-scheme-handler\https=google-chrome.desktop
     7	
     8	[Default%20Applications]
     9	application\xgr=qvge.desktop
    10	application\xhtml%2Bxml=google-chrome.desktop
    11	text\html=google-chrome.desktop
    12	video\x-matroska=vlc.desktop
    13	x-scheme-handler\http=google-chrome.desktop
    14	x-scheme-handler\https=google-chrome.desktop


Expected results:

    File type associations are unchanged. (Or the file type for this application is added without breaking other types.)

Additional info:

[lesha@thinkpad ~]$ cat /etc/fedora-release 
Fedora release 36 (Thirty Six)
[lesha@thinkpad ~]$ rpm -qf `which qvgeapp`
qvge-0.6.3-0.3git2a44063.fc36.x86_64

Comment 1 Eugene A. Pivnev 2022-11-20 15:30:46 UTC
You are right, this is bug: https://github.com/ArsMasiuk/qvge/issues/164
Wait for new build.

Comment 2 Fedora Update System 2022-11-20 16:16:52 UTC
FEDORA-2022-6329eeac55 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6329eeac55

Comment 3 Fedora Update System 2022-11-21 01:30:39 UTC
FEDORA-2022-6329eeac55 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-6329eeac55`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6329eeac55

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2022-11-29 01:27:51 UTC
FEDORA-2022-6329eeac55 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Aleksey Ischenko 2022-11-29 09:44:41 UTC
Thanks, I checked it out. Everything became good.


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