[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2021-06-13 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=414742

Ahmad Samir  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|CONFIRMED   |RESOLVED

--- Comment #22 from Ahmad Samir  ---
This is an upstream bug, per David's comment in the link I posted.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2020-03-21 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=414742

--- Comment #21 from Ahmad Samir  ---
FYI, https://phabricator.kde.org/D28079#631730

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2020-03-16 Thread Walther Pelser
https://bugs.kde.org/show_bug.cgi?id=414742

--- Comment #20 from Walther Pelser  ---
I made further testing and I got the impression, that update-mime-database
always and only refuses to delete . In your comment 18 
is a line . if this line would have been executed properly,
kmimetypefinder5 would not have been able to find a matching entry. That´s my
point of view.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2020-03-16 Thread Walther Pelser
https://bugs.kde.org/show_bug.cgi?id=414742

--- Comment #19 from Walther Pelser  ---
And this is my result:
cat ~/.local/share/mime/application/vnd.lotus-1-2-3.xml

http://www.freedesktop.org/standards/shared-mime-info;
type="application/vnd.lotus-1-2-3">
  
  Lotus-1-2-3-Tabelle
  
  
  
  
  

OS is openSUSETumbleweed and this should have it´s own settings. I ask myself
why this doesn´t work as expected.
Okay, we should better stop here, as a consensus seems not to be possible.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2020-03-15 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=414742

--- Comment #18 from Ahmad Samir  ---
$ cat .local/share/mime/application/vnd.lotus-1-2-3.xml 

http://www.freedesktop.org/standards/shared-mime-info;
type="application/vnd.lotus-1-2-3">
  
  Lotus 1-2-3 spreadsheet
  


$ kmimetypefinder5 libvlccore.so.123 
application/vnd.lotus-1-2-3

$ gio info libvlccore.so.123 | grep standard::content-type
  standard::content-type: application/vnd.lotus-1-2-3

so that's how it works in KDE and GNOME (gio).

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2020-03-15 Thread Walther Pelser
https://bugs.kde.org/show_bug.cgi?id=414742

--- Comment #17 from Walther Pelser  ---

This is attachment Nr.2 in the list above
(https://bugs.kde.org/attachment.cgi?id=124258)

http://www.freedesktop.org/standards/shared-mime-info;
type="application/vnd.lotus-1-2-3">
  
  Lotus-1-2-3-Tabelle
  
  
  
  
  


And this is  from 
https://specifications.freedesktop.org/shared-mime-info-spec/shared-mime-info-spec-latest.html
 
(part of it)

"For example, when using the default paths, “Load all the /text/html.xml
files” means to load /usr/share/mime/text/html.xml,
/usr/local/share/mime/text/html.xml, and ~/.local/share/mime/text/html.xml (if
they exist, and in this order). Information found in a directory is added to
the information found in previous directories, except when glob-deleteall or
magic-deleteall is used to overwrite parts of a mimetype definition." 

If I understand the example right, then the line "" delets all
the settings in /usr/share/mime/application/vnd.lotus-1-2-3.xml and overwrites
it with the settings in ~/.local/share/mime/application/vnd.lotus-1-2-3.xml and
the "" will be deleted too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2020-03-15 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=414742

--- Comment #16 from Ahmad Samir  ---
(In reply to Walther Pelser from comment #15)
> The reason for me to file this bug was, that I expected, that the settings
> in ~/.local/share/mime/application would overwrite the settings in
> /usr/share/mime/application here file: vnd.lotus-1-2-3.xml. But this did not
> happen. So I thought, that this should be solved.

Well, it can't be solved because this is how QMimeDatabase works, it always
readds the "main glob pattern" (i.e. the first glob pattern in the system-wide
.xml file); that's been the case since around 2012.

And that also seems what other tools are doing:
gio info libvlccore.so.123 | grep standard::content-type
  standard::content-type: application/vnd.lotus-1-2-3

What we can do is change the filetypes KCM to echo what the QMimeDatabase is
enforcing, i.e. disallow removing the first glob pattern in the list...

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2020-03-15 Thread Walther Pelser
https://bugs.kde.org/show_bug.cgi?id=414742

--- Comment #15 from Walther Pelser  ---
The reason for me to file this bug was, that I expected, that the settings in
~/.local/share/mime/application would overwrite the settings in
/usr/share/mime/application here file: vnd.lotus-1-2-3.xml. But this did not
happen. So I thought, that this should be solved.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2020-03-15 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=414742

--- Comment #14 from Ahmad Samir  ---
Also I echo the comment from the upstream bug report:
"What real world problem does this cause, apart from a spreadsheet icon
appearing in the middle of your /lib directory in your file manager?"

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2020-03-12 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=414742

Ahmad Samir  changed:

   What|Removed |Added

 CC||a.samir...@gmail.com

--- Comment #13 from Ahmad Samir  ---
QMimeDatabase always prepends the first glob pattern in the relative mimetype
xml file from /usr/share/mime/ to the list of glob patterns, so even if you
remove it in your user account that glob will always be-read/added to the glob
patterns of that mimetype... AFAICS, this is the intended behaviour.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2019-12-08 Thread Walther Pelser
https://bugs.kde.org/show_bug.cgi?id=414742

--- Comment #12 from Walther Pelser  ---
In that case (second Bug of comment 11) I added a comment to bug # 354688 and
tried to describe it as transparent as possible. Maybe at will work.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2019-12-06 Thread Walther Pelser
https://bugs.kde.org/show_bug.cgi?id=414742

--- Comment #11 from Walther Pelser  ---
Maybe my description was too short and not transparent enough. So I think, I
caused this misunderstanding myself.
But I think now, that there are 2 defects in this one description:
First:
The Symlink with a name that ends with ".123" should not be identified as a
lotus-1-2-3 file.
Second:
If shared-mime-info would work correctly no one would ever had recognised the
first defect. The .local mime setting would always override the default
setting. But I wonder, why this does not happen. In this .local setting "*.123"
files or symlinks are definitely excluded from being identified as a
lotus-1-2-3 files.
Should this be a separate bug?
You have changed the status into confirmed, but "resolved as "fixed"" may
become changed too?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2019-12-05 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=414742

Nate Graham  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 414742] Symlink should reflect the MIME type of the file it points to, or else just be identified as a link

2019-12-05 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=414742

Nate Graham  changed:

   What|Removed |Added

Product|frameworks-kcoreaddons  |frameworks-kio
 Resolution|UPSTREAM|---
  Component|general |general
   Severity|normal  |minor
Version|unspecified |5.64.0
 Status|RESOLVED|REPORTED
URL|https://gitlab.freedesktop. |
   |org/xdg/shared-mime-info/is |
   |sues/123|
   Assignee|mp...@kde.org   |fa...@kde.org
Summary|shared-mime-info:   |Symlink should reflect the
   |libvlccore.so.123 conflicts |MIME type of the file it
   |with vnd.lotus-1-2-3|points to, or else just be
   ||identified as a link

--- Comment #10 from Nate Graham  ---
Oh, I understand the issue now. Yes indeed, this is our issue Sorry for sending
you on a wild goose chase!


STEPS TO REPRODUCE:
- Create a symlink called test.123 that points to a file that is NOT a Lotus
1-2-3 file
- Right-click on that symlink > Properties

EXPECTED RESULTS
- The symlink is identified with the MIME type of the file it points to, or
maybe as a symlink

ACTUAL RESULTS
- The symlink is identified as a Lotus 1-2-3 file.

-- 
You are receiving this mail because:
You are watching all bug changes.