Bug#883867: bookworm for accessibility
May apologies; I've gotten two different software packages with the same name confused. The one with the reviews is GPL3 Bookworm 1.1.2 by Siddhartha Das, in Vala. It was originally made for elementaryOS, a Ubuntu derivative. The one with an accessibility emphasis is for Windows, and it is the MIT Bookworm v0.1b4 by Musharraf Omer, in Python Thank you, Paul, I had not heard of ebook-speaker! I had come across daisy-player, so I'm not sure why I hadn't. Useful information. On 2020-03-16 12:52, Paul Gevers wrote: Hi hjenkins, On 16-03-2020 19:53, hjenkins wrote: Packaging the Bookworm e-reader could significantly improve the accessibility of Debian. Bookworm is written by blind developers, according to its website. Thanks for letting us know about this piece of software. Are you aware of ebook-speaker, already packaged in Debian. Also that has been written by a blind developer. That said, for this bug: if anybody is interested to do the initial work, I think the accessibility team welcomes the package under the team umbrella. Paul
Bug#883867: bookworm for accessibility
Packaging the Bookworm e-reader could significantly improve the accessibility of Debian. Bookworm is written by blind developers, according to its website. E-book readers are important if you are vision-impaired. Many e-book programs don't work well with screenreaders. Bookworm has and interface and documentation that is accessible to the vision-impaired, and it also has good independent reviews from sighted users. FBreader seems to have been proprietized (formerly GPL2 or later)! I'm not sure if it's been forked or what; there do not seem to be new updates.
Bug#941768: open-vm-tools/10.3.10 does not compile with 4.19.0-6-amd64 on buster kernel upgrade
i915/bxt_guc_ver9_29.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_ver9_33.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for module i915 /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-4.19.0-6-amd64 Found initrd image: /boot/initrd.img-4.19.0-6-amd64 Found linux image: /boot/vmlinuz-4.19.0-5-amd64 Found initrd image: /boot/initrd.img-4.19.0-5-amd64 Found linux image: /boot/vmlinuz-4.9.0-8-amd64 Found initrd image: /boot/initrd.img-4.9.0-8-amd64 Found memtest86+ image: /boot/memtest86+.bin Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin done Setting up linux-headers-4.19.0-6-common (4.19.67-2+deb10u1) ... Setting up linux-headers-4.19.0-6-amd64 (4.19.67-2+deb10u1) ... *So no errors on the dist-upgrade anymore, and I have some confidence in the new kernel! On running a new update and upgrade: The following packages were automatically installed and are no longer required: irqbalance linux-compiler-gcc-6-x86 linux-headers-4.9.0-8-amd64 linux-headers-4.9.0-8-common linux-image-4.9.0-8-amd64 linux-kbuild-4.9 runit-helper *I didn't think that I was using the old vmxnet module. Out of curiosity, I ran: # find / -name "vmxnet*" /lib/modules/4.19.0-6-amd64/kernel/drivers/net/vmxnet3 /lib/modules/4.19.0-6-amd64/kernel/drivers/net/vmxnet3/vmxnet3.ko /lib/modules/4.9.0-8-amd64/kernel/drivers/net/vmxnet3 /lib/modules/4.9.0-8-amd64/kernel/drivers/net/vmxnet3/vmxnet3.ko /lib/modules/4.19.0-5-amd64/kernel/drivers/net/vmxnet3 /lib/modules/4.19.0-5-amd64/kernel/drivers/net/vmxnet3/vmxnet3.ko /usr/share/man/man9/vmxnet.9.gz /usr/src/linux-headers-4.19.0-6-amd64/include/config/vmxnet3.h /usr/src/linux-headers-4.19.0-5-amd64/include/config/vmxnet3.h /usr/src/linux-headers-4.9.0-8-amd64/include/config/vmxnet3.h *Should be good now, anyway. Thanks again. On 2019-10-05 04:43, Bernd Zeimetz wrote: severity 941768 normal thanks Hi, please remove the open-vm-tools-dkms package dpkg -P open-vm-tools-dkms Its not supported anymore. If you really needed it because you were using the old vmxnet module - this is deprecated since ~10 years, maybe more. Otherwise there was no reason to install the package in the first place... For those rare cases I did not want to force the removal on upgrade time, as they will still have the chance to have networking with an old kernel. Bernd On 10/5/19 3:49 AM, hjenkins wrote: Package: open-vm-tools Version: 10.3.10 Severity: grave *While upgrading to buster, it is necessary to upgrade open-vm-tools from 10.1.5 to 10.3.10. My install of 10.3.10 seems to have worked, and in retrospect, it seems to work when reinstalled. PROMPT# apt-get install -f --reinstall open-vm-tools Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: irqbalance linux-compiler-gcc-6-x86 linux-headers-4.9.0-8-amd64 linux-headers-4.9.0-8-common linux-image-4.9.0-8-amd64 linux-kbuild-4.9 runit-helper Use 'apt autoremove' to remove them. 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/568 kB of archives. After this operation, 0 B of additional disk space will be used. N: Ignoring file 'testing.list.old' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension N: Ignoring file 'unstable.list.old' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension (Reading database ... 318081 files and directories currently installed.) Preparing to unpack .../open-vm-tools_2%3a10.3.10-1+deb10u1_amd64.deb ... Unpacking open-vm-tools (2:10.3.10-1+deb10u1) over (2:10.3.10-1+deb10u1) ... Setting up open-vm-tools (2:10.3.10-1+deb10u1) ... Processing triggers for systemd (241-7~deb10u1) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.28-10) ... *However, when I tried to upgrade to buster: POST# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-4.19.0-6-amd64 linux-headers-4.19.0-6-common linux-image-4.19.0-6-amd64 The following packages will be upgraded: linux-headers-amd64 linux-image-amd64 2 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 57.0 MB of archives. After this operation, 324 MB of additional disk space will be used. N: Ignoring file 'testing.list.old' in directory '/etc/apt/sources.list.d/' as it has a
Bug#941768: open-vm-tools/10.3.10 does not compile with 4.19.0-6-amd64 on buster kernel upgrade
Package: open-vm-tools Version: 10.3.10 Severity: grave *While upgrading to buster, it is necessary to upgrade open-vm-tools from 10.1.5 to 10.3.10. My install of 10.3.10 seems to have worked, and in retrospect, it seems to work when reinstalled. PROMPT# apt-get install -f --reinstall open-vm-tools Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: irqbalance linux-compiler-gcc-6-x86 linux-headers-4.9.0-8-amd64 linux-headers-4.9.0-8-common linux-image-4.9.0-8-amd64 linux-kbuild-4.9 runit-helper Use 'apt autoremove' to remove them. 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/568 kB of archives. After this operation, 0 B of additional disk space will be used. N: Ignoring file 'testing.list.old' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension N: Ignoring file 'unstable.list.old' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension (Reading database ... 318081 files and directories currently installed.) Preparing to unpack .../open-vm-tools_2%3a10.3.10-1+deb10u1_amd64.deb ... Unpacking open-vm-tools (2:10.3.10-1+deb10u1) over (2:10.3.10-1+deb10u1) ... Setting up open-vm-tools (2:10.3.10-1+deb10u1) ... Processing triggers for systemd (241-7~deb10u1) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.28-10) ... *However, when I tried to upgrade to buster: POST# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-4.19.0-6-amd64 linux-headers-4.19.0-6-common linux-image-4.19.0-6-amd64 The following packages will be upgraded: linux-headers-amd64 linux-image-amd64 2 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 57.0 MB of archives. After this operation, 324 MB of additional disk space will be used. N: Ignoring file 'testing.list.old' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension N: Ignoring file 'unstable.list.old' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension Do you want to continue? [Y/n] y Get:1 http://security.debian.org stable/updates/main amd64 linux-headers-4.19.0-6-common all 4.19.67-2+deb10u1 [8,241 kB] Get:2 http://ftp.ca.debian.org/debian stable/main amd64 linux-headers-amd64 amd64 4.19+105+deb10u1 [6,684 B] Get:3 http://ftp.ca.debian.org/debian stable/main amd64 linux-image-amd64 amd64 4.19+105+deb10u1 [8,076 B] Get:4 http://security.debian.org stable/updates/main amd64 linux-headers-4.19.0-6-amd64 amd64 4.19.67-2+deb10u1 [797 kB] Get:5 http://security.debian.org stable/updates/main amd64 linux-image-4.19.0-6-amd64 amd64 4.19.67-2+deb10u1 [48.0 MB] Fetched 57.0 MB in 2min 15s (423 kB/s) Reading changelogs... Done Selecting previously unselected package linux-headers-4.19.0-6-common. (Reading database ... 296390 files and directories currently installed.) Preparing to unpack .../linux-headers-4.19.0-6-common_4.19.67-2+deb10u1_all.deb ... Unpacking linux-headers-4.19.0-6-common (4.19.67-2+deb10u1) ... Selecting previously unselected package linux-headers-4.19.0-6-amd64. Preparing to unpack .../linux-headers-4.19.0-6-amd64_4.19.67-2+deb10u1_amd64.deb ... Unpacking linux-headers-4.19.0-6-amd64 (4.19.67-2+deb10u1) ... Preparing to unpack .../linux-headers-amd64_4.19+105+deb10u1_amd64.deb ... Unpacking linux-headers-amd64 (4.19+105+deb10u1) over (4.19+105) ... Selecting previously unselected package linux-image-4.19.0-6-amd64. Preparing to unpack .../linux-image-4.19.0-6-amd64_4.19.67-2+deb10u1_amd64.deb ... Unpacking linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ... Preparing to unpack .../linux-image-amd64_4.19+105+deb10u1_amd64.deb ... Unpacking linux-image-amd64 (4.19+105+deb10u1) over (4.19+105) ... Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.19.0-5-amd64 I: /initrd.img.old is now a symlink to boot/initrd.img-4.19.0-5-amd64 I: /vmlinuz is now a symlink to boot/vmlinuz-4.19.0-6-amd64 I: /initrd.img is now a symlink to boot/initrd.img-4.19.0-6-amd64 /etc/kernel/postinst.d/dkms: Error! Bad return status for module build on kernel: 4.19.0-6-amd64 (x86_64) Consult /var/lib/dkms/open-vm-tools/10.1.5/build/make.log for more information. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64 W: Possible missing firmware /lib/firmware/i915/bxt_dmc_ver1_07.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cnl_dmc_ver1_07.bin for module i915 W: Possible missing firmware /lib
Bug#915412: RFP: LON-CAPA (loncapa): federated online course platform
Package: loncapa Severity: wishlist Loncapa seems to be a mature (1992-) piece of GPL software, widely used by universities to serve online courses. It delivers course materials, aids communication, does assessment, and federates with other Loncapa servers, so that educational materials can be shared across the network. There is an annual "LON-CAPA Workshop and User Meeting" conference. Details: https://en.wikipedia.org/wiki/LON-CAPA It seems to have a release schedule about as frequent as Debian's, and detailed install instructions for Ubuntu, among others (mostly Red-Hat-related distros), but no Debian package: http://install.lon-capa.org/ I have no idea why; possibly there is some reason for a lack of Debian package? Maybe I have misunderstood something?
Bug#739293: update on obstacles
Johannes Schauer's note of the 21st Dec 2017 said he was waiting for a new Dudle release; 1.3 was released not quite a fortnight later, Jan 3, 2018. The extension packaging discussed here is apparently still to be done: https://github.com/kellerben/dudle/issues/82 I think, subject to correction, that this isn't blocking the inclusion of the main Dudle package in Debian, it would just make it awkward to incorporate the extensions. Is there anything I can help with here?
Bug#901824: RFP: Dudle -- server for web polls, AGPLv3
Package: wnpp Severity: wishlist X-Debbugs-CC: freedombox-disc...@lists.debian.org Dudle is a server for web polls; when-shall-we-meet, event registration, and suchlike. It can do end-to-end encryption and does not require cookies or client-side scripts. A Dudle server package would be useful for the Freedombox project (CC'd). Dudle seems to have sprung from the research group of the Chair of Privacy and Data Security at the University of Dresden (which has ~25 staff). The university hosts a server on which the public can create polls. The sourcecode is in Github. https://dudle.inf.tu-dresden.de/ Dudle is AGPL, Version 3: https://dudle.inf.tu-dresden.de/about.cgi
Bug#898237: unable to find IP for freedombox
Solved. Added workaround instructions for re-instating a fixed-IP network configuration after running freedombox-setup at: https://wiki.debian.org/FreedomBox/Hardware/Debian Most of the problem was my complete unfamiliarity with NetworkManager, including not knowing that a lot of things can't be changed through nmtui but can be changed through nmcli (as of May 2018).
Bug#898237: freedombox-setup breaks static IP configuration
Package: freedombox-setup
Version: 0.10
Summary: I installed Debian with static-IP network configuration, it
worked. I then ran freedombox-setup, and my network connection stopped
working.
There is apparently no way or no simple way to set up static IPs on
Freedombox. Ideally, I would like freedombox-setup to automatically
preserve the existing network configuration from the Debian box on which
it is installed. Failing that, I would like documentation of this hitch,
clear warnings and error messages, and manual instructions for using
static IPs on Freedombox, if possible.
Details:
I installed Debian from CD using the graphical install. I encrypted the
disk. Under "select and install software", I deselected all the Desktop
environments, because I wanted a command-line-only system.
As part of the install, I inputted the network information for the
static-IP-only, DHCP-less, behind-a-firewall LAN I wanted to connect to
while I set up the FreedomBox.
I asked not to participate in popularity-contest, but the text under the
progress bar said that I was installing it! I stopped it, went back,
re-selected the option, and it didn't change anything; I saw the same text
flicker past. I suspect this was actually just an minor, irrelevant error
with the messages.
I had a brief hang-up where the system refused to believe that it still
had an install disk ("Media change" error). I ejected and re-inserted, and
it produced a different error message; I ejected and re-inserted for a
second time, and it worked.
I got two sets of apparently harmless error messages, these:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846946
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807996
But apart from that, no problems, and I doubt these minor snags are
relevant. The connection worked, the install worked, I had a working
command-line-only Debian system.
I then installed debsig-verify using apt-get. I checked, and popularity
contest was not installed.
I followed the instructions at
https://wiki.debian.org/FreedomBox/Hardware/Debian
with one modification: I had no problems with the policykit-1 bug and did
not do the workaround. I did remove the network config, except for
loopback, from /etc/network/interfaces, as per the instructions.
I did the double reboot. It all looked fine, and I was impressed by
FreedomBox's ease on install. I didn't notice that I had no network
connection until I tried to configure the Freedombox, and couldn't get
hold of the interface.
In the new FreedomBox's /etc/hosts, I still had my assigned system name
and IP from the Debian install, but the new FreedomBox did not respond to
them from other machines on the local network. I couldn't access anything
outside the FreedomBox from the FreedomBox.
I could not edit the relevant fields via nmtui. I could select the fields,
but not type into them. There was no message telling me why.
Setting up static IPs via nmcli seems horribly complex, and reportedly
also sometimes unreliable, which for a server would be problematic:
https://bbs.nextthing.co/t/wanted-a-nice-simple-unambiguous-way-to-configure-static-ip/13870/7
Despite what it says in this 2015 bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797614
...disabling network manager ('systemctl stop network-manager"),
restoring the commented-out lines in /etc/interfaces, and running "ifdown
-a", "ifup -a" did not allow me to configure the network manually.
Expected behaviour:
I expect a new system to need network setup, but once the network is
working, I expected that it would continue working for at least the rest
of the install. I was not expecting that freedombox-setup would undo an
function-essential part of the Debian setup without warning me or giving
an error message.
Possible fixes:
If a FreedomBox has no functioning network when freedombox-setup
completes, I'd suggest that it should give an error message. This is
especially important if all subsequent configuration is likely to be done
over the network. An error message upon boot if a FreedomBox finds no
network connection might be generally good.
If I had read that FreedomBox did not support static IPs, I would not have
installed it, as I am required to use them. If FreedomBox does not support
static IPs, I suggest that it say so clearly in the documentation, perhaps
in the install instructions as well as the manual.
It seems to me that ideally, freedombox-setup would automatically preserve
any existing network configuration of any Debian box it is used upon.
Configuring the network only once, using Debian's well-tested network
configuration, might contribute to a simple, robust install.
If freedombox-setup cannot automatically preserve any functioning network
connection of a Debian box it is used upon, I suggest that it should give
warning when it is used on Debian systems having an unpreservable network
configurations.
For instance, if freedombox-setup is run on a machine with static IP
setup, and it can't preserve that se
