Ok, so I removed that filter (using vim) from the filters file, and now I can run synaptic again - yay!
It was over a year ago when the filter was added, so my memory is very hazy, but I think it's quite possible that I created that filter. I probably got the list of names from the dependencies output from apt- cache or something (guess that's not important). The following observations may or may not be interesting - I made them playing around with name filters in the synaptics filters dialog window: - any name filer containing a new line I tried caused the crash (both valid and non-valid regex's, even a single newline character) - entering an invalid regex generates "regexp compilation error" in the terminal, doesn't produce a name filter in the filters file, but the invalid regex is visible (but grey) if I reopen the filters dialog. NOTE: if there is a newline in the regex, it's stored in the filters file and DOES reappear in the dialog! - when I create a new filter, I am unable to delete it using the synaptic gui interface. - the first time I open the filters dialog (Settings->Filters) I get this in the terminal: (synaptic:21119): GLib-GObject-WARNING **: invalid (NULL) pointer instance (synaptic:21119): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873860 Title: synaptic won't run in sudo mode and produces a segfault in the syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/873860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
