| Summary: | crash using devices ioslave in directory selection dialog | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | James <Spy_Hunter> |
| Component: | general | Assignee: | Scott Wheeler <wheeler> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
James
2004-01-24 11:57:06 UTC
Well, first it really shouldn't even be possible to access those devices in the dialog as it's supposed to just be for local directories (and I'm unable to get it to do so). But at any rate JuK isn't actually even mentioned in the backtrace, so yes, it's a kdelibs bug. I like the ability to access the devices ioslave in the directory chooser, because every device actually represents a local directory (when mounted). Removing the ability to access it doesn't make sense. Why even have a devices ioslave if you can't use it in many cases? Anyway, I think the reason you can't access it is because you may not have it in your Open dialog Quick Access panel (the icons on the left). It is in there by default in new installations of KDE, and it is very convenient for quick access to files that are stored on other partitions (a link to /mnt would do this too, though in a less user-friendly way). Clicking it allows you to change the list of folders to start at devices:/ even though you can't type devices:/ into the bottom of the dialog. You can also access lan:/ and floppy:/ this way, and probably others. This may be the source of the problem. Subject: Re: crash using devices ioslave in directory selection dialog
On Sunday 25 January 2004 2:13, James wrote:
> I like the ability to access the devices ioslave in the directory chooser,
> because every device actually represents a local directory (when mounted).
> Removing the ability to access it doesn't make sense. Why even have a
> devices ioslave if you can't use it in many cases?
Well, it's fine for a lot of applications -- ioslaves in general that is --
but for JuK it's a bit more complicated because of the way that indexing and
caching of meta-data is done. Some protocols -- i.e. devices -- might make
sense, but many are more unclear (like FTP might make sense, but only on a
LAN and there the implementation is still difficult because FTP isn't a
random access protocol).
So -- yes, this is an issue, but it's much bigger than just the dialog and
it's one that I haven't figured out how I'm going to solve yet.
|