On 1/31/13, Colin Law <[email protected]> wrote: > On 31 January 2013 01:53, go linux <[email protected]> wrote: >> On 1/30/13, Colin Law <[email protected]> wrote: >>> On 29 January 2013 22:49, go linux <[email protected]> wrote: >>>> Oh and why was it working properly in September but not in January? >>>> Seems some sort of regression was introduced in the months since then. >>> >>> There is the issue of why rhythmbox is running in the first place, >>> perhaps it was not previously running and that is the change (for >>> unknown reason). >>> >>> Colin >>> >>>> >>>> >> >> Would this be a valid test? I don't have a live Squeeze-Gnome disk or >> I would boot it to see if rhythmbox is launched on a 'clean' system >> without user intervention. If it is, that would mean. it's always >> been that way and something else is causing the current bug. > > Quite possibly. Also you could try (on your system) logging on as a > different user to see whether it automatically runs there. If you > don't have another user then create one, a test user is often a useful > thing to have available. If it does not run for the test user then it > is something in your main user setup. > > Colin >
Good idea! I just created a new user and rhythmbox was NOT launched on startup. So it's something in my setup . . . but what? I haven't made any changes to my my system other than updates in a long time. I do have a few things from multimedia and backports installed but neither is in my active sources.list and I haven't messed with them in a long time. So what changed since September? _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
