Open Rishabh42 opened 7 years ago
Most likely cause is --no-install-recommends
, but take care removing that, or the image may grow considerably. Either build with GNOME and recommends, and compare package list, or install Raspbian Stretch and compare package list. Use dpkg-query -W
to get the package lists in comparable form, and use diff
or meld
or some other tool to compare. Since new media detection is hardware independent, you can do these also on virtual machines running x86 or x86_64 architecture; much faster than waiting for a build.
Putting it another way, as you have Ubuntu as your native operating system, one of the packages already installed is responsible for the notification of new media insertion. Sugar relies on this. Also check sugar.log
in case the notification is happening but Sugar is not responding.
For further analysis, you might add a debugging message at the volume-added
signal handler given to the Gio.VolumeMonitor
, which would prove if the signal is received by Sugar;
Also check the group membership of the pi
account against the group membership of your own account on Ubuntu or the pi
account on Rasbian. If the account simply does not have the right to mount USB drives, then it is no surprise that it isn't told about them.
Thanks for the inputs will try the suggested approach. I've started using Debian stretch to build images now instead of Ubuntu
USB drives don't get automatically mounted on the frame whenever a new drive is connected. The command 'lsblk' when executed in the terminal activitiy does list the attached USB drives though.