Bug 235628 - Virtualbox .vdi files are treated as plain-text files making it easy to accidentally overload system by opening with kate
Summary: Virtualbox .vdi files are treated as plain-text files making it easy to accid...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kdecore (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-28 14:41 UTC by Keith Hughitt
Modified: 2024-09-14 16:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Keith Hughitt 2010-04-28 14:41:26 UTC
Version:            (using KDE 4.4.2)
Installed from:    Ubuntu Packages

Virtualbox hard-drive images (.vdi files) are often many Gigabytes. Because they are considered to be "plain-text" files by KDE/Dolphin, they are associated with Kate by default. Accidentally clicking such a file in Dolphin caused Kate to attempt to load the file resulting in a completely unresponsive system.

A better solution would be to either associate the files with Virtualbox, or to not give them any initial association.
Comment 1 Christoph Feck 2010-04-28 14:53:20 UTC
shared-mime-info does not have an entry for vdi files, from what I can see. You could file an enhancement request to add this at http://bugs.freedesktop.org/
Comment 2 Tanja Schulte 2010-10-17 15:21:32 UTC
I guess that's not the correct way but as the mimetype configuration allows to add mimetype definitions I created my own "application/virtualbox-vdi" one with an icon that shows a harddisk on a sheet.
Comment 3 Christoph Cullmann 2024-09-14 16:17:30 UTC
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann