#9320 closed bug (fixed)
Virtual disk has no icon
Reported by: | dsjonny | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | Kits/Application Kit | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
If I create a virtual disk using diskimage, the disk has no icon in the mount menu or in the DriveSetup.
After I mount it, it has an icon in the Tracker, but in the mount menu there is still no icon.
I use the latest nightly image: 45092
Attachments (1)
Change History (19)
comment:1 by , 12 years ago
Component: | - General → Applications/Tracker |
---|---|
Owner: | changed from | to
comment:2 by , 12 years ago
Component: | Applications/Tracker → Kits/Application Kit |
---|
follow-up: 5 comment:4 by , 11 years ago
Please don't go through every bug you own and confirm that it's not fixed yet... unless you plan to provide additional details which help narrow down the issue, all it does is spams everyone with useless ticket updates.
follow-up: 6 comment:5 by , 11 years ago
Replying to umccullough:
Please don't go through every bug you own and confirm that it's not fixed yet... unless you plan to provide additional details which help narrow down the issue, all it does is spams everyone with useless ticket updates.
I find it can be helpful, especially for hardware related bugs and one time a year is fine btw :)
comment:6 by , 11 years ago
Replying to korli:
Replying to umccullough:
Please don't go through every bug you own and confirm that it's not fixed yet... unless you plan to provide additional details which help narrow down the issue, all it does is spams everyone with useless ticket updates.
I find it can be helpful, especially for hardware related bugs and one time a year is fine btw :)
I'm sorry for that. I didn't want to spam, I just saw that, I have many old tickets without any update since months. Usually I check the most of my (bug) tickets with the latest nightly images because there are many commits to the source. So, I don't know if there is some related to these tickets (I don't understand many). And many times I see "Is this still exists?" questions in the tickets, so that's why I updated sometimes the tickets. Next time I will only update if there is some "really useful" info.
comment:7 by , 10 years ago
How is this supposed to work? For other devices the icon is retrieved using an ioctl and the drivers in add-ons/kernel/drivers/disk provide an implementation with their respective icon(s). However the disk image file driver seems to be implemented directly in the disk device manager and I see no provision for ioctls there?
comment:8 by , 10 years ago
You may want to look at http://cgit.haiku-os.org/haiku/tree/src/system/kernel/device_manager/FileDevice.cpp#n248.
The disk device manager just uses devfs_publish_file_device() which gets served by this class.
comment:9 by , 10 years ago
I added B_GET_VECTOR_ICON there but it didn't work. Still no icon in DriveSetup nor Tracker mount menu. Attaching the patch if someone can spot what Idid wrong.
by , 10 years ago
Attachment: | 0001-FileDevice-implement-icon-ioctls.patch added |
---|
comment:10 by , 10 years ago
patch: | 0 → 1 |
---|
comment:11 by , 10 years ago
Does it work now, since you actually committed it already? In any case, I would check that the hooks are really called, otherwise, I couldn't spot anything wrong.
comment:12 by , 10 years ago
No, it doesn't work yet and I mixed up things in git again, I didn't mean to push these changes yet.
comment:13 by , 10 years ago
So, after further investigation:
- Sending the B_GET_DEVICE_ICON ioctl works.
- Getting the icon using get_device_icon also works.
- When the volume is mounted, BVolume::GetIcon returns the standard "disk" icon for it. This is what is shown in Tracker as well. When the volume is not mounted, BVolumeRoster does not enumerate it.
I get the correct icon in DriveSetup now, but I get the standard "disk" icon in Tracker mount menu. I also see that DriveSetup "mounted on" and "file system" columns are not filled properly after initializing the volume. So there are more missing links here.
comment:14 by , 9 years ago
patch: | 1 → 0 |
---|
comment:15 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:17 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:18 by , 5 years ago
Milestone: | R1 → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Oops, didn't see the DriveSetup part. Most likely a problem in the mime database then.