Bug#998852: nyx: A config copied from /usr/share/doc/nyx/nyxrc.sample.gz breaks Nyx
All of these issues have been fixed upstream now: - https://github.com/torproject/nyx/pull/45 - https://github.com/torproject/nyx/pull/46 - https://github.com/torproject/nyx/pull/47 - https://github.com/torproject/nyx/pull/48 So this bug can be closed when the next Nyx release appears and is uploaded to Debian. -- Regards, Alexander Batischev
Bug#998852: Acknowledgement (nyx: A config copied from /usr/share/doc/nyx/nyxrc.sample.gz breaks Nyx)
Sorry, I didn't realise the sample config came from upstream. I still think the problems should be fixed, so I'll open issues and submit pull requests upstream. Sorry for the noise! -- Regards, Alexander Batischev
Bug#998852: nyx: A config copied from /usr/share/doc/nyx/nyxrc.sample.gz breaks Nyx
Package: nyx Version: 2.1.0-2.1 Severity: normal X-Debbugs-Cc: eual...@gmail.com Dear Maintainer, Some of the defaults in nyxrc.sample.gz prevent Nyx from starting, while others make it complain in the log. The first group includes: - `config_order order` prevents Nyx from starting, because "order" is not a correct value - `connection_order order` -- same as above - `color_override none` -- makes graphs invisible The settings that make Nyx complain are: - `graph_bound max_local` -- unsupported value `max_local`; perhaps you meant `local_max`? - `logged_events events` -- unsupported value `events` - `tor_chroot /path` -- nonexistent path - `data_directory ~/.nyx`, `unicode_support true`, `acs_support true` -- Nyx complains that these are unused I simply commented them all out, because I don't need any of them. Hopefully the sample config can be improved such that the user can just copy it, change the password, and get a working program. Thank you for your hard work! -- System Information: Debian Release: 11.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nyx depends on: ii python33.9.2-3 ii python3-pkg-resources 52.0.0-4 ii python3-stem 1.8.0-3 nyx recommends no packages. Versions of packages nyx suggests: ii tor 0.4.5.10-1~deb11u1 -- debconf-show failed
Bug#950964: anki: Anki won't play sound, claims mpv is too old
Package: anki Version: 2.1.15+dfsg-1 Severity: normal Dear Maintainer, When I start Anki, it reports on the stdout: mpv too old, reverting to mplayer Then it starts fine, but when I review a card that contains audio, no sound is played, and an error box is shown instead: Sound and video on cards will not function until mpv or mplayer is installed. Indeed, I only have MPV installed. If I install mplayer manually (2:1.3.0-8+b5 at the moment), it makes the error box go away, and audio plays fine. The message on stdout persists, though. I understand this is probably a temporary problem, and it'll be fixed when a newer version of MPV hits Debian testing, but until then, please consider adding mplayer as a hard dependency of Anki. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages anki depends on: ii libjs-jquery3.3.1~dfsg-3 ii libjs-jquery-flot 0.8.3+dfsg-1 ii libjs-jquery-ui 1.12.1+dfsg-5 ii libjs-mathjax 2.7.4+dfsg-1 ii libqt5core5a5.12.5+dfsg-8 ii python3 3.7.5-3 ii python3-bs4 4.8.2-1 ii python3-decorator 4.3.0-1.1 ii python3-distro 1.3.0-2 ii python3-distutils 3.8.0-1 ii python3-jsonschema 3.0.2-4 ii python3-markdown3.1.1-2 ii python3-pyaudio 0.2.11-1.1 ii python3-pyqt5 5.14.1+dfsg-2 ii python3-pyqt5.qtwebchannel 5.14.1+dfsg-2 ii python3-pyqt5.qtwebengine 5.14.0-1 ii python3-requests2.22.0-2 ii python3-send2trash 1.5.0-2 Versions of packages anki recommends: ii python3-matplotlib 3.1.2-1 Versions of packages anki suggests: pn dvipng pn lame ii mpv 0.32.0-1 -- debconf-show failed
Bug#917117: grub-efi-amd64-signed: doesn't mount cryptodisk
Hi, sorry it took me a while to respond. On Sat, Jan 12, 2019 at 10:53:37AM +, Colin Watson wrote: Could you please see if 2.02+dfsg1-10 fixes this? Both grub-efi-amd64 and -signed are now in testing, but they don't fix the issue. When I upgraded, my /boot/efi/EFI/debian/grub.cfg was rewritten with insmod and cryptomount commands removed. A couple of people pointed out that I forgot to add the luks module to the output of build-efi-images, which may have caused this. I might be misunderstanding you because I don't know anything about build-efi-images, but: to me the problem appears to be with the config, not modules. Even back on 2.02+dfsg1-6 I could `insmod` both "luks" and "lvm" modules, and boot Debian. So the modules *are* present, it's just that the config doesn't load them. -- Regards, Alexander Batischev PGP key 356961A20C8BFD03 Fingerprint: CE6C 4307 9348 58E3 FD94 A00F 3569 61A2 0C8B FD03 signature.asc Description: PGP signature
Bug#917117: grub-efi-amd64-signed: doesn't mount cryptodisk
Package: grub-efi-amd64-bin Version: 1+2.02+dfsg1+9 Severity: critical Dear Maintainer, I'm running a UEFI system. I have GRUB_ENABLE_CRYPTODISK=y in my /etc/default/grub. Ever since 2.02+dfsg1+6, each GRUB2 update removes cryptomount call from /boot/efi/EFI/debian/grub.cfg, and thus breaks the boot: GRUB drops into a recovery shell, unable to find my root partition (which is on LVM inside LUKS). /boot/efi is where I mount the ESP partition. I don't recall if the problem existed before 2.02+dfsg1+6. This has been reported in #908162 before (against 2.02+dfsg1+6). Ostensibly fixed in 2.02+dfsg1+7, but I still experience the bug. I'm running Debian testing which only has 2.02+dfsg1+8 at the moment, so I got 2.02+dfsg1+9 from Sid. That didn't fix the problem. For now, my solution is to manually edit aforementioned grub.cfg, and add the following at the very start: set prefix=(hd0,gpt1)/efi/grub insmod luks insmod lvm cryptomount (lvm/sda2_lvm-root) These lines are removed each time grub-efi-amd64 is reinstalled. Reinstallation of grub-efi-amd64-signed doesn't touch those lines. However, if I uninstall grub-efi-amd64-signed, reinstalling grub-efi-amd64 *doesn't* remove those lines. Thank you for maintaining the package! I've been running Debian on and off for almost ten years now, and that's the first critical bug I ever encountered. Please keep up the good work! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (600, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages grub-efi-amd64-bin depends on: ii efibootmgr 15-1 ii grub-common 2.02+dfsg1-9 grub-efi-amd64-bin recommends no packages. -- no debconf information
Bug#663198: linux-image-3.2.0.-1-amd64: ath9k module crashes a lot
Electronics Co., Ltd Bus 001 Device 004: ID 0b05:1788 ASUSTek Computer, Inc. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.2.0-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.41 ii initramfs-tools [linux-initramfs-tool] 0.100 ii linux-base 3.4 ii module-init-tools 3.16-1 Versions of packages linux-image-3.2.0-1-amd64 recommends: ii firmware-linux-free 3 Versions of packages linux-image-3.2.0-1-amd64 suggests: pn extlinux 2:4.05+dfsg-2 pn grub-pc1.99-14 pn linux-doc-3.2 none Versions of packages linux-image-3.2.0-1-amd64 is related to: pn firmware-atherosnone pn firmware-bnx2 none pn firmware-bnx2x none pn firmware-brcm80211 none pn firmware-intelwimax none pn firmware-ipw2x00none pn firmware-ivtv none pn firmware-iwlwifinone pn firmware-libertas none pn firmware-linux none pn firmware-linux-nonfree none pn firmware-myricomnone pn firmware-netxen none pn firmware-qlogic none pn firmware-ralink none pn firmware-realteknone pn xen-hypervisor none -- debconf information: linux-image-3.2.0-1-amd64/postinst/depmod-error-initrd-3.2.0-1-amd64: false linux-image-3.2.0-1-amd64/postinst/missing-firmware-3.2.0-1-amd64: linux-image-3.2.0-1-amd64/postinst/ignoring-ramdisk: linux-image-3.2.0-1-amd64/prerm/removing-running-kernel-3.2.0-1-amd64: true -- Regards, Alexander Batischev 4096R/0C8BFD03 CE6C 4307 9348 58E3 FD94 A00F 3569 61A2 0C8B FD03 signature.asc Description: Digital signature
Bug#595431: Aborting fsck aborts all scripts in rcS.d
Hi! I encountered this bug, too. How does changing /etc/init.d/rc with the below patch modify behaviour? No, Kel, nothing changed. Sorry. -- Regards, Alexander Batischev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536617: Fwd: Bug#536617: Half a year passed and still no support…
Hi, On 4 May 2010 20:10, RISKO Gergely ri...@debian.org wrote: Thanks for your interest, in #549967 I commented why I can not upload a version 0.25 or 0.26 currently. Okay, I see. Waiting for new ffmpeg build then :) If subtitle support is really important for you even with the current 0.24 version, you can try to install libkate-dev, liboggkate-dev and then after an `apt-get source ffmpeg2theora' try `dpkg-buildpackage -b' in the source directory. Please report success/failure. Yep, that worked! I successfully built ffmpeg2theora and installed it instead of standard version. But when I tried to create OGV file with embedded subtitles, I faced with problem: ffmpeg2theora works good, but after encoding it says about some kind of error (I remember there was -4 at the end, but I didn't save exact text). Then, when I open ogv in MPlayer, it recognizes audio and video streams, but says that stream 3 have unknown type (stream 3 supposed to be subtitles). I'm pretty sure that this is ffmpeg2theora's bug, not Debian's one. I didn't google it, through - as I said, I didn't save error's text, so I have almost nothing to start with. I think I also should mention that I have debian-multimedia repositories included to /etc/apt/sources.list, so libraries versions in my system may differ from pure Debian's one. With best regards, Alexander Batischev
Bug#536617: Half a year passed and still no support…
Hi! So, time passes but ffmpeg2theora still have no subtitles support. I'm running Squeeze now, so I have ffmpeg2theora version 0.24-2+b1 and libkate1 version 0.3.7-3, but when I try to create .ogv file with embedded subtitles, I get this message: WARNING - Kate support not compiled in, subtitles will not be output - install libkate and rebuild ffmpeg2theora for subtitle support Are there any hope to get support in future release or even earlier, maybe? With best regards, Alexander Batischev
