Hi Pedro and folks, Please don't just reassign apport bugs to "dbus" because the top entries in a stack trace are from libdbus.
Like any library, libdbus will crash if it's given invalid data. As an extreme example, strlen (0) will crash inside libc's strlen() function - but it's obviously not a libc bug. libdbus is more complicated, so the patterns aren't quite that obvious, but it's the same theory. A good way to tell whether something is a libdbus bug, or a bug in an application, is that libdbus is used by a large number of applications - so you'd expect multiple applications to produce the same basic trace. If you have apport bugs in 20 different applications (e.g. HAL, Network Manager, Upstart, etc.), all with a similar or identical stack traces ending in libdbus, you've probably got a libdbus bug. If you have 20 apport bugs in the same application (e.g. evolution-data-server), all with different (or even similar) stack traces ending in libdbus, you've probably got a bug in that application. I am, as ever, quite happy to be grabbed on IRC to take a look at a bug. However I'm afraid I must be grumpy, and will reassign any bugs reassigned to dbus *without an explanation as to why you think they are a dbus bug, not a bug in that application* back to the application. Scott -- Scott James Remnant [email protected]
signature.asc
Description: This is a digitally signed message part
-- ubuntu-desktop mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
