GNOME Bugzilla – Bug 576455
leaves crufty sockets in /tmp on exit
Last modified: 2012-07-24 20:31:50 UTC
[ Original report: http://bugs.debian.org/515873 from Paul Wise ] gnome-system-monitor leaves sockets named like this behind on exit: /tmp/gnome-system-monitor.<user>.<num>
I can confirm this using System Monitor 3.2.1, setting the status to New.
I (In reply to comment #1) > I can confirm this using System Monitor 3.2.1, setting the status to New. I believe your patch for bug #646393 fixes this. Can you confirm?
No, that patch doesn't fix this. That only changes the location of the socket file, now it is left in the XDG user runtime dir, defaulting to $HOME/.cache/gnome-system-monitor.<user>.<num>. This should be removed when quitting the application. Or it would be even better to have a properly working GtkApplication c++ class, which would eliminate the need for libbacon. See bug 351087 for more details.
(In reply to comment #3) > No, that patch doesn't fix this. That only changes the location of the socket > file, now it is left in the XDG user runtime dir, defaulting to > $HOME/.cache/gnome-system-monitor.<user>.<num>. Yes, I realize this but at least it doesn't clutter up the /tmp/directory. This should be removed when > quitting the application. Or it would be even better to have a properly working > GtkApplication c++ class, which would eliminate the need for libbacon. See bug > 351087 for more details. Yes, I agree. That's why I wasn't really concerned about this bug nor Bug #646393. Both will be taken care of with a move to GtkApplication. I'll see if I can use the C api for GtkApplication to do this.
As fixing 351087 by migrating to GtkApplication will fix this, I am marking this as a duplicate of that bug. *** This bug has been marked as a duplicate of bug 351087 ***