Comment 7 for bug 1401816

With the following changes to /etc/login.defs, the bumblebee and primus packages installed fine on my machine:

<diff>
--- a/login.defs
+++ b/login.defs
@@ -177,8 +177,8 @@ PASS_WARN_AGE 7
 UID_MIN 1000
 UID_MAX 60000
 # System accounts
-#SYS_UID_MIN 100
-#SYS_UID_MAX 999
+SYS_UID_MIN 100
+SYS_UID_MAX 999

 #
 # Min/max values for automatic gid selection in groupadd
@@ -186,8 +186,8 @@ UID_MAX 60000
 GID_MIN 100
 GID_MAX 60000
 # System accounts
-#SYS_GID_MIN 100
-#SYS_GID_MAX 999
+SYS_GID_MIN 100
+SYS_GID_MAX 999

 #
 # Max number of login retries if password is bad. This will most likely be
</diff>

Here's the snippet from /var/log/apt/term.log

<snip>
Log started: 2015-08-11 13:07:50
Selecting previously unselected package bumblebee.
(Reading database ... 295665 files and directories currently installed.)
Preparing to unpack .../bumblebee_3.2.1-5_amd64.deb ...
Unpacking bumblebee (3.2.1-5) ...
Selecting previously unselected package primus.
Preparing to unpack .../primus_0~20131127-2_amd64.deb ...
Unpacking primus (0~20131127-2) ...
Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-61-generic
Processing triggers for ureadahead (0.100.0-16) ...
ureadahead will be reprofiled on next reboot
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up bumblebee (3.2.1-5) ...
Adding members from group(s) 'adm sudo admin' to 'bumblebee':
rkersh syslog
Adding user rkersh to group bumblebee
Adding user syslog to group bumblebee
Selecting 01:00:0 as discrete nvidia card. If this is incorrect,
edit the BusID line in /etc/bumblebee/xorg.conf.nouveau .
bumblebeed start/running, process 17662
Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-61-generic
Processing triggers for ureadahead (0.100.0-16) ...
Setting up primus (0~20131127-2) ...
Log ended: 2015-08-11 13:08:39
</snip>

Note, that if I do "man login.defs" I see the following:

BUGS
       Much of the functionality that used to be provided by the shadow
       password suite is now handled by PAM. Thus, /etc/login.defs is no
       longer used by passwd(1), or less used by login(1), and su(1). Please
       refer to the corresponding PAM configuration files instead.

Could that explain why on my Ubuntu 14.04, the fact that the previous settings for SYS_GID_MIN, SYS_GID_MAX were not causing any problems? Is the bumblebee package relying on something that it shouldn't? I have no idea if this is the case ... just throwing the information out there.

More details:
Personally, I never touched /etc/login.defs since the original installation of Ubuntu. I tried to do a dpkg-reconfigure of the login package, but this didn't seem to do anything.