good news! (or bad, depending on what we want ;-)) i repeated the usual steps (removed all songs for the millionth time) and it worked. it seems that this time the application managed to write its configuration (?) before crashing(?). i forgot to mention it crashed quite often (the window just disappeared, usually not long after removing the "cursed" songs, but it did not happen each time). so perhaps it also crashed when exiting and that's why the new list of songs could not be written? (i'm guessing, perhaps it does not write the list on quit)
i have the apport crash file from one of such crashes but i don't know if i can safely reveal it as it contain a core dump, potentially including my ubuntu one password(?). as for the --debug, the only unusual thing for the otherwise succesful run was that the application did not quit on request, like if some threads were still trying to access the nonexistant smb share(?). so i just pressed ^C on the terminal after waiting a while. all subsequent runs are now perfect and the application quits completely and does not crash. assuming the rhythmbox saves its state in my home dir, i will have another chance to repeat this --debug run by restoring my /home backup. where should i look for its config files / song list? -- rhythmbox does not let me remove the old songs https://bugs.launchpad.net/bugs/574720 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
