Launchpad users are not associated with Linux Kernel Bug Tracker comments

Asked by David Ward on 2018-06-11

When using remote bug watches, Launchpad will associate a comment that was made directly on a Mozilla bug with the existing Launchpad user who made that comment. However, it does not do the same thing for Linux kernel bugs.

For example, see the following comment imported from into a Launchpad bug:
Clicking my name above the comment text will display my Launchpad user page. I did not have to do anything to make this work.

Now, see the following comment imported from into a Launchpad bug:
Clicking my name will take you to the Launchpad user page for "david.ward-linux-kernel-bugs" (which does not exist). If I try to claim this user name, Launchpad returns an error because it is not a valid e-mail address. Comments made by other users have the same issue.

For both Mozilla and the Linux kernel, my Bugzilla account is registered with the same e-mail address; this e-mail address is invisible when someone views the bug anonymously; and this e-mail address becomes visible when someone logs into the Bugzilla server.

Question information

English Edit question
Launchpad itself Edit question
No assignee Edit question
Last query:
Last reply:
Colin Watson (cjwatson) said : #1

It's not clear to me that we can do very much about this. I might be wrong, but as far as I can see Bugzilla only tells us about the username of the commenter, not their email address, even if it stores more information itself. It is then of course difficult to allow somebody to securely claim the identity, since we have no way to verify it.

In any case, for cases where there appears to be a software defect rather than some kind of administrative action we need to take, Launchpad Answers isn't the right place - software defects should be filed as bugs. It would be reasonable to use the "Create bug report" action on this question to convert this question into a bug, even if it's not clear that we can do very much about it at the moment.

Colin Watson (cjwatson) said : #2

(By "tells us", I'm referring to the XML-RPC API that we use to fetch information from Bugzilla, not to its HTML representation.)

David Ward (dpward) said : #3 and expose the same API though, right? How is it working for Mozilla bugs then?

(I'll file bugs in the future; there are many places on that suggest using Launchpad Answers to get in touch with specific questions.)

Colin Watson (cjwatson) said : #5

Oops, meant to mark this as Answered again with my last message.

Colin Watson (cjwatson) said : #6

Well, it might be reasonable to expect the same API, but in fact it's not quite. Maybe it's a Bugzilla version difference or maybe some kind of configuration difference; I'm not sure. But look at the following:

$ python
>>> import xmlrpclib
>>> mozilla = xmlrpclib.ServerProxy('')
>>> mozilla.Bug.comments({'comment_ids': [5440259]})['comments']['5440259']['creator']
'david.ward@<domain redacted>'
>>> kernel = xmlrpclib.ServerProxy('')
>>> kernel.Bug.comments({'comment_ids': [1052651]})['comments']['1052651']['creator']

Launchpad Answers is the right default for our documentation, I think, because things that really are just questions or support tickets or that kind of thing do belong there. It's just that actual defects in the software itself belong in Launchpad Bugs.

[Reposted comment to redact email address, since it's marked private on your Launchpad account.]

Can you help with this problem?

Provide an answer of your own, or ask David Ward for more information if necessary.

To post a message you must log in.