Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#2006 - Abiword stole my MIME types

Attached to Project: Arch Linux
Opened by Eugenia Loli-Queru (Eugenia) - Wednesday, 12 January 2005, 12:45 GMT
Last edited by Dale Blount (dale) - Wednesday, 12 January 2005, 13:00 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To dorphell (dorphell)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

After upgrading my Abiword 2.0.x to 2.2.2 yesterday, I now noticed that ALL my text-based files are now defaulting to AbiWord and that's very annoying because even simple files like READMEs or Makefiles are now opening with AbiWord. AbiWord didn't even ask me if I wanted to have this change done. Now, my Gnome is pretty annoying and changing back all these kinds of files with Nautilus' new mime system is daunting at best. Please don't let Abiword change all these mime types, but maybe, only for .doc or .abw files. For the simple text files, we have gedit, leafpad, emacs, vi etc, we don't need Abiword to behave an uninvited guest.
This task depends upon

Closed by  dorphell (dorphell)
Monday, 31 January 2005, 00:43 GMT
Reason for closing:  Deferred
Comment by Jan de Groot (JGC) - Wednesday, 12 January 2005, 13:13 GMT
It's rather a problem with gnome than a problem with abiword. If you install kate and havee /opt/kde/share in your XDG_DATA_DIRS, then your textfiles will open with a slow starting KDE component instead of with gedit.
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 12 January 2005, 13:25 GMT
Fine. Then, I expect the OEMs (in this case ArchLinux, Red Hat, Mandrake etc) to file bugs and/or send patches to the Gnome project for this and other issues. Plain users should only send bugs to their immediate linux distributor they use (like I did just now), not to the upstream developers. So, should I expect a resolution from ArchLinux? I definately can not fix the issue myself, there are countless files that Abiword now OwnZ.
Comment by Jan de Groot (JGC) - Wednesday, 12 January 2005, 15:43 GMT
You can fix: open a nautilus window, select a file you want to have changed and rightclick -> properties. Now in the open with tab: select the desired application.

We are delivering a 3rd party product as part of the distro, if you find packaging bugs or stuff that doesn't work, file it here. If you find errors that are clearly upstream, please file them upstream.
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 12 January 2005, 15:58 GMT
Are you out of your mind? It is not a simple filetype we are talking about. We are talking about MANY different filetypes that are now owned by Abiword, most of the time files that don't have an extension. I know how to change the default opening app for a file, problem is that abiword got hold to lot of them and it's simply too much work.

As for the upstream bugs, I completely disagree. All bugs encountered on a distro, must be filed on the distro by the users. If a bug is indeed upstream, the developers of the distro should either file the bug upstream themselves and/or submit patches. That's how the industry works and that's how it should be working. The user should never --ever-- be searching for who did what and why. That's how you can create a well-thought project. Not by pulling the "we are open source people, working in our time, spare us" story.
Comment by dorphell (dorphell) - Wednesday, 12 January 2005, 16:24 GMT
That is the true story though, which you still fail to grasp. Nobody here is paid. This is certainly an issue you now understand and can take the 10 minutes it'll take you to report it upstream. We're not using this "story" as an excuse but merely to remind people that we cannot do it all on our own, these little things you expect us to do users like you can attribute to. Users who use Arch and like it, should help out when they can, we are not a corporation, you did not pay us a cent for all we've given you thus far, and the help we're asking for here is not that demanding.

Loading...