possibly continued at https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4759#register-pane
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4759
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4759
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1880598 ***
https://bugs.launchpad.net/bugs/1880598
** This bug has been marked a duplicate of bug 1880598
package v4l2loopback-dkms 0.12.3-1 failed to install/upgrade: installed
v4l2loopback-dkms package post-installation script subprocess returned error
Duplicate of #1883721 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880598
Title:
package v4l2loopback-dkms 0.12.3-1 failed to install/upgrade:
installed v4l2loopback-dkms package post-installa
The original bug does not include the make.log mentioned in the build error.
Here is a make log, which at least results in the same error code.
NB this is for a slightly different system, being DKMS make.log for
v4l2loopback-0.12.3 for kernel 5.8.0-25-generic (x86_64)
** Attachment added: "make.
Actually, no, that's too flippant. I'm keenly intersted in this patch
being committed. Every week I run into it, and it causes me pain. In
particular it means that Ubuntu 9.04 server has no JeOS support for
VMware, since installing GCC to aply a single patch is hardly JUST
enough OS. I also regard
It's the project's way of encouraging us to become core committers?
--
Compilation of vmhgfs module fails
https://bugs.launchpad.net/bugs/362579
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I beg your pardon - it seems I aonly addressed the second part of your
problem - the first part, the absence of the wsgi.load file, is still
unexplained.
but - that's not a problem either, except arguably one of naming
convention the mod_wsgi .load file exists and is named
/etc/apache2/mo
I believe this is expected behaviour for apache modules under
Debian/Ubuntu, which have some light wrapper scripts to ease enabling
and disabling the modules without installing or uninstalling them.
To enabled mod-wsgi, do
# a2enmod mod-wsgi
this is documented in /usr/share/doc/apache2/README.
