Weird behavior when ejecting dmg files

Jump to First Reply
Posted:
in macOS edited January 2014
Hey,



I'll start by admitting that I'm a new Mac user - So I may be missing something, or doing something wrong...



Anyway, I'm experiencing a weird behavior when trying to eject a dmg file through the finder (after finishing installing a software, or later):



The finder doesn't let me eject the dmg and nothing happens, or even worse - the dmg doesn't eject and the finder window quits.



I'm encountering this behavior under 10.5.1



Any idea what's wrong?

Comments

  • Reply 1 of 7
    mr. memr. me Posts: 3,221member
    After you install software from a mounted disk image file, then quit the installer. Also make sure that you dismiss the Read Me file.
     0Likes 0Dislikes 0Informatives
  • Reply 2 of 7
    buddhabuddha Posts: 386member
    Quit anything that's running directly from the .dmg.
     0Likes 0Dislikes 0Informatives
  • Reply 3 of 7
    lirandlirand Posts: 174member
    Quote:
    Originally Posted by Mr. Me View Post


    After you install software from a mounted disk image file, then quit the installer. Also make sure that you dismiss the Read Me file.





    I did that of course.... Still - I don't think it's a reason for the finder to CRASH....
     0Likes 0Dislikes 0Informatives
  • Reply 4 of 7
    Hmmm. Well, give rebooting a shot, and from then after, heed the previous advice.
     0Likes 0Dislikes 0Informatives
  • Reply 5 of 7
    Quote:
    Originally Posted by lirand View Post


    Hey,



    I'll start by admitting that I'm a new Mac user - So I may be missing something, or doing something wrong...



    Anyway, I'm experiencing a weird behavior when trying to eject a dmg file through the finder (after finishing installing a software, or later):



    The finder doesn't let me eject the dmg and nothing happens, or even worse - the dmg doesn't eject and the finder window quits.



    I'm encountering this behavior under 10.5.1



    Any idea what's wrong?



    I'm not a new Mac user and mine does the same thing. It never occurred in Tiger but only started after I installed Leopard.
     0Likes 0Dislikes 0Informatives
  • Reply 6 of 7
    lirandlirand Posts: 174member
    Quote:
    Originally Posted by 1337_5L4Xx0R View Post


    Hmmm. Well, give rebooting a shot, and from then after, heed the previous advice.



    Rebooting solves the matter. But it still seems like a bug...
     0Likes 0Dislikes 0Informatives
  • Reply 7 of 7
    zoczoc Posts: 77member
    You can fill a bug report on discussions.apple.com



    Edit : There is already a thread about that Here
     0Likes 0Dislikes 0Informatives
Sign In or Register to comment.