On 1/31/13, Colin Law <[email protected]> wrote: > On 31 January 2013 20:23, go linux <[email protected]> wrote: >> >> On 1/31/13, Colin Law <[email protected]> wrote: >>> >>> Is there a Debian users list you could ask that on? It must be some >>> configuration that you have accidentally changed (or purposefully >>> without realising the side effect) rather than something that has been >>> installed, or it would affect all users. >>> >> >> Well, I did post to the pkg-gnome-maintainers mailing list which was >> the contact listed on the rhythmbox package. Guess I'll put something >> together for the Debian users list in a bit. > > On the Debian list the issue to ask about is not the problem with the > camera, it is just with help to work out why rhythmbox is running > without you asking it. >
OK. Will do. Actually, I may have already asked that question. > > I think someone already suggested that you check the autostart setup > for the user (don't know where that is in Debian). > rhythmbox is not in the start-up list but the gnome-keyring and gnome-settings-daemon are. > >> >>> >>> ps -ejH might just tell you something (though I am not very hopeful) , >>> it will show the processes as a tree so you can see which process >>> started rhythmbox. >>> >> >> Um . . . Happy to do that but it's going to need a little translation. >> ;) The list related to rhythmbox in memory maps (in the system >> monitor) is REALLY LONG! But I can't find a way to print it out. > > Not sure what you mean about rhythmbox and memory maps, but if you > need to copy stuff out of the terminal then you can use Ctrl+Shift+C > (or probably Edit Copy in the menu, dependant on which terminal you > are using). Are you talking about syslog? If so then the very first > entries for rhythmbox (and a few before it) might be interesting in > case they give an idea as to why it is starting up. > The 'memory maps' are an option to view for individual processes in the gnome-system-monitor gui not in a terminal. I don't know what command that would translate to. Early on I went through all the logs and only found one useful reference in .xsession-errors that I posted possibly in my original email. > ps -ejH produces a very simple output, though it can be a few screens > long. Just look for rhythmbox down the right hand side and you will > see it nested under its parent. As I said it is a bit of a long shot > but it might be informative. > Apologies for being so dense. The only only mention of rhythmbox is under the gdm3 tree: 1799 1798 1798 ? 00:00:00 gdm3 2732 1798 1798 ? 00:00:00 gdm-simple-slave 2733 2733 2733 tty8 00:00:38 Xorg 2785 1798 1798 ? 00:00:00 gdm-session-worker 2820 2820 2820 ? 00:00:00 x-session-manager 2858 2858 2858 ? 00:00:00 ssh-agent 2872 2872 2872 ? 00:00:00 seahorse-agent 2882 2820 2820 ? 00:00:00 gnome-power-manager 2897 2820 2820 ? 00:00:04 gnome-panel 2901 2820 2820 ? 00:00:01 nautilus 2907 2820 2820 ? 00:00:00 nm-applet 2908 2820 2820 ? 00:00:00 gdu-notificatio 2910 2820 2820 ? 00:00:00 polkit-gnome-au 2911 2820 2820 ? 00:00:07 compiz 2914 2820 2820 ? 00:01:02 firefox-bin 3210 2820 2820 ? 00:00:00 plugin-container 2916 2820 2820 ? 00:00:00 rhythmbox 2921 2820 2820 ? 00:00:00 kerneloops-applet 2922 2820 2820 ? 00:00:00 python > >> >>> >>> I have lost track slightly, is it actually rhythmbox that is running >>> or a rhythmbox related process? >>> >> >> Is that a trick question? The process is listed as rhythmbox. > > No, I just had a recollection that rhythmbox plugins were mentioned at > one point so was just checking that the process is actually RB, rather > than check back through the 30 odd messages in the thread. > Both rhythmbox and the rhythmbox-plugins are in the 'memory maps' for 'rhythmbox' (PID 2916). I guesstimate there are several hundred other entries in that list - all sorts of stuff from media to python. I originally ran across rhythmbox-plugins when I searched in synaptic for 'MTP'. That was the first clue that rhythmbox might be involved in preventing shotwell from accessing the camera. I really appreciate the followup. I love a good mystery! _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
