dmks fails building module as of missing dependency

Status changed to 'Confirmed' because the bug affects multiple users.

When I do sudo dpkg -i 1fjbtndrv-kernel-source_2.3.2-1_i386.deb then I have this readout:

Preparing to replace fjbtndrv-kernel-source 2.3.2-1 (using 1fjbtndrv-kernel-source_2.3.2-1_i386.deb) ...

------------------------------
Deleting module version: 2.3.2
completely from the DKMS tree.
------------------------------
Done.
Unpacking replacement fjbtndrv-kernel-source ...
Setting up fjbtndrv-kernel-source (2.3.2-1) ...

Creating symlink /var/lib/dkms/fujitsu-tablet/2.3.2/source ->
                 /usr/src/fujitsu-tablet-2.3.2

DKMS: add completed.

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=3.8.0-16-generic....(bad exit status: 2)
ERROR (dkms apport): kernel package linux-headers-3.8.0-16-generic is not supported
Error! Bad return status for module build on kernel: 3.8.0-16-generic (i686)
Consult /var/lib/dkms/fujitsu-tablet/2.3.2/build/make.log for more information.
dpkg: error processing fjbtndrv-kernel-source (--install):
 subprocess installed post-installation script returned error exit status 10
Errors were encountered while processing:
 fjbtndrv-kernel-source

========================================================================

Looking at /var/lib/dkms/fujitsu-tablet/2.3.2/build/make.log :

DKMS make.log for fujitsu-tablet-2.3.2 for kernel 3.8.0-16-generic (i686)
Thu Apr 11 19:12:37 UTC 2013
make -C /lib/modules/3.8.0-16-generic/build M=/var/lib/dkms/fujitsu-tablet/2.3.2/build modules
make[1]: Entering directory `/usr/src/linux-headers-3.8.0-16-generic'
  CC [M] /var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.o
/var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.c:200:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘input_fujitsu_setup’
/var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.c:289:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘fujitsu_dmi_matched’
/var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.c:299:15: error: ‘fujitsu_dmi_matched’ undeclared here (not in a function)
/var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.c:364:30: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘fujitsu_walk_resources’
/var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.c:387:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘acpi_fujitsu_add’
/var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.c:425:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘acpi_fujitsu_remove’
/var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.c:444:13: error: ‘acpi_fujitsu_add’ undeclared here (not in a function)
/var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.c:444:3: error: initializer element is not constant
/var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.c:444:3: error: (near initialization for ‘acpi_fujitsu_driver.ops.add’)
/var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.c:445:13: error: ‘acpi_fujitsu_remove’ undeclared here (not in a function)
/var/lib/dkms/fujitsu-tablet/2.3.2/build/fujitsu-tablet.c:445:3: error: initializer element is not constant
/var/lib/dkms/fujitsu-...

me too with bcmwl dkms:
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.8.0-19-lowlatency /boot/vmlinuz-3.8.0-19-lowlatency
  run-parts: executing /etc/kernel/postinst.d/dkms 3.8.0-19-lowlatency /boot/vmlinuz-3.8.0-19-lowlatency
  Traceback (most recent call last):
    File "/usr/share/apport/package-hooks/dkms_packages.py", line 22, in <module>
      import apport
  ImportError: No module named apport
  Error! Bad return status for module build on kernel: 3.8.0-19-lowlatency (x86_64)
  Consult /var/lib/dkms/bcmwl/6.20.155.1+bdcom/build/make.log for more information.
Looking at the installed apport packages, I find that python3-apport is installed, but not python-apport. Installing python-apport made it work; probably a dependency problem.

Same here when building v4l2loopback-dkms 0.6.1?field.comment=Same here when building v4l2loopback-dkms 0.6.1

Status changed to 'Confirmed' because the bug affects multiple users.

I have Ubuntu Studio, and this happens to me with the lowlatency kernel, but not with the generic kernel. Hope it helps.

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.