errors returned by syscall are not user-friendly, should not be shipped raw to the user

Bug #1460658 reported by John Lenton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snappy
Expired
Undecided
Unassigned
15.04
Expired
Undecided
Unassigned

Bug Description

code like thise:

  if err := syscall.Setgroups([]int{gid}); err != nil {
   return err
  }

  if err := syscall.Setgid(gid); err != nil {
   return err
  }
  if err := syscall.Setuid(uid); err != nil {
   return err
  }

needs to wrap all those errors with a more helpful explanation of what we were doing when the error occurred.

Revision history for this message
Michael Terry (mterry) wrote :

This situation got better with https://code.launchpad.net/~chipaca/snappy/muppets/+merge/261376

Arguably fixed?

Michael Vogt (mvo)
Changed in snappy:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Snappy 15.04 because there has been no activity for 60 days.]

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Snappy because there has been no activity for 60 days.]

Changed in snappy:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.