On Fri, Dec 7, 2012 at 1:43 AM, drevicko <[email protected]> wrote:
> Ok, so I removed that filter (using vim) from the filters file, and now > I can run synaptic again - yay! > Glad to hear that! > > 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). > I have asked to know whether the new filter has been created by a user action or by the update (that's the worst case, and shouldn't ever happen) . > > 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) > Yes, I know, I am thinking of a fix stopping the user from entering newline characters in the package name filter (as package names never contain 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! > We will not allow newlines in the name filter, see above. > > - when I create a new filter, I am unable to delete it using the > synaptic gui interface. > This is a known issue, see bug #779756, fix has been committed, but not yet released. > > - 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 > I have never seen this, but might have been fixed along with some ancient bugs which have been fixed but not yet released, we'll have to retest after they get released. Thanks for your time and your help in investigating the issue. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
